BackupDesk
User Guide — version 1.2.0
BackupDesk backs up folders on a schedule and lets you get them back. It is a job-based backup tool: you describe what to protect, where it goes and when it runs, and then operate it — jobs queue, run, report progress, and can be paused or cancelled.
If you have used Windows File History, OneDrive or Google Drive, BackupDesk is a different kind of thing. Those continuously mirror a folder somewhere. BackupDesk takes deliberate backups at levels you choose, keeps a history of them, and gives you control over how long they are kept.
Contents
- First run
- The screens
- Creating a backup job
- Backup levels and schedules
- Retention — how long backups are kept
- Running, pausing and cancelling
- Restoring
- Checking a backup is intact
- Backing up from another machine (FTP, FTPS, SFTP)
- Backing up to Google Drive
- Backing up to OneDrive
- Compression
- Encryption
- Settings
- Free version and BackupDesk Pro
- What a backup actually looks like on disk
- Troubleshooting
1. First run
BackupDesk has two parts: the window you open, and a background service that does the actual backing up. The service runs whether or not the window is open — that is what lets a backup happen at 2am while you are asleep.
Allowing your account to manage backups
The first time you open BackupDesk you may be asked to allow your account to manage backups, with one confirmation from Windows.
This is asked because the background service can read every file on the computer, so only approved accounts are allowed to control it. You confirm once and are never asked again.
If the computer is managed by someone else, an administrator can approve your account for you, including from a command prompt:
net localgroup "BackupDesk Operators" <username> /add
It takes effect the next time that user signs in.
The window and the tray
Closing the window does not stop BackupDesk — it keeps running in the notification area so scheduled backups still happen. Right-click the tray icon to reopen it, or to quit properly. You can turn this off in Settings if you would rather closing the window closed the app.
Hearing about problems without opening BackupDesk
Once you have opened BackupDesk once, it starts in the notification area each time you sign in to Windows, without opening a window. If a backup failed while you were away — overnight, or while the computer was off — you are told as soon as you sign in. Several results at once arrive as one notification.
You can turn this off in Settings → Start in the notification area when I sign in, or in Windows’ own list of startup apps. Backups still run either way; only the announcements stop.
2. The screens
| Screen | What it is for |
|---|---|
| Dashboard | The state of everything at a glance: what ran, what failed, what is due. |
| Backup Jobs | Your jobs. Create, edit, clone, enable, disable and start them. |
| Activity | What is running or queued right now, with progress. |
| Stored backups | Every backup set on each destination, and what depends on what. |
| Restore | Getting files back. |
| History | Every run that has finished, successful or not. |
| Settings | Machine-wide preferences, and the cloud accounts jobs can back up to. |
| About | Versions, and diagnostics to copy into a support message. |
A job whose latest backup failed says so in plain words — for example “The last backup failed yesterday. The last good one was 9 days ago.” — rather than only when it last ran.
3. Creating a backup job
Press + New Backup Job. A job needs three things. Everything else has a working default.
Sources — what to protect
Add one or more folders. A job can have several, and they can be on different drives. Sources may also be on another machine over FTP, FTPS or SFTP — see §9.
Exclusions let you skip things that are not worth backing up. BackupDesk suggests common ones (build output, caches, temporary files) which you can accept or ignore, and you can add your own patterns.
Destination — where it goes
A local folder, an external drive, a network share, or a folder in a Google account (§10) or a Microsoft OneDrive account (§11).
If it is still waiting when the job’s next backup is due, BackupDesk tells you. From then on the job is not protecting anything.
Network folders. BackupDesk writes to network folders as this computer, not as you, so a share you can open yourself may still refuse it. If that happens the backup fails straight away and says so: give this computer write access to the folder, or choose another destination.
Schedule — when it runs
Either pick a preset or build your own. See §4.
Impact — how much of the machine it uses
| Profile | What it does |
|---|---|
| Low impact (default) | Gentle on the computer. A backup should never make the machine feel slow. |
| Balanced | Finishes sooner, and you may notice it. |
| Full speed | As fast as the computer allows. For a maintenance window. |
You can also cap throughput, which is useful when backing up over a network you share with other people.
4. Backup levels and schedules
BackupDesk has three backup levels, and you choose which one each scheduled run uses. This is the core idea of the product, so it is worth two minutes.
| Level | What it stores | What it needs to restore |
|---|---|---|
| Full | Everything. | Nothing else. It stands alone. |
| Differential | Everything changed since the last full. | Its full, and nothing else. |
| Incremental | Everything changed since the previous backup of any level. | Its full and every incremental since. |
The trade-off is space against resilience:
- Differentials grow larger each day until the next full, but a damaged one only costs you that one backup.
- Incrementals stay small every day, but they form a chain — a single damaged incremental spoils every backup made after it.
BackupDesk shows you this where you choose levels, and where you delete backups. It is not trying to scare you off incrementals; it is information you need to make the choice.
Presets
If you would rather not think about it, pick one:
| Preset | What it does |
|---|---|
| Standard | A full once a month, a differential every week, an incremental every other day. A good balance for most machines. |
| Most resilient | A full every week and a differential every day. Uses more space, and no single damaged backup can spoil the others. |
| Smallest daily backups | A full every month and an incremental every day. Uses the least space, but a damaged incremental spoils every backup after it. |
| Manual only | Nothing runs on its own. You start each backup yourself. |
You can edit any preset afterwards — they are starting points, not modes. Once you change a preset’s rows the editor stops calling it by that preset’s name, and picking the preset again puts its rows back.
Why the first backup is slow and the rest are fast
The first run copies everything. After that, BackupDesk skips files that have not changed, which is what makes later runs feel almost instant.
Files that have changed are checked properly, so a file that was merely touched but not edited is recognised as unchanged.
If the computer restarts or sleeps
A backup interrupted by a restart runs again once the computer is back, rather than waiting for its next scheduled time. While a backup is running, BackupDesk stops the computer going to sleep on its own when idle, and lets it sleep again when the backup ends. Closing a laptop’s lid or choosing Sleep still puts it to sleep.
Files in OneDrive folders
Files in a OneDrive folder on this computer are backed up as ordinary files, including ones that are online-only: BackupDesk downloads them so they can be read, just as opening them would. If your sources include a large OneDrive folder of online-only files, the first backup downloads all of them. (This is about OneDrive as a source; to back up to OneDrive, see §11.)
5. Retention — how long backups are kept
Backups are deleted only under rules you set. Without retention, backups grow until the destination fills up and then quietly start failing — exactly when you believe you are protected.
Retention is set per job, in chains. A chain is a full backup plus everything that depends on it. The default is keep the last 3 chains.
Chains are always pruned as a whole, so a full is never deleted out from under the differentials or incrementals that need it.
If a destination fills up during a backup, that backup fails and says the destination is full. It never records a backup as complete with files missing.
Three rules BackupDesk will not break:
- It tells you when it prunes to make room. Silent deletion is not something a backup tool should do.
- It never deletes your last backup that can still be restored, even if the disk is full. You get a loud warning instead. A tool that deletes your last backup to make room for a new one is worse than useless.
- It never prunes a chain you are restoring from, or one a queued restore is waiting to read.
Unfinished backups. A backup that was cancelled or failed part-way leaves a folder that cannot be restored from. BackupDesk removes these itself after the job’s next good backup. Leftovers from versions before 1.1 are listed in the run so you can delete them yourself.
6. Running, pausing and cancelling
- Run now starts a backup immediately, at the level you pick next to the button. It defaults to Full, because a manual backup is usually taken before doing something risky.
- Jobs queue rather than running all at once, so two jobs do not fight over the same disk. A queued job tells you what it is waiting for.
- Cancel always works, and asks you to confirm first, saying what will be lost. A cancelled job never leaves a half-written backup that looks restorable — the set is only committed once it is complete.
- Pause and resume are available during the phases where they make sense.
Watch all of this on Activity. Finished runs move to History.
Following a backup while it runs
Activity shows a progress bar with a percentage, the current speed and an estimated time remaining. View opens a window that follows one backup live: how far it has got, how much has been saved, and how much space it is taking.
7. Restoring
Restoring is a job like any other: it queues, it reports progress, and it appears in History.
There are two ways to find what you want:
- Browse a point in time. Pick a backup set and walk the folder tree as it was at that moment.
- Search across sets. Type a filename to see every version of it in the chosen job’s backups, with the date of each, so you can pick the one from before whatever went wrong. Restore this version restores just that file.
Where it goes
- A folder you choose — safe, and the usual choice.
- The original locations — this overwrites the live files, and BackupDesk says so plainly.
What to do about files that are already there
| Choice | Behaviour |
|---|---|
| Replace files that are different (default) | Leaves identical files alone. |
| Replace every file | Overwrites everything, whether it differs or not. |
| Only restore what is missing | Never touches a file that is already there. Safe when you are unsure what has changed. |
You can restore everything, or tick just the folders and files you need. Before anything starts, BackupDesk shows what it is about to do and asks you to confirm, with a plain warning when it will replace files that are there now.
Backups of a job you have deleted
Deleting a job does not delete its backups. They stay listed under Stored backups and Restore with (deleted job) after the name, and can be browsed, verified, restored or deleted like any other. An encrypted job keeps its key, so its backups still open without the password.
Backups at the same destination made by another computer are listed too, as (no job on this computer), and can be browsed and restored.
8. Checking a backup is intact
Stored backups → Verify re-reads a backup and checks every file in it. This catches bit-rot — a disk quietly corrupting a file that nothing has touched in a year.
Verify works on encrypted backups too, and does not need the password to do it. Even without the password, it notices files that are missing as well as files that are damaged.
Worth running occasionally on anything archival, especially backups kept on a drive that spends most of its life in a drawer.
9. Backing up from another machine (FTP, FTPS, SFTP)
A source folder can live on another machine. Add a server under the job’s sources, then browse it to pick folders.
Supported: FTP, FTPS (FTP over TLS) and SFTP (file transfer over SSH). SFTP also covers anything you would have used SCP for.
Notes worth knowing:
- Test connection checks the server exactly the way the scheduled backup will, so a successful test means the 2am run will connect too.
- Accept an SFTP server’s key when you first connect. BackupDesk will not connect to a server you have not approved.
- SSH private keys are imported into BackupDesk, so moving or deleting the original file afterwards does not affect your backups.
- A destination cannot be an FTP or SSH server. Backups are written to a local folder, drive, network share, or a folder in Google Drive or OneDrive (§10, §11).
- If a server cannot be reached, the run says why — a changed server key, a password that is no longer accepted, or no answer at all.
- A busy server does not fail the backup. A file that disappears or a folder that cannot be opened during the backup is listed, and the rest of the backup completes.
- Shortcuts (links) on a server are not followed. Each one is listed, so you can add the folder it points to as a source of its own if you need it.
- File names with accents or non-Latin letters come through correctly.
10. Backing up to Google Drive
A job’s destination can be a folder in your Google account instead of a folder on this computer. Everything else about the job is unchanged: the same levels, the same schedule, the same retention, the same restore.
Connecting an account
Settings → Cloud accounts → Connect a Google account. Your web browser opens on Google’s own sign-in page. BackupDesk never sees your Google password, and scheduled backups run without asking you anything.
Choosing the folder
In the job editor, next to Browse, use Cloud…. Pick the account, navigate into a folder or create one, then Use this folder. Backups go into the folder shown at the top of the dialog. The picker works from the keyboard too: Enter opens a folder and Backspace goes up.
What is different, and what is not
- Compression and encryption work exactly as they do locally (§12 and §13). An encrypted backup in Drive stores its filenames encrypted too, so the folder names in your Drive give nothing away.
- Deleting old backups genuinely frees space in your Google account. Removing a backup chain reclaims the storage it used, rather than leaving it in the trash.
- A slow or interrupted connection is not a corrupted backup. An upload that does not finish leaves nothing behind — a half-written backup never appears as one you could restore from.
- Being offline is different from an unplugged drive. A job whose destination is a USB disk waits for the disk. A job whose destination is Google Drive does not wait for your connection: if the account cannot be reached when the backup is due, the run fails and tells you, rather than waiting quietly.
- A full Google account stops the backup. If the account runs out of storage during a run, the backup fails and says so, rather than completing with files missing.
- Free space is reported by Google, so the job editor shows that rather than a figure from a local disk.
Backing up a server straight to Google Drive
A job’s source can be on another machine (§9) while its destination is in Google Drive. Nothing is stored on this computer along the way, so backing up 10 GB from a server needs no free space here.
What it does need is the connection to both ends for the length of the run.
If the account stops working
Google can withdraw permission — if you revoke it, or after a long time unused. The account shows what is wrong under Settings → Cloud accounts. Use Test to check it.
To fix it, use Connect a Google account again and sign in with the same Google account. BackupDesk recognises it and repairs the existing connection, so every job that uses it keeps working. There is no need to disconnect it first, and BackupDesk will not let you while a job still uses it.
11. Backing up to OneDrive
A job’s destination can also be a folder in OneDrive, with either a personal Microsoft account (Outlook, Hotmail, Live, MSN) or a work or school account. Everything that works on Google Drive works on OneDrive: full, differential and incremental backups, compression, encryption, browsing, searching, verifying, restoring, retention and deleting backups.
Connecting an account
Settings → Cloud accounts → Connect a Microsoft account. Your web browser opens so you can sign in with Microsoft. BackupDesk never sees your password, and scheduled backups run without you signed in.
Choosing the folder
Exactly as for Google Drive: in the job editor, use Cloud… beside Browse, pick the Microsoft account, open a folder or create one, then Use this folder.
Worth knowing
- Very large files need some free space on this computer while they upload. It is freed automatically afterwards.
- Deleted backups do not go to the OneDrive recycle bin, so the space is really freed. OneDrive’s free-space figure can take a while to catch up.
- Being offline is a reported failure, not a wait — just as with Google Drive (§10).
- If the account stops working, use Connect a Microsoft account again and sign in with the same account. Every job that uses it keeps working, and your existing backups are unaffected.
12. Compression
Off by default. Per job, you can choose:
| Setting | Roughly |
|---|---|
| Faster | Least processor time, least saving. |
| Balanced | The best trade-off for most content — recommended if you want compression at all. |
| Smaller | Noticeably smaller, and considerably slower. |
Files that are already compressed — JPEG, MP4, ZIP, Office documents — are stored as-is, because compressing them again costs processor time and makes them slightly larger.
The compression level you pick is always honoured. The Impact setting is separate and only controls how much of the computer a backup uses.
13. Encryption
Off by default. When turned on for a job, file contents and the list of filenames are encrypted with AES-256, so someone who finds the drive learns neither what your files contain nor what they are called.
Turning it on
You choose a password, and BackupDesk shows you a recovery key.
Either the password or the recovery key will open a backup.
Scheduled backups do not ask for a password
BackupDesk remembers what it needs securely on this computer, so scheduled backups run unattended.
After a rebuilt computer or a reinstall, restoring will ask for the password, and scheduled backups of that job stop rather than run unencrypted. To fix it, turn encryption off and on again in the job and enter the password it was set up with. Earlier backups stay readable.
Turning it off, and changing the password
Backups already written stay encrypted and stay restorable. Only future backups are written unencrypted. A job whose history mixes encrypted and unencrypted backups restores all of them.
Turning encryption on again for the same job keeps earlier backups readable. This is also how to change the password: turn encryption off, then on again with the new password. You are shown a new recovery key — write it down. Backups made before the change still open with the password and recovery key they were made with.
14. Settings
Preferences for this computer. Individual jobs keep their own settings.
| Setting | What it does |
|---|---|
| Background service | Status, whether it can back up open files, and its version. Read-only — this is where you look when something is wrong. |
| Run at most … backups at the same time | One by default: two jobs on the same disk finish later in total than the same two run in turn, and make the machine feel worse while they do it. |
| New jobs start with — keep the last … chains | What a new job starts with. Never changes an existing job. |
| Tell me when: a backup fails | On. This is why notifications exist. |
| Tell me when: a backup finishes successfully | Off. A backup that worked is not news, and a notification per successful nightly run teaches you to ignore all of them — including the one that matters. |
| Tell me when: a drive comes back and a waiting job starts | On. Something has just started running unattended. |
| Tell me when: old backups are deleted to make room | On. |
| Cloud accounts | Connect, test and disconnect the Google and Microsoft accounts a job can back up to (§10, §11). |
| Theme | Follow Windows, light, or dark. “Follow Windows” switches when Windows does. |
| Keep running in the notification area when the window is closed | On. Backups run either way — the service does not need the window open. This only decides whether closing the window also quits the tray icon. |
| Start in the notification area when I sign in | On. So a backup that failed while you were away is announced when you sign in. Applies to your account only. |
Settings also shows whether BackupDesk Pro is active on this computer.
15. Free version and BackupDesk Pro
The free version of BackupDesk runs one backup job.
That one job is not limited in any way. All three levels, schedules, retention, snapshots of open files, remote sources, cloud destinations, compression, encryption, verify and restore all work fully. The limit is on how many jobs you can have, and nothing else.
BackupDesk Pro is a one-time purchase through the Microsoft Store that removes the limit on the number of jobs. It changes nothing else. Pro is recognised however you got it — bought in the app, on the Store website, on another computer, or redeemed from a code.
16. What a backup actually looks like on disk
Worth knowing, because it is the reason to trust the thing. Each backup is a plain folder that describes itself, and that has three consequences:
- There is no central database to lose. If a single backup folder survives a disaster, BackupDesk can read and restore it on its own.
- Your files are stored whole, not chopped into pieces shared between backups. You can open an unencrypted backup folder and copy a file out by hand if you ever want to.
- Uninstalling BackupDesk does not remove a single backup. They live wherever the job’s destination points and are not stored inside the application.
In an encrypted backup, both the files and their names are unreadable without the password or recovery key.
17. Troubleshooting
“Service: Not running”
Nothing is being backed up. Check the BackupDesk service in Windows Services and start it.
BackupDesk asks to allow your account every time
The approval did not stick. Have an administrator add you to the BackupDesk Operators group (see §1). It applies at your next sign-in. If access is lost while the app is open, the banner that explains it has an Allow this account button.
A job says it is waiting
Almost always a destination that is not currently there — an external drive unplugged, or a network share unreachable. Reconnect it and the job starts on its own, usually within seconds. A Google Drive or OneDrive destination behaves differently on purpose: it does not wait, it reports the failure.
“Access to … was refused”
The destination is a network folder BackupDesk is not allowed to write to. Give this computer write access to the folder (see §3), or choose another destination.
“This job is encrypted, but its key could not be unlocked on this machine”
See §13: turn encryption off and on again in the job and enter its password.
A run says some drives were read without a snapshot
Some drives, such as many USB sticks and network drives, cannot back up files that are open in other programs. Close those files if they matter, or they may be skipped and listed. Other sources are unaffected.
“The background service does not have the rights to take volume snapshots”
Backups will fail rather than risk missing files that are open. Check that the BackupDesk service is installed and running in Windows Services.
A backup failed on some files
The run reports which ones. Files open in other programs are normally still backed up; a file that could not be read is listed rather than quietly skipped.
A cloud account says it is disconnected
Connect the same account again from Settings → Cloud accounts — Connect a Google account or Connect a Microsoft account. The existing connection is repaired in place and every job that uses it keeps working.
Restoring asks for a password unexpectedly
Usually after a rebuilt computer or a reinstall. Your password or recovery key will work.
Getting help
About → Copy details copies the version information support will need. Include that in any message to support.
BackupDesk 1.2.0
Free for one backup job, with every feature unlocked.