Personal Backup copies chosen folders into another destination so documents, photos and project files can survive a failed drive or accidental loss. A job records what to copy, which files to exclude, how the destination should be arranged and when the run should start. Personal Backup is a file backup program, not a full system image: it does not capture a bootable Windows installation with every partition and recovery structure.
Folders define scope
Selection starts with source folders, and their subfolders are included automatically. Individual subdirectories can be removed or added back, while filters narrow the job by file name, type or age. This structure is clear for personal data, but selecting a broad profile folder can also collect caches, temporary downloads and application data that changes constantly.
An exclusion deserves the same attention as an inclusion. A filter written for temporary files can match a legitimate document with a similar extension. Reviewing the calculated file list before the first large run exposes that mistake while the original data still exists.
Destinations keep structure
The target can be a local folder, removable drive, network share or FTP server. Personal Backup keeps the original folder hierarchy and separates source drives under destination folders. This makes ordinary uncompressed backups browseable without opening a proprietary catalog.
A destination path is not proof that the destination is available. An unplugged USB drive can receive a different letter, and a network share can disconnect after login. If a scheduled job points to the wrong or absent location, the backup may fail even though the task itself remains valid. Checking logs and periodically opening files at the destination prevents a quiet scheduling failure from lasting for months.
Newer is a rule
By default, Personal Backup compares timestamps and copies a source file when it is newer than the stored copy. The archive bit is an alternative criterion. Timestamp logic is fast, but it can misread restored files, clock changes or tools that preserve an old modification date while replacing content.
Choosing a backup mode also controls deletion behavior. A mirror-like task can remove destination files that no longer exist at the source, while an accumulating task keeps older material. Mirroring is useful for a current duplicate, but it can reproduce an accidental deletion before the user notices. A separate generation or independent historical copy is safer for recovery from human error.
Compression changes recovery
Compression reduces file count and can save space, while encryption protects a backup stored outside the home or office. Both choices place an extra step between the user and the recovered file. An encrypted archive is useless without its password, and a damaged compressed container can affect more than one stored item.
Uncompressed copies are easier to inspect directly. Compressed and encrypted copies suit removable or remote storage when their restore path has been tested. The correct choice depends on whether quick individual-file access or compact protected storage matters more.
Schedules need conditions
Tasks can run at logon, logoff, fixed times or through Windows Task Scheduler. A logoff job can delay shutdown while many files copy. A fixed-time job does nothing if the computer is asleep unless the scheduler and power settings wake it. Network credentials may also be unavailable in a task running under another account.
Personal Backup records multiple jobs, so frequent work folders can use a different schedule from a large photo archive. That separation keeps one disconnected destination from blocking every backup. The final check is always a restore: opening several copied files and restoring one to a temporary location confirms more than a successful status line alone.
