Exchange Server Forums

Standby Continuous Replication failback problem

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> High Availability >> Standby Continuous Replication failback problem

Page: [1]

Message

<< Older Topic Newer Topic >>

Standby Continuous Replication failback problem - 29.May2008 7:23:19 PM

acwsmith

Posts: 2
Joined: 29.May2008
Status: offline

Hi,

I am in the process of completing an Exchange 2007 high availability solution for a customer. I am very close to completing this but have an issue that I'm hoping someone here can help with. Perhaps some of my notes will help others too.

I have two Windows 2003 r2 64 bit servers running exchange 2007, I have successfully configured SCR and can failover to the backup server pretty quickly despite having a 64gb mailbox store.

First of all I enabled the replication of the database on server 1 to server 2
I then suspended this replication and seeded the database instance on server 2. To complete this I resumed the replication.

This bit went pretty smoothly and I could see the log files populating on the standby machine.

I have managed to bring the backup store online using the recover-storagegroupcopy option and have mounted the store after correcting the database shutdown state using eseutil /r e00 /a

Now for failing back to the original server, this is where I have hit problems.

First of all I kept getting the following error: -
Enable-StorageGroupCopy : The Windows Cluster service encountered an error during function IsNodeClustered.

After comparing the servers it turned out the remote registry service was disabled on the source server, this was preventing me enabling the storagegroupcopy.

Now that I had that bit sussed I suspended the replication and tried to seed the database back to the source server, this is were I have hit a problem that I can't fix, I now receive the following error when trying to run the update: -

Update-StorageGroupCopy must be run on the passive node

I am running this on the passive node so I can't firgure out why I receive this error.

I have also tried creating a brand new storage group on server 2 and trying to replicate this to server 1, I can enable the replication and the status shows as healthy but I can't seed it.

Has anyone got any ideas on why the passive node is convinced it's the source for every database?

Thanks in advance for your help, it really is much appreciated.

Alastair

Post #: 1

Featured Links*

RE: Standby Continuous Replication failback problem - 13.Jun.2008 7:17:11 AM

acwsmith

Posts: 2
Joined: 29.May2008
Status: offline

As a quick follow up I have resolved this by uninstalling and reinstalling the 'Mailbox' role. I didn't want to do this but it was relatively painless once I moved the public folder replicas off this server.

Relocating the public folders requires patience whilst they replicate or balls of steel if using adsiedit (only use if you're in a hurry and 200% confident!).

I am now progressing with the automated failover script, will post this when completed too

(in reply to acwsmith)

Post #: 2