Acquia Copilot is a conversational AI connected into our product documentation and knowledge base. Ask Copilot about product features, technical details, troubleshooting and how to get started with Acquia products.
For information about backups in Site Factory, see Backing up sites.
Automated database backups
Daily backups from the last three days are always available in the Cloud Platform user interface and are listed as Automatic (Daily) on the Databases page. These daily backups are required and cannot be disabled. However, you can take on-demand backups at any time, for example, for critical stages of development. You must periodically check to ensure that backups complete as expected and test if you can restore websites from a backup copy.
For Cloud Next
Automated database backups are always generated overnight based on the regional location of the infrastructure.
The Cloud Platform user interface may occasionally display two daily backup tasks for the same day, indicating the backups taken at different times of the day.
On-demand database backups
You can take on-demand backups of any database through one of the following ways:
These backups are listed as Manual backups on the Databases page in the Cloud Platform user interface. Cloud Platform keeps your on-demand backups until you delete them. Based on the utilized resources, database backup times might vary for the same size of database.
Important
Database backup operation times out after 12 hours.
In Cloud Classic, your database backup copies count against the storage space limit associated with your subscription as the copies are stored in your file system. However, in Cloud Next, database backup copies are not stored in your file system and therefore are not counted against your subscription limit.
Taking a database backup on an application’s Environments page
Sign in to the Cloud Platform user interface.
Select your application.
On the card for the environment you want to back up, select the Back up databases icon.
In the list of databases, do one of the following:
To take backup of specific databases, select the checkboxes corresponding to those databases.
To take backup for all databases, select the Select All checkbox.
Select Continue.
In the confirmation dialog box, select Back up.
Taking a database backup on an environment’s Overview page
Your code is maintained in a version control repository managed by Acquia. Each time you use the Cloud Platform user interface to click-and-drag code from an environment running either master or a branch, a new tag is created in the version control system. You can revert to an earlier tag at any time in any of your environments.
File backups
Your uploaded files are kept separate from your Drupal codebase and database, using a symbolic link to your application’s /files directory. The Git version control system can manage text files full of code, but is less well suited for managing large collections of user-uploaded objects, such as images, videos, or file attachments.
Cloud Platform makes internal disaster recovery snapshots of your files, but these are not available for subscribers for normal backup purposes. If you want to back up your uploaded files, you can either do so manually from the command line or create a cron task to make backups on a regular schedule.
To back up your whole application on an environment from the command line, you can use Drush.
Note
The current Drupal version requires Drush 11 or later. Therefore, you must install Drush 11 or later only through Composer as Acquia does not manage the update to newer versions. For more information, see About Drush on Cloud Platform.
The drush archive-dump command creates a complete archive file of your application.
Important
Running this command on a large website (with large numbers of files, large databases, or volumes with a small files area) can lead to a full disk, which will cause the script to hang and will cause a website outage.
For information about backups in Site Factory, see Backing up sites.
Automated database backups
Daily backups from the last three days are always available in the Cloud Platform user interface and are listed as Automatic (Daily) on the Databases page. These daily backups are required and cannot be disabled. However, you can take on-demand backups at any time, for example, for critical stages of development. You must periodically check to ensure that backups complete as expected and test if you can restore websites from a backup copy.
For Cloud Next
Automated database backups are always generated overnight based on the regional location of the infrastructure.
The Cloud Platform user interface may occasionally display two daily backup tasks for the same day, indicating the backups taken at different times of the day.
On-demand database backups
You can take on-demand backups of any database through one of the following ways:
These backups are listed as Manual backups on the Databases page in the Cloud Platform user interface. Cloud Platform keeps your on-demand backups until you delete them. Based on the utilized resources, database backup times might vary for the same size of database.
Important
Database backup operation times out after 12 hours.
In Cloud Classic, your database backup copies count against the storage space limit associated with your subscription as the copies are stored in your file system. However, in Cloud Next, database backup copies are not stored in your file system and therefore are not counted against your subscription limit.
Taking a database backup on an application’s Environments page
Sign in to the Cloud Platform user interface.
Select your application.
On the card for the environment you want to back up, select the Back up databases icon.
In the list of databases, do one of the following:
To take backup of specific databases, select the checkboxes corresponding to those databases.
To take backup for all databases, select the Select All checkbox.
Select Continue.
In the confirmation dialog box, select Back up.
Taking a database backup on an environment’s Overview page
Your code is maintained in a version control repository managed by Acquia. Each time you use the Cloud Platform user interface to click-and-drag code from an environment running either master or a branch, a new tag is created in the version control system. You can revert to an earlier tag at any time in any of your environments.
File backups
Your uploaded files are kept separate from your Drupal codebase and database, using a symbolic link to your application’s /files directory. The Git version control system can manage text files full of code, but is less well suited for managing large collections of user-uploaded objects, such as images, videos, or file attachments.
Cloud Platform makes internal disaster recovery snapshots of your files, but these are not available for subscribers for normal backup purposes. If you want to back up your uploaded files, you can either do so manually from the command line or create a cron task to make backups on a regular schedule.
To back up your whole application on an environment from the command line, you can use Drush.
Note
The current Drupal version requires Drush 11 or later. Therefore, you must install Drush 11 or later only through Composer as Acquia does not manage the update to newer versions. For more information, see About Drush on Cloud Platform.
The drush archive-dump command creates a complete archive file of your application.
Important
Running this command on a large website (with large numbers of files, large databases, or volumes with a small files area) can lead to a full disk, which will cause the script to hang and will cause a website outage.
For example, to back up the Prod environment of an application named example1:
drush @example1.prod archive-dump
By default, the backup file is saved to the drush-backups folder. Use the --destination option to specify the full path and file name in which the archive should be stored.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
For example, to back up the Prod environment of an application named example1:
drush @example1.prod archive-dump
By default, the backup file is saved to the drush-backups folder. Use the --destination option to specify the full path and file name in which the archive should be stored.
Cloud Platform