Data Backups
- Maciej Zabielski
- Agnieszka Siemiatycka
Backup Content
Our SaaS platform uses different solutions to backup different types of user data. A general overview of backups schedule is provided in the table below:
A customer instance is running in one of the datacenters. A replica is stored in second data center for a quick recovery. Each datacenter has capacity to run all instances in an unlikely case of a datacenter failure.Â
Backup is created to a dedicated backup device in each of the datacenters. As a result a local and offsite backup is made for a quick recovery and redundancy.Â
Â
Customer data | Frequency | Main Data Center Retention | DR / Offsite Backup Retention | Value |
|---|---|---|---|---|
Database Content: objects, metadata, user information & profiles, drawing information etc | Daily |
|
| Critical |
Files Contents: all documents uploaded by the user. | Daily |
|
| Critical |
Configuration | ||||
Application Server - Customer configuration Content: Information about specific application configuration | Daily |
|
| High |
Infrastructure | ||||
SaaS environment Content: all building blocks of the hosting environment | Some parts of the environment are stored as backups of virtual machines, and entire environment creation is automated so that it can be restored as quickly as possible. |
|
*) For standby DR site a best effort synchronization is performed. In standard conditions the synchronization is performed 24/7 with minimum delay.Â
Backup Restore testing
Database Backups
continuously monitor the backup execution process and error codes (each backup)
continuously monitor whether each database has its backup (each backup).
We verify the backup restoration process once a week.
restore the database.
check if the restored data contains the expected TimeStamp or other verification data
File Backups
continuously monitor the backup execution process and error codes (each backup).
Compare the list of files from the backup with the list of files from the database.
Backup System Integrity Checks
Our Backup Server uses a built-in SHA-256 checksum algorithm, to ensure data integrity.
Within each backup, a manifest file (index. json) is created, which contains a list of all the backup files, along with their sizes and checksums.
This manifest file is used to verify the integrity of each backup.
Such verification is performed once a week.