Unfortunately this leads to .backup volume creation times being
spread over several hours.
A vos backupsys did in our case take 15 minutes and during that time
the system was not very responsive at all. So I sacrificed the single
backup time in favour for a more responsive system and nowadays
Can someone confirm that my assumptions about incremental AFS
backups are correct?
1) Aside from needlessly increasing the size of the dump, there's
no harm in setting the -time of an incremental dump to be
substantially earlier than it needs to be.
2) If I do a vos backup X and later a
Tom Fitzgerald wrote:
Can someone confirm that my assumptions about incremental AFS
backups are correct?
1) Aside from needlessly increasing the size of the dump, there's
no harm in setting the -time of an incremental dump to be
substantially earlier than it needs to be.
In my
We also ran into
problems with time between running on the command line vs.
cron. Our software compares time stamps in the vos dump
headers to avoid these types of problems.
I'm not sure what you mean here. Your software assumed the
current wallclock time was the time cron normally ran it,
On Fri, 25 Apr 2008, Kristen J. Webb wrote:
Tom Fitzgerald wrote:
Can someone confirm that my assumptions about incremental AFS
backups are correct?
1) Aside from needlessly increasing the size of the dump, there's
no harm in setting the -time of an incremental dump to be
substantially
Tom Fitzgerald wrote:
We also ran into
problems with time between running on the command line vs.
cron. Our software compares time stamps in the vos dump
headers to avoid these types of problems.
I'm not sure what you mean here. Your software assumed the
current wallclock time was the time
Stephen Joyce wrote:
One other thing to be aware of is that giving the -time option to vos
dump makes it look at the files' modification timestamps to determine
what to back up. It's very possible to create a file with an old
timestamp (using tar, touch, etc) so that it won't be caught by
Have you tested it with plain vos dump (not TiBs synthetic backups)?
If what you say is true, great!, although it disagrees with the docs that I
was reading. From the vos dump section of the Admin Reference:
--begin quote--
The following command writes a full dump of the volume user.terry to
Stephen Joyce wrote:
Have you tested it with plain vos dump (not TiBs synthetic backups)?
Yes, vos dump ... -time ... is what we use to obtain the incremental
dumps. I believe the decision to send a file to backup is based on
the vnode:uniquifier data, but I haven't dug into the code on the
1) Aside from needlessly increasing the size of the dump, there's
no harm in setting the -time of an incremental dump to be
substantially earlier than it needs to be.
In my experience, you are correct.
I wouldn't go _substancially_ earlier, but I concur that you're correct. I
10 matches
Mail list logo