I'm trying to set up an offsite copy of my backups. What I have in place now is a CommVault Commcell and MA in my main datacenter. All my regular daily backups are in one storage policy.
I recently installed an MA in one of my satellite offices, created another copy of the main storage policy and set the new copy up to be synchronous after a specific date.
I've been running the aux copy for more than a week now and it is making progress sending the backups over the slow datapipe. Now that I have backup jobs copied to another MA, I'm trying to devise a proper test of whether this can be used for my offsite backups (i.e. DR strategy).
I can browse that storage policy copy's jobs and then kick off a restore with default settings. The restore of a small file completed super quick. The restore of a larger file (40GB) seems to have gone much slower (17 minutes 23 seconds). I'm not sure if was is trying to
a) rebuild the index from the offsite copy, or
b) acquire it from the source copy (located on the media agent that peformed the original backup).
In order for this to be useful as an offsite copy, the remote office media agent needs everything present locally so in the event of a disaster at my main datacenter I can just set up a DR commserve job and then restore the db into it. Short of going through all that DR setup now, how can I tell if things are architected right?
Also, if any of the above is unclear or if any of you CommVault folks or customers who've done something similar have any ideas about how I should be doing things differently, I'd really like the insight.