Apple - Support - Most Recent - Xsan

Xsan: Best practices for data integrity

Mon, 08 Jun 2009 14:42:03 GMT

These suggested guidelines for deploying Xsan help to ensure consistent access to data stored on Xsan volumes.

Promise VTrak: Configuring for optimal performance

Fri, 05 Jun 2009 15:09:56 GMT

Configure Promise VTrak RAIDs for best performance using the guidelines in this article. Although Promise VTrak RAIDs may be manually configured, it is recommended that they be configured using the scripts described in this article. Both script and manual configuration steps are provided below. Note: Xsan-specific configuration scripts configure Revertible Spare Drives. In the event that a drive is replaced, data will be migrated from the Spare Drive to the replacement drive. Performance may be impacted for the duration of the migration procedure.

Promise VTrak: Second SAS-connected Expansion Chassis Only: Xsan (Data Only) configuration script

Thu, 04 Jun 2009 14:43:11 GMT

This article contains a script used to configure Promise VTrak SAS-connected Expansion Chassis for Xsan. This script is used in the event that a Promise VTrak RAID Controller has already been configured for use with Xsan, and that an Expansion Chassis is being connected to the already-configured RAID Controller. To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

Xsan: How to defragment data for multimedia applications

Thu, 04 Jun 2009 14:39:06 GMT

If you have media or render files stored on an Xsan volume that have become fragmented, multimedia applications may report dropped frames when you work with them. This can occur with any version of Final Cut Pro, Final Cut Express, iMovie, and Xsan.

Xsan 2: OK button disabled when editing affinity tag settings

Thu, 28 May 2009 15:20:06 GMT

When changing affinity tag settings during setup of an Xsan 2 volume, the OK button may become disabled. This can happen if the "MetadataAndJournal" affinity tag is set for use with "Any data". Using an affinity tag name that begins with a reserved storage pool name may also cause this issue.

Xsan: Client cannot access certain folders on Xsan volume, or cannot access an entire volume

Tue, 26 May 2009 13:24:44 GMT

Learn how to resolve three scenarios that one may encounter when attempting to access files on Xsan volumes or the volumes themselves: Scenario 1: A client may be unable to access folders on an Xsan volume. A red minus sign icon may appear on the folders, and when trying to access data, the Finder may state "The folder 'name' could not be opened because you do not have sufficient access privileges." If using the command line to attempt to navigate, this alert may appear: "Permission denied." Scenario 2: A client may be unable to access a folder or Xsan volume, but no red prohibitory icon appears on the volume or folder icons. When trying to access the volume or a folder on it, the Finder may state "The folder 'name' could not be opened because you do not have sufficient access privileges." If using the command line to attempt to navigate, this alert may appear: "Permission denied." Scenario 3: A client may not be able to perform basic file operations within an Xsan volume, or folder/file on the volume. In this situation, a lock icon may be visible on the volume/folder/icon in the Finder. This may occur even if the user's account has been given correct permissions. The Finder may become unresponsive.

Xsan, multimedia apps: Troubleshooting dropped frame issues

Wed, 13 May 2009 18:51:32 GMT

Learn how to troubleshoot situations in which dropped frames occur when video is stored via Xsan media. "Dropped frames" refers to frames of video that are unintentionally skipped during capture, editing, or playout.

Xsan 2: Integrating Promise VTrak RAIDs into an existing Xsan 2 deployment

Wed, 13 May 2009 16:17:48 GMT

In order to achieve maximum performance when integrating Promise VTrak RAIDs into an existing Xsan 2 volume that is composed of Apple Xserve RAIDs, the Promise VTrak RAIDs should not be included in storage pools that are composed of Apple Xserve RAIDs. Instead, create new storage pools to be exclusively composed of Promise VTrak RAIDs.

Xsan 2.1.1: Xsan Admin cannot save SAN document

Tue, 05 May 2009 14:49:49 GMT

If your Xsan 2.1.1 SAN includes one or more Xserve (Early 2009) or Mac Pro (Early 2009) members, you may not be able to save a SAN configuration document in Xsan Admin. If you already have a SAN configuration document saved, you may not be able to save changes to it, but Xsan Admin will still report the current status of the SAN. If you set up a new SAN, you may not be able to create a configuration document. Xsan Admin will present the SAN Setup assistant each time you open it.

Xsan 2: Compatibility of Xsan clients with Grass Valley SAN shared storage systems

Fri, 24 Apr 2009 16:15:47 GMT

Learn which versions of Xsan 2 are compatible with Grass Valley SAN shared storage systems.

Xsan 2: Xsan Admin Setup Assistant appears when opening Xsan Admin

Wed, 22 Apr 2009 20:45:38 GMT

You may see the Xsan Setup Assistant each time you open Xsan Admin. If you have already configured a SAN or previously connected to an existing SAN, you can avoid the Setup Assistant using the instructions in this article.

Xsan Admin: Unable to see a computer you want to add to a SAN

Fri, 06 Mar 2009 15:37:42 GMT

If you can't see a computer that you want to add to a SAN via Xsan Admin, follow the instructions in this article.

Xsan: How to automount StorNext volumes

Tue, 03 Mar 2009 18:39:47 GMT

This article describes the configuration of Xsan clients running Xsan 1.4.1 and earlier to automount filesystems hosted by Quantum StorNext Metadata Controllers. Perform these steps for each Xsan client that should mount a StorNext filesystem at startup. To configure automounting of StorNext filesystems on Xsan 1.4.2 or later, please refer to instructions in the StorNext installation guide for your version of StorNext available at the Quantum web site.

Xsan: Compatibility of Xsan versions with Mac OS X versions

Tue, 03 Mar 2009 15:51:20 GMT

This article contains a list of which Xsan versions are compatible with which versions of Mac OS X client and server; the matrix shows required versions of Xsan and Mac OS X for when you want to upgrade your Xsan version. Note: Xsan and Mac OS X versions running on MDCs must always be the same or later versions than those which are running on the Xsan clients (for example, clients running Xsan 1.4.2 on Mac OS X 10.4.11 means MDCs must be running Xsan 1.4.2 or later, and Mac OS X 10.4.11 or later).

Xsan: Compatibility of SAN clients with Xsan and StorNext controllers

Tue, 03 Mar 2009 15:50:35 GMT

Learn which versions of Xsan can be used in the same SAN with StorNext controllers, and which versions of StorNext can be used in the same SAN with Xsan controllers.

Xsan Tuner: Results from Final Cut Tasks may be unreliable on Intel-based Macs

Thu, 15 Jan 2009 22:49:05 GMT

On Intel-based Macs, results from Xsan Tuner's Final Cut Tasks may be unreliable.

Xsan: Managing video production workflow in relation to Xsan Volume bandwidth

Thu, 08 Jan 2009 18:36:44 GMT

In a video production workflow that utilizes Xsan, video clips are copied to and from an Xsan Volume. Each copy operation is called a stream. Video production operations that require streaming video include ingest, editing and playout. Each concurrently accessed stream of video consumes a portion of the Xsan Volume’s total minimum available bandwidth. It is important that the video editing workflow be managed so that the total minimum available bandwidth is not exceeded, as doing so may result in dropped frames.

Troubleshooting Xsan volume failover issues

Mon, 08 Dec 2008 22:57:01 GMT

What is "volume failover"? If two or more Metadata Controllers (MDC) are configured to host an Xsan volume, in the event that a MDC becomes inactive another MDC should take control of the Xsan volume. The act of a standby MDC assuming active hosting from another MDC is called "failover." Understanding failover-related communications: While configuring Xsan, one designates over which subnet Xsan metadata communication will occur. Over this subnet, MDCs communicate failover-related heartbeats. If this heartbeat communication cannot occur due to network conditions or misconfiguration, failover will not occur as expected. To determine which interface is being used for metadata communications follow these steps: Xsan 1.4.2 and earlier: Open Xsan Admin and select Setup > Computers. Inspect the settings for each MDC. Observe the ‘Access the SAN via’ setting which designates the subnet over which metadata communications will occur. Xsan 2.0 and later: Open Xsan Admin and select the Overview Pane. The Metadata Subnet is displayed in the Details section. When may failover occur? The following events may result in failover of all Xsan volumes: The active MDC is unreachable by the secondary MDC via the ethernet network used for metadata communications. The active MDC is rebooted or shutdown. The following events will result in failover of a specific Xsan volume: The active MDC cannot see one or more LUNs associated with the volume. Xsan Admin or cvadmin is used to failover a volume. Note: Following a failover event, a volume does not automatically failover back to the MDC that was hosting the volume previous to the failover.

Xsan 2, Mac OS X Server version 10.5: Directory Utility LDAPv3 plugin settings must be manually set on Primary Xsan Metadata Controller before Xsan Setup Assistant

Wed, 03 Dec 2008 15:07:20 GMT

When using the Mac OS X Server version 10.5 Server Assistant, if one assigns the role "Xsan Metadata Controller" and then chooses to connect to an existing Directory Domain, Directory Utility’s LDAPv3 plugin may not be configured as expected.

Xsan: Can't change role of Xsan client to metadata controller

Tue, 02 Dec 2008 19:42:54 GMT

You may not be able to change the role of an Xsan client to metadata controller if it is running Mac OS X 10.5 (client).

Xsan 1.4 or earlier: All controllers must be online when making SAN configuration changes

Thu, 20 Nov 2008 19:39:21 GMT

In a storage area network (SAN) with multiple metadata controllers (MDCs), if one or more controllers are down while you are reconfiguring the SAN, those controllers may not synchronize with the updated configuration when they come back online.

Xsan: Only Xsan and Open Directory services should be hosted on Xsan Metadata Controllers

Wed, 19 Nov 2008 21:53:41 GMT

Metadata controller performance may degrade when hosting additional services such as AFP, SMB, NFS, Mail, Netboot, and so on.

Xsan 1.4.2 or later: Unmounted Xsan volume re-mounts automatically

Thu, 13 Nov 2008 20:32:01 GMT

An Xsan volume may re-mount (become available) after unmounted or ejected via the Finder or the command line.

Xsan Help: Changing a Controller's IP Address

Tue, 11 Nov 2008 17:53:43 GMT

Follow the instructions below instead of those on page 67 of the Xsan Administrator's Guide.

Xsan Help: Tips to avoid unexpected volume behavior

Tue, 11 Nov 2008 17:37:36 GMT

Tips to avoid unexpected volume behavior.

Xsan Help: Tips to avoid unexpected admin or client behavior

Tue, 11 Nov 2008 17:08:38 GMT

Tips to avoid unexpected admin or client behavior.

Xsan: Guidelines for volume expansion

Tue, 11 Nov 2008 00:31:46 GMT

When adding LUNs to an Xsan volume, follow these guidelines:

Using QLogic switches with Apple Fibre Channel Cards

Tue, 11 Nov 2008 00:06:51 GMT

When using QLogic fibre switches with Apple Fibre Channel Cards (HBAs) in a Storage Area Network (SAN) topology such as an Xsan deployment, or in a Network Area Storage (NAS) deployment, you may need to modify the port settings to ensure constant communication between devices on the fabric. The port settings may vary depending on whether the fibre switch port will connect to an Apple Fibre Channel Card or to a fibre-attached storage device. In fibre switch terminology, hosts such as an Xserve or a Mac Pro workstation are known as initiators, and fibre-attached storage devices are known as targets.

Xsan 2, Promise VTrak RAID: Configuring for use in a video editing environment

Mon, 10 Nov 2008 23:26:53 GMT

You can choose to deploy Xsan 2.0 or later with a single Promise VTrak RAID Controller with the intention of later expanding your storage to include VTrak Expansion Chassis and/or additional RAID controllers. Follow the steps in this article to ensure that the Promise VTrak and Xsan are configured for optimal performance and for ease of adding storage.

Xsan 2: Upgrading Xsan 1.4.2 to Xsan 2

Mon, 10 Nov 2008 23:11:32 GMT

Follow these instructions to upgrade your Xsan 1.4.2 SAN to Xsan 2.

Promise VTrak: RAID Controllers - Direct Attached configuration script

Tue, 21 Oct 2008 17:15:35 GMT

This article contains a script used to configure Promise RAID Controllers for Direct Attached Storage. To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

Promise VTrak: RAID Controllers and SAS-connected Expansion Chassis - Direct Attached with Spares configuration script

Fri, 17 Oct 2008 17:50:15 GMT

This article contains a script used to configure Promise RAID Controllers and SAS-connected Expansion Chassis for Direct Attached Storage. To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

About the Xsan 2.1.1 Update

Wed, 15 Oct 2008 20:12:30 GMT

This article describes the Xsan 2.1.1 Update. This update is available as a manual download from Apple Support Downloads and as an automatic Software Update. Important: Read before installing Xsan 2.0 or 2.1 and Mac OS X 10.5 or Mac OS X Server 10.5, or later, is required in order to install Xsan 2.1.1. Mac OS X 10.5.5 or Mac OS X Server 10.5.5 or later is recommended for this update. If you are setting up a new Xsan deployment, please see this article for the proper installation order. Be sure that all Metadata Controllers (MDCs) are updated before you make any configuration changes. Before installing, please review the Xsan 2 Migration Guide. During installation, do not change any Xsan settings, whether using Xsan Admin or a command-line tool. Metadata Controller (MDC) software version Your MDCs must always have software versions (both Xsan and Mac OS) that are the same or more recent than the most recent client versions. For example, if any client in your Xsan network is using Xsan 2.1.1 with Mac OS X 10.5.5 or later, then your metadata controllers (MDCs) must also be updated to Xsan 2.1.1 on the same version of Mac OS X. Hardware requirements Xserve or Xserve G5 Mac Pro Power Mac G5 (any) 2GB RAM Storage network requirements Apple Fibre Channel PCI, PCI-X, or PCI-E Card

Promise VTrak: RAID Controllers - Direct Attached with Spares configuration script

Wed, 15 Oct 2008 17:04:15 GMT

Promise VTrak: RAID Controllers - 8-Drive Model - Direct Attached with Spares configuration script

Wed, 15 Oct 2008 17:03:19 GMT

Promise VTrak: RAID Controllers - 8-Drive Model - Direct Attached configuration script

Wed, 15 Oct 2008 17:02:56 GMT

Xsan 2: About yellow and red volume status alerts in Xsan Admin

Wed, 15 Oct 2008 16:54:39 GMT

A yellow "!" alert icon or red "x" icon may appear on an Xsan volume's icon in the Volumes pane of Xsan Admin. This may indicate that a volume is stopped or has not been activated on all appropriate controllers.

Xsan 2: Computer may appear more than once in a volume failover priority sheet

Tue, 14 Oct 2008 17:20:01 GMT

A computer may appear multiple times in an Xsan volume's "Edit Failover Priority" sheet if it was not removed from the SAN before Xsan was reinstalled on it.

Xsan: How to determine available capacity

Tue, 14 Oct 2008 17:19:03 GMT

Use the steps below to accurately detemine available capacity of an Xsan volume.

Promise VTrak: RAID Head - Xsan (Metadata and Data) configuration script

Tue, 07 Oct 2008 14:36:15 GMT

This article contains a script used to configure Promise VTrak RAID Controllers for Xsan (Metadata and Data). To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

Xsan: How to repair the filesystem

Wed, 24 Sep 2008 22:34:53 GMT

Xsan volumes are designed in such a way that filesystems are unlikely to become damaged ("corrupted"), but you should be aware of what you can do if filesystem repair becomes necessary. Follow the recommendations in this article in order to reduce the chances of an Xsan filesystem developing issues.

Xsan 2 or later: How to configure MultiSAN

Wed, 17 Sep 2008 15:27:17 GMT

Learn how to configure MultiSAN in Xsan 2 or later. What is MultiSAN? MultiSAN is a configuration in which any given MDC may host Xsan volumes that are not necessarily hosted by other MDCs. The benefit of MultiSAN is increased volume performance resulting from the distribution of volume hosting to specific Metadata Controllers.

Podcast Producer system requirements (Mac OS X 10.5)

Fri, 15 Aug 2008 21:10:10 GMT

Podcast Producer system requirements (Mac OS X 10.5)

Xsan Help: Tips for avoiding unexpected hardware or performance issues

Thu, 14 Aug 2008 18:26:07 GMT

Tips for avoiding unexpected hardware or performance issues.

Xsan 1.1: Modify upgraded Xsan installations for increased performance and stability

Thu, 14 Aug 2008 16:42:55 GMT

In Xsan 1.1, the default value for a volume's ThreadPoolSize parameter was changed from 16 to 128. Because the new default value is written to a volume's config file at the time of creation, you must manually edit the file to get this benefit for existing installations that were upgraded to 1.1.

Using Xsan 1.4 with Intel-based Macs

Thu, 14 Aug 2008 16:06:17 GMT

The shrink-wrap retail version of Xsan 1.4 supports Intel-based Macintosh computers running Mac OS X or Mac OS X Server 10.4.7 or later with at least 512 MB RAM and Fibre Channel connectivity.

Xsan Help: Using the cvadmin Command

Thu, 14 Aug 2008 15:25:26 GMT

On page 68 of the Xsan Administrator's Guide, in the instructions on upgrading controller software, step 1 shows how to use the cvadmin command to force a controller failover: $ sudo ./cvadmin fail

Xsan 2 Administrator's Guide: Correction to page 21

Wed, 30 Jul 2008 18:32:27 GMT

The Xsan 2 Administrator's Guide incorrectly states the "Number of computers on a SAN (metadata controllers and clients) is limited to 64" on page 21.

About the Xsan 2.1 Update

Wed, 25 Jun 2008 03:40:17 GMT

This article describes the Xsan 2.1 Update. This update is available via both Apple Downloads and Software Update. Important: Read before installing Xsan 2.0 and Mac OS X 10.5 or Mac OS X Server 10.5, or later, is required in order to install Xsan 2.1. Mac OS X 10.5.3 or Mac OS X Server 10.5.3 or later is recommended for this update. If you are setting up a new Xsan deployment, please see this article for the proper installation order. Be sure that all Metadata Controllers (MDCs) are updated before you make any configuration changes. Before installing, please review the Xsan 2 Migration Guide. During installation, do not change any Xsan settings, whether using Xsan Admin or a command-line tool. Metadata Controller (MDC) software version Your MDCs must always have software versions (both Xsan and Mac OS) that are the same or more recent than the most recent client versions. For example, if any client in your Xsan network is using Xsan 2.1 with Mac OS X 10.5.3 or later, then your metadata controllers (MDCs) must also be updated to Xsan 2.1 on the same version of Mac OS X.