This application is designed for the incremental backup of big data storages (i.e. NAS) to multiple removable devices with a smaller capacity. If the maximum capacity of a backup device is reached the backup could be continued on the next backup device.

Main features

In this state of development FrincBackup supports the following main features:


  • Scan all files on a source and write the meta data into a database.
  • Rescan all files on a source, check against database and mark changes.
  • Copy new or changed files.

Delete outdated files

Once a file was backuped it may change in your source. Backup will copy the new file version to your backup media. The old versions will stay untouched by this procedure, it remains on backup media. A file will also remain on backup media, it is has been deleted from source. After time. there will be an amount of unused old file versions on your backup media. Context menu "outdated files" gives you the opportunity to delete this old file versions.


  • Restore files after data loss.

Consistence check

By design FrincBackup will only notice new or modified files in your source directories when scanning. If a file has been deleted in your source, FrincBackup won't notice. "Consistence check" checks for each file in your database, wether the file still exists in source or if it has been deleted. If a file, which was backuped before, not exists in source any longer it is considered as outdated (see "Delete outdated files"). A file which was scanned before but never got it's way into a backup will be considered as lost. The filenames of all missing files are written into the "missing file list".

If af source file was deleted by accident be aware of running consistence check!

Although it will list your missing source file, it will also mark the backup file as outdated and your backuped file will be deleted next time you delete all outdated files.

Find files in database / Examine and manipulate

For now there is no way to view the files data and states on database in FrincBackups user interface. Maybe (or not) there will be a file viewer in future versions. I recommend to use an alternative database browser as SQLiteDatabaseBrowser, or SQLiteDatabaseBrowserPortable meanwhile.

Command line arguments

While backup procedure has to be started manualy by user interaction it is possible to start the scan/rescan procedures automatically. For this you may use FrincBackup with command line arguments.


FrincBackup.exe [database file path] [options]

Database file path

As database file path provide the full file path to your database file. If the file name is provided FrincBackup will try to open this database on application startup. A database file path must be provided in order to use the startup options. FrincBackup supports the following options:


FrincBackup starts to scan/rescan all sources found on the provides database file after application has started.


Application will be closed after finishing the scan/rescan of all sources. Works just in combination with the option -ScanAllSources.


FrincBackup.exe "C:\Backup\mybackup.db"

Opens mybackup.db with FrincBackup applications start.

FrincBackup.exe "C:\Backup\mybackup.db" -ScanAllSources -AutoClose

Opens mybackup.db with FrincBackup applications start an start to scan all sources found on database. Subsequent the application will be closed.

Operation modes

FrincBackup comes with two operation modes, backup mode and restore mode. Most common and default mode is backup mode.

By starting a restore the database is set to restore mode. Mode won't be set back to backup mode automatically. A restore may be interrupted temporarily and continued later. Restored files will be marked as restored and there will be not attempt to restore them again after such an interruption.

As long as database is in restore mode, it won't be possible to scan the source paths for changes or to start backup/copy procedures.

As database is set to restore mode by the decision to start a restore, you have to set back the database to backup mode after you consider the restore as finished. For this chose the menu itemĀ  'Reset database to backup mode' in the Database menu. Resetting database to backup mode will also reset the restored-flag of all files, this means all files will be considered as not restored again.

Devices / media

You may add multiple devices to a FrincBackup database. For each device you have to provide a name and a root path. The name must be unique on a FrincBackup database. By adding a device FrincBackup will create a small identifier file within the root path. Don't delete this file because it prevents this devicr, or better this root path, to be added twice on the same FrincBackup database or to be added to another FrincDatabase accidentally.

Within the root path FrincBackup will create it's backup structure. If you choose the "Copy here" function from the media context menu the copy procedure will create a unique directory derived form current date and time. Use the "Copy here" function each time you create a new backup increment. Choosing "Copy to last timed directory" from context menu will copy the files into the last found directory. This function is intended for the first full backup in case the copy process has to be stopped for some reasons and has to be continued later. It's not intended for everyday use, because it will overwrite files within you last increment under certain circumstances.


By default files named "thumbs.db" or "desktop.ini" are excluded from backup. For now there is no possibility to change this behaviour or to exclude other files or directorys. All files and directorys under a specified source path will be backuped. Lets say you have a file structure like D:/home, D:/system and D:/music adding a source path D:/ to FrincBackup will backup the whole structure. If you want to exclude D:/system your only chance is to add D:/home and D:/music as to separate sourc paths instead of D:/