VM backup failing with "Unable to access file since it is locked <232>" issue

[hariharan24]

Hi All

VM backup failing with "Unable to access file  since it is locked <232>" issue

Am facing the above said issue frequently in my setup.,  Am having VMware backup host as my RHEL LINUX master itself., Since my NBU version is 7.6.0.4

Randomly my VMware backups are failing with "VM backup failing with "Unable to access file  since it is locked <232>"

While digging into this issue., I came to know that the bpfis is calling to delete snapshot process before bpbkar is done & ends., Due to that reason respective VM's disk is getting locked state.,

This issue results as Datastore to FULL & become the Production VM to unusable state.,

Everytime to fix this issue., Am killing the respective VMs bpbkar process manually using kill -9 command.,

But this is an bug reported in Symantec for 7.6.0.2 & 7.6.0.3 versions & they also suggested to upgrade it to 7.6.0.4 - Whereas my NBU version is 7.6.0.4.

https://support.symantec.com/en_US/article.TECH181118.html

https://support.symantec.com/en_US/article.TECH223790.html

(These links gave me an idea - but they confirmed the bug is addressed in 7604 version)

But still am getting this failure issue., Can you please suggest why this issue is occuring in 7.6.0.4 version.,

Am getting serious escalations due to this issue.., Can anyone help me out with this ??

[sdo]

Are you sure that your Master Server and Media Server (and/or Enterprise Client - and/or VMware backup proxy 'hotadd' Client) are all at v7.6.0.4?

Maybe you are using 'hotadd' and have not updated the NetBackup Client in your 'hotadd' VMware backup proxy host to v7.6.0.4?

[hariharan24]

Am using NBD method to take VM backup.,

Master server itself acting as a media server as well as VM backup host - So the version is 7.6.0.4 only.,
 

[sdo]

Three ideas:

1) Has the backup server been rebooted since it was upgraded to v7.6.0.4?

.

2) This post shows that there is wait time that can be adjusted:

https://www-secure.symantec.com/connect/forums/vmware-snapshots-being-locked-netbackup-7602-upgrade

.

3) This is the VMware tech note for the problem:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2017072

...which in turn links to this VMware tech note which lists the versions that the problem is fixed in (VMware side):

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2007245

...note how it describes as being fixed in VDDK v5.0U1...

...yet we know that NetBackup v7.6.0.4 uses a VDDK at or higher than v5.5:

https://www-secure.symantec.com/connect/forums/limit-size-virtual-machine-while-backup-using-vadp

...so, I'm wondering if your problem is maybe that your ESX hosts are not running at least, (i.e. are lower than):

• ESXi 5.0 Update 1 
• ESXi/ESX 4.1 Update 3

Are you able to confim your ESXi hosts versions?

[hariharan24]

Yes the backup server was rebooted after the upgrade.,

Let me check the ESX host version & come back.,

Yes, I noticed that bpfis timeout wait interval can be increased to infintiy but, Meanwhile can anyone confirm why this issue is happening in 7604 version - As per the Symantec technote this issue has been addressed in this version 7604 ?? Am i right?

Then why am getting this error?

[Marianne]

Connect users cannot tell you why this is happening. If you feel that the NBU is not solved in version 7.6.0.4, then you need to open a Support call with Symantec/Veritas.

[NBU35]

Yes, we are also facing the same issue.

our backup host is Symantec appliance 5220, running at 2.6.0.4 i.e NBU is at 7.6.0.4.

version of VSphere is 5.5 . We upgraded to version 2.6.0.4 from .0.3 as per recommendation from SYmantec.

But issue still persists.

[hariharan24]

Thanks Champ35,

Can you please confirm, how can we resolve this issue? Will symantec provide EEB for this issue??

[hariharan24]

VCenter Version: vCenter server 5.5.0 build 2448239
ESXi Host Version: ESXi 5.5.0 build 2068910