StoreBackup

Software Screenshot:
StoreBackup
Software Details:
Version: 3.4.3
Upload Date: 20 Feb 15
Developer: Heinz-Josef Claes
Distribution Type: Freeware
Downloads: 22

Rating: nan/5 (Total Votes: 0)

StoreBackup is an open source and freely distributed command-line software project. It has been designed from the offset to act as a system backup tool that stores files on other disk drives than the one archived, such as external disks.

Features at a glance

Key features of the StoreBackup software includes several optimizations that improve performance and reduce the disk space needed for backups. It also unifies the advantages of standard, incremental and full backups.

The software supports integrity checks of backups, via md5 sums generated from source, support for isolated incremental backups, without directly accessing the the repositories, as well as support for time shifted replication of backups ("backup of backups").

Powerful command-line options

Being a command-line utility, StoreBackup features powerful command-line options. These and the usage message of the program can be viewed at a glance in any terminal emulator software by running the ‘perl storeBackup.pl --help’ command. The list of command-line options is huge, and so is the uisage message, but it will help you understand how to use the software.

Among some of the most important options, we can mention the ability to check the compression for files bigger than 1Kb, to use a custom configuration file, to remove the lock file before deleting old backups, to continue the backup process even if one or more of the exceptional directories don’t exist, as well as to hardlink identical symlinks.

Getting started with StoreBackup

StoreBackup is written in the Perl programming language and doesn’t require installation. This is a good thing, because after downloading the latest version from Softoware, saving the archive on your Home directory or a location of your choice and unpack it, you can use it directly via a Terminal app. All the executables are located on the ‘bin’ folder and require Perl.

What is new in this release:

  • multiTail.pl now supports colors and a bug regarding dedup with "blocked files" is fixed.

What is new in version 3.4.2:

  • This version adds support for handling sparse files and progress reports based on periods of time.

What is new in version 3.4.1:

  • This release delivers some bugfixes plus the new chapter "Internals" in the documentation.

What is new in version 3.4:

  • This release adds the ability to select via special marker files whether files in directories are backed up or compressed.
  • It's possible to store special files in archives if your target file system doesn't allow you to store them natively.
  • There are minor fixes.

What is new in version 3.3.1:

  • Bugs were fixed.
  • If you use storeBackupMount.pl, you will have to adjust your options.
  • Other scripts also have a few new options.

What is new in version 3.3:

  • This version can make an estimation if a compression might reduce the file size. E.g. when traveling, you can make backups without access to the master backup, and integrate these backups later into the central one.
  • Backups can be replicated (automated), so you can generate copies of your backups (e.g. on another external disk).
  • storeBackup can validate your backup via checksums.
  • With storeBackupCheckSource.pl, it can validate unchanged files in the source directory against checksums in the backup, e.g. to recognize bit rot.

What is new in version 3.2.1 RC1:

  • This bugfix release includes important fixes if you use lateLinks/lateCompress or de-duplication with blocked files or devices.

What is new in version 3.2:

  • Minor bugfix release.
  • It fixes all known bugs from v3.1 and introduces option highLatency.

What is new in version 3.1:

  • storeBackup.pl:
  • storeBackup did not backup sockets, now it does
  • for new files, the md5 sum is now calculated before *and* after copying / compressing for safety reasons. The file could have been changed during that time. So the md5 sum would not match the real one. A file with the firstly calculated md5 sum later could be hard linked to the changed file which means there is no backup of its content.
  • If both md5 sums do not match, an warning is generated and the md5 sum is set to ggggg... which is a not possible value. This problem does not exist for blocked files in v3.0.
  • improved statistic at the end of a run (sum of warnings and errors)
  • added options checkBlocksParallel and checkDevicesParallel
  • added option linkToRecent name clashes because of compressing files (eg. add .bz2) were not handeld corretly - bug was introduced in 3.0 corrected
  • when making a backup with source while not using includeDir then the md5 sums of all files were calculated also after the first backup
  • corrected some issues with the statistical output
  • option copyBWLimit is now deprecated because
  • of internal performance optimization
  • it is useless
  • new option suppressWarning
  • storeBackupUpdateBackup.pl:
  • if sourceDir=/, for the very first backup with option lateLinks an empty 'linkFrom' file was generated which lead to (useless) error messages. corrected.
  • storeBackupCheckBackup.pl:
  • now also checks if files in the backup are not listed in .md5CheckSum
  • storeBackupRecover.pl:
  • the directories in the path to the restored files / directories were not set the original permissions, corrected llt
  • added option --epoch to calculate human readable dates from epoch based dates
  • man:
  • man pages for all programs (Thanks to Ryan Niebur)
  • all programs:
  • solved issues with single quotes in path and filenames

What is new in version 3.1 RC1:

  • storeBackup.pl
  • storeBackup did not backup sockets, now it does for new files, the md5 sum is now calculated before *and* after copying / compressing for safety reasons. The file could have been changed during that time. So the md5 sum would not match the real one. A file with the firstly calculated md5 sum later could be hard linked to the changed file which means there is no backup of its content. If both md5 sums do not match, an warning is generated and the md5 sum is set to ggggg... which is a not possible value. This problem does not exist for blocked files in v3.0. improved statistic at the end of a run (sum of warnings and errors)
  • added options checkBlocksParallel and checkDevicesParallel
  • added option linkToRecent
  • name clashes because of compressing files (eg. add .bz2) were not handeld corretly bug was introduced in 3.0 corrected
  • when making a backup with source=/ while not using includeDir then the md5 sums of all files were calculated also after the first backup
  • corrected some issues with the statistical output
  • option copyBWLimit is now deprecated because: of internal performance optimization; it is useless
  • new option suppressWarning
  • storeBackupUpdateBackup.pl
  • if sourceDir=/, for the very first backup with option lateLinks an empty 'linkFrom' file was generated which lead to (useless) error messages. corrected.
  • storeBackupCheckBackup.pl now also checks if files in the backup are not listed in .md5CheckSum
  • storeBackupRecover.pl the directories in the path to the restored files / directories were not set the original permissions, corrected
  • llt
  • added option --epoch to calculate human readable dates from
  • epoch based dates man
  • man pages for all programs (Thanks to Ryan Niebur)
  • all programs
  • solved issues with single quotes in path and filenames

What is new in version 3.0:

  • This release has minor bugfixes and minor feature enhancements.

What is new in version 3.0 RC2:

  • This version is able to store big image files like mbox files and vmware images efficiently.
  • This pre-release fixes some bugs from rc1 which can result in not backing up some files in some rare cases.
  • If you use 3.0-rc1, you should install this version.

What is new in version 3.0 RC1:

  • This version adds consistency checking of backups and the ability to store complete devices (e.g. from truecrypt) or big image files (e.g. from VMware or Xen) with changes in parts from backup to backup efficiently.

What is new in version 2.0.1:

  • The keepLastOfWeek option was ignored by storeBackupDel.pl if it was set in the configuration file. Therefore, too many old backups were deleted, but only if you use storeBackupDel.pl.
  • This release also corrects a long term minor bug in the progressReport option for statistical output.

What is new in version 2.0:

  • The main changes since 2.0_rc2 are a -b shortcut for the option --backupDir and a bugfix related to the option keepRelative.

What is new in version 2.0 RC1:

  • This release introduces the option lateLinks, which allows setting hard links later (on the server) as a separate step (a speed up by a factor of 2 to 70 depending on the environment) for the direct backup time.
  • A program for rule-based searching in the backup (e.g. defining rules depending on age, size, name, and owner) has been added.
  • There is much better documentation: a detailed description is available as a PDF and on the homepage.
  • There are many other improvements.

Similar Software

AWIT DBackup
AWIT DBackup

19 Feb 15

Backer-upper
Backer-upper

3 Jun 15

Partclone
Partclone

11 Apr 16

Comments to StoreBackup

Comments not found
Add Comment
Turn on images!