How to back up your Magento 1 store

Key takeaways

• A complete Magento 1 backup should include both store files and the MySQL database.
• SSH or hosting-level backups are usually safer for larger Magento 1 stores than the built-in admin backup tool.
• Magento 1 admin backups are stored in var/backups, but you should also keep secure off-server copies.
• A backup is only useful if you can download, protect, and restore it when needed.

Learn how to create manual backups as well as schedule regular backups of your Magento 1 store.

Magento 1 includes a built-in backup tool, but the right backup method depends on your store size, server access, and restore needs. Larger live stores often need SSH, cPanel, phpMyAdmin, or hosting-level backups instead of relying only on the Magento Admin Panel.

What should a Magento 1 backup include?

A complete Magento 1 backup should include both the store files and the MySQL database. Store files include themes, media, extensions, custom code, and configuration files. The database stores products, categories, customers, orders, settings, and other store data.

Backing up only files or only the database may not be enough to restore the full store. A database backup can restore store data, but it won’t restore missing media files, theme files, extensions, or custom code.

Magento 1 backup methods

There are several ways to back up a Magento 1 store. The best method depends on your access level and the size of the store.

Method 1: Backup a Magento 1 store with SSH

SSH is often the fastest and safest option for larger Magento 1 stores because it can back up files and databases directly from the server.

Step 1: Connect to the server

Log in to your server with SSH and navigate to the Magento root directory. This is the folder where your Magento store files are located.

Step 2: Backup the Magento 1 files

Create a compressed archive of the Magento files:

This archive should include the Magento files, themes, media, extensions, and custom code.

Step 3: Backup the Magento 1 database

Export the Magento database with mysqldump:

Replace database_user and database_name with the correct values for your store. You can often find the Magento 1 database credentials in:

Step 4: Move backup files out of the public webroot

Do not leave backup archives in a public directory. Move the files above the public root if possible, download them with SFTP, and store copies securely. After confirming you have a safe copy, remove any public backup files from the server.

Method 2: Backup a Magento 1 store with cPanel and phpMyAdmin

If you don’t have SSH access, you may be able to back up files and the database through your hosting control panel.

Backup files with cPanel File Manager

Log in to the hosting control panel, open File Manager, and find the Magento installation folder. Compress the folder into an archive, then download it to a secure location.

After downloading the archive, move or delete any backup files that were created in a public directory.

Backup the database with phpMyAdmin

Open phpMyAdmin, select the Magento database, and click Export. Choose a custom export if needed, export the database as a .sql file, and download it.

Larger databases may fail through phpMyAdmin because of timeouts or size limits. In those cases, SSH or a hosting-level backup may work better.

Method 3: Backup a Magento 1 store from the Admin Panel

Magento 1 also includes a backup tool in the Admin Panel. This can be useful for smaller stores, but it may create resource issues on larger live stores.

From the Magento Admin Panel, select System > Tools > Backups.

Select your desired backup type: System Backup, Database and Media Backup, or Database Backup. System Backup creates a backup of the database and file system. The other two options are self-explanatory.

Read the warning, then click OK when ready.

Enter a backup name. If desired, select Put store on the maintenance mode while in backup creation, then click OK when ready. If you choose System Backup, you may also have the option to exclude the media folder.

You may view backups at any time by following Step 1. To delete a backup, select the corresponding check box, select Delete from the Actions drop-down menu, then click Submit.

Magento 1 Admin Panel backup types

Magento 1 gives you several backup options in the Admin Panel.

The right backup type depends on the work you are doing. For major updates, file changes, extension work, or troubleshooting, a fuller backup is usually safer.

Where does Magento 1 store backups?

Magento backs up files in the .gz format. The .tgz format is used for system, database, and media backups.

Backup files are stored in the var/backups directory for your Magento file system.

Files stored in the /var/cache, /var/log, and /var/report folders are exempt.

Don’t rely only on backups stored on the same server. Download a copy and store it somewhere secure, especially before major maintenance, updates, or hosting changes.

Use maintenance mode during backups

Magento 1 may let you put the store into maintenance mode while creating a backup. This can help reduce changes while the backup runs, especially before larger updates or database work.

Use this option carefully. Maintenance mode can interrupt customers, so schedule backup windows during lower-traffic periods when possible.

Scheduling regular backups in Magento 1

Magento 1 also lets you schedule backups from the Admin Panel.

From the Magento Admin Panel, select System > Configuration.

In the Configuration menu on the left, scroll to the ADVANCED menu, then select System.

Expand the Scheduled Backup Settings section. From the Enable Scheduled Backup drop-down list, select Yes. Designate your desired Backup Type, Start Time, and Frequency. If you wish to put your store into maintenance mode during these backups, select Yes from the Maintenance Mode drop-down list. Click Save Config when done.

Scheduled backups can help, but you should still confirm they run successfully and keep important copies off-server.

When should you backup a Magento 1 store?

Back up your Magento 1 store before extension installs, theme changes, code deployments, server changes, database changes, security work, configuration changes, catalog imports, major content updates, and host moves.

You should also keep regular scheduled backups for ongoing protection. Stores with frequent orders, customer activity, and catalog updates usually need more frequent backups.

Backup storage best practices

Magento 1 backups should be stored securely and not only on the production server. Keep off-server copies, restrict access, label backups clearly, encrypt sensitive backups where needed, and follow a retention schedule.

Avoid leaving backup archives in public directories. Old or exposed backups can create security risks because they may contain store files, configuration details, customer records, order information, or database credentials.

Verify your Magento 1 backup

A backup should be checked after creation. Confirm that the file archive exists, the database dump exists, the file sizes look reasonable, and the backup date and label are clear.

Download a copy, store it securely, and test a restore in staging when possible. 

How to restore a Magento 1 backup

Restore steps depend on how the backup was created. A full restore may require replacing files and importing the database.

Test restores in staging when possible. If you need to restore over a live store, work with your hosting provider or Magento developer before replacing files or importing database content.

Magento 1 support note

Magento 1 is no longer the current Magento release line, but some stores still need to maintain Magento 1 environments. For those stores, backups are especially important before updates, troubleshooting, hosting changes, or security work.

Tip: Review our guide on Magento 1 end of life: what you need to know to understand the implications for your store.

Magento 1 backup FAQs

Getting started with Magento 1 backups

A Magento 1 backup should include both files and database content. The safest method depends on your store size, server access, and restore needs.

Choose the backup method that fits your access level, create both file and database backups, then download and store a copy off-server.

Magento 1 backup workflows depend on reliable hosting, secure file access, storage, maintenance mode, and support. Liquid Web Magento hosting gives store owners the infrastructure and help they need to protect and manage Magento stores with confidence. Explore Liquid Web Magento hosting to find the right fit.

Jason Dobry