/usr/share/doc/backup-manager-doc/user-guide.html/ch-using.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">

<html>

<head>

<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">

<title>Backup Manager 0.7.7 User Guide - Using Backup Manager</title>

<link href="index.html" rel="start">
<link href="ch-configuration.html" rel="prev">
<link href="index.html" rel="next">
<link href="index.html#contents" rel="contents">
<link href="index.html#copyright" rel="copyright">
<link href="ch-about.html" rel="chapter" title="1 About this manual">
<link href="ch-configuration.html" rel="chapter" title="2 Configuration files">
<link href="ch-using.html" rel="chapter" title="3 Using Backup Manager">
<link href="ch-about.html#s-about-scope" rel="section" title="1.1 Scope">
<link href="ch-about.html#s-about-version" rel="section" title="1.2 Version">
<link href="ch-about.html#s-about-authors" rel="section" title="1.3 Authors">
<link href="ch-configuration.html#s-design" rel="section" title="2.1 Repository and Archives">
<link href="ch-configuration.html#s-methods" rel="section" title="2.2 Backup Methods">
<link href="ch-configuration.html#s-uploads" rel="section" title="2.3 Upload Methods">
<link href="ch-configuration.html#s-exports" rel="section" title="2.4 Exports">
<link href="ch-configuration.html#s-advanced" rel="section" title="2.5 Advanced features">
<link href="ch-using.html#s-command" rel="section" title="3.1 Command line">
<link href="ch-using.html#s-cron" rel="section" title="3.2 CRON integration">
<link href="ch-configuration.html#s-archive-repo" rel="subsection" title="2.1.1 The Repository">
<link href="ch-configuration.html#s-BM_REPOSITORY_ROOT" rel="subsection" title="2.1.1.1 BM_REPOSITORY_ROOT">
<link href="ch-configuration.html#s-BM_REPOSITORY_SECURE" rel="subsection" title="2.1.1.2 BM_REPOSITORY_SECURE">
<link href="ch-configuration.html#s-encryption" rel="subsection" title="2.1.2 Encryption">
<link href="ch-configuration.html#s-BM_ENCRYPTION_METHOD" rel="subsection" title="2.1.2.1 BM_ENCRYPTION_METHOD">
<link href="ch-configuration.html#s-BM_ENCRYPTION_RECIPIENT" rel="subsection" title="2.1.2.2 BM_ENCRYPTION_RECIPIENT">
<link href="ch-configuration.html#s-archives" rel="subsection" title="2.1.3 Archives">
<link href="ch-configuration.html#s-BM_ARCHIVE_STRICTPURGE" rel="subsection" title="2.1.3.1 BM_ARCHIVE_STRICTPURGE">
<link href="ch-configuration.html#s-BM_ARCHIVE_NICE_LEVEL" rel="subsection" title="2.1.3.2 BM_ARCHIVE_NICE_LEVEL">
<link href="ch-configuration.html#s-BM_ARCHIVE_PURGEDUPS" rel="subsection" title="2.1.3.3 BM_ARCHIVE_PURGEDUPS">
<link href="ch-configuration.html#s-BM_ARCHIVE_TTL" rel="subsection" title="2.1.3.4 BM_ARCHIVE_TTL">
<link href="ch-configuration.html#s-BM_REPOSITORY_RECURSIVEPURGE" rel="subsection" title="2.1.3.5 BM_REPOSITORY_RECURSIVEPURGE">
<link href="ch-configuration.html#s-BM_ARCHIVE_PREFIX" rel="subsection" title="2.1.3.6 BM_ARCHIVE_PREFIX">
<link href="ch-configuration.html#s-tarball" rel="subsection" title="2.2.1 Tarballs">
<link href="ch-configuration.html#s-tarball-desc" rel="subsection" title="2.2.1.1 Description">
<link href="ch-configuration.html#s-BM_TARBALL_NAMEFORMAT" rel="subsection" title="2.2.1.2 BM_TARBALL_NAMEFORMAT">
<link href="ch-configuration.html#s-BM_TARBALL_FILETYPE" rel="subsection" title="2.2.1.3 BM_TARBALL_FILETYPE">
<link href="ch-configuration.html#s-BM_TARBALL_SLICESIZE" rel="subsection" title="2.2.1.4 BM_TARBALL_SLICESIZE">
<link href="ch-configuration.html#s-BM_TARBALL_EXTRA_OPTIONS" rel="subsection" title="2.2.1.5 BM_TARBALL_EXTRA_OPTIONS">
<link href="ch-configuration.html#s-BM_TARBALL_DUMPSYMLINKS" rel="subsection" title="2.2.1.6 BM_TARBALL_DUMPSYMLINKS">
<link href="ch-configuration.html#s-BM_TARBALL_DIRECTORIES" rel="subsection" title="2.2.1.7 BM_TARBALL_DIRECTORIES">
<link href="ch-configuration.html#s-BM_TARBALL_TARGETS" rel="subsection" title="2.2.1.8 BM_TARBALL_TARGETS">
<link href="ch-configuration.html#s-BM_TARBALL_BLACKLIST" rel="subsection" title="2.2.1.9 BM_TARBALL_BLACKLIST">
<link href="ch-configuration.html#s-BM_TARBALL_OVER_SSH" rel="subsection" title="2.2.1.10 BM_TARBALL_OVER_SSH">
<link href="ch-configuration.html#s-tarballinc" rel="subsection" title="2.2.2 Incremental tarballs">
<link href="ch-configuration.html#s-tarballinc-desc" rel="subsection" title="2.2.2.1 Description">
<link href="ch-configuration.html#s-BM_TARBALLINC_MASTERDATETYPE" rel="subsection" title="2.2.2.2 BM_TARBALLINC_MASTERDATETYPE">
<link href="ch-configuration.html#s-BM_TARBALLINC_MASTERDATEVALUE" rel="subsection" title="2.2.2.3 BM_TARBALLINC_MASTERDATEVALUE">
<link href="ch-configuration.html#s-mysql" rel="subsection" title="2.2.3 MySQL databases">
<link href="ch-configuration.html#s-mysql-desc" rel="subsection" title="2.2.3.1 Description">
<link href="ch-configuration.html#s-BM_MYSQL_DATABASES" rel="subsection" title="2.2.3.2 BM_MYSQL_DATABASES">
<link href="ch-configuration.html#s-BM_MYSQL_SAFEDUMPS" rel="subsection" title="2.2.3.3 BM_MYSQL_SAFEDUMPS">
<link href="ch-configuration.html#s-BM_MYSQL_ADMINLOGIN" rel="subsection" title="2.2.3.4 BM_MYSQL_ADMINLOGIN">
<link href="ch-configuration.html#s-BM_MYSQL_ADMINPASS" rel="subsection" title="2.2.3.5 BM_MYSQL_ADMINPASS">
<link href="ch-configuration.html#s-BM_MYSQL_HOST" rel="subsection" title="2.2.3.6 BM_MYSQL_HOST">
<link href="ch-configuration.html#s-BM_MYSQL_PORT" rel="subsection" title="2.2.3.7 BM_MYSQL_PORT">
<link href="ch-configuration.html#s-BM_MYSQL_FILETYPE" rel="subsection" title="2.2.3.8 BM_MYSQL_FILETYPE">
<link href="ch-configuration.html#s-svn" rel="subsection" title="2.2.4 Subversion repositories">
<link href="ch-configuration.html#s-svn-desc" rel="subsection" title="2.2.4.1 Description">
<link href="ch-configuration.html#s-BM_SVN_REPOSITORIES" rel="subsection" title="2.2.4.2 BM_SVN_REPOSITORIES">
<link href="ch-configuration.html#s-BM_SVN_COMPRESSWITH" rel="subsection" title="2.2.4.3 BM_SVN_COMPRESSWITH">
<link href="ch-configuration.html#s-pipe" rel="subsection" title="2.2.5 Generic methods">
<link href="ch-configuration.html#s-pipe-desc" rel="subsection" title="2.2.5.1 Description">
<link href="ch-configuration.html#s-pipe-example" rel="subsection" title="2.2.5.2 Example">
<link href="ch-configuration.html#s-uploads-desc" rel="subsection" title="2.3.1 Description">
<link href="ch-configuration.html#s-uploads-global" rel="subsection" title="2.3.2 Global configuration keys">
<link href="ch-configuration.html#s-BM_UPLOAD_HOSTS" rel="subsection" title="2.3.2.1 BM_UPLOAD_HOSTS">
<link href="ch-configuration.html#s-BM_UPLOAD_DESTINATION" rel="subsection" title="2.3.2.2 BM_UPLOAD_DESTINATION">
<link href="ch-configuration.html#s-upload-ssh" rel="subsection" title="2.3.3 SSH uploads">
<link href="ch-configuration.html#s-uploads-ssh-desc" rel="subsection" title="2.3.3.1 Description">
<link href="ch-configuration.html#s-BM_UPLOAD_SSH_USER" rel="subsection" title="2.3.3.2 BM_UPLOAD_SSH_USER">
<link href="ch-configuration.html#s-BM_UPLOAD_SSH_KEY" rel="subsection" title="2.3.3.3 BM_UPLOAD_SSH_KEY">
<link href="ch-configuration.html#s-BM_UPLOAD_SSH_PORT" rel="subsection" title="2.3.3.4 BM_UPLOAD_SSH_PORT">
<link href="ch-configuration.html#s-BM_UPLOAD_SSH_HOSTS" rel="subsection" title="2.3.3.5 BM_UPLOAD_SSH_HOSTS">
<link href="ch-configuration.html#s-BM_UPLOAD_SSH_PURGE" rel="subsection" title="2.3.3.6 BM_UPLOAD_SSH_PURGE">
<link href="ch-configuration.html#s-BM_UPLOAD_SSH_DESTINATION" rel="subsection" title="2.3.3.7 BM_UPLOAD_SSH_DESTINATION">
<link href="ch-configuration.html#s-upload-ssh-gpg" rel="subsection" title="2.3.4 Encrypted SSH uploads">
<link href="ch-configuration.html#s-upload-ssh-gpg-desc" rel="subsection" title="2.3.4.1 Description">
<link href="ch-configuration.html#s-BM_UPLOAD_SSH_GPG_RECIPIENT" rel="subsection" title="2.3.4.2 BM_UPLOAD_SSH_GPG_RECIPIENT">
<link href="ch-configuration.html#s-upload-ftp" rel="subsection" title="2.3.5 FTP uploads">
<link href="ch-configuration.html#s-uploads-ftp-desc" rel="subsection" title="2.3.5.1 Description">
<link href="ch-configuration.html#s-BM_UPLOAD_FTP_SECURE" rel="subsection" title="2.3.5.2 BM_UPLOAD_FTP_SECURE">
<link href="ch-configuration.html#s-BM_UPLOAD_FTP_PASSIVE" rel="subsection" title="2.3.5.3 BM_UPLOAD_FTP_PASSIVE">
<link href="ch-configuration.html#s-BM_UPLOAD_FTP_TTL" rel="subsection" title="2.3.5.4 BM_UPLOAD_FTP_TTL">
<link href="ch-configuration.html#s-BM_UPLOAD_FTP_USER" rel="subsection" title="2.3.5.5 BM_UPLOAD_FTP_USER">
<link href="ch-configuration.html#s-BM_UPLOAD_FTP_PASSWORD" rel="subsection" title="2.3.5.6 BM_UPLOAD_FTP_PASSWORD">
<link href="ch-configuration.html#s-BM_UPLOAD_FTP_HOSTS" rel="subsection" title="2.3.5.7 BM_UPLOAD_FTP_HOSTS">
<link href="ch-configuration.html#s-BM_UPLOAD_FTP_DESTINATION" rel="subsection" title="2.3.5.8 BM_UPLOAD_FTP_DESTINATION">
<link href="ch-configuration.html#s-BM_UPLOAD_FTP_PURGE" rel="subsection" title="2.3.5.9 BM_UPLOAD_FTP_PURGE">
<link href="ch-configuration.html#s-upload-s3" rel="subsection" title="2.3.6 Amazon S3 uploads">
<link href="ch-configuration.html#s-uploads-s3-desc" rel="subsection" title="2.3.6.1 Description">
<link href="ch-configuration.html#s-BM_UPLOAD_S3_DESTINATION" rel="subsection" title="2.3.6.2 BM_UPLOAD_S3_DESTINATION">
<link href="ch-configuration.html#s-BM_UPLOAD_S3_ACCESS_KEY" rel="subsection" title="2.3.6.3 BM_UPLOAD_S3_ACCESS_KEY">
<link href="ch-configuration.html#s-BM_UPLOAD_S3_SECRET_KEY" rel="subsection" title="2.3.6.4 BM_UPLOAD_S3_SECRET_KEY">
<link href="ch-configuration.html#s-BM_UPLOAD_S3_PURGE" rel="subsection" title="2.3.6.5 BM_UPLOAD_S3_PURGE">
<link href="ch-configuration.html#s-upload-rsync" rel="subsection" title="2.3.7 RSYNC uploads">
<link href="ch-configuration.html#s-upload-rsync-desc" rel="subsection" title="2.3.7.1 Description">
<link href="ch-configuration.html#s-BM_UPLOAD_RSYNC_DIRECTORIES" rel="subsection" title="2.3.7.2 BM_UPLOAD_RSYNC_DIRECTORIES">
<link href="ch-configuration.html#s-BM_UPLOAD_RSYNC_HOSTS" rel="subsection" title="2.3.7.3 BM_UPLOAD_RSYNC_HOSTS">
<link href="ch-configuration.html#s-BM_UPLOAD_RSYNC_DESTINATION" rel="subsection" title="2.3.7.4 BM_UPLOAD_RSYNC_DESTINATION">
<link href="ch-configuration.html#s-BM_UPLOAD_RSYNC_DUMPSYMLINKS" rel="subsection" title="2.3.7.5 BM_UPLOAD_RSYNC_DUMPSYMLINKS">
<link href="ch-configuration.html#s-exports-burning" rel="subsection" title="2.4.1 Burning CDR/DVD media">
<link href="ch-configuration.html#s-BM_BURNING_METHOD" rel="subsection" title="2.4.1.1 BM_BURNING_METHOD">
<link href="ch-configuration.html#s-BM_BURNING_DEVICE" rel="subsection" title="2.4.1.2 BM_BURNING_DEVICE">
<link href="ch-configuration.html#s-BM_BURNING_DEVFORCED" rel="subsection" title="2.4.1.3 BM_BURNING_DEVFORCED">
<link href="ch-configuration.html#s-BM_BURNING_ISO_FLAGS" rel="subsection" title="2.4.1.4 BM_BURNING_ISO_FLAGS">
<link href="ch-configuration.html#s-BM_BURNING_MAXSIZE" rel="subsection" title="2.4.1.5 BM_BURNING_MAXSIZE">
<link href="ch-configuration.html#s-BM_BURNING_CHKMD5" rel="subsection" title="2.4.1.6 BM_BURNING_CHKMD5">
<link href="ch-configuration.html#s-BM_TEMP_DIR" rel="subsection" title="2.5.1 BM_TEMP_DIR">
<link href="ch-configuration.html#s-advanced-logger" rel="subsection" title="2.5.2 Logging to syslog">
<link href="ch-configuration.html#s-BM_LOGGER" rel="subsection" title="2.5.2.1 BM_LOGGER">
<link href="ch-configuration.html#s-BM_LOGGER_FACILITY" rel="subsection" title="2.5.2.2 BM_LOGGER_FACILITY">
<link href="ch-configuration.html#s-advanced-externals" rel="subsection" title="2.5.3 Writing external hooks">
<link href="ch-configuration.html#s-BM_PRE_BACKUP_COMMAND" rel="subsection" title="2.5.3.1 BM_PRE_BACKUP_COMMAND">
<link href="ch-configuration.html#s-BM_POST_BACKUP_COMMAND" rel="subsection" title="2.5.3.2 BM_POST_BACKUP_COMMAND">
<link href="ch-using.html#s-command-desc" rel="subsection" title="3.1.1 Restrictions">
<link href="ch-using.html#s-command-switched" rel="subsection" title="3.1.2 Options">
<link href="ch-using.html#s-version" rel="subsection" title="3.1.2.1 --version">
<link href="ch-using.html#s-verbose" rel="subsection" title="3.1.2.2 --verbose or -v">
<link href="ch-using.html#s-no-warnings" rel="subsection" title="3.1.2.3 --no-warnings">
<link href="ch-using.html#s-conffile" rel="subsection" title="3.1.2.4 --conffile or -c">
<link href="ch-using.html#s-force" rel="subsection" title="3.1.2.5 --force">
<link href="ch-using.html#s-upload" rel="subsection" title="3.1.2.6 --upload or -u">
<link href="ch-using.html#s-burn" rel="subsection" title="3.1.2.7 --burn or -b [&lt;DATE&gt;]">
<link href="ch-using.html#s-md5check" rel="subsection" title="3.1.2.8 --md5check or -m">
<link href="ch-using.html#s-purge" rel="subsection" title="3.1.2.9 --purge or -p">
<link href="ch-using.html#s-no-upload" rel="subsection" title="3.1.2.10 --no-upload or -p">
<link href="ch-using.html#s-no-burn" rel="subsection" title="3.1.2.11 --no-burn">
<link href="ch-using.html#s-no-purge" rel="subsection" title="3.1.2.12 --no-purge or -p">

</head>

<body>

<p><a name="ch-using"></a></p>
<hr>

<p>
[ <a href="ch-configuration.html">previous</a> ]
[ <a href="index.html#contents">Contents</a> ]
[ <a href="ch-about.html">1</a> ]
[ <a href="ch-configuration.html">2</a> ]
[ 3 ]
[ <a href="index.html">next</a> ]
</p>

<hr>

<h1>
Backup Manager 0.7.7 User Guide
<br>Chapter 3 - Using Backup Manager
</h1>

<hr>

<p>
<em>Now that you know in details how to write your configuration files, let's
see how to use Backup Manager.</em>
</p>

<hr>

<h2><a name="s-command"></a>3.1 Command line</h2>

<hr>

<h3><a name="s-command-desc"></a>3.1.1 Restrictions</h3>

<p>
In version 0.7.7, Backup Manager can only be used by <samp>root</samp>, as it
has be designed as a systemwide tool.
</p>

<pre>
     $ backup-manager
     backup-manager must be run as root.
</pre>

<p>
If you want to launch it from the command line, you first have to use the
<samp>root</samp> account.
</p>

<pre>
     $ su
     Password:
     # backup-manager -h
     /usr/sbin/backup-manager [options]
     
     Output:
     --help|-h           : Print this short help message.
     --verbose|-v        : Print what happens on STDOUT.
     --no-warnings       : Disable warnings.
     
     Single actions:
     --upload|-u         : Just upload the files of the day.
     --burn|-b           : Just burn the files of the day.
     --md5check|-m       : Just test the md5 sums.
     --purge|-p          : Just purge old archives.
     
     Behaviour:
     --conffile|-c file  : Choose an alternate config file.
     --force|-f          : Force overwrite of existing archives.
     
     Unwanted actions:
     --no-upload         : Disable the upload process.
     --no-burn           : Disable the burning process.
     --no-purge          : Disable the purge process.
     ouranos:/home/sukria#
</pre>

<p>
As you can see in the example above, using the <samp>-h</samp> switch (or
<samp>--help</samp>) gives a short help message and prints all supported
command switches.  We will cover in this section each of them.
</p>

<hr>

<h3><a name="s-command-switched"></a>3.1.2 Options</h3>

<p>
The following switches can be used for altering Backup Manager's behaviour.
</p>

<hr>

<h4><a name="s-version"></a>3.1.2.1 <samp>--version</samp></h4>

<p>
Prints on stdout the Backup Manager version installed on the system and exit.
</p>

<p>
Example:
</p>

<pre>
     # backup-manager --version
     Backup Manager 0.6
</pre>

<hr>

<h4><a name="s-verbose"></a>3.1.2.2 <samp>--verbose</samp> or <samp>-v</samp></h4>

<p>
Using this switch will enabled the verbose mode.  All actions are reported on
stdout.
</p>

<p>
Example:
</p>

<pre>
     # backup-manager -v
     Getting lock for backup-manager 10605 with /etc/backup-manager.conf: ok
     Cleaning /var/archives
     Entering directory /var/archives/lost+found.
     [...]
</pre>

<hr>

<h4><a name="s-no-warnings"></a>3.1.2.3 <samp>--no-warnings</samp></h4>

<p>
When a non-critical problem occurs (an error occured but the backup process can
follow) Backup Manager will print a warning message (and will log it if the
logger is enabled).  If you don't want to see warning messages, you can append
this switch on the command line.
</p>

<hr>

<h4><a name="s-conffile"></a>3.1.2.4 <samp>--conffile</samp> or <samp>-c</samp></h4>

<p>
Backup Manager relies on configuration files, by default, the file
<samp>/etc/backup-manager.conf</samp> is used but you can choose to run it with
a different one.  This is done by using the following syntax :
</p>

<pre>
     # backup-manager -c &lt;FILE&gt;
</pre>

<p>
Note that Backup Manager is designed to work properly when launched in parallel
mode with different configuration files, but it will refuse to run twice at the
same time with the same configuration file.  You can then safely do something
like that:
</p>

<pre>
     # backup-manager -c /etc/backup-manager/backup-nfs.conf &amp;
     # backup-manager -c /etc/backup-manager/backup-homedirs.conf &amp;
     # backup-manager -c /etc/backup-manager/backup-rsync-filer.conf
</pre>

<hr>

<h4><a name="s-force"></a>3.1.2.5 <samp>--force</samp></h4>

<p>
When building an archive, Backup Manager looks if the archive already exists in
the repository, if so, a warning is sent saying that the archive exists.  If
you want to bypass this warning and overwrite archives, use this switch.
</p>

<hr>

<h4><a name="s-upload"></a>3.1.2.6 <samp>--upload</samp> or <samp>-u</samp></h4>

<p>
If you have made a configuration file that enables the uploading system, you
can ask Backup Manager to perform the uploading session instead of the whole
process with this switch.
</p>

<hr>

<h4><a name="s-burn"></a>3.1.2.7 <samp>--burn</samp> or <samp>-b</samp> [&lt;DATE&gt;]</h4>

<p>
If you have made a configuration file that enables the burning system, you can
ask Backup Manager to perform the burning session instead of the whole process
with this switch.
</p>

<p>
You can also ask Backup Manager to burn only archives of a given date with
providing a timestamp after the <samp>--burn</samp> switch.
</p>

<p>
Example:
</p>

<p>
Burning all the archives made on March, 12nd 2006:
</p>

<pre>
     # backup-manager --bnurn 20060312
</pre>

<hr>

<h4><a name="s-md5check"></a>3.1.2.8 <samp>--md5check</samp> or <samp>-m</samp></h4>

<p>
If you have made a configuration file that enables the MD5 checks on burnt
media, you can ask Backup Manager to perform the MD5 checks instead of the
whole process with this switch.
</p>

<hr>

<h4><a name="s-purge"></a>3.1.2.9 <samp>--purge</samp> or <samp>-p</samp></h4>

<p>
This switch will as Backup Manager to just perform the archive repository
purge: removing any depreacted archives (according to
<samp>BM_ARCHIVE_TTL</samp>.
</p>

<hr>

<h4><a name="s-no-upload"></a>3.1.2.10 <samp>--no-upload</samp> or <samp>-p</samp></h4>

<p>
Use this switch if you have a configuration file that enables the uploading
system and want to run Backup Manager without it.
</p>

<hr>

<h4><a name="s-no-burn"></a>3.1.2.11 <samp>--no-burn</samp></h4>

<p>
Use this switch if you have a configuration file that enables the burning
system and want to run Backup Manager without it.
</p>

<hr>

<h4><a name="s-no-purge"></a>3.1.2.12 <samp>--no-purge</samp> or <samp>-p</samp></h4>

<p>
Use this switch if you want to disable the purging phase.  This can be useful
if you like to implement another kind of purging system, with a post-command
hook for instance.
</p>

<hr>

<h2><a name="s-cron"></a>3.2 CRON integration</h2>

<p>
There is a global idea behind Backup Manager's design: &quot;<em>You won't do
it if you have to think about it</em>&quot;.  This is specifically true for
backup concerns and it is strongly adviced to automate your backup process with
a tasks scheduler like CRON.
</p>

<p>
Setting up a Backup Manager job in cron is pretty easy, you just have to write
a shell script under the appropriate CRON sub-directory that will call
backup-manager.  The best sub-directory to choose is
<samp>/etc/cron.daily</samp> as Backup Manager handles daily archives.
</p>

<p>
Here is an example of a CRON script:
</p>

<pre>
     cat &gt; /etc/cron.daily/backup-manager
     #!/bin/sh
     
     /usr/sbin/backup-manager
</pre>

<p>
If you want to be notified by mail if a problem occurs during the backup
session, just make sure you receive mails coming from CRON.  When the verbose
mode is off, only warnings and errors are printed on stdout, so you will
receive a mail from the Backup Manager CRON job only in case of unexpected
effects.
</p>

<p>
On the other hand, if you like to receive daily mails from the job, even if
everything went well, just append the --verbose switch like that :
</p>

<pre>
     cat &gt; /etc/cron.daily/backup-manager
     #!/bin/sh
     
     /usr/sbin/backup-manager --verbose
</pre>

<hr>

<p>
[ <a href="ch-configuration.html">previous</a> ]
[ <a href="index.html#contents">Contents</a> ]
[ <a href="ch-about.html">1</a> ]
[ <a href="ch-configuration.html">2</a> ]
[ 3 ]
[ <a href="index.html">next</a> ]
</p>

<hr>

<p>
Backup Manager 0.7.7 User Guide
</p>

<address>
1.7 - 14 Apr, 2008<br>
<br>
Alexis Sukrieh<br>
<br>
</address>
<hr>

</body>

</html>
backup-manager-doc 0.7.10.1-2 / usr / share / doc / backup-manager-doc / user-guide.html / ch-using.html
