Ubuntu 18.04 Bacula 9.0.6-1build1
由于某些原因,Bacula 无法在其目录中找到之前的完整备份作业,尽管“作业”表中列出了完整备份作业。Bacula-web 显示完整备份作业已成功完成/终止。电子邮件通知(作业结果)也说明了这一点。示例:
JobID:41 Level:Full Status:Success 8/19/2019
JobID:43 Level:Incremental Status:Success 8/20/2019
JobID:44 Level:Full Status:Success 8/21/2019
电子邮件通知(JobID 45):
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: **No prior Full backup Job record found.**
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: No prior or suitable Full backup found in catalog. Doing FULL backup.
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: Start Backup JobId 45, Job=ubuntu-hm-srv-1-Incremental-Backup.2019-08-21_01.30.00_05
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: There are no more Jobs associated with Volume "ub-hm-srv-1-Incr-Bak-0003". Marking it purged.
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: All records pruned from Volume "ub-hm-srv-1-Incr-Bak-0003"; marking it "Purged"
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: Recycled volume "ub-hm-srv-1-Incr-Bak-0003"
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: Using Device "FileChgr1-Dev1" to write.
电子邮件通知(JobID 41):
19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Start Backup JobId 41, Job=ubuntu-hm-srv-1-Full-Backup.2019-08-19_16.23.00_02
19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Created new Volume="ub-hm-srv-1-Full-Bak-0015", Pool="ub-hm-srv-1-Full_Backups", MediaType="Disk-Stor-1" in catalog.
19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Using Device "FileChgr1-Dev1" to write.
19-Aug 16:23 ubuntu-hm-srv-1-sd JobId 41: Labeled new Volume "ub-hm-srv-1-Full-Bak-0015" on File device "FileChgr1-Dev1" (/mnt/backup/bacula/backup).
19-Aug 16:23 ubuntu-hm-srv-1-sd JobId 41: Wrote label to prelabeled Volume "ub-hm-srv-1-Full-Bak-0015" on File device "FileChgr1-Dev1" (/mnt/backup/bacula/backup)
19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Volume used once. Marking Volume "ub-hm-srv-1-Full-Bak-0015" as Used.
根据这个 Bacula 文档“我想要增量备份,但 Bacula 却将其作为完整备份运行。为什么?”,“...如果 Bacula 找不到成功的完整备份,它将继续执行完整备份。也许您取消了完整备份,或者它错误地终止了。在这种情况下,完整备份将不会成功...”我的备份不是这种情况。它们都成功终止了。
“...同一作业的完整备份...”。同一作业是什么意思?这些作业都是不同的(增量、差异和完整)。如果它们指的是相同的文件集,那么是的,它没有改变,并且对于所有相关的备份作业都是相同的。
为什么 JobID 43 找到了先前的完整作业 JobID 41,而 JobID 44 却没有找到?
任何想法?
谢谢。
答案1
最后,我通过 Bacula 邮件列表询问了这个问题,现在很明显我没有更彻底地学习 Bacula 配置。我的 bacula-dir 配置是错误的,因为它使用单独的作业进行完整、差异和增量备份,并有单独的计划,而我想为这些作业使用单独的池来进行备份轮换。必须使用一个作业来完成,该作业与我的问题配置相关:
JobDefs {
Name = "server-Backup_File_Job"
Type = Backup
Client = server-1-fd
FileSet = "Full Set"
Schedule = "WeeklyCycle"
Storage = FileStorage
Messages = Standard
Pool = Default
Full Backup Pool = server-Full_Backups
Differential Backup Pool = server-Diff_Backups
Incremental Backup Pool = server-Incr_Backups
SpoolAttributes = yes
Priority = 10
Write Bootstrap = "/var/lib/bacula/%c.bsr"
}
Job {
Name = "server-1-Backup"
Client = server-1-fd
JobDefs = "server-Backup_File_Job"
}
Schedule {
Name = "WeeklyCycle"
Run = Level=Full 1st sun at 01:30
Run = Level=Differential 2nd-5th sun at 01:30
Run = Level=Incremental mon-sat at 01:30
}
并为每种类型的备份设置单独的池,并配备相应的备份轮换设置。
因此,我发现在我的帖子日志中提供的内容令人困惑,结果只是我自己创建的不同备份作业造成的混乱。