Forum Discussion

msandrosov59's avatar
msandrosov59
Level 3
12 days ago

Problems with backup VM

Hi!

We have NetBackup 7.6.1.1. The specialists reassembled the VM VMware vCenter Server 6.0.0 as a result of the crash of the latter.

To work with NetBackup, I created an account in VMware and gave it Administrators rights in vCenter and local administrators rights.

I made the appropriate settings in NetBackup.

However, the jobs that previously worked successfully now end with an error.:

the backup failed to back up the requested files (6)

 

When completing tasks, I observe that the task of creating a snapshot is being started. I see that a snapshot is being created. But then an error is issued. I see it in the backup task log:

Error bpbrm(pid=6624) from client VM name: ERR - Error opening the snapshot disks using given transport mode: san:hotadd:nbd:nbdssl Status 23

the backup failed to back up the requested files (6)

 

I tried with other modes of transport, but I get the same error.:

Error bpbrm(pid=9256) from client VM name: ERR - Error opening the snapshot disks using given transport mode: nbd:san:hotadd:nbdssl Status 23

Error bpbrm(pid=7304) from client VM name: ERR - Error opening the snapshot disks using given transport mode: hotadd:nbd:san:nbdssl Status 23

 

What is the reason for the error? What am I missing?

 

 

18 Replies

  • kiyan's avatar
    kiyan
    Level 6
    1 day ago

    Hi,
    sorry for my late reply,
    it seems that for backup using Vcenter

    it is not looking for correct name, 902 should be used with esxi server not the Vcenter name
    I think this could be a name/IP resolution issue,confirm you can reach from netbackup to Vcenter by IP/Name, check the IP and name for vcenter and ESXI, are all of them available in DNS (or host file).
    somehow the netbackup is not able to get the esxi name

    • msandrosov59's avatar
      msandrosov59
      Level 3
      8 hours ago

      I think I've found the reason.

       

      NetBackup is functioning correctly, the problem is on the side of corrupted files on the ESXi datacenters.

       

      Status 23 - indicates corrupted binary files as one of the possible causes of this error.

      at least one corrupt on disk lock was detected on volume Other regions of the volume might be damaged too

       

       

       

  • kiyan's avatar
    kiyan
    Level 6
    6 days ago

    Hi,
    somehow , it is not reaching the host authentication at all.
    the vcenter version before it was exactly same version ?
    when you are running the backup from esxi , can you enable the log ?
    have you tried below article 
    VMware Backup fails with status 6 and 23.
    have you tried to remove the vmware/with ESXI from netbackup and add it again ?
    I think it will keep a record in emm database as well (nbemmcmd -listhosts -verbose) try to remove it from there as well, close your netbackup master/media services , 
    remove the cache using below command
    bpclntcmd -clear_host_cache 
    and start the services again, try to add one of esxi , try to take a backup of it .
    please share the telnet from master and media to esxi host (on port 443 and 902) and from esxi host to master (port 443) and port 902 to media server.

    • msandrosov59's avatar
      msandrosov59
      Level 3
      5 days ago

      Hi!

      I remove vcenter from Credentials Virtual Machne Server.

      Remove files from C:\Windows\Temp\vmware-System.

      Remove the cache using command:

      bpclntcmd -clear_host_cache

      Adding Vcenter to Credentials Virtual Machine Servers.

      Completing the task causes the same error.

      Running the backup from esxi with enable the log. Logs placed on OneDrive:

      OneDrive Logs

      Telnet from Netbackup to ESXI on port 443:

      Telnet fron Netbackup to ESXI on port 902:

      Unfortunately, I don't have access to the host's ESXI CLI.

       

       

  • kiyan's avatar
    kiyan
    Level 6
    7 days ago

    please enable the log ( I have provided you link on top) and run the backup and upload it here.

    • msandrosov59's avatar
      msandrosov59
      Level 3
      6 days ago

      I do not know how to attach these files here. Therefore, I created a link to the file in OneDrive.

      OneDrive

  • kiyan's avatar
    kiyan
    Level 6
    8 days ago

    in your policy , change the "primary VM identifier" to display name instead of hostname.
    and try that.
    did you do a test to take backup of an ESXI instead of VCENTER?did it work?

    • msandrosov59's avatar
      msandrosov59
      Level 3
      8 days ago

      Test to take backup of an ESXI instead of VCenter resulted in same error.

       

  • kiyan's avatar
    kiyan
    Level 6
    9 days ago

    find the details in below link:

    Configuring VxMS logging | NetBackup logging for VMware | Troubleshooting VMware operations | NetBackup™ for VMware Administrator's Guide | Veritas™
    one more thing,have you tried to add one of ESXI servers to netbackup, and add the root of the ESXI to netbackup and try to take backup from that esxi?like one VM only?
    can you share the screenshot of your vmware policy?specifically the VMware tab, what is the configuration there?

  • kiyan's avatar
    kiyan
    Level 6
    9 days ago

    Hi, Kindly enable the Verbosity of 5 and make sure the below log folder is available
    netbackup/logs/vxms
    and upload this log file once it has recorded the failure.

    • msandrosov59's avatar
      msandrosov59
      Level 3
      9 days ago

      Hi!

      I don't know if I did the right thing.

      I set the parameter Verbosity to 5. In Backup, Archive and Restore snap-in in File > NetBackupClient Properties... setup this value:

      After that, I started the task from the task list.

      I see several short files in the folder Program Files\Veritas\NetBackup\logs\vxms

      I do not know how to attach these files here. Therefore, I created a link to the file in OneDrive.

      VxMS

  • kiyan's avatar
    kiyan
    Level 6
    10 days ago

    Hi,
    if all servers (netbackup master, Media,Vcenter,ESXI servers) are on same network, then it is not a port issue,confirm below please:
    have you tried to confirm that you are able to reach ESXI servers, from Netbackup vmware host server (Netbackup media server, responsible for taking backup) by name and IP address ?
    is it possible to provide Vcenter administrator credentials (yes, the local administrator of Vcenter) to the netbackup and try to take backup?dont use the account you have created in Vcenter?
    if above did not work, enable log and take a backup , let it fail and upload the log here.

    • msandrosov59's avatar
      msandrosov59
      Level 3
      9 days ago

      Hi!

       

      Netbackup - is one server Master & Media. Yes, allservers on same nwetwork.

      Yes I can to reach ESXI servers by name & IP address.

      I have granted rights to Vcenter Administrator credentials. As you requested.

      The result is the same.

       

      Log of snapshot:

      07.02.2026 23:21:33 - Info nbjm(pid=3480) starting backup job (jobid=569857) for client imd3.msa.com, policy IMD3, schedule Full

      07.02.2026 23:21:33 - Info nbjm(pid=3480) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=569857, request id:{9349017B-63B5-4718-92DE-C99C2F69EDDE})

      07.02.2026 23:21:33 - requesting resource Any

      07.02.2026 23:21:33 - requesting resource srv-nbu01.main.msa.com.NBU_CLIENT.MAXJOBS.imd3.msa.com

      07.02.2026 23:21:33 - requesting resource srv-nbu01.main.msa.com.NBU_POLICY.MAXJOBS.IMD3

      07.02.2026 23:21:36 - granted resource srv-nbu01.main.msa.com.NBU_CLIENT.MAXJOBS.imd3.msa.com

      07.02.2026 23:21:36 - granted resource srv-nbu01.main.msa.com.NBU_POLICY.MAXJOBS.IMD3

      07.02.2026 23:21:36 - granted resource MediaID=@aaaak;Path=E:\;MediaServer=srv-nbu01.main.msa.com

      07.02.2026 23:21:36 - granted resource Disk01

      07.02.2026 23:21:36 - estimated 0 Kbytes needed

      07.02.2026 23:21:36 - begin Parent Job

      07.02.2026 23:21:36 - begin VMware, Start Notify Script

      07.02.2026 23:21:36 - started

      07.02.2026 23:21:37 - Info RUNCMD(pid=8504) started

      07.02.2026 23:21:38 - Info RUNCMD(pid=8504) exiting with status: 0

      Status 0

      07.02.2026 23:21:38 - end VMware, Start Notify Script; elapsed time: 0:00:02

      07.02.2026 23:21:38 - begin VMware, Step By Condition

      Status 0

      07.02.2026 23:21:38 - end VMware, Step By Condition; elapsed time: 0:00:00

      07.02.2026 23:21:38 - begin VMware, Read File List

      Status 0

      07.02.2026 23:21:38 - end VMware, Read File List; elapsed time: 0:00:00

      07.02.2026 23:21:38 - begin VMware, Create Snapshot

      07.02.2026 23:21:39 - Info bpbrm(pid=6760) imd3.msa.com is the host to backup data from

      07.02.2026 23:21:39 - Info bpbrm(pid=6760) reading file list for client

      07.02.2026 23:21:39 - Info bpbrm(pid=6760) start bpfis on client

      07.02.2026 23:21:39 - started process bpbrm (6760)

      07.02.2026 23:21:41 - Info bpbrm(pid=6760) Starting create snapshot processing

      07.02.2026 23:21:43 - Info bpfis(pid=8244) Backup started

      07.02.2026 23:21:49 - snapshot backup of client imd3.msa.com using method VMware_v2

      07.02.2026 23:32:11 - end VMware, Create Snapshot; elapsed time: 0:10:33

      07.02.2026 23:32:11 - Info bpfis(pid=8244) done. status: 0

      07.02.2026 23:32:11 - Info bpfis(pid=8244) done. status: 0: the requested operation was successfully completed

      07.02.2026 23:32:11 - end writing

      Status 0

      07.02.2026 23:32:11 - end Parent Job; elapsed time: 0:10:35

      07.02.2026 23:32:11 - Info nbjm(pid=3480) snapshotid=imd3.msa.com_1770495696

      07.02.2026 23:32:11 - begin VMware, Policy Execution Manager Preprocessed

      07.02.2026 23:32:43 - end VMware, Policy Execution Manager Preprocessed; elapsed time: 0:00:32

      07.02.2026 23:32:43 - begin VMware, Stop On Error

      Status 0

      07.02.2026 23:32:43 - end VMware, Stop On Error; elapsed time: 0:00:00

      07.02.2026 23:32:43 - begin VMware, Delete Snapshot

      07.02.2026 23:32:43 - started process bpbrm (4492)

      07.02.2026 23:32:44 - Info bpbrm(pid=4492) Starting delete snapshot processing

      Status 6

      07.02.2026 23:32:45 - Info bpfis(pid=1964) Backup started

      07.02.2026 23:32:46 - Info bpbrm(pid=4492) INF - vmwareLogger: RegisterExtensionAPI: SYM_VMC_ERROR: SOAP_ERROR

      07.02.2026 23:32:46 - Info bpbrm(pid=4492) INF - vmwareLogger: SOAP 1.1 fault: "":ServerFaultCode [no subcode]

      07.02.2026 23:42:58 - Critical bpbrm(pid=4492) from client imd3.msa.com: VMware_thaw: Unable to unlock virtual machine: imd3.msa.com.

      07.02.2026 23:42:58 - Critical bpbrm(pid=4492) from client imd3.msa.com: vfm_thaw: method: VMware_v2, type: FIM, function: VMware_v2_thaw

      07.02.2026 23:42:58 - Critical bpbrm(pid=4492) from client imd3.msa.com: snapshot delete returned status 1

      07.02.2026 23:42:58 - Info bpfis(pid=1964) done. status: 1

      07.02.2026 23:42:58 - end VMware, Delete Snapshot; elapsed time: 0:10:15

      07.02.2026 23:42:58 - Info bpfis(pid=1964) done. status: 1: the requested operation was partially successful

      07.02.2026 23:42:58 - end writing

      Status 1

      07.02.2026 23:42:58 - end operation

      07.02.2026 23:42:58 - begin VMware, End Notify Script

      07.02.2026 23:42:59 - Info RUNCMD(pid=2808) started

      07.02.2026 23:43:00 - Info RUNCMD(pid=2808) exiting with status: 0

      Status 0

      07.02.2026 23:43:00 - end VMware, End Notify Script; elapsed time: 0:00:02

      Status 6

      07.02.2026 23:43:00 - end operation

      the backup failed to back up the requested files (6)

       

      Log of Backup:

      07.02.2026 23:32:11 - Info nbjm(pid=3480) starting backup job (jobid=569860) for client imd3.msa.com, policy IMD3, schedule Full

      07.02.2026 23:32:11 - estimated 0 Kbytes needed

      07.02.2026 23:32:11 - Info nbjm(pid=3480) started backup (backupid=imd3.msa.com_1770496331) job for client imd3.msa.com, policy IMD3, schedule Full on storage unit Disk01 using backup host srv-nbu01.main.msa.com

      07.02.2026 23:32:12 - started process bpbrm (4436)

      07.02.2026 23:32:12 - Info bpbrm(pid=4436) imd3.msa.com is the host to backup data from

      07.02.2026 23:32:12 - Info bpbrm(pid=4436) reading file list for client

      07.02.2026 23:32:12 - connecting

      07.02.2026 23:32:13 - Info bpbrm(pid=4436) starting bpbkar32 on client

      07.02.2026 23:32:13 - connected; connect time: 0:00:01

      07.02.2026 23:32:14 - Info bpbkar32(pid=6600) Backup started

      07.02.2026 23:32:14 - Info bpbkar32(pid=6600) archive bit processing:<enabled>

      07.02.2026 23:32:14 - Info bptm(pid=1664) start

      07.02.2026 23:32:14 - Info bptm(pid=1664) using 262144 data buffer size

      07.02.2026 23:32:14 - Info bptm(pid=1664) setting receive network buffer to 1049600 bytes

      07.02.2026 23:32:14 - Info bptm(pid=1664) using 30 data buffers

      07.02.2026 23:32:14 - Info bptm(pid=1664) start backup

      07.02.2026 23:32:15 - begin writing

      07.02.2026 23:32:36 - Error bpbrm(pid=4436) from client imd3.msa.com: ERR - Error opening the snapshot disks using given transport mode: san:nbd:hotadd:nbdssl Status 23

      07.02.2026 23:32:37 - Info bpbkar32(pid=6600) bpbkar waited 0 times for empty buffer, delayed 0 times.

      07.02.2026 23:32:42 - Error bpbrm(pid=4436) could not send server status message

      07.02.2026 23:32:42 - Critical bpbrm(pid=4436) unexpected termination of client imd3.msa.com

      07.02.2026 23:32:42 - Error bpbrm(pid=4436) cannot send mail to 8819@msa.com

      07.02.2026 23:32:42 - Info bpbkar32(pid=0) done. status: 6: the backup failed to back up the requested files

      07.02.2026 23:32:42 - end writing; write time: 0:00:27

      the backup failed to back up the requested files (6)

       

  • kiyan's avatar
    kiyan
    Level 6
    12 days ago

    Hi, 
    one tip, is MASTER , MEDIA,VCENTER, ESXI are able to see each other ?are you able to reach them by IP And by Name?90 % percentage of the issue will be in name/IP resolution.
    as it is mentioned on top, as far as the snapshot is being created, that means the master, is able to reach Vcenter, so you should focus on Media and ESXI,
    is port 902 open between ESXI and Media server?are they able to resolve IP/name of each other?

     

    • msandrosov59's avatar
      msandrosov59
      Level 3
      12 days ago

      I checked the availability from the netbackup server on port 443 of Vcenter using telnet. And on esxi ports 443 and 902.

      All attempts were successful.

      The servers are on the same network. The Netbackup server has an IP address of 10.104.4.116. The vCenter server has an IP address of 10.104.4.20. Firewalls on both servers are disabled.

  • StefanosM's avatar
    StefanosM
    Level 6
    12 days ago

    for beginning stay with nbd transport mode. (network mode)
    You have to open from master and media servers the 443 port to the vcenter and 443 and 902 port to the ESXis 

    • msandrosov59's avatar
      msandrosov59
      Level 3
      12 days ago

      I checked the availability from the netbackup server on port 443 of Vcenter using telnet. And on esxi ports 443 and 902.

      All attempts were successful.

      The servers are on the same network. The Netbackup server has an IP address of 10.104.4.116. The vCenter server has an IP address of 10.104.4.20. Firewalls on both servers are disabled.