DB Mirroring Networking Issues

  • Hello,

    I am currently working on a database mirroring setup for 10 databases each under 5 GB.

    When i enable mirroring on the Principal server, even before i actually start mirroring databases i noticed that network wait increases. I am using Quest Performance Analysis to monitor my Principal and my Mirror.

    I haven't found documentation on this type of wait (DBmirror Events Queue, DBmirror CMD) and don't know if I should be concerned or if this is normal.

    As i try to add new databases for mirroring i noticed that these wait events increase and at 5-6 databases network workload starts to be a problem as it rises to 80-90% although performance monitor on both mirror and principal report a maximum of 200 KB / sec transfer.

    Both Principal and Mirror have a Gbit network card and they're both in the same private lan.

    If you have any suggestions on what i should monitor please give me a hint.

    Here is a screenshot of what Q. Perf. Analysis signals as a network performance problem.

    Thank you.

  • Hi Zgondea Paul,

    Hi there...I cannot answer your question only concur with exactly what you have found here.

    I last week I started mirroring from our 2008R2 sql 2 node cluster to a separate 2008R2 standalone server. So far I have mirrored x2 databases 1 live and 1 test. I too noticed the mirror network wait increase straight away so I decided to remove the test database from mirroring and noticed a small drop. You will see this quite clearly from my screenshot (see attached). I plan on mirroring x4 db's from the cluster after watching how things go for the next 5-7 days.

    Iam finding it difficult to find info on what I should expect here.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply