Accessing Another Veeam Server's Object Storage

[jeff.kuhn]

Case #07640656 has been submitted

Our Object Storage is in Backblaze, S3 Compatible.

We have a Veeam O365 backup server in our old tenant, Azure.com. It is running version 7.1. It has not been in full use for months. Backups are still readable from that server. We want to decommission it, but boss wants to make sure we can read those backups from our new backup server.

We now have a Veeam O365 backup server in our new tenant, Azure.us that is running version 8.1. I attempted to reach the repositories, which I can do, but I cannot add them to my new backup server and I'm deathly afraid to change any settings (like losing my job while buying a new home afraid) in Backblaze (and don't think I can do so, anyway).

When attempting to set up the repository on the new server, I get the error "The selected bucket supports blob versioning. Select a bucket with disabled blob versioning." What settings do I need to change in Veeam 8.1 to allow me to read these buckets?

I have access to the old server, and I can upgrade it to the identical version if need be, but will my repositories still be readable afterwards?

[Polina]

Hi Jeff,

1) Is your Backblaze repository immutable and does it contain any backup copies?
2) Non-immutable repositories with enabled blob versioning are an unsupported configuration. You cannot continue backing up to such repositories on v8x or re-attach such repositories to another v8x server.
2a) As a workaround to keep your existing historical data, you can keep the Backblaze repositories on your old server, and upgrade that server from 7.1 to 8.1. Our support will help you to upgrade these repositories (some additional manipulations will be needed). Note, that no new backups should be saved to such repositories - you can only read from them if needed.

Does it make sense?