Hi Mirza,
Thank you for the details on the unexpected behavior and the case number.
The issue itself based just on the errors you're reporting look to be connectivity related, though I understand you have done a bit of work on this front already and looks like it was able to resolve the issue for some of the databases, but not all. No known issues at this time match the behavior and it looks more environmental at first blush.
The case is currently with our Advanced Technical Support, so please continue the research along with Veeam Support, looks like there are some steps to check from the most recent correspondence, and hopefully the joint research will identify why these last few DBs are having challenges.
Thank you for the details on the unexpected behavior and the case number.
The issue itself based just on the errors you're reporting look to be connectivity related, though I understand you have done a bit of work on this front already and looks like it was able to resolve the issue for some of the databases, but not all. No known issues at this time match the behavior and it looks more environmental at first blush.
The case is currently with our Advanced Technical Support, so please continue the research along with Veeam Support, looks like there are some steps to check from the most recent correspondence, and hopefully the joint research will identify why these last few DBs are having challenges.
Statistics: Posted by david.domask — Oct 03, 2024 8:06 am