SQL Tutorial: SQL Server Backup and disaster recovery

SQL Server backup and disaster recovery

The data processing becomes more and more important in the modern enterprise operation, more and more crucial, may even become the enterprise development bottleneck. The importance of data protection is self-evident. If an enterprise does not have a good data protection program or strategy, once the important data loss, the consequences will be disastrous, along with the loss of economic benefits.

The major server hardware vendors (IBM,HP, etc.) provide good data protection policies (hardware or software). A well known RAID disk array (redundant array of independent disks) is a good way to protect data. In the case of SQL Server , a detailed data backup plan can be developed through a maintenance plan.

Data backup strategy (full backup, differential backup and transaction log backup)

Data backups are services for data recovery, so before you set up a data backup plan, consider whether you can take advantage of the backup's valid recovery data (within the time allowed by downtime). You should also consider the RPO allowed by the system (Recovery point objective, after a disaster occurs, The point at which the system or data must be recovered, RTO (Recovery time objective), which is how long it takes to restore the system or data to a functioning state when a system recovery tool or solution is used after a disaster occurs.

There are three commonly used backup schedules:

(1). Only full backup

The time period between two full backups fails and the data is lost and can only be recovered to the last fully backed up data.