Here is an example where the Verify job uses the same schedule but
different Messages than standard. Pool, Storage, and Schedule entries are
up to you and have not been included; they are not remarkable. The
important thing to note is that the Verify will perform a verify of the
last backup of the job specified in the "VerifyJob" line. Let me know if
you have any questions.
# Captures
Job {
Name = "Captures"
Schedule = "SaturdayEvening"
Type = Backup
Client = captures
Level = Full
Storage = LTO-3
FileSet = "Captures"
Messages = Standard
Pool = Captures
Write Bootstrap = "/var/spool/bacula/bootstrap/%c-%n-%i.bsr"
Priority = 40 # Low priority; this job can take a while to get done.
ClientRunBeforeJob = "/usr/local/bin/captures_stage"
}
# Verify
# The verifies run at a lower priority compared to the backup job.
Job {
Name = "CapturesVerify"
VerifyJob = "Captures"
Schedule = "SaturdayEvening"
Type = Verify
Client = captures
Level = VolumeToCatalog
Storage = LTO-3
Accurate = yes
FileSet = "Captures"
Messages = "Verify_Captures"
Pool = Captures
Write Bootstrap = "/var/spool/bacula/bootstrap/%c-%n-%i.bsr"
Priority = 41 # Low priority; this job can take a while to get done.
ClientRunAfterJob = "/usr/local/bin/captures_post_verify %c-%n-%i"
}
#... FileSet
......................................................................................
FileSet {
Name = "Captures"
Include {
File = /mnt/captures/staging
Options {
signature = MD5
noatime = yes
xattrsupport = yes
One FS = yes
}
}
}
# The Client name "captures" allows us to move this job from host to host.
Client {
Name = captures
Address = hostname.example.com
FDPort = 9102
Catalog = MyCatalog
Password = "topseekrit" # password for FileDaemon
File Retention = 2 months
Job Retention = 2 months
AutoPrune = yes # Prune expired Jobs/Files
}
# Message delivery for verify messages.
Messages {
Name = Verify_Captures
mailcommand = "/usr/local/bin/my_smtp -h mailhub -f \"\(Bacula\) \<
bac...@example.com\>\" -s \"Bacula: %t %e of %c %l\" %r"
operatorcommand = "/usr/local/bin/my_smtp -h mailhub -f \"\(Bacula\) \<
bac...@example.com\>\" -s \"Bacula: Intervention needed for %j\" %r"
mail = i...@example.com = all, !skipped
operator = i...@example.com = mount
append = "/var/log/bacula/verify.log" = all, !skipped
catalog = all, !skipped, !saved
}
*- Mike Schwager*
* Linux Network Engineer, Mocho Trading LLC*
* 312-646-4783 Phone 312-637-0011 Cell 312-957-9804 Fax*
On Thu, Sep 24, 2015 at 6:54 AM, Wanderlei Huttel <wanderleihut...@gmail.com
> wrote:
> Bacula manual is not so clear about Verify Jobs.
>
> What is the best practice to implement verify jobs for any backup job ?
>
> Can somebody show some example?
>
>
--
This message is for the named person(s) use only. It may contain
confidential proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and notify the
sender. You must not, directly or indirectly use, disclose, distribute,
print, or copy any part of this message if you are not the intended
recipient. Mocho Trading LLC reserves the right to monitor all e-mail
communications through its networks. Any views expressed in this message
are those of the individual sender, except where the message states
otherwise and the sender is authorized to state them to be the views of any
such entity.
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
