bakonf

this options applies to the archiving of files. If the level given is 0, the virtuals database is cleared, all files which match the configuration options are archived, and their state is then saved in the virtuals database. If the level is 1, the database is opened readonly, and only the files which are no longer equal with their state as recorded in the database, or files which don't have an entry in the database, are stored.

The recommended operation mode is to create weekly an archive using level 0, and daily one using level 1. In this way, you need any weekly archive to recreate the full system, and if the daily archive is also available, you will have the latest configuration.

use FILENAME as configuration file, instead of the default /etc/bakonf/bakonf.xml

save the generated archive as FILE. Note that if this parameter is given it will override any directory given with -d (i.e. this name is taken a a full filename).

save the generated archive under the given DIRECTORY. The filename will be constructed using the current hostname and year, month, day (e.g. host.example.com-2002-12-19.tar). If any of the compression options are given, the file will have the proper suffix appended. If not given, the default directory is /var/lib/bakonf/archives.

compress the generated archive with gzip

compress the generated archive with bzip2

do not save any files in the filesystem. In this case bakonf does not even open a database, bu you must still give the -L option.

do not save any metainformations in the filesystem

shows the version number and exits

shows a short help message about the invocation and exits