Forum Discussion

Lacey_Chu's avatar
Lacey_Chu
Level 4
10 years ago

BMR full backup partially successful.

Hi,

NetBackup master/media/BMR master/boot server 7.6.1.2  OS:redhatlinux65  ( one physical machine )

SRT redhatlinux65 

six NetBackup clients 7.6.1.2:  redhatlinux6.6 KVM on top of redhatlinux6.5; NetBackup client software was installed on each VM.

one NetBackup client 7.6.1.2: redhatlinux59 KVM on top of redhatlinux6.5; NetBackup client software was installed on VM.

I am doing BMR full backup of my seven clients.

six NetBackup clients:  redhatlinux6.6 KVM  ---- failed

one NetBackup client: redhatlinux59 KVM -- succeeded

The detailed status is listed below. Can anyone help me on this issue? Thanks in advance!

06/03/2015 15:09:18 - Info nbjm (pid=42111) starting backup job (jobid=794) for client tang1-oam-1, policy Fullbackup-VzW, schedule diff-incr
06/03/2015 15:09:18 - Info nbjm (pid=42111) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=794, request id:{736DB956-09BF-11E5-9E2E-33D52B46E2F2})
06/03/2015 15:09:18 - requesting resource Fullbackup
06/03/2015 15:09:18 - requesting resource ming.NBU_CLIENT.MAXJOBS.tang1-oam-1
06/03/2015 15:09:18 - requesting resource ming.NBU_POLICY.MAXJOBS.Fullbackup-VzW
06/03/2015 15:09:18 - granted resource  ming.NBU_CLIENT.MAXJOBS.tang1-oam-1
06/03/2015 15:09:18 - granted resource  ming.NBU_POLICY.MAXJOBS.Fullbackup-VzW
06/03/2015 15:09:18 - granted resource  MediaID=@aaaac;Path=/var/images/nbk/fullbackup;MediaServer=ming
06/03/2015 15:09:18 - granted resource  Fullbackup
06/03/2015 15:09:20 - estimated 959088 kbytes needed
06/03/2015 15:09:20 - begin Parent Job
06/03/2015 15:09:20 - begin Bare Metal Restore: Start Notify Script
06/03/2015 15:09:20 - Info RUNCMD (pid=6664) started
06/03/2015 15:09:20 - Info RUNCMD (pid=6664) exiting with status: 0
Operation Status: 0
06/03/2015 15:09:20 - end Bare Metal Restore: Start Notify Script; elapsed time 0:00:00
06/03/2015 15:09:20 - begin Bare Metal Restore: Bare Metal Restore Save
06/03/2015 15:09:21 - collecting BMR information
06/03/2015 15:09:21 - connecting
06/03/2015 15:09:21 - connected; connect time: 0:00:00
06/03/2015 15:09:21 - transfering BMR information to the master server
06/03/2015 15:09:21 - connecting
06/03/2015 15:09:21 - connected; connect time: 0:00:00
06/03/2015 15:09:21 - started process bpbrm (pid=6670)
06/03/2015 15:09:46 - Error bpbrm (pid=6670) BMRERR: Received BMR error: Failed to import Config file. (27)
06/03/2015 15:09:46 - Error bpbrm (pid=6670) BMRERR: Received BMR error: Unable to parse client information. (6)
06/03/2015 15:09:46 - Error bpbrm (pid=6670) BMRERR: Received BMR error: Failed sending the discovery. (21)
06/03/2015 15:09:46 - Error bpbrm (pid=6670) BMRERR: Received BMR error: BMR information discovery failed. (35)
06/03/2015 15:09:46 - Info bmrsavecfg (pid=0) done. status: 1: the requested operation was partially successful
06/03/2015 15:09:46 - end writing
Operation Status: 1

06/03/2015 15:09:46 - end Bare Metal Restore: Bare Metal Restore Save; elapsed time 0:00:26
06/03/2015 15:09:46 - begin Bare Metal Restore: Policy Execution Manager Preprocessed
Operation Status: 0
06/03/2015 15:11:37 - end Bare Metal Restore: Policy Execution Manager Preprocessed; elapsed time 0:01:51
06/03/2015 15:11:37 - begin Bare Metal Restore: End Notify Script
06/03/2015 15:11:37 - Info RUNCMD (pid=8042) started
06/03/2015 15:11:37 - Info RUNCMD (pid=8042) exiting with status: 0
Operation Status: 0
06/03/2015 15:11:37 - end Bare Metal Restore: End Notify Script; elapsed time 0:00:00
Operation Status: 1

06/03/2015 15:11:37 - end Parent Job; elapsed time 0:02:17
the requested operation was partially successful  (1)

Regards,

Lacey

7.6
Backup and Recovery
Linux
NetBackup
Troubleshooting
  • Jaime_Vazquez's avatar
    Jaime_Vazquez
    10 years ago

    Disk type /dev/vda is not a supported device type by BMR. This due to the virtual environment it was created under.  It is a virtual device path.

     

    Look at this article for more information:

    Statement of Support for NetBackup 7.x in a Virtual Environment (Virtualization Technologies)   
    http://www.symantec.com/docs/TECH127089

     

     

     

  • Jaime_Vazquez's avatar
    Jaime_Vazquez
    Level 6
    10 years ago

    Use the following TECH article to assist in diagnosing the root cause of the error:

    BMR enabled backup jobs fail with status code 1
    http://www.symantec.com/docs/TECH207639

    Process failed on the client (failure of the bmrsavecfg process) or on the Master (failed to import the client data into the BMRDB).   The diagnostic steps in the article will point to which area it failed and help diagnose the cause of the failure.

    Let us know what you find out.

  • Lacey_Chu's avatar
    Lacey_Chu
    Level 4
    10 years ago

    I created a new SRT with redhadlinux66, installed the 7.6.1 client and 7.6.1.2 maintainance to this SRT.

    But still failed with the same error when did BMR backup.

  • Lacey_Chu's avatar
    Lacey_Chu
    Level 4
    10 years ago

    I executed the commant on my client.

    but with command not found error. Any advice here? Thanks

    tang1-oam-1:root # vxlogcfg -a -p 51216 -o 121 -s DebugLevel=5
    -bash: vxlogcfg: command not found

  • Lacey_Chu's avatar
    Lacey_Chu
    Level 4
    10 years ago

    error while execute below command on master server

    bmrs -o import -res config -path $PATH/bundle.dat   or $PATH\bundle.dat

    log into is attached. (vxlogview -i 119 )

    please help investigate. thanks!

  • Jaime_Vazquez's avatar
    Jaime_Vazquez
    Level 6
    10 years ago

    The SRT has nothing to do with the bmrsavecfg problem. SRT are created on a Boot Server and is not related to any client activity.

    The vxlogcfg command is found in the /usr/openv/netbackup/bin directory. Make sure it is in your path.

  • cruisen's avatar
    cruisen
    Level 6
    10 years ago

    Hi Lacey Chu,

    please checkthis technote:

    https://support.symantec.com/en_US/article.TECH60242.html

    Basically you need to Ensure that the parted command is available on the client. BMR runs the parted command when capturing the client disk partition information. If the command is not available on the client, the parted package will need to be installed on the client.

    best regards,

    Cruisen

     

  • Lacey_Chu's avatar
    Lacey_Chu
    Level 4
    10 years ago

    Hi Cruisen,

    I checked that the parted command is available on my client.

    tang1-oam-1:root # parted
    GNU Parted 2.1
    Using /dev/mapper/vg00-lvol11
    Welcome to GNU Parted! Type 'help' to view a list of commands.
    (parted) help

    Any other suggestion?

    Thanks,

    Lacey

     

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago
    Have you had a look at the vxlogview output? There are errors such as : "[ParseClientInformation.cpp:ParseClientInformation()] Critical function failed. OutputType = FDISK_NUM. 05/15/2015 00:08:03.627 V-128-18 [ImportCfg.cpp:ImportConfig()] unable to parse client information 05/15/2015 00:13:55.635 [ParseFdisk.cpp:ParseFdisk()] Unable to find the disk object for disk /dev/vda" So, it seems that OS command fdisk cannot find the disk object for /dev/vda. What type of disk /volume is this?
  • Lacey_Chu's avatar
    Lacey_Chu
    Level 4
    10 years ago

    Disk /dev/vda: 85.9 GB, 85899345920 bytes
    16 heads, 63 sectors/track, 166440 cylinders
    Units = cylinders of 1008 * 512 = 516096 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00022596

       Device Boot      Start         End      Blocks   Id  System
    /dev/vda1   *           3         612      307200   83  Linux
    Partition 1 does not end on cylinder boundary.
    /dev/vda2             612      166441    83577856   8e  Linux LVM
    Partition 2 does not end on cylinder boundary.

    Disk /dev/vdb: 644.2 GB, 644245094400 bytes
    16 heads, 63 sectors/track, 1248304 cylinders
    Units = cylinders of 1008 * 512 = 516096 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000