To increase the reliability of our systems, Healthy.io has redundancy plans for all our information and software, including regularly performed corporate testing and restoration procedures. It has defined and documented a formal definition of redundancy at the system level and requirements for each system. This includes how it will restore each system, the scope of data to be imaged, frequency of imaging, and duration of retention based on relevant contractual, legal, regulatory, and business requirements.
Backups, part of the redundancy methodology, are stored in a physically secure remote location at a sufficient distance to make them reasonably immune from damage to data at the primary site with physical and environmental controls to ensure their protection.
Healthy.io uses Automated Cloud-native tools to manage and track all redundancy files. It maintains Inventory records for the backup copies, including content and current location. It also keeps backup copies of the produced integrity and security to ensure future availability and ‘fail-safeness,’ and identifies and mitigates any potential accessibility issues with the backup copies in the event of an area-wide or natural disaster.
Service Level Agreements (SLA) with third parties include the detailed fail-safes to control confidentiality, integrity, and availability of all backup information and software systems.
Healthy.io backs up covered information in an encrypted format to ensure confidentiality. The additional organizational fail-safes include daily and weekly performance and incremental /differential backups to separate locations. Healthy.io methodology ensures that a current, retrievable copy of covered information is available before the movement of servers. Healthy.io tests backup information following each backup to verify content reliability and information integrity, or at least annually after that.
Healthy.io regularly manages backups for all data repositories. A point-in-time data backup works daily, allowing for a 24-hour Recovery Point Objective (RPO).
In the event of a disaster, corresponding data repositories for restoration and backup provide fail-safe functionality after the Incident Response team completes the root-cause analysis and can isolate it.