New
#11
Hi,
Possibly
I see it another way
I never know exactly when I want to make an image
So I don't use a schedule and do a full when I want too :)
Could just be a default setting quirk to prompt you to upgrade for that feature
Hi,
Possibly
I see it another way
I never know exactly when I want to make an image
So I don't use a schedule and do a full when I want too :)
Could just be a default setting quirk to prompt you to upgrade for that feature
The schedule is set.
I will not divulge the reason behind my previous schedule inability. If I did, the local assisted living facility might proactively pick me up!
Thanks for the help--
Mark
You're welcome and glad to see you got this solved :)
I had to come back and say how incredibly pleased I am with Reflect. Being a refugee from the increasingly meaningless, convoluted iterations of Acronis' UI (apparently looking for some reason to justify yearly new versions apart from OS arrivals) vs. Reflect's simple and clear UI one wonders how Acronis could still be in business. After I stopped thinking in terms of complexity and just paid attention to Reflect's screens I am one amazed user.
One question that I've had from Acronis and now for Reflect. There's the option to validate existing backups and another option to validate upon restore. If validate is done during the initial backup and then the file just stays put on the drive from then on, why the need for all this after the fact validation? Such post validation is never necessary for an ordinary folder/file backup or opening an Excel, Word or whatever file after years of not using.
FWIW, using the free version for home use, I can see only one reason to possibly purchase the software at some point--email notification upon failure.
Post validation is indeed not obvious. But an image can, like any other record in the system, get corrupted at any time of it's existance. Then you will have trouble with the restore and a post-validation may tell you the cause.
As a practical matter, is there consensus here regarding setting a profile to periodically validate and/or validate prior to restore?
No idea whether there is consensus. I myself never do any validation. But I make frequent images so if one does not work I take another one.
I'm not sure of a consensus either, but I wouldn't make any assumptions that a successful validation means that you will necessarily have a successful restore. Put another way---I can't recall an instance where it was known that an unsuccessful restore would have been successful if only the user had validated the image. The unsuccessful restores are more often attributable to operator error or unknown reasons.