Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 315
  • Last Modified:

Veritas 8.6 agent inquiry

Hi, I got a windows 2k with veritas 8.6 installed and 3 license for an agent. I had 3 installed on a win nt 4.0  server sp6a on a pdc and bdc and another on wint server 4.0 server.

Suddenly backup on the pdc wouldn't work and i checked the agent it says installed: yes, status: running, version not available.

I tried a test backup on the other 2 server bdc and another nt server and the backup is successfull however, when i tried the pdc it stays at backup scan.
(i had the same test above and it shows the version 8.6.xx.xx)

i have re-installed the agent and still have the same problem. please advice.

0
edongskiu
Asked:
edongskiu
1 Solution
 
scampgbCommented:
Unfortunately I can't give you a precise answer, but I can suggest a few things to check.

This could well be a login/authentication problem.

I suggest that you look in the application event log on the PDC and see if there's anything in there, especially after a reboot.
Check what account the Backup Exec agent service is running as.  It will need to be an account that can access the files you want to back up - making it a member of the "Backup Operators"group should help with this.

I've encountered some odd behaviour with Backup Exec on NT when the remote PC you're trying to back up (in your case, the PDC) is logged in at the console.
I suggest making sure that no-one is logged into the server console, and try the backup again.

Also, did you get any error messages when doing the remote install of the agent?

I suggest that you try to do a test backup of a file from the PDC, with detailled logging turned on.  If none of the above works, it might give some hints as to the problem.

Let me know how you get on with that lot, and I'll think of some other ideas.
0
 
edongskiuAuthor Commented:
I found the root cause of the problem, it arises everytime I reboot the server and the only way to resolve it is to re-attach the server and it works fine afterwards.

thanks!
 
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now