I have three 3 S3 Compatible repositories that were the capacity tier for 3 SOBRS that I created. I sealed and put the repos in maintenance mode about 3 months ago. Retention for the jobs in the repos is 90 days.
Next week I want to start removing the data from those repos and ultimately remove the repo altogether because we will be discontinuing our relationship with the vendor.
Couple of things.
1. Since I don't need the data anymore, I don't need to evacuate the repos, correct?
2. I can simply remove the repos from the SOBRs now that they are sealed and in maintenance mode, correct?
3. After the repos are removed from the SOBRs, I can take them out of sealed mode and maintenance mode, correct?
4. Once the repos are removed from Veeam, Veeam will place any backups /restore points on those repos in Capacity Tier (Orphaned) under each of the job names, correct?
5. After that I can go into Backups / Cap Tier (orphaned) / expand the job name / remove restore points that were placed on the removed repos, correct?
Lewis
-
- Enthusiast
- Posts: 52
- Liked: 5 times
- Joined: Apr 09, 2023 7:50 pm
- Contact:
-
- Veeam Software
- Posts: 11
- Liked: 3 times
- Joined: Jul 13, 2020 3:47 pm
- Full Name: Kirill Chukhlantsev
- Contact:
Re: S3 REPO REMOVAL
Hello!
1. Yes, correct. Since the data in the Object Storage repositories is no longer needed, evacuation is not required.
2. Yes, correct. Please note that any backups still present on these repositories will be removed from the configuration database.
3. Right. If no jobs are directly targeting these repositories, both Maintenance and Sealed modes can be disabled.
Note: Object Storage repositories are still subject to background retention. This typically isn't a concern if the data is no longer needed.
4. Not exactly. After the Object Storage repository (which was part of the Capacity Tier) is removed from the SOBR, backups on that repository are also removed from the configuration database.
5. No. Backups should be removed before removing the repository from the SOBR Capacity Tier (as after detach from SOBR backups are removed from the configuration database and are no longer present in the UI).
Important: To delete backups, Maintenance Mode must be disabled. Deletion is blocked for repositories in Maintenance Mode.
1. Yes, correct. Since the data in the Object Storage repositories is no longer needed, evacuation is not required.
2. Yes, correct. Please note that any backups still present on these repositories will be removed from the configuration database.
3. Right. If no jobs are directly targeting these repositories, both Maintenance and Sealed modes can be disabled.
Note: Object Storage repositories are still subject to background retention. This typically isn't a concern if the data is no longer needed.
4. Not exactly. After the Object Storage repository (which was part of the Capacity Tier) is removed from the SOBR, backups on that repository are also removed from the configuration database.
5. No. Backups should be removed before removing the repository from the SOBR Capacity Tier (as after detach from SOBR backups are removed from the configuration database and are no longer present in the UI).
Important: To delete backups, Maintenance Mode must be disabled. Deletion is blocked for repositories in Maintenance Mode.
Who is online
Users browsing this forum: AM1 and 10 guests