use update_clients to upgrade clients to 7.5.0.3 but failed

[Ivy_Yang]

hi,

as per the doc http://www.symantec.com/business/support/index?page=content&id=TECH178490 , I upgrade linux clients to 7.5.0.3 from NBU master.

currently our NBU master and media server are running NBU7.5.0.3;

Master:  [root@lx0034nbumast iyang]# cat /usr/openv/netbackup/bin/version
              NetBackup-RedHat2.6.18 7.5.0.3
Media : [root@lx0034nbumed01 ~]# cat /usr/openv/netbackup/bin/version
            NetBackup-RedHat2.6.18 7.5.0.3

and clients are running with NBU7.1 or 6.5.

[root@lx0034nbumast ~]# /usr/openv/netbackup/bin/admincmd/bpplclients -allunique -noheader |grep Linux |grep fin > clients_name

[root@lx0034nbumast iyang]# cat clients_name   ====>I only pick 2 boxes
Linux RedHat2.6 client1
Linux RedHat2.6 client2

[root@lx0034nbumast iyang]# /usr/openv/netbackup/bin/update_clients  -ClientList clients_name     
There are 12 clients to upgrade.
Do you want the bp.conf file on the clients updated to list this server as the master server? [y,n] (y)
Enter the number of simultaneous updates you wish to take place [1 - 2] (default: 2): 
The upgrade will likely take 1 to 2 minutes.
Do you want to upgrade clients now? [y,n] (y)
Please be patient.
Updating client client1-- Linux hardware running RedHat2.6
Updating client client2-- Linux hardware running RedHat2.6
The update trace can be found in /tmp/update_clients.09-06-2220.14843.

[root@lx0034nbumast iyang]# cat  /tmp/update_clients.09-06-2220.14843    
Will not update client client1
        client1 is defined as a client type from an earlier release of NetBackup.
Will not update client client2
       client2 is defined as a client type from an earlier release of NetBackup.

Any one who can help point theright direction?

[Ivy_Yang]

by the way, some posts mentioned if OS upgraded or current hardware mismatched what configured at the first time.

but I don't have such issue.  let me take client1 as example. the os version is exactly the same.

 [fndsa@client1~]$ uname -a         
Linux finprdc1n1 2.6.18-238.el5 #1 SMP Tue Jan 4 15:41:11 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

[root@lx0034nbumast iyang]# bpgetconfig -s client1 -L -A
Client/Master = Client of lx0034nbumast
NetBackup Client Platform = Linux, RedHat2.6
NetBackup Client Protocol Level = 7.1.0
Product = NetBackup
Version Name = 7.1
Version Number = 710000
NetBackup Installation Path = /usr/openv/netbackup/bin
Client OS/Release = Linux 2.6.18-238.el5
Cipher = AES-128-CFB
Cipher = BF-CFB
Cipher = DES-EDE-CFB
Cipher = AES-256-CFB
Patch Level = 7.1

any idea?

[Marianne]

Check version file on the client in netbackup/bin folder. Probably older installation that shows 2.4 version? In that case, use update_clients with -ForceInstall. Also check for 32-bit clients that cannot be updated.

[Ivy_Yang]

hi,Marianne

the clients are new..they are redhat2.6 and they are 64bit

I tried -ForceInstall  but don't work

[fndsa@finprdc1n1 ~]$ cat /usr/openv/netbackup/bin/version
NetBackup-RedHat2.6 7.1

[Andy_Welburn]

Can you confirm the client version on the master?

/usr/openv/netbackup/client/Linux/RedHat2.6/version

[Genericus]

I created a "gotcha" thread for just this type of thing.

The update client command can fail for a number of reasons - some are already noted - 32bit is a big fail.

Space in /tmp is also a fail - if you limit the size the install can fail.

Version file can also cause it to fail.

Be aware - you may need to login to the failed clients and manually start the netbackup client, since the failed install can cause backups to fail until the client is restarted.

Test by checking your Host properties/Clients - you will get a error 58 to those clients if connectivity is broken.

[Marianne · Accepted solution]

Have a look at Client Selection topic in OS Compatibility Guide - 
New 7.x Client Selection for RHEL is Linux RedHat2.6.18.

Verify correct version in /usr/openv/netbackup/client/Linux/RedHat2.6.18/version on your master.

Update your policies and/or ClientList file, followed by ForceInstall.

[CRZ]

I'm not sure update_clients will actually work for you given that "RedHat2.6" and "RedHat2.6.18" are "different."  If you want to test it, you could manually edit your client_names file and change the "2.6" to "2.6.18" but I honestly don't know if that will work or not.  Otherwise, you should be able to change the type in the GUI like Marianne says, and then push a "new" client installation out from there.

I'm sure we had an excellent reason for changing the client name in 7.5 beyond making this process extremely aggravating.  ;)

[Ivy_Yang]

[root@lx0034nbumast iyang]# cat /usr/openv/netbackup/client/Linux/RedHat2.6/version
NetBackup-RedHat2.6 7.1

[Ivy_Yang]

thanks for your responding!

but we are 64bit os...we have enough space in /tmp.......still digging

[Ivy_Yang]

hi, Marianne

it's indeed works after I changed the client from RedHat2.6 to RedHat2.6.18.

Actually I tried this last week but I forgot to update "clientlist" with  RedHat2.6.18 so it failed.

I tried again today and ran "/usr/openv/netbackup/bin/admincmd/bpplclients -allunique -noheader |grep Linux" to get "clientlist"

then it works1 hiahiahia

thanks everybody for your help!