Veeam on Prem and Veeam for AWS Dr scenario

[StevenMeier]

I have a question for the bright folks in the forum.
We have veeam on Prem - using SOBR that go to AWS capacity S3 tiers and cold storage tiers in AWS.
We also Have Veeam for AWS - this is integrated with out on prem so we can retore in both directions etc. Veeam for AWS backups up to AWS s3 storage.

So

In a DR scenario - IF we loose our Veeam on Prem.

1) can we make Veeam for AWS see the aws s3 tiers that our on prem veeam use for SOBR storage and restore jobs from them into Veeam for AWS and create EC2 instances as a recovery ???

If so what are the steps.
If not what do we do for a DR where we loose Veeam on prem.

[david.domask]

Hi Steven,

Not quite, the easiest way would be to ensure you have a copy of the Veeam Configuration Backup and spin up a new VBR server in the desired location that can reach your S3 buckets, then perform the Configuration Restore and begin restoring.

Configuration Backup is typically the fastest way to get back up and running, but even without the configuration backup, spin up a new Veeam Backup and Replication Server and then add the S3 repositories and import backups. Once imported, you will be able to being restores to EC2.

[StevenMeier]

Thanks for the reply
I posted this in an older forum , about what I have been doing asking more questions , I would appreciate your eyes over this

veeam-backup-replication-f2/dr-planning ... 42a5e53c52

[david.domask]

Hi Steven,

I will comment in that topic shortly, but immediately one thing that stands out related to this topic:

>Our on Premise VBR Server uses performance local Tier and capacity Tier and cold tier via SOBR in . I export and copy our Veeam SQL database backup to the AWS EC2 veeam Server .

This is strongly ill-advised as noted here, as any stored credentials or other secrets (server certificate) won't be properly backed up and you will need to do quite a bit of prep-work after restoring the configuration.

I would advise use the Configuration Restore for this as opposed to exporting the configuration database.

[StevenMeier]

The VBR Server is running as I restored it to aws from a backup , I do export the veema config and sql backups to another box in aws as I do not leave this instance powered on. I have had no issues doing file restores. But I need to be able to Test a full vm restore with access to the on premise veeam hardware blocked to make sure its works. Hence the question around how best to access the s3 backups of the on premise sobr so I dont cause and issue so I can test .DO I need to import into a new repository to the dr copy instance , does this affect the meta data in the backups of the sobr in the s3 buckets.
These backup devices are not domain joined so certs and stuff are not an issue.

[david.domask]

Hi Steven,

For testing the DR service, two ways:

1. Disable original Veeam server and do a configuration restore to the DR server. Do the necessary testing, then a fresh configuration backup and restore to the original VBR.
2. Add the buckets as read-only to the DR site temporarily and test restores. You can import the Object Storage backups and then proceed to testing the restore.

[StevenMeier]

Thanks David for the replies.. Hoping to start this next week under change control . will report back on progress and if have more questions.