Or even 'vol vopy' as well..its free, and will work at max possible performance between your two.
Mind you..that any changes in the data as you copy..may not migrate across as well unless you do schedule a downtime.
If you were my customer and I had to do this..I would use vol copy.
-----Original Message----- From: Harechmak, John Sent: Wednesday, May 24, 2000 3:31 PM To: kgc@sonic.net; toasters@mathworks.com Subject: RE: Migrating from NetApp to new NetApp
Hi,
There is a whitepaper that might be interest on the netapp website: "Migrating Data Between NetApp Filers" http://www.netapp.com/tech_library/3018.html. Have you considered NDMPcopy?
-- johnrh
-----Original Message----- From: Kelsey Cummings [mailto:kgc@sonic.net] Sent: Wednesday, May 24, 2000 2:50 PM To: toasters@mathworks.com Subject: Migrating from NetApp to new NetApp
I've got a f230 with 4 shelves of 4GB disks and its replacement, an f740. I talked to netapp support and they recommended that the best method to move the data from the f230 to the f740 would be to tapes with dump and restore. I can't believe that there isn't a more efficient way to do this. We are an ISP and all mail/ftp/http is served off of the netapp, any downtime will be painfull so we'd like to minimize it as best we can.
What choices to migrate the data do we have? We've considered tar/cpio over nfs but that's going to take some time even if we migrate one service at a time. dump/restore seems clumsy. and plain ole 'cp' would take forever. Apparently there are issues with volcopy going from SCSI to FCAL, is that true?
Thanks guys. This ought to help us out.
Say hello to Brian for me Jeff.
jeff.mohler@netapp.com wrote:
Or even 'vol vopy' as well..its free, and will work at max possible performance between your two.
Mind you..that any changes in the data as you copy..may not migrate across as well unless you do schedule a downtime.
If you were my customer and I had to do this..I would use vol copy.
-----Original Message----- From: Harechmak, John Sent: Wednesday, May 24, 2000 3:31 PM To: kgc@sonic.net; toasters@mathworks.com Subject: RE: Migrating from NetApp to new NetApp
Hi,
There is a whitepaper that might be interest on the netapp website:"Migrating Data Between NetApp Filers" http://www.netapp.com/tech_library/3018.html. Have you considered NDMPcopy?
-- johnrh
-----Original Message----- From: Kelsey Cummings [mailto:kgc@sonic.net] Sent: Wednesday, May 24, 2000 2:50 PM To: toasters@mathworks.com Subject: Migrating from NetApp to new NetApp
I've got a f230 with 4 shelves of 4GB disks and its replacement, an f740. I talked to netapp support and they recommended that the best method to move the data from the f230 to the f740 would be to tapes with dump and restore. I can't believe that there isn't a more efficient way to do this. We are an ISP and all mail/ftp/http is served off of the netapp, any downtime will be painfull so we'd like to minimize it as best we can.
What choices to migrate the data do we have? We've considered tar/cpio over nfs but that's going to take some time even if we migrate one service at a time. dump/restore seems clumsy. and plain ole 'cp' would take forever. Apparently there are issues with volcopy going from SCSI to FCAL, is that true?
-- Kelsey Cummings - kgc@sonic.net sonic.net System Administrator 300 B Street, Ste 101 707.522.1000 (Voice) Santa Rosa, CA 95404 707.547.2199 (Fax) http://www.sonic.net/ Fingerprint = 7F 59 43 1B 44 8A 0D 57 91 08 73 73 7A 48 90 C5
+-- jeff.mohler@netapp.com once said: | If you were my customer and I had to do this..I would use vol copy.
We have done this before, and we used the following method. Note that we are in a mostly read environment - if you're doing more writing than we are, then this might be more painful for us.
0. Set up the volume on the new filer however you like (it has to be as big or bigger than the current vol to use vol copy, even if the vol is mostly empty). Change your fstabs on the machines using the volume to point to the new location. Export the new volume in the same manner as the current volume.
1. Re-export the current volume read-only (writes will fail - we did this during a maint. window and the impact was minimal for us).
2. Use 'vol copy' to copy the volume to the new machine. This is fairly quick when compared to some of the other methods (i.e. tar, dump/restore).
3. Once the vol copy is done, reboot (or simply remount - for us rebooting was easier) the boxes so they pick up the new mount point.
4. Confirm the old filer is no longer serving data, and you're done.
I'd also suggest checking out ndmpcopy.
Oz
-
jeff.mohler＠netapp.com -
Kelsey Cummings -
Ozzie Sabina