Scheduled Manual FULL Image after Disk Geometry Change

[JayDee]

I think you missed my point.  I understand that your current approach to SYSTEM images (fixed in v5.4.2.3) is somewhat adequate for that issue, but it is not adequate for those users primarily using DISK/PARTITION imaging.

I, like many other users, know what partitions we need for a successful reBOOT.  As a result, I use DISK/PARTITION imaging to include my needed System partitions as well as other important partitions contained on that same disk.  The added function in v5.4.2.3 DOES NOT WORK for DISK/PARTITION imaging.  The result of that failure is/can be as follows...

When using TASK-based imaging, the imaging operation (any image type, scheduled or manual) does not inform the user that they no longer have certain partitions being imaged that were originally in the task spec.  Any attempted recovery operation WILL NOT recover any previously changed partition geometry... why, because they no longer exist in the images being taken since the geometry change.  What's worse, if a user's RETENTION spec removes the only versions of those geometrically changed partitions, the user has no previous references to their originally changed partitions, ie, dead in the water.

Since the most important partition on the System, the OS partition, occasionally gets changed by MicroSloth due to space needs on updating Windows Recovery partitions, without notice to the user by the way... this turns out to be a recipe for disaster, especially for those who rely on set'n'forget task imaging.

I don't know what type of partition geometry checking you are doing, but it needs to be improved very soon.  Other major imaging apps, Macrium REFLECT being the somewhat gold standard, do exactly what's expected here.  They detect a geometry change in whatever type of image is being done and force a new FULL image, restarting the imaging chain with the new geometry... the only real flaw here is their app doesn't tell the user of that fact, they just discover it along the way  .  You should do the same thing with, hopefully, a user notice 

Just so I can understand... if there's a geometry change 5.4.2.3 will initiate a full backup but not necessarily all the previously specified partitions?
So, at the moment, I would need to create a new backup task instead?

JayDee