foggy wrote:As I've mentioned in my first post above, the general requirement is not to have multiple repositories pointing to exactly the same location
Now that I realize is going on, I totally agree with you.
foggy wrote:since this can result in multiple issues, including the observed behavior. You've seen one of the issues caused by how metadata handling is currently performed (which is fixed by the hotfix you obtained)
Ok understood, jobs pointing the exact same share location has caused issues with the metadata which has caused some sort of corruption with my backup job association with files. I wish the KB mentioned creating sub-folders. Come to think of it, I'm regretting finding that KB article and just leaving the Backup Jobs to 20 restore points.
foggy wrote:So ideally, you should avoid repositories pointing to the same location.
I would like to point out that the current and previous support person working on the case has not once said anything about pointing the backup jobs to different sub-folders (feel free to scan the case notes). The only thing that has occurred is a patch was provided that has now made everything worse even though Backup Copy Jobs are disabled. I have started including my account manager in the communication going back and forth. I'm sure you can understand my frustration.
Looking forward to sleeping better each night when this is all over and Backup Jobs are back to normal!
@mkaec, thank you for the clear instructions. As soon as Veeam support make this recommendation I will make the changes to the Backup Jobs.