FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with 36: SYM_VMC_TASK_REACHED_ERROR_STATE

[mklchan777]

I've been backing up fine all along until I was hit with this error as shown. Not sure what's causing it. Do advise, thanks.

05/01/2016 7:08:40 PM - Critical bpbrm(pid=13755) from client xxxxxx002.xxx.xxxroot.com: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with 36: SYM_VMC_TASK_REACHED_ERROR_STATE

05/01/2016 7:08:40 PM - Critical bpbrm(pid=13755) from client xxxxxx002.xxx.xxxroot.com: FTL - VMware error received: Unable to access file since it is locked

05/01/2016 7:08:40 PM - Critical bpbrm(pid=13755) from client xxxxxx002.xxx.xxxroot.com: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze

[Marianne]

This seems to be a VMware problem.

See http://www.veritas.com/docs/000021732 

Exctract: 

The issue with VDDK 5.0 and 5.1 has been acknowledged by VMware in the below VMware KB.

http://kb.vmware.com/kb/2040846

The issue is fixed in VDDK 5.5 and in VDDK 5.0 Update 3.

This issue is resolved in NetBackup 7.6.0.2 where VDDK 5.5 is integrated
For more information on VDDK 5.5 support after NetBackup 7.6.0.2 release, please check "Support for NetBackup 7.x in virtual environments" in the below link.

http://www.symantec.com/docs/TECH127089

[mklchan777 · Accepted solution]

After a NetBackup version upgrade & a software upgrade from NetBackup 7.5 to NetBackup 7.6.1, this issue is resolved. Thanks.

[Marianne]

If you keep on marking your own posts as Solution, you are going to end up with nobody wanting to help you. It is common practice to mark Solution (or split solution ) for the posts that pointed you in the right direction.