Back up your site

Always make a backup before applying updates. Drupal CMS checks for compatibility and tests updates as best it can, but updating code is never completely safe. Even an update that works can break features unique to your site.

Goal

A backup that lets you roll your site back to the state it was in before an update. It covers the database, uploaded files, the codebase, and a tested rollback procedure.

Prerequisites

• A running Drupal CMS site.
• Access to your hosting provider’s tools and documentation.

Steps

Check your hosting provider’s backup tools

The backup process depends on your hosting provider, so start there. Many managed Drupal hosting services provide one-click backups, scheduled backups, and restoration tools. If your provider offers backup tools or automated snapshot features, use them, and review the provider’s documentation before setting up custom backups.

Cover the four parts of a complete backup

Whatever tools you use, a complete backup includes:

• A snapshot of your site’s database.
• A copy of any user-uploaded files, such as images embedded in a blog post.
• A snapshot of the current codebase.
• A rollback procedure that has been tested and documented.

Set up a custom backup if your host offers none

To build your own backup strategy, start with the How to back up your Drupal site guide on Drupal.org.

Verify

A backup only counts if you can restore from it. Test the rollback procedure: restore the backup and confirm the site returns to its previous state, including the database, uploaded files, and codebase. Document the steps so anyone on your team can repeat them.

Related

• How updates work in Drupal CMS explains when updates arrive and who applies them.
• Update Drupal core and update modules and themes are the updates this backup protects against.
• How to back up your Drupal site on Drupal.org covers custom backup strategies in depth.