Feature Request: Longer Job Name, Table Filter and Row Copy

[volkanvk]

Hi, i will sugest some feature request for the actual VBR v11.

• Job Names are to short with the maxmimu of 50 characters because we use the same jobname with an extension for the copy jobs and i must truncate everytime hte job names..
  On the VBR console on the lists like the disk/copy backups a filter on the differents headers to filter/get items for a defined time or range instead expdanding all disk jobs and seeking for the date...
  Copy selected rows in the console to paste direkt to excel

[HannesK]

Hello,
and welcome to the forums.

Job Names are to short with the maxmimu of 50 characters

that looks like a bug for the backup copy jobs (not a feature request ). I just tried it out: backup, surebackup, replication, cdp and tape jobs accept longer names. there is only a warning with longer than 50 characters.

On the VBR console on the lists like the disk/copy backups a filter on the differents headers to filter/get items for a defined time or range instead expdanding all disk jobs and seeking for the date...

what is the overall goal? could we get some more information on the use case? Maybe there are alternative ways to do the same.

Copy selected rows in the console to paste direkt to excel

same question like above... what is the goal of having that data in Excel? Is there maybe already everything available in VeeamONE (which can do Excel exports)?

Best regards,
Hannes

[HannesK]

ok, the 50 characters limit for backup copy jobs is a feature, not a bug... it's to avoid of maximum path lengths issues. changing that part of the software could only be justified if many customers think that the 50 characters a problem for them.

[Tecbil]

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:

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.