I can't speak for @StanoSedliak, but we had the same issue, using MSSQL for the DB. In our case, the provided hotfix didn't fix anything but, considering the poor performance of the rep that we were dealing with, I don't find that surprising. In the end, I gave up on Veeam support for this issue and recreated all relevant backup jobs. If a restore is required in the next two weeks, we will have to manually import the old backups and perform the recovery for our customer, and we';ll have to remember to manually remove the old backups after we hit a complete retention cycle on the new jobs. To me, this was a HUGE bug and brought our v12.1 rollout to an immediate halt.
Statistics: Posted by RubinCompServ — Feb 02, 2024 2:47 pm
