Forum Discussion

Mohamedkhattab's avatar
Mohamedkhattab
Level 4
11 years ago

VM backup alwayes finished with "the backup failed to back up the requested files(6)" status

Hi all,

I still can't take vm backup for some client inside vshpere 5.5,when job start i recieved the below error's

 

6/7/2014 5:00:48 PM - Error bpbrm(pid=33007) from client XXXXX: ERR - Error opening the snapshot disks using given transport mode: Status 23
6/7/2014 5:00:49 PM - Critical bpbrm(pid=33007) from client XXXXX: FTL - cleanup() failed, status 6   

6/7/2014 5:02:00 PM - Info bpbkar(pid=0) done. status: 6: the backup failed to back up the requested files

 

i have a full admin permission in the vcenter,also i upgraded the master server to 7.6.0.2 and  appliance to 2.6.0.2

so please advice.

 

7.6
Backup and Recovery
NetBackup
Windows Server (2003-2008)
  • Anonymous's avatar
    Anonymous
    11 years ago

    Check in vSphere against your hosts that they licensed for vStorage API feature.

    Crucial that the vsphere permission is added at the vcenter server object top level and not at any other object level and set to Propogate to children.

    Here's another gotcha. You might have you permission inserted at a lower level object for No Access - overriding the top level.

    Why? This is actually handy in a vSphere environment with global datacenters but may be backing up using different products in different geographies relative to vStorage. So add the NetBackup for Vmware credentials user as No Access on datacenters you dont need access to enumerate for your VM backups, and you will only see the VM's you want to backup and not see others in the NetBackup VM selection dialog of the VMware policy.

  • Mohamedkhattab's avatar
    Mohamedkhattab
    Level 4
    11 years ago

    I removed the application Consistent option,also note the shpsymbk02 is my appliance.

    i checked the VMware guide and followed all the configuration steps but without success.

    any other solution to fix the issue or not?

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    As per my post above:

    The next log that we will need is vxms log.

    See in Troubleshooting chapter of NBU for VMware manual (chapter 14):
    To configure VxMS logging on a Linux backup host.

    Please copy logs to .txt files (e.g. vxms.txt) and upload as File attachments.

    Please also share screemshots of SLP config.

  • Anonymous's avatar
    Anonymous
    11 years ago

    Check in vSphere against your hosts that they licensed for vStorage API feature.

    Crucial that the vsphere permission is added at the vcenter server object top level and not at any other object level and set to Propogate to children.

    Here's another gotcha. You might have you permission inserted at a lower level object for No Access - overriding the top level.

    Why? This is actually handy in a vSphere environment with global datacenters but may be backing up using different products in different geographies relative to vStorage. So add the NetBackup for Vmware credentials user as No Access on datacenters you dont need access to enumerate for your VM backups, and you will only see the VM's you want to backup and not see others in the NetBackup VM selection dialog of the VMware policy.