Handy Backup copies selected files, mail, databases, disk data, or supported online sources to another storage location through saved tasks. A task records what to protect, where to put it, when to run, and how later runs compare with earlier copies. This differs from dragging a folder to another drive: the program can repeat the same selection on a schedule, keep dated generations, encrypt a backup, and restore data through a matching recovery task.
A task holds policy
The New Task Wizard starts with the data source and destination. Later steps set the backup method, schedule, compression or encryption choices, and error handling. Handy Backup stores those decisions under a named task, so changing the files in a source folder does not require rebuilding the task. Changing the task’s own properties can affect the next run more substantially than adding one file.
Destinations can range from local or removable storage to supported network and online services. A successful connection test only proves that the account and path work at that moment. A scheduled job can still fail later if the drive letter changes, credentials expire, the destination fills, or the computer sleeps before the task starts. The task log is therefore part of the backup routine rather than an optional troubleshooting screen.
Full and incremental
A full backup copies the entire selected set. It takes the most space and transfer time, but its recovery does not depend on a chain of earlier incremental runs. Handy Backup runs a full copy the first time. It can also return to a full run after task properties change, even when the task normally uses an incremental plan.
Incremental backup compares files and copies new or changed files. The comparison works at file level. Editing a small part of a large file can therefore cause the whole file to enter the new backup. This is different from byte-level differencing and matters for large mailbox containers, virtual disks, and other files that change internally.
Differential backup stores differences relative to a full backup in versioned folders. Restoring it requires both the full set and the relevant differential data. Removing the full base to save space breaks that recovery path. Mixed plans repeat a full backup after a chosen number or period of incremental or differential runs, which limits how long a chain can grow.
Some sources stay full
Not every data plugin supports incremental or differential work. Tasks built with Database, Disk Clone, and Virtual Machine groups perform full backups to preserve data integrity. Selecting Incremental in a general plan does not force those sources into a file comparison that they cannot safely use. A single-archive destination also prevents the normal separate-file comparison required by incremental and differential modes.
This behavior can surprise an administrator who expects every daily run to remain small. The source type, archive mode, and a recent task edit can all trigger a full copy. Storage planning should use the actual task log and destination growth rather than the label chosen when the task was first created.
Versions need rotation
Versioned backup keeps dated recovery points instead of replacing one destination state. Rotation settings decide how many survive. An aggressive rule saves space but can remove the last copy made before a slow corruption or accidental edit. A loose rule can fill the destination and stop later jobs. Handy Backup cannot infer how long the organization needs to discover a bad file.
Encryption protects stored backup data only while the password remains available. A recovery task needs that password, and losing it removes the practical path back to the files. The destination also needs protection from the same incident as the source. A permanently attached drive can be reached by destructive software or an operator mistake, so at least one recovery copy should remain separate from the computer between planned updates.
Restore proves the copy
A completed backup records that the task wrote data. A test restore checks whether the expected files, versions, credentials, and decryption details still work together. Handy Backup can restore to the original or another selected location, but overwrite and deletion options need careful review. A recovery task that deletes unrelated destination files can turn a test into a destructive operation.
