So I gather I shouldn't use WSB for Exchange?

  

Jean-Paul Natola

 


From: [email protected]
To: [email protected]
Subject: RE: [Exchange] event 218 after backup
Date: Mon, 16 Jun 2014 22:18:29 +0000









Doesn’t really matter.
 
WSB freezes all Exchange databases at the same time. It ain’t smart enough to 
do one at a time.
 


From: [email protected] [mailto:[email protected]]
On Behalf Of J- P

Sent: Sunday, June 15, 2014 11:11 PM

To: [email protected]

Subject: RE: [Exchange] event 218 after backup


 

What is odd, is that it occurs on both DB (one that is 75GB and the other which 
I created for testing 4 gb)



  

Jean-Paul Natola

 








Date: Sat, 14 Jun 2014 23:47:42 -0400

Subject: RE: [Exchange] event 218 after backup

From: [email protected]

To: [email protected]
"Yes, and judging by your question, I guess it should not be checked?"
No, it should be checked. I could see if VSS wasn't being used that a backup 
could mess with the database somehow

On Jun 14, 2014 7:29 PM, "J- P" <[email protected]> wrote:


Yes, and judging by your question, I guess it should not be checked?



  

Jean-Paul Natola

 








Date: Sat, 14 Jun 2014 18:07:36 -0400

Subject: Re: [Exchange] event 218 after backup

From: [email protected]

To: [email protected]
Do you have the full database with VSS option checked?


On Jun 14, 2014 5:14 PM, "J- P" <[email protected]> wrote:


Hi all,



I have an ex2013 , running on 2012hyper-v guest, after the backup of the 
databse completes, email stops working for some minutes, then this error is 
logged



the copy of database 'DB_Name' on this server experienced a performance 
problem. Failover returned the following error: "There is only one copy of this 
mailbox database (DB_Name). Automatic recovery is not available.". For more 
detail about the failure, consult
 the Event log on the server for other storage and "ExchangeStoreDb" events.





To humor myself I created a new DB moved a couple of mailboxes to it, and after 
the backup the same error was logged.





This is single server setup, no DAG involved, using built-in windows server 
backup



Any thoughts on why this only occurs after backup?



 









                                          

Reply via email to