![what happened to symantec backup exec 2014 what happened to symantec backup exec 2014](https://i0.wp.com/www.alphr.com/wp-content/uploads/2014/11/it_photo_146110.jpg)
This points to Exchange VSS errors so leads you down the wrong path. I was having ESE errors when the backup tries to run and fails immediately after. Lenora Moss Technical Support Engineer, SMB Partner Support, Symantec Corporation Surprise surprise, it works just fine :-)
What happened to symantec backup exec 2014 free#
Is this due to only having slightly less than 10% free space on the physical host or just Backup Exec being its usual self? Does HyperV REQUIRE that you have a certain percentage of space free on the physical machine to process?įor further troubleshooting: what happens when Windows Server Backup is configured for the VM backup and ran? Getting a reliable backup of their whole vhd.
![what happened to symantec backup exec 2014 what happened to symantec backup exec 2014](https://image.slidesharecdn.com/ps-symantec-bcdc-perm-140627022956-phpapp02/95/symantec-backup-exec-2014-symantec-14-638.jpg)
I'm inclined to believe Microsoft in this case, but I'm getting nowhere and our customer isn't Symantec say it's the VSS writers (apart from one support technician who admitted their product was a joke) but then Microsoft say it's Symantecs issue. "Failed to create the backup of virtual machine 'HG-2011-SBS'. I also have the following error on the physical host each time I run the backup: "Error: NetLocalGroupGetMemebers(spfarm), 0x80070560, The specified local group does not exist." In the Event log of the Virtual Machine itself, there is only one VSS error, of which I'm told I can safely ignore, but resolved anyway: If the virtual machine is not properly configured, it may be necessary to use the Event Viewer in the virtual machine to identify the Use the Event Viewer on the Hyper-V host to identify the cause. Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).Ī virtual machine snapshot could not be created.
What happened to symantec backup exec 2014 full#
We have had an occasional full HyperV backup to tape, but almost every otherĭay it fails with the following in Backup Exec (now 2014): They have only 150GB spare on the drive which seemed like enough. vhd which is 1.46TB in size, and a fixed disk. We have a customer which has Server 2008 R2 with a. I'm sure this will be a favourite topic, but I was wondering if anyone could shed any light on this situation.