D2D Verify Job Anomoly!

[Martin Thirkell]

I cant post the screenshot here so Ill do my best to describe it!
Yesterday, i started receiving alerts that incrementals were being
missed. On inspection, the Verify task was taking a long time and as
such the incrementals (every 2 hours) were being skipped. Not such a
big deal, except the Verify task wasnt due to run until tonight!

Again, big deal, however its STILL scheduled to run tonight! I cant
really have this task "doing its own thing" and impacting on our
backups

Any ideas/advice as to how this has happened and more importantly, how
I fix it?

Martin

[Brian Kunick]

I just had the same thing happen.  I had applied the updates to D2D and then a short while later noticed that Verify was running but was not scheduled for another 7 days...

 

> Date: Thu, 19 Jan 2012 00:11:05 -0800
> Subject: D2D Verify Job Anomoly!
> From: mar...@thirkell.co.uk
> To: ca-arcs...@googlegroups.com

[Pratap Karonde]

Usually when D2D runs un-scheduled backups as verify, it prints a
message in activity log to indicate the reason why the job was
converted to verify backup. Did you notice anything there?

Verify backups could be executed if the last shutdown of the machine
was abnormal (power loss, etc) or if D2D has to upgrade the driver.
Under very rare condition, error in generating catalog for previous
backup can also trigger a verify backup.

[Martin Thirkell]

This was off the back of an update (update 3 I believe) being applied,
so that's possibly the cause?