Forum Discussion

h-mazeh's avatar
h-mazeh
Level 3
4 years ago

Netbackup appliance vmware vsan

Hello.

I added my vsan vcenter to my vmware access hosts and it synced.
When trying to back up any vm, snapshot takes a long time and stops with below error.
Can you help?

Jul 24, 2020 1:36:11 AM - Info bpbrm (pid=288024) Starting delete snapshot processing
Jul 24, 2020 1:36:11 AM - Info bpfis (pid=288034) Backup started
Jul 24, 2020 1:36:11 AM - Warning bpbrm (pid=288024) from client VM-01-IVR-APP1-VAS: cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.VM-01-IVR-APP1-VAS_1595542170.1.0
Jul 24, 2020 1:36:11 AM - Info bpfis (pid=288034) done. status: 4207
Jul 24, 2020 1:36:11 AM - end VMware: Delete Snapshot; elapsed time 0:00:01
Jul 24, 2020 1:36:11 AM - Info bpfis (pid=288034) done. status: 4207: Could not fetch snapshot metadata or state files
Jul 24, 2020 1:36:11 AM - end writing
Operation Status: 4207
Operation Status: 156
Snapshot error encountered  (156)
  • vSAN needs an NBD/NBDSSL/HotAdd transport make sure you did not select SAN: there is no SAN in vSAN.

    For NBD (or SSL) you need specific port access as specified in the NBU for VMware Admin Guide.

    For Hot Add, you need to have a VM with Media Server/NBU Client that acts as a backup host which has access to the same datastore so they can mount the snapshot disks.

  • Thanks for your answer.

    The VM backup host helped, but there was another cause.

    Once VSAN is backed up, you need to uncheck CBT options from vmware tab in policy.

3 Replies

  • vSAN needs an NBD/NBDSSL/HotAdd transport make sure you did not select SAN: there is no SAN in vSAN.

    For NBD (or SSL) you need specific port access as specified in the NBU for VMware Admin Guide.

    For Hot Add, you need to have a VM with Media Server/NBU Client that acts as a backup host which has access to the same datastore so they can mount the snapshot disks.

    • h-mazeh's avatar
      h-mazeh
      Level 3

      Thanks for your answer.

      The VM backup host helped, but there was another cause.

      Once VSAN is backed up, you need to uncheck CBT options from vmware tab in policy.

  • we need to look into the bpfis logs with pid=288034, and also do you see any errors in vCenter console for this specfic VM tasks and events?

    does this VM ever get successfully backup?