I hope he's doing OK, and the damage isn't permanent. -- Espi
On Mon, Jul 28, 2014 at 7:29 PM, Michael B. Smith <[email protected]> wrote: > I'm tired. My 15 year-old broke two bones last night requiring me to > spend most of the night in the hospital. > > > > But COME ON! REALLY!? > > > > I asked you a series of very specific questions. You didn't answer any of > them. > > > > Good luck. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *David McSpadden > *Sent:* Monday, July 28, 2014 10:10 PM > *To:* <[email protected]> > *Subject:* Re: [Exchange] quorum failure > > > > Would I troubleshoot dag and from the same way? > > Sent from my iPhone > > > On Jul 28, 2014, at 10:07 PM, "Michael B. Smith" <[email protected]> > wrote: > > Perhaps change the subject? > > > > Have you looked at the event log? > > > > Have you looked at the cluster log? > > > > Have you looked at the FC log? > > > > What have you done beside run a report? > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *David McSpadden > *Sent:* Monday, July 28, 2014 9:58 PM > *To:* [email protected] > *Subject:* RE: [Exchange] DAG & DPM > > > > Why would my quorum start to fail?? > Exchange DAG Health Check Report > > Exchange Server Database Availability Group health check results as of > Monday, July 28, 2014 9:45:38 PM > > Database Availability Group *IMCU-DAG* Health Summary: > > *Database* > > *Mounted on* > > *Preference* > > *Total Copies* > > *Healthy Copies* > > *Unhealthy Copies* > > *Healthy Queues* > > *Unhealthy Queues* > > *Lagged Queues* > > *Healthy Indexes* > > *Unhealthy Indexes* > > *DB-Bronze* > > 081013VMEXCHB1 > > 1 > > 3 > > 3 > > 0 > > 3 > > 0 > > 0 > > 3 > > 0 > > *DB-Gold* > > 081013VMEXCHB1 > > 1 > > 3 > > 3 > > 0 > > 3 > > 0 > > 0 > > 3 > > 0 > > *DB-Platinum* > > 081013VMEXCHB2 > > 1 > > 3 > > 3 > > 0 > > 3 > > 0 > > 0 > > 3 > > 0 > > *DB-Silver* > > 081013VMEXCHB2 > > 1 > > 3 > > 3 > > 0 > > 3 > > 0 > > 0 > > 3 > > 0 > > *DB-Unlimited* > > 081013VMEXCHB1 > > 1 > > 3 > > 3 > > 0 > > 3 > > 0 > > 0 > > 3 > > 0 > > Database Availability Group *IMCU-DAG* Health Details: > > *Database Copy* > > *Database Name* > > *Mailbox Server* > > *Activation Preference* > > *Status* > > *Copy Queue* > > *Replay Queue* > > *Replay Lagged* > > *Truncation Lagged* > > *Content Index* > > *DB-Bronze\081013VMEXCHB1* > > DB-Bronze > > 081013VMEXCHB1 > > 1 > > Mounted > > 0 > > 0 > > False > > False > > Healthy > > *DB-Bronze\081013VMEXCHB2* > > DB-Bronze > > 081013VMEXCHB2 > > 2 > > Healthy > > 0 > > 0 > > False > > False > > Healthy > > *DB-Bronze\081013VMEXCHDR* > > DB-Bronze > > 081013VMEXCHDR > > 3 > > Healthy > > 0 > > 0 > > False > > False > > Healthy > > *DB-Gold\081013VMEXCHB1* > > DB-Gold > > 081013VMEXCHB1 > > 1 > > Mounted > > 0 > > 0 > > False > > False > > Healthy > > *DB-Gold\081013VMEXCHB2* > > DB-Gold > > 081013VMEXCHB2 > > 2 > > Healthy > > 0 > > 1 > > False > > False > > Healthy > > *DB-Gold\081013VMEXCHDR* > > DB-Gold > > 081013VMEXCHDR > > 3 > > Healthy > > 0 > > 1 > > False > > False > > Healthy > > *DB-Platinum\081013VMEXCHB2* > > DB-Platinum > > 081013VMEXCHB2 > > 1 > > Mounted > > 0 > > 0 > > False > > False > > Healthy > > *DB-Platinum\081013VMEXCHB1* > > DB-Platinum > > 081013VMEXCHB1 > > 2 > > Healthy > > 0 > > 0 > > False > > False > > Healthy > > *DB-Platinum\081013VMEXCHDR* > > DB-Platinum > > 081013VMEXCHDR > > 3 > > Healthy > > 0 > > 0 > > False > > False > > Healthy > > *DB-Silver\081013VMEXCHB1* > > DB-Silver > > 081013VMEXCHB1 > > 2 > > Healthy > > 0 > > 0 > > False > > False > > Healthy > > *DB-Silver\081013VMEXCHB2* > > DB-Silver > > 081013VMEXCHB2 > > 1 > > Mounted > > 0 > > 0 > > False > > False > > Healthy > > *DB-Silver\081013VMEXCHDR* > > DB-Silver > > 081013VMEXCHDR > > 3 > > Healthy > > 0 > > 0 > > False > > False > > Healthy > > *DB-Unlimited\081013VMEXCHB1* > > DB-Unlimited > > 081013VMEXCHB1 > > 1 > > Mounted > > 0 > > 0 > > False > > False > > Healthy > > *DB-Unlimited\081013VMEXCHB2* > > DB-Unlimited > > 081013VMEXCHB2 > > 2 > > Healthy > > 0 > > 0 > > False > > False > > Healthy > > *DB-Unlimited\081013VMEXCHDR* > > DB-Unlimited > > 081013VMEXCHDR > > 3 > > Healthy > > 0 > > 0 > > False > > False > > Healthy > > Database Availability Group *IMCU-DAG* Member Health: > > *Server* > > *Cluster Service* > > *Replay Service* > > *Active Manager* > > *Tasks RPC Listener* > > *TCP Listener* > > *DAG Members Up* > > *Cluster Network* > > *Quorum Group* > > *File Share Quorum* > > *DB Copy Suspended* > > *DB Initializing* > > *DB Disconnected* > > *DB Log Copy Keeping Up* > > *DB Log Replay Keeping Up* > > *081013VMEXCHB1* > > Passed > > Passed > > Passed > > Passed > > Passed > > Passed > > Passed > > *FAILED* > > n/a > > Passed > > Passed > > Passed > > Passed > > Passed > > *081013VMEXCHB2* > > Passed > > Passed > > Passed > > Passed > > Passed > > Passed > > Passed > > *FAILED* > > n/a > > Passed > > Passed > > Passed > > Passed > > Passed > > *081013VMEXCHDR* > > Passed > > Passed > > Passed > > Passed > > Passed > > Passed > > Passed > > *FAILED* > > n/a > > Passed > > Passed > > Passed > > Passed > > Passed > > > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Michael B. Smith > *Sent:* Monday, July 28, 2014 9:43 PM > *To:* [email protected] > *Subject:* RE: [Exchange] DAG & DPM > > > > There is almost always a reason. J > > > > Some of them take longer to figure out than others. You must consolidate > information from event logs, the DPM logs, and the crimson log. > > > > Also, DPM separates some capabilities that you may consider part of the > "backup" responsibility to the OS (e.g., dedupe - that is an OS > responsibility). > > > > I've been very happy with DPM, but getting it to be stable in a complex > environment can take some work. You can figure it out by yourself, with a > consultant, or with MSFT support. > > > > To Dan's original question... there are two different Exchange VSS writers - > one for the replica and one for the primary. They both have to be working > properly. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Daniel Chenault > *Sent:* Monday, July 28, 2014 4:06 PM > *To:* [email protected] > *Subject:* RE: [Exchange] DAG & DPM > > > > Oh yeah, I REALLY dislike how DPM is not very helpful when it runs into > problems. > > "There is a problem with VSS on the source machine." > ------------------------------ > > From: [email protected] > To: [email protected] > Subject: RE: [Exchange] DAG & DPM > Date: Mon, 28 Jul 2014 20:03:13 +0000 > > I would like to follow this convo as well. > > I continue to get DPM errors but no real reason that I can figure? > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Daniel Chenault > *Sent:* Monday, July 28, 2014 3:55 PM > *To:* [email protected] > *Subject:* [Exchange] DAG & DPM > > > > I inherited this setup and am just trying to make heads or tails of the > continuing problems (mostly "replica out of sync"). > > How does DPM handle the log files in a DAG? Does it only backup the active > DB and... then what? I've read two books thus far on DPM and Exchange and > neither went into the actual workings under the hood; mostly screen shots > of how to set this or that up. > > Had a situation where a backup kept failing for no good reason I could > see. Had to failover the DB to it's partner (unrelated) and all of a sudden > the logs cleared. > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > Please consider the environment before printing this email. > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > > > Please consider the environment before printing this email. > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > > > Please consider the environment before printing this email. >
