Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ExecView Problem since patch was installed 1

Status
Not open for further replies.
Nov 21, 2002
10
US
Hello and thanks in advance for any replies I get to this one.

I'm having a problem with ExecView Console 3.2 since I installed a security patch from Veritas to all of my servers and remote agents. I run BE 10 and have just installed the 10.0 5520 Hotfix 15 to all of the servers and remote agents. Backups seem to be running fine and services are all up and running on all machines. My problem is this, in ExecView on my main backup server I am showing 5 out of 13 Remote Servers as accesible, the rest are showing up not accessible.

I've tried creating a new monitoring group in ECM but when I try to add servers it tells me it cannot connect. I know its not an authentication problem, i can remotely connect to all of the servers fine through BE, just not through ECM. I tried a repair install of ECM on one of the remote servers with no luck. I've restarted all BE Services on all remote servers also with no success.

If anyone has any ideas it would be a great help. Also if there is something i didn't explain clearly enough let me know.

Regards,
 
When you installed the ECm on the servers did you install it from execview or backup exec. If you did from execview you should remove it and then install it through backup exec
 
Thanks for the suggestion.
Actually I resolved this some time ago after discovering that the previous installation used a different port in the ECM Configuration. This would never have been an issue if there was some internal documentation indicating that my particular office used a non-standard RMI port for ECM.

For anybody that runs into this in the future, here is the way I resolved the issue.

1st you have to locate the ecmsettings.properties file.
It will be located in the directory you installed BE and ECM to.
ex. D:\Program Files\VERITAS\Backup Exec\ECM\

The file will look something like this:

rmiport = 1099
ecmport = 3524
maxnumcompletedjobs = 99
sendcompletestatus = 99

You can see the line that reads 'rmiport = 1099' which in my organization has been changed to utilize a different port for whatever reason. Both the RMI and ECM port numbers are customizable, you just have to use that same set of ports across your entire enterprise. If someone had told me that from the get-go, I would never have had this problem.
[thumbsup2]
Regards,

Arlie



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top