Information for: DEVELOPERS   PARTNERS

Acquia Cloud backups

Acquia maintains a comprehensive backup solution including application code, static files, and databases. Integrated backup facilities use Amazon’s Elastic Block Store (EBS) and Simple Storage Service (S3).

Automatic snapshots for disaster recovery

Acquia Cloud takes hourly snapshots of the passive master database, file system, and code repository. These snapshots are programmatically stored in Amazon S3 buckets (Amazon’s highly available cloud storage) and used to restore an application in case of multiple disk failure or total data center loss. Backup data stored in Amazon S3 is maintained in the same region (for example, US-East, US-West, or EU-East) where the production application is located. Amazon S3 repositories are distributed amongst various Availability Zones (data centers) and several devices within each Availability Zone for redundancy.

Acquia Cloud retains disaster recovery snapshots on the following schedule:

  • The four most recent hourly snapshots
  • Daily snapshots retained for one week
  • Weekly snapshots retained for one month
  • Monthly snapshots retained for three months

Acquia doesn’t provide subscriber access to these snapshots and won’t use the snapshots to restore applications due to either data loss or deletion by subscribers.

EBS snapshot workflow

Subscriber on-demand backups

Subscribers have full server access to implement their own on-demand backups of code, files, and database content. To assist, Acquia provides the previous three days’ database backups (dumps of the MySQL database) to Acquia Cloud subscribers using the Acquia Cloud interface or Cloud API. Subscribers may make on-demand backups of any database at any time on the Workflow tab of the Acquia Cloud user interface, or through SSH/SCP. Acquia Cloud Site Factory subscribers can also make backups using the Acquia Cloud Site Factory interface.

Acquia Cloud keeps your on-demand backups until you delete them. Your backup copies count against the storage space of your account. Subscribers may download database backups and restore a previous backup on the Backups tab of the Acquia Cloud user interface.

At the Drupal code layer, subscribers can manage and deploy their subscriber-developed code using Acquia’s code repository service (Git). These services allow for rollback and redeployment of Drupal code, effectively backing up the application’s code.

To ensure your organization’s ability to access your application’s code, settings, database, and files during a major service interruption or a disaster, Acquia recommends you use the Acquia Cloud-provided interfaces to copy the data to a local or cloud storage location independent of Acquia on a regular basis, or after you have deployed changes to the Acquia Cloud platform. You should also periodically check to ensure backups complete as expected and test if you can restore applications from a backup copy.