Backup and recovery in sql server database
Download as PPTX, PDF1 like1,589 views
The document discusses the backup and recovery of SQL Server databases, detailing methods for creating full, differential, and transaction log backups. It outlines the process of backing up and restoring databases, emphasizes the importance of backups for data protection against failures, and notes the challenges related to storage space and version compatibility. The conclusion highlights the critical role of database administrators in managing backups and responding to data loss events.
Backup and recovery in sql server database
- 1. SUBMITTED TO- Er. Beena Awasthi SUBMITTED BY- Anshu Maurya (005) Subhi Agnihotri (033) Backup and Recovery of SQL Server Database
- 2. Introduction How to create a full “Database Backup” How to restore from “Backup” Advantages of using Database Backup Drawbacks and Limitations Conclusion
- 3. In SQL Server we can create database backup in 3 ways • Full – creates a complete backups of database as well as part of transaction log, so the database can be recovered. • Differential – a data backup that is based on the latest full backup of a complete or partial database. It contains only those extends that have changed since the last full backup. • Transaction Log – A backup of transaction logs that includes all log records that were not backed up in a previous log backup. It allows us to backup the active part of the transaction log.
- 4. Right click on the database that you want to backup Then, Select "Tasks" and click on "Back Up”.
- 5. Now, Select the Backup type “Full” to create a full database backup and “Add” backup location.
- 6. Give file name and Click “OK”.
- 7. Again, Click on “Ok” to create full database backup.
- 8. • Right click on the database and click on “Restore Database”.
- 12. Protects you from potentially catastrophic data loss. o Backups of a database are useful for routine administrative purposes. 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.
- 13. Due to a full backup of the database, every time space required might develop into an issue. In case of a disaster, recovery is only possible since the last FULL backup. Backups created by more recent versions of SQL server cannot be restored in earlier versions of SQL Server (doesn’t allows downgrading). Database created in lower versions of SQL server takes more time to restore in higher versions due to the upgrade process of database.
- 14. DBA must be prepared for situations where a failure impacts the availability, integrity or usability of a database. Reacting to failures and disruptions is a key component of DBA’s job. The idea of creating a database backup and restoring them when they are needed creates space overhead wherever we save the backup copy. But it has saved many business industries and other organizations from loss of millions or billion dollars.