Not sure why this posted twice and in such an odd format! We progressed from this situation
and asked another question ("Is it possible to set a null password for your DB user?") on the forum
and have recieved assistance on this. Just thought I'd better post an 'answer' here as it seems to be
getting lots of views.
Basically, I shouldn't have used the srvbuildres tool for the DR scenario, I should have just removed
the master.dat file; CommVault does all the 'clever' restore bits itself in the background, including
running the dataserver command (similar to srvbuildres) to rebuild the necessary files. Having it in
this inconsistent state meant CommVault couldn't connect.
The connection in CommVault should remain as the 'sapsa' user and password; when it rebuilds
master it KNOWS that by default only a sa account exists with a null password and it is able to
connect in the background.
The database should be down; you shouldn't start it in single user mode. CommVault does what it
needs to do in the background.