I tried to find a tool that retained compression on a
per-file basis to perform a catalog migration but I could not find one. I
considered custom writing my own in .net but never got around to it.
Why not simply compress the entire DR volume? You’ll take
a slight performance hit come DR time, but you probably don’t need the
entire catalog at that point anyway. I only copy the last 3 weeks of
backups to DR for hot restores. The rest of the images will be restored
cold from the most recent catalog backup. I use the following command run from
a scheduled task on my masters.
robocopy "D:\Program
Files\VERITAS\NetBackup\db\images" <target unc> /S /ZB /PURGE
/MAXAGE:21 /TBD /R:3 /W:3 /LOG:<path to log file> /XD tmp
Be sure to exclude tmp folders, these are where running backups
write their image files. If you try to robocopy an image that is being
generated you will kill the backup. Once the image is complete, it will be
moved to the appropriate subfolder.
Btw, I’ve tested this numerous times in DR scenarios and
it has never failed.
-Jonathan
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of pranav
batra
Sent: Wednesday, July 07, 2010 11:51 AM
To: Veritas
Subject: [Veritas-bu] Catalog Copy ???////?/
We
have a catalog of aroung 250 gb.
Its
on a F drive which is coming from SAN.
This
drive is composed of 3 luns.
Now
for DR purpose we want the data to copy from this drive to another drive that
will be composed of a single lun of 300 Gb.
Now
we used a robocopy method to copy this data:-But this has a bug that it
does not retain the compression of files.
What
other method you suggest to copy the data to other drive?????
Thanks and Regards
Pranav Batra
Chin
music and high voltage T20 action on MSN Sports Sign up
now.
