When setting up an Xsan volume, what must you do if you have Windows clients who are going to need access to the volume?

If you have Windows clients, choose an ID mapping method.
Note: To use ID mapping, Windows clients must be running StorNext 2.7. Xsan controllers and clients must be running Xsan 1.3 or later.

Generate IDs from GUID: Windows clients dynamically generate UIDs and GIDs based on GUID information in an Active Directory domain.

Use IDs from LDAP (RFC 2307): Windows clients get UID and GID values from the uidNumber and gidNumber attributes in Active Directory records.

For more information, see Mapping Windows User and Group IDs on page 112.

Terminal: How to run a Mac OS X package installer on a remote computer

ssh to the remote machine

sudo installer -pkg /tmp/Install_Package_Name.mpkg -target /

Or, if you want to watch the progress of installation, add the -verbose parameter:
$ sudo installer -verbose -pkg /tmp/Install_Package_Name.mpkg -target /

Terminal: how to copy something to a remote computer

scp -r /Volumes/MyVolume/Install_Package_Name.mpkg user@remotehost:/tmp/

this will put the package into the /tmp folder on the remote machine

When setting up a LUN that is larger than 2 terabytes, what must you keep in mind about legacy compatibility?

If you set up a LUN that is larger than 2 terabytes (TB), be aware that older clients (those running Xsan on Mac OS X 10.3 Panther or Xsan 1.2 or earlier on Mac OS X 10.4 Tiger) cannot read these large LUNs. A dialog appears on these older clients that says the LUN is unreadable. Be sure to click Ignore to dismiss this dialog. Do not click Format, or information on the corresponding Xsan volume will be lost. If you use LUNs greater than 2 TB, you should upgrade all SAN clients to Xsan 1.3 or later on Mac OS X or Mac OS X Server v10.4.

When configuring Xsan, If you create users and groups individually on each SAN computer without using a directory service (like Open Directory), what must you do?

If you create users and groups individually on each SAN computer, be sure that each user or group name is assigned the same numeric user ID (UID) or group ID (GID) on all SAN computers. One way to do this is to create an identical list of users and groups in the same order on each computer following a fresh install of the operating system.

Describe how to estimate metadata and Journal Data Storage Needs based on the number of files on a volume

To estimate the amount of space required for Xsan volume metadata, assume that 10 million files on a volume require approximately 10 gigabytes of metadata on the volumes metadata storage pool.

What are Xsan 1.4 hardware requirements

– Macintosh computers with an Intel or PowerPC G5 processor
– Clients should have a minimum of 256 MB of RAM.
– Controllers should have a minimum of 512 MB of RAM. For optimum performance, add an additional 512 MB of RAM for each SAN volume hosted by the controller.

Supported Operating Systems

You can install Xsan 1.4 only on computers running
– Mac OS X or Mac OS X Server v10.4.7 or later
To join an Xsan 1.4 SAN, Windows, AIX, IRIX, Linux, and Solaris clients must be running ADICs StorNext File System version 2.6 or 2.7. For complete compatibility information,
see Version Compatibility on page 12.

Supported Storage Devices

Although you can use any standard LUN storage device, this guide assumes you are using Xserve RAID systems for your storage devices.

Important: Be sure to install the latest firmware update on your Xserve RAID systems before you use them with Xsan.

For the best performance, use Xserve RAID systems that have:
– A full set of 14 Apple Drive Modules
– 512 MB of cache in each controller (1 GB total)

Fibre Channel Fabric
Unlike file system metadata, which controllers and clients exchange over Ethernet, actual file content in an Xsan SAN is transferred over Fibre Channel connections (as is
metadata that controllers access on a volume). To set up the connections, you need:

– Apple Fibre Channel PCI, PCI-X, or PCI-E cards for each client and controller computer
– One or more supported Fibre Channel switches
– Fibre Channel cables connecting computers and storage devices to the switches to form a Fibre Channel fabric

Fibre Channel PCI Cards
Install Apple Fibre Channel PCI, PCI-X, or PCI-E cards in all Macintosh computers that will connect to the SAN.

Fibre Channel Switches

The following Fibre Channel switches have been tested with Xsan, Xserve RAID systems, and the Apple Fibre Channel PCI, PCI-X, and PCI-E cards:
– Brocade Silkworm 3200, 3800, 3900, and 12000 series
– QLogic SANbox 28, SANbox 216, SANbox 264, SANbox 1400, and SANbox 5200
– Emulex SAN Switch 355, 375, and 9200
– Cisco MDS 9000 family

maximum length for the LUN name (label or disk name) on an Xsan volume

242 characters

maximum length for storage pool name (on an Xsan volume)

255 characters

maximum SAN name length

255 characters