Hi everyone!
I need some guidance on how to configure a Verify job that doesn’t check
hard-links of files.
I’m receiving lots of messages like these:
10-jul 22:15 srv JobId 88710: SHA1 digest differs on
"/usr/share/man/man1/erb.ruby2.5.1.gz". File=2jmj7l5rSw0yVb/vlWAYkK/YBwk
Vol=Q8i9IIJgCt54Z7XEmwpCJY2slug
10-jul 22:15 srv JobId 88710: Cat checksum differs:
/usr/share/man/man1/erb.ruby2.5.1.gz
10-jul 22:15 srv JobId 88710: SHA1 digest differs on
"/usr/share/man/man1/newaliases.1.gz". File=2jmj7l5rSw0yVb/vlWAYkK/YBwk
Vol=H14R1gsvQiU4NhM+ftl2UWkRxtg
Where all digests on ‘File=' are the same.
After several months of investigation I believe these are caused by hard-linked
files. I’d like to know how to ignore these links.
This is an example of a Verify Job definition and the corresponding FileSet:
JobDefs {
Name = "DefaultVerify"
Type = Verify
Level = Data
Accurate = yes
Schedule = "v_CicloSemanal"
Messages = "Msj_Verificaciones"
FileSet = "Full Set"
Pool = lto8
Priority = 1000
# SkipVerify = HardLinks
}
job {
JobDefs = "DefaultVerify"
Name = "v_bd-test"
Verify Job = "bd-test"
Client = "srv"
FileSet = "bd-test-fs"
Schedule = "v_CicloSemanal-UTI"
Priority = 1160
}
FileSet {
Name = "bd-test-fs"
Include {
Options {
signature = SHA1
Verify = pins1
sparse = yes
}
File = /
}
}
"SkipVerify = HardLinks” was sugested by ChatGPT, but is not a valid statement.
The only thing that worked so far was including "hardlinks = no” as an option
on the FileSet, but I don’t think it will be useful in case I need to restore a
full backup.
Thanks a lot!
Cristobal Sabroe Yde
Unidad de Tecnología de la Información
Universidad Nacional de Río Cuarto
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
