115 is just a failure to snap.
Log on to Vcenter and see if you can snap it manually from VCenter.

If it won't snap from Vcenter, TSM can't snap it either, and you will have to 
treat it as a VMware problem.

If it will snap manually (and I'm assuming this is a Windows guest), then the 
problem was getting it to snap at that particular time.  VMware calls MS VSS to 
quiesce a Windows machine before a snap.  Usually if it won't snap it's because 
it won't quiesce, and if it won't quiesce it's usually because there is too 
much I/O going on .  

Find out what is going on with the guest at that time and if it happens every 
night, try scheduling at a different time of day.
As a last resort you can ask the VMware guy to disable the link between VMware 
and MS VSS, see if that works.  But I'm not sure what all the implications of 
that are.  I'm sure you can't use the SQL-aware VE function if you disable VSS.

Good luck!

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Kalipolites, Marc
Sent: Thursday, November 13, 2014 4:50 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM VE Backup Fails for 1 Guest

I have 2 guests on the same host. The scheduled full back up runs on the 
VMPROXY but 1 Guest never backs up. Errors are as seen below.
Any help would be appreciated.

2014-11-12-18.26 ANE4015E Error processing 'LOGOSSQL3': unexpected TSM error 
(115) encountered (SESSION: 9265)
2014-11-12-18.26 ANE4174E Full VM backup of VMware Virtual Machine 'LOGOSSQL3' 
failed with RC=115 mode=Periodic Full - Full, target node name='VCENTER5', data 
mover node name='VCENTER5_DM' (SESSION: 9265)

Thanks

Marc Kalipolites
Systems Network Administrator
Dutchess County OCIS
mkalipolites AT dutchessny DOT gov