This discussion is locked
VTmaint
Level 1 (10 points)

Q: Safest way to uninstall XSan? Failover functionality worse with Xsan 1.4.1

I’ve recently updated one MDC to Xsan 1.4.1 from 1.4 in the hope of improving failover functionality.

Long story short, it’s much worse!

Failover is now more or less non-existent (logs indicate the filesystem is in standby rather than active) and when (after much rebooting & starting / stopping of volumes) the 1.4.1 MDC is hosting data throughput is very sticky with lots of spinning beach balls for the FCP clients.

I’d like try reinstalling 1.4.1 before trying anything more drastic –crucially without risking the data stored on the system.

I’m thinking:

1. Entirely isolate the sticky MDC by removing from both fiber & Ethernet networks
2. Backup /Library/Filesystems/Xsan/Config
3. Run 1.4 uninstaller
4. Reinstall 1.4 then 1.4.1 update

Then do I restore my backed up config files, or will the config data be copied from the active MDC when the newly installed machine is promoted to ‘controller’ in Xsan Admin?

If anyone has any advice it would be most welcome!

XServe G5, Mac OS X (10.4.8)

Posted on Nov 20, 2010 8:04 AM

Close
VTmaint

Q: Safest way to uninstall XSan? Failover functionality worse with Xsan 1.4.1

  • All replies
  • Helpful answers

  • by VTmaint,

    VTmaint VTmaint Nov 20, 2010 8:04 AM in response to VTmaint
    Level 1 (10 points)
    Nov 20, 2010 8:04 AM in response to VTmaint
    Did my complete (OS and all!) reinstall, with the config automatically copied from the active controller rather than reinstating from a local backup.

    Performance was still rubbish, and eventually traced to a duff copper fiber cable! Suspect it's been that way for some time, but only revealed itself when forced to fail over as part of the 1.4.1 update.

    Failover now seems transparent, and throughput normal. Time will tell...