Tag:"vmware"

Backup Exec 20.3 now available to modernize your Data Protection
Backup Exec 20.3 is now available with Day 1 support for Microsoft Windows Server 2019 and Microsoft Exchange Server 2019, new GDPR Guard capability for compliance enforcement, support for Alibaba Cloud, support for VMware vSphere 6.7 Update 1, Granular VMware VM-disk backups, enhanced job logic persistence and more.
BackupMikko
6 years ago Place Backup Exec
17KViews
3likes
4Comments
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
8 years ago Place Backup Exec
14KViews
2likes
10Comments
Instantly Available: Backup Exec™ 15 Feature Pack 5
Recover Instantly with Instant Recovery for VMware and Hyper-V Virtual Machines!Backup to Hybrid Cloud with Private, Hosted and Public Cloud Storage options!Protect Microsoft SQL Server 2016, Exchange 2016 CU2 and much more
BackupMikko
9 years ago Place Backup Exec
7.7KViews
10likes
8Comments
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
Experience clarity on hybrid cloud with Veritas at VMworld 2019
Details on the new Veritas Enterprise Data Services Platform, and insight into our partnership with VMware to help our joint customers “experience clarity,” and more.
AlexRestrepo
6 years ago Place Protection
7.1KViews
0likes
0Comments
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
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
12 years ago Place Backup Exec
6.3KViews
4likes
38Comments
SAN Transport on VMware VSAN
Hi, We recently deployed a new VM infrastructure using Vmware VSAN 6.0 It's running in 10G network and the netbackup 5230 appliance is using the same network for backup. Currently backups are running over LAN method which has some speed limitation on VMware kernel side. I would like to know if VSAN is supported for SAN Transport to maximize the backup speed. Based on the Veritas Education videos online, it is supported but I dont know how to enable it. I cant find any documentation about it as well. https://www.youtube.com/watch?v=-IILCXjhBZc Please help.
HROH_
8 years ago Place NetBackup
5.9KViews
0likes
6Comments
NetBackup and Backup Exec: Day 1 Support for VMware vSphere 6.5
It’s Tuesday, November 15 th . Do you know how you are going to protect your VMware vSphere 6.5 environments? If you’re using the latest version of NetBackup or Backup Exec, you would be safe and sound…
BackupMikko
8 years ago Place Backup Exec
5.9KViews
5likes
2Comments
A Glimpse into the Rich History of Instant Access at Veritas
While the world was standing in line to get their hands on that very first iPhone, our engineering team was busy developing the foundationtechnologies for Instant Access.
SonyaD
5 years ago Place Protection
5.8KViews
1like
2Comments