Backup

Scope

All data in the Perfion SaaS environment is backed up according to a standard schedule. Backups are taken for both the SQL databases, as well as for the virtual machines running the backend services, and file shares.

The data is kept within Azure and always located in the same region as the customers' live environment and data.

Transfer of data into the backup vault has no impact on the production workloads.

All backups are configured with “ZRS” (Zone Redundant Storage), which means that multiple backups are saved across the Azure region, which ensures robustness against even local physical damage/events.

Requesting a backup restore

All communication about backups or restore procedures should be handled via the Service Desk. Should a restore be of an urgent nature, an existing Service Desk request can be escalated by sending an email to escalations@perfion.com with a reference to the request.

Backup schedule

Database

For all databases we have 7 days point-in-time backup stored. This means that we can restore the database to any specific point-in-time for the past week.[RD1] 

Beyond that, we have 4 weekly backups stored in long term retention.

Virtual Machines and file shares

All virtual machines and file shares are backed up nightly.

Data is stored for 30 days. 

Recovery Point Objective (RPO)

RPO defines the maximum acceptable amount of data loss measured in time.

• SQL database: In emergency situations, data loss may be up to 15 minutes. In practice, the actual RPO is often shorter.

• File Shares and Virtual Machines (VMs): Data loss may be up to 24 hours.

Recovery Time Objective (RTO)

RTO defines the maximum acceptable time to restore services after a disruption.

• Simple operations (e.g., restoring a single file or database): Recovery may take up to 6 business hours.

• Complex operations (e.g., full backend system outage requiring redeployment): Recovery may take up to 2 business days.