We're looking for the drives by getting a list from the system, and then matching the low-level UUID for the drive (assigned when the drive is erased) to the one that was saved during the schedule. If the drive was erased outside SD!, it definitely won't work -- but you indicated it runs OK manually (I assume you're running the schedule from the scheduled copies window)... but there's literally no difference between running it manually with that and when the scheduler is run on schedule.
So... I'm not sure why this would happen, if all the above is accurate. Do you have more than one schedule? Does it only happen with some destinations (or some sources)?
__________________
--Dave Nanian
|