This commit is contained in:
Nico Schottelius 2006-06-15 23:45:33 +02:00
parent 85bc0f7782
commit a524a9e7a3
3 changed files with 8 additions and 7 deletions

View file

@ -1,5 +1,5 @@
0.4 to 0.4.1: 0.4 to 0.4.1:
* updated documentation * updated documentation, fixed some English related problems
* added Texinfo documentation * added Texinfo documentation
* added a manpage (English) * added a manpage (English)
* fixed problem with 'make install' (strip was used) * fixed problem with 'make install' (strip was used)

View file

@ -1,4 +1,6 @@
- add --version, -V - add --version, -V
- hint: : in path / sed / general problem
- hint: backuping backup
- do we want rsync -H by default? - do we want rsync -H by default?
- update documentation: - update documentation:

View file

@ -109,8 +109,9 @@ Runtime options
the directory specified by the variable '$CCOLLECT_CONF' the directory specified by the variable '$CCOLLECT_CONF'
(use 'CCOLLECT_CONF=/your/config/dir ccollect.sh' on the shell). (use 'CCOLLECT_CONF=/your/config/dir ccollect.sh' on the shell).
When you start `ccollect`, you have either to specify which interval When you start `ccollect`, you have to specify which interval
to backup (daily, weekly, yearly; you can specify the names yourself, see below). to use for backup (daily, weekly, yearly; you can specify the names yourself,
see below) and which sources to backup or -a (to backup all source).
The interval is used to specify how many backups to keep. The interval is used to specify how many backups to keep.
@ -454,7 +455,7 @@ Now you could use /home/backup/web1 as the `destination` for the backup.
Do *not* name the first backup something like "daily.initial", but use Do *not* name the first backup something like "daily.initial", but use
the "*0*" (or some very low number, at least lower than the current year) the "*0*" (or some very low number, at least lower than the current year)
as extension. `ccollect` uses `sort` to find the latest backup. `ccollect` as extension. `ccollect` uses `sort` to find the latest backup. `ccollect`
itself uses 'interval.YEAR-MONTH-DAY-HOUR:MINUTE.PID'. This notation will itself uses 'interval.YEAR-MONTH-DAY-HOURMINUTE.PID'. This notation will
*always* be before "daily.initial", as numbers are earlier in the list *always* be before "daily.initial", as numbers are earlier in the list
which is produced by `sort`. So, if you have a directory named "daily.initial", which is produced by `sort`. So, if you have a directory named "daily.initial",
`ccollect` will always diff against this backup and transfer and delete `ccollect` will always diff against this backup and transfer and delete
@ -479,8 +480,7 @@ F.A.Q.
What happens, if one backup is broken or empty? What happens, if one backup is broken or empty?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Let us assume, that one backup failed (connection broke or the source Let us assume, that one backup failed (connection broke or the source
hard disk had some failures). So we've one backup in our history, hard disk had some failures). So we've an incomplete backup in our history.
which is incomplete.
The next time you use `ccollect`, it will transfer the missing files. The next time you use `ccollect`, it will transfer the missing files.
This leads to This leads to
@ -507,7 +507,6 @@ permissions. Try `chmod 0755 /etc/ccollect/sources/'yoursource'/*_exec``.
Why does the backup job fail, when part of the source is a link? Why does the backup job fail, when part of the source is a link?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When a part of your path you specified in the source is a When a part of your path you specified in the source is a
(symbolic, hard links are not possible for directories) link, (symbolic, hard links are not possible for directories) link,
the backup *must* fail. the backup *must* fail.