Embed Size (px)
Citation preview
Microsoft SQL Server
Backup & Restore Plan
Hamid Jabarpour Fard
SpeakerHamid Jabarpour Fard Consultant/Trainer/Speaker CEO, Fard Solutions Sdn. Bhd.
Email: [email protected] Website: http://www.hfard.com Website: http://www.fard-solutions.com
AgendaWhy do we need to backup and restore plan?Backup and Restore plan considerations.Database Backup BenefitsScenario
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.
Backup and Restore Plan ConsiderationsRecovery 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
Design the Backup and Restore StrategyThe 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?
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?
Database Backup BenefitsProtects 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.
ScenarioFard 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?
Questions and Answers
?
