I'm in a situatio where we have one F760 with 4 shelves of 9Gb SCSI disk, and three shelves of 36Gb FC attached disks. The FC disks were added later, so the original install of vol0 was done to the SCSI disks.
We'd like to get rid of the SCSI disks (and use one shelf of FC to hold it), but I'm concerned since we have /vol/vol0 on it. Has anyone moved /vol/vol0 off SCSI to FC before, and if so, what problems did you run into?
Many customers have used vol copy to move the data over. Just make sure that the destination fiber-based volume is at least as large as the original SCSI volume. You vol copy the data over. Set the new volume to be the root volume. Then you can destroy the SCSI volume. I'd probably type download, just to be safe. Then I'd reboot...the filer won't actually destroy the old vol0 and start using the new volume until you actually reboot. Then if you want to keep the vol0 name, you can rename the new root volume.
This has worked for many customers that I've talked to. Has anyone seen differently?
-- Adam Fox NetApp Professional Services, NC adamfox@netapp.com
Just make sure you clean up stale NFS filehandles after the move. The old method would be killing any processes that have open files on the Filer or rebooting all the clients.
As I mentioned several messages earlier, I asked NAC to implement a filehandle renumbering command which might have made it into some release already. This would remove the need to do stale NFS filehandle cleanup.
Tom
On Fri, 14 Apr 2000, Fox, Adam wrote:
I'm in a situatio where we have one F760 with 4 shelves of 9Gb SCSI disk, and three shelves of 36Gb FC attached disks. The FC disks were added later, so the original install of vol0 was done to the SCSI disks.
We'd like to get rid of the SCSI disks (and use one shelf of FC to hold it), but I'm concerned since we have /vol/vol0 on it. Has anyone moved /vol/vol0 off SCSI to FC before, and if so, what problems did you run into?
Many customers have used vol copy to move the data over. Just make sure that the destination fiber-based volume is at least as large as the original SCSI volume. You vol copy the data over. Set the new volume to be the root volume. Then you can destroy the SCSI volume. I'd probably type download, just to be safe. Then I'd reboot...the filer won't actually destroy the old vol0 and start using the new volume until you actually reboot. Then if you want to keep the vol0 name, you can rename the new root volume.
This has worked for many customers that I've talked to. Has anyone seen differently?
-- Adam Fox NetApp Professional Services, NC adamfox@netapp.com
-
Bruce Sterling Woodcock -
Fox, Adam -
tkaczma＠gryf.net