Storage groups set up and mounted on node of CCR cluster but not replicating
HiIn the progress of setting up a new CCR cluster for Exchange 2007. So far on node01, the cluster resources are all up, the storage groups are all created and the mailbox stores are mounted. These are not being replicated to the second node, should this be the case?I don't want to try failing the cluster resource over without checking in case it corrupts or something.So basically, I'm asking why aren't the storage groups and mailbox stores copying from one node to the other? Microsoft Exchange Replication Service is running. The drive is not shared out on the second (destination) node, if this helps diagnosis.I was assuming the process would be automatic once the stores had been created. EMC reports stores as 'healthy and mounted'.Any suggestions/advice?Thanks
July 3rd, 2009 12:34pm

Does it mean that all the database files didnt copy to the passive node? Please check if theres any related event in the application log on the nodes Please verify the functionality of CCR, analyze the output Run <Get-ClusteredMailboxServerStatus Identity CMSName | Fl> Run <Get-StorageGroupCopyStatus | Fl> on both nodes
Free Windows Admin Tool Kit Click here and download it now
July 3rd, 2009 1:10pm

Hi, thanks for your time. I'll answer your questions best I can:1. We move the cluster to the passive node to test resilience, then created mailboxes and storagegroupson this node. I was hoping when we failed it back, it would create all the mounts and then start replicating. As they don't exist on the active node it obviously fails rbinging up the resource; is this the problem? I need to create them on the active node only?2. On the active node I get this event:Event Type:ErrorEvent Source:MSExchangeFBPublishEvent Category:Devices Event ID:8213Date:03/07/2009Time:11:05:48User:N/AComputer:X64EXCHND02Description:The description for Event ID ( 8213 ) in Source ( MSExchangeFBPublish ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: x64exchvs01, 0x8004010f.and on the passive node I get:Event Type:ErrorEvent Source:MSExchangeFBPublishEvent Category:General Event ID:8213Date:03/07/2009Time:11:05:48User:N/AComputer:X64EXCHND02Description:The Microsoft Exchange System Attendant service failed to create session for virtual machine x64exchvs01. The error number is 0x8004010f. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.3.[PS] H:\>Get-ClusteredMailboxServerStatus -Identity x64exchvs01 | Fl Identity : x64exchvs01ClusteredMailboxServerName : X64EXCHVS01.xxxxx.comState : OnlineOperationalMachines : {X64EXCHND01 <Quorum Owner>, X64EXCHND02 <Active>}FailedResources : {}IsValid : TrueObjectState : Unchanged[PS] C:\Documents and Settings\bigbrother>Get-StorageGroupCopyStatus | Fl Identity : x64exchvs01\SurnamesAIStorageGroupName : SurnamesAISummaryCopyStatus : ServiceDownNotSupported : FalseNotConfigured : FalseDisabled : FalseServiceDown : TrueFailed : FalseInitializing : FalseResynchronizing : FalseSeeding : FalseSuspend : FalseCCRTargetNode :FailedMessage : Microsoft Exchange Replication service RPC f ailed : The Microsoft Exchange Replication s ervice may not be running on server x64exchn d01. RPC exception: Error 6d9 from cli_GetCo pyStatusExSuspendComment :CopyQueueLength : 0ReplayQueueLength : 0LatestAvailableLogTime :LastCopyNotificationedLogTime :LastCopiedLogTime :LastInspectedLogTime :LastReplayedLogTime :LastLogGenerated : 0LastLogCopyNotified : 0LastLogCopied : 0LastLogInspected : 0LastLogReplayed : 0LatestFullBackupTime :LatestIncrementalBackupTime :LatestDifferentialBackupTime :LatestCopyBackupTime :SnapshotBackup :SnapshotLatestFullBackup :SnapshotLatestIncrementalBackup :SnapshotLatestDifferentialBackup :SnapshotLatestCopyBackup :OutstandingDumpsterRequests :DumpsterServersNotAvailable :DumpsterStatistics :IsValid : TrueObjectState : Unchanged Identity : x64exchvs01\SurnamesJRStorageGroupName : SurnamesJRSummaryCopyStatus : ServiceDownNotSupported : FalseNotConfigured : FalseDisabled : FalseServiceDown : TrueFailed : FalseInitializing : FalseResynchronizing : FalseSeeding : FalseSuspend : FalseCCRTargetNode :FailedMessage : Microsoft Exchange Replication service RPC f ailed : The Microsoft Exchange Replication s ervice may not be running on server x64exchn d01. RPC exception: Error 6d9 from cli_GetCo pyStatusExSuspendComment :CopyQueueLength : 0ReplayQueueLength : 0LatestAvailableLogTime :LastCopyNotificationedLogTime :LastCopiedLogTime :LastInspectedLogTime :LastReplayedLogTime :LastLogGenerated : 0LastLogCopyNotified : 0LastLogCopied : 0LastLogInspected : 0LastLogReplayed : 0LatestFullBackupTime :LatestIncrementalBackupTime :LatestDifferentialBackupTime :LatestCopyBackupTime :SnapshotBackup :SnapshotLatestFullBackup :SnapshotLatestIncrementalBackup :SnapshotLatestDifferentialBackup :SnapshotLatestCopyBackup :OutstandingDumpsterRequests :DumpsterServersNotAvailable :DumpsterStatistics :IsValid : TrueObjectState : Unchanged Identity : x64exchvs01\SurnamesSZStorageGroupName : SurnamesSZSummaryCopyStatus : ServiceDownNotSupported : FalseNotConfigured : FalseDisabled : FalseServiceDown : TrueFailed : FalseInitializing : FalseResynchronizing : FalseSeeding : FalseSuspend : FalseCCRTargetNode :FailedMessage : Microsoft Exchange Replication service RPC f ailed : The Microsoft Exchange Replication s ervice may not be running on server x64exchn d01. RPC exception: Error 6d9 from cli_GetCo pyStatusExSuspendComment :CopyQueueLength : 0ReplayQueueLength : 0LatestAvailableLogTime :LastCopyNotificationedLogTime :LastCopiedLogTime :LastInspectedLogTime :LastReplayedLogTime :LastLogGenerated : 0LastLogCopyNotified : 0LastLogCopied : 0LastLogInspected : 0LastLogReplayed : 0LatestFullBackupTime :LatestIncrementalBackupTime :LatestDifferentialBackupTime :LatestCopyBackupTime :SnapshotBackup :SnapshotLatestFullBackup :SnapshotLatestIncrementalBackup :SnapshotLatestDifferentialBackup :SnapshotLatestCopyBackup :OutstandingDumpsterRequests :DumpsterServersNotAvailable :DumpsterStatistics :IsValid : TrueObjectState : Unchanged Identity : x64exchvs01\VIPandBlackberryStorageGroupName : VIPandBlackberrySummaryCopyStatus : ServiceDownNotSupported : FalseNotConfigured : FalseDisabled : FalseServiceDown : TrueFailed : FalseInitializing : FalseResynchronizing : FalseSeeding : FalseSuspend : FalseCCRTargetNode :FailedMessage : Microsoft Exchange Replication service RPC f ailed : The Microsoft Exchange Replication s ervice may not be running on server x64exchn d01. RPC exception: Error 6d9 from cli_GetCo pyStatusExSuspendComment :CopyQueueLength : 0ReplayQueueLength : 0LatestAvailableLogTime :LastCopyNotificationedLogTime :LastCopiedLogTime :LastInspectedLogTime :LastReplayedLogTime :LastLogGenerated : 0LastLogCopyNotified : 0LastLogCopied : 0LastLogInspected : 0LastLogReplayed : 0LatestFullBackupTime :LatestIncrementalBackupTime :LatestDifferentialBackupTime :LatestCopyBackupTime :SnapshotBackup :SnapshotLatestFullBackup :SnapshotLatestIncrementalBackup :SnapshotLatestDifferentialBackup :SnapshotLatestCopyBackup :OutstandingDumpsterRequests :DumpsterServersNotAvailable :DumpsterStatistics :IsValid : TrueObjectState : UnchangedThese commands were run from the second node, where the mailboxes were created.To clairfy the topologyx64exchnd01 - x64exchnd02active ---------------- passiveWe failed over to the passive node, then created our storage groups and mounts. I was going to wait for them to replicate and then failback. However they are not replicating.Thanks
July 3rd, 2009 1:21pm

For replication to kick in there must be some activity in the transaction logs and databases. iIn my lab I dismount and mount the database and replication starts kicking. if that is not possible;logon to a mailbox in the database and send a mail.lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
July 3rd, 2009 5:43pm

Microsoft Exchange Replication service RPC failed : The Microsoft Exchange Replication service may not be running on server x64exchnd01. RPC exception: Error 6d9 from cli_GetCopyStatusEx Please try to method below: Reseeded the passive node databases after suspending the storage group copy and deleting the corrupted database files and logs, then resumed the storage group copy How to Seed a Cluster Continuous Replication Copy
July 6th, 2009 5:50am

Thanks, this was the correct answer. I actually found it before I came back here, and was in the middle of doing it. Basically I had to delete the contents of the logs folder on the passive node, and the mail stores. Then suspend the storage groups and do an -updatestoragegroup reseeding it. It all went well.
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2009 12:54pm

Glad it worked for you J
July 6th, 2009 1:02pm

Was the root cause ever identified ?I'm having this same issue. However, I have30+ storage groups with about 1.5TB total size of mailbox databasestoreseed.That will take forever.I'd like to ensure this issue doesn't return or that we don't have another underlying problem before reseeding unnecessarily.Thanks!
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2009 10:45pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics