Backups

Alex Apostolou

Your data is safely and securely managed with a Microsoft SQL Server 2012 database managed within the Amazon EC2 environment.

Every Client’s data is stored and retrieved from a completely separate and isolated database instance. There is no possibility of Clients seeing other Clients data. The only foreseeable issue that could occur is database corruption. To minimise the effects of database corruption, every Client’s database is backed up on the following cycle:

  • Every 24 hours, a Complete Database Backup is taken. This process begins at midnight Australian Eastern Standard Time and typically lasts less than 30 minutes and does not involve any interruption to available or services. From a complete database backup, all RiskView data can be recovered.
  • Every 1 hour, a Differential Database Backup is taken. This process begins every hour on the hour and does not involve any interruption to available or services. From the complete backup and all the differential database backups until the corruption is detected, then RiskView data up until the last hourly backup can be recovered. In other words, the most data that could ever be lost is 1 hour’s data.
  • Every 1 hour, we replicate the Complete Database Backup and the Differential Database Backup files to our secure and off-site AWS storage account. Thereby providing a further level of redundancy.
  • Every day, we delete the Complete Database Backup and the Differential Database Backup files that were taken from 30 days prior. This period allows sufficient time to identify any problems and for them to be corrected.

Using this strategy we believe your data is very safe. But if you would like to discuss alternative strategies, please let us know.

Is it helpful to you?

Total Votes: 1

1
0