RE: Netbackup Client Using Wrong Server

The HKLM\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\Server key does hold the old server, followed by the new one - so that may be causing the problem. Unfortunately it's stored in hex values so I'm hesitant to try updating it. The other odd thing I noticed is that in the "Backup, Archive and Restore" GUI, it won't let me delete the old server from the server list, but it allows me to delete and re-add the new one all I want, and allows me to make either of them current. So, it seems that it is having a hard time letting go of the old server for some reason.  

It does show the correct server under
HKEY_CURRENT_USER\Software\VERITAS\NetBackup\NetBackup Client\oracle\Settings\DefaultServerName so I'd think that would do the trick, but maybe that other key you mentioned is overriding this one.  

I think we might have to go with a reinstall.  

I'm not positive that PARMS was ever working, but IIRC, we had to set those in order to get the backups to work initially - otherwise we would have just set all the NB_ORA_* parameters as regular environment variables in the script like we do for all our Unix clients, but those don't seem to get picked up consistently on Windows.  

Thanks!

From: Jared Still [mailto:jkstill_at_gmail.com]

See what is in the registry:
HKLM\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\Server  

How do you know that the PARMS parameters worked in the past, and you weren't
just lucky and all the defaults worked?

Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

--
http://www.freelists.org/webpage/oracle-l