transition to the per-machine format for source job

[Danh3]

Hello Community,

Having upgraded to V12, we still have Legacy Backup Copies in use.

To transition to the per-machine format, the source repository needs to be updated to 'Use per-machine backup files.'

Here are the details and questions related to this upgrade:

The source job for file servers currently backs up to the repository located at D:\c-primary. Due to limited available space, creating a new repository is not an option. Is it possible to create a new folder (C-primar-nf) on the D: drive to act as a new backup repository, hosting data in per-VM format?

Ex: creating a new folder, c-primary-nf, in D: and adding "D:\c-primary-nf" to the Veeam backup repository while enabling the option 'Use per-machine backup files.'

Some source jobs will need to continue running in the old format for repo D:\c-primary. Does this approach enable the coexistence of both the new per-machine format (D:\c-primary-nf) and the old format (D:\c-primary) on the same drive for the source jobs?

thanks

[Mildur]

Hello Dan

Due to limited available space, creating a new repository is not an option.

Where have you found this information, that a new repository is required?

Some source jobs will need to continue running in the old format for repo D:\c-primary.

When you change the setting to 'Use per-machine backup files', these jobs will keep producing per-job backup files until you upgrade them to the new format or run an active full backup.

Best,
Fabian

[Danh3]

@Fabian

thanks and within the same repository can host both new and old formats vols as long as they are not nested.