Vitaliy S. wrote:What kind of records are you doing? Will backup indexing backup files help in your scenario?
Here's a small example- just to illustrate:
On a specific day X, I decide to upgrade to Windows 1X. Everything seems to work just fine at first, but after some 10 days or so - I begin to experience problems to the degree that I finally get nowhere, so I decide to roll back to my previous "last known good" state. As VEP backs up my system every night, all I now need to do - is to remember exactly which day it was that I did the fatal upgrade. Regretfully I cannot remember, and there's nothing in the backup anywhere that can help me find the right date.
What I need is a way to record (note down) comments to each, any, none or all backups along the way, so that I can easily recall the chain of events from one day to the next.
It doesn't help me much to have 31 backups for August as long as I cannot tell them apart except for the date of the file.
That's why I now have to punch a separate excel file, recording everything I do, so that I know what to look for. I think a modern Backup system should provide that feature - at least allow me to rename each file name to something meaningful to me - without Veeam loosing track of history, sequence and generations, thus being able to restore a working bare metal disk independent of how backup files were named. Alternatively, if it is mandatory for you to strictly follow a specific naming convention, then at least support some form of editable text-only meta-data tag attached to each backup file. And keep copies in a local DB so that global search can be made to locate the right backup to restore from. As it is now, I cannot even search easily across generations of backups to locate a specific version of a file, folder or sets of such.