Home

Failover

Prev Page Next Page
Introduction
Recovery models
Main backup types
Backing up the database files by copying
The transaction log
Transaction log restore sequence
Log sequence numbers
Truncating and shrinking the transaction log
Backing up the tail
Inside the transaction log
So, what's in a backup file?
Test: A full backup does not contain deleted data
Verifying backup files
Verifying backup files on a budget
Cumulative backups
Recovering individual tables
Backup and restore history details
Backup reads and writes
Speeding up backups
Backup speed details
Speeding up restores
Restore state affects speed too
Backup and restore rights
Log shipping
Log shipping in SQL Server 2000
Setting up log shipping using Enterprise Manager
Checking the set up
Failover
Log shipping in SQL Server 2005
Setting up log shipping using Management Studio
Checking the set up
Log shipping status report
Failover
Log shipping in SQL Backup
Using the CopyTool utility
Failover
3rd party backup applications
VDI
VDI versions
VDI errors
SQL Backup - beyond compression
Restoring a chain of transaction log backups
Restoring to the latest possible state
Backing up multiple databases
Backup retention
Making a copy of the backup file
Backup file naming conventions
Restoring the latest backup set
Network resilience
Encryption
Integrated database verification
Database file relocation
Improved backup retention
RESTORE HELP
High-availability group support
Common SQL Backup issues
Installation checklist
Setting up rights
Configuring service rights
Backup data
Hanging issues
Common backup and restore errors
Error 3201 - when performing a backup to a network share
Full database backup file is larger than database size
Error 3205 - Too many backup devices specified for backup or restore
Error 4305 - an earlier transaction log backup is required
Bringing a database that is in recovery or read-only mode online
Using bulk-logged recovery model but transaction log backup is still large
Error 14274 - unable to delete SQL Server Agent job
Error messages when restoring from different versions of SQL Server.
Pending
vdi error codes
Restore speed details
Help, my transaction log file is huge!
Mirror or log ship



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 those 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

You can also use the sp_change_primary_role and sp_change_secondary_role stored procedures to perform the final tasks on the primary and secondary databases respectively.  If you have set up a monitor server too, you can use the sp_change_monitor_role stored procedure to update the log shipping records.  See the Books Online documentation on these stored procedures for further details.

Document history
6/27/2008    Initial release.    
 
Copyright 2008 - 2017 Yohz Ventures Sdn Bhd. All rights reserved.
All product and company names are trademarks or registered trademarks of their respective owners.