Troubleshooting - Exchange Database Agent

The following section provides information on some of the troubleshooting scenarios related to backup:

EXDB0002: Error Code: 82:128

Symptom

For Exchange 2010, database backup fails with following network received failure message:

Error Code: 82:128

Errors similar to the following will be seen on the Exchange server in extidbbackup.log. This log file is located under

C:\Program Files\Company Name\SnapProtect\Log Files

1234 1d58 10/22 10:01:00 1234 ** CVSession::receiveMessageInt(...): - RemoteHost=mediaagent.com. - RemoteProcess=cvd.exe. - checkDataWaiting () failed. Error=9000022. Error code 9000022 translates to: [...]:Remote machine [...]. The socket connection was lost unexpectedly. MyIoctl returned 0 bytes waiting. Check Network Connectivity.

The following error may also be seen in the extimbstartbackup.log on the CommServe specifically for DAG backups.

1234 1d58 10/22 11:01:00 1234 ** CVSession::receiveMessageInt(...): - RemoteHost=exchangeserver.com. - RemoteProcess=extidbbackup.exe. - checkDataWaiting () failed. Error=9000022.

Possible Cause

This error may occur because there is an idle connection during the backup job. There are two scenarios that might trigger the issue:

  1. Exchange backup during an integrity check between the MediaAgent and Exchange Server
  2. Exchange DAG backups between the Exchange Server and the CommServe

The Exchange database backup will first open a pipeline between the MediaAgent and Exchange Server.

  • During the time of an integrity check of the data, there will be no traffic over this connection.
  • At all times during a DAG configured Exchange database backup, a monitoring thread on the CommServe is connected to the Exchange backup process.
  • During the backup operation no data will be flowing through this pipeline.

Many environments have network settings in place that will disconnect a connection if it is idle for more than a certain period of time. If the connection goes down the job will go pending with the above mentioned error.

Resolution

We recommend setting up a one-way firewall between the servers that are losing their connection. For details on configuring the firewall, refer to Firewall - Direct Connections.

With this configuration in place, a persistent pipeline is configured that sends keep-alive messages at regular intervals.

The example below uses MediaAgent and Exchange Servers, but substitute the CommServe for the MediaAgent if the disconnect is occurring between CommServe and Exchange Servers.

Configure CommServe and MediaAgent Firewall Settings:

  1. Configure the CommServe using these steps:
    1. Right-click the CommServe_name in the CommCell Browser, then click Properties.
    2. Click the Firewall Configuration tab, then the Incoming Connections tab.
    3. Click Add. The Connection to dialog box opens.
    4. In the From list, select the name of the client you just installed.
    5. Select the State of the connection from the client. In the case you are configuring, the client initiates the connection to the CommServe. If the firewall restricts incoming connections to only specific ports, select RESTRICTED. Configuring Third-Party Connections using the Firewall Configuration File describes port restriction.
    6. Click OK, then click OK again to close the CommCell Properties dialog box.
    7. From the CommCell Browser, right-click the CommServe computer and click All Tasks > Push Firewall Configuration.
    8. Read the warning, then click Continue.
    9. Click OK.

    You have now configured the CommServe system to receive communication from the client. You can verify that your firewall configuration was pushed successfully by checking the Event Viewer window.

  2. Configure the MediaAgent using these steps:
    1. Right-click the MediaAgent_name from the CommCell Browser and click Properties.
    2. Click Advanced.
    3. Click the Firewall Configuration tab, then select Configure Firewall Settings and click Add.
    4. In the From list, select the name of the client you just installed.
    5. Select the State of the connection from the client. In the case you are configuring, the client initiates the connection to the MediaAgent. If the firewall restricts connections to only specific ports, select RESTRICTED.
    6.   Configuring Third-Party Connections using the Firewall Configuration File describes port restriction. Click OK.
    7. Click the Incoming Ports tab, then set the port number on which the incoming tunnel connection is received in the Listen for tunnel connections on port box.

      Additional Open Ports: You can speed up data transfer for components that handle it (such as MediaAgent or File System iDataAgent), by opening additional ports on the firewall, and configuring them as open in this dialog. Specify the range of ports in the Additional open ports area, in the From and To fields. Click Add to add the ports. To remove a port from the listing, select the port and click Delete. The ports must be within the range of 1024 - 65000. Ensure that the ports specified here are not used by other applications.

      For more information on additional open ports, see Optimizing Backup and Restore using Additional Ports.

      Click OK.

    8. From the CommCell Browser, right-click the MediaAgent computer and click All Tasks > Push Firewall Configuration.
    9. Read the warning, then click Continue.
    10. Click OK.

    You have now configured the MediaAgent to receive communication from the client. You can verify that your firewall configuration was pushed successfully by checking the Event Viewer window.

Configure Client Firewall Settings

  1. Right-click the client from the CommCell Browser and then click Properties.
  2. In the Client Computer Properties dialog box, click Advanced.
  3. On the Firewall Configuration tab, select Configure Firewall Settings, then the Advanced option. Read the warning, then click OK to acknowledge it and continue.
  4. Click Add.
  5. From the From list, select the name of the CommServe computer.

    From the State list, select BLOCKED since the CommServe computer cannot open connections to the Client.

    Click OK.

  6. Click Add to specify the MediaAgent connection details.

    From the From list, select the name of the MediaAgent computer.

    From the State list, select BLOCKED since the MediaAgent cannot open connections to the Client.

    Click OK.

  7. On the Outgoing Routes tab, click Add. The Route Settings dialog box appears.

    Select the CommServe name from the Remote Group/Client list.

    Under the Tunnel Connection Protocol area, select Encrypted to enable authentication and encryption for tunnel connections.

    Note: You do not need to select the Force all data (along with control) traffic into the tunnel check box because this route is not towards the MediaAgent.

    Click OK.

  8. From the CommCell Browser, right-click the client and click All Tasks > Push Firewall Configuration.
  9. Click Continue.
  10. Click OK. The client is configured to communicate with the CommServe and MediaAgent.
  11. In the CommCell Console, right-click the client computer name, then click All Tasks > Check Readiness. Confirm the results shown in the Client Connectivity dialog box.

    If the client computer is not ready, verify your settings against the above recommendations and revise them as required.

Additional Settings

If you need to set up outgoing routes from any host computer, please see Configuring Outgoing Tunnel Connections.

Completed with one or more errors

Backup jobs from Exchange Database iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:

  1. For Exchange Legacy:
    • If at least one database is found to be un-mounted and the remaining databases are backed up successfully.
    • If one database is failed to backup due to exchange streaming API failure or network failure and we cannot recover from those errors for the legacy backup.
  2.  For VSS backup:
    • Some databases mounted, some un-mounted within one SG will not cause any failure
    • 'un-mounted' error may cause job failure if all databases within one SG are un-mounted.
    • Other database failures due to exchange, includes Exchange information store server down, Exchange VSS writer not  in stable state etc.
  3.  For Exchange 2010:
    • Backup from one node that is failing and the other succeeding will cause Completed w/ one or more Errors.
    • Any un-mounted database (involved in a backup) will cause a job failure.
    • Other database failures due to exchange, includes Exchange information store server down, Exchange VSS writer not  in stable state etc.

Backups failing with "No more allocated streams are available" error message

Backups might fail with this error message if an incremental storage policy is being used. Remove the incremental storage policy and assign a standard storage policy before you run the backups.