Group: Forum Members
Can't answer your main questions, but fyi if you want to allow your script to delete images, you won't be able to use Macrium Image Guardian, so if you decide you're willing to give that up in order to maintain your existing setup, make sure you permanently disable that (or don't install it in the first place).
You might also be interested in some of the discussions that have occurred around here recently about verification. In short, if you're initially capturing the image locally, you would be especially unlikely to ever see a verification failure; the (relatively) greater risk is actually copying the file to a remote location, which is why it would actually make more sense to verify the image from its permanent location, even if that's slower. But "more sense" is to the extent that verification makes any sense at all, which again has been discussed quite a bit, thanks in part to insight from Macrium themselves. The only scenario I've seen suggested where verification can add value would be as an early warning system for a destination storage device (or its cable) that has gone bad -- but in that case, chances are you'd see corruption in any other files you tried to store there, and obviously you're not verifying all of your regular file copies. Other than that, in case you're unaware, verification does NOT check the image contents against the original source data to confirm that everything was backed up accurately; it simply confirms that the image file itself is completely readable and does not have any internal corruption that would render it unusable. But of course a successful verification immediately after a file is created is absolutely no guarantee that the image will still be intact whenever you need to restore something from it. Additionally, if you're verifying an Inc or Diff backup, the verification routine also only verifies that one image file, NOT all of the parent backups in the chain that would also have to be intact in order to restore it. This is why I skip verification in favor of frequent backups to a daily disk rotation, the latter of which brings other benefits. I personally believe that even Macrium doesn't see much value in verification. Their KB article about it says they estimate less than 1 in 1000 systems (not backups) will ever see a verification failure, and the verification option wasn't even added until Reflect V6, which suggests to me that it was added only due to satisfy customer demand and eliminate a perceived competitive disadvantage, and NOT because it was actually considered technologically important. Sometimes it's easier to appease the masses rather than educate them.
Just some food for thought.