Forum Discussion

dipendra's avatar
dipendra
Level 4
8 years ago

Netbackup VMware Policy: Linux VM backup is failing with error 50 when File Recovery option is enbld

Hello,

Netbackup Environment on 7.6.1

Master on Linux 6.2

Media Server **bleep** Backup Host as Netbackup Appliance 5230 on 2.6.1

Linux VM on RHEL 6.2 with 12 TB of Disk size.

VMware policy

Backups are failing since few days after the filesystem extension was done on a Logical Volume, the backup works without File Level Recovery option but fails with error 50 when FLR is enabled and complains about:

 

GetDiskChangedInfoAPI: SYM_VMC_ERROR:  SOAP_ERROR

   04/15/2017 18:25:52 : g_vmmInterfaceLogger:libvix.cpp:1890 <INFO> : SOAP 1.1 fault: "":ServerFaultCode [no subcode]

Any help on this topic is much appreciated.

  • Thiago_Ribeiro's avatar
    Thiago_Ribeiro
    8 years ago

    Hi, 

    Did you check the Netbackup EEB Guide ? Maybe it can be a problem with NBU version 7.6.1. I was seeing the Netbackup EEB Guide Release 7.6 and 7.6.x.x ( Version 8), and I found these EEBs for this version. 

    Have you applied them in your environment?

    Look:

    Etrack Incident: 2990696
    ■ Associated Primary Etrack: N/A
    ■ Associated Service Request Etrack(s): N/A
    ■ Description:
    An issue occurred where VMware backups would fail with status codes 50 and
    84 and generate a backup-and-archive manager (bpbkar) core dump issue on
    a NetBackup appliance.

    EEB 3643984

    Hot fix or EEB Identifier
    3643984

    Description - Logical volume mapping (LVM) fails due to an incorrect offset for one of the file extents during VMware backup.

    Resolved in Versions - 8.0, 7.7.3, 7.7.2, 7.7.1, 7.7, 7.6.1.2

     

  • Thiago_Ribeiro's avatar
    Thiago_Ribeiro
    Moderator
    8 years ago

    Hi, 

    Did you check the Netbackup EEB Guide ? Maybe it can be a problem with NBU version 7.6.1. I was seeing the Netbackup EEB Guide Release 7.6 and 7.6.x.x ( Version 8), and I found these EEBs for this version. 

    Have you applied them in your environment?

    Look:

    Etrack Incident: 2990696
    ■ Associated Primary Etrack: N/A
    ■ Associated Service Request Etrack(s): N/A
    ■ Description:
    An issue occurred where VMware backups would fail with status codes 50 and
    84 and generate a backup-and-archive manager (bpbkar) core dump issue on
    a NetBackup appliance.

    EEB 3643984

    Hot fix or EEB Identifier
    3643984

    Description - Logical volume mapping (LVM) fails due to an incorrect offset for one of the file extents during VMware backup.

    Resolved in Versions - 8.0, 7.7.3, 7.7.2, 7.7.1, 7.7, 7.6.1.2

     

    • dipendra's avatar
      dipendra
      Level 4
      8 years ago

      Thanks Thiago,

       

      Let me check, this information can turn out to be very helpful.

    • dipendra's avatar
      dipendra
      Level 4
      8 years ago

      Can someone please share the link to download the EEB particularly for 7.6.1 Netbackup Environment and any document detailing about where to install (on server, backup host (Appliance) etc ....

  • dipendra's avatar
    dipendra
    Level 4
    8 years ago

    Tried:

    1. CBT reset option.

    2. Multiple Full Backups and then testing of FLR enabled backup but failed.

    Please guide here on next plan of action..

    • Marianne's avatar
      Marianne
      Level 6
      8 years ago

      Have you checked this document to see if this VM is supported for File Recovery option?

      Statement of Support for NetBackup 7.x and 8.x in a Virtual Environment:    http://www.veritas.com/docs/000006177

      See table 12 : VMware guest operating systems supported for file-level recovery

      • dipendra's avatar
        dipendra
        Level 4
        8 years ago

        Thankyou Marianne,

         

        Yes it is in the supported list, RHEL 6.2 and NBU installed is 7.6.1 on Master and Appliance on 2.6.1.

        The problem here seems to be that the Netbackup is unable to read information about modified time stamps etc and even CBT enabled backup is happening Full everyday with below statement in logs:

         

        04/26/2017 10:32:37 - Info bpbrm (pid=14022) reading file list for client
        04/26/2017 10:32:37 - Info bpbrm (pid=14022) accelerator enabled
        04/26/2017 10:32:37 - Info bpbrm (pid=14022) There is no complete backup image match with track journal, a regular full backup will be performed.
        04/26/2017 10:32:37 - Info bpbrm (pid=14022) starting bpbkar on client

    • GeForce123's avatar
      GeForce123
      Level 5
      8 years ago

      What is your ESXi version?

      What was the original disk space before extending it?

      I assume when you say the CBT reset option, you are referring to either doing this through vSphere or using powerCLI is that correct? Simply disabling BLIB in the backup policy does not turn off CBT.

       

      • dipendra's avatar
        dipendra
        Level 4
        8 years ago

        ESX Version is 5.5 U3

        CBT reset was done from vsphere and even I have disabled all Optimized options, ran a full backup and turned them back ON.

  • Thiago_Ribeiro's avatar
    Thiago_Ribeiro
    Moderator
    8 years ago

    Hi dipendra, I was looking for something at VMware side, and I found something in VDDK 5.5 Release Notes.

    See if this applies for you case.

    VDDK 5.5 Release Notes - https://www.vmware.com/support/developer/vddk/vddk-550-releasenotes.html

    QueryChangedDiskAreas API returns incorrect sectors after extending virtual machine VMDK file with Changed Block Tracking (CBT) enabled (2090639) - https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2090639

    Thiago.