Scenarios

Failover Operation in Log Shipping:

1) Primary is corrupt and hence we would want to perform Failover. First verify if
it is a suspect situation and if database can be rectified without Failover.

2) Check the possibility of transfering logins from Primary to Standby server. If

entire instance crashes then it would be difficult to transfer logins, hence a
automated job that transfers logins at regular intervals from P-S is a recommended
practice.

3) Disable/Delete all the Log Shipping Jobs. This will stop the log shipping which
is in progress.

4) Verify whether all backups have been moved to Backup share and also copied to
Local Copy or not.

select * from log_shipping_primary_databases

Verify column Last Backup file and timestamp

select * from log_shipping_secondary

select * from log_shipping_secondary_databases
Verify column Last Restored file and timestamp

5) If all backups have been moved and are in sync. Attempt last tail log backup on
the Primary database and copy the file to the Backupshare and Local Copy.

6) Copy job follows a pattern and hence would not copy the file to Local Copy
directory. Restore job restores and verifies each and every file and ensures that
the manual Tail log backup is restored.

7) Restore the standby database WITH RECOVERY.

RESTORE LOG LShip FROM DISK='\\10.10.10.3\BKPShare\LShip_Last.trn' WITH RECOVERY

8) Confirm Application Team about the new IP Address, Instance Name, Port Number,
New database name.

9) Customer will test the application and confirm on the usage.

10) Verify if any Orphan users exist or not.

11) Reconfigure Reverse Log Shipping with Standby as New Primary.

Switchover Operation in Log Shipping:

1) As a part of DR Test (or) upon Customer/Application Team/Client approval switch

over operation is normally performed.

2) Transfer the logins from Primary to Standby server and Vice-Versa.

3) Disable all the Log Shipping Jobs. This will stop the log shipping which is in
progress.

4) Verify whether all backups have been moved to Backup share and also copied to
Local Copy or not.
5) If all backups have been moved and are in sync. Attempt last log backup WITH
NORECOVERY on the Primary database and copy the file to the Backupshare and Local
Copy.

backup log DBName to disk=N'\\Monitor\GaneshaShare\Ganesha_Last.trn' WITH

NORECOVERY

This will set the Primary database to Restoring state to ensure that it will accept
backups from Standby server.

6) Copy job follows a pattern and hence would not copy the file to Local Copy
directory. Restore job restores and verifies each and every file and ensures that
the manual last log backup is restored on the standby server.

7) Restore the standby database WITH RECOVERY. This will make the standby database
ONLINE and it becomes the new Primary.

8) Confirm the customer the new IP Address, Instance Name, Port Number, New
database name.

9) Customer will test the application and confirm on the usage.

10) Verify if any Orphan users exist or not.

10b) Delete existing log shipping configurations using below commands

sp_delete_log_shipping_primary_database LShip
sp_delete_log_shipping_secondary_database LShip_STBY

Query manually all the log_shipping_* tables to verify the old configurations are
deleted or not.

11) Reconfigure Reverse Log Shipping with Old Standby as New Primary and Old
Primary as New Standby.