5 hours ago
Fwiw I'm not new to imaging. I've been using different kinds of software for this task since Norton Ghost on MS-DOS. But, there's a decided difference between creating an imaging program to be run manually when you need it and using an imaging program to keep up with unattended backups. Until my PC took a nosedive 4 years back I had imaging software set up to run unattended on a monthly schedule. Day 1: Full; Every Monday: Diff, every other day of the month: Inc. I manually moved the oldest of the last two complete sets to an unattached drive at the beginning of each month, and I kept 6 months worth of backups on that drive. I kept a copy of that unattached drive at a different location as well. (Now I just hobble through on a laptop until Intel comes up with a decent home user desktop CPU for or I give up on them and go AMD.) I kept an eye on things, but didn't want to have to constantly babysit the operation.
My point being, it seems to me Hasleo wants to live up to standards of scheduling unattended imaging backups, and I think it's fair for expect such an imaging program to continue an unattended backup sequence after a hiccup, like a change in drive geometry. I would agree with @n8chavez if the program were designed to only be used to image/clone a drive when you needed to. But it's not. And from Hasleo's reponses in this thread it seems they agree with how I view the situation.
My point being, it seems to me Hasleo wants to live up to standards of scheduling unattended imaging backups, and I think it's fair for expect such an imaging program to continue an unattended backup sequence after a hiccup, like a change in drive geometry. I would agree with @n8chavez if the program were designed to only be used to image/clone a drive when you needed to. But it's not. And from Hasleo's reponses in this thread it seems they agree with how I view the situation.