Hi all
We have SOBR repositories in our environment but we are migrating entirely to Az cloud and thus slowly removing the local backup servers (performance tier) as we migrate.
What is the best way to remove the SOBR performance tiers and effectively retire the SOBR repository but keep the capacity / archive tier for longer term retention and restore possibilities without data loss ?
Appreciate any input!!
Matthew
-
- Influencer
- Posts: 14
- Liked: 1 time
- Joined: Sep 13, 2018 8:38 am
- Full Name: Matthew Oldham
- Contact:
-
- Product Manager
- Posts: 20675
- Liked: 2380 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: SOBR Performance tier removal
To retain backups on the capacity tier, first detach it from the scale-out backup repository. Then, configure it as a standalone object storage repository and start the backup import process. You'll need to follow the same procedure for the Archive Tier.
In this case, retention policies will not be applied to these backups, so you will need to manually delete them as needed.
Thanks!
In this case, retention policies will not be applied to these backups, so you will need to manually delete them as needed.
Thanks!
-
- Influencer
- Posts: 14
- Liked: 1 time
- Joined: Sep 13, 2018 8:38 am
- Full Name: Matthew Oldham
- Contact:
Re: SOBR Performance tier removal
Hi
Thanks for the quick reply, apologies for delayed response.
So just to ensure I interpret correctly its to uncheck under the SOBR properties > Capacity Tier and then run add a new object storage repository wizard and import / scan on creation ?
Cheers again
Thanks for the quick reply, apologies for delayed response.
So just to ensure I interpret correctly its to uncheck under the SOBR properties > Capacity Tier and then run add a new object storage repository wizard and import / scan on creation ?
Cheers again
-
- Product Manager
- Posts: 20675
- Liked: 2380 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: SOBR Performance tier removal
Yes, you are correct. It is necessary to detach the Capacity Tier from the Scale-Out Backup Repository, then add it as a standalone object storage repository, and after adding it, initiate the backup import procedure, the link to which I provided earlier. Thanks!
Who is online
Users browsing this forum: G_Mellor and 11 guests