Repeat attempt not working
ATI 2020 Build 25700.
My wife's laptop is doing daily differential backups to a NAS using WiFi. Today her PC was in sleep mode when the backup was supposed to occur. It appears that ATI woke the PC from sleep, which is set in the Scheduling Advanced Settings. When the PC woke, it didn't have WiFi, so the differential backup failed because the network share was inaccessible. When I checked the PC, WiFi activated, and I expected the backups to be reattempted. The repeat attempt options are set to 6 attempts every 30 minutes. I found the PC in sleep mode about 5 minutes after the scheduled backup time, and had WiFi active about a minute it woke. Should ATI have attempted to repeat the backup? When I used to backup to external hard drives, it would continue to try to do the backup until the drive was connected or when the number of attempts was reached. Because the NAS share was inaccessible did that stop ATI from performing repeat attempts?
Steve,
When I backed up to external hard drives, I found the default of 5 attempts at 30 second intervals to be too quick; a total of 2.5 minutes. Because the total time was short I decided to use 30 minutes instead of 30 seconds. I understand what you are saying but it doesn't explain why the repeat attempts didn't take place today.
The backup is scheduled to start at 2PM, at 2:05 I woke the PC, and WiFi was active by 2:06. I was able to access the NAS share. I made sure the PC didn't go back to sleep, and it was active with WiFi at 2:30PM when the first attempt should have taken place. At 2:35 I checked ATI to see if the backup had started, but it hadn't. Maybe there is a difference in attempting to connect to an external hard drive and a NAS. It might think the network connection won't occur after one failure.
Gary, you may need to employ a Pre Command for your backup task to wake up the NAS if that is also going to sleep when idle.
An example of a Pre Command:
:: File Name = CheckIP.Bat @echo off :: --------------------------------------------------------------------- :: -- baseIP should be set to the device IP address to be checked for -- :: --------------------------------------------------------------------- set baseIP=192.168.0.29 set loopcount=20 :: Checking for active baseIP address on local network :: errorlevel 0 = IP found / 1 = IP not found. :loop echo pinging %baseIP% for %loopcount% times ping -n 1 -l 1 %baseIP% > nul if %errorlevel%==1 goto next @echo %baseIP% found active on network! timeout /t 10 exit /b 0 :next @echo %baseIP% not found active on network! set /a loopcount=loopcount-1 if %loopcount%==0 goto exitloop timeout /t 10 goto loop :exitloop if %errorlevel%==1 exit /b 1 exit /b 0 : pause
Steve,
Thanks for the Pre-Command example. I plan to change the number of attempts to 10 and the interval to 1 minute. The NAS is a Synology DS918+, and I checked the logs today and didn't notice anything about it going to sleep. I've also looked at the Synology forum and noticed a number of posts about failures to hibernate, which I think is their sleep.
I looked at the backup_worker log for yesterday. Acronis didn't wake the PC from sleep as the first log entry was at 2:05:01PM, which was the time that I woke it. ATI couldn't access the share folder for the backup, issued a 5017 retcode, and exited at 2:05:03PM. No attempts were made to retry the connection.
I checked the backup_worker log for the backup that ran after I waited 30 minutes for the retry. The connection was made to the NAS and the backup ran successfully.
It appears that ATI doesn't perform retries if the backup destination is a NAS and the first connection attempt fails.
Acronis didn't wake the PC from sleep as the first log entry was at 2:05:01PM, which was the time that I woke it.
Gary, please check your Power Options and in particular that you have Wake Timers enabled so that ATI can wake the PC from a sleep state.
The above image is from my laptop which wakes up just fine to perform various scheduled backups including to my own Synology NAS.
Steve,
I've changed Allow Wake Timers to Enable for Battery and Plugged In. Battery was disabled and Plugged In was Important Wake Timers Only.
Last night I found another option that required change. "Run operations at system startup with delay (in minutes)" was set to 0. I changed it to 2 minutes. I felt the 0 minutes didn't give the PC any time to activate WiFi. In the past I always ran non-scheduled full backups, so I made sure WiFi was active and the PC could connect to the NAS before starting the backup.
I've made the same changes to my PC too. I plan to setup the Pre-Command today. If I have questions about the setup, I'll get back to you.
I have another question. Do you do full backups to your NAS via WiFi? I'm asking because mine were very slow and occasionally at night I would lose WiFi on my PC. For the night of a full backup I take my PC to where the router is located and connect it via Ethernet for the backup. I'm just wondering about what others do.
I have another question. Do you do full backups to your NAS via WiFi? I'm asking because mine were very slow and occasionally at night I would lose WiFi on my PC. For the night of a full backup I take my PC to where the router is located and connect it via Ethernet for the backup. I'm just wondering about what others do.
Yes. I very rarely take the laptop to where I could plug into an ethernet cable & can't remember if I have ever done with this specific laptop!
I did invest a little while back in a Netgear Orbi wireless mesh system for home which improved my wireless coverage significantly and stopped a lot of the connection / dropout issues I had previously when using powerline type wifi plugs. I have the main Orbi router sitting near my cable broadband modem/router box, then 2 satelite Orbi boxes spaced out, one downstairs and the other up. Orbi wasn't the cheapest option but has been well worth the money spent.