Had odd behavior with my scheduled backup for Thursday.  Today, at its scheduled time, the dialog window came up saying the backup was about to execute.  I thought it then started because it disappeared, but, at the same time, I was scrolling through windows in Firefox, so I wasn't paying attention.  I went away to eat breakfast and came back to the PC, resuming work.  At 10:15 AM, 30 minutes after the scheduled start for the backup, the prompt to run the backup appeared again.


I cancelled the backup, thinking the 9:45 AM one had run.  But, when I checked the Logs, it had not, in fact, run at 9:45.  And because I cancelled it at 10:15, it hadn't run at all.  I checked the schedules for Thursday's backup and there was only one set: the one for 9:45 AM.  There were also no set schedules for any backup to run on any day at 10:15 AM.


One possible explanation is I may have, somehow, set the delay running of the backup to 30 minutes later in the countdown dialog.  I think there's a delay for 15 minutes option, so there may be a 30 minute as well.  I may have, while scrolling through the web pages, accidentally somehow selected a 30 minute delay in the countdown dialog.  It makes some sense as the delay was 30 minutes after the previous prompt.


The above explanation also makes some sense because I believe I've done this before while scrolling through Firefox pages when the countdown window opens.


Anyway, I thought I'd report this.  I'll keep an eye on tomorrow's backup, if I can remember, and make sure it actually runs on time.  And hopefully I can remember to monitor next Thursday's scheduled backup and check on it running on time.


Thanks!

The ol' PEBKAC error ;-)

                                

Actually, I'd never heard of that term before.    Had to look it up.  I've actually used User Error many times before.  LOL  Even during the beta testing of v8.  I reported what I thought was an issue, but it turned out to be user error.  Back at my last job, we had to write up error logs whenever something happened.  A software self cancellation or a hardware failure.  One time I had to shamefully admit to an Operator Error. 


Also, as I said before, I think this happened to me one other time and I had concluded it was because the prompt window popped up while I was attempting to click on and scroll through web pages in my browser.

+x

 

dbminter - 21 January 2022 4:11 PM

Actually, I'd never heard of that term before.    Had to look it up.  I've actually used User Error many times before.  LOL  Even during the beta testing of v8.  I reported what I thought was an issue, but it turned out to be user error.  Back at my last job, we had to write up error logs whenever something happened.  A software self cancellation or a hardware failure.  One time I had to shamefully admit to an Operator Error. 


Also, as I said before, I think this happened to me one other time and I had concluded it was because the prompt window popped up while I was attempting to click on and scroll through web pages in my browser.

Years ago, I noted that an aircraft accident report by the NTSB attributed the crash to "cockpit error".  I've reused that many times in the intervening years, sometimes to classify mistakes by others, but also to point to mistakes made by me. (I'm "winning"!). 

LOL!  I love that one!  How can the cockpit even make an error?  It's an inanimate object.    Unless the original reporter meant the cockpit as a general term for those operating inside the cockpit.  It's still poorly worded, though.