cancel
Showing results for 
Search instead for 
Did you mean: 

VMware policy error 4275

shahriar_sadm
Level 6

Hi dear all,

Netbackup 8.0 master server installed on windows 2012, (vCenter is 6.5) some VMware policies snapshot are partial successful with the following error:

Apr 27, 2019 6:58:24 AM - Critical bpbrm (pid=20408) from client VM_display_name: 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].
Apr 27, 2019 6:58:28 AM - Critical bpbrm (pid=20408) from client VM_display_name: vfm_thaw: method: VMware_v2, type: FIM, function: VMware_v2_thaw
Apr 27, 2019 6:58:28 AM - Critical bpbrm (pid=20408) from client VM_display_name: snapshot delete returned status 1
Apr 27, 2019 6:58:28 AM - Info bpfis (pid=18672) done. status: 1
Apr 27, 2019 6:58:28 AM - end VMware: Delete Snapshot; elapsed time 0:00:12
Apr 27, 2019 6:58:28 AM - Info bpfis (pid=18672) done. status: 1: the requested operation was partially successful
Apr 27, 2019 6:58:28 AM - end writing
Operation Status: 1
Apr 27, 2019 6:58:28 AM - begin VMware: End Notify Script
Apr 27, 2019 6:58:28 AM - Info RUNCMD (pid=20808) started
Apr 27, 2019 6:58:28 AM - Info RUNCMD (pid=20808) exiting with status: 0
Operation Status: 0
Apr 27, 2019 6:58:28 AM - end VMware: End Notify Script; elapsed time 0:00:00
Operation Status: 1
The requested operation was partially successful (1)

but backups are successful

Next backup of every VM faced this issue failed with status 4275 and this error

Apr 27, 2019 2:20:20 AM - snapshot backup of client VM_display_name using method VMware_v2
Apr 27, 2019 2:20:25 AM - Critical bpbrm (pid=20808) from client VM_display_name: FTL - vSphere_freeze: Unable to consolidate virtual machine disks, status: 36 (SYM_VMC_TASK_REACHED_ERROR_STATE). Error Details: [Unable to access file since it is locked].
Apr 27, 2019 2:20:25 AM - Critical bpbrm (pid=20808) from client VM_display_name: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
Apr 27, 2019 2:20:25 AM - Critical bpbrm (pid=20808) from client VM_display_name: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
Apr 27, 2019 2:20:25 AM - Critical bpbrm (pid=20808) from client VM_display_name: FTL - snapshot processing failed, status 4275
Apr 27, 2019 2:20:25 AM - Critical bpbrm (pid=20808) from client VM_display_name: FTL - snapshot creation failed, status 4275
Apr 27, 2019 2:20:25 AM - Warning bpbrm (pid=20808) from client VM_display_name: WRN - ALL_LOCAL_DRIVES is not frozen
Apr 27, 2019 2:20:25 AM - Info bpfis (pid=16648) done. status: 4275
Apr 27, 2019 2:20:25 AM - end VMware: Create Snapshot; elapsed time 0:00:07
Apr 27, 2019 2:20:25 AM - Info bpfis (pid=16648) done. status: 4275: Unable to consolidate virtual machine disks
Apr 27, 2019 2:20:25 AM - end writing
Operation Status: 4275
Apr 27, 2019 2:20:25 AM - begin VMware: Stop On Error
Operation Status: 0
Apr 27, 2019 2:20:25 AM - end VMware: Stop On Error; elapsed time 0:00:00
Apr 27, 2019 2:20:25 AM - begin VMware: Delete Snapshot
Apr 27, 2019 2:20:26 AM - Info bpbrm (pid=18264) Starting delete snapshot processing
Apr 27, 2019 2:20:26 AM - Info bpfis (pid=12124) Backup started
Apr 27, 2019 2:20:26 AM - Warning bpbrm (pid=18264) from client VM_display_name: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.VM_display_name_1556315416.1.0
Apr 27, 2019 2:20:26 AM - Info bpfis (pid=12124) done. status: 4207
Apr 27, 2019 2:20:26 AM - end Parent Job; elapsed time 0:00:09
Apr 27, 2019 2:20:26 AM - Info bpfis (pid=12124) done. status: 4207: Could not fetch snapshot metadata or state files
Apr 27, 2019 2:20:26 AM - started process bpbrm (pid=18264)
Apr 27, 2019 2:20:26 AM - end writing
Operation Status: 4207
Apr 27, 2019 2:20:26 AM - end VMware: Delete Snapshot; elapsed time 0:00:01
Apr 27, 2019 2:20:26 AM - begin VMware: End Notify Script
Apr 27, 2019 2:20:27 AM - Info RUNCMD (pid=18952) started
Apr 27, 2019 2:20:27 AM - Info RUNCMD (pid=18952) exiting with status: 0
Operation Status: 0
Apr 27, 2019 2:20:27 AM - end VMware: End Notify Script; elapsed time 0:00:01
Operation Status: 4275
Unable to consolidate Virtual Machine Disks (4275)

Do you have any idea
Thanks

4 REPLIES 4

Lowell_Palecek
Level 6
Employee

>Critical bpbrm (pid=20408) from client VM_display_name: do_thaw: Unable to remove virtual machine snapshot...

When bpbrm reports an error from the client, check the client log in question. In this case, look at the bpfis log on your backup host.

I can't say the direct cause of the 4275 error in the next backup. I suspect it has the same cause as the bpfis error in the first backup.

The following error is not important. The cleanup code couldn't find the snapshot state file because the creation code didn't create it before it failed:

>Warning bpbrm (pid=18264) from client VM_display_name: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.VM_display_name_1556315416.1.0

One thing I would check is whether the original snapshot disappeared during the first backup. This could happen if there is insufficient space for the snapshot as it grows.

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

the core error is:

Apr 27, 2019 2:20:25 AM - Info bpfis (pid=16648) done. status: 4275: Unable to consolidate virtual machine disks

So ask your VMware admin to perform disk consolidation (it sometime requires VM outage).

Regards

Michal

Hi @Michal_Mikulik1 

Yes you are right, but it happens exactly after partial successful snapshot or even you kill a backup proccess, next backup will failed with 4275 status. I think its related to netbackup 

Thanks

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

The interpretation of status 1 as 'partially successful' is actually incorrect.

The status 1 on VMware side is actually a failure (error status is Critical):
 Critical bpbrm (pid=20408) from client VM_display_name: snapshot delete returned status 1

Where application reports a status of 0 for success and 1 for failure, NBU will unfortunately take that status code exactly 'as is'. 

So, you need to troubleshoot the 'snapshot delete' error. 
You need to check bpfis log (level 3 at least) on the backup host and VM admin needs to check for errors on VMware side.
'Something' is preventing NBU from deleting the snapshots. 
It could be insufficient permissions.