Grooming Policy Too Simplistic in Professional Posted yesterday at 06:31 AM · Edited 2 hours ago by DavidHertzberg Insert next-to-last paragraph about Restore of an entire source volume from a Backup Set that has been Groomed for "transients"—enhancement considerably less attractive · Report reply x509, Actually you may be smoking more-powerful stuff than you think you are.😄 How about having a one-bit flag in the Catalog for a Backup Set that marks a file as "transient" if it has been backed up N times in the last N days/weeks—which it would have been because its file size or contents kept changing while its name and directory stayed the same? It would be safe (but see the next-to-last paragraph for when it wouldn't be) to keep only the latest backup of such "transient" files—regardless of legal requirements—so long as they aren't in certain directories known to possibly contain business-critical files. It would probably be safest to have the Windows/Mac variant of Retrospect automatically avoid doing "transient" flagging in such directories. There would no doubt have to be an additional checkbox for each Backup Set's Grooming Options , with a subsidiary checkbox specifying whether "transient" flagging is to be done on a daily or weekly basis. There could then be a Built-In Selector (see page 437 of the Retrospect Windows 16 User's Guide; the Retrospect Mac term is Rule), usable only in a Groom script—as opposed to a Backup or Proactive script, that would be used to Exclude all files marked as "transient" unless they have the date of the latest backup per the Backup Set Catalog. Such a Groom script could be run after the last of the daily/weekly backups to a Backup Set. However, for Backup Sets whose Grooming Options have the additional box for "transient" flagging and which has been Groomed for "transients", a Restore would have to use the Catalog File—rather than a Snapshot—for any files flagged as "transient" regardless of whether a previous Snapshot was chosen to restore an entire source volume. This would not be good for situations in which the source volume has been backed up and "transient"-Groomed since undetected ransomware encrypted it, or in which the latest versions of some applications files turn out to have been erroneously updated by the user—a situation which has happened to me. That makes this enhancement sound considerably less attractive. Here is why and how to submit a Support Case for an enhancement.