↑↓ selectEnter openEsc close

    1. Elbuz

    How to back up your database and restore your data

    16 min readUpdated

    Elbuz backs up the whole database nightly — products with prices, contacts, documents, settings — and restores any backup from the past week in one click.

    When you need this:

    • A bulk update broke prices — a restore returns the database to the previous night.
    • A risky operation is ahead — a manual backup is a restore point in minutes that nightly runs never push out.
    • The rollback may be unneeded — the backup list survives a restore, so you can undo it.

    Where to start: “Restore DB backup” → “Create” before risky work.

    What backups can do

    What a backup includes and what it doesn't

    A backup is a full dump of your account's database: the table structure and every row in it. In practice, it contains all products with prices and specifications, categories, supplier price lists and matches, contacts and documents, program settings, users and their permissions, and logs.

    What a backup does not include:

    • product photos and uploaded files. They are kept in a separate file storage. The database stores only links to them, so after a restore the card knows where its image is again — but if the file itself was deleted from storage, a database backup won't bring it back;
    • your site's database. If your site is connected via Elbuz Tunnel, it has its own database and its own backups — see below;
    • account settings on the Elbuz side — plan, balance, domain. They are not stored in your database.

    A backup file is a compressed dump. The program compresses it with a fast compression algorithm and puts it in cloud storage under your account ID. Backups are not on the disk you see in the program and take up no space there.

    Nightly backups: how many and how long they are kept

    Every night, roughly between 02:15 and 02:25 Kyiv time, Elbuz backs up the database of every account except free ones. This runs on the service side: there is nothing to turn on or configure, and it doesn't affect how the program works during the day.

    Before each new backup, the program keeps the seven most recent automatic backups and deletes older ones: the row disappears from the list and the file from storage. So after a nightly run the list has eight automatic backups: seven previous ones and the one just made.

    In practice this gives you a one-week window: today you can go back to any day up to last week, and no further.

    One week is all the time you have. A mistake made two weeks ago can no longer be fixed by restoring a backup: there is no backup of that day either in the list or in storage. If you deleted something and aren't sure whether you need it, check right away.

    Only automatic backups are rotated. A backup you create manually stays in the list and nothing pushes it out — it survives any number of nightly runs.

    A free account is not included in nightly backups: you can only create a backup in it manually. In other accounts an empty list means the first nightly backup hasn't run yet.

    The time of the nightly run is set by the service; you can't change it from the program.

    How to create a backup manually

    The “Create” button is in the top left corner. Click it and a blue message about creating the backup appears — nothing else is needed: the program dumps the database, compresses it, uploads it to storage, and adds a row to the list. On a large database this takes minutes; better not close the window meanwhile.

    When it's done, you'll see “Database backup completed”. Refresh the list and the new backup appears in the first row, marked as manual.

    The window has no button to delete a backup: a manual backup stays in the list for good.

    Three places where creating a backup can stop: dump, compression, upload to storage. In each case no row is added to the list, and you see a failure message
    NoYesNoYesNoYes“Create”Automatic backups beyond sevenare deleted from the list and storageThe database is dumpedDump succeeded?“Database backup was not created—see the error log for details.”The dump is compressedCompression succeeded?The file is uploadedto cloud storageStorage accepted the file?The backup is added to the listmarked as manual“Database backup completed”
    • Action or result
    • Decision: the path depends on the answer

    Make a manual backup before any action that is hard to undo. The most common examples:

    • a bulk catalog update from price lists, if you changed the matching or pricing rules;
    • merging duplicate products — it physically deletes cards;
    • bulk deletion of products, categories, or contacts;
    • reworking access rights, after which employees may lose windows they need;
    • setting up something big for the first time — a tunnel, an export, inventory tracking.

    A backup costs you one button and a few minutes of waiting. Recovering from a failed bulk operation without a backup costs much more.

    How to restore the database from a backup

    Find the date you need in the list and click “Restore DB” next to it.

    The program asks you to confirm: the dialog names the date of the backup you are restoring from, and the confirm button is red. Read the date in the dialog — it's your last chance to notice that you clicked the wrong row.

    The whole database is replaced. This is not “bring back deleted products” and not a selective restore: after the load your data will be exactly as it was at the time of the backup. Everything done after it — new orders, changed prices, imported price lists, correspondence — will be gone.

    That's why you restore when nobody is working in the program. If a colleague is placing an order right then, it disappears along with everything else — the program doesn't warn anyone. Sign-in sessions also go back to the backup state, so anyone whose session isn't in the backup is sent to the sign-in page on their next action.

    What happens next: the program downloads the backup file from storage, unpacks it, and loads it into the database. On a large database this takes a while — from a few minutes to tens of minutes. Don't close the window or reload the page during this time.

    When it's finished, you'll see “Database restore completed”. Click “OK” — the page reloads and you see the program with the restored data.

    If the load failed, you'll see “Database restore failed: mariadb returned an error. The dump is kept so the attempt can be repeated.”

    • You get the same message if the backup file couldn't be downloaded from storage or unpacked: then the load never started.
    • The page doesn't reload, and the “Restore DB” buttons are active again.
    • The database may be left half-loaded — try again with the same button. The backup list isn't lost on a retry: the program uses the one set aside before the first attempt.
    • If the retry fails too, contact support; the error details are already in the log.

    What the program does after a restore

    A restore is more than loading a dump. Along with it, Elbuz does three more things — four if the built-in store is enabled in the account — and it helps to know about them.

    • Keeps the backup list. A week-old dump knows nothing about backups made after it. So the backup list is set aside before the load and put back afterwards. You don't lose the option to roll back again, to a different date.
    • Applies database updates. New tables and fields may have appeared in the program during the week. Right after the load, every update the dump doesn't know about is applied — otherwise the current program would work with an old data structure.
    • Queues a search reindex. Quick product search uses its own index; after the database is replaced, it has to be rebuilt.
    • Clears the if the built-in store is enabled. Otherwise store pages would show data that is no longer in the database. Other accounts skip this step.
    What happens behind one button. The arrow back from the error is the “attempt can be repeated”: the dump is still there
    NoYesNoYes“Restore DB”next to the date you needConfirmed the datein the dialog?Nothing happensThe backup is downloaded fromstorage,unpacked, and loaded into thedatabase.On a large database — tens ofminutesLoad succeeded?“mariadb returned an error”.The dump is kept, the attemptcan be repeated with the samebuttonThe backup list is put backDatabase updates are appliedA search reindex is queuedIf the built-in store is enabled,the cache is cleared
    • Action or result
    • Decision: the path depends on the answer

    Both creating a backup and restoring are recorded in the Operation log along with how long they took. To find out who rolled back the database and when, look there.

    A backup of your site database is something else

    If your site is connected via Elbuz Tunnel, it has its own database — and its own backups. They are made on the site side, kept separately, and have nothing to do with the “Restore DB backup” window. A simple rule: the system settings window is about your database in Elbuz; the tunnel window is about the site database.

    Checklist before a risky operation

    Before a risky operation

    Scenarios

    Set a restore point before a bulk operation

    What to do. In the “Restore DB backup” window, click “Create” and wait for “Database backup completed”. Only then start the catalog update, duplicate merging, or bulk deletion.

    What you get. A row highlighted in color is added to the “List of backups”, with the “Manual backup” tooltip. Nightly runs won't push it out: the seven-backup limit counts automatic backups only.

    What you don't get. Photos and files — only the database. Changes colleagues make after you click “Create” aren't in the backup either: it captures the database when the dump starts. If something goes wrong, you see “Database backup was not created — see the error log for details.”, and no row is added.

    A bulk operation broke your data — go back to before it

    What to do. In the list, find a backup made before the operation: your manual one, if you made it, or the nightly one from the day before. Click “Restore DB” next to it, check the date in the dialog, and confirm with the red “Restore DB” button.

    What you get. The whole database becomes what it was at the time of the backup. After “Database restore completed” and the “OK” button, the page reloads. The backup list stays the same as before the restore.

    What you don't get. A selective rollback: everything done after the backup date disappears — both the broken and the correct changes, new orders included. Photos deleted from storage don't come back.

    If the operation happened before the oldest of the seven nightly backups and you made no manual one before it, there is nothing to roll back to.

    Roll back but keep a way back

    What to do. First click “Create” — a manual backup of the current state — and wait for “Database backup completed”. Only then click “Restore DB” next to the date you need.

    What you get. The backup list is set aside before the load and put back after it, so the manual backup you just made stays in the list. If the rollback turns out unnecessary, “Restore DB” next to that manual backup takes the database back to its state before the rollback.

    What you don't get. Changes colleagues made between clicking “Create” and the restore are neither in the manual backup nor in the one you rolled back to.

    What to do when there is no backup or the restore failed

    Symptom, cause, and what to do
    What you seeWhyWhat to do
    The backup list is empty The account is free — it isn't included in nightly backups. Or the account was created today: the first nightly backup hasn't run yet Click “Create” and make a backup manually (how)
    The date you need is not in the list The seven most recent automatic backups are kept — exactly a one-week window You can't roll back further than a week. Going forward: make a manual backup before risky actions — it is never pushed out
    “Database restore failed: mariadb returned an error” Loading the dump broke off, and the database may be left half-restored. Or the backup file couldn't be downloaded from storage or unpacked — then the database didn't change Click the same button again: the unpacked dump is kept for exactly this. If that doesn't help, contact support
    After the restore, cards have no photos Images are stored outside the database, and the backup doesn't contain them Upload the photos again or get them from the supplier's price list (why)
    A colleague complains their work is gone A restore replaces the whole database — everything done after the backup date is lost Agree on restores in advance and do them when nobody is working

    FAQ

    Can I restore just one product or one document?

    No. A restore loads the whole database: afterwards your data is exactly as it was at the time of the backup. The program has no selective restore of individual records.

    Will product photos come back after a restore?

    Not if the files themselves were deleted: a database backup contains only links to images, and the files are kept in a separate storage. If the files are still there, the cards will show them again (what a backup includes).

    Can I download a backup to my computer?

    No. The backup file is kept in the service's cloud storage, and the window has no download button. There is no button to delete a backup either.

    What happens to my colleagues' work during a restore?

    The program doesn't warn anyone. The database is replaced entirely, sign-in sessions included: some people are sent to the sign-in page, and everything done after the backup date disappears. Schedule restores outside working hours.

    Can I back up price lists and formulas?

    Yes, as part of a full database backup — with source settings, rules, markups, and formulas. There is no separate backup of only price lists or formulas, and price list files are not included. A previous formula version is restored with the “Change history” button in the formula window.

    Where to find it and who has access

    Menu
    Account → System settings → “Other settings” → “Restore DB backup”
    Other ways in
    the “Restore DB backup” shortcut, if it has been added to the desktop
    Access right
    the “Restore DB backup” window (by default for “Management”) and the “System settings” window
    Prepare
    for a restore — a time when nobody is working in the program
    System settings window, “Other settings” section with the “Restore database backup” tile among other tiles
    1Restore database backup tile
    2“Other settings” section
    1. Restore database backup — the tile that opens the list of backups; it sits in the bottom row between Task schedule and System functions.
    2. Other settings — the section in the left panel that holds the tiles of separate settings windows.

    The window is small: the “Create” button at the top, then the “List of backups” heading and the backups themselves — the date and time of each, with a “Restore DB” button next to it. The 20 most recent backups are shown, newest first.

    Restore database backup window with the Create button and the list of backups
    1Create button
    2List of backups heading
    3Backup date and time
    4Restore DB button
    1. Create button — makes a new backup (not pressed).
    2. List of backups heading — the list of available copies.
    3. Backup date and time — each row is one copy, newest to oldest.
    4. Restore DB button — restores the database from that copy (not pressed).

    Manual backups are highlighted in color in the list. Hover over the date and the tooltip says “Manual backup”. This is the only way to tell a manual backup apart in the list.

    Where database backups are kept

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free