I have 15 scheduled backup's all backing up to external drives.

Smart Update BATCAVE (Backup) from Macintosh repeat's it's self 5 times a day at varying intervals, these schedules were all deleted yesterday and new ones were created. (these are the only ones that throw the error)

The remaining ones fire on MTWTF twice a day, once in the morning and once in the evening, and have never thrown this error, and have not been recreated.

So, a single copy scheduled at a given time throws that error?

it seems like that, the ones that seem common are 11am and 1pm

I just don't see why it would make any difference. I'm unable, at present, to reproduce.

hmm, ok Dave, interesting, I will go back to the start, and delete all schedules, uninstall SD, reinstall SD and redo all the schedules and monitor it over the week
and see what comes of it.

ok, I have deleted all schedules, uninstalled SD, run disk warrior, and tech tool pro,
re-installed SD, setup new schedules, and the problem still randomly occurs, and it
seems that the 1pm schedule is the only one that repeats it’s self.
I no I can probably move it to 1.05 or some thing, but that is not fixing the problem.

It’s not the end of the world, more a consistent annoyence.

I've been trying to reproduce the issue, but haven't been able to yet... perhaps create them one at a time and see where it starts failing for you?

I have re-added the schedules one at a time, to see if other factors
are adding anything to the problem and it has come down to
the 1pm schedule that seems to be the issue.

My set up is as attached screen shot, the external drives
for the BATCAVE backup’s are never unplugged, yet the external
drives for the PREPRESS SERVER backup’s are rotated out daily

The drive for the BATCAVE backup is in good health as I have
tested it to confirm it isn’t having issues.

Which means that some of these schedules are failing daily?

only the 1pm one

No, I mean for missing volumes.

have tested all volumes through a weekly rotation, and the only scheduled backup that continually throw's this error is the 1pm one, everything else runs like clockwork..... maybe because it's winter here now :rolleyes:

So...the 11am one no longer fails? Just the 1pm one?

it appears to be so, haven't had any other issues apart from the 1pm one.

yesterday had a 3pm scheduled backup throw the same error