Knowledge base

Backing-up is a crucial process that everyone should do in order to have a fail-safe, for when the inevitable happens. The principle is to make copies of particular data in order to use those copies for restoring the information if a failure occurs (a data loss event due to deletion, corruption, theft, viruses, etc.)

Mirror backup is identical to a full backup, with the exception that the files can be compressed/encrypted only individually. Mirror backups keep only the latest file versions in the destination (no versioning). A mirror backup is most frequently used to create an exact copy of your data in the destination.

Incremental backup stores all files changed since the last FULL, DIFFERENTIAL OR INCREMENTAL backup. The advantage of an incremental backup is that it takes the least time to finish. The disadvantage is that during a restore operation, each increment is processed and this could result in a lengthy restore job.

The full backup type copies all selected files and folders. Full backup is time consuming (when compared to incremental and differential backup types), but it allows the fastest and easiest restore. It is the starting point of all other backup types.

This article explains how to back up data keeping the original file format (without using compression). The Mirror backup type is the only one that does not use zip compression. The resulted backup will be an exact copy (mirror) of the source files, without altering their initial file format.

Copy backup is a backup that copies all selected files but does not mark each file as having been backed up. In other words, the archive attribute is not cleared. Copying can be carried out between normal and incremental backups because copying does not affect these other backup operations.

Backup4all does not allow users to select multiple backup destinations for a single backup job. However, users can create multiple backup jobs assigned with the same backup tag and each job could have a different backup destination. When a backup tag is scheduled to run, all backup jobs containing that tag will run sequentially. It is specifically useful when you want to have the same backup stored on different destinations for increased data protection. For example you can have the same backup stored on a remote FTP location and also on an external hard drive - if one backup destination will become unavailable at least you can recover your data from the other destination.