In our situation, the backup had no problem. One had completed, the other was busy sending data and had to be cancelled. as soon as the backups finished & the snapshots were deleted, the servers started responding normally. No one knows why. Of course this is a big red flag for our VM Engineers. Thanks, -steve
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Friday, March 06, 2015 3:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VE 7.1.1.1 backup "freezing" a VM & question about "megablocks" >>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 ----------------------------------------------------- Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm