ACPHO B.40173 on Win11 Pro: error 60612: backup cannot be started, "Plug in external drive"
This regular backup job was working happily two weeks ago. I shut down the computer while on vacation, and when I returned ACPHO updated to Build 40173 and now I get this error when trying to do a backup to my USB 3.1 connected DAS. My backup location and files are easily visible to Windows explorer. So what's the problem? All my windows updates were also applied and the system rebooted. Thanks!
Thanks for the response, Ian. It's a workaround but not a solution, really.
I tried the first pathway "double click on the destination and reset the destination drive" but it clearly doesn't want to continue to use the existing backup scheme. See screen snip 2022-10-19_13-30-25.png. So I created a new backup path and told it to save to that, as per the second screen snip 2022-10-19_13-32-15.png. It seems to be performing a backup of some kind now, but I'm not confident that the system will keep working into the future.
So my question is: why did the backup scheme break like this? Why wouldn't ACPHO just continue the existing working backup scheme that was in place before my holidays and not modified? If I can't rely on the backup system working through reboots and software upgrades, it doesn't seem like I'd want to continue to use this system.
paulrob wrote:Thanks for the response, Ian. It's a workaround but not a solution, really.
I tried the first pathway "double click on the destination and reset the destination drive" but it clearly doesn't want to continue to use the existing backup scheme. See screen snip 2022-10-19_13-30-25.png. So I created a new backup path and told it to save to that, as per the second screen snip 2022-10-19_13-32-15.png. It seems to be performing a backup of some kind now, but I'm not confident that the system will keep working into the future.
It is rather odd that it thinks you are setting a different location when you are not. The only explanation is that somehow the settings became corrupted - something that really should not happen.
The second screen snip is not "attached" so I cannot comment on it.
paulrob wrote:So my question is: why did the backup scheme break like this? Why wouldn't ACPHO just continue the existing working backup scheme that was in place before my holidays and not modified? If I can't rely on the backup system working through reboots and software upgrades, it doesn't seem like I'd want to continue to use this system.
No idea why it broke - but it definitely should not have done so. As I said earlier it looks like corruption of the settings. [There may be something in one of the log files that will suggest what went wrong.] There is a "zap" tool that can be used to delete all settings. I have never used it. You then (apparently) can reconfigure backups - you would then, presumably have to add them back as the task has been deleted.
I work on the basis that things are likely to go pear-shaped when you least expect them to do so. I have multiple backup tasks to multiple locations: Acronis Cloud, my Synology NAS, to local disk drives and sometimes USB disk drives. On mission critical PC's I also have other backup solutions as well as ACPHO.
Afterthought: Could the issue have been triggered by a firmware upgrade to the DAS? Cannot think why it would lead to this problem. It could be a driver issue: on one of my PCs backups to my NAS are killed because the NIC stops working - checked the power settings and power mode is not set to go into power-saving. It is a real pain.
Ian
IanL-S wrote:
No idea why it broke - but it definitely should not have done so. As I said earlier it looks like corruption of the settings. [There may be something in one of the log files that will suggest what went wrong.] There is a "zap" tool that can be used to delete all settings. I have never used it. You then (apparently) can reconfigure backups - you would then, presumably have to add them back as the task has been deleted.I work on the basis that things are likely to go pear-shaped when you least expect them to do so. I have multiple backup tasks to multiple locations: Acronis Cloud, my Synology NAS, to local disk drives and sometimes USB disk drives. On mission critical PC's I also have other backup solutions as well as ACPHO.
Afterthought: Could the issue have been triggered by a firmware upgrade to the DAS? Cannot think why it would lead to this problem. It could be a driver issue: on one of my PCs backups to my NAS are killed because the NIC stops working - checked the power settings and power mode is not set to go into power-saving. It is a real pain.
The DAS firmware was updated in January 2021, and is the latest from QNAP (it's a TR-002 with FW 1.1.1) so there's been no DAS FW updates. Currently it has 2 HDDs configured as 16 TB in Raid 0, 14.5 TB usable, 8.7 TB free and my pc has a 2TB SSD only half full, so there's heaps of backup space available.
I agree things go pear shaped according to Murphy's Law, so this is not my only backup system, I have two others on different media and different methods. But that's why I have multiple backups, for when one fails like this...
The Acronis backups are failing yet again with the same error codes after having built a new backup job in a different path on the DAS.
Where can I find the ZAP tool please? My only other alternative would be to uninstall and reinstall the ACPHO, but that doesn't remove the registry settings I think.
Thanks. Paul
Paul, task zap is a command that can be issued for the Acronis Scheduler Manager tool when it is being used, and will remove ALL Acronis scheduled tasks, so that they will need to be rescheduled after its use. Link to the tool in my signature. The tool is a stand-alone program with no installation needed.