Bring a site back from downtime and implement post-recovery actionsDiscuss in our Forum Discuss in Slack
Bringing a site back from downtime and remediating the cause of downtime to ensure that the site stays up post-recovery is a multistep process. After you engage with support and determine the cause of the issue, the recovery process may include the steps outlined below. The precise playbook will depend on the nature of the issue and the configuration of the site.
The Signal Sciences and Advanced GCDN layers are primarily managed by Pantheon’s Professional Services team, with some updates and support tasks performed by the Customer Success Engineering team, which also performs intake on the initial request. This ensures that responses can meet the contracted SLA, and Pantheon aims to escalate/reassign to Professional Services on an as needed basis.
In the event of an attack, exploit, or other issue related to the global edge, file a ticket via the normal support channels, with an on-call emergency ticket filed in cases where downtime or serious service degradation occurs, and notify the Pantheon account team via Slack.
Recovery of a site may take minutes, but time to recovery can be uncertain. Additional features have been implemented at the Global CDN level to provide a more immediate solution. These features minimize downtime while the specific issues are remediated.
The Global CDN natively provides a layer of protection via the full-page cache. Experience Protection ensures that requests are fulfilled using stale cache, sending back pages that have technically expired. This only applies to requests that are cacheable; sites with a low cache hit rate will not be fully protected.
A set of static pages can be hosted directly and when certain failure conditions are detected, traffic can be redirected to a placeholder. The placeholder will provide a minimally acceptable user experience rather than error messages and a completely unreachable site.
In cases where the Google Cloud Platform infrastructure becomes compromised, Pantheon support can trigger a Multizone failover to redirect traffic at the load-balancing layer to a backup cluster of application servers on an alternate zone. For more information, refer to the Multizone Failover documentation.
Multizone failover is not designed to protect against issues on the Global CDN, on the load balancing layer, or at the application level. The automated monitoring that triggers a failover condition is focused on infrastructure issues. The zonal redundancy has an identical codebase, a continually replicated database, and uses a common filesystem, application issues would cause the same failure conditions regardless of zone.
Failover has an impact on the Redis object cache service - the cache will be automatically rebuilt in the new zone on failover, but this is transactionally heavy, and the site should be tested to determine the performance impact of a mass cache rebuild. This test can be scheduled by filing a support ticket.
Sites using Pantheon’s Solr search indexing service require support intervention as well as reindexing on the application side, and is not a supported integration.
Customer playbook should include:
- If using Redis: Test application for ability to handle a mass Redis cache rebuild.
- If using Solr: Consult with your Pantheon Customer Success Manager (CSM) to determine an appropriate monitoring and recovery strategy.
Remediating Application Issues
In cases where the site code, database, or assets have become corrupted or compromised, determine which aspects of the site require restoration. recovery processes differ and recovery time is dependent on enacting the correct playbook.
Managed Updates Deployment Issue
As part of the Managed Updates deployment process, a Multidev will be cloned from the Live environment. It will be used primarily for testing, but also as a backup. If the Live deployment fails, results in a regression, or compromises the site, this Multidev will be used as the source to restore Live to a pre-deploy state.
Codebase is Unrecoverable
The codebase can be restored from a selected backup via Terminus - the Dashboard Restore Tools restore all aspects of the site, and cannot be used to selectively restore. For more information, refer to the Backup Restore documentation information.
Reverting a Bad Commit to Pantheon
If a bad commit has been deployed to your Pantheon site, you can roll back the commit using Git. The process depends on the nature of the change and whether it involves core updates or upstream updates, etc. For more information, refer to the Undo Commits documentation.
Database and Filesystem Issues
The Database/files tools on the Site Dashboard can be used to clone either the files or database from a different environment (Test to Live, for example). For more information, refer to the Database Workflow docuemntation.
Restoring a Database from a Backup
The database can be restored from a selected backup via Terminus. The Dashboard Restore tools restore all aspects of the site, and cannot be used to restore selectively. For more information, refer to the Backup Restore documentation.
Restoring a Database from an External Dump
The database can be restored from an external dump using the Database/files tools on the Site Dashboard. An archive file can be uploaded, or a MySQL archive accessed on a remote location. For more information, refer to the Database Workflow docuemntation.