Symantec Netbackup 6.5.4 to 7.5 Upgrade Failed
Hi Guys,
I have a problem after upgrading symantec netbackup 6.5.4 to NBU netbackup 7.5 for red hat linux 6.2. I've set up 2 clustered master server (nbu 6.5 and update to 6.5.4) with VVR. I readed all netbackup 7.1 and 7.5 release notes, install guide, upgrade guide and clustered master server guide. But after upgrading to nbu 7.5 i received these error:
./netbackup start
NetBackup Authentication daemon started.
NetBackup network daemon started.
NetBackup client daemon started.
NetBackup SAN Client Fibre Transport daemon started.
NetBackup will not run without /usr/openv/db/bin/NB_dbsrv running
NetBackup Authorization daemon started.
NetBackup Event Manager started.
NetBackup Audit Manager started.
NetBackup Deduplication Manager started.
NetBackup Deduplication Engine started.
NetBackup Enterprise Media Manager started.
NetBackup Resource Broker started.
Rebuilding device nodes.
Media Manager daemons started.
NetBackup request daemon started.
NetBackup compatibility daemon started.
NetBackup Job Manager started.
NetBackup Policy Execution Manager started.
NetBackup Storage Lifecycle Manager started.
NetBackup Indexing Manager started.
NetBackup Remote Monitoring Management System started.
NetBackup Key Management daemon started.
NetBackup Service Layer started.
NetBackup Agent Request Server started.
NetBackup Bare Metal Restore daemon started.
NetBackup Vault daemon started.
NetBackup CloudStore Service Container started.
VCS
NetBackup Service Monitor started.
NetBackup Bare Metal Restore Boot Server daemon started.
I tried to start NB_dbsrv but i received these error:
/usr/openv/db/bin/NB_dbsrv: error while loading shared libraries: libdbserv11_r.so: cannot open shared object file: No such file or directory
Please Help.
Thanks.
Hi Marriane,
Japao is my collegue and we have been working on this project.
This is the full story
Existing setup is Globally clustered (single node each site) NBU 6.5 Master on RHEL 4 which we initially planned to migrate to new machines running RHEL 6 then upgrade to 7.5.
During the testing, we have migrated the catalog to the new clustered setup. All the tests were ok. When it was time to upgrade it to 7.5 we encountered the error as mentioned in this post.
We rolled back the machines in the new setup and tried to upgrade it to 7.1 this time however the same error persists.
When we filed a case to Symantec support, after several days of troublehshooting, they concluded that 6.5.4 is not supported in RHEL 6.2. Which explains why during the installation it is unusually looking for some RPMS. Everything will work fine until you try to upgrade it.
So what we did is to reinstall the operating system to RHEL 5.7 and proceeded with the recommendation of support to upgrade it first to 7.1 then 7.5
Hope this experience will help others in the future
