I've had a problem with Backup & Recovery 17 for a few months now. I use it to perform bi-weekly image backups of my Windows 10 system disk (Disk 0). The backups are saved to external drive M: The backups complete successfully for a week or two, then one day I open the program and one or more of the most recent marks on the timeline have gone orange. The message is
Not Available
Description: Failed to find the backup files
Solution: Check the network path (where this backup is resided) can be reached from this PC or the external storage device is connected
The device is connected, available to all users and the files are there right where Backup & Recovery put them. Today the most recent entry is orange, the two before it are green, all the files are on the same disk!
I started digging around in the program files and I find entries like this in the "jobs.log" file:
Jobs databases are stored in C:\ProgramData\Paragon Software\Hard Disk Manager 17\storage\jdb. Not sure if you can edit them though -- or whether the product will work correctly afterwards. It's recommended to modify the backup job using HDM17 launcher itself.
If you need to restore these backups, assuming they're not corrupted -- you can try 'Restore from File' feature.
Thanks for the reply. I used "DB Browser for SQLite" to inspect the contents of both .db files. There was nothing in either file that looks like a file path name. In fact, I can't find the job descriptions anywhere in ProgramData or Users. Well hidden or I'm not looking in the right places.
Enough time has passed that the problem files have been removed by the retention policy and things seem to be working normally. Perhaps it was just a Disturbance in the Force.
On trying to find the file made by a 'backup files' run, I find the destination empty and Restore fails to point to an existing backup file (HDM 17). This has happened three times in a row. Since I am a small business person with constant time pressure, you can imagine that I have little choice but to find software where tis functionality works smoothly. Perhaps there is a quick fix for this problem; but this route is for programmer-type persons.
This message is for your info. No need to reply.