Hint: source specific intervals

This commit is contained in:
Nico Schottelius 2006-10-26 10:30:14 +02:00
parent 735353bd05
commit bf4433ad63
2 changed files with 18 additions and 1 deletions

View file

@ -225,6 +225,7 @@ while [ "$i" -lt "$no_sources" ]; do
c_vverbose="$backup/very_verbose" c_vverbose="$backup/very_verbose"
c_rsync_extra="$backup/rsync_options" c_rsync_extra="$backup/rsync_options"
c_summary="$backup/summary" c_summary="$backup/summary"
c_incomplete="$backup/incomplete_remove" c_incomplete="$backup/incomplete_remove"
c_pre_exec="$backup/pre_exec" c_pre_exec="$backup/pre_exec"
@ -405,7 +406,7 @@ while [ "$i" -lt "$no_sources" ]; do
# #
# FIXME: add marking here # FIXME: add marking here
# touch c_marker # touch $c_marker
# #
# #

View file

@ -537,6 +537,22 @@ use a link to
The only requirement is that it is executable. The only requirement is that it is executable.
Using source specific interval definitions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When you are backing up multiple hosts via cron each night, it may be
a problem that host "big_server" may only have 4 daily backups, because
otherwise its backup device will be full. But for all other hosts
you want to keep 20 daily backups. In this case you would create
`/etc/ccollect/default/intervals/daily` containing "20" and
`/etc/ccollect/sources/big_server/intervals/daily` containing "4".
Source specific intervals always overwrite the default values.
If you have to specify it individually for every host, because
of different requirements, you can even omit creating
`/etc/ccollect/default/intervals/daily`.
F.A.Q. F.A.Q.
------ ------