Forum Discussion

spitman's avatar
spitman
Level 5
7 years ago

Help with nbu 8 client install - solaris

I have a client I'm trying to update the software on...

SunOS thishostname 5.10 Generic_147148-26 i86pc i386 i86pc

I'm on the NBU 8 master server, and I've tried the solaris10 and solaris10x86 ssh_to_client installs... neither are working. The ssh beginning part works of each, but then there's errors...

Solaris10:

Password:
Starting NetBackup Deduplication installer
testing: /tmp/pdde_pkg_dir_2912

Cannot access /etc/pdregistry.cfg. Please confirm /etc/pdregistry.cfg exists
and restart the installation.

NetBackup Deduplication preinstall check failed

ERROR:   Deduplication precheck failed.  Resolve issues with Deduplication
         installations and re-run this NetBackup installation script.

client_config_failed

Solaris_x86_10_64:

Password:
Starting NetBackup Deduplication installer
testing: /tmp/pdde_pkg_dir_3141

Cannot access /etc/pdregistry.cfg. Please confirm /etc/pdregistry.cfg exists
and restart the installation.

NetBackup Deduplication preinstall check failed

ERROR:   Deduplication precheck failed.  Resolve issues with Deduplication
         installations and re-run this NetBackup installation script.

client_config_failed

I recently upgraded the master/media servers from 7.7.3 to 8 (well, 3, they're appliances) and now I'm going through the clients trying to update them. This one client (and several others to come) were at 7.7.1... but due to the deinstall at the beginning this one now isn't working at all.

Help! And thanks.

  • Marianne's avatar
    Marianne
    7 years ago

    Okay, so we know that solaris10 is the wrong one since this is for SPARC.
    Solaris10x86 is correct for x86.

    What does /etc/release show on the client?
    And /usr/openv/netbackup/bin/version?

    If you have confirmed compatibility, then maybe a good idea to investigate the 'Cannot access /etc/pdregistry.cfg' error.

    There is a fairly old TN on how to check for corrupt /etc/pdregistry.cfg. https://www.veritas.com/support/en_US/article.000020909 
    There is still reference in this TN to 'Symantec/PureDisk', so, no idea if this TN can be followed to the letter. 

    Best to compare contents with other 

5 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    7 years ago

    Okay, so we know that solaris10 is the wrong one since this is for SPARC.
    Solaris10x86 is correct for x86.

    What does /etc/release show on the client?
    And /usr/openv/netbackup/bin/version?

    If you have confirmed compatibility, then maybe a good idea to investigate the 'Cannot access /etc/pdregistry.cfg' error.

    There is a fairly old TN on how to check for corrupt /etc/pdregistry.cfg. https://www.veritas.com/support/en_US/article.000020909 
    There is still reference in this TN to 'Symantec/PureDisk', so, no idea if this TN can be followed to the letter. 

    Best to compare contents with other 

    • spitman's avatar
      spitman
      Level 5
      7 years ago
      # cat /etc/release
                    Oracle Solaris 10 1/13 s10x_u11wos_24a X86
  Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.
                            Assembled 17 January 2013
# cat /usr/openv/netbackup/bin/version
cat: cannot open /usr/openv/netbackup/bin/version
# uname -a
SunOS thishostname 5.10 Generic_147148-26 i86pc i386 i86pc
#

      (the version file isn't there, because I've attempted multiple installs and it's apparently wiped it out.)

      I'll check out that link you posted and report back, thanks Marianne--

      And if it turns out I just can't upgrade the client, I'm fine to go back to the previous one it had (7.7.3) to get backups. This is just an unstructured data backup.

      • spitman's avatar
        spitman
        Level 5
        7 years ago

        So at some point the pdregistry.cfg had been "moved aside" (i.e. renamed) during an install and sat there. So I just put a copy of it back into place.

        THEN I found out that /tmp was almost out of room. Did I mention this is a pretty old host? :( So we added some swap (/tmp) to it, and reran the install...

        Voila!

        Thanks to all.