I have been using
checkfilechanges=yes|no
If enabled, the Client will check size, age of each file after their
backup to see if they have changed during backup. If time or size
mismatch, an error will raise.
zog-fd: Client1.2007-03-31_09.46.21 Error: /tmp/test mtime changed
during backup.
In general, it is recommended to use this option.
But I understand what your asking but I have to ask myself how much
might change after starting the back up before the verify is ran.
Unless I miss understand, if the data changes over the time of the
backup would it not fail?
Our business deals with alot of jpeg/pdf stuff so I just hope to capture
as much as I can.
On 5/2/2018 1:43 PM, Joe Nash wrote:
Hi,
Should I verify my LTO7 tapes after every job?
I've got a single tape drive, no changer.
When I archive data (ie, move data from disk to tape to free up disk space) I
verify the tapes with both VolumeToCatalog and DiskToCatalog jobs.
But what about regular incremental backups? Should I run both both verify jobs
after EACH incremental backup? Is that standard practice?
It's like 10TB of data and growing.
It would save downtime to skip verifying tapes.
What do you think?
Thanks.
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
