athento.com

Backup or data backup policy

Tabla de contenidos

Athento has backup policies to ensure the stability and integrity of the information. The objectives of the backup policy are:

  1. Safeguard the information assets of customers of Athento’s cloud service.
  2. Avoid data loss in the event of accidental deletion or data corruption, system error, or disaster.
  3. Allow the timely restoration of information and business processes, in the event of such events.

This policy applies to all Athento Cloud servers; for On-Premise instances, the backup policy must be carried out and maintained by the customer.

System backups may not be used in any case for the following purposes:

  1. Data archiving for future reference.
  2. The maintenance of a versioned history of data.

Retention periods

The retention periods of the information contained in system-level backups are designed to allow recoverability and provide a snapshot of the information over time, as it existed during the time period defined by the system backup policies.

Backups are kept for 1 year**. Backups are incremental.

Backup characteristics

Systems will be backed up according to the following scheme:

  1. Daily incremental backup every 24 hours.
  2. Backups will be performed at 00 hours (CET).
  3. Primary and secondary backups are performed in different locations.
  4. Backup destination on Disks
  5. Backups are performed for both the document repository and the database in which metadata and other meta-information are stored.
  6. Likewise, functional replicas of the production servers are performed.
  7. Backups are periodically verified by restoring a replica.

Repository backups

For certain plans, such as enterprise, backup copies of the repository binaries can be made in:

  1. Azure blob storage (in archive mode)
  2. Backblaze

These copies are made in data centers in Europe.

Backup review

Backups are reviewed to :

  1. To check and correct errors.
  2. To monitor the duration of the backup task.
  3. To optimize backup performance when possible.
  4. To identify problems and take corrective actions to reduce the risks associated with failed backups.

** This time may be reduced on a one-off basis by actions such as architecture changes, migrations, etc.