Backup in the company: Restore tests without errors

Regular restore tests are the be-all and end-all of data backup.

When the subject of backups is raised in companies, most managers feel well prepared. The importance of data backup is not in doubt, and the protocols for carrying out regular backups are correspondingly sophisticated. But when it comes to recovery, there is often a lack of understanding. Very few companies think about the recovery process. It is assumed that data backup is the most important step. However, this is wrong, because the aim of every backup is ultimately to restore the data in the event of an emergency. However, a successful backup and a successful recovery are by no means the same thing.

The backup is only half the battle

As companies have to expect serious losses and difficulties if a data loss occurs, great efforts are invested in a conscientious and regular backup. However, backing up data is only half the battle. The test of a recovery is usually omitted due to time constraints. People rely on the fact that a recovery will somehow succeed thanks to regular data backups. In fact, companies are usually able to reconstruct their data from any existing backup source. However, if the most recent backup is damaged, the only option is to fall back on older data that is no longer up-to-date. Depending on the industry, it can make a big difference whether you can restore yesterday's data or have to fall back on last week's data. There are industries in which restoring to the previous day's status can lead to losses and losses because the data stocks change hourly.

Plan restore tests conscientiously

It is not enough to rely solely on the conscientious execution of backups. The reason for not carrying out restore tests is almost always the same: Lack of time or lack of specialized personnel. While each department carries out its backups according to fixed schedules, there is no room for the most important step, the recovery test? This is a strategy that can take revenge the next time data is lost. The management of every company should be aware of this problem and take appropriate precautions. "Backup tests should be established as a process in companies," says Marcel Binder from BIG IT Systems GmbH, because recovery must not be neglected. The first step is to check the requirements for recovery. Very few companies think about how quickly a restore needs to be implemented in the event of a crisis.

Simple checklist helps with the recovery test

The solution to the problem is as simple as it is compelling: in the same way that backup plans and the associated protocols are developed, a company must also develop a recovery plan. This includes the random recovery of data from the most recent restore inventory. The personnel responsible for the recovery should regularly work through a data backup checklist in which the performance of the recovery test is logged and any errors that have occurred are recorded. The minimum requirement for this should be a check of the backup logs of the current backup and a random recovery test. As a simple aid for our readers, we have developed a corresponding checklist, which you can download at the end of the article. It is important to carry out the restore test just as regularly and conscientiously as the backup itself. After all, copies of data that cannot be restored are of little use in an emergency.

Documents:

Backup checklist