SQL Server Database Backup and Restore Plan
Download as PPTX, PDF3 likes1,900 views
The document outlines the importance of a backup and restore plan for Microsoft SQL Server, highlighting statistics indicating that many businesses fail to recover from data loss without such plans. It discusses considerations like recovery time and point objectives, and the optimal design strategies based on database usage and potential risks. Additionally, it emphasizes the benefits of backups in protecting against data loss from various failures and includes a specific scenario for implementing a recovery solution.
SQL Server Database Backup and Restore Plan
- 1. Microsoft SQL Server Backup & Restore Plan Hamid Jabarpour Fard
- 2. Speaker Hamid Jabarpour Fard Consultant/Trainer/Speaker CEO, Fard Solutions Sdn. Bhd. Email: [email protected] Website: http://www.hfard.com Website: http://www.fard-solutions.com
- 3. Agenda Why do we need to backup and restore plan? Backup and Restore plan considerations. Database Backup Benefits Scenario
- 4. Why do we need to have backup and restore plan? Based on statistics: 90% of businesses losing data from a disaster are forced to shut down within two years. The survival rate for companies without a disaster recovery plan is less than 10%. Only 44% of businesses successfully recovered information after a recent data recovery event. 53% of claimants never recoup the losses incurred by a disaster.
- 5. Backup and Restore Plan Considerations Recovery Time Objective: How long would you like to spend on database recovery after the corruption. Recover Point Objective: At which point would you like to stop recovery operation after the corruption. Time Last Backup Corruption Recovery RPO RTO
- 6. Design the Backup and Restore Strategy The optimal strategy depends on a variety of factors, of which the following are especially significant: How many hours a day do applications have to access the database? How frequently are changes and updates likely to occur? Are changes likely to occur in only a small part of the database or in a large part of the database? How much disk space will a full database backup require?
- 7. Design the Backup and Restore Strategy (Cont.) How do you prefer to restore the database? Does your application access to a part of database? Do you need to stop recovery on specific time or transaction?
- 8. Database Backup Benefits Protects you from potentially catastrophic data loss. With valid backups of a database, you can recover your data from many failures, such as: Media failure. User errors, for example, dropping a table by mistake. Hardware failures, for example, a damaged disk drive or permanent loss of a server. Natural disasters. backups of a database are useful for routine administrative purposes Note: This is the only way to reliably protect your SQL Server data.
- 9. Scenario Fard Solutions Sdn. Bhd. has a SQL Server 2008 R2 instance, named “SQL01”. SQL01 has few databases which one of that is for Finance department which called “FinanceDB”. FinanceDB contains 125 tables and indexed views which 25 of them are having a transaction per second. The IT management requirement is to access at least these 25 tables as soon as possible after any database corruption and the data loss should be less than 15 seconds. What is your solution?
Editor's Notes
- #5: sys.dm_os_schedulers: Returns one row per scheduler (there is one user scheduler per core) and shows information on scheduler load and health. See Chapters 3 and 5 for more information.sys.dm_os_waiting_tasks: Returns one row for every executing task that is currently waiting for a resource as well as the wait type. See Chapter 3 for more information.sys.dm_os_memory_clerks: Memory clerks are used by SQL Server to allocate memory. Significant components within SQL Server have their own memory clerk. This DMV shows all the memory clerks and how much memory each one is using. See Chapter 2 for more information.
- #6: sys.dm_os_schedulers: Returns one row per scheduler (there is one user scheduler per core) and shows information on scheduler load and health. See Chapters 3 and 5 for more information.sys.dm_os_waiting_tasks: Returns one row for every executing task that is currently waiting for a resource as well as the wait type. See Chapter 3 for more information.sys.dm_os_memory_clerks: Memory clerks are used by SQL Server to allocate memory. Significant components within SQL Server have their own memory clerk. This DMV shows all the memory clerks and how much memory each one is using. See Chapter 2 for more information.
- #7: sys.dm_os_schedulers: Returns one row per scheduler (there is one user scheduler per core) and shows information on scheduler load and health. See Chapters 3 and 5 for more information.sys.dm_os_waiting_tasks: Returns one row for every executing task that is currently waiting for a resource as well as the wait type. See Chapter 3 for more information.sys.dm_os_memory_clerks: Memory clerks are used by SQL Server to allocate memory. Significant components within SQL Server have their own memory clerk. This DMV shows all the memory clerks and how much memory each one is using. See Chapter 2 for more information.
- #8: sys.dm_os_schedulers: Returns one row per scheduler (there is one user scheduler per core) and shows information on scheduler load and health. See Chapters 3 and 5 for more information.sys.dm_os_waiting_tasks: Returns one row for every executing task that is currently waiting for a resource as well as the wait type. See Chapter 3 for more information.sys.dm_os_memory_clerks: Memory clerks are used by SQL Server to allocate memory. Significant components within SQL Server have their own memory clerk. This DMV shows all the memory clerks and how much memory each one is using. See Chapter 2 for more information.
- #9: sys.dm_os_schedulers: Returns one row per scheduler (there is one user scheduler per core) and shows information on scheduler load and health. See Chapters 3 and 5 for more information.sys.dm_os_waiting_tasks: Returns one row for every executing task that is currently waiting for a resource as well as the wait type. See Chapter 3 for more information.sys.dm_os_memory_clerks: Memory clerks are used by SQL Server to allocate memory. Significant components within SQL Server have their own memory clerk. This DMV shows all the memory clerks and how much memory each one is using. See Chapter 2 for more information.
- #10: sys.dm_os_schedulers: Returns one row per scheduler (there is one user scheduler per core) and shows information on scheduler load and health. See Chapters 3 and 5 for more information.sys.dm_os_waiting_tasks: Returns one row for every executing task that is currently waiting for a resource as well as the wait type. See Chapter 3 for more information.sys.dm_os_memory_clerks: Memory clerks are used by SQL Server to allocate memory. Significant components within SQL Server have their own memory clerk. This DMV shows all the memory clerks and how much memory each one is using. See Chapter 2 for more information.