Buy

Remote › Backups

Premium

The Remote backups page backs up folders and databases on your servers. WebDonkey builds the archive on the server itself: one tar holding the files and the database dumps. The archive stays in a folder on the server or is fetched to your Mac. A backup runs by hand or on a schedule. Remote backups are a Premium feature.

What you do here

Dumps you make on the Database card of a remote database land in the same list, see Back up a database.

Page layout

  • Header: title and short description, on the right New remote backup. The button is locked as long as there is no SSH connection. Add one under Connections first.
  • Risk notice: the strip Caution: working directly on the server reminds you that Remote features work on real servers. More shows the full text, Got it hides it, Don't show again turns it off. You switch it back on under Settings › General at Remote notices.
  • Connections (left): your servers with the search field Search connections…, your folders and All connections. Each server shows how many backups it has. Pick a server and the page shows only its backups and archives, and a new backup starts with that server. The choice applies to all Remote pages and survives a restart. Collapse folds the list into a narrow strip at the edge, Show connections brings it back. In a narrow window it folds by itself.
  • Run without the app open: a notice whether macOS may start scheduled runs while the app is closed, with Set up and Settings. See Schedule and retention.
  • The backup cards: name, server, schedule, the paths and databases saved, Last run, the next run and the Storage. On the right the buttons Back up now, Archives, Open in Finder (only when kept on this Mac), Check space, edit (pencil) and delete (bin).
  • Remote backups made: every archive a Remote feature made, see The backup list.

Without any backup the page says No remote backups yet. with a button to create one. With a server picked that has nothing yet, it says Nothing here for … yet.

Free and Premium

Remote backups are entirely Premium. Without Premium a lock lies over the page and scheduled runs no longer start. Your backups and their archives stay stored and run again once Premium is active. Prices are at webdonkey.io/pricing.

From the command line

wd remote backup lists the backups. With run, add, edit and delete you start, create, change and delete them. More under Servers (Remote).

Create a backup Premium

A remote backup describes what is saved from which server, where the archive goes and when it runs. You create it once, then start it by hand or let it run on a schedule. A backup can save folders, files and databases together, or just one of them.

Where to find it

Sidebar Remote › Backups, then New remote backup at the top right. You open an existing backup with the pencil on its card; the dialog is then called Edit remote backup.

How to do it

  1. On the left, pick the server the backup belongs to and click New remote backup.
  2. Enter a Name, for example "Full shop". Check the Server.
  3. Under Paths, add the folders and files: type a path in the field and click Add (or press Enter), or pick them on the server with Browse….
  4. Under Do not back up, list what should be left out, such as var/cache or node_modules.
  5. Under Databases, pick the server's databases and the format of each.
  6. Choose the Storage location: On this Mac (WebDonkey backup folder) or On the server with a folder.
  7. Set Schedule and Retention if you want, see Schedule and retention.
  8. Click Save. The backup appears as a card. Nothing is saved yet: start the first run with Back up now, see Run a backup and check space.

Save unlocks once there is a name, a server and at least one path or database, for a server destination also the target folder, and once the file name and the cron expression are valid. A path still standing in the input field is taken along when you save.

Fields and options

Name and server

Field Meaning
Name What the backup is called on its card and in the list. It can also be part of the archive's file name.
Server The SSH connection that is backed up. The server picked on the left is preselected. When editing, the server can no longer be changed. Switching the server of a new backup removes the databases you picked, because they belong to the old server.

A new backup you have not saved yet stays as a draft, even when you leave the page. Cancel discards it. If you have already filled something in and picked another server on the left since, the dialog says so: This draft is for …; … is chosen in the list.

File name of the archive

The field File name of the archive sets the name without its ending; WebDonkey adds .tar. The buttons + Name, + Server, + Date and + Time insert placeholders at the cursor. The default is {name}_{date}_{time}. Default name resets the field to it.

Next archive: shows what the next file name looks like. Date and time are written as 2026-09-29 and 09-16-00. Letters, digits, spaces, -, _, . and the placeholders are allowed, at most 120 characters. The field marks any other character in red.

Without date or time the same name can come up again. WebDonkey still never overwrites an archive; it appends -2, -3 and so on. The note below the preview says so too.

Paths

  • Type a path on the server into the field, such as /var/www/shop, and take it with Add or Enter. Paths without a leading / and paths starting with ~/ count from the SSH user's home folder.
  • Browse… opens the server browser Choose on the server. There you tick several folders and files with the box in front of each row (Select) and take them with Add selected. Use this folder takes the folder that is open.
  • The x at a path removes only that path.
  • While nothing is entered, the list says No paths yet.

If a path you entered is a symbolic link, such as public_html or current, WebDonkey saves the content it points to. A link that leads nowhere counts as missing.

Do not back up

One pattern per line, relative to each path above:

  • var/cache leaves out <path>/var/cache and everything in it.
  • A pattern without / matches that name at any depth, such as node_modules or *.log.
  • * and ? work as in the shell.

What is left out does not count in the space check either. A pattern must not lead out of the paths (no ..), and at most 100 patterns are possible.

Databases

The databases come from the entries under Remote › Databases for this server. If the server has several entries, first pick the entry, then the database in the field Choose a database… (with its size), and click Add. If the server has no entry yet, it says: This server has no database yet. Add one under Remote › Databases.

Each database picked stands as a row with its format and the file it becomes in the archive (db/<name> with the ending of the format; a name already taken gets -2, -3).

Format File in the archive Restorable
SQL (default) .sql yes
SQL (gzip) .sql.gz yes
PostgreSQL archive (PostgreSQL only) .dump yes
CSV (ZIP) .zip no, for other programs only
JSON .json no, for other programs only

A database can be backed up without any folder. If its database entry has been deleted since, the row shows in red until you remove it with the x.

Storage location

  • On this Mac (WebDonkey backup folder): WebDonkey fetches the finished archive to your Mac. Without a folder it lands in WebDonkey's backup folder, inside remote in a folder per server. With Choose folder, or by typing, you use a folder of your own. In a folder of your own, the retention deletes only archives this backup wrote there, recognised by their name and by WebDonkey's list of what it wrote, never other files.
  • On the server: the archive stays on the server, in the folder you type or pick with Browse…. The folder must not lie inside one of the folders being backed up, or every run would pack the previous archives again.

Edit and delete

  • The pencil opens Edit remote backup with the same fields. Changes apply from the next run.
  • The bin asks Delete remote backup?. The backup and its schedule are deleted, and its failed attempts leave the list. Archives already made stay in the list and on disk. If the archives are kept on your Mac, Also delete its archives on this Mac deletes them too.

Troubleshooting

What you see Why What to do
New remote backup is locked There is no SSH connection. Add one under Connections.
Paths must be absolute, and "/" itself cannot be backed up. A path is /, the whole server. Enter the folders you actually need.
Paths with “..” are not allowed … The path climbs up with ... Enter the folder directly.
The archive destination lies inside a folder that is backed up … The target folder on the server lies inside a saved path. Choose a destination outside it.
This “Do not back up” pattern is not allowed … The pattern contains .., or there are more than 100. Keep patterns inside the paths.
One of the databases does not belong to this server … The database comes from another server. Remove it and choose it again.
A character of the file name is marked red The character is not allowed in the file name. Use letters, digits, spaces, -, _, . and the placeholders.

See also

Run a backup and check space Premium

Back up now starts a run of a remote backup right away. First WebDonkey checks whether there is enough room on the server and, where needed, on your Mac. Check space shows you these numbers without a run, so you know up front whether the backup fits.

Where to find it

Sidebar Remote › Backups, the buttons Back up now and Check space on a backup's card.

How to do it

  1. Click Back up now on the card.
  2. A bar with the current phase appears below the card. During the run the button reads Cancel.
  3. When it is done, the card says Backup made with the size and the location (on this Mac or the path on the server). The archive appears under Remote backups made.

You can switch to other pages meanwhile. The run goes on, and when you come back the card shows how far it is or how it ended.

Check the space up front

  1. Click Check space.
  2. A box with Enough space. or Not enough space. and the numbers appears below the card.
  3. The x at the top right closes the box.

The phases of a run

Phase What happens
Checking space WebDonkey measures the folders and the databases and compares them with the free space.
Dumping databases Each database picked is written to a dump on the server.
Packing on the server Folders and dumps go into one tar archive.
Downloading Only when kept on this Mac: the archive comes to your Mac.

While dumping, packing and downloading, the bar shows the progress in percent and the amount, while downloading also the total size. While packing the display stays below 100 % until the server reports it is done, because the total was measured beforehand.

Cancel ends the run in every phase. Dumps and archive on the server are then cleaned up.

What the space check shows

Line Meaning
Folders: … · Databases: … How large the folders (without what is under Do not back up) and the databases are.
On the server (…): needs up to …, free … The folder on the server where the work happens, the most the backup needs there and how much is free.
On this Mac: free … Only when kept on this Mac: the free space there.
Not found on the server: … Paths of the backup that do not exist on the server.

Whatever does not fit is marked in red.

What happens in the background

  • Before every run WebDonkey checks the space. If the backup may not fit, or would leave less than 10 % free, the dialog Not enough free space asks first, because a full disk can bring down a running server. It shows the same numbers as Check space. Run anyway starts the run, Cancel leaves it.
  • On the server a private work folder is created. WebDonkey writes the dumps into db/ there and packs everything with a single tar. The archive is not compressed, which is what makes the progress measurable. It carries a list of its contents that a restore uses later.
  • Kept on the server: the finished archive is moved into place in the target folder, and only then does it carry its final name. There is never a half-written archive under that name.
  • Kept on this Mac: WebDonkey downloads the archive, compares its size with the archive on the server and then deletes the work folder on the server. The archive appears in the target folder on your Mac only once it is complete.
  • Permissions: archives and work folders on the server can be read only by your SSH user, file backups without a database included.
  • Checking the archive: if packing is cut off, or the archive is empty or far smaller than the folders it should hold, the run counts as failed and the archive is discarded.
  • One run at a time: a backup never runs twice at once, whether its schedule, a click or WebDonkey Editor started it.
  • Quitting: if you quit WebDonkey while a backup runs on the server, Quit WebDonkey? asks first.

Notes after a run

A run can succeed and still leave something out. The card says so after Backup made, and so does the entry in the list:

  • Left out while packing, because the SSH user may not read them: …: files and folders that belong to the web server's user, for example (caches, sessions), with their number and the first paths. Everything else is in the archive.
  • Some files changed while they were packed.: the archive is complete, but single files may hold an intermediate state.
  • Not in the backup: the events of …: the database account lacks the EVENT privilege. Without it the server does not even show which events exist. Everything else was saved.

Free and Premium

Running and checking space are part of Premium. Without Premium no run starts.

Troubleshooting

What you see Why What to do
The SSH user may not read this path: … A path you entered is closed to the SSH user entirely. The run stops before packing. Take the path out or give the user read access.
The destination folder on the server cannot be written to: … The target folder is missing or read-only. Choose a folder the SSH user may write to.
Could not create a work folder on the server. No work folder can be created on the server. Check permissions and free space on the server.
The database client (mysqldump / pg_dump) is missing on the server. The program for the dump is missing. Install the client on the server or take the database out.
The dump of … on the server is incomplete … The dump ended too early. The backup was not kept. Run again and check the database's logs.
The archive is far smaller than the folders it should hold … Packing was cut off, for example by a hosting limit. Nothing was saved. Run again, leave large folders out under Do not back up or split them into several backups.
Downloading the archive failed The connection broke off, or not everything arrived. Run again.
This remote backup is already running … Its schedule or another click started it already. Wait until that run is done.
Backup cancelled. You clicked Cancel. Nothing to do; the server has been cleaned up.
A scheduled run is listed as failed There was not enough free space. A scheduled run cannot ask and is skipped. Make room, or start it once by hand with Run anyway.

See also

Schedule and retention Premium

A remote backup can run by itself: every hour, every day, every week or by a cron expression. The retention sets how many archives are kept. WebDonkey removes older ones after each run, on your Mac and on the server.

Where to find it

In the dialog New remote backup or Edit remote backup, the sections Schedule and Retention at the very bottom.

How to do it

  1. Open the backup with the pencil on its card.
  2. Under Schedule, choose Every day at Run, for example, and set the time at At.
  3. Under Retention, choose Keep multiple backups at Backup handling and enter the number at Backups to keep.
  4. Click Save. The card now shows the schedule, such as "daily at 02:30", and the next run.

Fields and options

Schedule

Field Meaning
Run Manual only (default), Every hour, Every day, Every week or Cron expression….
On Only with Every week: the weekday.
At With Every day and Every week: the time, default 03:00.
Schedule (cron expression) Only with Cron expression…: five fields for minute, hour, day of month, month and weekday, default 0 3 * * *. Below it are presets to click: Every minute, Every 15 minutes, Hourly, Daily at 03:00, Weekdays at 09:00, Mondays at 03:00. An expression that is not valid is marked red (Not a valid cron expression.), and Save stays locked.

Below the fields one sentence says when the backup runs, for example "Runs every day at 03:00.", followed by a note on who starts scheduled runs.

Retention

Field Meaning
Backup handling Keep only the newest: each run replaces the previous archive. Keep multiple backups: several complete archives stay. The default is Keep multiple backups.
Backups to keep How many successful archives stay, at least 2, default 10. Older ones are deleted.

What happens in the background

  • Who starts it: scheduled runs use the same scheduler as local backups. It runs while WebDonkey is open. A run that was missed because WebDonkey was closed runs at the next start.
  • Without the app open: with Run on schedule without the app set up under Settings › System, macOS starts the runs while the app is closed as well. That needs your administrator password once. The card then shows runs without the app. You can also use the notice Run without the app open at the top of the page directly with Set up. After a WebDonkey update it reports Update needed; set it up once more then. More under Run without the app open.
  • No room, no run: a scheduled run cannot ask. If the backup may not fit, the run is skipped and listed as failed. The entry says how much room was needed and how much was free.
  • Cleaning up: after each successful run WebDonkey deletes the successful archives of this backup beyond the number at Backups to keep, on the server too. What may go is decided by this backup's list of runs, never by a file name. A file WebDonkey did not write itself, or one that has changed since, stays where it is; only its entry goes. The same applies in a folder of your own on your Mac.
  • WebDonkey Editor: the editor shows the same remote backups. Scheduled runs are started only by WebDonkey (or by macOS, if scheduling without the app is set up), never by the editor. Back up now works in the editor.

Free and Premium

Schedules are part of Premium. When Premium ends, scheduled backups stop. The schedule stays stored, and with Premium back, missed runs are caught up once.

Troubleshooting

What you see Why What to do
A scheduled run did not happen WebDonkey was closed and scheduling without the app is not set up. Set up Run on schedule without the app under Settings › System.
The notice shows Permission missing The permission for macOS is missing. Set it up again.
Save stays locked The cron expression is not valid. Fix the expression or click a preset.
Old archives disappear The retention cleans up. Raise Backups to keep.

See also

The backup list Premium

The list Remote backups made shows every archive a Remote feature made: the runs of your remote backups and the dumps from the Database card of a remote database. From here you restore, download archives, show them in Finder and tidy up the list.

Where to find it

  • Sidebar Remote › Backups, at the bottom of the page the section Remote backups made. With a server picked on the left, the list shows only its entries.
  • Only the archives of one backup: the Archives button on its card. A window with the same list for that backup opens.
  • On the Backups page, All remote backups leads here once there are remote archives.

How to do it

  1. Find the entry. The newest archive is at the top.
  2. If the archive is on your Mac, Show in Finder shows the file.
  3. If it is on the server, Download fetches a copy to your Mac.
  4. Restore… opens Restore from a backup.
  5. The bin removes the entry, see below.

What an entry shows

Part Meaning
Icon Archive of a remote backup, database icon for a dump of the Database card.
Name The name of the backup or the database.
Remote Mark for archives of a Remote feature.
Format Such as TAR for an archive of a backup, or the format of a dump.
failed The run made no archive. The reason is below.
File missing Check files no longer found the file on this Mac.
File changed A different file lies at the path than the one the backup wrote.
Second line Server, date, size and on this Mac or on the server.
Note line What the run left out or why it failed, see Run a backup.

If an archive holds folders and databases, its parts are indented below it, see Partial restore. The entry's own buttons then read Restore all… and Download all.

Buttons at an entry

Button When What it does
Restore… Successful archives whose file is there and whose server is still a connection Opens the restore dialog.
Show in Finder Archives on this Mac Shows the file in Finder.
Download Archives on the server Downloads a copy into WebDonkey's backup folder for this server and shows it in Finder. The archive on the server stays.
Bin Always Removes the entry after asking.

Removing entries

The bin asks Remove backup from the list?. The dialog says what happens to the file:

  • Archive on this Mac: the entry and its archive on this Mac are deleted.
  • Archive on the server: only the entry is removed. The archive stays on the server; the dialog names the path.
  • Archive in a folder of your own: the entry is removed. Also delete the file? deletes the file as well.
  • File missing: only the entry is removed.
  • File changed: only the entry is removed, the file stays where it is.

Tidying up

Above the list are three tools:

  • Check files looks whether the archives of this list are still on this Mac. Missing ones then carry File missing. If nothing is missing, it says No missing files found. Archives on a server are not checked.
  • Remove missing entries (n) appears when files are missing. It removes those entries without deleting any file.
  • Remove failed (n) appears when there are failed attempts and takes them off the list. Archives are not affected.

Exports

CSV and JSON files from the Database card stand in a section of their own, Exports, below the list. These are files for other programs; they cannot be restored. The bin there asks Remove export from the list? and deletes entry and file on this Mac.

What happens in the background

  • The list reads itself again every 15 seconds and shows up to 200 entries.
  • WebDonkey only touches files a run wrote itself. If a different file lies at a path by now, replaced by hand for example, the list marks the entry File changed. It then offers nothing but removing it from the list; the file itself stays.

Troubleshooting

What you see Why What to do
Restore… is missing The run failed, the file is missing or changed, the server is no longer a connection, or it is an export. Check the entry. A deleted archive cannot be brought back.
The file … is no longer the one this backup wrote … The file was replaced or changed. Remove the entry. The file stays where it is.
The file of this backup is no longer on this Mac. The file was moved or deleted. Remove missing entries or put the file back.
No remote backups yet. There has been no run yet. Start a backup with Back up now.

See also

Restore from a backup Premium

Restore… puts folders and databases of an archive back on the server. This overwrites data on a running server. That is why you pick every part yourself, check the target and confirm a database by typing its name. Before each database, WebDonkey backs up its current state if you want; that safety backup is preselected.

Where to find it

Sidebar Remote › Backups, under Remote backups made the Restore… button at an entry (Restore all… for archives with several parts). The same is in the Archives window of a backup card.

How to do it

  1. Click Restore… at the entry. The dialog Restore from backup opens. Its subtitle names the archive, date and server.
  2. Read the red box A restore overwrites data.
  3. Under Folders and files on the server, check which folders come back and where to. Untick what you do not want back.
  4. At How the folders come back, choose between Replace folder and Merge.
  5. Under Databases, tick the database that should come back. Choose Database entry and Target database, with several dumps also the Snapshot.
  6. Leave Back up the current state first ticked.
  7. Click Restore…. The dialog Overwrite on …? lists everything that is overwritten.
  8. For each database, type the name of the target database exactly as it is shown. Only then does Overwrite unlock.
  9. Click Overwrite and follow the progress in the dialog.

A single part, such as just one database, is quicker through its own row in the list, see Partial restore.

Fields and options

Folders

Each folder of the archive is listed with its path and size, below it the folder on the server it comes back to.

Element Meaning
Tick Restore this folder. Folders are preselected.
Origin The folder goes back where it was saved from.
Mapped by you You chose another target.
Change… Opens Choose the target folder on the server. The mapping is saved at once and also applies to future archives of this backup (Saved. It also applies to future archives of this backup.).
Back to origin Removes your mapping.

How the folders come back

  • Replace folder (default): the folder becomes what the backup holds. The folder that is there now stays next to it under a new name, and subfolders the backup left out on purpose (Do not back up) are taken over. That needs room for both. Archives without a list of their contents cannot do this; then only Merge is possible.
  • Merge: files from the backup overwrite those on the server, whatever else lies there stays. This cannot be taken back.

Databases

A database is never recognised and put back by itself. It is not preselected, and WebDonkey proposes neither entry nor target database, because a wrong dump or a wrong target database does great harm.

Field Meaning
Tick Restore this database. Its engine and format stand next to it.
Snapshot Only when there are several dumps: This backup with its date, or a dump from the Database card with date and size. Databases of which only the Database card has dumps get a row of their own, marked Database card.
Database entry Which entry under Remote › Databases restores it (Choose an entry…). Only entries of the matching engine on this server are offered.
Target database Which database the dump goes into (Choose a database…). The databases of the entry and the name from the backup are offered.
Back up the current state first Preselected. WebDonkey first saves the target database as an SQL backup that appears in the list like any other. That way the restore can be undone. If you untick it, the dialog warns in red: without a backup nothing can be taken back, and if the restore fails partway, a MySQL or MariaDB database stays half restored.

CSV and JSON exports cannot be restored. If the server has no matching entry, the row says: This server has no matching database entry. Add one under Remote databases.

The confirmation

Overwrite on …? names the server and starts with The following is overwritten with the backup from …:. For each folder it says whether it is replaced or receives the files. For each database it lists Dump, Source, Backup date, Target database (in red), Database entry and Server, below them the field Type the name of the target database to confirm. Upper and lower case count. At the end it says A safety backup is taken first. or, without one, warns in red that nothing is backed up.

What happens in the background

The parts you picked run one after the other: first all folders, then each database. Every part has its own row with its state (Waiting, progress, done or error) and its Cancel button. A part that fails or asks does not hold up the others.

For the folders the row shows these phases: Checking space, Sending the archive to the server (only when the archive is on your Mac), Unpacking on the server and, when replacing, Swapping the folders. A database shows Restoring…. A finished part reports Restore finished.

After replacing, the row 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. What the SSH user was not allowed to write is reported as Could not be written on the server: ….

If a part cannot go on without you, its row asks:

  • Space: the folders may not fit on the server. Replacing needs room for both versions; if it does not fit, the folder stays as it is. Restore anyway or Do not restore.
  • Version jump: the dump comes from another server version. Across versions a restore can fail or turn out differently. Restore anyway or Do not restore.
  • DEFINER: views, routines, triggers or events run as an account that does not exist on the target. Rewrite DEFINER to … lets them run as the account that restores. The file itself stays unchanged.

Retry starts a cancelled or failed part again. If a database with a safety backup fails, WebDonkey puts it back as it was from that backup and says so.

Free and Premium

Restoring is part of Premium.

Troubleshooting

What you see Why What to do
Restore… in the dialog stays locked Nothing ticked, or a database lacks entry or target database. Choose both or untick it.
Overwrite stays locked A name is not typed exactly. Type the name of the target database character by character.
The folder … cannot be replaced … It is the home folder, the folder above it cannot be written, or something that is not a folder lies there. Close the dialog and choose Merge, or map the part to another folder.
The SSH user may not write to this folder Missing write permission at the target. Check permissions or map another target.
Another restore of folders is already running. Another dialog is restoring folders right now. Wait until it is done.
The mapping of this backup was changed in the meantime … Another window mapped the folders anew. Nothing was written. Close the dialog, open it again and check the folders.
Cancelled. Files already written stay. You cancelled the folders. Check the folders, start again if needed.
This older backup packed the folders … into one folder … An old archive mixes folders of the same name. Save the folders as a file and sort them by hand, see Partial restore.

See also

Partial restore Premium

If an archive holds folders and databases, the list shows its parts one by one: a row Files with the paths saved, and a row per database. That way you restore only what you need, or take a single part as a file without restoring it.

Where to find it

Sidebar Remote › Backups, under Remote backups made, indented below an entry. Parts appear only for successful archives of a remote backup whose file is there and unchanged and that hold both. An archive with only folders or only databases stays one row.

How to do it

Restore just one part

  1. Find the entry and the row of the part below it.
  2. Click Restore… in that row.
  3. The dialog Restore from backup shows only this part. Its subtitle says Files (the folders without the databases) or Database … (only this database without the folders).
  4. For a database the tick is already set, because you chose it explicitly. You still choose entry and target database yourself.
  5. Go on as under Restore from a backup.

Save one part as a file

  1. Click Download… in the row of the part (archive on the server) or Save as… (archive on this Mac).
  2. Pick place and name in the macOS save dialog. It proposes the archive's name with -files.tar for the folders, or with the file name of the dump.
  3. While it transfers, the button reads Downloading… or Saving…. Finder then shows the file.

The folders come as one tar, a database as its dump. That way you get a single database out of a large archive without touching the other parts.

What the rows show

Row Content Buttons
Files The paths saved, separated by · Restore…, Download… or Save as…
Database The database's name Restore…, Download… or Save as…

For archives with parts, the entry's own buttons read Restore all… and Download all.

Troubleshooting

What you see Why What to do
No part rows The archive holds only one kind of content, the run failed, or the file is missing or changed. Use the entry's buttons, or check it with Check files.
This part is not in the backup The dump is missing from the archive. Use another archive.
The file … is no longer the one this backup wrote … The archive file was replaced. The entry then carries File changed. Remove the entry.

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