Forum Discussion

danguss's avatar
danguss
Level 4
6 years ago

Vmware Backup Status code 50

Hello, I have a problem with vmware backups ending status code 50.

The backups is aborted 

client process aborted  (50)

Des anyone have any idea of ​​the problem?

Master server: Windows Server 2016 x64

Media server host: Linux  3.10.0-693.17.1.el7.x86_64

esx vmware host: Red Hat Enterprise Linux Server release 7.6

vmware client: Red Hat Enterprise Linux Server release 7.6

vCenter: 6.5

 

8.1.2
Linux
  • Marianne's avatar
    Marianne
    6 years ago

    File level restore for XFS is very new - it was only introduced in NBU 8.1.2. 

    It seems that there are some 'teething' problems with this feature. 
    Like this one: https://www.veritas.com/support/en_US/article.100045622.html
    This is not related to your issue, but something else is wrong with this feature in your environment.

    It is therefore important that Veritas is made aware of this to investigate and find a solution.

  • Marianne's avatar
    Marianne
    Level 6
    6 years ago

    danguss 

    I have downloaded your logs. 

    I first had a look at the Job details - it shows that the bpbkar process failed.
     We also see in the Job details bpbkar PID 29656 with a timestamp of 09:14:16.

    The bpbkar log that you uploaded does not match. 
    Not the timestamps or the PID. 

    Please locate the correct bpbkar log and upload? 

      • Marianne's avatar
        Marianne
        Level 6
        6 years ago

        danguss 

        There should be another bpbkar log or more entries in bpbkar log. 

        The log ends at 08:52:16. 
        Job Details shows this entry: 
        22/08/2019 08:52:18 - Info bpbkar (pid=46861) 0 entries sent to bpdbm.

        If bpbkar on backup host srv15453 'crashed', there should be a core file.
        Can you please check on the media server /  backup host ?

        Question - do you have file level recovery option selected in the policy? 
        If so, have you tried without this option? 

        bpbkar log also shows errors returned by VxMS.

        Looking at VxMS logs, we see errors such as these: 

        08/22/2019 08:52:16 : readFileDataIntoBuffer:RvpUnixFile.cpp:265 <ERROR> : Unable to read file of type: 5
        08/22/2019 08:52:16 : readFileDataIntoBuffer:RvpUnixFile.cpp:266 <WARN> : Returning: 3

        08/22/2019 08:52:16 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <ERROR> : Initialize: Invalid superblock header
        08/22/2019 08:52:16 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <WARN> : FileSystemObject::claimFileSystem - unknown filesystem

        08/22/2019 08:52:16 : g_vixInterfaceLogger:libvix.cpp:1805 <DEBUG> : [VFM_ESINFO] VixDiskLib: VixDiskLib_GetMetadataKeys: Insufficient buffer size (has 1, need 203). Error 24 (Buffer is too small) at 5930.

        (There are multiple buffer errors).

        I don't know if this is coincidence, but it looks like the same time that bpbkar process crached. 
        VxMS carried on after this timestamp.

        Last VxMS entry:
        08/22/2019 08:52:29 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <WARN> : Retrieving inode 135110846 failed

        You will be better off logging a Support call with Veritas - they are better equipped to read and understand the errors in VxMS log.