Database Design And Recovery{1}

by Ming X
The article I read is called Database Recovery Options, by Lockwood Lyon. The backups of application data are very important and sufficient for any recovery needs. There should be a recovery strategy applied from the beginning, starting with database design. The author mentions that there are two things database designer must know; the recovery time objective (how long can the application data (or portions of the data) be unavailable?) and the recovery point objective (to what point must data be recovered? To a specific date/time? To the end of the most recently completed transaction?). It’s not only the database design that needs to consider recovery needs; applications that access the data must also be designed with recovery in mind. And at last, there should be a the infrastructure team supporting them. The author also mentions several database backup options for recovery; including database unloads, database full image copies, hot standby and Disk mirroring.

In a perfect world we would never have to worry about our computers failing, nor would we have to worry about natural disaster. But we don’t live in a perfect world so data backup and recovery is very important. Although many database systems these days incorporate tools for database backup and recovery in their infrastructure and interfaces, it is wise to know what the entire backup and recovery process entails. With growing volumes of both personal and organizational information, there is certainly a need for safe backup and recovery.

Especially for organizations; if a database crashes and there is no plan of recovering it, the outcome can be very devastating as this can amount to data loss, revenue loss and dissatisfaction to clients. Whether an organization is small or big, backing up essential data is of great importance. Database backups are essential to the day to day functions of a company. Here is a major reason why we need to backup regularly; if you work for a company, and you don’t backup your database, you could be fired or face some other serious career problem. I found something interesting, if you Google “fired because of no database backup”, it returns 10,700,000 results; some of them go into detail.



Lyon, Lockwood: Database Recovery Options, Database Journal, 10/22/2012