Hi,
I'm not sure how long volcopy will take. You will have to budget 8-10 hours minimum.
Thought I'd share some numbers on this with you:
F630 local volume copy (no load) ~36 GB/hr F630 -> F760 via GbE (no load) ~48 GB/hr F760 -> F760 via 100bT (load on source) ~28 GB/hr
++++++++
The second option to consider if you have NDMP backup in place Take a snapshot of Filer A Using NDMP backup Filer A. (This will take about 7 hours) Restore the back to Filer B. (This will take about 10-12 hours) Remove Filer A from the network.( rename it Filer C) Get a snapshot of Filer C. Backup any changes from Filer C since last backup.(this is an incremental backup) (This will take less than 1 hour) Restore the incremental backup to Filer B. (this will take about 1-1.5 hours) Filer B should look like Filer A data. This will keep all your associated ACL.
Alternatively, you can use NDMPcopy available on ftp://ftp.ndmp.org and skip writing/reading to/from tape. As outlined in the "Migrating Data Between NetApp Filers" white paper at:
http://www.netapp.com/technology/level3/3018.html
Cheers, Grant
On Thu, 14 Jan 1999, Melvin, Grant wrote:
This is the approach we've used successfully many times. It's nice to do a level 0, then do a 1, cut to the new filer, then do a level 2. If you plan to do the whole thing at during hours of light load, the risk involved here is negligible.
Matt Stein wrote:
We've used NDMPcopy to do just that, and it works pretty well. In one of our more recent adventures with NDMPcopy, however, the level0 of a ~100GB directory worked, but the level 1 bombed out with a "volume too high" error. That was really irritating, espescially when NDMPcopy usually works. We resorted to a date-restricted GNU tar to capture the very rough equivalent of a level 1 dump.
--Bryan
-
Bryan Hess -
Matt Stein -
Melvin, Grant