Virtualization

1331 Topics

vCenter backup fail
I keep running into the same issue where BE2014 will error out when it reaches vCenter in the VM backup scheme. I get the following messages whether BE is backing up the whole datacenter or backing up the indivual VM. vcenter test-Backup -- The job failed with the following error: An attempt to take a snapshot of a virtual machine failed because it was unable to quiesce an application. A quiesced snapshot could not be created for the virtual machine (DC)ha-datacenter(DC)\vm\Vcenter. Is vCenter supported in BE2014?
Solved
kennyb
10 years ago Place Backup Exec
7.6KViews
1like
10Comments
Where to install the Backup Exec Agent for VMware
Hi, I'm using VMware vSphere with some guest VMs. But I'm not sure where to install the Backup Exec 2010 Agent for VMware. I cannot find any documents on internet. Any one kindly know the answer? Thank you.
Solved
hongkong123
14 years ago Place Backup Exec
7.3KViews
1like
10Comments
Backup Exec hangs while backing up VMware VMs (snapshot)
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. 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. 1798 64 Bit) VM. At 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. 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). Last time it stopped at 95% of our backend Exchange 2010 server (running, approx. 300GB), last time before it stopped while backing up a powered off Windows Server 2003 test system (approx. 30GB). 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. 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. Snapshots manually initiated in vSphere client have not been an issue yet, disk space is available, too. Have not found any similar problem desciption in Google... Any help really appreaciated!
Solved
Bembel
13 years ago Place Backup Exec
6.3KViews
1like
15Comments
Attach a physical tape drive (SAS) to Hyper-V 2012 Virtual Machine
I will have Backup Exec 2012 running on a Windows 2008 R2 virtual machine which is hosted on a Windows 2012 R2 Hyper-V server and want to know if it is possible to connect a physical LTO5 tape drive / library to the Hyper-V server and make it available to the Backup Exec VM. I have previously been advised that it is possible by a Symantec engineer but since read that this is not the case, or if it is, it isn't supported. Does anyone know how I can do this or get around the problem? If there are any 3rd party products which can help, then that could also possibly be an option (depending on security accreditation). Thanks.
Solved
chris48
11 years ago Place Backup Exec
6.3KViews
1like
4Comments
GRT-Enabled Backups on GPT-Partitioned VMware-VMDKs
Hi, I just run into the Issue, that GRT-Enabled Backups via AVVI on GPT-Partitioned VMDKsin VMware fail with an exception and are not supported as stated in the SCL. Does anyone know the technical background of this limitation and if there might be a chance to get this feature later on with another ServicePack ? I wonder because it seems to be possible with MicsoroftHyper-V based VMs (according to the SCL:http://www.symantec.com/business/support/index?page=content&id=TECH217478&key=15047&basecat=COMPATIBILITY_LIST&actp=LIST ). The problemis, that 2TB+ Volumes are getting more common even for smaller customers and doing agent level backups in VMs prevent me from doing SAN-basedbackups, which are way faster especially with FC. Switching off GRT is also not an option as this is one of the most basic backup features and about 75% of my restore jobs are single-file or directory based restores on file servers. Source:http://www.symantec.com/business/support/index?page=content&id=TECH69498&actp=search&viewlocale=en_US&searchid=1415000582760 Regards, inti
Solved
Inti
10 years ago Place Backup Exec
6.1KViews
3likes
20Comments
Backup Exec support for ESXi (free)
HI, we have 1 customer who has 2 VMWare ESXi 5.0 Hypervisors with the free license of VMWare. We were backing up these ESXi 5.0 machines with Symantec back-up Exec 2010 R3 which worked fine. We could back-up the machines and granulary restore files from these back-ups. We even had Symantec Support work on a case where the back-ups were failing due to misconfiguration. Recently we have upgraded 1 of these 2 ESXi hosts to VMWare ESXi 5.5 u1 and the back-ups started failing. We were advised to upgrade to Backup Exec 2012 and we did. After we upgraded to Backup Exec 2012 we were still getting the same errors for this particular host. The VMs from the ESXi 5.0 host were backing up without any issues. We then found out that in order for back-up Exec 2012 to be able to back-up ESXi 5.5 u1 we would need a VMWare standard license because Backup Exec 2012 uses the Vstorage API. if we were to downgrade the ESXi (free) 5.5 u1 host to ESXi (free) 5.1 u3, would we be able to back-up the VMs on this host again with Back-up Exec 2012 VMWare integration?
JosVerhallen
11 years ago Place Backup Exec
5.8KViews
0likes
9Comments
V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib.
Hello Everyone, Currently we have a server 2008 64bit server with BE 2014 which was upgrade from 2012 and for some strange reason I keep getting this particular error message while backing up a few VMs as you can see below. V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib. VixDiskLib_Read() reported the error: NBD_ERR_DISKLIBV-79-57344-38366 - WARNING: "VMVCB::\\10.0.1.5\VCGuestVm\(DC)ha-datacenter(DC)\vm\SCSMDW\SCSMDW\SM Warehouse-000002.vmdk" is a corrupt file. This file cannot verify. Transport mode 'nbd' was used for the read operation of the disk 'SM Warehouse_1-000002.vmdk' In addition, I have research this particular message and I have not yet found anything online that is exactly what I am having issues with. Furthermore to provide additional background information the issue that I am having with the VM are on an Exsi host that is running version 5.5.
Vdang
10 years ago Place Backup Exec
5.6KViews
0likes
17Comments
install failed with error code 1603
Hi, When taking image backups i am getting the particular error. Even the Full Image backups doesnt work. Image Backups-Incremental Image Backups-Daily -- The job failed with the following error: Incremental\\Differential backup methods are not supported for this VM. The backup job failed, since the option 'to fall back to a full backup' was not selected. I logged a case with Symantec support and they said each VM should have an agent installed whether you need to take a GRT backup or just an image backup. Secondly they said all VMs must have hardware version7 inorder to do an incremental backup inorder to allow change block tracking feature within VMware. As a first step I am trying to push the RAWS agent to each VM. While installing agents on some VMs i am getting the following error 'install failed with error code 1603' I checked firewall settings and they are disabled. Thanks!
Solved
zak2011
13 years ago Place Backup Exec
5.5KViews
1like
4Comments
Backup error: Unable to open a disk of the virtual machine
Our setup: 3 vSphere servers with 4 SAN disks. 1 backup server connected to the SAN When we try to backup our VM's running on vSphere 4.0 we get the error "Unable to open a disk of the virtual machine". So we made the 4 SAN disks available to the backup server. But after that I'm lost. In Windows Disk Management we see the 4 disks but 2 of them have a Windows disk signature! I have no idea how this is possible. But to make things more complicated: I can only make a backup of VM's that have their files on the disks that have a disk signature. So I thought, just create a disk signature on the other 2 disks and I can backup the others VM's as well. But I cannot write a disk signature on the SAN disks (write protected...) So at the moment I'm lost. How can I make the disks available to the backup server in order to backup the VM's without writing disk signatures? I really hope someone can help me with this... Jeroen
Solved
jeroenburen
14 years ago Place Backup Exec
5.4KViews
1like
13Comments
Catalog error on one particular sever
Hi I'm back. After small issue to upgrade to backup exec 2012 sp1a, I have a very strange error. If I make a full backup of my virtual servers (CSV cluster), the backup to disk works just fine. But when the jobs start to make a duplication to tape, I receive an error saying 'An error was encountered writing to the on-disk catalogs'. the final error is The job failed with the following error: An error occurred while retrieving catalog information I found this article http://www.symantec.com/business/support/index?page=content&id=TECH53393 but it was no solution. The error is only generated on a particular server.
ApieBe
12 years ago Place Backup Exec
5.3KViews
1like
10Comments