Topic Last Modified: 2009-03-12

This topic describes a problem in which you cannot reseed the log files to a Passive Node in a cluster continuous replication (CCR) environment in Microsoft Exchange Server 2007. When you run the Update-StorageGroupCopy cmdlet, you receive the following error message:

Summary: 2 item(s). 1 succeeded, 1 failed.

Elapsed time: 00:00:00

Suspend <GUID or Name of the storage group>

Completed

Exchange Management Shell command completed:

suspend-StorageGroupCopy -Identity <GUID or Name of the storage group>' -SuspendComment 'Administrator initiated Update-StorageGroupCopy'

Elapsed Time: 00:00:00

Update <GUID or Name of the storage group>

Failed

Error:

This task can only be performed locally on the source or target computer.

Exchange Management Shell command attempted:

update-StorageGroupCopy -Identity '<GUID or Name of the storage group>' -DeleteExistingFiles

Elapsed Time: 00:00:00

When you view the debug logging reports, you see the following message:

update-StorageGroupCopy -Identity <GUID or Name of the storage group> -DeleteExistingFiles -Verbose -Debug

VERBOSE: Update-StorageGroupCopy : Beginning processing.

VERBOSE: Update-StorageGroupCopy : Searching objects "<GUID or Name of the storage group>" of type"StorageGroup" under the root "$null".

VERBOSE: Update-StorageGroupCopy : Previous operation run on domain controller'<Computer Name>'.

VERBOSE: Update-StorageGroupCopy : Processing object "<GUID or Name of the storage group>".

Confirm

This task can only be performed locally on the source or target computer.

[Y] Yes [A] Yes to All [H] Halt Command [S] Suspend [?] Help

(default is "Y"):

Update-StorageGroupCopy : This task can only be performed locally on the source or target computer.

At line:1 char:24

+ update-StorageGroupCopy <<<< -Identity '<GUID or Name of the storage group>' -DeleteExistingFiles -Verbose -Debug

VERBOSE: Update-StorageGroupCopy : Ending processing.

This problem occurs because the passive node is not in the Preferred Owner list on the Cluster Group. To resolve this problem, follow the procedure that is documented in the topic How to Configure Clustered Mailbox Server Ownership in a CCR Environment.