I thought this was fixed in 6.5.2a which was just released
Reneé Carlisle
ServerWare Corporation
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Navarro,
Eddy
Sent: Friday, July 25, 2008 8:21 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] 6.5.2 and Solaris - BEWARE!!!
All,
If
you are running a Solaris NBU master server and are planning on upgrading to
6.5.2, think twice. We just upgraded and now backups simply do not
work. Backups either do not start AT ALL when scheduled or manually
started backups error out with code 230.
Per
the technote at http://seer.entsupport.symantec.com/docs/305609.htm
Issue:-
Upgrading NetBackup to 6.5.2 can cause scheduled or manually
initiated backups to fail with STATUS 230. The policies are failing to
update/convert the backup selection list from a UTF-8 to a local locale.
All the policies are available in the NetBackup class/policy
database. Existing policies can be updated and new policies can be
created, however, they experience the same problem when started. The only
backups that can be run successfully are User Backups.
This problem has now been on
systems running Solaris 8, Solaris 9 and Solaris 10.
Evidence:-
(NBPEM Log)
11/06/2008 10:52:42.273 [Debug] NB 51216 nbpem 116 PID:23387
TID:3 File ID:116 [No context] 1 [PolicyInfoConverter::FileListToSelectionList]
Could not convert policy '<POLICY_NAME>' failed to convert
filelist entry 0, error code=22 (PolicyInfoConverter.cpp:445)
11/06/2008 10:52:42.274 [Application] NB 51216 nbpem 116
PID:23387 TID:3 File ID:116 [No context] [Error] V-116-206 Failed to
get policy <POLICY_NAME> information from database, 20
11/06/2008 10:52:42.274 [Application] NB 51216 nbpem 116
PID:23387 TID:3 File ID:116 [No context] [Error] V-116-266 call
NBProxy::getRealAndVirtualPolicyByName failed to nbproxy with status 20
Solutions:-
Option 1: Install NetBackup
6.5.3, search patch readme for reference 1317013.
or
Option 2: Uninstall
NetBackup 6.5.2. NetBackup 6.5.1 or 6.5GA do not experience this problem.
or
Option 3: Contact Symantec
support to request an emergency engineering binary fix for NetBackup 6.5.2, if
NetBackup 6.5.3 is not yet available (NetBackup 6.5.3 is scheduled for
August/September 2008).
We have been on the phone with
Symantec to obtain this “binary fix” since 6.5.3 isn’t out
yet, and evidently this is phantomware as they are saying it is not yet
available.
