Cloud Platform
Rolling back production deploys
If a production deploy of a security update goes wrong, it may be necessary to consider rolling back your production code and database(s) to quickly get your production site back up and running.
If a member of the support team is actively assisting you with the failed deploy, we can advise on whether or not a rollback is advisable. Ultimately the decision to roll back is the decision of you or your team and Acquia takes no responsibility for data loss as a result of a production roll back.
Before rolling back your site you should exhaust all other troubleshooting options to get your site back up. Have you:
If you have exhausted all the options and any further troubleshooting steps, it may be time to consider rolling back to get the site back up. There are a number of steps for rolling back your production environment:
Rolling back code
Rolling back the database
If no database updates were required when deploying your code to production, you can simply roll back the code that was deployed to the previous tag. In the case of Remote Administration updates, any database updates are communicated in our initial ticket notification.
This option does not present any risk to your database, however it is always best practice to have a fresh database backup available when making changes to production. Remote Administration always generates an on demand backup before deploying code to production.
If database updates were required as part of the deployment process, the rollback process will also require you to revert the database to the previous backup. Failing to do so will mean that your code and database will diverge, which may cause errors on your site.
Rolling back the database will result in the loss of any data created after the database backup. This includes any newly created content, user created content, user accounts and user activity on the site. When considering a database rollback, it is important to consider your own acceptable level of data loss. For sites with high volumes of user activity and user generated content, we recommend you implement a content freeze or put the site in maintenance mode prior to deploying changes to production to minimize this risk.
To revert your site to a previous backup:
If Remote Administration preferences are set to merge the updates into your master branch, an additional step is required to revert this branch. Failure to do so means that any new tags or branches created from master will contain the problematic updates.
To revert the merge:
Cloud Platform