locked
problems with SCR on exchange 2007 sp3 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I currently have SCR setup between two servers, they are both windows 2003 x64 sp2, exchange 2007 sp1 (source), sp3 (target) seems to work fine.

    I built a new server, windows 2008 R2 server with exchange 2007 sp3. I migrated all the mailboxes off the first server onto this one, but for some reason i am unable to setup SCR replication.

    I broke the first SCR replication between the original source and target in case there was an issue. I also upgraded the target to exchange 2007 sp3 in case version was an issue, but still to no avail. i googled and checked around but was not able to find the solution. i know for sure i am typing the command in correctly as I have set this up before and I have also resumed the original SCR, unforunately no data is being replicated. I am not sure if this is an issue with windows 2008 R2 and exchange 2007 or if there is some under lying issue with my AD.

    [PS] C:\Windows\system32>enable-StorageGroupCopy -Identity serverA\sg1 -Standby
    Machine serverb
    Enable-StorageGroupCopy : The Windows Cluster service encountered an error duri
    ng function IsNodeClustered.
    At line:1 char:24
    + enable-StorageGroupCopy <<<<  -Identity servera\sg1 -StandbyMachine serverb
        + CategoryInfo          : InvalidOperation: (serverA\SG1:ADObjectId) [Ena
       ble-StorageGroupCopy], ExClusTransientException
        + FullyQualifiedErrorId : B53648E6,Microsoft.Exchange.Management.SystemCon
       figurationTasks.EnableStorageGroupCopy

    my schema is 47 if that matters.

    source box is windows 2008 R2 with exchange 2007 sp3

    target box is windows 2003 x64 / sp2 with exchange 2007 SP3

    any advice would be greatly appreciated before i open a call into microsoft.

    Tuesday, August 3, 2010 10:04 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I think you will need to have the target the same OS as the source to get it working correctly. I'm sure MS will suggest that. Give that a try and let me know.
    • Proposed as answer by jader3rd Wednesday, August 4, 2010 12:11 AM
    • Marked as answer by e wong Wednesday, August 4, 2010 4:41 PM
    Wednesday, August 4, 2010 12:03 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I think you will need to have the target the same OS as the source to get it working correctly. I'm sure MS will suggest that. Give that a try and let me know.
    • Proposed as answer by jader3rd Wednesday, August 4, 2010 12:11 AM
    • Marked as answer by e wong Wednesday, August 4, 2010 4:41 PM
    Wednesday, August 4, 2010 12:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    that seemed to be the problem. source and target must have the same OS as well. at least i am progressing forward now.

    initially i didnt have a spare machine and i did not have VM available so i wanted to avoid installing a new server. since the target was at a remote location, i did not have console access to reinstall the OS, i was able to setup VM on another machine and get it working.

    thanks for your help.

    Wednesday, August 4, 2010 4:42 PM