Apple Xsan 2 - Manual (Page 134)

134 Appendix A Upgrade to Xsan 2.3
Convert a metadata controller to a client:
In Xsan Admin, select Computers in the SAN Assets list, select the metadata controller
m
in the list, and choose Make Client from the Action pop-up menu (gear).
If you can’t choose Make Client, make sure all Xsan clients and metadata controllers
are turned on and their status is Ready in Xsan Admin’s Computers list.
Step 5: Unmount and stop all volumes
Before migrating data from your old metadata controllers to new computers, stop all
SAN volumes so they can’t be changed.
Unmount and stop al volumes:
1 In Xsan Admin, select Mounts in the SAN Assets list.
2 Choose a volume from the Volume pop-up menu.
3 Select all clients in the list and click the Unmount button.
To select more than one client, hold down the Command or Shift key as you select
clients in the list.
4 Choose Stop Volume from the Action pop-up menu (gear).
5 Repeat for all volumes in the SAN.
Step 6: Connect new Macs to the SAN
Connect your new Macs to the SAN’s Ethernet and Fibre Channel networks. If
necessary, remove old computers to make ports available.
Don’t go through the setup assistant on the new Macs yet.
Important: Mac OS X Lion Server is recommended for all SAN controllers and is
required if you use Xsan Admin to manage users and groups. Make sure any client you
want to convert to a controller has Mac OS X Lion Server.
Step 7: Migrate the primary metadata controller
Use the server setup assistant to migrate server data from the old primary controller to
a new server.
Migrate the primary controller to a new server:
1 Use Xsan Admin to make sure the primary metadata controller is in the failover priority
list for every SAN volume.
2 Make sure Xsan Admin isn’t open on any computer that can connect to a metadata
controller.
Xsan Admin can become confused if it’s open when a SAN computer’s IP address
migrates to a new computer.