Magento Guide → Security → Backup My CMS Tables

How to backup CMS tables on Magento 2

Key takeaways

• Magento 2 CMS content is stored in database tables.
• A full database backup includes key CMS tables.
• Admin backups are easiest, while CLI, mysqldump, and phpMyAdmin offer more control.
• Backups should be verified and stored securely.

Your CMS content, like pages and static blocks, helps shape your Magento storefront. Losing it during a failed update or server crash can be a nightmare. Fortunately, Magento 2 includes simple tools for backing up your CMS tables safely. Whether you’re using the Admin Panel, the command line, or automated jobs, backing up takes just a few minutes and can save you hours of recovery work.

Let’s walk through exactly how to do it, one step at a time.

What are Magento 2 CMS tables?

Magento CMS tables are database tables that store CMS pages, CMS blocks, and their store-view relationships. This includes content used for pages, banners, reusable content blocks, and other storefront content.

The CMS-related tables you may need to back up include cms_page, cms_block, cms_page_store, and cms_block_store.

Any full database backup will automatically include these tables. You don’t need to separate them out unless you’re doing something advanced, like migrating only CMS content.

Before you backup CMS tables in Magento 2

Before you begin, confirm that you have the right level of access. You may need Magento admin access, SSH access, database credentials, or hosting control panel access depending on the backup method.

Also check that your server has enough disk space and that you know where the backup file will be stored. For larger stores or database-sensitive work, choose a low-traffic time or use maintenance mode to reduce changes while the backup runs.

Method 1: Backup CMS tables from the Magento admin panel

The easiest way for beginners to back up CMS tables is through Magento’s built-in Admin Panel tool.

Go to Stores > Configuration > Advanced > System > Backup Settings

Set Enable Backup to Yes

Save the configuration

Go to System > Tools > Backups

Click Database Backup

Add a unique backup name if prompted

Choose whether to use maintenance mode

Run the backup and download the file from the backup grid when complete

A database backup includes the CMS tables along with the rest of the Magento database. The exact options may vary based on your Magento version, admin permissions, and hosting environment.

Method 2: Backup CMS tables with the command line

The Magento CLI lets you run backups with more precision and control than the admin panel. Connect to your server with SSH, then navigate to your Magento 2 root directory. From there, run:

php bin/magento setup:backup –db

This backs up the database, including CMS tables, and stores the backup in var/backups/.

You can also add:

–media

for media files, or:

–code

for core Magento and custom code.

This command may place the site in maintenance mode during the backup, so plan around store traffic and confirm the backup file is created successfully.

Method 3: Backup only CMS tables with mysqldump

If you only want the CMS-related tables, use a MySQL dump instead of a full database backup.

Run:

mysqldump -u [username] -p [database_name] cms_page cms_page_store cms_block cms_block_store > cms_tables_backup.sql

Replace [username] and [database_name] with your real database username and database name.

This method is best for developers, admins, or teams moving CMS content between environments without touching products, orders, or customers.

Method 4: Backup CMS tables with phpMyAdmin

phpMyAdmin can be useful if you prefer a visual database tool outside of Magento. Log in to your hosting control panel, open phpMyAdmin, and select the Magento database.

Select the CMS tables you want to export:

• cms_page
• cms_page_store
• cms_block
• cms_block_store

Click Export, choose the export method, and download the .sql file.

Be careful when working directly in the database. Avoid editing, dropping, or importing tables unless you understand the impact on the store.

Full database backup vs CMS-table-only backup

How to verify your Magento 2 CMS table backup

A backup should be verified before you rely on it. After the backup runs, check the file location, file size, timestamp, and download access.

You should also confirm that you know how the backup would be restored. This matters most before large CMS edits, theme changes, content migrations, or database work.

When to backup CMS tables

Back up CMS tables before editing CMS pages or blocks, updating homepage content, building campaign landing pages, changing themes, moving content between environments, cleaning up the database, or running Magento updates that may affect content.

If your team updates CMS content often, a scheduled full database backup or hosting-level backup can provide a safer fallback than one-off manual backups.

Common Magento 2 CMS table backup issues

Sometimes backups don’t go as planned. Common issues include backup options not appearing, permission errors, not enough disk space, backup timeouts, maintenance mode confusion, missing SSH access, or phpMyAdmin export limits.

If you don’t see the backup options in your Admin Panel, go to Stores > Configuration > Advanced > System > Backup Settings and make sure the backup tool is enabled.

If your store stays offline after a backup, delete the maintenance flag:

rm var/.maintenance.flag

For permission issues, check that the backup directory and required Magento folders are writable. For large databases, the CLI or hosting-level backups may be more reliable than an admin panel backup.

Backup storage and security best practices

Full database backups may include sensitive store data, so store them carefully. Limit access to backup files, avoid public web directories, and keep off-server copies when possible.

Use secure storage, retention policies, and encryption where appropriate. Backups should help you recover from a problem without creating a new security risk.

How hosting affects Magento backups

Reliable backups depend on more than Magento’s admin backup button. Hosting can affect disk space, database access, file permissions, backup storage, restore options, and support when something goes wrong.

Magento 2 CMS tables FAQs

Getting started with Magento 2 CMS tables

Backing up CMS tables in Magento 2 protects pages, static blocks, banners, and storefront content stored in the database.

Start by deciding whether you need a full database backup or a CMS-table-only export. Then verify the backup file before making changes.

Magento backups are easier to manage when your hosting environment supports secure storage, database access, restore options, and expert help when something goes wrong. Liquid Web Magento hosting gives ecommerce teams the performance, support, and reliability they need to protect and manage growing stores. Explore Liquid Web Magento hosting to find the right fit.