vmware

320 Topics

Solution for VSS exceptions with VMware guests / VM tools
Hi everyone, We have been experiencing VSS issues with VMware guests in regards to the installed Backup Exec Agent and a previously installed VMware Tools VSS option. Uninstalling the VMware Tools VSS option in various ways including restarts did not fix our issues. If you search the internet for solutions, you find many attempts but no real solution or explanation. One of our admins spend several hours with the Veritas support without a solution, he was about to escalate the issue with them, when we found the root cause and could actually fix our issues. First the steps to solve this: Uninstall the VMware Tools VSS option (no restart will be requiered) Make sure VMware VSS service was deleted If this is not the case, you might need to do so manually and remove additional DLL's etc. as well as restart the system, but this is independent from this solution You might have already done steps 1 and 2 but you still get VSS exceptions from the backup that says you have more than one VSS agent installed: V-79-8192-38331 - The backup has detected that both the VMware VSS Provider and the Symantec VSS Provider have been installed on the virtual machine 'hostname'. However, only one VSS Provider can be used on a virutal machine. You must uninstall the VMware VSS Provider. Now you wonder what causes this and you get stuck You could uninstall the Veritas/Symantec Backup Exec Agent and only back the system up per VMDK You would lose the GRT / granular backup / restore capabilities Check your registry for the following reg key HKLM\System\CurrentControlSet\Services\BeVssProviderConflict If this key exists, but your VMware VSS provider is uninstalled, you need to follow up with step 5 Open a notepad as administrator Open this file in the notepad C:\ProgramData\VMware\VMware Tools\manifest.txt Search for the following two entries: Vcbprovider_2003.installed vcbprovider.installed Make sure both of them are set to FALSE, most likely one of them is TRUE Run a test backup This test backup now should not show the exception anymore The registry key should vanish (refresh/press F5) without you taking action So what happened? You uninstalled the VMware Tools VSS provider, but this manifest file did not get updated. We actually could see that it sometimes does get updated and sometimes does not. This seems to be some kind of issue with the VMware Tools uninstalled/installer. But why this manifest.txt file? As we found out, there scripts that get executed by Symantec/Veritas Backup Exec before the backup. You might find them in two locations, and it seems to depend a bit on the Windows version which script is executed (at which location). You could edit them both and just undo the checks in the scripts, but this wouldn't be correct. It is more correct to update the manifest.txt file. If you want to, you can check the date/time of the manifest.txt file before you change it - you might see it was not updated while you uninstalled the VMware Tools VSS provider (assuming you did only do this and not do additional installs/uninstalls within the VMware Tools / please note as well that this only is true when you still experienced those issues). Now, back to those scripts, you find them here: C:\Windows C:\Program Files\Symantec\Backup Exec\RAWS\VSS Provider The name of the script that matters: pre-freeze-script.bat This script checks several DLLs, registry entries, paths and on Windows 2008 and newer the ProgramData-Path for this specific manifest.txt file and the two entries mentioned. Once you uninstall the VMware VSS provider, and the file did not get updated, you might see this issue and wonder how to solve it. The solution is to simply update it to mirror the uninstallation of the VMware VSS provider (vcbprovider). We double checked this with several installations and could see if the file actually gets updated, those two values are set to FALSE, if it doesn't, at least one of the values remains true, what causes the pre-freeze-script.bat to write the registry key mentioned earlier and therefor causing the issue in the backup - exceptions. If you still have the same issues after updating the manifest.txt, simply check all the DLL's that are mentioned in the script and make sure they don't exist. You might also consider to manually delete the registry-key (it seems to be just a dumy-key) to make sure there is no issue that prevents the script from deleting it. Make sure it does not re-appear after a backup! Otherwise you might still have some DLLs left on your system that cause the script to re-create the registry key. Hope this helps a few of you out there. This was an ongoing issue for a while and I came accross those issues many times ever since Windows 2008. This applies to Windows 2008 R2, Windows 2012, Windows 2012 R2 and pretty sure to Windows 2016 as well. It helped us getting rid of those issues completely and actually not even needing a single restart of the guest VM to solve the issues (removing the VMware VSS provide did not need a restart). Regards Florian Rossmark
Solved
frossmark
9 years ago Place Backup Exec
14KViews
2likes
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
15 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.4KViews
1like
15Comments
vSphere 5.1 Support Update
Symantec and VMware are unwaveringly dedicated to quality in our jointly developed solutions. During our testing with the VMware vStorage 5.1 API Symantec discovered issues* that introduce data recovery risks. We raised these concerns with our friends at VMware, who documented them in their knowledge base and in the VMware vSphere 5.1 release notes. VMware expects to release a vStorage API update, and at that time we expect to retest and once again support joint solutions. Read this blog for more details!
Turls
13 years ago Place Backup Exec
6.3KViews
4likes
38Comments
symantec backupexec 2012 AOF VSS hatası (Advanced open file)
Exchange sp1 den 2 ye geçiş yaptıktan sonra seninde her ay gelip kontrollerinde fark ettin ve gördüğün hataydı bildiğin gibi. Hata: LCR veya CCR Yapısındaki ddatabes lerin bir kısmını başarı ile alıp diğerlerinde VSS hatası vermesiydi. Bu VSS hatası için genel olarak net bir çözüm bulamamıştık, microsoft VSS Backup hatasını kabullenmiş bununla ilgili bir sürü makale ve güncelleme çıkarmış ancak net bir çözüm için Exc SP2 Rollup 4 veya SP3 Geçerseniz düzelir diyordu.. Veritas backup forumlarından yola çıkarak edindiğim bilgiler doğrultusunda şunları yaparak çözdüm. 1. Ekteki Vss-update311216.reg dosyasını her CCR deki nod1 ve nod2 ye yüklenmesi gerekiyor 2. Nod’larda symantec agent kurulurken AOF (Advanced open file) kurulmaması gerekiyor 3. Backup jop ayarlarken AOF disable edilmesi 4. Back up from the active copy only mutlaka seçilmeli. Default gelen önerilen seçilmemeli. Konuyu farklı bir şekilde anlatan symantec formu aşağıdadır. Ama en doğrusu benim izlediğim yoldur. Evyap’ta bu sorun devam ediyor diye biliyorum.. http://www.symantec.com/business/support/index?page=content&id=TECH61607
semih_soykal
14 years ago Place Backup Exec
5KViews
0likes
9Comments
e000959a - An attempt to take a snapshot of a virtual machine failed because it was unable to quiesce an application
When doing backups of VM servers I get the following error and some of my backups don't comlete. e000959a - An attempt to take a snapshot of a virtual machine failed because it was unable to quiesce an application This happens with both Full backups and Differentials. I am running Backup Exec 2012 fully patched. The VMWare environment is version 5. Any thoughts or ideas are appreciated.
mike915
13 years ago Place Backup Exec
5KViews
2likes
8Comments
BackupExec & EMC Datadomain
Hello; Nowadays I need to implement a deduplicated disk based backup&recovery solution for a clustered vmware system which is hosting exchange 2010 and AD servers... I have to decide how to position deduplication and backup software solutions together. In some articles I see that Symantec Backupexec and/or Netbackup is used with EMC Datadomain EMC Datadomain has deduplication feature and it's used also as a backup/recovery software. If I buy EMC Datadomain, will I need to another software Symantec Backupexec or Netbackup ? Both Backupexec and Netbackup has "deduplication" feature. If I prefer Backupexec, what's the advantage of Datadomain as an additional appliance?
Tirelibirefe
15 years ago Place Backup Exec
4.6KViews
1like
5Comments
Exchange 2010 Backup : Updating Catalogs Very Long
When backing up Exchange Server 2010 it appears to backup the data with zero issues. However, it takes 20+ hours to run a Differential backup due to the length of time it takes to update the catalogs. This was an issue for us in the previous version of Backup Exec 2010 R3. The issue was not consistent though. For instance; in 2012 we had an issue in late July and early December. The issue in July seemed to correct itself? The issue from December is still ongoing. The backup rate is at about 282 MB/min. Whereas while updating catalogs runs at about 1 MB/min. This definitely appears to be the issue as the entire backup is less than 10GB. The full backup runs normally and does not take an extended period of time while updating catalogs. For all Exchange backups we are running GRT. Any help would be greatly appreciated.
snosurfur
13 years ago Place Backup Exec
4.3KViews
1like
18Comments
Information Store shows 0kb, can't backup Exchange 2010 with BE 2010 R2
Hello. I've read several technotes about this, and threads, and haven't found the answer yet. I have moved Backup Exec 2010 R2 to a WIndows Server 2008 R2 x64 machine so that I could backup my Exchange 2010. My Exchange 2010 server is a VM within ESXi 4.1, for reference, but the RAWS is installed on the Exchange 2010 VM, and so is VMWare Tools. I have installed the Exchange 2010 Management tools on the new BE Media server. The Exchange 2010 server already has the MAPI/CDO 1.2.1 installed. I am getting this when trying to choose selections for doing a GRT backup of the Exchange 2010 server...notice that the Information Store shows 0kb for both the Mailbox Database and the Public Folder Database: I found out that I did NOT have the Backup Exec system account set in the Local Admin group on the Ex2010 server, and did NOT have that account in the "Organization Management" role group. I fixed both things, and verified that the account is a Local Admin on the mail server and is in the "Organization Management" role group. Yet, I still can't get the Information Store to populate and backup. I tried just selecting the Information Store here anyways thinking maybe it was a glitch, and when running the backup, I received this error: Can anyone tell me what I'm doing wrong and how to get the Exchange 2010 GRT backup to work?
Solved
TheMind
15 years ago Place Backup Exec
3.8KViews
0likes
22Comments
0xe0009578 - Unable to copy the virtual machine disk using the VMware VixDiskLib
Hi, I use BackupExec 2010 with VMWare agent to backup a vSphere 4 serverfarm. On three servers I get the error message 0xe0009578 - Unable to copy the virtual machine disk using the VMware VixDiskLib. The KB articel linked to this error message mentions that this error occours when the VM has virtual harddisks on different datastores. This does not apply to all three affected VMs. In particular, one VM has only one virtual harddisk. Nevertheless, I applyed the suggested hotfix 348284 (that superseeded the previous hotfix 344584). But the error is still there. Any ideas? LiveUpdate says, installation is up to date. Regards
ScottHastings
16 years ago Place Backup Exec
3.6KViews
1like
13Comments