Removing the Performance Tier?

[mike.anderson]

Hi All,

I have a bit of dilemma on how to present data to a customer. We're a Veeam service provider, and we have a SOBR for a client that is made up of 2 block storage extents in the performance tier and up until recently it had no capacity tier. We pass this SOBR through to them via Cloud Connect.

Recently they have asked us to "archive" the data to object storage - the chains are all dormant now.

We added a capacity tier and mirrored the backups to it. But now I'm unsure the best way to continue to present these to the client, and get rid of the block storage.

The capacity tier is setup with a short immutability period if that makes a difference.

Do we:

1. Leave the existing SOBR intact and remove the performance tier block storage extents?
2. Remove the S3 Capacity Tier and add it to a new SOBR with s3 performance extents?
3. Some other option entirely?

I'm also happy to cross post to the Service Provider forum as well if that's a more appropriate spot, but this seems to be more about S3 and SOBRs in my mind.

[sfirmes]

Mike, one method that is used often to move backup job(s) to different repository types is our Backup Move feature. The use case that I see the most is when customers/service providers are moving backups from block/file based repositories to object storage based repositories. The 2nd most popular use case that I see is when a customer is moving from storage vendor A to storage vendor B.

Hope this helps.

[mike.anderson]

I don't think the Backup Move feature is available to us since it's all through a Veeam Cloud Connect console and the backups and encrypted - we don't see them under "Disk" etc. I should have been more clear about that!

If you think I'm wrong I'm happy to look into it though!

Thanks!