• Article

An error occurred when the Restore-StorageGroupCopy cmdlet failed to copy all logs

 

Topic Last Modified: 2007-11-16

The Microsoft Exchange Server 2007 Management Pack for Operations Manager monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.

To learn more about this alert, if you are using Microsoft Operations Manager 2005, do one or more of the following:

  • From the Operator Console, select this alert, and then click the Properties tab. Review the description of the alert that includes the variables specific to your environment.

  • From the Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description. Review the events that have been logged that meet the criteria of this Operations Manager alert.

To learn more about this alert, if you are using System Center Operations Manager 2007, do one or more of the following:

  • From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.

  • From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the events that have been logged that meet the criteria of this Operations Manager alert.

Details

Product Name

Exchange

Product Version

8.0 (Exchange Server 2007)

Event ID

2087;2088

Event Source

MSExchangeRepl

Alert Type

Warning

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Mailbox/Cluster

MOM Rule Name

An error occurred when the Restore-StorageGroupCopy cmdlet failed to copy all logs.

Explanation

This alert indicates that the the Restore-StorageGroupCopy cmdlet failed to copy all logs.

  • Information 2087 indicates that the Restore-StorageGroupCopy task was successful in mounting the copy of the database but the Microsoft Exchange Replication Service was unable to copy all the logs from the previously active node in the process.

    The event indicates that the current active node has had a lossy database mount where one or more log files from the failed active node could not be copied and replayed.

    Note   In certain circumstances, overriding the loss restrictions of mounting the storage group on the newly active node may require reseeding the previously active node storage group. Reseeding would be required if one or more of the logs in the loss region had been written to the database.

    The Restore-StorageGroupCopy cmdlet in the Microsoft Exchange Server 2007 cluster continuous replication (CCR) environment copies over the log files from the failed node and activates the database on the current active node.

    In a local continuous replication (LCR) solution, the Restore-StorageGroupCopy cmdlet is used to disable LCR and make the passive copy viable for Mount-Database. In a CCR configuration, Restore-StorageGroupCopy is used when the automatic mount support does not mount the database and the administrator must explicitly intervene to mount the database. In this scenario, the administrator uses Restore-StorageGroupCopy before performing the Mount-Database operation.

  • Information event 2088 indicates that the Microsoft Exchange Replication Service did not copy all the logs from the previously active node to the current active node during a Restore-StorageGroupCopy operation.

    This event is generated only in a local continuous replication (LCR) environment. In LCR, the administrator has the option of activating the copy either by moving the files to the location of the previously active database or by changing the paths of the previously active database to the newly activated copy. To do this, the administrator can use the ReplaceLocations switch in the Restore-StorageGroupCopy task. This event relates to the latter option where the LCR copy paths are pointing to the copy and not all log files are available in the copy.

    The event indicates that the current active node has had a lossy database mount where one or more log files from the last mounted node could not be copied.

    Note   In certain circumstances, overriding the loss restrictions of mounting the storage group on the newly active node may require reseeding the previously active node storage group. Reseeding would be required if one or more of the logs in the loss region had been written to the database.

    The Restore-StorageGroupCopy task in an LCR solution is used to disable LCR and make the passive copy viable for Mount-Database. The Mount-Database command is the task to activate a passive storage group copy.

For more information about Restore-StorageGroupCopy, see Restore-StorageGroupCopy.

User Action

No user action is required. This alert provides information about data loss resulting from mounting the database in the current active node. The Restore-StorageGroupCopy operation will check if all logs created on the source server for the storage group are present in the copy, and if not, will try to copy them again.

For More Information

To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.

To review Exchange Server 2007 event message articles that may not be represented by Exchange 2007 alerts, see the Events and Errors Message Center.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.