Common reasons for the offsite backup to fail to run as scheduled
... and the #1 reason.... drum roll....
Someone changes the Windows user password from which the task is scheduled! If you change the password of the windows user, you must delete and reschedule the backup task!
Other popular reasons:
#2 McAfee or AVG antivirus conflicting with MySQL. We recommend ESET antivirus. Both AVG and McAfee have known issues with MySQL
#3 The scheduled task is running as a Windows user different from that which RGP was configured. The RGP backup settings are *by Windows user*.
#4 The local backup folder is on a removable media drive (USB, ZipDrive, etc)... and the media gets removed.
Comments
And windows updates.
is anyone else having difficulties with the TaskScheduler-based nightly BACKUP after having converted to Window 10? Ours was pretty much flawless until this conversion. The job appears to execute without error but then no backup file is created... seems odd.
We've done the obvious things:
(1) recreate the TaskScheduler job
(2) Use the 'Advanced CMD' TaskScheduler job
(3) manually run the job from within RGP
Only (3) seems to be working.
Looking for some clues from y'all..
ADVthanksANCE,
michael grimes
Michael,
I've heard no specific backup troubles regarding Windows 10.
Using #2 - "the Advanced CMD file", I have NEVER heard of problems... meaning, that method ALWAYS works provided the task gets executed. Something else is going on is my thought. What do the backup logs indicate when using method #2?
Thanks Andy.
We use a different AV -- and a new version was just released (for Windows 10)... will check.
Send the RGP backup log to me.... that will tell all.
OK... we've re-scheduled with the Advanced CMD file.
scheduled NOON test worked with "Advanced CMD"
will let it run this way and see what happens.
no root-cause found for the previous failures.
but, no matter if this continues to succeed reliably.
Please sign in to leave a comment.