Backup / Restore

Owned by Bernhard Wolkerstorfer (Unlicensed)
Last updated: Apr 11, 2016
1 min read

The eRecruiter requires a backup and restore concept to avoid data loss in case of a critical system failure. The following documentation can be used as a draft to create a company-specific concept.

Database

The backup of the database can be performed while it is serving requests. The following backup strategy is recommended:

  • A full backup of the database at least once a day using the SQL server backup tools.
  • A transaction log backup at least once an hour using the SQL server backup tools.
  • (recommended, virtualized) A snapshot of the virtual HDD at least once a day.

To restore a corrupted database the following step should be performed:

  1. Restore of the last full backup.
  2. Restore of the transaction logs to the lastest point in time that is available.

Data (Applicants, Mandators)

To ensure a complete and full backup we recommend the following 3-step backup strategy:

  1. Storage should be located on a redundant storage system (SAN) located in multiple data centers.
  2. Backup at least once a day to a LIVE backup (random access) for fast recovery.
  3. Backup at least once a day to a tape storage device.

To restore the data the following strategy is recommended:

  1. Failover to a redundant storage.
  2. Restore of the latest backup available (possible loss of data up 24 hours)

(optional) Application Server

It is recommended to perform a backup of the application server to allow fast recovery in case of an error. It is recommended to use a virtualized infrastructure to as it allows to perform the following actions:

  1. LIVE failover to another hypervisor (reduction of down time)
  2. Restore from virtual machine snapshow

 

 

 

 

 

Â