cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup tried to delete the same snapshot twice

Bogdanl
Level 4

Hello,

I encounter a issue during the backup of one of my VMs which ends in partial because NBU deletes twice the generated snapshot; the first one works, the second one fails.

The error reported by the vcenter would be "normal" in the sense that netbackup tries to delete the snapshot twice, the first time succeeds, the second time fails because the snapshot no longer exists. I just manually validate that I can make a snapshot and delete it on this VM without error (and without the attempt does generate two tests). The behavior is different on other VMs, netbackup does not try to delete the snapshot twice

Any advice will be apreciated

 Failed to delete snapreplicapair file [C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.E00001.srv.entreprise.int_1543444207.1.0.snapreplicapair] return value[-1]                        error [2] [No such file or directory]
23:33:34.738 [16748.15952] <4> keep_alive_and_snapshot_control: Starting keep alive thread.
23:33:34.738 [16748.15952] <2> deleteReference: reference not found in the list
23:33:34.738 [16748.15952] <4> unlockSnapshot: Delete reference: status [-4]
23:33:34.738 [16748.15952] <2> writeSnapshotLockFile: Writing type[2] refcount[0]
23:33:34.738 [16748.15952] <2> writeSnapshotLockFile: Writing Flags [0] [0]
23:33:34.738 [16748.15952] <2> writeSnapshotLockFile: Writing Last addReffernt Time [Thu Jan 01 01:00:00 1970 ]
23:33:34.738 [16748.15952] <2> writeSnapshotLockFile: Writing Last Hostname []
23:33:34.848 [16748.15952] <2> getFileName: FileName is [C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\E00001.srv.entreprise.int_1543444207_copy1.lock]
23:33:34.848 [16748.15952] <2> unlockSnapshot: file[C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\E00001.srv.entreprise.int_1543444207_copy1.lock] : zero reference count
23:33:34.848 [16748.15952] <4> unlockSnapshot: Released snapshot lock: status [0]
23:33:34.848 [16748.15952] <4> do_post_processing: Deleting snapshot lock files from client for id [E00001.srv.entreprise.int_1543444207] and copy_number [1]
23:33:34.848 [16748.15952] <2> getFileName: FileName is [C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\E00001.srv.entreprise.int_1543444207_copy1.lock]
23:33:34.848 [16748.15952] <2> deleteSnapshotLockFile: Renamed lock file from [C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\E00001.srv.entreprise.int_1543444207_copy1.lock] to [\sgbc.] for deletion
23:33:34.848 [16748.15952] <2> deleteSnapshotLockFile: File[\sgbc.] delete: status[0]

Thank you

7 REPLIES 7

Lowell_Palecek
Level 6
Employee

I'm not sure you're showing the relevant log snippet. This looks like a portion of the bpfis log, correct? The files in the fi_cntl folder are used for managing a snapshot across processes. They are not the snapshot itself. I don't think a failure here causes a non-zero backup status.

Please show the "logparams" and exit status lines from the log for this pid and any other pid that contains the snapshot timestamp 1543444207. (E00001.srv.entreprise.int_1543444207 is the "fis id" in the same client_timestamp as a backup id.)

Hello Lowell,

Thank you for your reply, attached are the complete bpfis logs

There is only one deletion of this snapshot:

>23:33:34.598 [16748.15952] <2> onlfi_vfms_logf: INF - vfm_thaw: delete snapshot ...
...
>23:33:34.738 [16748.15952] <4> onlfi_thaw: INF - do_thaw return value: 0

Moreover, there is no error here. Both the "bpfis create" and "bpfis delete" processes for this snapshot finished with status 0:

>23:31:23.234 [7912.15840] <4> bpfis Exit: INF - EXIT STATUS 0: the requested operation was successfully completed
>23:33:35.269 [16748.15952] <4> bpfis Exit: INF - EXIT STATUS 0: the requested operation was successfully completed

What failure are you seeing and where are you seeing it?

Hello,

Please see below

 

8 déc. 2018 19:30:55 - Info bpbrm (pid=8320) INF - vmwareLogger: WaitForTaskComplete: The object 'vim.vm.Snapshot:snapshot-43251' has already been deleted or has not been completely created <31>8 déc. 2018 19:30:55 - Info bpbrm (pid=8320) INF - vmwareLogger: WaitForTaskComplete: SYM_VMC_ERROR:  TASK_REACHED_ERROR_STATE8 déc. 2018 19:30:55 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  TASK_REACHED_ERROR_STATE8 déc. 2018 19:30:56 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF - vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns="urn:vim25" xsi:type="ManagedObjectNotFound"><obj type="VirtualMachineSnapshot"></obj></ManagedObjectNotFoundFault>8 déc. 2018 19:30:57 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF - vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns="urn:vim25" xsi:type="ManagedObjectNotFound"><obj type="VirtualMachineSnapshot"></obj></ManagedObjectNotFoundFault>8 déc. 2018 19:30:58 - Critical bpbrm (pid=8320) from client brs140_UOB_e06173: do_thaw: Unable to remove virtual machine snapshot, status=6 (SYM_VMC_SOAP_ERROR). Error Details: [The object 'vim.vm.Snapshot:' has already been deleted or has not been completely created].8 déc. 2018 19:31:05 - Critical bpbrm (pid=8320) from client brs140_UOB_e06173: vfm_thaw: method: VMware_v2, type: FIM, function: VMware_v2_thaw8 déc. 2018 19:31:05 - Critical bpbrm (pid=8320) from client brs140_UOB_e06173: snapshot delete returned status 18 déc. 2018 19:31:05 - Info bpfis (pid=3724) done. status: 18 déc. 2018 19:31:05 - end VMware: Delete Snapshot; elapsed time 0:02:488 déc. 2018 19:31:05 - Info bpfis (pid=3724) done. status: 1: the requested operation was partially successful

 

 

8 déc. 2018 18:55:09 - Info nbjm (pid=6212) starting backup job (jobid=96463) for client brs140_UOB_e06173, policy ENT_PROD_BOOTDISK, schedule Full8 déc. 2018 18:55:09 - Info nbjm (pid=6212) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=96463, request id:{D78184C3-E36B-410E-BA8C-F2BC652899EF})8 déc. 2018 18:55:09 - requesting resource  Disk_HEBDO8 déc. 2018 18:55:09 - requesting resource  e00001.srv.entreprise.int.NBU_CLIENT.MAXJOBS.brs140_UOB_e061738 déc. 2018 18:55:09 - requesting resource  e00001.srv.entreprise.int.NBU_POLICY.MAXJOBS.ENT_PROD_BOOTDISK8 déc. 2018 18:55:09 - granted resource  e00001.srv.entreprise.int.NBU_CLIENT.MAXJOBS.brs140_UOB_e061738 déc. 2018 18:55:09 - granted resource  e00001.srv.entreprise.int.NBU_POLICY.MAXJOBS.ENT_PROD_BOOTDISK8 déc. 2018 18:55:09 - granted resource ....8 déc. 2018 18:55:09 - granted resource  Disk_HEBDO8 déc. 2018 18:55:38 - estimated 31043986 kbytes needed8 déc. 2018 18:55:38 - begin Parent Job8 déc. 2018 18:55:38 - begin VMware: Start Notify Script8 déc. 2018 18:55:43 - Info RUNCMD (pid=15540) started8 déc. 2018 18:55:43 - Info RUNCMD (pid=15540) exiting with status: 0Operation Status: 08 déc. 2018 18:55:43 - end VMware: Start Notify Script; elapsed time 0:00:058 déc. 2018 18:55:43 - begin VMware: Step By ConditionOperation Status: 08 déc. 2018 18:55:43 - end VMware: Step By Condition; elapsed time 0:00:008 déc. 2018 18:55:43 - begin VMware: Read File ListOperation Status: 08 déc. 2018 18:55:43 - end VMware: Read File List; elapsed time 0:00:008 déc. 2018 18:55:43 - begin VMware: Create Snapshot8 déc. 2018 18:56:07 - started process bpbrm (pid=216)8 déc. 2018 18:56:07 - Info bpbrm (pid=216) brs140_UOB_e06173 is the host to backup data from8 déc. 2018 18:56:07 - Info bpbrm (pid=216) reading file list for client8 déc. 2018 18:56:07 - Info bpbrm (pid=216) start bpfis on client8 déc. 2018 18:56:08 - Info bpbrm (pid=216) Starting create snapshot processing8 déc. 2018 18:56:08 - Info bpfis (pid=5276) Backup started8 déc. 2018 18:56:13 - snapshot backup of client brs140_UOB_e06173 using method VMware_v28 déc. 2018 18:56:19 - Info bpbrm (pid=216) INF - vmwareLogger:  Creating snapshot for vCenter server 10.209.107.25, ESX host epb666vesx25.brs666.bcrs.fr, BIOS UUID 4221d6e3-3298-1346-2cb1-0f3ddaf49dca, Instance UUID 50213860-9a8f-7c41-0c7e-8f8aa355441d, Display Name brs140_UOB_e06173, Hostname e06173.srv.entreprise.int 8 déc. 2018 18:56:36 - end VMware: Create Snapshot; elapsed time 0:00:538 déc. 2018 18:56:36 - Info bpfis (pid=5276) done. status: 08 déc. 2018 18:56:36 - Info bpfis (pid=5276) done. status: 0: the requested operation was successfully completed8 déc. 2018 18:56:36 - end writingOperation Status: 08 déc. 2018 18:56:36 - end Parent Job; elapsed time 0:00:588 déc. 2018 18:56:36 - Info nbjm (pid=6212) snapshotid=brs140_UOB_e06173_15442917188 déc. 2018 18:56:36 - begin VMware: Policy Execution Manager PreprocessedOperation Status: 08 déc. 2018 19:28:12 - end VMware: Policy Execution Manager Preprocessed; elapsed time 0:31:368 déc. 2018 19:28:12 - begin VMware: Validate ImageOperation Status: 08 déc. 2018 19:28:17 - end VMware: Validate Image; elapsed time 0:00:058 déc. 2018 19:28:17 - begin VMware: Delete Snapshot8 déc. 2018 19:28:41 - started process bpbrm (pid=8320)8 déc. 2018 19:28:42 - Info bpbrm (pid=8320) Starting delete snapshot processing8 déc. 2018 19:28:42 - Info bpfis (pid=3724) Backup started8 déc. 2018 19:29:43 - Info bpbrm (pid=8320) INF - vmwareLogger: Error 504 fault: SOAP-ENV:Server [no subcode]8 déc. 2018 19:29:43 - Info bpbrm (pid=8320) INF - vmwareLogger: WaitForTaskComplete: SYM_VMC_ERROR:  SOAP_ERROR8 déc. 2018 19:29:43 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  SOAP_ERROR8 déc. 2018 19:30:34 - Info bpbrm (pid=8320) INF - vmwareLogger: Error 504 fault: SOAP-ENV:Server [no subcode]8 déc. 2018 19:30:34 - Info bpbrm (pid=8320) INF - vmwareLogger: WaitForTaskComplete: SYM_VMC_ERROR:  SOAP_ERROR8 déc. 2018 19:30:34 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  SOAP_ERROR8 déc. 2018 19:30:55 - Info bpbrm (pid=8320) INF - vmwareLogger: WaitForTaskComplete: The object 'vim.vm.Snapshot:snapshot-43251' has already been deleted or has not been completely created <31>8 déc. 2018 19:30:55 - Info bpbrm (pid=8320) INF - vmwareLogger: WaitForTaskComplete: SYM_VMC_ERROR:  TASK_REACHED_ERROR_STATE8 déc. 2018 19:30:55 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  TASK_REACHED_ERROR_STATE8 déc. 2018 19:30:56 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF - vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns="urn:vim25" xsi:type="ManagedObjectNotFound"><obj type="VirtualMachineSnapshot"></obj></ManagedObjectNotFoundFault>8 déc. 2018 19:30:57 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF - vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns="urn:vim25" xsi:type="ManagedObjectNotFound"><obj type="VirtualMachineSnapshot"></obj></ManagedObjectNotFoundFault>8 déc. 2018 19:30:58 - Critical bpbrm (pid=8320) from client brs140_UOB_e06173: do_thaw: Unable to remove virtual machine snapshot, status=6 (SYM_VMC_SOAP_ERROR). Error Details: [The object 'vim.vm.Snapshot:' has already been deleted or has not been completely created].8 déc. 2018 19:31:05 - Critical bpbrm (pid=8320) from client brs140_UOB_e06173: vfm_thaw: method: VMware_v2, type: FIM, function: VMware_v2_thaw8 déc. 2018 19:31:05 - Critical bpbrm (pid=8320) from client brs140_UOB_e06173: snapshot delete returned status 18 déc. 2018 19:31:05 - Info bpfis (pid=3724) done. status: 18 déc. 2018 19:31:05 - end VMware: Delete Snapshot; elapsed time 0:02:488 déc. 2018 19:31:05 - Info bpfis (pid=3724) done. status: 1: the requested operation was partially successful8 déc. 2018 19:31:05 - end writingOperation Status: 18 déc. 2018 19:31:05 - begin VMware: End Notify Script8 déc. 2018 19:31:10 - Info RUNCMD (pid=16100) started8 déc. 2018 19:31:10 - Info RUNCMD (pid=16100) exiting with status: 0Operation Status: 08 déc. 2018 19:31:10 - end VMware: End Notify Script; elapsed time 0:00:05Operation Status: 1The requested operation was partially successful  (1)

The first bpfis logs you provided were from inside the VM. They were for MS-Windows backups of C:\ and D:\.

Your new post is the job details from a VMware backup. To investigate further would require studying verbose bpfis logs from the backup host, and also VMware logs.

Two points about the message "... has already been deleted or has not been completely created."

1. Consider the "or" case. In the message.

2. The message comes from VMware, not NetBackup. I don't know what it means.

I think you need to open a support case for the level of effort that's going to be required to sort out the issues.

FWIW, the following is your post with the missing line breaks added.

8 déc. 2018 18:55:09 - Info nbjm (pid=6212) starting backup job (jobid=96463) for client brs140_UOB_e06173, policy ENT_PROD_BOOTDISK, schedule Full
8 déc. 2018 18:55:09 - Info nbjm (pid=6212) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=96463, request id:{D78184C3-E36B-410E-BA8C-F2BC652899EF})
8 déc. 2018 18:55:09 - requesting resource  Disk_HEBDO
8 déc. 2018 18:55:09 - requesting resource  e00001.srv.entreprise.int.NBU_CLIENT.MAXJOBS.brs140_UOB_e06173
8 déc. 2018 18:55:09 - requesting resource  e00001.srv.entreprise.int.NBU_POLICY.MAXJOBS.ENT_PROD_BOOTDISK
8 déc. 2018 18:55:09 - granted resource  e00001.srv.entreprise.int.NBU_CLIENT.MAXJOBS.brs140_UOB_e06173
8 déc. 2018 18:55:09 - granted resource  e00001.srv.entreprise.int.NBU_POLICY.MAXJOBS.ENT_PROD_BOOTDISK
8 déc. 2018 18:55:09 - granted resource ....
8 déc. 2018 18:55:09 - granted resource  Disk_HEBDO
8 déc. 2018 18:55:38 - estimated 31043986 kbytes needed
8 déc. 2018 18:55:38 - begin Parent Job
8 déc. 2018 18:55:38 - begin VMware: Start Notify Script
8 déc. 2018 18:55:43 - Info RUNCMD (pid=15540) started
8 déc. 2018 18:55:43 - Info RUNCMD (pid=15540) exiting with status: 0Operation Status: 0
8 déc. 2018 18:55:43 - end VMware: Start Notify Script; elapsed time 0:00:05
8 déc. 2018 18:55:43 - begin VMware: Step By ConditionOperation Status: 0
8 déc. 2018 18:55:43 - end VMware: Step By Condition; elapsed time 0:00:00
8 déc. 2018 18:55:43 - begin VMware: Read File ListOperation Status: 0
8 déc. 2018 18:55:43 - end VMware: Read File List; elapsed time 0:00:00
8 déc. 2018 18:55:43 - begin VMware: Create Snapshot
8 déc. 2018 18:56:07 - started process bpbrm (pid=216)
8 déc. 2018 18:56:07 - Info bpbrm (pid=216) brs140_UOB_e06173 is the host to backup data from
8 déc. 2018 18:56:07 - Info bpbrm (pid=216) reading file list for client
8 déc. 2018 18:56:07 - Info bpbrm (pid=216) start bpfis on client
8 déc. 2018 18:56:08 - Info bpbrm (pid=216) Starting create snapshot processing
8 déc. 2018 18:56:08 - Info bpfis (pid=5276) Backup started
8 déc. 2018 18:56:13 - snapshot backup of client brs140_UOB_e06173 using method VMware_v2
8 déc. 2018 18:56:19 - Info bpbrm (pid=216) INF - vmwareLogger:  Creating snapshot for vCenter server 10.209.107.25, ESX host epb666vesx25.brs666.bcrs.fr, BIOS UUID 4221d6e3-3298-1346-2cb1-0f3ddaf49dca, Instance UUID 50213860-9a8f-7c41-0c7e-8f8aa355441d, Display Name brs140_UOB_e06173, Hostname e06173.srv.entreprise.int
8 déc. 2018 18:56:36 - end VMware: Create Snapshot; elapsed time 0:00:53
8 déc. 2018 18:56:36 - Info bpfis (pid=5276) done. status: 0
8 déc. 2018 18:56:36 - Info bpfis (pid=5276) done. status: 0: the requested operation was successfully completed

8 déc. 2018 18:56:36 - end writingOperation Status: 0
8 déc. 2018 18:56:36 - end Parent Job; elapsed time 0:00:58
8 déc. 2018 18:56:36 - Info nbjm (pid=6212) snapshotid=brs140_UOB_e06173_1544291718

8 déc. 2018 18:56:36 - begin VMware: Policy Execution Manager PreprocessedOperation Status: 0
8 déc. 2018 19:28:12 - end VMware: Policy Execution Manager Preprocessed; elapsed time 0:31:36
8 déc. 2018 19:28:12 - begin VMware: Validate ImageOperation Status: 0
8 déc. 2018 19:28:17 - end VMware: Validate Image; elapsed time 0:00:05

8 déc. 2018 19:28:17 - begin VMware: Delete Snapshot

8 déc. 2018 19:28:41 - started process bpbrm (pid=8320)
8 déc. 2018 19:28:42 - Info bpbrm (pid=8320) Starting delete snapshot processing
8 déc. 2018 19:28:42 - Info bpfis (pid=3724) Backup started
8 déc. 2018 19:29:43 - Info bpbrm (pid=8320) INF - vmwareLogger: Error 504 fault: SOAP-ENVSmiley Frustratederver [no subcode]
8 déc. 2018 19:29:43 - Info bpbrm (pid=8320) INF - vmwareLogger: WaitForTaskComplete: SYM_VMC_ERROR:  SOAP_ERROR
8 déc. 2018 19:29:43 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  SOAP_ERROR

8 déc. 2018 19:30:34 - Info bpbrm (pid=8320) INF - vmwareLogger: Error 504 fault: SOAP-ENVSmiley Frustratederver [no subcode]
8 déc. 2018 19:30:34 - Info bpbrm (pid=8320) INF - vmwareLogger: WaitForTaskComplete: SYM_VMC_ERROR:  SOAP_ERROR
8 déc. 2018 19:30:34 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  SOAP_ERROR

8 déc. 2018 19:30:55 - Info bpbrm (pid=8320) INF - vmwareLogger: WaitForTaskComplete: The object 'vim.vm.Snapshot:snapshot-43251' has already been deleted or has not been completely created <31>
8 déc. 2018 19:30:55 - Info bpbrm (pid=8320) INF - vmwareLogger: WaitForTaskComplete: SYM_VMC_ERROR:  TASK_REACHED_ERROR_STATE
8 déc. 2018 19:30:55 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  TASK_REACHED_ERROR_STATE
8 déc. 2018 19:30:56 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF - vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns="urn:vim25" xsi:type="ManagedObjectNotFound"><obj type="VirtualMachineSnapshot"></obj></ManagedObjectNotFoundFault>
8 déc. 2018 19:30:57 - Info bpbrm (pid=8320) INF - vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF - vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns="urn:vim25" xsi:type="ManagedObjectNotFound"><obj type="VirtualMachineSnapshot"></obj></ManagedObjectNotFoundFault>
8 déc. 2018 19:30:58 - Critical bpbrm (pid=8320) from client brs140_UOB_e06173: do_thaw: Unable to remove virtual machine snapshot, status=6 (SYM_VMC_SOAP_ERROR). Error Details: [The object 'vim.vm.Snapshot:' has already been deleted or has not been completely created].
8 déc. 2018 19:31:05 - Critical bpbrm (pid=8320) from client brs140_UOB_e06173: vfm_thaw: method: VMware_v2, type: FIM, function: VMware_v2_thaw
8 déc. 2018 19:31:05 - Critical bpbrm (pid=8320) from client brs140_UOB_e06173: snapshot delete returned status 1

8 déc. 2018 19:31:05 - Info bpfis (pid=3724) done. status: 1

8 déc. 2018 19:31:05 - end VMware: Delete Snapshot; elapsed time 0:02:48
8 déc. 2018 19:31:05 - Info bpfis (pid=3724) done. status: 1: the requested operation was partially successful
8 déc. 2018 19:31:05 - end writingOperation Status: 1
8 déc. 2018 19:31:05 - begin VMware: End Notify Script
8 déc. 2018 19:31:10 - Info RUNCMD (pid=16100) started
8 déc. 2018 19:31:10 - Info RUNCMD (pid=16100) exiting with status: 0Operation Status: 0
8 déc. 2018 19:31:10 - end VMware: End Notify Script; elapsed time 0:00:05Operation Status: 1The requested operation was partially successful  (1)

Hello,

It will be a good idea to modify the TCP/IP maximum retransmission timeout ? I found the below link with the same issue,but i would like to make sure that doesn't affect anithyng else .

http://kadirkozan.com.tr/netbackup/vmware-sanal-makine-yedeklemesinde-alinan-6-the-backup-failed-to-...

https://www.veritas.com/support/en_US/article.TECH37307

https://support.microsoft.com/en-us/help/170359/how-to-modify-the-tcp-ip-maximum-retransmission-time...

Thank you

 

 

 

Error code 6 "backup failed" is pretty generic. Why did you pick this particular TechNote?

In my previous post, I advised you to seek help from Veritas Support, because the problem is not so simple as, "NetBackup tried to delete the same snapshot twice." This failure message comes from the VMware VDDK (not NetBackup), "The object 'vim.vm.Snapshot:snapshot-43251' has already been deleted or has not been completely created."