Restoring XSAN Config
Restoring XSAN Config
RESTORE XSAN CONFIG
Here's a summary of the actions you'll want to take:
1. preserve a copy of your volume.cfgp file and fsmlist file from /Library/Preferences/Xsan by copying these to a safe place.
2. export copies of your users using Server.app
3. stop the Xsan volume
4. destroy the LDAP configurations on ODM and ODR by removing the bindings in the OD section.
5. turn off Xsan on both MDCs
6. wipe the files from /Library/Preferences/Xsan on each MDC.
The Xsan should now be unconfigured, but the volume contents are still intact. Now we take actions to rebuild the Xsan membership:
7. Use Server app to configure Xsan on MDC1. Note:
This will establish a new OD master on the primary MDC if it isn't already an OD master.
8. DO NOT CREATE ANY NEW XSAN VOLUMES UNTIL EXISTING VOLUMES HAVE BEEN RESTORED.
Creating new volumes using the old LUNs will destroy old data
9. Restore the existing volume: Copy the old volume config files and fsmlist file back into /Library/Preferences/Xsan. Note that you can use the old .cfg format (ASCII) used in Mavericks and older or the newer .cfgp format (plist) used in Yosemite and newer.
10. Run xsanctl pushConfigUpdate in Terminal to copy the config files you just added into the Xsan configuration stored in LDAP:
$ sudo xsanctl pushConfigUpdate
11. Refresh the view in Server app -> Xsan, your volume should now show up in Server.app
Update Xsan MD Network
$ sudo xsanctl changeip oldIP newIP
13. Start and mount volume on MDC1 using the following commands in Terminal:
$ sudo xsanctl start
$ sudo xsanctl mount
14. Import user accounts back into the new ODM.
15. Re-enter passwords for newly imported users.
16. Enable Xsan on MDC2.
17. Xsan clients will need to delete their existing Xsan profile and use the newly created one.
This should leave you with a newly configured MDC1/ODM, as well as an MDC2/ODR, with your user accounts from before and your Xsan volume with it's pre-existing contents intact.
Here's a summary of the actions you'll want to take:
1. preserve a copy of your volume.cfgp file and fsmlist file from /Library/Preferences/Xsan by copying these to a safe place.
2. export copies of your users using Server.app
3. stop the Xsan volume
4. destroy the LDAP configurations on ODM and ODR by removing the bindings in the OD section.
5. turn off Xsan on both MDCs
6. wipe the files from /Library/Preferences/Xsan on each MDC.
The Xsan should now be unconfigured, but the volume contents are still intact. Now we take actions to rebuild the Xsan membership:
7. Use Server app to configure Xsan on MDC1. Note:
This will establish a new OD master on the primary MDC if it isn't already an OD master.
8. DO NOT CREATE ANY NEW XSAN VOLUMES UNTIL EXISTING VOLUMES HAVE BEEN RESTORED.
Creating new volumes using the old LUNs will destroy old data
9. Restore the existing volume: Copy the old volume config files and fsmlist file back into /Library/Preferences/Xsan. Note that you can use the old .cfg format (ASCII) used in Mavericks and older or the newer .cfgp format (plist) used in Yosemite and newer.
10. Run xsanctl pushConfigUpdate in Terminal to copy the config files you just added into the Xsan configuration stored in LDAP:
$ sudo xsanctl pushConfigUpdate
11. Refresh the view in Server app -> Xsan, your volume should now show up in Server.app
Update Xsan MD Network
$ sudo xsanctl changeip oldIP newIP
13. Start and mount volume on MDC1 using the following commands in Terminal:
$ sudo xsanctl start
$ sudo xsanctl mount
14. Import user accounts back into the new ODM.
15. Re-enter passwords for newly imported users.
16. Enable Xsan on MDC2.
17. Xsan clients will need to delete their existing Xsan profile and use the newly created one.
This should leave you with a newly configured MDC1/ODM, as well as an MDC2/ODR, with your user accounts from before and your Xsan volume with it's pre-existing contents intact.