Document toolboxDocument toolbox

(no) Data Backups

Owned by Maciej Zabielski
Jun 30, 2022
2 min read

Translation needed

The content of this page was copied from another page tree and needs to be translated or updated.

When you finish translation, make sure to

  • Replace the label NEEDS-TRANSLATING with TRANSLATED

  • Remove this macro from the page



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

Customer data

Frequency

Main Data Center Retention

DR / Offsite Backup Retention

Value

Database

Content: objects, metadata, user information & profiles, drawing information etc

Daily

  • Daily backup rotated every 5th day and stored on a storage system with snapshots.

  • Last 90 snapshots are stored.





  • Async standby replica*

  • Daily backup rotated every 5th day and stored on a storage system with snapshots.

  • Last 90 snapshots are stored.

  • Daily test restore for last backup.

Critical

Files

Contents: all documents uploaded by the user.

Daily

  • Offline classic backup

  • 90 snapshots for the main storage



  • Async standby replica

  • 90 daily snapshots

Critical

Configuration









Application Server - Customer configuration

Content: Information about specific application configuration

Daily

  • Configuration stored outside of VM

  • 90 snapshots of configuration storage device

  • Async standby replica*

  • (1 hour window, includes snapshots)

  • Automation of client configuration





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.

  • Async Standby environment

  • Daily test restore - last day backup






*) For standby DR site a best effort synchronization is performed. In standard conditions the synchronization is performed 24/7 with minimum delay.