Preventing database corruption

Products

• VMware vCenter Server

Issue/Introduction

There is no guaranteed way to prevent data loss. However, the frequency of data loss events and their impact can be greatly reduced by taking proper precautions. A well-rounded approach to data protection has the best chance of avoiding data loss events.

Symptoms:
A SQL database has become corrupted
You need to recover the database
You cannot log in to the vCenter Server

Environment

VMware vCenter Server
VMware vSphere ESXi

Resolution

Successful recovery from database corruption generally requires an effective backup strategy. Without a backup strategy, recovery requires reinstallation of programs and regeneration of data. Even with an effective backup strategy, restoring a system to the precise state it was in prior to the database corruption is extremely difficult.

VMware recommends employing the vendor specific method to recover from a known good backup in the event of a corrupted database.

This assumes that you have backups in the first place, and that they are not corrupt themselves. Often, people want to know how to get a badly corrupted database running again when they do not have a backup. This is not possible without experiencing some form of data loss that may play havoc with your business logic and relational data integrity.

In the event no backup is available, seek advice from the vendor of the database you are using.

Deciding on a backup strategy and setting it up can be complicated. At a minimum, VMware recommends having a regular full-database backup to ensure you have at least one point-in-time to recover from.

Additional Information

For vendor specific information, see:

• Microsoft's SQL Server TechCenter
• Oracle's Support Resources Page