Group: Forum Members
The 1 at the end of the “core” name (before the automatic numbering at the end) is Reflect’s naming collision avoidance mechanism for cases where the pattern-based name already exists at the destination. I would have expected that running the purge before the backup would solve this. But maybe Reflect’s code evaluates the existing backups to determine the new file’s name before executing the purge. I can’t think of a way to script around this that would be both clean and reliable. A clean way would be to write something that said, “Take the current day of the week and delete any backups that have that day in their name.” I wouldn’t feel comfortable using something like that — maybe adding a constraint of deleting only the oldest matching backup? — but that would be pretty easy to write in PowerShell if you feel you’d be comfortable with it.
In terms of getting rid of the 00-00, that would require renaming the file after the fact. That would be pretty easy to script.
However, both of the script behaviors described above — deleting backups and renaming them — would be blocked by Image Guardian. So you’d have to decide whether disabling that protection would be worth the naming outcomes you want. If so, I could help with this after the holiday.