Job Results
A VolumeToCatalog Verify Job that does not find any problems creates a job report that looks similar to the one shown below.
main-dir JobId 2: Bacula Enterprise main-dir 4.0.4 (04Sep10):
Build 0s: x86_64-unknown-linux-gnu suse 11.1
JobId: 2
Job: Verify-Last -RH1-Job-Volume.2010-10-17_00.04.16_21
FileSet: Test Set
Verify Level: VolumeToCatalog
Client: s-rhi-fd
Verify JobId: 1
Verify Job:
Start time: 17-Oct-2010 00:04:18
End time: 17-Oct-2010 00:04:25
Files Expected: 2,216
Files Examined: 2,216
Non-fatal FD errors: 0
FD termination status: OK
SD termination status: OK
Termination: Verify OK
dir Jobld 3: Verifying against Jobld=2 Job=RH1-config.2010-10-17_00.03.08_20
dir Jobld 3: Bootstrap records written to /opt/bacula/main-dir.restore.bsr
dir Jobld 3: Start Verify Jobld=3 Level=VolumeToCatalog Job=Verify-Last-RH1-Job-Volume.2010-10-17_00.16.06_43
dir Jobld 3: Using Device "FileStorage"
sd Jobld 3: Ready to read from volume "F-8" on device "FileStorage" (/data)
sd Jobld 3: Forward spacing Volume "F-8" to file: block 0:1359
sd Jobld 3: Error: block.c:1098 Volume data error at 0:1359! Short block of 2646 bytes on device "FileStorage" (/data) discarded
sd Jobld 3: Error: read_record.c:150 block.c:1098 Volume data error at 0:1359! Short block of 2646 bytes on device "FileStorage" (/data) discarded
sd Jobld 3: End of Volume at file 0 on device "FileStorage" (/data), Volume "F-8"
sd Jobld 3: End of all volumes.
dir Jobld 3: Warning: The following files are in the Catalog but not on the Volume(s):
dir Jobld 3: /etc/sestatus conf
... many lines skipped
dir Jobld 3: /etc/yum/yum-updatesd.conf
dir Jobld 3: Error: Bacula Enterprise s-su-1-dir 4.0.4 (04Sep10):
17-Oct-2010 00:16:10
Build OS: x86_64-unknown-linux-gnu suse 11.1
JobId: 24473
Job: Verify-Last-RH1-Job-Volume.2010-10-17_00.16.06_43
FileSet: Test Set
Verify Level: VolumeToCatalog
Client: s-rhl-fd
Verify JobId: 24458
Verify Job:
Start time: 17-Oct-2010 00:16:08
End time: 17-Oct-2010 00:16:10
Files Expected: 2,216
Files Examined: 0
Non-fatal FD errors: 0
FD termination status: OK
SD termination status: OK
Termination: *** Verify Error ***
We show the job report for the same volume to catalog verification, but this time the volume has been damaged. Initially, some informational messages from the storage daemon (sd) show up, indicating the volume problem. As a result of the inability to properly read that volume, lateron, most of the backed up files could not be found in the volume. Accordingly, the job fails with “*** Verify Error ***”.
Note that in the job reports introduced above, the job to verify against
is not set, i.e. it is selected automatically. Setting the job to verify
against by adding Verify Job = <job name>
to the job resource
results in a job report as shown below.
main-dir JobId 3: Verifying against JobId=2 Job=RHi-sbin.2010-10-17_01.25.35_48
main-dir JobId 3: Bootstrap records written to /opt/bacula/main-dir.restore.bsr
main-dir JobId 3: Start Verify JobId=3 Level=VolumeToCatalog Job=Verify-RH1-sbin-Job-Volume .2010-10-17_01.30.39_52
main-dir JobId 3: Using Device "FileStorage"
main-sd JobId 3: Ready to read from volume "F-2" on device "FileStorage" (/data)
main-sd JobId 3: Forward spacing Volume "F-2" to file:block 0:191.
main-dir JobId 3: Bacula Enterprise main-dir 4.0.4 (04Sep10):
Build 0S: x86_64-unknown-linux-gnu suse 11.1
JobId: 3
Job: Verify-RH1-sbin-Job-Volume.2010-10-17_01.30.39_52
FileSet: Test Set
Verify Level: VolumeToCatalog
Client: s-rhi-fd
Verify JobId: 2
Verify Job: RHi-sbin
Start time: 17-Oct-2010 01:30:41
End time: 17-Oct-2010 01:30:43
Files Expected: 279
Files Examined: 279
Non-fatal FD errors: 0
FD termination statu: OK
SD termination status: OK
Termination: Verify OK
main-dir JobId 24478: Begin pruning Jobs older than 3 hours.
main-dir JobId 24478: No Jobs found to prune.
main-dir JobId 24478: Begin pruning Jobs.
main-dir JobId 24478: No Files found to prune.
main-dir JobId 24478: End auto prune.
This is the approach to use if there is more than one job defined for a client, and the backup and verify jobs need to be separated from each other. The configuration used to create the above examples is shown in figures below.
Job {
Name = Verify-Last-RH1-Job-Volume
Type = Verify
Level = VolumeToCatalog
Client = s-rh1-fd
JobDefs = Default Job
}
Job {
Name = Verify-RH1-sbin-Job-Volume
Type = Verify
Verify Job = RH1-sbin
Level = VolumeToCatalog
Client = s-rh1-fd
JobDefs = Default Job
}
Job {
Name = RH1-config
Type = Backup
Level = Full
Client = s-rh1-fd
File Set = etc-fs
JobDefs = Default Job
}
Job {
Name = RH1-sbin
Type = Backup
Level = Full
Client = s-rh1-fd
File Set = sbin-fs
JobDefs = Default Job
}
FileSet {
Name = etc-fs
Include {
Options {
Verify = pnugsicm1
Signature = SHA1
}
File = /etc
}
}
FileSet {
Name = sbin-fs
Include {
Options {
Verify = pinsmc5
Signature = MD5
}
File /sbin
}
}
JobDefs {
Name = "Default Job"
Type = Backup
Level = Incremental
Client = s-su-1-fd
FileSet = "Test Set"
Schedule = "HourlyCycle"
Storage = File
Messages = Standard
Pool = Tier1
Priority = 10
Write Bootstrap = "/var/lib/bacula/%n.bsr"
}
Pool {
Name = Tier1
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 1 days
Maximum Volume Jobs = 5
Volume Use Duration = 1 days
Maximum Volumes = 50
Maximum Volume Bytes = 4G
Scratch Pool = Scratch
Recycle Pool = Scratch
Next Pool = Tier2 # not needed here
Storage = File # should not need details
}
Client {
Names-rh1-fd
Address = 1sb-254.1sb.os.bacula systems.com
FDPort = 9102
Catalog = MyCatalog
Password = "rhifd"
File Retention = 2 hours
Job Retention = 3 hours
Auto Prune = Yes
}
This configuration will be re-used and enhanced for the following discussions of other Verify Job types.
With VolumeToCatalog verification set up and providing good results, the first important step towards a continuously verified backup solution has been taken. 7 In the following chapters, we will build on the knowledge gained and the existing configuration, adding more verifications.
See also
Go back to:
Go to:
Go back to the main Advanced Features Usage page.
- 7
In tightly audited environments, keeping the job reports for your verify jobs may help when your backup setup is audited for correctness and reliability.