More and more shops update their Xsan environments to Leopard server and client and Xsan 2.
While this is quite easy, I’ve got some customers who want to replace their existing Apple Xserve RAIDs with 4Gb, redundant-controllers PROMISE RAIDs at the same time.
I choose the following way to do the whole thing:
- Upgrade your existing Xsan environment to the latest Mac OS X 10.4.x/ Mac OS X Server 10.4.x version and upgrade to Xsan 1.4.2.
- Do a quick cvfsck on your volume, if necessary invoke cvfsck -w.
- Now rename /Library/Filesystems/Xsan/config/XsanVolumeName.cfg to /Library/Filesystems/Xsan/config/XsanVolumeNameOld.cfg.
- In /Library/Filesystems/Xsan/config/fsmlist change XsanVolumeName to XsanVolumeNameOld.
- Fix the ICB mismatch by invoking cvfsk -w in interactive mode. This and the above two steps are explained at Xsanity.
- Now copy the MDC’s directory /Library/Filesystems/Xsan/config/ to an external device.
- Install Leopard on the MDC, upgrade it to the latest version, and install Xsan 1.4.2 on it, too. Enter a valid Xsan serial number in Xsan Admin (Xsan 2 license works with Xsan 1.4.2, too).
- Mount the existing volume to see if it still works. Now unmount it, stop the volume, and install Xsan 2.
- If you open Xsan Admin the Xsan Assistant starts up and asks you for some self-explaining data. After that your volume can be mounted again. Try if it still works and then deactivate and stop the volume again.
- Again, cfsck the volume.
- Now you can set up your new device, mount it using your old device’s original volume name and copy the data over to the new storage.
- After you copied the data to the new device, delete the old Xsan volume and remove it physically.
- Now install Leopard on all FC connected machines as well as Xsan 2 and integrate them with you new Xsan volume.
Hope this helps.
USE AT YOUR OWN RISK !!