Forum Discussion

nzog86's avatar
nzog86
Level 3
2 years ago

VMware virtual machine backup fails with status code 6 : User Backup failed

Morning all,

Need help for backup failure of my vmware virtual machines with the error code 6 User backup failed.

Below, the detailed status logs:

18 janv. 2023 08:12:13 - Info bpbrm (pid=332147) The data-in-transit encryption (DTE) is disabled for the client (cmmkp-nba-media01) as the global DTE mode is set to 'Preferred Off' and the client DTE mode is set to 'Automatic'
18 janv. 2023 08:12:13 - Info bpbrm (pid=332147) smallsafe-svr01 is the host to backup data from
18 janv. 2023 08:12:13 - Info bpbrm (pid=332147) reading file list for client
18 janv. 2023 08:12:13 - Info bpbrm (pid=332147) accelerator enabled
18 janv. 2023 08:12:13 - Info bpbrm (pid=332147) There is no complete backup image match with track journal, a regular full backup will be performed.
18 janv. 2023 08:12:13 - Info nbjm (pid=100405) starting backup job (jobid=813988) for client smallsafe-svr01, policy MKP-VM-SAFE, schedule full
18 janv. 2023 08:12:13 - estimated 0 kbytes needed
18 janv. 2023 08:12:13 - Info nbjm (pid=100405) started backup (backupid=smallsafe-svr01_1674025933) job for client smallsafe-svr01, policy MKP-VM-SAFE, schedule full on storage unit stu_disk_cmmkp-nba-media01 using backup host cmmkp-nba-media01
18 janv. 2023 08:12:13 - started process bpbrm (pid=332147)
18 janv. 2023 08:12:13 - connecting
18 janv. 2023 08:12:14 - Info bpbrm (pid=332147) starting bpbkar on client
18 janv. 2023 08:12:14 - Info bpbkar (pid=332240) Backup started
18 janv. 2023 08:12:14 - Info bpbrm (pid=332147) bptm pid: 332255
18 janv. 2023 08:12:14 - Info bptm (pid=332255) start
18 janv. 2023 08:12:14 - Info bptm (pid=332255) using 262144 data buffer size
18 janv. 2023 08:12:14 - Info bptm (pid=332255) using 30 data buffers
18 janv. 2023 08:12:14 - connected; connect time: 0:00:00
18 janv. 2023 08:12:15 - Info bptm (pid=332255) start backup
18 janv. 2023 08:12:16 - Info bpbkar (pid=332240) INF - Backing up vCenter server vcenter67-mkp.adcm.orangecm, ESX host esxib1-hpe-mkp-svr04.adcm.orangecm, BIOS UUID 423ca1b4-0631-6dbe-61d9-bad9882d3be7, Instance UUID 503c318d-0c6a-55e5-712c-9e41446e7c9f, Display Name smallsafe-svr01, Hostname 172.26.60.19
18 janv. 2023 08:12:17 - begin writing
18 janv. 2023 08:16:50 - Critical bpbrm (pid=332147) from client smallsafe-svr01: FTL - cleanup() failed, status 6
18 janv. 2023 08:16:52 - Error bptm (pid=332255) media manager terminated by parent process
18 janv. 2023 08:16:57 - Info cmmkp-nba-media01 (pid=332255) StorageServer=PureDisk:cmmkp-nba-media01; Report=PDDO Stats (multi-threaded stream used) for (cmmkp-nba-media01): scanned: 2 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled, where dedup space saving:100.0%, compression space saving:0.0%
18 janv. 2023 08:16:57 - Critical bpbrm (pid=332147) unexpected termination of client smallsafe-svr01
18 janv. 2023 08:16:57 - Info bpbkar (pid=0) done. status: 6: the backup failed to back up the requested files
18 janv. 2023 08:16:57 - end writing; write time: 0:04:40
User backup failed  (6)

  • nzog86's avatar
    nzog86
    Level 3
    2 years ago

    VxMS logs

    01/18/2023 09:27:54 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <ERROR> : Initialize: Invalid superblock header
    01/18/2023 09:27:54 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <ERROR> : Initialize: Invalid superblock header
    01/18/2023 09:27:54 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <ERROR> : Initialize: Invalid superblock header

    01/18/2023 09:27:54 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <ERROR> : Initialize: Invalid superblock header
    01/18/2023 09:27:54 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <ERROR> : Initialize: Invalid superblock header
    01/18/2023 09:27:54 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <ERROR> : Initialize: Invalid superblock header
    01/18/2023 09:27:54 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <ERROR> : Initialize: Invalid superblock header
    01/18/2023 09:27:54 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <ERROR> : Initialize: Invalid superblock header
    01/18/2023 09:27:54 : vdGetMetaData:VixInterface.cpp:1086 <ERROR> : Error 16052 in reading metadata for the virtual disk
    01/18/2023 09:27:54 : getMetaData:VixFile.h:434 <ERROR> : g_vixInterface->vdGetMetaData returned error 6

    • davidmoline's avatar
      davidmoline
      Level 6
      2 years ago

      Hi nzog86 

      What is the OS of the VM and what file system type of the VM being backed up. Have you checked that it is supported by granualr recovery? 

      For instance btrfs is not supported. 

      To resolve if this is the case run the policy with these VM optimisations unchecked:

      1. File Level Recovery,
      2. Exclude Swap and Paging Files
      3. Exclude Deleted Blocks

      Cheers
      David

  • AlexeyF's avatar
    AlexeyF
    Level 4
    2 years ago

    Hi 

    the following fix proposed by Veritas support has worked in my case.

    (I don't know though what was the error in the VxMS logs)

     

    FIX:

    In the datastore where the machine resides there is a small file:

    <VM_HOST_NAME>.vmdk ' ("Disk DescriptorFile")

     

    Your VMware administrator or VMware support engineer can look for the following and delete the affected line, as shown in the examples below.

     

    Access the ESX using SSH so you can review the small .vmdk file. (This file doesn't show up when using vCenter to browse the datastore)

    Use "cat" to see the contents of the file.

    In it you will see a few sections:

    "#Disk DescriptorFile"

    "# Extent description"

    "The Disk Data Base"

    "#DDB"

     

    Under #DDB, you should see that there is a line where you are missing a value.

    ddb.virtualHWVersion = "4"

    ddb.comment = ""

     

    Deleting the (ddb.comment="") line will fix the issue.