<?xml version='1.0' encoding='UTF-8'?>







	
	



<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Apple - Support - Most Recent  - Xsan</title>
<link>http://www.apple.com/support/</link>
<description>Apple - Support - Most Recent - Apple Inc.</description>
<language>en-us</language>
<copyright>Copyright 2009 Apple Inc.</copyright>
<ttl>1440</ttl>
<pubDate>Mon, 23 Nov 2009 05:28:46 GMT</pubDate>
<category>Apple</category>
<generator>In house</generator>
<docs>http://rss.support.apple.com/xsan</docs>
 








	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2: Switching a controller's metadata Ethernet interface]]></title>
	<description>Release date: Tue, 06 Oct 2009 19:17:00 GMT</description>
	<link>http://support.apple.com/kb/HT3898</link>
	<content:encoded><![CDATA[On some occasions a user may require a change in the Xsan controller metadata network interface. Note that all clients and controllers should have an interface that is on the desired subnet.]]></content:encoded>
	<pubDate>Fri, 30 Oct 2009 18:58:38 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3898</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2.2: "Incorrect search policy" appears in Xsan Admin]]></title>
	<description>Release date: Fri, 25 Sep 2009 18:04:00 GMT</description>
	<link>http://support.apple.com/kb/HT3888</link>
	<content:encoded><![CDATA[In Xsan Admin 2.2, computers may be reported as having an &quot;Incorrect search policy&quot; if the Directory Service search policy on the Xsan node is changed. 
If Xsan manages your users and groups, or if you chose to connect to an existing Open Directory domain in Server Assistant, then Xsan Admin will monitor the Directory Service search policy on each Xsan node. In these two situations, Xsan Admin expects each nodes' search policy to contain only the server(s) that Xsan Admin adds to the computers.]]></content:encoded>
	<pubDate>Tue, 13 Oct 2009 20:43:59 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3888</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Compatibility of SAN clients with Xsan and StorNext controllers]]></title>
	<description>Release date: Tue, 08 Apr 2008 16:01:00 GMT</description>
	<link>http://support.apple.com/kb/HT1517</link>
	<content:encoded><![CDATA[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.]]></content:encoded>
	<pubDate>Mon, 12 Oct 2009 21:43:43 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT1517</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2.2: How to set Spotlight search levels]]></title>
	<description>Release date: Thu, 30 Jul 2009 16:49:00 GMT</description>
	<link>http://support.apple.com/kb/HT3749</link>
	<content:encoded><![CDATA[With Xsan 2.2, Spotlight supports two different levels of searching:&nbsp;File system search and Indexed search.

    File system search (FsSearch) - Searches against file system attributes are enabled but no indexed searching of content is performed.
    Indexed search (ReadWrite) - Full file system and indexed content is enabled; the index will be updated as file system content changes.

By default, Indexed search is enabled when Spotlight is activated for an Xsan volume in Xsan 2.0 or later.
The FsSearch option requires Mac OS&nbsp;X v10.6 metadata controllers using Xsan 2.2.]]></content:encoded>
	<pubDate>Tue, 06 Oct 2009 19:51:19 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3749</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2.x: Available free space incorrect after bandwidth expansion]]></title>
	<description>Release date: Thu, 24 Sep 2009 21:50:00 GMT</description>
	<link>http://support.apple.com/kb/TS3041</link>
	<content:encoded><![CDATA[After expanding an Xsan volume,  the available free space may be less than expected. If free space does not increase by the size of the storage that was added to the volume, follow the instructions in this article.]]></content:encoded>
	<pubDate>Fri, 02 Oct 2009 16:13:11 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS3041</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Guidelines for volume expansion]]></title>
	<description>Release date: Thu, 14 Aug 2008 15:45:00 GMT</description>
	<link>http://support.apple.com/kb/HT2769</link>
	<content:encoded><![CDATA[When adding storage to an Xsan volume, use these guidelines.]]></content:encoded>
	<pubDate>Wed, 30 Sep 2009 17:32:24 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT2769</guid>
	</item>











	
	
	
	
	
	
	
	<item>
	<title><![CDATA[About the security content of Xsan 2.2]]></title>
	<description>Release date: Mon, 17 Aug 2009 22:01:00 GMT</description>
	<link>http://support.apple.com/kb/HT3797</link>
	<content:encoded><![CDATA[This document describes the security content of Xsan 2.2.
For the protection of our customers, Apple does not disclose, discuss, or confirm security issues until a full investigation has occurred and any necessary patches or releases are available. To learn more about Apple Product Security, see the Apple Product Security website.
For information about the Apple Product Security PGP Key, see &quot;How to use the Apple Product Security PGP Key.&quot;
Where possible, CVE IDs are used to reference the vulnerabilities for further information.
To learn about other Security Updates, see &quot;Apple Security Updates.&quot;]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 18:24:35 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3797</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2: Integrating Promise VTrak RAIDs into an existing Xsan 2 deployment]]></title>
	<description>Release date: Fri, 22 Feb 2008 12:34:00 GMT</description>
	<link>http://support.apple.com/kb/HT1110</link>
	<content:encoded><![CDATA[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.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:40:05 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT1110</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 1.4.2 and earlier: cvcp does not copy extended attributes for individual file copies]]></title>
	<description>Release date: Tue, 11 Aug 2009 15:41:00 GMT</description>
	<link>http://support.apple.com/kb/TS2940</link>
	<content:encoded><![CDATA[In Xsan 1.4.2 and earlier, copying an individual file using cvcp does not copy the file's extended attributes. Since preservation of a file's extended attributes is  essential for proper functioning of many file types, you should avoid copying files with cvcp in this way.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:34:26 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2940</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Update Xsan 2.1.1 to 2.2 for compatibility with Mac OS X v10.6 or Mac OS X Server v10.6]]></title>
	<description>Release date: Tue, 25 Aug 2009 01:01:00 GMT</description>
	<link>http://support.apple.com/kb/HT3826</link>
	<content:encoded><![CDATA[Xsan 2.1.1 is not compatible with Mac OS X v10.6 or Mac OS X Server v10.6 Snow Leopard.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:33:21 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3826</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2.2: After changing the Primary MDC, "Incorrect search policy" appears in Xsan Admin for Xsan 2.1.1 or earlier clients]]></title>
	<description>Release date: Tue, 18 Aug 2009 18:56:00 GMT</description>
	<link>http://support.apple.com/kb/HT3801</link>
	<content:encoded><![CDATA[With Xsan 2.2 or later you can change the role of another controller to the Primary MDC. If the metadata controllers are providing Open Directory services, using this feature will also move the Open Directory Master to the new Primary MDC. Xsan clients running Xsan 2.2 or later will automatically update their Directory Service bindings to the new Open Directory Master.
However, Xsan clients running Xsan 2.1.1 or earlier will not automatically update their Directory Service bindings, and will appear with an &quot;Incorrect search policy&quot; in Xsan Admin.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:33:06 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3801</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Compatibility of Xsan versions with Mac OS X versions]]></title>
	<description>Release date: Thu, 08 May 2008 17:33:00 GMT</description>
	<link>http://support.apple.com/kb/HT1862</link>
	<content:encoded><![CDATA[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 2.1.1 on Mac OS X 10.5.8 means MDCs must be running Xsan 2.1.1 or later, and Mac OS X 10.5.8 or later). For more information about compatibility between Xsan versions within a SAN, see this article.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:32:41 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT1862</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[About the Xsan 2.2 Update]]></title>
	<description>Release date: Thu, 18 Sep 2008 22:57:00 GMT</description>
	<link>http://support.apple.com/kb/HT3172</link>
	<content:encoded><![CDATA[This article describes the Xsan 2.2 update, available as a manual download from Apple Support Downloads and as an automatic Software Update.
Important: Read before installing

    Be sure that all Metadata Controllers (MDCs) are updated before you make any configuration changes.
    Your MDCs must always have software versions (both Xsan and Mac OS X) that are the same or more recent than the most recent client versions. For details, see this article.
    If you are updating from a version earlier than Xsan 2.1.1, are upgrading to Snow Leopard, or have PowerPC-based computers on your SAN, please see the Xsan 2 Migration Guide for additional instructions.
    During installation, do not change any Xsan settings, whether using Xsan Admin or a command-line tool.

Software requirements

    Mac OS X or Mac OS X Server v10.5.8 or 10.6 or later (Mac OS X Server required for MDC if you are using Xsan to manage users and groups)
    Xsan 2.0, 2.1, 2.1.1, or 2.2

Hardware requirements

    Xserve with an Intel processor, or Mac Pro
    2GB RAM for Xsan client
    2GB RAM plus 2GB per volume for MDC
    Apple Fibre Channel Card
]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:32:11 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3172</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Mac OS X Server v10.6, Xsan 2.2: How to enable SSL on a mail cluster]]></title>
	<description>Release date: Thu, 27 Aug 2009 00:41:00 GMT</description>
	<link>http://support.apple.com/kb/HT3839</link>
	<content:encoded><![CDATA[Learn how to enable SSL&nbsp;on  a mail cluster using Xsan. These instructions  supplement, but do not replace, the &quot;Securing Mail Service with SSL&quot; section of the Mail Service Administration guide.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:31:46 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3839</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Upgrading from Xsan 1.4.2 to Xsan 2.x]]></title>
	<description>Release date: Tue, 26 Feb 2008 22:44:00 GMT</description>
	<link>http://support.apple.com/kb/HT1127</link>
	<content:encoded><![CDATA[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.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:31:21 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT1127</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2.2: Enabling extended attributes]]></title>
	<description>Release date: Fri, 14 Aug 2009 00:26:00 GMT</description>
	<link>http://support.apple.com/kb/HT3791</link>
	<content:encoded><![CDATA[If all of the computers on your SAN are running Xsan 2.2 or later, you can enable extended attributes on your SAN volumes to improve volume performance and efficiency.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:30:26 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3791</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2.2: "fsmpm not running" message in Xsan Admin]]></title>
	<description>Release date: Thu, 30 Jul 2009 21:18:00 GMT</description>
	<link>http://support.apple.com/kb/TS2923</link>
	<content:encoded><![CDATA[Xsan Admin may display the message &quot;fsmpm not running&quot; for a computer that is a member of the Xsan.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:29:48 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2923</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Compatibility of Xsan metadata controllers (MDCs) and clients]]></title>
	<description>Release date: Fri, 31 Jul 2009 17:39:00 GMT</description>
	<link>http://support.apple.com/kb/HT3755</link>
	<content:encoded><![CDATA[In some situations, you can use clients and metadata controllers with different versions of Xsan in the same SAN.
In all cases, the versions of Xsan and Mac OS X on the metadata controller must the same as, or later than, the latest versions on a client.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:29:04 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3755</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2.2: Avoid using native extended attributes with StorNext clients]]></title>
	<description>Release date: Thu, 30 Jul 2009 18:46:00 GMT</description>
	<link>http://support.apple.com/kb/HT3751</link>
	<content:encoded><![CDATA[If you connect StorNext clients to your SAN running Xsan 2.2, avoid using native extended attributes. StorNext clients will not preserve extended attributes when copying or moving files on the Xsan 2.2 volume.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:28:16 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3751</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2: Optimizing file system journal size]]></title>
	<description>Release date: Thu, 30 Jul 2009 21:22:00 GMT</description>
	<link>http://support.apple.com/kb/HT3762</link>
	<content:encoded><![CDATA[Xsan versions earlier than 2.2 defaulted to creating a file system journal of 16 MB, which is a reasonable default for many Xsan volumes. There may be circumstances in which this journal size may be insufficient and hamper performance in file system operations, especially ones involving metadata. Increasing the journal size may improve performance of file system operations. Changing the journal size for an Xsan volume can be done without recreating the volume. You should first back up your Xsan configuration on your metadata controllers, back up any data, and test the changes in a test environment before implementing them in a production environment.
Xsan 2.2 automatically includes this change in the volume Journal when the volume is created, but this process will still be valid if you wish to manually tune the journal size.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:27:19 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3762</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Install Xsan 2.2 Update for 10.6 after installing Mac OS X v10.6]]></title>
	<description>Release date: Thu, 30 Jul 2009 18:50:00 GMT</description>
	<link>http://support.apple.com/kb/TS2920</link>
	<content:encoded><![CDATA[After upgrading an Xsan system to Mac OS&nbsp;X v10.6 Snow Leopard or Mac OS&nbsp;X&nbsp;Server v10.6, you may see one of these status messages&nbsp; in the Xsan Admin computer list next to the Mac that was upgraded:

    &quot;Xsan 2 not installed&quot;
    &quot;Unreachable or offline&quot;
]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:26:54 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2920</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2: "The item will be deleted immediately" or "-1407" alert when moving items to the Trash]]></title>
	<description>Release date: Wed, 12 Aug 2009 14:50:00 GMT</description>
	<link>http://support.apple.com/kb/TS2942</link>
	<content:encoded><![CDATA[When moving items from a locally-mounted Xsan volume to the Trash, you may see an alert stating &quot;The item will be deleted immediately&quot; or an alert with the number -1407.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:26:24 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2942</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2: Compatibility of Xsan clients with Grass Valley SAN shared storage systems]]></title>
	<description>Release date: Tue, 14 Apr 2009 16:05:00 GMT</description>
	<link>http://support.apple.com/kb/HT3531</link>
	<content:encoded><![CDATA[Learn which versions of Xsan 2 are compatible with Grass Valley SAN shared storage systems.]]></content:encoded>
	<pubDate>Mon, 14 Sep 2009 17:24:04 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3531</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2.x: If an Xsan volume failover occurs before Spotlight becomes active, the Backup Controller may not enable Spotlight]]></title>
	<description>Release date: Thu, 20 Aug 2009 23:26:00 GMT</description>
	<link>http://support.apple.com/kb/TS2950</link>
	<content:encoded><![CDATA[After creating a volume with Spotlight enabled, or after enabling Spotlight on an Xsan volume, it make take several minutes for Spotlight to become active on the volume. &nbsp;During this time, if an MDC failover occurs, Spotlight will not activate properly. This article applies to Xsan v2.0 and later.]]></content:encoded>
	<pubDate>Wed, 26 Aug 2009 17:51:51 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2950</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[About the Xsan 2.1.1 Update]]></title>
	<description>Release date: Thu, 18 Sep 2008 22:53:00 GMT</description>
	<link>http://support.apple.com/kb/HT3171</link>
	<content:encoded><![CDATA[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.
    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
]]></content:encoded>
	<pubDate>Wed, 29 Jul 2009 16:09:07 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3171</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Some features are not supported with StorNext volumes]]></title>
	<description>Release date: Wed, 01 Jul 2009 17:39:00 GMT</description>
	<link>http://support.apple.com/kb/HT3658</link>
	<content:encoded><![CDATA[Some Xsan features are not supported when accessing a SAN&nbsp;volume running on Quantum StorNext metadata controllers.]]></content:encoded>
	<pubDate>Tue, 14 Jul 2009 20:46:54 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3658</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2.1.1: Script to reboot Intel-based Xserve MDCs after failover]]></title>
	<description>Release date: Fri, 05 Jun 2009 20:09:00 GMT</description>
	<link>http://support.apple.com/kb/HT3620</link>
	<content:encoded><![CDATA[This script in this article immediately reboots an Xsan Metadata Controller (MDC) that has lost control of an Xsan volume after an Xsan volume failover. If a failover occurs for any reason, the script will be executed by the MDC that takes control of the volume. The script uses Lights Out Management (LOM) to send a reboot signal to the previously active MDC. This action ensures that the Xsan volume&rsquo;s metadata cannot be modified by the previously active MDC after a failover.
Xsan includes multiple safeguards to avoid a situation where an Xsan volume is active on more than one MDC. This script is not required. It is provided as an example for sites where an additional hardware-based method is desired to prevent this unlikely scenario.
Use of this script is optional and at your own risk. Verify system requirements before installing. Apple does not provide support for modifications of this script.
Notes

    This script is designed for Xsans with two MDCs running Xsan 2.1.1. Do not deploy this script if your Xsan volume has more than two MDCs.
    Both MDCs must be Intel-based Xserves because of the LOM commands this script uses to send the reboot signal.
    This script can be used in Xsans with more than one volume. Each volume should be configured to run on both MDCs with the same failover priority.
    It is recommended that only Xsan and Open Directory services be hosted on Xsan MDCs. If Open Directory services are running on the MDCs, it is important that an Open Directory Replica be available at all times. This will ensure continual availability of Open Directory services should an MDC be rebooted by this script.
    Important: The MDC&rsquo;s internal hard drives should be formatted as Mac OS Extended with journaling enabled.
]]></content:encoded>
	<pubDate>Tue, 14 Jul 2009 20:40:56 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3620</guid>
	</item>





















	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Best practices for data integrity ]]></title>
	<description>Release date: Thu, 14 Aug 2008 15:03:00 GMT</description>
	<link>http://support.apple.com/kb/HT2761</link>
	<content:encoded><![CDATA[These suggested guidelines for deploying Xsan help to ensure consistent access to data stored on Xsan volumes.]]></content:encoded>
	<pubDate>Mon, 08 Jun 2009 14:42:03 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT2761</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Promise VTrak: Configuring for optimal performance]]></title>
	<description>Release date: Thu, 13 Mar 2008 19:39:00 GMT</description>
	<link>http://support.apple.com/kb/HT1200</link>
	<content:encoded><![CDATA[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.]]></content:encoded>
	<pubDate>Fri, 05 Jun 2009 15:09:56 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT1200</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Promise VTrak: Second SAS-connected Expansion Chassis Only: Xsan (Data Only) configuration script]]></title>
	<description>Release date: Mon, 01 Jun 2009 18:02:00 GMT</description>
	<link>http://support.apple.com/kb/HT3600</link>
	<content:encoded><![CDATA[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 &quot;#Begin Copy&quot; to the line &quot;#End Copy&quot; 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.]]></content:encoded>
	<pubDate>Thu, 04 Jun 2009 14:43:11 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3600</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: How to defragment data for multimedia applications]]></title>
	<description>Release date: Thu, 28 May 2009 21:46:00 GMT</description>
	<link>http://support.apple.com/kb/TS2778</link>
	<content:encoded><![CDATA[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.]]></content:encoded>
	<pubDate>Thu, 04 Jun 2009 14:39:06 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2778</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2: OK button disabled when editing affinity tag settings]]></title>
	<description>Release date: Fri, 08 May 2009 19:20:00 GMT</description>
	<link>http://support.apple.com/kb/TS2737</link>
	<content:encoded><![CDATA[When changing affinity tag settings during setup of an Xsan 2 volume, the OK button may become disabled. 
This can happen if the &quot;MetadataAndJournal&quot; affinity tag is set for use with &quot;Any data&quot;. Using an affinity tag name that begins with a reserved storage pool name may also cause this issue.]]></content:encoded>
	<pubDate>Thu, 28 May 2009 15:20:06 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2737</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Client cannot access certain folders on Xsan volume, or cannot access an entire volume]]></title>
	<description>Release date: Mon, 11 May 2009 18:44:00 GMT</description>
	<link>http://support.apple.com/kb/TS2742</link>
	<content:encoded><![CDATA[Learn how to resolve three scenarios that one may encounter when attempting to access files on Xsan volumes or the volumes themselves:

    Scenario 1:&nbsp;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 &quot;The folder 'name' could not be opened because you do not have sufficient access privileges.&quot; If using the command line to attempt to navigate, this alert may appear:&nbsp;&quot;Permission denied.&quot;
    
    &nbsp;
    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 &quot;The folder 'name' could not be opened because you do not have sufficient access privileges.&quot; If using the command line to attempt to navigate, this alert may appear:&nbsp;&quot;Permission denied.&quot;
    
    &nbsp;
    Scenario 3:&nbsp;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.
    
    
    
]]></content:encoded>
	<pubDate>Tue, 26 May 2009 13:24:44 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2742</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan, multimedia apps: Troubleshooting dropped frame issues]]></title>
	<description>Release date: Mon, 11 May 2009 15:32:00 GMT</description>
	<link>http://support.apple.com/kb/TS2741</link>
	<content:encoded><![CDATA[Learn how to troubleshoot situations in which dropped frames occur when video is stored via Xsan media. &quot;Dropped frames&quot; refers to frames of video that are unintentionally skipped during capture, editing, or playout.]]></content:encoded>
	<pubDate>Wed, 13 May 2009 18:51:32 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2741</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2.1.1: Xsan Admin cannot save SAN document]]></title>
	<description>Release date: Thu, 05 Mar 2009 20:59:00 GMT</description>
	<link>http://support.apple.com/kb/TS2641</link>
	<content:encoded><![CDATA[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.&nbsp; If you set up a new SAN, you may not be able to create a configuration document.&nbsp; Xsan Admin will present the SAN Setup assistant each time you open it.&nbsp;]]></content:encoded>
	<pubDate>Tue, 05 May 2009 14:49:49 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2641</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 2: Xsan Admin Setup Assistant appears when opening Xsan Admin]]></title>
	<description>Release date: Tue, 24 Feb 2009 22:14:00 GMT</description>
	<link>http://support.apple.com/kb/HT3461</link>
	<content:encoded><![CDATA[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.]]></content:encoded>
	<pubDate>Wed, 22 Apr 2009 20:45:38 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3461</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: How to automount StorNext volumes]]></title>
	<description>Release date: Thu, 19 Feb 2009 21:48:00 GMT</description>
	<link>http://support.apple.com/kb/HT3453</link>
	<content:encoded><![CDATA[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.]]></content:encoded>
	<pubDate>Tue, 03 Mar 2009 18:39:47 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3453</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan Tuner: Results from Final Cut Tasks may be unreliable on Intel-based Macs]]></title>
	<description>Release date: Wed, 14 Jan 2009 17:20:00 GMT</description>
	<link>http://support.apple.com/kb/TS2522</link>
	<content:encoded><![CDATA[On Intel-based Macs, results from Xsan Tuner's Final Cut Tasks may be unreliable.]]></content:encoded>
	<pubDate>Thu, 15 Jan 2009 22:49:05 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2522</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Managing video production workflow in relation to Xsan Volume bandwidth]]></title>
	<description>Release date: Thu, 14 Aug 2008 16:08:00 GMT</description>
	<link>http://support.apple.com/kb/HT2770</link>
	<content:encoded><![CDATA[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&rsquo;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.]]></content:encoded>
	<pubDate>Thu, 08 Jan 2009 18:36:44 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT2770</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Troubleshooting Xsan volume failover issues]]></title>
	<description>Release date: Mon, 17 Nov 2008 23:00:00 GMT</description>
	<link>http://support.apple.com/kb/HT3315</link>
	<content:encoded><![CDATA[What is &quot;volume failover&quot;?
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 &quot;failover.&quot;
Understanding failover-related communications:
While configuring Xsan, one designates over which subnet Xsan metadata communication will occur.&nbsp; 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 &gt; Computers. Inspect the settings for each MDC. Observe the &lsquo;Access the SAN via&rsquo; 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.
&nbsp;
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.]]></content:encoded>
	<pubDate>Mon, 08 Dec 2008 22:57:01 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3315</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[ 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]]></title>
	<description>Release date: Mon, 06 Oct 2008 15:59:00 GMT</description>
	<link>http://support.apple.com/kb/TS2386</link>
	<content:encoded><![CDATA[When using the Mac OS X Server version 10.5 Server Assistant, if one assigns the role &quot;Xsan Metadata Controller&quot; and then chooses to connect to an existing Directory Domain, Directory Utility&rsquo;s LDAPv3 plugin may not be configured as expected.]]></content:encoded>
	<pubDate>Wed, 03 Dec 2008 15:07:20 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2386</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Can't change role of Xsan client to metadata controller]]></title>
	<description>Release date: Tue, 04 Nov 2008 23:48:00 GMT</description>
	<link>http://support.apple.com/kb/TS2431</link>
	<content:encoded><![CDATA[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).]]></content:encoded>
	<pubDate>Tue, 02 Dec 2008 19:42:54 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2431</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan 1.4 or earlier: All controllers must be online when making SAN configuration changes]]></title>
	<description>Release date: Tue, 08 Jul 2008 17:17:00 GMT</description>
	<link>http://support.apple.com/kb/HT2308</link>
	<content:encoded><![CDATA[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.]]></content:encoded>
	<pubDate>Thu, 20 Nov 2008 19:39:21 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT2308</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[Xsan: Only Xsan and Open Directory services should be hosted on Xsan Metadata Controllers]]></title>
	<description>Release date: Fri, 31 Oct 2008 19:22:00 GMT</description>
	<link>http://support.apple.com/kb/TS2428</link>
	<content:encoded><![CDATA[Metadata controller performance may degrade when hosting additional services such as AFP, SMB, NFS, Mail, Netboot, and so on.]]></content:encoded>
	<pubDate>Wed, 19 Nov 2008 21:53:41 GMT</pubDate>
	<guid>http://support.apple.com/kb/TS2428</guid>
	</item>






	
	
	
	
	
	
	
	<item>
	<title><![CDATA[ Xsan 1.4.2 or later: Unmounted Xsan volume re-mounts automatically]]></title>
	<description>Release date: Thu, 13 Nov 2008 20:19:00 GMT</description>
	<link>http://support.apple.com/kb/HT3308</link>
	<content:encoded><![CDATA[An Xsan volume may re-mount (become available) after unmounted or ejected via the Finder or the command line.]]></content:encoded>
	<pubDate>Thu, 13 Nov 2008 20:32:01 GMT</pubDate>
	<guid>http://support.apple.com/kb/HT3308</guid>
	</item>




</channel>
</rss>


