I'm upgrading my xSAN to mountain lion from 10.6.8. I'd like to stop using OpenDirectory on my controllers. I have my clients connected to my "real" open directory server and everything seems to work ok except I have warnings in xsan admin showing incorrect search policy. If I demote the mdc replica to standalone, xsan admin complains that it is not a replica. When I demote the mdc master to standalone OD, or connected to a OD, xSAN admin says it should be a OD master.
Is it possible to undue the original configuration to use OD? Or should I just leave it as configured and ignore the warnings?
I've been trying to backup a Xsan 4 Volume (10.10.2) on promise vtrak E610F with no luck .
once I've been trying host the Time Machine backup drive on OS X Server 10.0.2 and use it on one of the Xsans' clients .
every time the backup finishes , the client is trying to backup the all Xsan volume again and no incremental with an error message "Backup volume is out of space , find another place to backup to... "
alternatively , I've tried to connect the backup Volume and run the backup direct from there ,
but again it's not backup it incrementally , and running out of space after it's first backup .
am I missing something about xsan4 compatibility ?
I have roughly 100TB on xsan, and would like to backup this data onto another san. I'm wondering if there are software out there that does good compression with video files. Allocating another 100TB would be so costly, son wondering how does every backup their data.
Submitted by Apple Knowledge Base on Mon, 03/02/2015 - 1:32pm
Xsan may need to be enabled on OS X Lion clients that were migrated from Mac OS X v10.6 via the Migration Assistant. A migrated system may show fsmpm's status as not running, or may show the computer as unreachable or offline in Xsan Admin on another system such as the metadata controller.
Submitted by Apple Knowledge Base on Tue, 02/24/2015 - 4:39pm
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.