Server Fault is a question and answer site for system and network administrators. 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

In my environment I have setup Exchange 2007 in an CCR cluster, mirroring our main servers to a set of servers in passive mode. One of the partitions on the passive node that I have setup for the logs for Exchange 2007 has faulted, causing the partition to be unreadable. I have replaced the partition on the passive node, and setup the drive to mirror the one in active mode, but the logs are not replicating since the change.

Is there anyway to force the replication of the new drive for the logs to the new partition? Any idea why the logs are not replicating?

Any help or comments is appreciated, and thanks in advance.

share|improve this question
Have you re-seeded the database on the passive node? – Shane Madden Sep 5 '12 at 1:50
Hi Shane, this looks like the route I may need to take. Thank you for your support! – Jake A Sep 5 '12 at 2:15
Hello Shane, I ran into another issue today with the passive node. I have not re-seeded yet, as I just found that 2 of the DB's are dirty. My question is, how do I proceed from here? Should I repair the DB's first, or should I re-seed? Any ideas? – Jake A Sep 5 '12 at 15:07
Is it showing as dirty on the active node, or the passive one? – Shane Madden Sep 5 '12 at 16:14
Just on the passive one. The active one says clean on all DB's. Also, I ran eseutil | M L on both nodes, and the logs are clean on both the active and passive. – Jake A Sep 5 '12 at 16:16
up vote 2 down vote accepted

With the active node's databases in a good state and the passive node's in a dirty state (and transaction logs not being copied and replayed), a re-seed is the appropriate next step.

It brings the passive node's database back to a working current baseline by copying the current data from the active node, and allows for the log copying to be started back up once that's complete.

share|improve this answer
Just the answer I was looking for, thanks again Shane! – Jake A Sep 5 '12 at 16:23
Hey Shane, sorry, another question. To begin the re-seed, do I need to delete the DB files and transaction logs, leaving the folders empty? Also, any suggestions or references on how to proceed with the re-seeding process? – Jake A Sep 5 '12 at 16:55
Nope, it should take care of the deletions for you. Should be able to just click the "update storage group copy" thing in the sidebar when you have the storage group selected in the management console. – Shane Madden Sep 5 '12 at 17:48
Since we are re-seeding, I would like to take the opportunity to increase the disk size where the DB's are located. Would it be possible to setup the new empty partition that is larger, and just start fresh? Or will I need to clone/copy the data over to the new disk/partition before re-seeding? – Jake A Sep 5 '12 at 18:13
@yum_tacos4u You might need to create some of the directory structure, but a new clean partition should work just fine. – Shane Madden Sep 5 '12 at 18:59

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.