Xsan 2: Upgrading Xsan 1.4.2 to Xsan 2
Summary
Follow these instructions to upgrade your Xsan 1.4.2 SAN to Xsan 2.
Products Affected
Xsan, Xsan 2, Xsan 2
- Back up your SAN volumes (see the Xsan Migration Guide for complete instructions)
- Unmount and stop existing volumes (see the Xsan Migration Guide for complete instructions)
- Verify volume integrity using cvfsck (see the Xsan Migration Guide for complete instructions)
- If you are running a version of Xsan earlier than Xsan 1.4.2, please follow the upgrade instructions to update your SAN and metadata controllers to 1.4.2.
- Once your SAN is using Xsan version 1.4.2, upgrade your metadata controllers (and any clients you wish) to Mac OS X 10.5 Leopard. If your Leopard media does not install version 10.5.2, use Software Update to update to version Mac OS X 10.5.2.
- Install Xsan 2.
- Run the SAN Setup Assistant (see the Xsan Migration Guide for complete instructions). The last step of the assistant is to add Xsan 2 serial numbers. Once this is complete, click Continue. This starts the upgrade of each volume.
Important: Do not use the Xsan Admin application during the upgrade process as the update process causes the volume to be unresponsive to Xsan Admin. This unresponsiveness does not indicate that the update is not proceeding. - To tell when the upgrade of all volumes is complete, watch the volume logs either by using ssh to log into the controller or by logging into the controller and running the Console application. The update messages will be logged in the cvlogs for the respective volume. The logs are named "/Library/Filesystems/Xsan/data/<vol-name>/cvlog".
- Once a volume has been "started" the update process, called the "RPL Update" in the logs, will automatically begin. The update will proceed on the controller hosting the volume. Look for the messages indicating the RPL update is complete. Note: the update measures progress (10%, 20%, 100%) in terms of the number of inodes on the file system at the beginning of the update. The update process can cause additional inodes to be allocated, and so the process can proceed past 100%. This is normal.
- Remount the volume via the Xsan Admin on the controller(s) and on any desired client (see the Xsan Migration Guide for complete instructions)
- If you choose to enable Spotlight on an upgraded volume, please follow the instructions here.
Note: If you choose to upgrade an Xsan 1.4.2 client on an Xsan 2 SAN to Xsan 2, first remove it from the SAN, perform the upgrade, and then add it back to the SAN.
Rate this article: