No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor BCManager 6.5.0 eReplication User Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
What Can I Do When "Operation failed" Is Displayed During the Execution of Exchange or SQL Server Protected Groups

What Can I Do When "Operation failed" Is Displayed During the Execution of Exchange or SQL Server Protected Groups

Symptom

During the Exchange or Oracle protected group execution, the Freeze or Application Unfreezing step fails to be performed with a message indicating Operation failed displayed.

Possible Causes

  • Possible cause 1: The database is offline. (for SQL Server)
  • Possible cause 2: Databases that store volumes in Dismounted state exist. As a result, VSS fails in backup preparation. (for Exchange)
  • Possible cause 3: The database does not exist.
  • Possible cause 4: A serious error occurs, preventing the VSS execution. (for SQL Server)
  • Possible cause 5: The VSS service on the host where the database is installed is disabled.
  • Possible cause 6: The disk where the database resides is offline. The VSS traverses all the metadata of Writer, that is, the VSS traverses all online databases. If the disk of a database goes offline but the database remains online, the VSS cannot read data from the disk of the database. Then protected group execution fails.

Procedure

  1. Possible cause 1: The database is offline (for SQL Server). To resolve this problem, complete the following steps:
    1. Log in to the host on which the database is installed.
    2. Check whether the SQL Server database is in Offline state.

      • If the database is in Offline state, select and right-click the database. Choose Tasks > Bring Online from the shortcut menu to set the database online.

        Operation steps may vary with database versions. The following uses SQL Server 2012 as an example.

      • If the database is in Online state, see 4.

    3. Re-execute the protected group.
  2. Possible cause 2: Databases that store volumes in Dismounted state exist, VSS fails in backup preparation. (for Exchange) To resolve this problem, complete the following steps:

    If either the mailbox database or any mailbox database on the LUNs owning this mailbox database in the protected group of Exchange 2013 is in Dismounted state, the protected group fails to be executed. Establishing multiple mailbox databases on a LUN at the production center is not recommended.

    1. Log in to the host on which the database is installed.
    2. Clear databases in Dismounted state.
    3. Select and right-click a mailbox database in Dismounted state, and choose Mount Database from the short-cut menu to re-mount the mailbox database.

      The following procedure Exchange 2010 as an example. For databases of other versions, refer to the following procedure based on actual requirements.

    4. Re-execute the protected group.
  3. Possible cause 3: The database does not exist.

    Contact Huawei technical support.

  4. Possible cause 4: Possible cause 4: A serious error occurs, preventing the VSS execution. (for SQL Server) To resolve this problem, complete the following steps:
    1. Run the vssadmin list writers command to check the status and errors of SqlServerWriter.
    2. If the Non-retryable error occurs, locate root causes by checking the eReplication Agent log files and Windows logs.
    3. Restart the Windows service of SQL Server VSS Writer.
    4. Run the vssadmin list writers command to check the status and errors of SqlServerWriter. The environment is recovered successfully if the command output is as follows:

    5. Re-execute the protected group.
  5. Possible cause 5: The VSS service on the host where the database is installed is disabled. To resolve this problem, complete the following steps:

    The following operation uses Windows Server 2008 as an example.

    1. Log in to the host on which the database is installed.
    2. Open the service manager.
    3. In the navigation tree, choose Configuration > Services.
    4. In the area on the left, find the Volume Shadow Copy service, and check whether its startup type is Manual or Automatic. If the type is Disabled, change it to Manual or Automatic.

    5. Re-execute the protected group.
  6. Possible cause 6: The disk where the database resides is offline.
    1. Log in to the host on which the database is installed.
    2. Open the service manager.
    3. In the navigation tree, choose Storage > Disk Management.
    4. In the area on the right, select and right-click the disk in Offline state, and choose Online from the short-cut menu.

      NOTE:
      If changing the disk status to Online fails, check whether the network between the application host and storage device is normal.

    5. Re-execute the protected group.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 14256

Downloads: 70

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next