how to? manually move VBKs to existing S3 repo

[DDIT]

Hi,

We had an issue with storage on an offsite repo managed by us, so we manually copied a dozen large VBK files (~3TB each) off this storage to the root of a Wasabi bucket using rclone.

The backups are therefore sitting in this folder...

Code: Select all

amazonS3://s3/eu-central-1.wasabisys.com/mybucketname

This Wasabi bucket is already established as a capacity tier repo in a SOBR. Veeam references this path...

Code: Select all

amazonS3://s3/eu-central-1.wasabisys.com/mybucketname/veeam/Archive/GFSRestorePoints

In order to get these backup files to appear in VBR (Object Storage - Orphaned), we moved one of the smaller backups from the root into the Veeam referenced folder, then ran a rescan, but got an error "Failed to synchronize 1 backups".

Should this work? If so, I'll open a support case, but just want to make sure I'm doing something that should work/best way/is supported?

Thanks in advance.

[Mildur]

Hi Michael

No, this will not work.
Veeam do not store „vbk + vib“ in the bucket. It cannot do anything with such files in a bucket. It‘s an unexpected format for the capacity tier.

Veeam stores unique blocks of vbk or vib in the bucket. You need to download this files back to the performance tier and let it offload again to store it in the veeam native format for the capacity tier.

[Mildur]

I‘m sorry, there was a mistake in my answer.
You can‘t download the backup files to the performance tier and offload it again.
Imported backups will not be offloaded to the capacity tier.

[DDIT]

OK, understood. Thanks for taking the time to answer.