Restoring the data based on our backups of the previous day can then be done in a few hours (for the largest clusters), with priority on the paid subscriptions. We have automated provisioning to deploy our services in a new hosting location. How is this accomplished: we actively monitor our daily backups, and they are replicated in multiples locations on different continents.This is the time to restore the service in a different data center if a disaster occurs and a datacenter is completely down. RTO (Recovery Time Objective) = 24h for paid subscriptions, 48h for free trials, education offer, freemium users, etc. ![]() This means you can lose max 24h of work if the data cannot be recovered and we need to restore your latest daily backup. Disaster recovery: in case of complete disaster, with a data center entirely down for an extended period, preventing the failover to our local hot-standby (never happened so far, this is the worst-case plan), we have the following objectives:.Hardware failover: for services hosted on bare metal, where hardware failure is possible, we implement local hot standby replication, with monitoring and a manual failover procedure that takes less than 5 minutes.You can contact our Helpdesk to restore any of those backups on your live database (or on the side). ![]() ![]()
0 Comments
Leave a Reply. |