01-27-2020 01:17 PM - edited 01-28-2020 05:34 AM
Has anyone noticed anything similar when trying to push an upgrade via VxUpdate?
Client is running 8.1.1 and is a Solaris10 (Generic_150400-59 sun4u sparc) a container. The global zone is running NetBackup 8.2.
23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) Installing NetBackup Pre-Check as <VRTSnbpck> 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) ## Executing preinstall script. 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) Thursday, January 23, 2020 3:27:33 PM EST: Installing package VRTSnbpck. 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) Bad string 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) Resolved machine role [CLIENT] from existing NetBackup configuration. 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) Bad string 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) Bad string 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) Please review the VERITAS SOFTWARE LICENSE AGREEMENT located on 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) the installation media before proceeding. The agreement includes 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) details on the NetBackup Product Improvement Program. 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) For NetBackup installation and upgrade information specific to your 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) platform and to find out if your installed EEBs or hot fixes are 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) contained in this release, check the Installation and Upgrade checklists 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) and the Hot Fix and EEB Release Auditor, both available on the Veritas 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) Services and Operations Readiness Tools (SORT) page: 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) https://sort.veritas.com/netbackup. 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) ERROR: Detected an attempt to install incorrect platform and/or 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) operating system and version client binaries on [FQDN]. 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) ERROR: Detected an attempt to install incorrect platform and/or 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) operating system and version client binaries on [FQDN]. 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) pkgadd: ERROR: preinstall script did not complete successfully 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) 23-Jan-2020 3:27:35 PM - Info RUNCMD (pid=46790) Installation of <VRTSnbpck> failed.
The following appears in the VRTSnbpck install log file
ERROR: Detected an attempt to install incorrect platform and/or operating system and version client binaries on [FQDN>].
and packages installed on the container are:
application VRTSnbcfg NetBackup Configuration
application VRTSnbclt NetBackup Client
application VRTSnbjava NetBackup Java Console
application VRTSnbjre NetBackup Java JRE
application VRTSnbpck NetBackup Pre-Check
PS: This issue has appeared on more than 1 container.
01-28-2020 05:53 AM
Hello,
review all NetBackup policies for this client if it has a correct OS/HW type configured in them.
Regards
Michal
01-28-2020 06:38 AM
Both the global zone and the container are setup as Solaris/Solaris10 in their backup policy and backed up only via a single backup policy.
01-28-2020 06:54 AM - edited 01-28-2020 06:54 AM
Is this a 'whole root local zone' or 'sparse root local zone'?
I think vxupdate will only work for whole root local zone.
This TN is quite old, but it explains different scenarios: https://www.veritas.com/content/support/en_US/article.100025009
01-28-2020 07:39 AM
@MarianneJust verified that those are whole root local zones.
I will open a case with support and update as I get more information.
02-04-2020 12:10 PM
Nothing much to add but a quick update. Support says there are somes issues with VxUpdate and Solaris. They suggested manual install, which fails with the following message. Any suggestions?
ERROR: Detected an attempt to install incorrect platform and/or operating system and version client binaries on solClient.
02-05-2020 12:15 AM - edited 02-05-2020 12:21 AM
What is in the current 'version' file on the client?
(/usr/openv/netbackup/bin/version)
Can you navigate to /usr/openv/netbackup/bin/ in the installation media (you may need to extract it somewhere) and compare contents of version file?
Is /usr mounted read/write?
**** EDIT ****
Herewith my experience with update_clients which gave the same error as your installation attempt :
https://vox.veritas.com/t5/NetBackup/update-clients-failure/td-p/245901
02-05-2020 09:07 AM
# less NetBackup_8.2_CLIENTS1/NBClients/anb/Clients/usr/openv/netbackup/client/Solaris/Solaris10/version NetBackup-Solaris10 8.2 # cat /usr/openv/netbackup/bin/version NetBackup-Solaris10 8.1.1 # uname -a SunOS clientName 5.10 Generic_150400-30 sun4v sparc SUNW,Sun-Fire-T200
NB: I extracted the NetBackup_8.2_CLIENTS1.tar.gz on the client to do a manual install.
What is the difference between Solaris/Solaris10 and Solaris/Solaris_x86_10_64 ?
Also, the upgrade worked on a different container.
-bash-3.2$ uname -a SunOS goodClient 5.10 Generic_150400-59 sun4u sparc SUNW,SPARC-Enterprise -bash-3.2$ cat /usr/openv/netbackup/bin/version NetBackup-Solaris10 8.2
Is there a fundamental difference betwwen these two? Both are Solaris 10, and one worked and other failed!
02-06-2020 01:57 AM
Not sure where this question is coming from?
What is the difference between Solaris/Solaris10 and Solaris/Solaris_x86_10_64 ?
Solaris/Solaris10 is for SPARC hardware.
Solaris/Solaris_x86_10_64 is for x86 hardware.
If you try to install NBU for Solaris_x86_10_64 on SPARC hardware, I would expect the installation to fail.
These binaries will simply not work on SPARC.
02-13-2020 01:25 PM
quick update: I removed NetBackup client install manually from the Solaris server. Then tried to install 8.2 manually - it failed the same way. Tried installing 8.1.1 and installation went on normally.
It seems the installer is broken in version 8.2 for Solaris.
So another attempt at VxUpdate after a clean install of 8.1.1 ends up filling up the partition on which the NetBackup is installed. Especially, the install fails to stop all processes and fill up /usr/openv/netbackup/logs/nbstop/ with several GB of log files!
02-25-2020 12:22 PM
I never use VxUPdate for solaris since you can run the update_client from the master to update all the unix clients.
I may take up some space - make sure you have allocated at least4GB for /tmp.
If you have issues, it may leave it in an uncertain state, which will require a full uninstall, sometimes the solution is to reinstall on old version and upgrade it, lol.
If you run the update_client, it will build a file in /tmp, you can edit it so save out only the clients you want, then update only those few. I am only up to 8.1.2, but it has worked great so far.