Microsoft SQL Server enables you to back up and restore your databases. The SQL Server backup and restore component provides an important safeguard for protecting critical data stored in SQL Server databases. A well-planned backup and restore strategy helps protect databases against data loss caused by a variety of failures. Test your strategy by restoring a set of backups and then recovering your database to prepare you to respond effectively to a disaster.
A copy of data that can be used to restore and recover the data is called a backup. Backups let you restore data after a failure. With good backups, you can recover from many failures, such as:
User errors, for example, dropping a table by mistake.
Hardware failures, for example, a damaged disk drive or permanent loss of a server.
Additionally, backups of a database are useful for routine administrative purposes, such as copying a database from one server to another, setting up database mirroring, and archiving.
Contains information about differential bases, how differential backups work, and how to create the various types of data and differential backups: database backups, partial and differential partial backups, and file and filegroup backups.
Contains information about how SQL Server works with backup devices, using backup media, viewing information about and verifying SQL Server backups, detecting and coping with media errors, and using mirrored backup media sets.
Contains an introduction to restore scenarios as they are supported under the simple recovery model and the full/bulk-logged recovery models, as well as a description of how restore and backup recovery work, and overviews of the restore system tables and the RESTORE statement.
Contains an introduction to the basic concepts of restoring and recovering backups and how they work, a brief overview of restore operations, and information about how to implement the various restore scenarios.
Contains information about how to combine multiple RESTORE statements to restore a sequence of backups from a single database and recover the database. Provides information about what occurs when files or file groups have been added, dropped, or have had their names changed since they were backed up, and also describes optimizations that can be used to minimize or eliminate unnecessary rolling forward during a file restore operation.
Describes how to use marked transactions in two or more related, full-recovery model databases that must be kept logically consistent. By creating marked transactions, you can retain consistent between them during restore and recovery.