Buy

Backups

Premium

The Backups page backs up your local projects. A backup set bundles one or more folders and files and one or more databases into one entry that you back up by hand or on a schedule. Every run writes a complete, self-contained archive with files and databases together. You restore it whole or in parts and need no other run for that. Backups are a Premium feature.

What you do here

Page layout

Area Content
Header Categories and New backup set.
Note Run without the app open Scheduled backups otherwise only run while WebDonkey is open. Here you hand that over to macOS, see Run without the app open.
Backup sets One card per set, grouped by category, sets without one under Uncategorized. Each card has Run now, Archives, Open in Finder, edit and delete.
Backups made All archives of your sets, newest first, with their parts. You restore from here.
Remote backups Appears if you also back up servers, with the link All remote backups. You restore, delete and check those archives on the Remote › Backups page.

As long as there is no set, it says “No backup sets yet. Create one to bundle folders and databases.” with New backup set.

What this page is not for

  • This page backs up your projects: folders, files and databases.
  • A single database is quicker to back up right on the Databases page, on Free as well.
  • The backup of WebDonkey itself (sites, services, settings, for moving to another Mac) is under Settings › System.

Free and Premium

Backups are entirely Premium. On Free the page shows the note Backups are Premium.

If Premium ends and you already have sets, everything stays. The page then shows a plain list with a note that scheduled backups no longer run. For each set you see the schedule, the last run and the size, with its archives below, each with date and size. You can switch the schedule off with Switch schedule off, show an archive in Finder or delete it, and delete the set, with its archives if you want. Creating, running and restoring need Premium again. The archives are ordinary ZIP archives with the ending .wdbak, so you can get at your data without WebDonkey too.

With Hide Premium features under Settings › Navigation, Backups leaves the sidebar on Free.

Create a backup set Premium

A backup set describes what gets backed up, where to and when. You create it once and then back it up with one click or on a schedule. The dialog is called New backup set when you create one and Edit backup set when you change one.

Where to find it

Sidebar Local › Backups, New backup set at the top right. You edit an existing set with the pencil on its card. On the command line, wd backup add creates a set and wd backup edit changes one. More in Tasks, backups and logs.

How to do it

  1. Click New backup set.
  2. Name: for example “My project”. Without a name you cannot save.
  3. Category (optional): assigns the set to a group, see Manage categories. The default is Uncategorized.
  4. Under Paths, use Add folder and Add file to add what should be backed up. Without a path it says “No paths yet”.
  5. For each folder, set under Exclude what is skipped (see below).
  6. Under Databases, choose a database with Choose a database… and click Add. Repeat for each further one.
  7. Set the storage location, schedule and retention.
  8. Click Save.

The set appears as a card. Nothing is backed up yet: click Run now or wait for the schedule.

Exclude

Large folders that can be regenerated do not belong in the archive. Under Exclude for each folder you specify what is skipped:

  • Type a name or sub-path into the add… field and confirm with Enter or a comma, for example node_modules or var/cache.
  • Or click one of the Suggestions: node_modules, vendor, .git, var/cache, .next, dist, build.
  • Or pick a folder or file with the two icons at the field (Pick a folder to exclude, Pick a file to exclude). If the pick lies inside the backed-up folder, WebDonkey enters the sub-path, otherwise the name.

A plain name like node_modules applies at any depth, a sub-path like var/cache exactly at that spot. The × at an entry takes it out again.

Databases

The Choose a database… list shows the databases of your running WebDonkey servers, each entry with server and name, such as “MySQL · shop”. MySQL, MariaDB and PostgreSQL can be backed up. MongoDB databases are listed as not supported and cannot be added. If a server is not running, its databases do not appear. Start it on the Databases page then.

Edit, draft and delete

  • Editing only changes the set. Archives that already exist stay as they are.
  • If you switch to another page while typing, your draft stays. Cancel discards it.
  • The trash can on the card (Delete) asks Delete backup set. The archives on disk are kept. If the set has archives, you can tick Also delete the archives on disk, with their size after it. Then WebDonkey deletes them too, and that cannot be undone.

See also

Schedule, storage location and retention Premium

In a backup set's dialog you decide when it runs, where the archives go and how many of them WebDonkey keeps. One set can back up to an external drive every night and keep the last ten, while another only runs by hand in the default folder.

Where to find it

Sidebar Local › Backups, New backup set or the pencil on a set's card. The Storage location, Schedule and Retention sections are at the bottom of the dialog.

Schedule

Under Schedule, choose at Run:

Choice When it runs More fields
Manual only Only when you click Run now. Default. none
Every hour Once an hour. none
Every day Every day at the chosen time. At, default 02:00
Every week Once a week on the chosen day. On (Monday to Sunday, default Monday) and At
Cron expression… By an expression of your own with five fields. Schedule (cron expression), default 0 3 * * *

Below the fields a sentence sums up when the backup runs, such as “Runs every day at 02:00.” or “Runs every Monday at 03:00.”. On the set's card a label shows the schedule: Manual, Hourly, Daily, Weekly or Cron.

For a cron expression you can click one of the presets instead of typing (Every minute, Every 15 minutes, Hourly, Daily at 03:00, Weekdays at 09:00, Mondays at 03:00). The field is checked as you type. For an invalid expression it says “Not a valid cron expression.” below, and Save stays off. The syntax is the same as for scheduled tasks, see The schedule.

All times are your local time. When the clocks change, a time that does not exist runs at the first minute after it, and a time that occurs twice runs only once.

When the app is closed

Scheduled backups run inside WebDonkey. If the app is closed, nothing happens at the planned time. The dialog says so: “Scheduled runs need WebDonkey to be running. Anything missed while it was closed is caught up the next time you open it.”

If a nightly backup should also run with the app closed, set up macOS scheduling through the note on the Backups page or under Settings › System, see Run without the app open. Then macOS backs up the files without the app too. If the database servers are not running at that time, for example because WebDonkey stops all services when it quits, the backup leaves out the databases and names them. The WebDonkey journal then shows a warning “Partly backed up: the files only”.

Storage location

Under Storage location you choose per set:

Choice Where the archives go
Default (WebDonkey) Into WebDonkey's backup folder, one subfolder per set. By default under ~/Library/Application Support/WebDonkey/project-backups/.
Custom folder Into a folder of your choice, for example on an external drive. Enter the path (placeholder /path/to/backups) or use Choose folder. WebDonkey creates a subfolder named after the set inside it.

On the card, Storage shows either WebDonkey or the path. Open in Finder on the card shows the folder.

Retention

Under Retention, choose at Backup handling:

  • Keep multiple backups: default. Under Backups to keep you set how many, at least 2, default 10. After every run WebDonkey deletes the oldest archives beyond that number.
  • Keep only the newest: each run replaces the previous archive.

Every archive is complete and self-contained, files and databases together. So you lose nothing when older ones go.

These rules apply when cleaning up:

  • Only successful runs of this set count whose archive still sits under its original name in the current storage location. WebDonkey leaves alone an archive you renamed or moved, or one from an earlier storage location.
  • The newest archive that holds all databases of the set always stays, even if many runs without databases came after it. Nights with the app closed never rotate the last complete dump away.

See also

Run a backup and view archives Premium

You back up a set right away with Run now or let it run on its schedule. Every run writes an archive. All archives are listed under Backups made, with their parts, their size and the buttons for restoring, saving and deleting.

Where to find it

Sidebar Local › Backups. The set cards are at the top, Backups made below. On the command line, wd backup run runs a set and wd backup runs lists its archives. More in Tasks, backups and logs.

A set's card

Element Meaning
Name and label The set's name and its schedule, for example Daily.
“x paths · y DBs” How many paths and databases the set backs up.
Last run When it last backed up.
Size How much space all archives of the set take together.
Storage WebDonkey or the path of the custom folder.
Run now Starts a run.
Archives Shows the archives of this set only, in a dialog.
Open in Finder Opens the folder with the archives.
Pencil, trash can Edit or delete the set, see Create a backup set.

How to do it

  1. Click Run now on the card.
  2. The card shows the progress: first Dumping database: with the name, then Archiving files… with a counter, finally Finalizing….
  3. At the end the card shows a message:
    • Backup finished with the archive's path and the space all archives of the set now take.
    • Backup failed with the reason.
    • Backup cancelled if you cancelled.
  4. The message stays until you close it with the close icon (Dismiss). That way you see the result even if you were elsewhere in the meantime.

While a run is going, Run now turns into Cancel. A cancelled run leaves no half archive behind. If the set is already running, started by its schedule or another click, WebDonkey says this backup is already running and does not start a second one.

A run by hand needs the database servers running. If one is not, the run fails with the reason, and you start the server on the Databases page. A scheduled run backs up only the files in that case, see Schedule, storage location and retention.

Backups made

Backups made lists every archive of all sets, newest first. Archives on a card shows the same list for that set only. For each archive you see name, date, size and on this Mac. If it holds folders and databases, its parts are indented below: one Files line with the backed-up paths and one line per database.

Button What it does
Restore all… or Restore… Opens the dialog for restoring the whole archive, see Restore a backup.
Restore… on a part line Restores only this folder part or only this database.
Save as… on a part line Saves exactly this part as a file of its own, such as a database dump.
Show in Finder Shows the archive in Finder.
Trash can Asks Remove backup from the list? and deletes the entry and its archive on this Mac. If the archive is in a folder of your own, WebDonkey only removes the entry, unless you tick Also delete the file?.

Above the list are tools for tidying up:

  • Check files looks whether the archives are still on this Mac. Missing ones then carry File missing. If none is missing, it says “No missing files found.”
  • Remove missing entries (n) takes the entries without a file off the list. Nothing is deleted.
  • Remove failed (n) takes failed runs (badge failed) off the list.

If a different file than the one the backup wrote now sits at an archive's path, the entry carries File changed. WebDonkey does not touch that file. The entry can only be removed from the list, the file stays where it is.

What happens in the background

  • An archive is a file ending in .wdbak, an ordinary ZIP archive inside. It is named after the set with date and time in UTC, for example My_project-20261106-020000.wdbak. Spaces and special characters in the name become _. It holds the folders, one SQL dump per database and a list of its contents.
  • WebDonkey dumps the databases to a temporary file first and then packs everything. If a database fails, no half archive is written.
  • If a set has two folders with the same name, such as two public folders, WebDonkey keeps them apart in the archive (public, public-2).
  • Every run, by hand or scheduled, appears in the WebDonkey journal with reason, duration, archive path and size.
  • A scheduled run reports its result in the bell. Turn that off under Notifications at Backup created.

Tips

  • Back up by hand before big changes as well.
  • Exclude large folders that can be regenerated, such as node_modules or vendor.
  • Run Check files now and then to see whether the archives on an external drive are still there.

See also

Restore a backup Premium

From any archive of your backup sets you bring back everything or single parts: the folders, one database or both. Nothing is overwritten without asking. Before overwriting a database, WebDonkey backs up its current state, and a replaced folder stays next to the new one under another name.

Where to find it

Sidebar Local › Backups, in the Backups made list (or in a set's Archives dialog):

  • Restore all… on the archive: everything it holds.
  • Restore… on the Files line or on a database: only that part.

If an archive holds only one kind of content, the button on the archive is simply called Restore….

How to do it

  1. Click Restore all… or Restore…. Restore from backup opens.
  2. Folders and files lists every backed-up folder with its target and a check box in front. Untick a folder that should not come back.
  3. Under How the folders come back, choose whether WebDonkey replaces or merges the folders (see below).
  4. Under Databases, tick the databases that should come back. When opened with Restore all…, none is preselected. When opened from a database's line, exactly that one is selected.
  5. For each selected database, choose the server (Database entry, for example MySQL) and the Target database (Choose a database…).
  6. Click Restore….
  7. The confirmation Overwrite on this Mac? lists what gets overwritten. For each database it shows dump, source, backup date, target database and server. Type the name of each target database into its field, then Overwrite unlocks.
  8. The progress shows Checking space, Unpacking and, when replacing, Swapping the folders. At the end the dialog tells you what came back and where the previous folders are.

A folder's target

Each folder comes back into the folder it was backed up from (Origin). If you want it somewhere else, for example to look at an old version next to the current one:

  1. Click Change… at the folder and pick the target in Finder.
  2. The folder then shows Mapped by you. The mapping is saved right away and also applies to future archives of this set.
  3. Back to origin removes it again.

Replace or merge folders

Choice What happens
Replace folder The folder becomes what the backup holds. The current folder stays next to it under a new name, and subfolders the backup left out on purpose (such as node_modules) are taken over into the new one. This needs room for both. It is not possible with older archives that carry no list of their contents, the choice is then disabled.
Merge Files from the backup overwrite files of the same name in the folder, everything else there stays. This cannot be taken back.

After replacing, the report names for each folder where the previous one is now. WebDonkey leaves these folders where they are. Delete them yourself once you no longer need them.

Databases

  • You pick the Target database from the databases of the chosen server. System databases are not listed.
  • If there are several snapshots of a database, choose the one you want under Snapshot.
  • The target database is always backed up first: an SQL backup of its current state in the folder for database backups. So the restore can be undone, see Backup and restore.
  • If no matching server is installed in WebDonkey, the dialog says: “No database server of this kind is installed in WebDonkey. Install it under Databases.”
  • As when restoring on the Databases page, WebDonkey asks if the dump comes from another server version or contains foreign DEFINERs. Do not restore then leaves out that database, the other parts carry on.

Good to know

  • If the space on the Mac may not be enough, the dialog warns you beforehand with the space needed and the space free.
  • WebDonkey does not restore files whose name would put them outside the target folder. The report names them.
  • If an older archive packed two folders of a set with the same name into one folder, WebDonkey does not restore that part, so that no folder gets the other one's files. Save it with Save as… then and sort it by hand. New archives keep such folders apart.

Free and Premium

Restoring is Premium. Without Premium you still get at your data: an archive is an ordinary ZIP archive with the ending .wdbak that you can unpack with unzip in the terminal, for example.

See also

Manage categories Premium

Categories group your backup sets, for example by client projects, websites or shops. On the Backups page the cards then appear under the heading of their category, with a colored dot in front. Sets without a category appear under Uncategorized.

Where to find it

Sidebar Local › Backups, Categories at the top right.

How to do it

  1. Click Categories. Manage categories opens. If there are none yet, it says “No categories yet.”
  2. Enter a name under New category, for example “Client work”.
  3. Pick a color with the color field (Color).
  4. Click Add. The category appears in the list above.
  5. Close the dialog with Close.
  6. Open a set with the pencil and choose the new category under Category (see Create a backup set).

The trash can next to a category (Delete) removes it. The sets in it stay and move to Uncategorized.

See also

Cookie preferences

This website uses cookies to ensure the best experience possible. Your choice applies to webdonkey.io and the shop at shop.webdonkey.io. More information...

Technically required

Cookies required for this website to function:

Always on
WebDonkey
WebDonkey
Provider: BuI Hinsche GmbH, Neumarkt 7, 06712 Zeitz, Germany
Purpose: Your consent, colour scheme and language for website and shop, price switches; with wd_debug in the address, the measurement events in the developer console for troubleshooting
Cookies and storage: Cookie wd_consent on .webdonkey.io, shared with shop.webdonkey.io (12 months); cookies wd_theme and wd_lang on .webdonkey.io, shared with shop.webdonkey.io, only when you switch colour scheme or language yourself (365 days); localStorage wd:consent, wd:theme, wd:lang; sessionStorage wd:acc, wd:term, wd:debug (only with wd_debug in the address; until the tab closes)

Statistics

Shows us which pages and products people look at on webdonkey.io and in the shop, where visitors come from and how they get to a purchase (with order number, amount and products, without name or email address). Provider: Google. Transfer to the USA possible (EU-US Data Privacy Framework). Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Google Analytics 4
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Usage statistics: page views, clicks, scroll depth, sources, devices, load times; in the shop also basket, checkout, purchases, registration and sign-in
Cookies and storage: _ga, _ga_<ID> (2 years)
Privacy policy

Marketing

Measures whether our ads on Facebook, Instagram and TikTok lead to visits and downloads on webdonkey.io and to registrations and purchases in the shop, and builds audiences for ads. Providers: Meta and TikTok, with whom we are jointly responsible for this. With this consent Google may also set advertising cookies (_gcl_…). Transfer to the USA and other countries outside the EU possible. Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Meta Pixel (Facebook, Instagram), TikTok Pixel
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Meta Pixel (Facebook, Instagram)
Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland
Purpose: Ad measurement and target groups on Facebook and Instagram, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _fbp (3 months), _fbc (3 months, only if you arrive through an ad), fr on facebook.com (3 months)
Privacy policy
TikTok Pixel
Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland
Purpose: Ad measurement and target groups on TikTok, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _ttp, _tt_enable_cookie (13 months)
Privacy policy