... SIZE="-1">/opt/storeBackup.)¹

You need root permissions to install storeBackup at /opt/storeBackup and to follow the next steps. You can also unpack and run storeBackup from a place where you do not have root permissions. If you start storeBackup without root permissions, it will run with the permissions you have at that moment.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... storeBackup.pl.²

see installation if you do not know what this means

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... SSH³

see FAQ4 for details about making a backup via SSH

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... NFS⁴

See section 5.7 how to configure NFS properly - you must have write access to the directory where you want to save your backup. If you are root, you should have root permissions on this mounted directory.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... flexible⁵

If you want to backup more than one top-level directory tree at a time, you should have a look at option followLinks in section 4.2.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... necessary)⁶

This is only necessary if you use storeBackup.pl with option lateLinks. The necessary time for running storeBackupUpdateBackup.pl can be seen in Example of a Run.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... SIZE="-1">async⁷

see configuring nfs

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... vpn⁸

The vpn software was openvpn, the connection was tunneled trough several firewalls.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... lines.⁹

You also can exclude too big files with option exceptRule of storeBackup.pl from the backup and save them later when you have access to a better line.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... series.¹⁰

The logic behind the suppressWarning option is that repeated non-critical warnings can cause the user to ignore most warnings in general. Here is an example of how you could benefit from this option. Say you have defined a list of directories to exclude from the backup such as temporary directories. Sometimes you limit your list of included directories also. If you limit the included directories in such a way that the excluded directories are not part of the backup, storeBackup would normally generate a warning for every such ``missing'' excluded directory. However, you may choose to leave the excluded directories defined in the configuration file because when you expand your included directory list you do not want to risk forgetting to again define the excluded directories. But you also do not want the warnings because too many non-critical warnings might prevent you from seeing an important warning. In that situation, you can use this option. It means that when altering your included directories list, you only have to make one change (includeDirs) rather than two changes (includeDirs and exceptDirs). However, there is a situation where using this option to suppress warnings of missing excluded directories could have a negative consequence. Say you have an excluded temporary directory named testing that you do not want to back up. Say you rename testing to app1_testing (but you still don't want it backed up. If you do not update your storeBackup config file, and if app1_testing is under an included directory, it will now be backed up. However, if you have not suppressed this class of warning, storeBackup will alert you that testing (the previously excluded directory name) cannot be found. That will probably remind you of your change and let you update your configuration. So use this option with caution. If you are not sure whether you should use it, you probably should not.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... computers).¹¹

see section 4.2, option otherBackupDirs to see how this can be configured

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.