Backup directory naming

[sperkins]

Dear all,

We are using the latest version of Veeam BandR v6 (migrated from v5) are are very happy with it.

One question regarding the backup repository : it seems that certain jobs are created at the root directory of the share and some have had a directory created (which is much better), and dont have the job name in the file name.

In 1 or 2 cases, it seems that when we renamed a job some files kept the original name.

Do you know how this happened ? Is there a way to "move" or "rename" the files ?


Thanks,
Sebastian

[dellock6]

This happens when you upgrade: migrated jobs from v5 stays in all in one folder, while when you create them from scratch in v6 they are separated in one folder per jobs.
I'm confused about the naming: all backup files has the name of the job as prefix, regardless where they are saved...

[Gostev]

Is there a way to "move" or "rename" the files ?

You can move your backup files into any other folder within the repository root folder, and map the job into the new location using the Map Backup functionality.

[sperkins]

You can move your backup files into any other folder within the repository root folder, and map the job into the new location using the Map Backup functionality.

Thanks for the idea, I will go for the remap into a new directory.

This happens when you upgrade: migrated jobs from v5 stays in all in one folder, while when you create them from scratch in v6 they are separated in one folder per jobs.
I'm confused about the naming: all backup files has the name of the job as prefix, regardless where they are saved...

Thanks now I know what happened. For the naming, the initial job name seems mapped to the folder name and .vbm file. If I rename the job, only the .vrb's and vdk's get updated. Is this correct ?

Sebastian

[foggy]

For the naming, the initial job name seems mapped to the folder name and .vbm file. If I rename the job, only the .vrb's and vdk's get updated. Is this correct ?

Yes, I see the same behavior.