Quick question regarding worst case scenario restore testing from a Wasabi Object Storage repository

[massimiliano.rizzi]

Hello Community and good day,

please consider the following scenario, where everything is working correctly:

==================================================
1. An existing Backup copy job targeting an immutable Wasabi Object Storage repository (NOT part of a SOBR Capacity Tier)
2. Our customer would like to perform a full test restore of the most recent restore point of all 20+ business-critical VMs from the Wasabi Object Storage repository above. As you might imagine, they want to test the worst case scenario where everything on-prem has been hit by either a ransomware or a catastrophic event
==================================================

We will be using a separate helper Veeam Backup server and a separate helper VMware vSphere infrastructure at our premises for the reasons below:

==================================================
1. We have plenty of bandwidth at our office (up to 2.5 Gbit/s download), whereas our customer is limited to 100 Mbit/s download
2. We don't want to impact the operations of the production environment
==================================================

Both the Veeam Backup Server used in production and the helper Veeam Backup server used for restore testing purposes will run the the same and most recent build of Veeam Backup & Replication.

Of course, we will temporarily disable all Backup copy operations on the Veeam Backup Server used in production and only leave Backup Jobs enabled.

What is the most appropriate procedure for temporarily adding the Wasabi Object Storage repository from which we will restore from to the helper Veeam Backup server in order not to break anything on the Veeam Backup Server used in production when resuming the Backup copy operations ?

Any help will be greatly appreciated.

Thanks!

Massimiliano

[veremin]

The main recommendation is to disable all jobs on the production backup server that write to this repository. Additionally, do not create any other jobs on the helper backup server that could write data to this repository and potentially cause issues on the production backup server, which would not be aware of the changes made.

Thanks!

[massimiliano.rizzi]

The main recommendation is to disable all jobs on the production backup server that write to this repository. Additionally, do not create any other jobs on the helper backup server that could write data to this repository and potentially cause issues on the production backup server, which would not be aware of the changes made.

Hi Vladimir,

thank you very much for your quick reply and for the information below.

Apart from the main recommendations to disable all jobs on the production backup server and to prevent the helper backup server from writing data to this same repository, I believe that the last recommendation is to have the production VBR server take ownership back, so we will need to go through the properties on the production server again to take control back when resuming Backup copy job operations?

Thanks again!

Massimiliano

[veremin]

Yes, you are right—in the current implementation, only one backup server can have access to the object storage backup repository.

Therefore, when you add the repository to the helper backup server, you’ll see a message about ownership and will need to agree to transfer it to the helper backup server.

After you’ve completed all checks with backups on the helper backup server, you’ll need to repeat the ownership transfer operation on the original backup server.

Thanks!

[massimiliano.rizzi]

Yes, you are right—in the current implementation, only one backup server can have access to the object storage backup repository.

Therefore, when you add the repository to the helper backup server, you’ll see a message about ownership and will need to agree to transfer it to the helper backup server.

After you’ve completed all checks with backups on the helper backup server, you’ll need to repeat the ownership transfer operation on the original backup server.

Okay, got it. Thank you very much for your time!

Massimiliano