we need to move TBs of millions of tiny files from one storage array (CX4) to another (VNX). The files are bound in a W2k3 host on 8 different disks. We use SANCopy for the initial sync and then robocopy to pull the changes from daily usage.
The problem we have is that we anticipate the last sync will took much longer than we have for leaving the application in an offline state.
Who can suggest more efficient methods of doing the migration/sync?
Thanks in advance!
You may want to look into Powerpath Migration Enabler with Hostcopy. With a Windows 2003 server there is no downtime required for the application and you can throttle the migration speed.
Mirrorview is supported as a metod of replication between to Celerra/VNX. I believe it is one of most convenient solution, but customer need to pay MV lic fee as cost,
I think upon your context, your customer has already purchased SANCopy lic, that migth lead them use robocoy as lic cost free solution.
we need to change the offset of the filesytem. that's why we decided to use a host based copy mechanism.
it's a w2k3 machine.
any further suggestions regarding robocopy alternatives w/o rebooting the server?
I did a google search and found this Blog
"Robocopy is slooow. Tips or alternative software? "
"Five Best Alternative File Copiers"
"RoboCopy Alternatives for Windows:
IIRC, Robocopy from the Windows 2003 admin pack (or whatever it was) was single-threaded, and the Windows 2008 version defaults to 8 threads (customizable from 1-128). Copying robocopy from a 2008 to 2003 box doesn’t appear to work<http://www.petri.co.il/forums/showthread.php?t=41569>, but you could explore having a Windows 2008 target, source, or even a separate copy host (UNC to UNC robocopy session).
You could also try running a different robocopy session against some of the subdirectories (assuming you have multiple directories).
Turn off logging and restartable mode. If you’ve got inheritance set up correctly, you shouldn’t have to worry about the security option. Avoid the /COPYALL option.
Open Migrator was suggested yesterday. It will allow you to migrate to a disk with a different offset alignment, but it will also require some rebooting.
Because he notfied us of his latest requirement:
"we need to change the offset of the filesytem. that's why we decided to use a host based copy mechanism."
Mount the new target disk, change it's offset alignment, format and perform an OM migration.