On Tue, 25 Aug 2009 10:03:43 -0600 (MDT), James L Rogers said:
Hi,
I am running Bacula Version: 3.0.2 (18 July 2009)
x86_64-unknown-linux-gnu redhat on CentOS release 5.3.
I want to verify a volume that was written several jobs ago. The volume
was written to a USB drive and I am afraid that the file is corrupted. The
volume is a differential backup that consists of 18 jobs (one job per file
set) from 2 different clients.
I have found several setups via google for the Verify job resource but
nothing with my exact situation. Here is my current job resource which
only tried to verify the last backup (incremental) of fileset0k and not
the previous differential backup of fileset0k.
Job {
Name = VerifyUSB
Type = Verify
Level = VolumeToCatalog
Messages = Standard
Pool = differential
# Client=server1.prinmath.com-fd
Client = server2.prinmath.com-fd
FileSet = fileset0k
Verify Job = fileset0k
}
Here are my questions:
1) How do I specify the VerifyJob resource if I want an older job than
the last backup of the specified fileset? Apparently a job number does
work here.
There is no way to do that with a VerifyJob at the moment. It always verifies
the last matching jobid that ran.
2) Do I have to set up 18 Verify Jobs and run each one to verify the
entire volume or can I address the volume in it's entirety (remembering
that two clients wrote a total of 18 jobs to the volume).
3) Can anyone point me to a solution that is similar to my situation?
You could check the low level consistency of the volume by using the bls
command line tool, which should check at least that every block matches its
checksum.
__Martin
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
