Before every merge, Elbuz Tunnel backs up the catalog tables in your site database, so you can roll back a faulty export in a few clicks.
When you need this:
- First export to a live site — the backup is saved on your hosting before a single storefront row changes.
- A run broke prices or descriptions — “Restore” returns the catalog tables to the state they were in when the backup was taken.
- Hosting space is limited — backups are compressed, and those older than the period you set are deleted automatically.
Where to start: the tunnel template card → the “DB archive” section.
What the backup does
- Backup before the merge — tables of the selected entities, compressed, with the date in the file name.
- Retention period — older backups are deleted before a new one is taken.
- Restore — pick a backup from the list and overwrite the site tables after confirming.
Site database backup
An Elbuz CMS store doesn't have this section. Its template window has neither the “DB archive” block nor a restore option: such a store is backed up automatically, and you restore it from the template with the “Backups” button — see How to restore your store from a backup. For sites on your own hosting (OpenCart, WooCommerce, and others), everything below applies.
The “DB archive” section is a collapsed “Site database backup settings” card; click its title to expand it. Inside are two checkbox toggles, “Create a backup copy of the site database” and “Use compression”, and two fields. In a new template, backup is on, along with compression.
1
Create a backup copy of the site database2
Use compression3
Number of days to keep backups4
File prefix- Create a backup copy of the site database — a copy of the site database is made before the data is merged.
- Use compression — the copy is packed into a .gz file.
- Number of days to keep backups — older copies are deleted before a new one is made.
- File prefix — text added at the start of the backup file name.
The backup is taken before the merge: when all data has already been sent to the module and sits in temporary tables in the site database, but not a single row has reached the working tables of the yet.
The log shows this: the line “A backup copy of the site database has been created:” with the file name comes after all the “Export …” lines and before “Updating site”. If the run breaks off earlier — during data transfer or via “Stop” — there's no backup, but the site's working tables haven't changed either.
The file is saved to the etrade_http_tunnel2/backup folder on your site's hosting and named “database name – date and time”, for example mysite_db-18-08-2026-03-40.sql.gz. The “File prefix” field adds your text to the start of the name — handy when backups of several sites are stored side by side.
Older templates may have 0 there; you can clear the field or enter something meaningful. The .gz extension comes from the “Use compression” checkbox — with it, the backup is compressed and takes up noticeably less space on your hosting.
The “Number of days to keep backups” field defaults to 7. Older files aren't deleted on a schedule but before a new backup is taken — so as long as no export runs, old backups stay where they are.
What the backup includes: only the tables of the entities checked in “Select data to export”. For OpenCart: checked categories — the backup gets the category tables; products — the tables of products, discounts, specials, and links to categories and stores; attributes, options, photos — their own tables.
Manufacturers are one table. Other platforms back up more, because their catalog lives in other tables: WooCommerce adds posts and postmeta, which means pages and blog posts too.
No platform's backup includes orders, customers, site settings, design themes, or modules. It's a catalog backup, not a site backup: in OpenCart, even static pages aren't included, and in WooCommerce they are only because they share a table with products. A full site backup is your hosting's job, and the tunnel doesn't replace it.
The backup checkbox doesn't work in every mode. All CMS in the list take a backup — CS-Cart, Magento, OpenCart 2 and 3, PrestaShop, and WooCommerce. There's one exception: the “MySQL (SQL custom query)” mode.
There, the checkbox is on but no backup is taken — the log simply won't have the line “A backup copy of the site database has been created:”. If you work with your own SQL query, back up the database with your hosting's tools before the first run.
Restoring from a backup
It's the “Restore site database” item in the “Additional” column on the right of the template card. The window is titled “List of backups” and lists the files from the backup folder on your hosting, each with a “Restore” button.
The “Restore” button first opens a warning: “Restore the site database from the copy “…”? Every table in the copy is overwritten completely - the current site data is lost. This cannot be undone.” The restore starts only after you confirm.
After you confirm, the module loads the selected dump into the site's working database over what's there now: tables in the backup are overwritten completely, and anything that changed in them after the backup was taken is lost — new products, corrected prices, edits in the site admin.
What exactly gets overwritten depends on the platform: in OpenCart it's the catalog (products, categories, manufacturers, attributes, options, photos); in WooCommerce, pages and blog posts too. Check the date and time in the file name before you click.
If the selected file has already been deleted after its retention period, you'll get a message saying the file doesn't exist. Refresh the window and pick another backup.
Scenarios
First run on a live site
What to do. In the “DB archive” section, leave backup creation and “Use compression” on.
What you get. Before the merge, a backup of the selected entities' tables is saved to the etrade_http_tunnel2/backup folder, and the log shows “A backup copy of the site database has been created:” with the file name. What you don't get. The backup doesn't include orders, customers, or site settings.
An export broke prices on the site
What to do. The “Additional” column → “Restore site database”, the backup dated before the failed run → “Restore” → confirm.
What you get. The tables from the backup are overwritten completely. What you don't get. A restore can't be undone, and anything that changed in these tables after the backup was taken is lost.
Backups of several sites are stored side by side
What to do. Enter the site name in “File prefix”.
What you get. Each backup's name starts with your text, so you won't mix them up. What you don't get. The retention period doesn't depend on the prefix — old backups are deleted before a new one is taken.
What to do when there's no backup or the restore failed
| What you see | Why | What to do |
|---|---|---|
| The log has no “A backup copy of the site database has been created:” line, although the checkbox is on | Backup isn't implemented for the “MySQL (SQL custom query)” mode | Back up the database with your hosting's tools before the run (about the backup) |
| “Class PDO not found” | The PHP pdo extension isn't installed on your site's hosting. It's needed only for the site database backup before the update |
Install php-pdo, or clear the backup checkbox in the template settings (about the backup) |
| The backup you need isn't in the list, or the response says the file doesn't exist | The backup was deleted after its retention period — 7 days by default | Refresh the window and pick another backup; to keep backups longer, increase “Number of days to keep backups” |
FAQ
Where is the site database backup stored, and what does it include?
In the etrade_http_tunnel2/backup folder on your site's hosting; the name is made up of the database name, date, and time. It includes only the tables of entities checked in “Select data to export”. By default, backups are kept for 7 days.
Why is there no backup line in the log, although the checkbox is on?
In the “MySQL (SQL custom query)” mode, no backup is taken — make one with your hosting's tools. All CMS in the list do take a backup.
Will the “Restore” button ask before restoring?
Yes. A warning with the backup file name opens first, and the restore starts only after you confirm. Check the date and time in the file name before you click.
Does the backup replace a hosting backup?
No. It's a catalog backup, not a site backup: it doesn't include orders, customers, settings, design themes, or modules.
When are old backups deleted?
Before a new one is taken: files older than “Number of days to keep backups” are deleted. As long as no export runs, old backups stay where they are.
The Elbuz CMS template has no database archive. Where are the backups?
An Elbuz CMS store is backed up automatically 4 times a day, and backups are kept for 7 days. The account administrator restores it from the “Elbuz CMS” template with the “Backups” button: How to restore your store from a backup.
Where to find it and who has access
- Menu
- Directories → Operations → Data export → Elbuz Tunnel template card
- Other entry points
- the “Additional” column on the right of the template card → “Restore site database”
- Access right
- “Restore site database” — a separate right, also checked when the action runs
- Prepare
- the PHP pdo extension on your site's hosting
Without the “Restore site database” right, the form won't open, and a direct restore call is rejected: the operation can't be undone.
Related topics
- For the big picture of the tunnel — How to export products to your site's database.
- If you turn on deletion on the site — How to remove products from your website that are no longer in the catalog.
- If you write the merge with your own queries — Updating the site with your own SQL queries: there, you make the backup yourself.
- If you need a backup of Elbuz itself — Backup and restore.
