cancel
Showing results for 
Search instead for 
Did you mean: 

Live update failing from 7.6.0.1 to 7.6.0.3

tollboy
Level 4

Hello,


I am testing live update on my environment as we have to upgrade lots of windows client. I am running the live update policy for one windows machine only.

This is what error I am getting.

 

==================

04/07/2015 01:20:03 - requesting resource backup1.NBU_POLICY.MAXJOBS.LiveUpdate-Test
04/07/2015 01:20:04 - granted resource  backup1.NBU_POLICY.MAXJOBS.LiveUpdate-Test
04/07/2015 01:20:05 - started process RUNCMD (pid=15477)
04/07/2015 01:20:06 - ended process 0 (pid=15477)
04/07/2015 01:20:40 - Info nbliveup (pid=2196) LiveUpdate Server location converted from "file:/net/backup1/usr/openv/liveUpdateServer" to "file:\\backup1\usr\openv\liveUpdateServer"
04/07/2015 01:20:40 - Info nbliveup (pid=2196) Updating LiveUpdate Server location to: file:\\backup1\usr\openv\liveUpdateServer
04/07/2015 01:21:40 - Error nbliveup (pid=2196) Error executing "C:\Program Files\Symantec\LiveUpdate\LUALL.EXE" -s -h "C:\Program Files\VERITAS\NetBackup\LiveUpdateHost.hst", stopping update.
04/07/2015 01:21:41 - Info nbliveup (pid=2196) Start of the pack summary file:
04/07/2015 01:21:41 - Info nbliveup (pid=2196) (02/08/07 22:12:21) Installed VERITAS NetBackup 5.1 Maintenance Pack 4 (NB_51_4_M)
04/07/2015 01:21:41 - Info nbliveup (pid=2196) (05/29/09 17:38:59) Installed Veritas NetBackup 6.5.3 (6.5 Release Update 3) (NB_65_3_U)
04/07/2015 01:21:41 - Info nbliveup (pid=2196) (05/29/09 17:42:54) Installed Veritas NetBackup 6.5.3.1 (6.5 Release Update 3 HotFix 1) (NB_65_3_U)
04/07/2015 01:21:41 - Info nbliveup (pid=2196) (01/17/10 00:38:31) Installed Veritas NetBackup 6.5.4 (6.5 Release Update 4) (NB_65_4_U)
04/07/2015 01:21:41 - Info nbliveup (pid=2196) End of the pack summary file:
04/07/2015 01:21:41 - Info nbliveup (pid=2196) EXIT STATUS 77
execution of the specified system command returned a nonzero status  (77)

==================

 

I am ataching the logs from liveupdate directory on client as well.

 

Master Server: Solaris 10 (7.6.0.3)

Client:  Windows 2003, (7.6.0.1)

 

NFS  server on master server as live update server:

/usr/openv/liveUpdateServer       (everyone)

 

Please let me know if I am doing something wrong.

 

 

3 REPLIES 3

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
According to the output in your opening post, the client seems to be on NBU 6.5.4. LiveUpdate found patch history from 5.1.x through to 6.5.4. No evidence of 7.x. Maybe double check Client OS? Possibly something that is no longer supported by NBU 7.x?

tollboy
Level 4

I have tried it other windows server also same issue. Some how it is detecting only these versions of NBU all the time. In NBU folder.

below is the from the bpcoverage of the client.

 

root@backup1 2 [ / ] # bpcoverage  -c  usnvwwaspvrms1
       File System Backup Coverage Report (UNIX and Windows only)
       ---------------------------------------------------------------------------------

       Key:  *         - Policy is not active
             UNCOVERED - Mount Point not covered by an active policy
             MULTIPLE  - Mount Point covered by multiple active policies


CLIENT: usnvwwaspvrms1

   Drive Letter               Backed Up By Policy   Notes
   ------------               -------------------   -----
   C:\                        npvntmon
   C:\                       *NB6531_win_clients
   F:\                        npvntmon
   F:\                       *NB6531_win_clients
   Shadow Copy Components:\   npvntmon
   Shadow Copy Components:\  *NB6531_win_clients

                       Policy Hardware/OS Report
                       -------------------------

       Key:  *         - Policy is not active
             CLIENT    - hostname (uname information)
             VERSION   - NetBackup version running on the client


CLIENT:  usnvwwaspvrms1 (Service Pack 2/Windows2003 5.2 build 3790)
VERSION: 7.6

   Policy Name           Hardware/OS
   -----------           -----------
  *NB6531_win_clients    Windows-x86/Windows2003
   npvntmon              Windows-x86/Windows2003
root@backup1 3 [ / ] #

 

 

Earlier the client was on some 7.1. I have upgraded it to 7.6.0.1  manually, so that I can test the live upgrade between minor version first. Windows 2003 is supproted as a client, isn't it?

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

So, client is already on 7.6?

CLIENT:  usnvwwaspvrms1 (Service Pack 2/Windows2003 5.2 build 3790)
VERSION: 7.6

 

I have honestly no 1st-hand experience with NBU LU. 
All I noticed in job log were the references to o-l-d versions.

Not sure how exactly LU checks for Client versions, as Client's History file (In C:\Program Files\Veritas\Patch) only contains record of patches, not version upgrades.

The version.txt file in C:\Program Files\Veritas\NetBackup contains the currently installed version.
IMHO, LU should look at the version file as well, not only History.

Windows Server 2003 is still supported by NBU 7.6.x as a Client.

Probably best to log a Support call at this stage...