VMware 7.0.2 with BE 21.2R2
Dear all, We are setting up a test environment with the following elements: -VMware Cluster with two ESXi nodes and vCenter 7.0.2 -Fujitsu Eternus DX200S5 storage cabinet -Backup Exec 21.2R2 In the virtual layer we have several Windows Server 2019 VMs with Fault Tolerance active, could you confirm what is the current integration of these FT machines in Backup Exec backups and restores for specified versions of the involved products? At least, we have checked that backups can be completed directly from vCenter, without the need of additional agents. How we should perform a complete restore of a FT VM? Thank you very much for your help. BR, Samu632Views0likes1CommentCompute requirements for a VMware Backup Host
Hello VOX Community, Do we know where can I find the documentation for VMware backup host requirements of compute (vCPU, RAM etc..) for hot-add mode ? I have looked around VMware guides for netbackup but couldnt find it documented anywhere.Solved1.1KViews0likes2CommentsMultiple Clients Failing - VMware - status 196
Hi All, I am pretty new to Veritas Netbackup systems and I have been dealing with a status 196 on a client environment that has now been happening for a month. This issue is resulting in multiple policies failing due to a backup window timeout error. The policies failing are VMWare policies and are configured to use the vsphere intellingent policy backup method using annotations. I raised a veritas support case and the TSE based on his investigation advised to reduce the number of backup jobs from each policy running at any given time. However this atleast for now can not be done due to the client's requirement of not having backups run during business hours. Currently the backups are set to full backups and are backing up sizes raning from 4TB, 2TB, 1TB. I was wondering if any assistance or knowledge share can be done here to help troubleshoot and diagnose the issue at hand? Happy to provid emore clear and concise information for further understanding. Many Thanks!1.4KViews0likes4CommentsVMWare Backups Failing - Login Failure?
Hi, We have recently started having an error when backing up VM's via the vCenter server: The job failed with the following error: A failure occurred while locking the virtual machine in place for backup/restore operations. VDDK-WARN: VixDiskLibVim: Login Failure. Callback error 1800 at 2500. I can't find much information on this callback error code, anyone have any insights? The account used has full top level vCenter permissions and previously worked. I have ran a debug and at the point of failure we see: [fsys\shared] - VDDK-Log: [LoadTempHive] Registry hive D:\Program Files\Veritas\Backup Exec\Data\VMwareTemp\vixmntapi225\BCD is loaded under the name mntApi388674662730830357 [fsys\shared] - VDDK-Warn: ERROR 2 opening key mntApi388674662730830357\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\12000002 [fsys\shared] - VDDK-Warn: ERROR 2 opening key mntApi388674662730830357\Objects\{df2aff03-2345-11df-9851-e076a68f85fc}\Elements\12000002 [fsys\shared] - VDDK-Warn: ERROR 2 opening key mntApi388674662730830357\Objects\{df2aff02-2345-11df-9851-e076a68f85fc}\Elements\12000002 [fsys\shared] - VDDK-Warn: ERROR 2 opening key mntApi388674662730830357\Objects\{df2aff04-2345-11df-9851-e076a68f85fc}\Elements\12000002 [fsys\shared] - VDDK-Warn: ERROR 2 opening key mntApi388674662730830357\Objects\{521d7511-7875-11e7-93d9-e44bb22fdbc2}\Elements\26000022. [fsys\shared] - VDDK-Log: BootConfiguration::GetDefaultOsInfoFromVistaBCD error 0 [fsys\shared] - VDDK-Warn: ERROR: Error 13 reading Element value from key mntApi388674662730830357\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\24000001 [fsys\shared] - VDDK-Warn: ERROR 2 opening key mntApi388674662730830357\Objects\{521d7511-7875-11e7-93d9-e44bb22fdbc2}\Elements\26000022. [fsys\shared] - VDDK-Warn: ERROR 2 opening key mntApi388674662730830357\Objects\{521d7510-7875-11e7-93d9-e44bb22fdbc2}\Elements\26000022. [fsys\shared] - VDDK-Log: BootConfiguration::RetrieveVistaOsEntries error 0 entries:2 [fsys\shared] - VDDK-Log: PopulateOperatingSystemEntries error 0 [fsys\shared] - VDDK-Log: Unloaded hive mntApi388674662730830357 [fsys\shared] - VDDK-Log: DeleteHive: Deleted 8 hive log files on cleanup. [fsys\shared] - VDDK-Log: OSLoaderEntry: 'Windows' 'Windows Server 2012 R2' (disk:0 partition:0 offset:368050176) [fsys\shared] - VDDK-Log: Mntapi_GetSystemVolume: System volume found (BCD, index 1) [fsys\shared] - VDDK-Log: CopyHive: Copied 4 hive log files on D:\Program Files\Veritas\Backup Exec\Data\VMwareTemp\vixmntapi55. [fsys\shared] - VDDK-Log: [LoadTempHive] Registry hive D:\Program Files\Veritas\Backup Exec\Data\VMwareTemp\vixmntapi55\SOFTWARE is loaded under the name mntApi396366928930830357 [fsys\shared] - VDDK-Warn: ERROR: Error 2 reading CSDVersion value from key mntApi396366928930830357\Microsoft\Windows NT\CurrentVersion [fsys\shared] - VDDK-Warn: ERROR 2 reading SP information [fsys\shared] - VDDK-Log: CurrentType key is Multiprocessor Free [fsys\shared] - VDDK-Log: 64 bit registry contains Multiprocessor Free [fsys\shared] - VDDK-Log: Product name is Windows Server 2012 R2 Datacenter [fsys\shared] - VDDK-Log: OSLoaderEntry: 'Windows' 'Windows Server 2012 R2' (disk:0 partition:0 offset:368050176) [fsys\shared] - VDDK-Log: Mntapi_GetSystemVolume: System volume found (BCD, index 1) [fsys\shared] - VDDK-Log: CopyHive: Copied 4 hive log files on D:\Program Files\Veritas\Backup Exec\Data\VMwareTemp\vixmntapi59. [fsys\shared] - VDDK-Log: [LoadTempHive] Registry hive D:\Program Files\Veritas\Backup Exec\Data\VMwareTemp\vixmntapi59\SYSTEM is loaded under the name mntApi398936896330830357 [fsys\shared] - VDDK-Warn: ERROR: Error reading from mntApi398936896330830357\ControlSet001\Services\vmxnet - 2. [fsys\shared] - VDDK-Warn: ERROR 2 getting vmxnet information, assuming vmxnet is not installed [fsys\shared] - VDDK-Log: Unloaded hive mntApi396366928930830357 [fsys\shared] - VDDK-Log: DeleteHive: Deleted 8 hive log files on cleanup. [fsys\shared] - VDDK-Log: Unloaded hive mntApi398936896330830357 [fsys\shared] - VDDK-Log: DeleteHive: Deleted 8 hive log files on cleanup. [fsys\shared] - VDDK-Log: OSLoaderEntry: 'Windows' 'Windows Server 2012 R2' (disk:0 partition:0 offset:368050176) Thanks,Solved2.7KViews0likes2CommentsEnable file recovery for VMware virtual machines
NetBackup has a feature called Enable file recovery from VM backup that allows the restore of individual files from VMware virtual machine backups. How is this any different than using GRT? Can you use GRT on a VM and restore a single file from a snapshot backup?2.4KViews0likes3CommentsHow can I check that the datastore LUNs are accessible to VMware Backup Host.
Greetings to all !! Environment: Master Server : Linux VM : 2.6 NBU Version : 7.6.0.4 Media Server : NetBackup Appliance 5230 NBU Version : 7.6.0.4 NBU Appliance Version : 2.6.0.4 Transport Mode : SAN Storage : VNX Block level Cisco mds switch. I have few queries, as backup of vm getting failed with 6 error code. As using SAN, how can I check that the datastore LUNs are accessible to VMware Backup Host. (Apart from checking zoning, which is perfectly fine) If the previous backup failed, it might have left some disks of the backup VM attached to Backup Host. These disks need to be manually removed before attempting the next backup. -- How can I find the left out disk of vm on the backup host? If a new LUN added to storage and zoning done with Backup Host, do we need manual scan at Backup host ? The backup getting completed using NBD mode as ESXi host is accessible at 902 port via backup host. But why its being failed using SAN mode, however zoning is perfectly fine? Your assistance would be really appreciable.1.7KViews0likes2Comments