Granular recovery technology (GRT) enabled restore to an exchange setup with Client Access Server (CAS) hardware NLB fails with an error "Remote agent not found" error

Article:TECH156173  |  Created: 2011-03-22  |  Updated: 2014-02-06  |  Article URL http://www.symantec.com/docs/TECH156173
Article Type
Technical Solution


Issue



GRT enabled restore to an exchange setup with CAS hardware NLB fails with an error "Remote agent not found"


Solution



For Backup Exec 2010:

Create a host file entry in the backup server with the IP of actual CAS server pointing to the NLB.

Eg : If the NLB name is NLB.domain.com and actual servers are SERVER1(with IP - 192.168.0.2) and SERVER2 (IP - 192.168.0.3), go to backup server's C:\Windows\System32\Drivers\etc and edit the hosts file to add below lines, and then run the GRT restore.

192.168.0.2          NLB.domain.com
192.168.0.3          NLB.domain.com

For Backup Exec 2012 and later

Run a redirected restore directly to the actual CAS server.

That means, in the above given example, if you have Backup Exec 2012, while restoring, use redirection option to restore to SERVER1 or SERVER2.


Supplemental Materials

SourceETrack
Value2327117
Description

 EXCH: GRT restore fails with “Remote agent not detected error” if environment is set to hardware CAS NLB


SourceUMI
ValueV-79-57344-33898
Description

Remote Agent not detected.

The resource could not be restored because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.



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


Terms of use for this information are found in Legal Notices