Hello all,
I am facing the issue in SQL server backup:
|
Hello all,
I am facing the issue in SQL server backup:
|
Nice issue
I think some people did not get the difference between Commvault support (or their partners that provide support) and this Community. (Though even while contacting Support a bit of information is required)
I’d add to
when did this start happening? anything change on the SQL end?
When did this last work?
What troubleshooting have you already done?
One thing to try is to increase the timneou.
To increase the VDI timeout, follow these steps
1. In the CommCell Browser GUI, right-click on the SQL iDataAgent (iDA) Subclient Instance and select properties. The General tab is where to modify the VDI timeout
2. Change the VDI Timeout value to 900 and select OK.
3. Start a new Backup or Restore.
4. Increase VDI Timeout value again if error reoccurs.
After the change is made, the following message will be displayed in the Event Viewer confirming the change was made.
Event Code 83:501: VDI timeout was changed from [original seconds] to [new seconds value]
Hi
In my case the problem was the time difference in seconds
The VDI timeout interval is the length of time the system waits for the SQL Server to respond to the backup or restore requests. During a backup or a restore operation, by default, Commvault waits 300 seconds in the first attempt. (5 Minutes)
Timeouts occur intermittently due to the large size of our databases. To mitigate this issue, one solution we propose is to adjust the VDI timeout values. By increasing these values, we aim to minimize or eliminate the occurrence of timeouts, ensuring smoother operations for our database tasks.
any one now how max we can set the vdi timeout?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.