I am trying to test recovery from a disaster, but feel the SSO part is like a Catch 22 situation. I cannot get it to work.
We have a DB cluster where SSO is also a clustered service, just like the documentation recommends.
I want to be able to recover from a DB/SSO cluster disaster. So the we have a third DB server for log shipping. On that server we also have a “waiting” SSO service to take over as Master. That SSO has joined the current one, but is not Master.
The problem is to make that server the backup server SSO Master.
We cannot run
ssomanage -updatedb NewServer.xml if the old DB is down. We cannot
ssoconfig -restoresecret secret.bak, since it is not the Master.
Has anyone done this and got it to work?