Home > E-Database Recovery Strategies

An error can occur in an entire database object such as a table, data space, or table space becoming corrupted. This type of problem can be recovered by using the e-Database Recovery Strategy. The e-Database Recovery Strategy can recover application error, or a problem with the actual file used by the database object. More severe errors can impact multiple database objects, or even worse, an entire database. Sometimes small data integrity problems can be more difficult to eradicate than more massive problems. However, problems that impact a larger percentage of data are likely to be identified much earlier. In general, the earlier an error is found, the more recovery options available to the e-Database Recovery Strategy and the easier it is to correct the data.

A database recovery strategy must plan for different types of recovery. The disaster could be anything from a simple media failure to a natural disaster destroying your data center. Applications may be completely unavailable until the recovery is complete. There are many levels of RAID technology and, depending on the level in use, different degrees of fault-tolerance that are supported. For more details on RAID, please see the accompanying sidebar. Another desirable aspect of RAID arrays is the ability to use hot swappable drives so the array does not have to be powered down to replace a failed drive. Instead, a drive can be replaced while the array is up and running - and that is a good thing for eDBAs because it enhances overall data availability.

A disaster that takes out your data center is the worst of all possible situations and will definitely result in an outage of some considerable length. The length of the outage will depend greatly on the processes in place to send database copies and database logs to an off-site location. Overall downtime for a disaster also depends a good deal on how comprehensive and automated your recovery procedures are at the remote site. The e-Database Recovery Strategy should be prepared with automated procedures for handling a disaster. But simple automation is insufficient. The e-Database Recovery Strategy must ensure the consistent backup and offsite routing of not just all of the required data, but also the IT infrastructure resources required to bring up the organization's databases at the remote site.

Conventional techniques to perform a point-in-time data recovery will remove the effects of all transactions performed since a specified point in time. The traditional approach will involve an outage. Steps for PIT recovery include: Identifying the point in time to which the database should be recovered. Depending on the DBMS being used, this can be to an actual time, an offset on the database log, or to a specific image copy backup (or set of backups). Care must be taken to ensure that the PIT selected for recovery will provide data integrity, not just for the database object impacted, but for all related database objects as well. The database objects must be taken off-line while the recovery process applies the image copy backups. When complete, the database objects can be brought back online. For the e-business, this type of tool can pay for itself after a single usage if it significantly reduces an outage and enables the e-business application to come back online quickly.

Data Recovery Software - RAID Recovery

More Information
Cause for Data Loss
Disaster Planning
Disaster Level
Business Continuity Planning
Surveying a hard disk?
Network Security Policies
Security Audit
Computer Security Policies
e-Security Toolkit
Plan Assurance
Business Impact Analysis
Disaster Recovery Plan
Disaster Recovery Toolkit
Disaster Recovery Policies
Business Continuity Plan
Risk Analysis
Disaster Assistance
Disaster Recovery Training
Novell Data Recovery
Macintosh Data Recovery
Linux Data Recovery
RAID Recovery
E-mail Recovery
Logical Data Error Recovery
Corruption Recovery Tools

Related Information
File Recovery
Data Recovery USA
DLT Tape Drive
Hard Disk Recovery
RAID Controller