When trying to expand and browse an Exchange 2010 Database Availability Group (DAG) in a backup selection list an error is encountered: 'The media server could not connect to the Exchange 2010 DAG virtual node. The backup Exec remote agent must be installed and running on all nodes in the DAG.'

Article:TECH142542  |  Created: 2010-10-23  |  Updated: 2013-10-21  |  Article URL http://www.symantec.com/docs/TECH142542
Article Type
Technical Solution


Issue



When trying to expand and browse an Exchange 2010 Database Availability Group (DAG) in a backup selection list an error is encountered: 'The media server could not connect to the Exchange 2010 DAG virtual node. The backup Exec remote agent must be installed and running on all nodes in the DAG.'
 


Error



An error was encountered while attempting to browse the contents of NAME-DAG.  
The media server could not connect to the Exchange 2010 DAG virtual node. 
The backup Exec remote agent must be installed and running on all nodes in the DAG.
Right-click the Exchange 2010 DAG virtual node, and then click Properties. Ensure that the correct version of a remote agent is installed and running on the virtual node. 


Environment



Microsoft Exchange 2010


Cause



In Backup Exec 2010 under certain conditions, the Information Store (IS) selections may not be visible in the backup selections for an Exchange 2010 server.


These issues may occur if the Backup Exec Logon Account being used to access the Exchange server does not have the required permissions assigned to it

- OR -

If the remote agent is not installed or is not up to date.

- OR -

The above problem might occur as a result of Windows 2008 using Internet Protocol version 6 (IPv6) as a preferred protocol over Internet Protocol version4 (IPv4) and If the Exchange nodes are Windows 2008 Server.


Solution



Check for the following solutions and retry the backup job.

Solution 1:

Use Microsoft Cluster Administrator to ensure that the virtual DAG node is online and to check proper configuration of the Mail server nodes.

Solution 2:

Make sure that the Remote agent is installed on all the nodes of a DAG and that they are of the same version as that of the Backup Exec server.

Solution 3:

1. Ensure that the Backup Exec logon account being used to access the Exchange server is part of the Local Administrators group on the Exchange 2010 server and all the nodes of the DAG.

2. Ensure that the Backup Exec logon account is a member of the "Organization Management" Role Group in Exchange 2010.

Solution 4:

The above problem might occur as a result of Windows 2008 using Internet Protocol version 6 (IPv6) as a preferred protocol over Internet Protocol version4 (IPv4) and If the Exchange nodes are Windows 2008 Server. 

Perform the following on all the nodes of the DAG and Exchange server.

To resolve the issue, perform one of the following procedures on the Client Access server. The procedure to implement the workaround depends on whether the Exchange topology is running the Client Access server role and Mailbox server role on the same Exchange server or on different Exchange servers. 
 
For a single-server topology where the Client Access server role is running on the same Exchange server as the Mailbox server role.
 
1. Open the hosts file located at %SystemRoot%\system32\drivers\etc\ by using an editor such as Notepad.
 
%SystemRoot% refers to the drive where the Windows system files are located.  
 
2.  Comment out the line that references the IPv6 address.  
# :::1    localhost
 
3. Add the following lines into the file:
 
127.0.0.1                   hostname of the computer 
127.0.0.1                   FQDN of the computer 
actual IPv4 address    hostname of the computer 
actual IPv4 address    FQDN of the computer
 
3. Save the changes made to the file and restart the Backup Exec services on the Exchange server. 
4. Reboot the Exchange server. 
5. Run an Information Store backup/restore and verify the results. 




Article URL http://www.symantec.com/docs/TECH142542


Terms of use for this information are found in Legal Notices