Open a support ticket with Veritas.
If its its a general issue, they should know how to workaround the issue fairly quick.
Extract from NetBackup Upgrade Guide
Converting from Symantec RPM packages to Veritas RPM packages
Because of package name changes, rpm -U does not work to upgrade Linux clients
from NetBackup 7.7.2 and earlier to NetBackup 7.7.3 and later. You have two
options to correctly upgrade your client and convert to the Veritas RPM packages.
■ Remove the old SYMC* RPM packages with the command shown. This process
preserves your NetBackup client configuration.
rpm -e SYMCnbjava
rpm -e SYMCpddea
rpm -e SYMCnbclt
rpm -e SYMCnbjre
Then upgrade to the new Veritas RPM packages using the RPM installer of your
choice. More information is available.
See “To install or upgrade the Linux client binaries using standard RPM tools:”
on page 125.
■ Alternatively, you can use the NetBackup installer to upgrade the client to the
new Veritas RPM packages.
The last bullet point seems to indicate that the NetBackup installer 'should' work.
Any clues in the Installation log?
Hi Marianne,
I got the exact same reply from support.
The problem is that their option 1 is not practical for 1000+ clients and option 2 gets a failure related to the rpm names not matching.
Catch-22 situation.
So we are investigating a method using puppet (system versioning tool, with global script capabilities)
Rob.
Any clues in the Installation log?
Possible failure due to OS security lockdown at this customer?
We have not seen any other reports of upgrade failures as a result of package name change.
So, gut-feel is that there is something 'different' at this particular site.
