Hi Steve, Version 5.0u2 is not supported for Virtual Environments version 7.1.
reference: http://www-01.ibm.com/support/docview.wss?uid=swg21652843 *Supported VMware vCenter Server versions* The following VMware vCenter Server versions are supported: - vCenter Server 5.1 - vCenter Server 5.5 *Attention:* ESXi 5.1 hosts must be at Update 3 or newer patch or update level. ESXi 5.5 hosts must be at Patch 4 or newer patch or update level. These prerequisite levels address a critical VMware Changed Block Tracking (CBT) integrity issue described in VMware KB 2090639 <http://www-01.ibm.com/support/kb.vmware.com/kb/2090639>. Regards, Stefan On Fri, Mar 6, 2015 at 9:29 PM, Prather, Wanda <wanda.prat...@icfi.com> wrote: > >>We had a situation yesterday where 2 VE backups were causing the VM's to > go unresponsive. No response to ping, unable to RDP, etc. As soon as the > backup finished (or was killed in one case), the servers picked back up > where they left off. They never rebooted, but you can actually see in the > Windows event logs a gap where no activity happens. Has anyone seen this > behavior before? VE is at 7.1.1.1, the Hosts are ESXi 5.0 U2, vCenter is > 5.5, windows 2008R2. > > > > > > ooo! > > Haven't seen that one before. > > > > My basic VE debugging steps when a VM won't back up (all from the VM side): > > > > * check from VCenter that there are no outstanding VM snapshots for > those VM's (trigged by TSM or otherwise) > > * check from VCenter that there is no current performance alert for > those VM's > > * check from Vcenter that vmtools are up to date (it tells you if > they aren't) > > * do a VMware snap from VCenter (If VM can't snap it, nobody can). > > > > If you can't get this far, it's a VMware problem.. > > > > Wanda Prather > TSM Consultant > ICF International Enterprise and Cybersecurity Systems Division >