Skip to main content
commvault.com commvault.com
Solved

DDB retirement

J
Bit
Forum|alt.badge.img+2
  • jxb
  • Bit
  • 5 replies

Hi,

I’d like to Retire a Media Agent hosting a global dedup database on which my primary copies are pointing ,to keep only my secondary copies hosted on another MA for archival purposes.

Looking at the documentation I found that I can seal a ddb using an xml script but its mentioning the parameters -storagePolicyName 'xxxxx' and -copyName 'xxxxx'. What in my case where I have a global dedup db with multiple copies linked to it?

https://documentation.commvault.com/v11/expert/retiring_deduplication_database.html

Thx in advance for your answers.

 

Best answer by Emils

Hi ​@jxb 

First I would like to confirm whether the secondary copies are not associated to the global Dedupe as this may change the next steps also are you planning to delete the Primary Copies or keep them?

If they’re not associated and you’re planning to delete the associated copies, then you don’t necessarily need to run the script. 
The steps would be:

1. Delete all data associated to the Global Dedupe are aged and pruned. Deleting a global DDB policy.
2. Run Data aging

If you’re planning to keep the Copies, then you’ll need to move the DDB off the Mediaagent and seal the DDB.

 

View original
Did this answer your question?

2 replies

Emils
Vaulter
Forum|alt.badge.img+13
  • EmilsVaulter
  • Vaulter
  • 151 replies
  • Answer
  • March 31, 2025

Hi ​@jxb 

First I would like to confirm whether the secondary copies are not associated to the global Dedupe as this may change the next steps also are you planning to delete the Primary Copies or keep them?

If they’re not associated and you’re planning to delete the associated copies, then you don’t necessarily need to run the script. 
The steps would be:

1. Delete all data associated to the Global Dedupe are aged and pruned. Deleting a global DDB policy.
2. Run Data aging

If you’re planning to keep the Copies, then you’ll need to move the DDB off the Mediaagent and seal the DDB.

 

J
Bit
Forum|alt.badge.img+2
  • jxb
  • Author
  • Bit
  • 5 replies
  • March 31, 2025
Emils wrote:

Hi ​@jxb 

First I would like to confirm whether the secondary copies are not associated to the global Dedupe as this may change the next steps also are you planning to delete the Primary Copies or keep them?

If they’re not associated and you’re planning to delete the associated copies, then you don’t necessarily need to run the script. 
The steps would be:

1. Delete all data associated to the Global Dedupe are aged and pruned. Deleting a global DDB policy.
2. Run Data aging

If you’re planning to keep the Copies, then you’ll need to move the DDB off the Mediaagent and seal the DDB.

 

Hi Emils,

 

Thx for answering. I use the same method I’m used to when doing a hardware refresh. sync the copies then promote the secondary primary then delete the copy , Storage pool, MA and disk lib.

Reply


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