Thanks for the help. I'm trying VolumeToCatalog, and I
believe it is working. My problem with testing was
probably that I was expecting Bacula to make another
checksum for the disk file that was backed up and
compare that with what's on the volume. When in fact
it doesn't, it uses what's in the cat
Arno Lehmann wrote:
> I assume that you do a VolumeToCatalog verify - that's what your
> configuration set up at least.
Right. I didn't look closely enough at the config before answering.
--
Phil Stracchino [EMAIL PROTECTED]
Renaissance Man, Unix generalist, Perl hacker
Mobile: 60
Hi,
Marcus wrote:
Ok. I thought the verify and fileset I'd set up was
supposed to verify by MD5 checksums, but I might have
messed that up.
Nonetheless, I deleted all files from the ../dlt
directory, ran the verify again, and it passed.
Could I be verifying against the verify or something
cra
> Verify checks that what was backed up matches what
> is on disk. The new file you added was not included
> in the backup, and therefore was not included in the
> verify.
Ok. I thought the verify and fileset I'd set up was
supposed to verify by MD5 checksums, but I might have
messed that up.
Marcus wrote:
> I've been playing with verifies and they seem to pass
> when they should fail.
...
> I simply put a text file in /video/dlt, backed it up,
> changed the test and verified. It passed the verify,
> it also passed when I added another file to ../dlt.
> What am I doing wrong?
Nothing.
I've been playing with verifies and they seem to pass
when they should fail.
Here are the two jobs I am doing:
Job {
Name = "Video to DLT-Archive"
Type = "Backup"
Level = "Full"
Client = bench-fd
Fileset = "Video-DLT"
Messages = Standard
Pool = Video-DLT4
Storage = FastStor1
}
Jo
