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

[Mildur]

Hi Fleodux

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

That would work with block-based repositories, where you can simply delete VBK and VIB files from the target.

With object storage, you cannot delete individual objects from the target in the same way, since we do not store VBK/VIB files there. It is also not possible to select and delete individual restore points for a single VM or machine through the console or API.

It is a request we receive from time to time, but there is currently no ETA.
I am happy to add you as +1 to the request.

Best,
Fabian

[fleodux]

Oh, I actually never noticed that, thank you for letting me know and thank you for adding me to the request.

Even if recreate a SOBR with an empty performance tier, I can see background retention is not working with archive tier and is not working with capacity tier when there's no job configured against it.
https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
So we will need to keep all restore points for the entire retention time (6 months for capacity tier, 5 years for archive tier)