Import SOBR with Capacity Tier to different VBR instance?

[squebel]

Hello,

I am completely shutting down an environment but have the need to retain a large set of backups, with GFS archives, that are being written to a SOBR that has 3 performance capacity extents. This SOBR also has the capacity tier enabled with the full copy option enabled. I would like to import all of these backups into the catalog of a completely different VBR server. I know how to get the performance capacity vbk/vibs over to the new environment without issue but I am not sure how to import the entire SOBR in especially since it has the capacity tier copies as well. I have opened case 07441209 regarding this and am working with Support but wanted to ask here.

Thanks in advance!

[Mildur]

Hi squebel

1.) Performance Tier:
- Add your performance tier extents as simple repositories (no rescan yet!).
- Create a new Scale-Out Backup Repository (SOBR) and add all three extents.
- Rescan your SOBR.

2.) Backups on Capacity Tier:
- Connect your object storage bucket with the new backup server and add it as a capacity tier for the new SOBR. The wizard will start an import session.

Alternative for Step 2: Instead of adding the bucket as a capacity tier, you can perform an import operation. This will also allow you to gain access to the backups from the previous capacity tier bucket.

Best,
Fabian

[squebel]

Hey Fabian, thank you for the reply!

If I did the alternative to step 2 and didn't tie that bucket to the SOBR as a capacity tier, the restore points on the capacity tier wouldn't age automatically with the restore points in the performance extents, right?

[squebel]

Fabian, I followed your steps here but the VBR now sees no restore points on the capacity tier for some reason. I have rescanned a few times and just get an error. I will work with support on this but it did not go as smooth as had hoped.

[Mildur]

Capacity tier restore points must be „imported“, not rescanned.
Did you add the bucket as a capacity tier to the new SOBR or did you leave it as standalone? If standalone, try an import:

https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian

[squebel]

Well, I added it as a standalone first and told it not to rescan. Then I added it as a capacity tier to the SOBR and it looked like it was going to rescan. I gave it the encryption passphrase and it asked me about syncing All or Latest restore points. I said Latest and then it finished but there are no restore points showing up. I then turned off the capacity tier to the SOBR and then attempted the Import operation on the bucket as a standalone repo. It said it would take some time. It seemed to finish almost immediately but I don't see anything running, no events of the import and no restore points.

[Mildur]

Nothing in Capacity Tier (Imported)? No import session visible somewhere in the history menu?

Please open a case so we can check where the process is not working. I run the procedure before posting it here in my lab, but without encryption enabled. I‘ll run it again tomorrow with encryption on.

Best,
Fabian

[squebel]

Nothing that I can see. 07441209 is open. I've updated the case with this new info and waiting to hear back. I fear that maybe I did not detach the object repo correctly from the old VBR server or something.

[squebel]

I get the following message which is interesting that it calls out "capacity tier extent"...

10/3/2024 4:53:32 PM Processing capacity tier extent of Offsite-Archive 3
10/3/2024 4:55:32 PM Warning Failed to synchronize Offsite-Archive Details: S3 error: The specified key does not exist. Code: NoSuchKey

Ahh the good ol "NoSuchKey" message