SQL Server getting error VDI timeout attempts expired for SQL Database

Nice issue @Abhi.M, now seriously what do you expect from the community? Should we shoot with hail? The amount of information you are sharing is so limited. Before we can even think of offering help you will definitely have to deliver more information and context about the environment, the problem etc.

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 @Onno van den Berg ‘s a special mention about what has already been troubleshooted on your side, because, yes, we do have more and more topics here (and even in our real lives) we’re escalated/reported but without background information AND no troubleshooting. 😐

Hi

In my case the problem was the time difference in seconds

@Abhi.M 

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?