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.

[dkr]

Hello, I have a similar issue. I want to achieve the same situation but in my case we don't use a SOBR for our backup job. That's why I think it is useful to use this topic instead of creating a new one.

I need to change my S3 immutable backup target repository's "Service point" to an internal endpoint as well. I just added the bucket as a repository again, with the new service point so that only the service point is different and it is pointing to the same bucket. I rescanned it and I'm ready to use it. However, I don't see the new repository in the backup job's repository pulldown list. Unlinking the backup job from the current repository also gives me a warning that it will create a next full when it's re-attached and I want to prevent that from happening as well.

How can I keep using the backup job which is configured for a forever incremental chain while switching the repositories?

Dennis

[david.domask]

Hi Dennis, welcome to the forums.

Please open a Support Case and let Veeam Support review the situation with you.

If the new endpoint was added successfully you should be able to choose the repository as a target and remap to the existing backups, so best to let Support review the situation as too much guessing over the forums.

Please share your case number once created, thanks!