Hey /r/veeam,

Hope all is well. We currently have an On-Prem Veeam B&R. And originally set up a capacity archive tier. And sending logs into the S3 Archive Bucket.

However, once the dust settled and we spoke to our Veeam engineer, it was discovered that Veeam Archive/SOBR setup deploys a VPC Security Group to AWS. We decided to delete that VPC Security Group based on the information we were given:

That it wasn't a requirement for the On-Prem Veeam B&R to have this AWS environment to backup data to an archive-tier s3 bucket.

Fast forward to today and the Archive Tier is no longer working. Looking at the Veeam logs it looks as though the On-Prem Veeam B&R instance is looking for the Security Group deployed to AWS. Weird...

And crap. The instance was backing up to the Archive Tier. Okay...

What I'd like to do is re-deploy the Archive Tier in the On-Prem Veeam B&R environment. And point it to the existing Archive Tier S3 bucket. What don't know is this:

• How will Veeam react after adding an S3 bucket with already existing Archive Tier data stored in it?
• Will Veeam accept and re-index the archive tier data? Will it want to blow away the data in that S3 bucket? Or will it just not care and not allow us to do anything with that data?

Need a lot more information to understand how Veeam will react to readding this bucket. I'm also struggling to find hard/definitive documentation on what this VPC is supposed to do?

I've read that it deploys a temporary EC2 instance whenever it has to move data from the Capacity and Archive tier. But the issue cropped up after we were told that EC2 instance only applied to Veeam B&R instances deployed to AWS.

Appreciate any help or information that can be provided. Thank you.

• acebossrhino