Upgrading from Xsan 1.4.2 to Xsan 2.x
Follow these instructions to upgrade your Xsan 1.4.2 SAN to Xsan 2.
This article is a summary of, and companion to, the Xsan Migration Guides, Second Edition and Third Edition, which can be found at this website.
Important: Refer to the appropriate edition of the Migration Guide for detailed instructions about each step listed below.
Updating SAN clients
Use Xsan Admin to remove Xsan 1.4.2 clients from your SAN prior to upgrading you metadata controllers. Use the steps described below to upgrade the metadata controllers, and when instructed, upgrade your clients, then use Xsan Admin to add them back to the SAN. When upgrading the client, install the desired Mac OS X or Mac OS X Server version (v10.5.8 or v10.6) then update to the desired Xsan version (2.1.1 or 2.2).
Updating Metadata Controllers
When updating Xsan 1.4.2 controllers to Xsan 2, you may use any of the following three methods:
Upgrade from Xsan 1.4.2 to Xsan 2.1.1: Follow the steps in section A, below.
Upgrade from Xsan 1.4.2 to Xsan 2.2, using the same controllers: Follow the steps in sections A and B, below.
Upgrade from Xsan 1.4.2 to Xsan 2.2, while migrating to new controllers: Follow the steps in sections A and C, below.
A: Upgrading from Xsan 1.4.2 to 2.1.1
For detailed instructions in this section, please refer to the Xsan Migration Guide, Second Edition.
Back up your SAN volumes.
Unmount and stop existing volumes.
Verify volume integrity using cvfsck.
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.
If you are using Mac OS X 10.4 or Mac OS X Server 10.4, upgrade to Mac OS X 10.5 or Mac OS X Server 10.5.
If you are using an earlier version of Mac OS X 10.5 or Mac OS X Server 10.5, update to version 10.5.8.
Install Xsan 2. Important: Do not install Xsan 2.2 at this time. If your Xsan installation disc contains Xsan 2.2, do not use the disc. Instead, download Xsan 2.0 from Apple Support Downloads and install it. Use the serial number from your Xsan 2.2 disc.
Update to Xsan 2.1.1.
Run the SAN Setup Assistant. This starts the upgrade of each volume.
Wait for the volume upgrade to finish. The file-system upgrade can take less than an hour for a small volume or more than a day for a large one.
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.
If you do not plan to upgrade to Mac OS X v10.6 or Mac OS X Server v10.6 at this time, you may enable Spotlight on SAN volumes now.
If you plan to upgrade to Mac OS X v10.6, wait until after upgrading to enable Spotlight. Spotlight indexing may take several minutes or several hours depending on the size of the volume.
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 your target version is Xsan 2.1.1, your upgrade is complete: you may now upgrade your SAN clients and add them back to the SAN.
If you are upgrading to Xsan 2.2 on the same computer, continue with the instructions in section B.
If you are migrating to Xsan 2.2 on a new computer, skip to section C.
B: Upgrading from Xsan 2.1.1 to 2.2, using the same controller
For detailed instructions in this section, please refer to the Xsan Migration Guide, Third Edition. Step 1 in this section corresponds to step 3 in the "Updating Your SAN Software" section of the Guide.
If you plan to use Mac OS X Server 10.6 on your metadata controllers, upgrade the first controller now.
Update the first metadata controller to Xsan 2.2.
Upgrade the remaining controllers to 10.6 (if desired) and Xsan 2.2.
Upgrade previous SAN clients and add them back to the SAN.
If you have upgraded your controllers to Mac OS X Server 10.6, and use Xsan Admin to manage users and groups, establish your Open Directory replicas.
If all of your clients are using Xsan 2.2 or later, you may enable native extended attributes. Important: You cannot undo this action.
If you upgraded to Mac OS X v10.6, you may now enable Spotlight on SAN volumes, if desired.
Mount the SAN volumes on the SAN clients.
C: Migrating from Xsan 2.1.1 to Xsan 2.2 on new controllers
For detailed instructions in this section, please refer to the Xsan Migration Guide, Third Edition. Step 1 in this section corresponds to step 3 in the "Upgrading Both SAN Hardware and Software" section of the Guide.
Connect at least two Intel-based computers to the Xsan 2.1.1 SAN created in section A. These will be the new metadata controllers.
If you plan to run Mac OS X Server v10.6 on the new controllers, upgrade them now if necessary.
Install Xsan 2.2 on the new computers. If your Xsan installation disc contains Xsan 2.0, you will not be able to install it on Mac OS X Server v10.6. In this situation you will need to download and use the Xsan 2.2 full installer from Apple Support Downloads. Use the serial number from your original Xsan 2.0 disc.
Use Xsan Admin 2.2 on one of the new computers to add them all to the SAN.
Adjust volume failover priorities, so that all volumes are hosted by the new controllers during migration.
Make one of the new machines the primary controller.
Demote the old controllers.
Add new SAN clients. Upgrade any previous SAN members which will be clients of the upgraded SAN and add them back to the SAN.
If all of your clients are using Xsan 2.2, you may enable native extended attributes. Important: You cannot undo this action.
If you upgraded to Mac OS X v10.6, you may now enable Spotlight on SAN volumes, if desired.
Mount the SAN volumes on the SAN clients.
Learn more
If you see an alert in Xsan Admin that a volume is not running on a new Xsan 2.2 controller after adding it to an Xsan 2.1.1 SAN (step C-4 above), restart the volume.
If you encounter any issues when enabling native extended attributes, see this article.
If you are using Xsan to manage users and groups, the Password Server may not be running on your backup metadata controller after you upgrade it to Mac OS X Server v10.6. Use the following command to restart the service:
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.PasswordService.plist
