Remote Agent not present - but only on one volume

[DJA771]

Hi everyone, I'm tearing my hair out with this one...

We have a W2K server (SP3) running remote agent 8.6. The C: drive is failing to backup using the remote agent, but the D: drive is backing up OK with the remote agent.

The log reports Remote Agent not present - performing standard backup.

Anyone ever had this problem?

 

[vesna72]

Yes, I am having that problem right now - and its not the first time it has happened either. I found in the past that I just had to reinstall remote agent on that particular remote server and/or drive, and it worked - until now. Reinstalling remote agent hasn't helped. The problem may lay in the backup Exec agent browser, where its not detecting the remote agent on the server. I'm painstakingly going through logs or any files that may be locking this particular service and rendering it unavailable, so if I come up with some genius answer, I will be posting it in here ASAP.

 

[DJA771]

Hi Vesna72, I'm glad I'm not alone with this.

 

[cndybndy]

YOu have install the remote agent to the server/drives in question login using the Admin Account for the Remote Agent. Make Sure you reboot the machines after installing the Remote Agent. Go into the Backup Exec Console and open the selections tab and make sure that the drives you want backup up are showing. Go into the registry and make the following changes. First stop your backup services.

1. Stop the Backup Exec Services on backup server.
2. Open Regedit.exe and browse down the following path:
a. HKLM\software\veritas\backupexec\engine\ntfs
3. Change the value of Restrict Anonymouse Support to 1
4. Go to Edit-->New --Dword Value
5. Value name should be useAdSSCheck
6. String should just be the number 0
7. Change Keys under Hkey_Local _Machine\Software\Veritas\Backup Exec\Engine\Agents Increase the Send Timeout value to 1800 (decimal)
Increase the Receive Timeout value to 1900 (decimal
8. Start the Bakcup Exec Services
-On the target server (server for which the error is reportted)
1. Stop the Remote Agent Service
2. Follow Steps 2-6 from the list above
3. Start the Remote Agent Service

** If any keys are not on remote machine, that is ok skip those
Run test of System State

YOU ALSO NEED TO HAVE THE BACKUP ACOUNT USERID ADDED TO THE ADMINISTRATIVE GROUP ON ALL THE SERVERS.

 

[DarraghFitzpatrick]

go to the veritas web site, look in the knowledge base, searching with the exact message listed in your backup event log. There are 3-4 articles describing solutions

 

[dogmata]

most common reason is that there are some legacy appletalk entries in the registry on either the media server or the the remote box. Remove those entries from a registy key (think its in hklm\ \ \ winsock\transports

as per previous post its on their website

 

[dogmata]

another thought just occurred to me...are you using OFO (open file option) > if so, increase the remotes agent timeout values in the registry on the media server as, if OFO is taking 1000 secs to aquire the snapshot (needs 5 secs of disk quiet time) the remote agent , who's timeout value is about 300 secs, will timeout:

- HKLM\software\veritas\backup exec\engine\....cant remember the path after that but the values are called "GRFS Timeout" (cahnge this to dec > then 1200 >> then back to hex, Receiveas and receiveas Timeout values to 3600 dec, cycle the backup exec services

Cheers
Dog

 

[dogmata]

** note, previous entry should of been ReceiveAs and SendAs timeout values > got a bit trigger happy

Cheers
Dog