Backup & Redundancy

Last Published December 12, 2018

Service Continuity and Disaster Recovery

The Records365 service uses a variety of technologies and processes to ensure service continuity, minimise the chance of data loss and ensure recovery of data in the event of a disaster.

These include:

  • Service load balancing
  • Persistent queuing mechanisms
  • High availability DNS
  • Segmentation of virtual infrastructure into redundant availability sets and update domains
  • Synchronous data mirroring
  • Continuously replicated storage

The Recovery Point Objective (RPO) is) twelve (12) hours for the service. This period represents the maximum time period over which data loss may be experienced in the service in the event of an outage or system failure. Typically, organizations should expect data loss of no more than 2 hours since RecordPoint protects your Records365 data and has a copy of that data that is equal to or less than 2 hours old.

The identified Recovery Time Objective (RTO) is forty-eight (48) hours for the recovery of the service in the event of an outage or system failure. Organizations will be able to resume service within 48 hours after major service disruption or if a disaster incapacitates a hosting data centre. Typically, organizations should expect a recovery time of no more than 12 hours.

Data Backup

Data protection services are provided to prevent the loss of Records365 data.

Backups are performed every 24 hours, incremental every 4 hours and retained for 7 days.