Maybe the vmware*.log files can help!? Either take a look at them, or compress/zip them and attach the .zip file to a reply post to find out whether they contain any hints.
It looks like something went badly wrong during a backup at 3 AM on the June, 20th, but unfortunately the log file doesn't show what exactly happened. It just showed that the snapshot could not be deleted due to a missing file and them the VM stopped working.
Possible options are either open a support call with the backup vendor, or edit the VM's configuration (.vmx) file manually and replace the virtual disk, i.e. replace:
scsi0:0.fileName = "/vmfs/volumes/52378378-bd8fee3a-174d-0025b51100af/IRVLBLLFT03/IRVLBLLFT03-000001.vmdk"
scsi0:0.fileName = "IRVLBLLFT03.vmdk"
and optionally delete the "IRVLBLLFT03-ctk.vmdk".
If you do this from the ESXi host's command line, follow http://kb.vmware.com/kb/1026043 to reload the VM after editing the .vmx file.
Since the VM was stopped right after this issue, you may not lose data if you manually revert to the base disk, but I cannot promise you anything.
thanks Andre...it work perfrctly....
Thanks & Regards