It would be nice to add a comment to an *existing* backup. i.e. a backup operation previously made, but now notable for some reason....

thanks

Hi bullshark,
+1

The ability to add comments (at one or other phase of a backup task) has been discussed at least once in the past (although most of that discussion possibly occurred on the earlier 'version 5' Forum.)

To be fair to Macrium's developers, I can see how it might be tough to allow us to reliably 'associate' a particular comment with a particular backup, or even with a particular backup set, given the wide flexibility in our backup Retention Rules and the 'Synthetic Full' options - where older backup files in a set will be automatically deleted (or be merged or 'incorporated') - hence making it awkward or impossible to maintain a logical connection with any notes that we'd embedded into those files.

So it would obviously be necessary to 'manage' our comments at some level higher than the level of our specific backup-image files, even though it's exactly those files which (speaking for myself) I want to 'annotate' with my backup-related notes!  Perhaps (Macrium developers ...) there could be some way to let us insert our own notes into the HTML LOG files that Reflect creates for each backup?

In the meantime I am manually 'adding' notes to my backup tasks by creating text files in the folders alongside my .mrimg image files. It's a clunky and time-consuming solution which requires me to take yet more care when - at some later date - I will want to correlate those notes with their matching backup-sessions. Then, to add to the clunkiness, and because I make good use of the Synthetic Full incremental backup scheme, I need to visit those backup destination folders periodically to move those still historically-relevant left-over text files aside! (I don't delete these notes until I know that I'll no longer need that parrticular backup *set*.)

Macrium Reflect is an almost perfect backup solution IMO, but this absence of a readily accessible, per-backup notes mechanism is the 'flaw' that niggles me the most.
Colin P.


--
Two backups is one backup too few.

In the meantime I am manually 'adding' notes to my backup tasks by creating text files in the folders alongside my .mrimg image files.

Ditto.  Not unrelated, I think, to RefDM's suggestion about the need for some additional capabilities for the post-operational manipulation and usage of specific data pertaining to Reflect's backup files and sets.  Information that is "locked into" backup files themselves isn't entirely adequate for some potentially very useful "follow-up" applications. That is likely to become increasingly apparent as more users respond to ongoing CMC developments.


Regards, Richard V. ("Arvy")