VBR / S3 Repository - How to change Service Point?

[Dagr]

TLDR; We have a SOBR Capacity Tier Extent that we need to change the Service point (s3 endpoint) on. How do we do this?
For reference: Case #07456403.

The reason:
The need to change the Endpoint is that is was “misconfigured” to use a public endpoint, instead of a direct endpoint (the Backup server is located in a public cloud). As such, the current setup is economically very costly, due to ingress/egress fees.
As Repo is used for Offlading data in a SOBR, and the VBR is a VCC Server the S3 repo have already received around 10-15TB data. To not get in to further issues (extracting said data and keeping it on the performance tier due to Veeams limitation to move the data to offload again) I would see the change of endpoint as the fastest/cleanest way instead of creating a new repo, and creating more fees & space needed on the Performance tier by downloading the current data from the S3 Repo.

The issue:
Looking at the GUI, the Endpoint field is grayed out, and Powershell cmdlets does not have a Set-VBRObjectStorageRepository, where this can be changed. I do however see the Servicepoint under "Get-VBRObjectStorageRepository".
it looks like it should be possible to somehow leverage the "Connect-VBRAmazonS3CompatibleService" cmdlet to somehow change the service point.

A possible solution?
Did some more digging and found the capacity tier's in the SQL DB by running:

Code: Select all

SELECT Id,name,path
  FROM [VeeamBackup].[dbo].[BackupRepositories]
  Where type = '14'

Would it be posible to just change the "path" ? or will this mess stuff up?

[david.domask]

Hi Daniel,

Manually changing this in the database is not a good idea, and likely will result in difficulties with the Capacity Tier extent after the edits.

https://helpcenter.veeam.com/docs/backu ... -providers

Since you're just changing the endpoint, this process should work without having to download the data first. Simply add the new Object Storage Repository, and on this step ensure the option to Search the repository for existing backups and import them automatically is not checked. (We don't want to import the backups just yet)

Edit the SOBR after this, remove the old Capacity Tier Extent and replace it with the newly added repository, then rescan the SOBR.