Recovery Scenario

Recovery from
Tape Backup

Recovery using

CSFv3 BUDR

Planned server maintenance

No failover option available so major business disruption is experienced while server is offline.

Recovery server can be commissioned in preparation for maintenance window.

No business disruption experienced.

Unplanned server maintenance

No failover option, so business disruption is experienced while server is offline.

Recovery server can be commissioned reactively.

Minimal business disruption required while recovery server is brought online (<4hrs)

Server failure due to component failure (assuming a valid warranty in place)

Requirement to invoke hardware warranty, replace faulty parts, rebuild operating system and reinstall application software and restore backup data.

Significant business disruption due to the time taken to replace parts and re-install software and data. (>2 days)

Recovery server can be commissioned reactively.

Minimal business disruption experienced while recovery server is brought online (<4hrs)

No business disruption while failed server is repaired and rebuilt offline.

No business disruption to switch back to repaired server as this can be planned for a maintenance window.

Multi-server failure due to component failure (assume a valid warranty in place)

Same as above but much longer recover timescale due to multiple systems involved.

Significant business disruption due to the time taken to replace parts and re-install software and data. (>4 days)

Recovery server can be commissioned reactively to support multiple servers simultaneously.

Minimal business disruption experienced while recovery servers are brought online (<1 day)

No business disruption while failed servers are repaired and rebuilt offline.

No business disruption to switch back to repaired servers as this can be planned for a maintenance window.

Server failure damage or loss (warranty not applicable)

Requirement to procure new server hardware, rebuild operating system and reinstall application software, and then restore backup data.

Significant business disruption due to time taken to obtain replacement server and re-install software and data. (>3 days and <3 weeks)

Recovery server can be commissioned reactively.

Minimal business disruption required while recovery server is brought online (<4hrs)

No business disruption while failed server is replaced and rebuilt offline.

Loss of whole building

e.g. Building is damaged or unavailable for access e.g. fire, power failure etc.

Requirement to host some or all servers and services in another building for an extended period.

Requirement to procure new server hardware, rebuild operating system and reinstall application software, and then restore backup data.

Significant business disruption due to time taken to obtain replacement server and re-install software and data. (dependant on access to building in some circumstances e.g. fire, but several weeks likely)

Recovery server can be commissioned reactively to support multiple servers simultaneously.

Users can be directed to work from home and access recovery systems remotely.

Minimal business disruption required while recovery servers are brought online (<1 day) and users are redirected to recovery servers (<2 days).

No business disruption while lost site is re-instated, servers are replaced and rebuilt offline.