Parameters

To see the complete status of a CCR or LCR copy by using the Exchange Management Shell, run the Get-StorageGroupCopyStatus cmdlet. Depending upon the options that you provide, the cmdlet either returns information about a specific copy on a specific server or all copies on a server.

The basic cmdlet syntax is shown in the following example code:

	Copy Code
Get-StorageGroupCopyStatus

When you use the basic syntax, the following sample output is provided:

The cmdlet with a formatted list option is shown in the following example:

	Copy Code
Get-StorageGroupCopyStatus |fl

When you use the formatted list option, the complete copy status with all the fields is provided:

• Identity: MBXNODE01\StorageGroup1
  
  
• StorageGroupName: StorageGroup1
  
  
• SummaryCopyStatus: Healthy
  
  
• Failed: False
  
  
• FailedMessage:
  
  
• Seeding: False
  
  
• Suspend: False
  
  
• SuspendComment:
  
  
• CopyQueueLength: 0
  
  
• ReplayQueueLength: 0
  
  
• LatestAvailableLogTime: 6/14/2006 4:42:01 PM
  
  
• LastCopyNotificationedLogTime: 6/14/2006 4:42:01 PM
  
  
• LastCopiedLogTime: 6/14/2006 4:42:01 PM
  
  
• LastInspectedLogTime: 6/14/2006 4:42:01 PM
  
  
• LastReplayedLogTime: 6/14/2006 4:42:01 PM
  
  
• LastLogGenerated: 4
  
  
• LastLogCopyNotified: 4
  
  
• LastLogCopied: 4
  
  
• LastLogInspected: 4
  
  
• LastLogReplayed: 4
  
  
• LatestFullBackupTime:
  
  
• LatestIncrementalBackupTime:
  
  
• SnapshotBackup:
  
  
• IsValid: True
  
  
• ObjectState: Unchanged
  
  

The following table provides the type and describes the fields in the output.

You can make a quick assessment of the health of a copy by looking at the results in the SummaryCopyStatus, Failed, CopyQueueLength, and ReplayQueueLength, and LastInspectedLogTime fields. These fields show whether the copy is functioning properly and whether the copy is relatively current in both copying and applying logs. If the LastInspectedLogTime is not current, that can indicate that the replication service is stopped or that there is a low rate of traffic on the storage group. If the copy is ever in an unhealthy state, the reason should be determined and corrected. If the copy queue length value is more than 3, the reason should be determined and corrected. If the replay queue length value is more than 20, the reason should be determined and corrected.

To use the Get-StorageGroupCopyStatus cmdlet, the account you use must be delegated the following:

• Exchange Server Administrator role and local Administrators group for the target server
  
  

For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.

There are some rare scenarios where the replication status can be misleading. Following is a list of those scenarios:

• A storage group that is not active (that is, not changing) can report as healthy when it might not be healthy. This situation could occur because the unhealthy condition could not be detected until a log is replayed.
  
  
• During replication initialization, the replication status is being re-evaluated and may not be accurate. When the initialization completes, the status is updated.
  
  
• The value of the LastLogGenerated field can be wrong when a database is dismounted. However, all logs with end user content are replicated if the storage group copy is replicating.
  
  
• When there are one or more missing logs in the middle of a log stream, the passive copy continues to try to recover. In doing so, the replication status switches between failed and healthy states. The replay and copy queues will continue to grow.
  
  
• Under some very rare conditions, a log can be successfully verified but it can still fail to replay. In this situation, the system will alternate between failed and healthy states as it attempts to recover. The replay and copy queues will continue grow.
  
  

The first code example is of the Get-StorageGroupCopyStatus command when the storage group name is not ambiguous.

The second code example describes how to get the copy status SG1 on server MBX.

The third code example describes how to get status on all storage groups for the server MBX.

The fourth code example produces copy information for all copies for the local server. On a passive node, it returns information for all copies of the associated active storage group copy.

	Copy Code
Get-StorageGroupCopyStatus -Identity Storage_Group_1 Get-StorageGroupCopyStatus -Identity:MBX\SG1 Get-StorageGroupCopyStatus -Server:MBX Get-StorageGroupCopyStatus