Alternatively, is it possible to delete the /Library/Preferences/Xsan, create a new volume, and then replace it with my existing. I'm not sure, but I'm assuming if I recreate the volume fresh it will destroy the data. Has anyone else had this issue and do you know of a way to get Server app to recognize that the volume is present and mounted. I've since deleted the config files on the other clients with the plan of installing the new config files after I fixed the open directory issue. So, the volume mounted on the primary MDC and it mounts successfully on one other machine that has an old config file. It shows the connection as active, but shows that no volumes are configured, and also shows no servers. When I turned Xsan back on in Server app, the SAN volume mounted on the primary MDC, but the all of the data in the Server app is blank. I had to destroy and recreate my open directory config on my primary MDC (I did archive everything). ![]() In any case, failover to my backup MDC was not working properly and I could not successfully add new profiles to clients as it would not authenticate. I've been having issues with my open directory settings in that I was unable to make any changes, I believe something became corrupted in some way. ![]() More info when I test some more and upgrade clients out in the real world. I have not tested Xsan 4 with StorNext but I expect there is compatibility, as usual. To configure the clients you export a config profile and install it on the clients, or enrol the Xsan controller in MDM (Profile Manager, for example) and push out the config to the clients. Therefore, join your Xsan controller to your OD or risk creating a new master OD. If there is no OD set up then it will create one (same with DNS). Also, it depends on Open Directory (and DNS of course). I’ve done some basic testing with Xsan 4 and it does away with the Xsan Admin app, all setup is done in the Server.app. Officially, you can NOT have Xsan 3 (10.9) clients on a 10.10 Xsan, and, vice versa, 10.10 (Xsan 4) clients will not work on a Xsan 3 based SAN. If you upgrade your Mac to 10.10 then it is incompatible with Xsan 3. There are some changes to how to set up Xsan and compatibility between versions of OS X and Xsan.
0 Comments
Leave a Reply. |