Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a SQL Server 2008 R2 database instance running on a VM. Nightly, between 10p and 12a, we are getting the following error message:

DATE/TIME: 2/3/2014 10:16:37 PM

DESCRIPTION: Database mirroring connection error 4 '64(The specified network name is no longer available.)' for 'TCP://'.

We have determined these alerts are happening at the same time the Veeam backup up is running.

Is there a way to turn OFF the SQL Server Alerts from 10p to 12a ?

share|improve this question
up vote 3 down vote accepted

To answer your direct question, I'd probably go about that with a dedicated SQL Server Agent Job to toggling the alert enabled status with the duration of that time.

To disable that alert:

use msdb;

exec dbo.sp_update_alert @name = 'YourAlertName', @enabled = 0;

And then 4 hours later (either as a separately scheduled job, or with just a WAITFOR DELAY in the initial job that does the disabling):

use msdb;

exec dbo.sp_update_alert @name = 'YourAlertName', @enabled = 1;

That's the short answer. But the more thorough one would be a question... Why is your process during this time causing this error? Unfortunately I can't advise without digging quite a bit deeper into what that is or what it is doing, as I'm not familiar with Veeam. But the point I'm trying to get across is, instead of silencing an alert during this timespan, I'd be even more interested in finding out why that process is causing that error, in turn triggering the alert.

share|improve this answer
We believe the reason is a configuration issue on the esxi host. It doesn't have very much memory allocated to the server and the Veeam host is actually one of the machines on the host. We believe the true fix would be to add a physical machine to run Veeam. (I could be wrong - limited knowledge of exsi) We're going to go through another wave of improvements soon, and this is just a temporary fix. – petemill66 Feb 7 '14 at 19:04

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.