Change from Private VPC end backup to using Internet for SOBR

[StevenMeier]

Hi Folks,

We recently set up our On Premise Veeam using SOBR's to use a Private VPC endpoint to Backup to AWS.

After a month Of using the cost of this is very prohibitive and a looking at Just going back to talking to the S3 Buckets over the Internet.

This Process was done by an external entity for us as our team was too busy to do this project and the project has completed over a month ago.
Could Someone advise where to start and what to look at and we can go from there. I am sure its simple but just want to make sure we cover our bases.

Cheers in advance.

[david.domask]

Hi Steven,

It should be as simple as simply re-adding the S3 bucket via a normal endpoint. Very likely the external entity followed this process: https://www.veeam.com/kb4226

So you just need to reverse these steps first, then re-add the bucket as an Object Storage Repository in Veeam, then import the backups.

1. Take a configuration backup "just in case" as a fall-back point
2. Reverse the procedure in https://www.veeam.com/kb4226
3. Remove the existing Object Storage repository from Veeam. The backups will temporarily be removed from the UI (they will not be removed from the S3 bucket)
4. Re-add the bucket as shown in the User Guide
5. On this step, check the boxes to scan for existing backups

The initial rescan may take a bit of time to run as it finds all the backups, but after that you should be good to go. You will just need to map the backup files (step 3 on that user guide page) and you will be good to go.

Since you use a SOBR, very likely you don't even need to re-map the backup files, as once you add the new repository to the SOBR it will auto-matically map for the jobs.

[StevenMeier]

Thanks for this much appreciated