Skip to main content
commvault.com commvault.com

Hi all,

since I am still struglling to understand the procedure of Media Agent +DDB and Disk Library deletion I would like to open this thread and with your help summarize the proper procedure.

 

Brief description of the situation:

 

  • Disk Library and associated DDB
    - Contains no relevant data, maybe only some unimportant leftovers
    - Haven’t been used due to other available DDB stores and storage arrays.
    - Disk Library and DDB mount paths/partitions are in an offline state.
     
  • Current state:
    - Old Media Agent is stopped and no longer accessible.
     

How can we properly remove both the old DDB and Disk Library?

  1. Disk Library Deletion: Is it possible to delete mount paths that are in an offline state? If not, is there an alternative workaround? I assume that once the mount paths are deleted, deleting the Disk Library should be possible.

  2. DDB Deletion: Since the DDB partitions are also offline, can the "Retiring a Deduplication Database" script (https://documentation.commvault.com/2022e/expert/retiring_deduplication_database.html) be used in this case? Would this script work to remove the DDB?

  3. Global Deduplication Storage Pool: Is it necessary to delete the global deduplication storage pool as part of this process?

  4. Media Agent Deletion: Finally, I assume that right-clicking on the Media Agent and selecting the delete option should be sufficient.

Adding a valuable link that might have been supplemented with a more detailed explanation and step-by-step instructions - (https://documentation.commvault.com/11.20/impact_of_mediaagent_deletion.html)

 

I’d greatly appreciate any personal experiences or additional advice you can provide!

 

 

Hi @drPhil,

 

May i know how many storage policies are associated with the media agent?

 

And the clients associated with the storage policies are still active or is it being disabled?

 

 

1.If storage policy copy associated with the media agent it is not having any data and if the clients associated with the storage policy is longer used to take backup then you can delete the storage policy.
2.If the client is used to take backups then we need to re-associate the clients to different storage policy and then delete the storage policy.
3.Delete the storage pool if the storage pool is only associated with the storage policy which was deleted in the earlier steps. Deleting the storage pool will delete the deduplication database. But incase if the deduplication data based is being referred by other media agents and storage policies you can move the DDB to a new media agent
4.Mount path deletion: If the mount path is local to the media agent which is being decomissioned and if it doesn't contain any data you can delete the mount path and delete the disk library.
5 If the mount path is local to the media agent and does contain data you can perform the move mount path to different media agent and post that the mount path move is completed you can go ahead and delete the mount path.

But before deleting the library make sure the Library properties --> Associations tab shows no Storage Policy Copies.

And Mount path properties --> Deduplication DBs tab shows no DDB.

5.Once the library is delete you can remove the media agent license and delete the media agent from media agents option and do not delete the media agent entry from client computers as doing the hard delete of machine from client computers will erase the machines backed up data.

Please let me know incase of any queries.

You can also refer the below document.

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

 

Regards,

Karthik

 

 

Hi @kkarthikk and thank you so much for your valuable post, which provided exactly the information I was looking for.

Indeed, the old Media Agent had two or three storage policies assigned. I finally understand the procedure: first, you need to remove the storage policy by reassigning the client and deleting the policy. Then, you can delete the storage pool if there are no dependent copies (and move the DDB if some deduplication data are still referenced by another Media Agent). After that, you can delete the mount paths and the entire library, but before deletion, ensure there are no associations with storage policy copies or DDBs. Removing the Media Agent role and releasing the license is then straightforward.

Reply


Terms & ConditionsCookie settings