This weekend 95% of my backups finished by Saturday-noon... incredible backup
time savings (they used to run until monday morning)...
yet im reporting ~500 hours of elapsed time. A few months ago without all these
optimizations backup times were running until monday morning and reporting ~300
Is the reported elapsed time including the time that job spent in queue? If so
that would explain this, as now I have nearly 1,000 jobs queuing at night that
could explain the jump in total elapsed time yet decreased backup times.
@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] report backup status elapsed time
Is the reported elapsed time including the time that job spent in queue? If so
that would explain this, as now I have nearly 1,000 jobs queuing at night that
could explain the jump in total elapsed time yet decreased
Thanks for the info. I see Active Elapsed as a selectable column in my
Activity Monitor, but unfortunately, I can't get that column in my Reports for
historical info... I'm thinking command line may be able to pull this info for
me. I am researching, will post my findings :)
Okay, here's a confusing one...
I used Reports Client Backups and ran a separate report for the last 9
weekends. (We run full backups on weekends starting Friday night).
My results are surprising and I cannot quantify why it looks this way...
Weeknbsp; nbsp;Data#40;TB#41;nbsp; nbsp;Elapsed