Forum Discussion

Krutons's avatar
Krutons
Moderator
5 years ago

8.2 Client Upgrade

I recently upgraded an environment from 8.1.1 to 8.2 and had no issues except with 3 linux clients. When I tried to push the client upgrade using the deployment policies, I get a status 7226. I also ...
  • Krutons's avatar
    Krutons
    5 years ago

    Genericus  I have plenty of free space, that wasn't the issue.

     

    So I manually removed the RPM packages for everything after stopping the services. Then reran the install and it completed successfully with no issues.

     

    [root@<client name> NetBackup_8.2_CLIENTS2]# rpm -qa | grep VRTS

    VRTSnbcfg-8.2.0.0-1561464060.x86_64

    VRTSpbx-1.11.17.1-1.x86_64

    VRTSnbpck-8.2.0.0-1561464247.x86_64

    VRTSnbjava-8.2.0.0-1561464074.x86_64

    VRTSnbjre-8.2.0.0-1561464061.x86_64

    VRTSnbclt-8.2.0.0-1561464188.x86_64

    VRTSpddea-12.0.0.0-0140.x86_64

X2's avatar
X2
Moderator
5 years ago

I had one Linux (RHEL 6) client which failed with 7226. Normally, 7226 came up with Windows servers not having enough free space. But the RHEL 6 issue was peculiar (VxUpdate failed and so did manual install). In the end, it ended out to be non-NetBackup issue. The rpm database on the machine was corrupt. Once I recreated it, the installation (manual as there was no working NetBackup on the machine) went smoothly.

Also, as your servers shows VRTSnbpck as version 8.2, doesn't hurt recreating the rpm database and verifying which packages are actually installed.

  • Krutons's avatar
    Krutons
    Moderator
    5 years ago

    DPFreelance I have deleted all the certs on the client and re-deployed, same result.

    X2 I'll give that a try, didn't think about that. Even though I am still able to query the rpm packages, it could still be corrupt? Is there a way to verify that or check before I go and try to rebuild the rpm database.

    • davidmoline's avatar
      davidmoline
      Level 6
      5 years ago

      Krutons the other thing that is showing as a problem is the failure to remove the previous PBX package. You may want to see if you can manually remove that package from one of the systems. It could be a RPM DB corruption as suggested, or there could be something else (is PBX running in secure mode - although why that would cause a failure I don't know). Has the pbx_exchange process stopped (can it be killed)?

      Removing the PBX package manually will allow the new install (however you execute it) to just proceed without the removal step (so should allow the client package to install - unless there are other issues such as the rpm db corruption).

      I'd be surprised if this was a cert related issue - it looks to me a more fundamental OS rpm uninstall.install problem.

      • Krutons's avatar
        Krutons
        Moderator
        5 years ago

        Thanks davidmoline 

        I've verified that the RPM DB isn't corrupted and the PBX service is not running in secure mode. I've stopped all serivces on this server including PBX then restarted them all with no issues. The backups continue to run fine on 8.1.1. I'll try to manually remove the RPM package for PBX and maybe the VRTSnbpck RPM package as well and then try to manually run the 8.2 uprgrade/install again.