The first question we ask when performing an audit of an organisations backup and recovery strategy is “Why do you backup?”
The most common answer we get is “Because we have to” which implies that backup is just another box we have to tick and therefore we will just select our data for backup and hope that we can recover it.
The only answer to the question “Why do you backup?” is to RECOVER.
The ability to recover should be the main criteria for choosing a backup product. Our engineers test the recovery of thousands of systems every year. As a result, we know a lot about how to configure your backups to facilitate this recovery. With its large market share, we have found that Backup Exec is the most common product we come across in the market place, but it is also the most reliable when it comes to recovery. More often than not, inability to recover is not the fault of the backup product, but rather how it has been configured by the user. Half of the Backup Exec manual covers restore/recovery, but nobody gets to read it until they have to, at which point it might be too late as they did not configure their backups to facilitate the recovery.
Recovery can be further broken down into the following categories:
- Recovering individual items of data
- Recovering individual systems
- Recovering an entire site.
Lets look at each of these individually.
If this is an area of interest, then let me know and I will send you the rest of the article which covers application agents, archiving, virtualisation agents and system recovery.
(this is an exerpt from a longer article by Lewis McMahon, Storage On-Line)