Skip to main content

Some great answers on my previous posts so trying my luck with this one!

 

If the entire Commvault environment were to be destroyed,  CommServe, Media Agents, VSA’s deleted for example but DR backups of the CommServe Databases held on a functioning file server. 

  1. Can Commserve be reconstructed, and the Databases reimported (thinking definite yes for this!) Same machine name and IP?
  2. The tricky one now! Can a Linux Media Agent be manually rebuilt (yes) BUT can it access and use backups that were written to a NFS share by the previous Media Agent? Obviously, all Index Cache and DDB database that was on this machine will have been obliterated OR may actually be also backed up on the same NFS share by the scheduled DDB, index server backups that will have run. 
  3. Lastly the actual CommServe, Media Agents and VSA components will also have been backed up by Commvault in VM based backups and also held on NFS storage. Can these be resurrected from the dead?

Is there a flow chart or process on how to attack this?  Just as importantly is there a way to architect the deployment to make recovery from this situation easier? 

 

  1. Yes, the commserve database is absolutely vital. We offer a free service to upload your database to our servers for safe keeping - use it, as many customers hit by ransomware lose access to their DR location
  2. Of course it can. The index and DDB are protected in the library. Once the MEdia Agent has access to the storage, it will automatically restore the DDB and the index and be able to reconstruct both. The DDB is not required for restore, only backup - so that can be reconstructed while restores are underway
  3. You never need to restore a media agent, VSA, or whatever. Just reinstall it with the same name and its configuration will come from the CommServe database.

There is full steps for recovery on the docs site: https://documentation.commvault.com/2023e/expert/43507_commcell_recovery.html

Reply


Terms & ConditionsCookie settings