Xsan client/server OS mismatch

Discussion in 'Mac OS X Server, Xserve, and Networking' started by ytk, Oct 11, 2010.

  1. ytk macrumors regular

    Jul 8, 2010
    I want to connect a 2010 Mac Pro to an Xsan network, but this is proving somewhat frustrating as the Xserve running the Xsan metadata controller is still on 10.5, but the new Macs won't boot anything but 10.6. The documentation for Xsan seems very specific that the MDC must be running the same or higher version of both the Xsan software and the OS in order to work properly. Unfortunately, upgrading the Xserve is not an option at the current time. The version of the Xsan software can match, but there's no way to get the OS versions to match.

    That being said, I know somebody who has tried this configuration, running 10.6 on a client for a 10.5 server, and he said it seemed to work fine. So what's the worst that could happen? Assuming I manage to get it to connect, am I asking for trouble down the line? Is there somebody out there who can relate a tale of woe resulting from not following Apple's seemingly pedantic requirements to the letter?
  2. calimedic911 macrumors newbie

    Nov 23, 2010
    usually the manufacturers recomendations are for support purposes only. that way they only have to train their support techs on the most current spec instead of all of the permeatations out there.
  3. logandzwon, Feb 18, 2011
    Last edited: Feb 18, 2011

    logandzwon macrumors 6502a

    Jan 9, 2007
    As long your Xsan software is all on the same version it should be fine. You should update your MDCs though. Or upgrade to a set of these; http://activestorage.com/activesan.php and reuse your xsans for something else.

    After a little more reading... It seems Apple really frowns on having a client at a newer OS level then the controller. I don't think it's a Xsan problem, I think it has to do with permissions. Newer OS X (10.5 and 10.6) support ACLs, 10.4 doesn't.

    I did once have a set-up where I have 10.5 and 10.4 on the same 10.4 meta data controller, all under XSAN 1.4.2, however it was temporary during a migration.

Share This Page