October 22, 2013 at 12:11 pm
Hi we have dr drill schedule in upcoming week and they are going to carry out it atleast for a day.After switch over they are going to make updates insert delete in secondary servers.so should i configured reverse log shipping is it possible?
Second thing after task is over, is it possible that i take tail log backup from secondary and apply it to primary so as bring both dr and primary server in synch.
would there be any issues.
Third when primary becomes avaliable is it possible to switch back i mean would tail log bkp can be again applied to secondary again.
October 24, 2013 at 2:38 am
If it is in DR Test / Drill :
You need to failover to the Secondary / Target / DR instances & Databases and validate the Status.
Once the DR Test is done you need to switch over back.
Cluster - switch the nodes A to B or vice versa.
Mirroring - Failover to Mirrored DB and once DR test is done, again fail back to normal.
Log shipping - Manuall failover, test and then reconfigure back to normal. IF updates are done on Secondary the logs (check lsn) should be applied.
Replication - Manual failover, need to reconfigure. Stop and reconfigure.
for understanding, reference - http://www.sqlserver-training.com/10-sql-server-disaster-recovery-solutions/-
----------------------------------------------------------------------------------------
Reversing log shipping is simple. It doesn’t require reinitializing the database with a full backup if performed carefully. However, it’s crucial that you remember the following:
?You need to preserve the log sequence number (LSN) chain.
?You need to perform the final log backup using the NORECOVERY option. Backing up the log with this option puts the database in a state that allows log backups to be restored and ensures that the database’s LSN chain doesn’t deviate.
?The primary log shipping server must still be accessible to use this technique.
?To fail over to a secondary log shipping server, follow this 10-step process:
?Disable all backup jobs that might back up the database on both log shipping partners.
?Disable the log shipping jobs.
?Run each log shipping job in order (i.e., backup, copy, and restore).
?Drop log shipping.
?Manually back up the log of the primary database using the NORECOVERY option. Use the command
?BACKUP LOG [DatabaseName]
?TO DISK = 'BackupFilePathname'
?WITH NORECOVERY;
?where DatabaseName is the name of the database whose log you want to back up and BackupFilePathname is the backup file’s pathname (e.g., Z:\SQLServerBackups\TLog.bck).
?Restore the log backup on the secondary database using the RECOVERY option, and bring the secondary database online. The primary and secondary databases have now switched positions.
?Back up the log of the new primary database (optional).
?Restore the log on the new secondary database using the NORECOVERY option (optional).
?Reconfigure log shipping.
?Re-enable any backup jobs that were disabled.
?Note that step 7 and step 8 are listed as optional because they’re not required for establishing log shipping. However, I recommend performing these steps to ensure that the log shipping configuration will proceed without any problems.
Cheers,
- Win
"Dont Judge a Book by its Cover"
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply