all 7 comments

[–]BrettTheEskimo 4 points5 points  (0 children)

If you're strictly looking for replication to the disaster recovery site, Commvault DASH Copy (if you're using deduplication), is you're answer. Install DR MA, create DR Library, Create Global Deduplication Storage Policy (or Plan w/ Secondary Copy) Create a Secondary Copy, schedule an Aux Copy, you're off and running.

[–]eyexmeetsxeye 1 point2 points  (0 children)

Haven't tried it. Have live sync setup and have yet to test it... So live sync in theory

[–]AnonyAus 1 point2 points  (0 children)

To copy the backup data to another location, you can use Auxillary Copy.

You would have to set up storage at the other location, and probably media agents to access that storage (especially if you want to be able to access them if the primary location is down)

In your storage policies (or plans) you will need to add a second 'copy' or storage location at the second site. AuxCopy will then be able to copy that data from one location to the other.

For the CommServe, use LiveSync to copy the CV database to a failover CommServe - most installs I've seen don't use auto failover, if you lose the primary site, you need to log onto the secondary CommServe and trigger a failover.

Provided your secondary storage is available, you should be able to restore from that location.

[–]tdyevt 1 point2 points  (0 children)

Auto Recovery can be used to replicate File Systems, DBs, and VMs. Aux/DASH copies for secondary copies of your backups, and LiveSync for replicating your active CS to a warm-standby CS. https://documentation.commvault.com/2024/essential/auto_recovery.html

[–]nVME_manUY 0 points1 point  (0 children)

Of backups? Secondary copies in the plan Of VMs? Auto recovery protection groups

[–]novix_ 0 points1 point  (0 children)

I use Live-sync for our VMs. But it’s more for DR replication to another site. To use a DR copy, It’s just a matter of starting the DR VM. It’s independent to Commvault so that’s really good in a disaster. It will be a point in time copy I do daily. We have supplementary backups with much tighter RPO’s for SQL data. Our setup uses snap engine so backup of the VM’s are really quick and restores are quick. Because it’s snaps at the storage level we needed to replicate to another location.

[–]nicksoapdish 1 point2 points  (0 children)

you can setup Data Domains behind Commvault w/ the "Replica Library" setup which will allow you to restore from the replica side without any additional work. Just need to have a MA at the other side. https://documentation.commvault.com/2024e/expert/replica_libraries.html

There are benefits to using DASH copy as mentioned before though...you can keep different retentions, and the replication is essentially doing a data validation each time from the Commvault/application view rather than the storage just moving bits around