
CliveSRT |
Hi,
What version of Symantec Backup Exec are you running? I would suggest uninstalling the remote agent and then pushing it out through the Backup Exec program to that server. You may need to reboot the server that the remote agent has been pushed to afterwards.
-CliveSRT-

tbitner |
Also check your Remote agent licensing on the Backup Exec server. Make sure you have enough remote agent licenses for all the remote servers. Also check their support site at <a href="http://www.symantec.com/enterprise/veritas/index.jsp" rel="nofollow">http://www.symantec.com/enterprise/veritas/index.jsp</a>

dtorizuka |
Assuming you installed the remote client on the remote server, check that the service is running on the remote server.
Also check the service login information on the remote server

SanStorageMan |
A quick thing to check is to make sure that name resolution is working properly. Run a reverse lookup for the client from the server and vice versa and make sure they can resolve each others’ names.
Jeff Redington

mFlorat |
Jmello,
In addition to the other replies you don’t mention what you are backing up to disk….tape? If your tape device is not set properly the B/U’s won’t work is RSM(removable storage mgr service) on ? B/E will exhibit this type of behavior if its on. It’s supposed to off by default but we’re talking windows here so that is not guaranteed. I had similar issues with B/E 10d, their tech support answer was update and add lic’s open file etc….I din’t want to spend any more than I already had so I found a better solution and dumped B/E, the problem is gone and i sleep better at night.
Good Luck.

astronomer |
I showed this to our backup expert and he said this is one of two things. Either there aren’t enough licenses or the agent wasn’t installed correctly. He insisted veritas is very particular about the syntax when installing the agent. The syntax is: setup /RANT32: -s
Hope this helps.
rt

jmello |
It was indeed a license issue. Thank you all very much for your help!