Common use of Back-ups and Disaster Recovery Clause in Contracts

Back-ups and Disaster Recovery. For all Cloud and Private Cloud installations back-ups are generated and stored every 24 hours. Backup media, where relevant, is verified for integrity and stored encrypted at a secure offsite facility. For Cloud and Private Cloud High Availability (HA) installations, eLabNext will ensure that all of Your data up to the last committed transaction is replicated up in real-time to ensure a Recovery Point Objective (RPO) of less than 5 minutes in case of a disruption of the system or a disastrous event one of the data centers. In case of a disastrous event impacting the integrity of the full system, eLabNext will be able to restore of loss of data with a maximum Recovery Point Objective (RPO) of 24 hours and a Recovery Time Objective (RTO) of 4 hours, provided that the data loss was caused by eLabNext or failure of our systems. eLabNext shall not be liable for data loss resulting from intentional failures or negligent actions by You. System Recovery Point Objective (RPO) Recovery Time Objective (RTO) Cloud 24 hours* 4 hours Private Cloud 24 hours* 4 hours On-Premises N/A N/A eLabNext validates its disaster recover procedure every month, by manual inspection of the back-up file’s size and date on receipt. A representative back-up sample is used to perform a full system restore procedure. Disaster Recovery will only be executed in case of an event that impacted the availability of data. In the event of information processing errors caused by eLabNext, upon reasonable request, and subject to reasonable security procedures, You will be permitted to request a restoration of Data from the most recent backup files for disaster recovery purposes. Requests to perform a disaster recovery to undo system changes are excluded from these services. Storage of backups remotely at the customer's site is available only under an Advanced Support Agreement. For eLabNext On-Premises installations, backups and disaster recovery are Your responsibility and are excluded from these Service and Support Terms.

Back-ups and Disaster Recovery. For all Cloud and Private Cloud installations back-ups are generated and stored every 24 hours. Backup media, where relevant, is verified for integrity and stored encrypted at a secure offsite facility. For Cloud and Private Cloud High Availability (HA) installations, eLabNext will ensure that all of Your data up to the last committed transaction is replicated up in real-time to ensure a Recovery Point Objective (RPO) of less than 5 minutes in case of a disruption of the system or a disastrous event one of the data centers. In case of a disastrous event impacting the integrity of the full system, eLabNext will be able to restore of loss of data with a maximum Recovery Point Objective (RPO) of 24 hours and a Recovery Time Objective (RTO) of 4 hours, provided that the data loss was caused by eLabNext or failure of our systems. eLabNext shall not be liable for data loss resulting from intentional failures or negligent actions by You. System Recovery Point Objective (RPO) Recovery Time Objective (RTO) Cloud 24 hours* 4 hours Private Cloud 24 hours* 4 hours On-Premises N/A N/A eLabNext validates its disaster recover procedure every month, by manual inspection of the back-up file’s size and date on receipt. A representative back-up sample is used to perform a full system restore procedure. Disaster Recovery will only be executed in case of an event that impacted the availability of data. In the event of information processing errors caused by eLabNext, upon reasonable request, and subject to reasonable security procedures, You will be permitted to request a restoration of Data from the most recent backup files for disaster recovery purposes. Requests to perform a disaster recovery to undo system changes are excluded from these services. Storage of backups remotely at the customer's site is available only under an Advanced Support Agreement. For eLabNext On-Premises installations, backups and disaster recovery are Your responsibility and are excluded from these Service and Support Terms.