When it's time to failover to the secondary database, so that it becomes our primary database, here are a few things that are usually done:

·if possible, back up the transaction log on the primary database

·apply all outstanding transaction logs to the secondary database after careful consideration.  You may not want to restore all the transactions, if the reason you are failing over is because some unwanted transactions were performed on the primary database.  In these cases, you would want to restore to a point-in-time just before these transactions were committed.

·run a final restore with recovery on the secondary database e.g.

RESTORE DATABASE AdventureWorks WITH RECOVERY

·point your users to the new primary database

·set up log shipping again as part of your disaster recovery plan