Agent for VMware Virtual Infrastructure

571 Topics

V-79-8192-38330 on VMware backup
Hi. We get V-79-8192-38330 errors in the backup log because some machines having independent/persistent vdisks. We know that BE will skip those vmdks for technical reasons and this is what we intend. However the backup gets the status failed which leads to the fact that the customer has to look into every backup log in detail to see if something else caused the backup to fail. Is there any way that this "error" doesn't cause the backup status being set to failed? Thanks.
harsi
6 years ago Place Backup Exec
1.6KViews
0likes
12Comments
Disable GRT only for specific VMs
Hi, I have to backup a couple of VMs. On some of them I can't install the Remote agent. Either because they are Linux appliances or because firewall rules don't permit direct communication between them and the media server. So, it is expected to get the warning V-79-57344-38726 - Backup Exec failed to connect to virtual machine 'XXX' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup for every of these VMs. It seems, to suppress this annoying warning the only method would be to disable GRT globally for this backup job. This would also effect the VMs that have the agent installed and where GRT is a recommended feature. An alternative would be to split the backup job in two - one with GRT enabled, and a second with GRT disabled and only the respective VMs selected. I would of course prefer to have just a single backup job. Is there a method to either suppress the warning or to disable GRT just for specific VM? Kind regards!
Solved
ScottHastings
6 years ago Place Backup Exec
3.9KViews
0likes
5Comments
Cannot access vSphere Server (BE 15)
After upgrading from BE 2014 to BE 15 (actually it was uninstall BE2014 and install BE 15) I cannot access a vSphere 5.5 Server. If I try to backup , then i get a failure message saying that the credentials could not be tested, sometimes "server did not answer". Changing credientials does not help. Also I cannot open the tree of VMs as before. The message says simply "a communication failure occurred". therefore I cannot build a new backup job i already read something about this phenomen, but this seemed to work for already existing jobs with failure meesages logged. I tried to replace the actual libcurl.dll by a version from BE 2014 - no change. i also de-activated IPv6 on the backup server - no change. All updates are installed. Agent seeems to be working Can someone help me ?
Solved
Nicolas_Nickisc
9 years ago Place Backup Exec
3.6KViews
0likes
8Comments
Plug-in for Vmware Vcenter Appliance
I have installed de Backup exec Plugin for on vmware (version 2.1). WithvCenter Client i connect to thevCenter Applianbe. When i click on the tab Symantec Backup Exec and log te backup server i see no info (see attachment). The same view when i log on a singe ESXi server. Is the vcenter appliancenot supported. Vmware vCenter Serverapplicance 5.5.0 2442330 Vmware ESXi 5.5.0 1623387 Vsphere Client 5.5.0 Thanks Abdel Belgdour
Solved
Abelgdour
9 years ago Place Backup Exec
1.8KViews
0likes
4Comments
Problem adding ESXi hosts to BE15
I'm trying to create a backup of VMware VMs in Backup Exec 15. I created a new domain user "BackupExec" and gave it permissions to the vSphere (ESXi 5.5) server at the "Administrator" level,and it propagated those permissions to all the hosts and virtual machines. However, when I test the credentials, I'm successful at logging on only to VSphere athost level and to theindividual virtual machine that's running the VSphere software,and not to the other 2 virtual machines that I've scheduled for backup.I even tried changing the credentials for the other 2 virtual machines to my defaultBEsystem logon account (which I know works because I can do aregular file-level backup using it),but that doesn't work either.??? Help will be very much appreciated!
Deborah_Lane-Ol
9 years ago Place Backup Exec
486Views
0likes
2Comments
incremental errors 0xe00095b3 Unable to create the virtual disk. Using deduplication storage
Hi. We have strange behavior of BE 2015. Environment: 1. BE2015 server with local disks for local disk-based storage. e:\ f:\ g:\ h:\, each logical volume on one HDD. installed features: Copy Server Configurations,Virtual Tape Library Support,Deduplication Option,Agent for VMware and Hyper-V,Agent for Applications and Databases. 2. Configured disk based storages in BE2015 using local disks and named: Deduplication disk storage 0001- H:\BackupExecDeduplicationStorageFolder Disk storage Full- E:\BEData\ Disk storage inc- G:\BEData\ Duplication storage- F:\BEData\ 3. Test server being backed up on ESXi named wksmon01. It is just a regulary flat machine with win7 no additional application on it. 4. Test job which backs up virtual machine wksmon01 with options: GRT (for files) + NBD. Two templates: full -uses "Deduplication disk storage 0001", incremantal- uses"Disk storage inc". One stage: duplicate to disk immediate after full backup uses "Duplication storage". Let's start action! а. Full backup-passes with no errors. GRT provide restore individual files. b. Automatically passes duplication stage. No errors. c. First Incremental backup- passes. No errors. d. Remove duplication storage: - make "Duplication storage" to disabled state - make disk F:\ offline using disk management console e. Second incremental backup- ERROR. 0xe00095b3 - Unable to create the virtual disk. Full error text in attach. After abig series of test jobs with different options and different storage i have that: Incremental jobs start to fail only after removing "Duplication storage" which was used to duplicate baseline full backup. If i change job option tonot using GRT than all subsequent incremental jobs runs fine with no errors even after removing "Duplication storage". If i use "Deduplication disk storage 0001" for both full and incremental jobs with GRT enabled thanall subsequent incremental jobs runs fine wiht no error also. If i use "Disk storage Full" for full backup and "Disk storage inc" for incremental with GRT enabled i also have no errors with all subsequent incremental jobs even after removing "Duplication storage". SUMMARY. incremental jobs with enabledGRT optionstart to fail after removing "Duplication storage" which was used to copy baseline full backup in case when full backupuses Deduplication disk storage and incremental jobs use Disk storage.
alexey107
9 years ago Place Backup Exec
2.4KViews
0likes
9Comments
How to exclude Drive/vmdk or files from vmware virtual-based backup
HI @ all, I need to backup different VMs using virtual-based backups. Now my questions: How can I exclude a whole drive from the backup? How can I exclude a whole vmdk from the backup? How can I exclude a from the backup? Thanks for any help! best regards,
Solved
windows-it
9 years ago Place Backup Exec
3.4KViews
5likes
2Comments
Can't restore VM's vmdk to different storage
Hi. We use BE 2015 with all updates. Virtual infrastructure is ESXi5.5.0 all servers are part of cluster. Also we have several SAN datastores to which all cluster nodes have access. I need to restore VM to different datastore than original is. I create restore job as: "to a differnet vCenter or ESX server" Virtual machine datastore or datastore cluster- here we select different storage. After restore completed we have only "Virtual machine Configuration File" and "Virtual Machine Working Location" located on storage i selected in the job. But all VM's .vmdk are on the same storage as the original one. How could i make job to restore all vmdks to the storage that i need.
alexey107
9 years ago Place Backup Exec
893Views
0likes
10Comments
Backup only full, can't incremental
Dear, i have some problem with job backup increment. the backup cannot running increment but always running full backup. the previous job, full backup running successfully. this issue occur when increase new virtual disk (drinian*******_9.vhdx) on that server, full backup succesfully and backup incremental running very high same with full backup. i find some information " A Full backup was run on this virtual machine, since the option to fall back to a full backup was selected. Incremental\\Differential backup methods are not supported for this virtual machine." - symantec backup exec 2012 hotfix 217347 - server windows 2008 R2 - Vmware version 5.5 what should i do? please inform me if i'm wrong. what is the best practies after increase virtual disk?
Solved
RIDHO07
9 years ago Place Backup Exec
3.1KViews
1like
6Comments
VMware based incrementals not working
Hi, I'm having issues with getting Incremental backups of VMware virtual machines working using the AVVI agent. V-79-57344-38324 - 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. V-79-57344-38366 - Backup Exec 2014. vSphere 5.5 I've confirmed that VM hardware version is appropriate and that CBT is enabled and working. Full backups have completed successfully. What can caused the above message and incrementals to not be possible? Thanks
Dead-Data
9 years ago Place Backup Exec
1.1KViews
4likes
4Comments