Has anyone overcome this failover failure? CSCec63309

benhanson · ‎08-17-2007

I'm just running into this and the tech is suggesting the only fix is to uninstall failover, do a DiRT backup on primary, reinstall Unity on the primary, do a DiRT restore, then re-run the failover config.

This is regarding a bug where Unity won't start on the secondary once the failover config has been run, if the primary was originally upgraded from 3.1(x) to 4.0(x)

Christopher McAlpin · ‎08-17-2007

Failover - Problems when one server upgraded and other new install

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCec48081

benhanson · ‎08-17-2007

Amazing! Thank you very much, I almost wasn't going to post this question!

Ran unitydbex.sql from \CommServer\Localize\DefaultConfiguration\ENU, script threw a few errors saying "xx already exists", ignored them, Unity started right up. Failover monitor shows failover working, I'll test and confirm but looks great!

Thanks again, you just saved me a weekend day of work! TAC was suggesting I reinstall Unity.