Have you tried just rebooting the server to see what happens? You obviously need to make sure you can do this, and then try to factor in issues caused by snapshotting or other issues.
From: bounce-9519603-8066...@lyris.sunbelt-software.com [mailto:bounce-9519603-8066...@lyris.sunbelt-software.com] On Behalf Of Paul Cookman Sent: 28 May 2012 12:31 To: MS-Exchange Admin Issues Subject: RE: dag issue? What I don't understand is why it effected all databases on the server when there was only one DB in the dag, it doesn't sound right because what if I wanted to have an active active? From: Steve Goodman [mailto:st...@stevieg.org]<mailto:[mailto:st...@stevieg.org]> Sent: 28 May 2012 09:07 To: MS-Exchange Admin Issues Subject: RE: dag issue? If it's multi-site yep Steve From: Paul Cookman [mailto:paul.cook...@selection.co.uk]<mailto:[mailto:paul.cook...@selection.co.uk]> Sent: 28 May 2012 08:49 To: MS-Exchange Admin Issues Subject: RE: dag issue? This does sound like what happened, I was a bit surprised as I only had one test DB in the Dag, I didn't expect it to effect all databases. Would you still go with having DAC mode on? From: Steve Goodman [mailto:st...@stevieg.org]<mailto:[mailto:st...@stevieg.org]> Sent: 28 May 2012 07:30 To: MS-Exchange Admin Issues Subject: Re: dag issue? As a first point of call I would look at increasing the cluster timeout settings. I've heard similar things about Veeam before during backup - mainly nodes failing over and IIRC there is some threads on the Veeam Community site about the issue. Steve Sent from my iPhone On 27 May 2012, at 11:07, "Paul Cookman" <paul.cook...@selection.co.uk<mailto:paul.cook...@selection.co.uk>> wrote: I had an issue Friday morning I wanted to run past someone. I have created a two node Dag multisite with witness in the primary site, DAC enabled. I am testing as I go so I only had a test DB as part of the DAG. (Servers are Virtualised and use Veeam for backups) While committing the snapshot the primary server momentarily lost communication to all servers and all the (LIVE) databases dismounted and wouldn't remount. In a state of panic I removed the Dag to get users working again. I think from going through the logs that possibly the remote site node got quorum of the witness and then it believed that the databases were up on the remote site (set to Activate only and not automatic by the way). Possibly if I had rebooted the remote server the primary would of got quorum again and allowed me to mount databases? Any thoughts on this as I need to be able to reboot the primary server if needed without the databases not being able to mount. I don't mind my failover being completely a manual process. What do you think on what happened and a solution to my problem? Kindest regards, Paul. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
