Archive tier migration

[fleodux]

Hello,

I currently have a SOBR with capacity tier and archive tier that I need to migrate to a new Veeam Appliance for restore purposes only.
Performance tier is only 4 weeks of retention so I will wait for the retention points to expire.
Capacity tier is 6 month retention and archive tier is 5 years retention.

I assume capacity tier can be added as a standalone S3 repo and rescan for restore points, what about the archive tier ?
Can it be added also as a standalone S3 repo ? Is archive appliance still needed ?
Or do I need to recreate a new SOBR on the new server

[Mildur]

Hi Fleodux

Rescan is for “direct to object storage” and “object storage in Performance Tier“ repositories.

For Capacity Tier and Archive Tier, please use the import option on the new backup server. Configuring a SOBR is not required for restore only.

Keep in mind, with imported backups, there won’t be any retention processing. To make sure retention is still applied, a SOBR is required.
It may be better if you reconnect performance, capacity and archive tier to the new VSA and recreate your SOBR. Then run a rescan of the SOBR.

Best,
Fabian

[fleodux]

Hi,

Thank you for your response.

It will be impossible to reconnect performance tier as it is a jbod attached to the physical current Veeam server and we are migrating to an appliance in a VM.

Also, backup repos are imported for restore purposes only, there won't be any backup jobs running against them, so there won't be any retention processing, as far as I know, even with a SOBR. (Assuming the retention processing is done by the backup job)

I thought we can process retention manually once a month/quarter.

Best Regards