Forum Discussion

santave's avatar
santave
Level 4
11 years ago

transfering BMR information hang

Hi,

Previously client backup with BMR run completed succesfully.
Then its hanging when transfering BMR information to the master server on the last 2 days.
It just stuck on below log, then in few hours it will terminated by admin. Attached is the bmr log file.

Please suggest how to check and fix this issue?
 

01/26/2014 09:55:18 - begin Stream Discovery: Bare Metal Restore Save
01/26/2014 09:55:19 - collecting BMR information
01/26/2014 09:55:19 - connecting
01/26/2014 09:55:19 - connected; connect time: 0:00:00
01/26/2014 09:55:19 - transfering BMR information to the master server
01/26/2014 09:55:19 - connecting
01/26/2014 09:55:19 - connected; connect time: 0:00:00
01/26/2014 09:55:19 - started process bpbrm (pid=7602)

Thanks,
Santave

7.5
Backing Up
Backup and Recovery
Configuring
Linux
NetBackup
Restore
  • mandar_khanolka's avatar
    mandar_khanolka
    11 years ago

    backup selection is the problem. in order to take bmr enabled backup you need to consider at least OS file systems backup and netbackup client directory backup.

    Just backing up /tmp wont be sufficient to recover the system back.

    If you just want to see BMR enabled backup as success then add below directory path in your backup selection list. NOTE: Until and unless you add ALL_LOCAL_DRIVES or at least OS file system (+ system state in case of windows) you wont be able to recover your system.

    Add NB CLient dir path in backup selection list:

    for windows client, for instance:

    c:\program files\veritas\netbackup\baremetal\client

    for unix client, for instance,

    /usr/openv/netbackup/baremetal

    Try bmr enabled backup now.

    Thanks.

    Mandar

17 Replies

Sort By
Show More
  • santave's avatar
    santave
    Level 4
    11 years ago

    The 2 clients have the same OS version and nbu, redhat 6.2, nbu 7.5.0.6
    I have restarted nbu services on master, media and clients also, but no luck.

    Do you think, the new bmr can't update the exisiting bmr image?
    Should I delete old bmr image? (too bad, can't rename the old bmr image)

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    11 years ago

    Please get the logs

    vxlogcfg -a --prodid 51216 --orgid 119 -s DebugLevel=6 -s DiagnosticLevel=6

    The above will enable debug and diagnostic level 6 for OID 119: BMR Master Server Daemon (bmrd)  .

    Herewith a list of BMR OID's:

    119. BMR master and boot server (bmrd bmrdb)

    121. BMR Save Configuration  (bmrsavecfg)

    Repeat above vxlogcfg command for all required BMR processes (--orgid).

    Command to collect logs on master

    vxlogview -i 119 > <Path>\bmrd.log

    Command to collect logs on client

    vxlogview -i 121 > <Path>\bmrd.log

     

    Also provide the bpbrm log from media server.

  • santave's avatar
    santave
    Level 4
    11 years ago

    Before I run vxlogcfg, how to see my current config?
    After log generated, how to rollback my log config?

    If bmr failed, bmw config will not updated.
    But FS standard backup is completed successfully, when I disable BMR.
    In such case, Can I use the old bmr config for OS restoration and new FS backup image for data?

  • mandar_khanolka's avatar
    mandar_khanolka
    Level 6
    11 years ago

    >> In such case, Can I use the old bmr config for OS restoration and new FS backup image for data?

    It would work well with BMR recovery using "current" config. But in this case there should not be any change happened on your client system which can hamper BMR recovery. Changes like, disk/volume/fs/NIC etc.

    BTW check bpbrm (media server),, bmrd (bmr master server) and bmrsavcfg (client) logs to trace this issue.

    This is weird. I think problem is with process communication at media server. The logs would help to figure this out.

    Thanks.

    ~Mandar

  • santave's avatar
    santave
    Level 4
    11 years ago

    Hi, Please find all the logs attached.

    I tried, created new test policy with bmr enabled, backup selection = /tmp
    Still same issue, log attached.
     

  • mandar_khanolka's avatar
    mandar_khanolka
    Level 6
    11 years ago

    backup selection is the problem. in order to take bmr enabled backup you need to consider at least OS file systems backup and netbackup client directory backup.

    Just backing up /tmp wont be sufficient to recover the system back.

    If you just want to see BMR enabled backup as success then add below directory path in your backup selection list. NOTE: Until and unless you add ALL_LOCAL_DRIVES or at least OS file system (+ system state in case of windows) you wont be able to recover your system.

    Add NB CLient dir path in backup selection list:

    for windows client, for instance:

    c:\program files\veritas\netbackup\baremetal\client

    for unix client, for instance,

    /usr/openv/netbackup/baremetal

    Try bmr enabled backup now.

    Thanks.

    Mandar

  • santave's avatar
    santave
    Level 4
    11 years ago

    Do you mean, change backup selection to /usr/openv/netbackup/baremetal ? (create blank directory first)

    note: I have another policy for this server that backup all_local_drives with BMR disable.