We are doing agent-based backup of some standalone physical Win2016 servers with Microsoft SQL 2016, Veeam upgraded to B&R 9.5 U4 and Agent version 9.5.0.1536.
When the SQL backup kicks in, it does a snapshot snapshot - backs up - truncates logs - finishes.
During this process existing SQL connections has increased response time, and new connections are set to status WAIT and then timeout.
Is this a common problem? Any suggestions to resolve?
Sorry for doubleposting, first posted this in the Agent for Windows group but here is probably more on target.
-
olavl
- Influencer
- Posts: 13
- Liked: 1 time
- Joined: Jan 23, 2018 8:21 am
- Full Name: OL
- Contact:
-
Dima P.
- Product Manager
- Posts: 14773
- Liked: 1719 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Freeze when backing up MSSQL on physical
Hello Olav,
You may see such behavior when your SQL server is a bit low on compute resources: whenever backup is performed agent issues the snapshot creation and uses it for backup. This operation is resource consuming, so SQL server might start to throttle it's own activities whenever it sees the lack of RAM or CPU. May I ask if you see any negative effect on your production databases? Thank you in advance.
You may see such behavior when your SQL server is a bit low on compute resources: whenever backup is performed agent issues the snapshot creation and uses it for backup. This operation is resource consuming, so SQL server might start to throttle it's own activities whenever it sees the lack of RAM or CPU. May I ask if you see any negative effect on your production databases? Thank you in advance.
Who is online
Users browsing this forum: No registered users and 8 guests