In the past I have moved large amounts of data over night. 100Gig -200Gig.
This is how I was configured. -3 sun server were used to copy the data via NFS version 2 with the command "cpio" from one mount point to the other. Each mount point would be from a different sub-directory. -one server with an ATM FORE OC-3 interface, with 4 concurrent cpio streams allowing 20Gig/hr -and two server using built-in 100BT-FD, each server with 2 concurrent cpio streams allowing 12Gig/hr from each system -My new server would have 3 to 6 interfaces to allow for load balancing of traffic during the copy. Change your export to be READ ONLY and disable your SHARE to PC clients or rename the system and have the new system renamed with Filer A and configuration. Keep in mind this will not keep any ACL associated with any file. For 150Gig it would take about 4 hours if all goes well.
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.
I'm not sure how long volcopy will take. You will have to budget 8-10 hours minimum.
Michel Kapuscinski mikeka@nortel.com
-----Original Message----- From: Anthony Fiarito [SMTP:alf@cp.net] Sent: Thursday, January 14, 1999 4:25 PM To: toasters@mathworks.com Cc: alf@cp.net Subject: moving data between filers
Here is the scenario:
I have two identically configured F630 filers. Filer A is active and contains about 150 gigs of data (all in one volume). Filer B is brand new and empty. I need to replicate the data from Filer A to Filer B with the minimal amount of downtime for Filer A. I could do a vol copy to move the data, but in the time that it would take to complete, much of the data would have changed and would be out of date. I was thinking of some sort of solution where I could do a vol copy (or something similar) of the data from Filer A to Filer B while Filer A was up and running. Once that was done, I should shut down Filer A and resync the changes that were made to Filer A during the copy to Filer B (thus giving me an exact copy of the data on each netapp). It would be similar to doing a level 0 dump while everything was active, and then a level 1 while they were shut down. The problem though is that I need them to be synched exactly (i.e. files/dirs that get deleted from Filer A during the initial copy would also get deleted from Filer B during the sync phase). Another option might be to do an rdist from Filer A to Filer B of the data while they are active, isolate them from the network once that is done, and re-run rdist to sync of any changes that took place during the initial move. With 150 gigs of data though, this would probably take a ReallyLongTime[tm], thus not being a viable solution.
Has anyone tackled a situation like this before? What methods did you use and in what sort of time frame were you able perform the replication?
Thanks in advance for any feedback.
-alf
Anthony Fiarito alf@cp.net Critical Path Operations