There is nothing built into DP for SQL that does that, but I am still trying to understand what the issue is. If you have an automated schedule to back up ALL databases (*) that are active on any given SQL Server instance, it will find that the Principal database is running on the second instance, and back it up from there.
Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[email protected]> wrote on 11/13/2007 10:07:25 AM: > Hi Del! > I just spoke with the SQL guy and his question is a little bit more > clear to me now. > The database is running on the Principal and a copy is running on the > Mirror. > The database is backed up on the Principal. After a take-over the Mirror > becomes the new Principal, so the backup should be backed up on another > physical Windows node. > The only one who knows about the take-over is the Witness, so for the > backup application to know on which Windows node to execute the backup, > he should talk to the Witness. > My SQL guy actually wants to know how he can assure that the backup > continues on the other node after a take-over. > Thanks again in advance for you reply!!! > Kindest regards, > Eric van Loon > KLM Royal Dutch Airlines >
