Skip to main content
commvault.com commvault.com
Solved

How to retire a DDB?

M
Byte
Forum|alt.badge.img+14

Hi all

 

If I can just confirm something that I think makes sense.
In my case, I have a Media Agent that only backed itself up and hosted it’s own DDB.

This client no longer backs itself up. It’s retentions have all been met and no data resides on the Storage Policy or the DDB.

I want to remove the alert in the Command Centre that notifies me the DDB isn’t being backed up.

If I understand correctly, I just do the below in this order:

 

  1. Retire DDB using the ddb_sealing.xml
  2. Delete Storage Policy
  3. Delete Media Agent and associated Library?

 

Thanks.
Mauro

 

Best answer by Mauro

Hi all

 

Thanks for the responses.
The MA definitely only ran it’s own backups. It was a standalone that backed up its local SQL DB and File System. Retention was 30 days, so removing everything (including the DDB) is my best option as I want the Commcell to be cleared of it.

Regards,
Mauro

View original
Did this answer your question?
If you have a question or comment, please create a topic

3 replies

O
Vaulter
Forum|alt.badge.img+15
  • OrazanVaulter
  • Vaulter
  • 630 replies
  • March 14, 2022

Good morning.  You should not have to do anything such as retiring the DDB unless you removed the storage policies from the CommServe after sealing.  Once all jobs in all of the storage policy copies are aged or deleted and data aging is run, the sealed DDB should disappear.  Have you deleted storage policy copies since sealing the DDB?

J
Vaulter
Forum|alt.badge.img+9
  • jgeorgesVaulter
  • Vaulter
  • 69 replies
  • March 15, 2022

Hey @Mauro 

You can seal the DDB and this should address the alerts, as we don’t protect a sealed DDB.

However if you want to retire the Storage Policy and Media Agent / Library, than you’re steps are spot on. A couple of important notes:

  • ​​​​Ensure all data in the Storage Policy is Aged and Pruned.
  • Ensure the Media Agent is not responsible for any other roles (Indexing Server, Content Indexing Node, Proxy MA etc)
  • Ensure the library is not used for any other backups/deduplication databases before attempting to delete.

One note, you don’t require the XML to seal the DDB. You can do this from the GUI by righ clicking the DDB Policy > All Tasks > Seal Deduplication Database.

 

Cheers,
Jase

T
1 person likes this
M
Byte
Forum|alt.badge.img+14
  • Mauro
  • Author
  • Byte
  • 101 replies
  • Answer
  • March 17, 2022

Hi all

 

Thanks for the responses.
The MA definitely only ran it’s own backups. It was a standalone that backed up its local SQL DB and File System. Retention was 30 days, so removing everything (including the DDB) is my best option as I want the Commcell to be cleared of it.

Regards,
Mauro

Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings