![]() |
|||||||||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
#1
|
|||
|
|||
scheduled backup failure
Just thought I'd report an odd occurrence. I have scheduled daily backups to two disks. I hadn't checked on them in a few weeks, but when I did, I found that one was working fine, and the other was not working at all. This second scheduled backup (to a new SSD) simply wasn't running. The "Last Copy" recorded for it was weeks ago, and the "Next Copy" was properly listed for tomorrow. The "Next Copy" was being updated every day, even though the copy was never made. The schedule seemed to be filled out correctly for daily operation, but I deleted and reentered it. It appears to now be working properly. Kind of strange. The lesson here is that if you have scheduled backups, check on the "Last Copy" occasionally to make sure they're really doing what they're supposed to be doing.
|
#2
|
||||
|
||||
Did you have it set to not give an error when a volume was missing?
__________________
--Dave Nanian |
#3
|
|||
|
|||
I can't be sure, but I don't think the volume was missing from SuperDuper. Certainly the volume was mounted on the machine, as the first clue I had that this was happening was when opened the volume to see what was not supposed to be there.
That being said, how do you set SuperDuper to give an error when the volume is missing? That would be smart thing to do. |
#4
|
||||
|
||||
The default is to show an error (it's a checkbox in the settings sheet).
I'm guessing you had it unchecked and had modified the low-level ID of the volume that wasn't running, so while the name may have been the same, it was no longer the same ID as it was before.
__________________
--Dave Nanian |
#5
|
|||
|
|||
Ah, I see that checkbox, and it was not checked. Maybe I accidentally unchecked it? The disk at issue is a new SSD, and I'm writing to two partitions on it. A "weekly" partition, and a "daily" partition. It was the latter that wasn't working. The former was. Both partitions were created at the same time, so it isn't clear why one low-level ID would be screwed up and the other wasn't.
Last edited by Dan Lester; 03-24-2022 at 02:52 PM. |
#6
|
||||
|
||||
I don't know, Dan. The evidence is, at this point, lost, so we'll have to see if it happens again.
Remember, we support notifications, and you can use those to see if the backups are running...
__________________
--Dave Nanian |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | Rate This Thread |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Startup Disc and Hard Drive Partitioning Questions | Paint Guy | General | 15 | 10-27-2010 03:25 PM |
Scheduled backup failed to run | penmaster | General | 4 | 01-31-2010 11:31 PM |
Backup failure on a certain file | bmat | General | 3 | 09-25-2007 10:06 AM |
Scheduled backup crashes, but only on one Mac | jonlevine | General | 1 | 02-21-2007 11:08 AM |
How to verify a Scheduled Backup? | tuqqer | General | 3 | 12-06-2005 07:50 PM |