Dear List
We run a verifyjob between a regular tape-backup and a catalogb ackup to
tape.
The first time the job was run as an initcalalog job to have an inital
verification state.
The purpose of the verify job is to asure that the data of the regular
backup is written to tape correctly. I fear that the current config of
the job does not do that.
It is defined as:
Job {
Name = "Verify_Zim"
Type = Verify
Level = VolumeToCatalog
Client = zim-fd
FileSet = "Full Set"
Messages = Standard
Storage = "DDS-4"
Pool = Default
Schedule = "VerifyCycle"
}
We run Bacula version 2.4.1 on Debian Etch with Mysql.
I get an email every night with:
- new files in /var/lib/postgresql
- 2 new files in CVS (a very long path is specified): we have not been
using CVS in favor of SVN for years now......
- new files created that day
- files in catalog but not on disk(!) of:
- our IMAP server
- /var/lib/bacula
- /var/lib/postgresql
- files in /home
- a file in CVS (which we do not use)
Seeing this gives an unreliable view of what is happening.
The CVS files: is that a (known) bug?
It seems we get a comparation of what is on disk at that time versus
what was in the catalog the night before, which is a very different
verify then the one I had in mind (verification of files written to tape).
Any hints much appreciated!
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
