November 19, 2002 at 10:18 am
In the case of failover from box A to box B, using backup and restore as your failover solution, you restore your last full backup and then restore transaction logs up to the last log dump available. After restoring all the txlogs, (assuming it is available) can you then stop sql on box b, copy the txlog from box a, and put it in the location of the txlog on box b to act as the txlog for that database? The intention is to get the current committed transactions that haven't been backed up yet.
Remember this when a developer tells you it will just be temporary. Temporary = Permanent.
November 19, 2002 at 10:27 am
I'm not sure that copying the txlog from box a to box b get all the committed transactions to box b. Since the transaction have already been comitted on box A, I assume that SQL Server will assume they have already been applied to DATA, and therefore they will never be applied to box b. I have not tested this, I am only guess this.
If you want the latest transaction why not do another transaction log back, and copy that to box b, then restore with recovery? To make this work, your original restores will need to not perform recovery.
Gregory Larsen, DBA
If you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples
Gregory A. Larsen, MVP
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply