Day One (Full Backup)

The day one full backup functions like any traditional full backup procedure. A full backup can include all the files on your hard disk or it can include only important data files and program settings. This type of backup ensures that there is a copy of every file that might need to be restored. It should be noted that, as files are selected for backup, a counter is displayed that indicates the number of files selected and the total number of uncompressed megabytes. These totals are located in the lower right-hand corner of the application window.

The first full backup will take considerably more time to process and transmit, and will likely be scheduled to run at a different time of the day than subsequent backups.

Day Two (FastBIT II Backup)

It is possible to create efficient FastBIT backups on day two by caching (storing) the compressed full backup from day one. In most cases, the full backup will not be stored in the local cache because of disk space requirements and because most of the files are not actively changing. However, if only archive files are selected to be backed up on day one, then it may be desirable to change the default so that files included in the full backup are stored. This option will cause the FastBIT backup process to begin on day two.

The log file for a particular backup can be viewed to determine which files have been backed up using the FastBIT process.

Day Three (FastBIT II Backup)

Typically, noticeable file size reductions can be detected on day three. In most cases, only a minimal amount of file changes are likely between day two and day three. The new changes are compared against the files stored in the local disk cache and a FastBIT backup is created for those files. The FastBIT backup represents the actual differences in the data between day two and three. The effects of the FastBIT backup will be evident by the sizes of the files created. Detailed information pertaining to the sizes of files and the percentage of reduction can be viewed in the log. The changed files are saved to the local disk cache and will allow a FastBIT backup to be generated for the next backup. If a file stored in the local disk cache is not active for a specified number of backups (default=5), then the copy of that file is removed from the local disk cache, making room for newer active files.