Late to the party but we are struggling with the 50 chars limit too. Would be very nice if this could get expanded.
Edit:
The reason behind this is:
When executing a standard workstation backup job which its name has more than 50 chars, there is no problem storing the whole foldername on the filesystem:
![Image]()
But for the according backup copy job on the other hand, the name gets cut over after 50 chars, which results in the following ugly behaviour:
![Image]()
As you can see on the screenshot there are two other jobs which have a similiar hostname. For those two jobs the names are being cut on exactly the most wrong point so that the following job's folder name is being extended with an underline _1.
It's very unexpected that backup cop jobs are behaving differently from standard backup jobs according to foldernames on the filesystem.
Edit:
The reason behind this is:
When executing a standard workstation backup job which its name has more than 50 chars, there is no problem storing the whole foldername on the filesystem:
But for the according backup copy job on the other hand, the name gets cut over after 50 chars, which results in the following ugly behaviour:
As you can see on the screenshot there are two other jobs which have a similiar hostname. For those two jobs the names are being cut on exactly the most wrong point so that the following job's folder name is being extended with an underline _1.
It's very unexpected that backup cop jobs are behaving differently from standard backup jobs according to foldernames on the filesystem.
Statistics: Posted by Tecbil — Nov 29, 2024 3:32 pm
