![]() Gladly we back up all data (non-VMs) separately directly to tape (VMware Direct I/O connected SCSI LTO juke box), so I have at least my data at hand, but I don't understand why even a snapshot of a powered off system halts the Symantec VMware job. ![]() The only thing to do is hit cancel at the BE machine (which actually wouldn't cancel or stop the job), then reboot the BE machine, cancel the VMware job in vSphere client and then "delete" the VMware snapshot to return to merge the changes on the disks. 300GB), last time before it stopped while backing up a powered off Windows Server 2003 test system (approx. ![]() Last time it stopped at 95% of our backend Exchange 2010 server (running, approx. This is only when using backup-to-disk, which actually is a (VMFS 5) partition within the BE virtual machine (drive letter V: size 1,5TB). 1798 64 Bit) VM.Īt some point in the backup process - and different VMs - I can see that there is no progress anymore for hours or days in my vSphere client (percentage of the job freezes) and in BE the MB/min indicator decreases and no changes to the number of backed up Bytes. We are running a VMware 5 (Build 768111) environment with a fibre channel SAN which is being backed up by a Windows 2008 R2 BE2012 SP1a (Verion 14.0 Rev. We are having this issue for weeks/months now : while processing a backup-to-disk job using Backup Exec 2012 SP1a VMware infrastructure agent the backup process hangs at some point.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |