Implementation Training Who’s involved in the process? Testing Failsafe your process Remember what the purpose of backups are!
Backing up your data Data Files .MDF .LDF Backup Devices Create Delete
Recovery Models Simple Most restrictive model. Can’t complete transaction log backups. Good if you only want to recover to your last full backup. Bulked Log Ability to recover to the end of a full backup or the end of a transaction log. Lose the ability to restore to a specific point in time. Full Allows full, differential, transaction log and filegroup recoveries. Provides the highest level of data protection. Point in time restores.
Types of Backups Full Database Differential Database Transaction Log Filegroup
Full database backup Completes a full backup up the database right up to the point where the database finishes. Backs up all tables, indexes, system tables and the database object in those tables Striping example
Differential Backup Creates a backup of the changes made to the database since the last full backup Does not keep track of individual transactions so it does not provide the ability to restore to a point in time
The Transaction Log The transaction log keeps a log of each transaction giving a DBA the ability roll forward or roll back to a specific point. When the transaction log is backed up the log is truncated. Transaction log backups are scheduled in intervals typically 5 to 30 minutes. Backs up the transactions since the last Full Backup, Differential Backup or Transaction Log Backup.
Filegroups Allow a user to place tables, indexes and other database objects into specific database files. Can be backed up and restored individually or in groups. Useful when time restraints prevent full backups.
Verifying the Backup Does not check the consistency of the database (i.e. DBCC CHECKDATABASE). Verifies the integrity of the database backup and checks for corruption. Makes sure all the data in the backup set is readable.
Job Scheduling The most widely used way complete day to day and week to week scheduled backup operations. Creation of jobs though Enterprise Manager. SQL Server Agent must be started.
Database Maintenance Plans Expanded job scheduling abilities. Creates jobs managed by the SQL Server Agent. Can schedule integrity checks, reorganize indexes and delete unwanted database backups.
Storage Using a consistent method of keeping track of your backups. Using the system backup tables in the msdb database. Archiving backups to tape and different considerations for different industries
Restore scenarios Data Migration Development Testing Disaster Recovery Recovering Backups Standby Servers
Restore Basics Make sure you are using the correct backup set. RESTORE LABELONLY: summarizes information about the backup set. RESTORE HEADERONLY: returns information about each item in the backup set including the order in which the backups were made. RESTORE FILELISTONLY: returns the associated data files in relation to a specific backup device.
Point in Time Restore andRestore to Mark Allows user to restore to a point before a failure or corrupt data Allows user to restore without unwanted data STOPATMARK: Transactions can be ‘marked’ so that a restore can take you up to that marked transaction. STOPBEFOREMARK: Restores can also restore up to but not including that mark.
Restoring Filegroups Restored by restoring the specified filegroups and applying a previous log and the next transaction log to bring the database to a consistent state.
Using a Backup to Create aNew DatabaseA new database can be created by using the backup from an existing database. This is made possible by using the ‘with move’ statement which copies the data files and applies them to the new database.
Consistency in Backing Up theSystem Databases Itis important to consistently backup up the master database and the msdb databases. In a restore scenario the master database should be restored first and the msdb database should be restore next followed by the model. The user databases should be restored last.