Share via


Cannot Enable Storage Group Copy from a Different Domain

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Applies to: Exchange Server 2007 SP1

This topic provides information about how to troubleshoot the Enable-StorageGroupCopy command in a Microsoft Exchange Server 2007 Service Pack 1 standby continuous replication (SCR) environment.

This issue occurs if you run the Enable-StorageGroupCopy cmdlet from a computer that is in a different domain than the domain of the computer on which you are enabling the storage group copy. For example, if you have a mailbox server named Mailbox01 and a standby server named Standby01 in the "corp" domain and you run the command Enable-StorageGroupCopy -Identity Mailbox01\SG1 -StandbyMachine Standby01 from a computer in the "mfg" domain, you will receive the following error:

Unable to find the source node for storage group 'SG1' using remote procedure calls (RPCs).

Enable-StorageGroupCopy succeeds in enabling the copy. However, the command also tries to find the log files for the storage group to determine if it should suspend replication. The command does not use the fully qualified domain name (FQDN) of the source computer, and because the source is in a different domain, it cannot find the location of the log files and therefore returns the error.

Resolution

You do not need to perform any steps to resolve this error. The storage group copy has been enabled. To verify that SCR has been enabled, run the following command:

Get-StorageGroupCopyStatus -Identity Mailbox01\SG1 -StandbyMachine Standby01

Active Directory will replicate the information about the enabled copy to the domain where the source and target computers reside. The replication service will recognize the new configuration. If the first log file is available on the source, replication to the target will begin. If the first log file is not available on the source, the copy must be seeded first. Typically, Enable-StorageGroupCopy will initiate the seeding. However, in this scenario, Enable-StorageGroupCopy cannot determine if the first log file is available. It will not initiate the seeding. If the first log file is not available on the source, you must manually seed the storage group copy. For detailed steps to seed a storage group copy, see How to Seed a Standby Continuous Replication Target.

For More Information

For more information about enabling a storage group copy in an SCR environment, see Managing Standby Continuous Replication.