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.6KViews0likes6Comments
Snapshot error status 156 using VCB
Enviro: NB 6.5.3.1 on dedicated master, media and proxy. Proxy attached to 2 CLARiiONS, one for source vmdks, the other for snapshot cache. VCB 1.5 Windows Server 2003 R2 SP2 x64 is the VCB proxy. Attached to array over 2Gb FC. VM Backup : 1 transfer type: 3 vmdk type: 1 Seems like if backing up one VM at a time will work. Running them in "streams" all results in snapshot errors although I don't see any bottlenecks anywhere. When I setup the VCB policy I enabled 5 streams. When the jobs kick off, only the first one was successful, the others all fail with "- Critical bpbrm(pid=5932) from client qa01: FTL - snapshot creation failed, status 156". 90% of our VM's are Linux so all I care about is fulls I guess. I'm attaching the bpfis log from the proxy, the bpvmutil log has nothing relavent to this issue as the discovery is all running fine, just incredibly slow. Has anyone seen this issue? thanks in advance. There are multiple failing commands and errors but I do not see how to resolve this based on other posts.Solved5.1KViews1like42CommentsFailed to get VM Server Info List
Hi, I am trying to set up new clients in the VCB policy on a 6.5.3 server. The proxy is dedicated and is running 6.5.3 as well. The Virtual Center Server has over 75 running VM's it knows about, yet when I try to Browse Virutal Machines in Net Backup, all I get is the "file read failed (13)" error. I created the bpvmutil logs and setup the verbose logging levels. Seems as though from the command line I can login to the VCS fine but when I query names, it only returns one junky little test VM and none of the others: C:\Program Files (x86)\VMware\VMware Consolidated Backup Framework>vcbVmName.exe -h virmgmt101-dev -u sa_vmbackup -p ****** -s any [2009-04-21 07:00:57.739 'App' 5996 info] Current working directory: C:\Program Files (x86)\VMware\VMware Consolidated Backup Framework [2009-04-21 07:00:57.739 'BaseLibs' 5996 info] HOSTINFO: Seeing Intel CPU, numCoresPerCPU 4 numThreadsPerCore 1. [2009-04-21 07:00:57.739 'BaseLibs' 5996 info] HOSTINFO: This machine has 1 physical CPUS, 4 total cores, and 4 logical CPUs. [2009-04-21 07:00:57.739 'BaseLibs' 5996 info] Using system libcrypto, version 90709F [2009-04-21 07:01:13.066 'BaseLibs' 5996 warning] SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs virmgmt101-dev [2009-04-21 07:01:13.066 'BaseLibs' 5996 warning] SSLVerifyCertAgainstSystemStore: The remote host certificate has these prob lems: * The host name used for the connection does not match the subject name on the host certificate * A certificate in the host's chain is based on an untrusted root. [2009-04-21 07:01:13.066 'BaseLibs' 5996 warning] SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0 [2009-04-21 07:01:13.066 'BaseLibs' 5996 warning] SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so c onnection will proceed despite the error [2009-04-21 07:01:15.316 'vcbVmName' 5996 warning] IP address not set. Found VM: moref:vm-23253 name:test4 uuid:50165156-871d-1e74-52e2-18d82d7e8584 ipaddr: I'll attach the relavent log file as I am stumped and we don't know where to look for the answers. The one thing that might be biting us is the VCB proxy / master/ media servers are completely firewalled off from the ESX/VCS servers. We have port 443 open from the VCB proxy to the VCS, and the logs show the communication is working. Just a sanity check, but do the master and media server need to talk to the VMware servers or does everything pass thru the proxy as I think? thanks in advance!Solved5KViews1like9Comments
Getting Media Write Error (84) attempting to write to DataDomain
I am using Netbackup 7.1.0.3 and was successful backing snapshots to the DataDomain (DD) until recently. The space was at 100 percent and would not clear any space over a couple of weeks (was getting 84 errors then. I then began to expire some data in order to get more space and now have cleared more than 2/3 of the contents but still cannot write to the DD.Solved4.3KViews2likes13Comments
Restore VMDK as a file
Hello Is there a way to restore VMDK backups as flat files to an alternate location? Without restoring the VM itself? This question came up because we had an issue with our vCenter a few weeks back and realized we couldn't restore ANY VM's without vCenter being active so we are looking for a way to recover vCenter without vCenter. One way we think we can skin this cat is to use the vmdk files and push those to a host. However I don't know HOW to get the VMDK's out from netbackup as files. Suggestions? ThanksSolved4.2KViews0likes6CommentsBackup a VM with disk type RDM
Hi Experts, I have a few questions. I am trying to backup a vm with disk type RDM which is deployed on a ESX may i know how the backup flows ? through Ethernet or FC ? Two cases 1. Agent Installed directly on Agent & 2. What if i have backup host (ESX or NBU appliance as Backup Host) Environment:- Master server 8.0 (VM machine Windows 2016) Media Server:- NBU 5240 Appliance (MSDP Pool) Client:- Windows 2016 Hosting SQL (Using RDM type of disks) Also i would like to know is the restore always happen through ETHERNET ? How can i choose it to run through FC ? Any inputs on service resilency while deploying a Master on VM ? (What if my VM crashed ) Does the VM clone helps to recover ? If yes , to what state ? Thanks Nayab,Solved4.1KViews0likes6CommentsNetbackup failed to obtain SSO Certificate using VMWare vCloud Suite APIs
Hi We have two netbackup appliance 3.1.1, 5240 in two datacenters one virtulized NBU-master with 8.11. Installation is rather straigth. This problem is somehow related to vmware backup. A bit of the setup for that policy: letsay one databox called dc007 (the faulty one) and dc008 (the goodone) Policytype: VMware disable client-side deduplication use Accelerator Standard schedule Select automatically through VMware intelligent Policy Query (yee.. short this one) empty box "Enable vCloud Director integration". (we dont use cloud in any circomstans) Advanced settings (the imortant one) virtual machine quisce - enable snapshot retry 2 Snapshot creation intervals 10 (rest is no or 0 or disabled Transport SAN Problem This policy has stopped work after a reboot on the appliance otherwice all same (what i can remeber). This works: Query builder with one object in Like "displayname equal <hostname>" when the dc007 is the media server and i run a TEST Query and run the work. Same query on the other appliance box as "Netbackup host to perform autmatic virtual machine selection This doesnt work: Multiple lines in the query when dc007 is media server do the work, gives FAILED with the error "2018-nov-07 09:57:30 - Error nbpem (pid=5076) Failed to obtain SSO certificate using VMware vCloud Suite APIs, msg = [com.vmware.vapi.std.errors.Unauthenticated: Unauthenticated (com.vmware.vapi.std.errors.unauthenticated) => {" Change this do the DC008 it goes well or the NBU-Master What I've done so far Rebooted the master server Rebooted the media server Restarted the service Have an ongoing ticket with Veritas (good fellow) ;). (but on the other side of our timezone).. Rearange and created new policy with simple querys in any form to see if it helps. .same error.. Regards Pontus AnkarbågeSolved3.9KViews0likes3Comments
Retrieving details of resource pools - Failed system call failed (11) with Alternate location Option (Netbackup 7.5.0.3)
Hello, I have got error " Retrieving details of resource pools - Failed system call failed (11) " after i had tried to recover virtual machine with Alternate location option. Here is the pertinent information and error details: Client: Windows2008, NBU Client 7.5.0.3 Master server: Windows2008, NBU Server 7.5.0.3 Error detail of most recent failure: 16:44:27.735 [7452.8124] dovSphereLogin: sApiType = HostAgent 16:44:27.735 [7452.8124] dovSphereLogin: version = 4.1 16:44:27.735 [7452.8124] dovSphereLogin: sBuild = 348481 16:44:27.735 [7452.8124] dovSphereLogin: full name = VMware ESXi 4.1.0 build-348481 16:44:27.735 [7452.8124] dovSphereLogin: sName = VMware ESXi 16:44:27.735 [7452.8124] dovSphereLogin: sOsType = vmnix-x86 16:44:27.735 [7452.8124] dovSphereLogin: sProductLineId = embeddedEsx 16:44:27.735 [7452.8124] dovSphereLogin: sVersion = 4.1.0 16:44:27.735 [7452.8124] dovSphereLogin: sServerCurrentTime = Mon Aug 06 16:44:31 2012 16:44:27.735 [7452.8124] dovSphereLogin: login for ESXHQ-01.CDGM.LOCAL completed with flags 70 and status 0 16:44:29.061 [7452.8124] vmwareLogger: RetrieveObjPropertiesEx: for mor = Null failed, SYM_VMC_ERROR: SOAP_ERROR 16:44:29.061 [7452.8124] vmwareLogger: SOAP 1.1 fault: "":ServerFaultCode [no subcode] "The object has already been deleted or has not been completely created" Detail: <ManagedObjectNotFoundFault xmlns="urn:vim25" xsi:type="ManagedObjectNotFound"><obj type="HostSystem">Null</obj></ManagedObjectNotFoundFault> 16:44:29.061 [7452.8124] vmwareLogger: getObjectProperty: Could not get property summary for, mor=<Null><HostSystem> 16:44:29.061 [7452.8124] vmwareLogger: RetrieveDcMorAndObjMorFromPath: SYM_VMC_ERROR: FAILED_TO_GET_OBJECT_PROPERTY 16:44:29.061 [7452.8124] vmwareLogger: GetConfigTargetNetworkDetailsAPI: SYM_VMC_ERROR: FAILED_TO_GET_OBJECT_PROPERTY 16:44:29.061 [7452.8124] vmcGetConfigTargetNetworkDetails failed for ESXHQ-01.CDGM.LOCAL with 74 16:44:30.356 [7452.8124] vmwareLogger: RetrieveObjPropertiesEx: for mor = Null failed, SYM_VMC_ERROR: SOAP_ERROR 16:44:30.356 [7452.8124] vmwareLogger: SOAP 1.1 fault: "":ServerFaultCode [no subcode] "The object has already been deleted or has not been completely created" Detail: <ManagedObjectNotFoundFault xmlns="urn:vim25" xsi:type="ManagedObjectNotFound"><obj type="HostSystem">Null</obj></ManagedObjectNotFoundFault> 16:44:30.356 [7452.8124] vmwareLogger: getObjectProperty: Could not get property summary for, mor=<Null><HostSystem> 16:44:30.356 [7452.8124] vmwareLogger: RetrieveDcMorAndObjMorFromPath: SYM_VMC_ERROR: FAILED_TO_GET_OBJECT_PROPERTY 16:44:30.356 [7452.8124] vmwareLogger: GetConfigTargetDvPortGroupDetailsAPI: SYM_VMC_ERROR: FAILED_TO_GET_OBJECT_PROPERTY 16:44:30.356 [7452.8124] vmcGetConfigTargetDvPortGroupDetails failed for ESXHQ-01.CDGM.LOCAL with 74 16:44:30.356 [7452.8124] generateServerFiles: listNetworks failed with 11 16:44:30.356 [7452.8124] dovSphereDisconnect: disconnect for ESXHQ-01.CDGM.LOCAL completed with flags 0 and status 0 16:44:30.356 [7452.8124] <2> browseDatastores: generateServerFiles returned 11 16:44:30.356 [7452.8124] <2> bpVMutil main: EXIT STATUS 0: the requested operation was successfully completed 16:44:33.498 [1100.6816] <2> logparams: C:\Program Files\Veritas\NetBackup\bin\bpVMutil.exe 5632 ESXHQ-01.CDGM.LOCAL ESXHQ-01.CDGM.LOCAL 16:44:33.498 [1100.6816] virt_test_log: log function is called 16:44:33.498 [1100.6816] <2> bpVMutil main: cmd = 22 ESXMount = ESXHQ-01.CDGM.LOCAL ESXserver = ESXHQ-01.CDGM.LOCAL, flags = 0 16:44:33.498 [1100.6816] generateServerFiles: get_id_lock returned 0: -> wait lock timeout value: 15 minutes -> WRITE LOCK ESXHQ-01.CDGM.LOCAL_lock fd = 248 -> lockname = ESXHQ-01.CDGM.LOCAL_lock 16:44:33.498 [1100.6816] generateServerFiles: checking file C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\ESXHQ-01.CDGM.LOCAL_datas_tree.xml 16:44:33.498 [1100.6816] generateServerFiles: checking file C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\ESXHQ-01.CDGM.LOCAL_net_tree.xml 16:44:33.498 [1100.6816] <2> browseDatastoreTree: get_id_lock returned 0: -> wait lock timeout value: 30 minutes -> WRITE LOCK ESXHQ-01.CDGM.LOCAL_lock fd = 248 -> lockname = ESXHQ-01.CDGM.LOCAL_lock 16:44:33.498 [1100.6816] <2> browseDatastoreTree: fileCOPY of C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\ESXHQ-01.CDGM.LOCAL_datas_tree.xml to C:\Windows\TEMP\VMutl-01100344246273498816000000000-a06816 returned 0 16:44:33.498 [1100.6816] <2> bpVMutil main: EXIT STATUS 0: the requested operation was successfully completed What steps should I take to get this done? and suggest me the best. Thanks in Advance PhanuphanSolved3.8KViews0likes4Comments
AD GRT - vmware snapshot
Hi, this must be a subject discussed countless of times- regardless I havn't quite found the answers I was looking for. I am trying to figure out if I can and should backup Active Directory using vmware snapshots, and if it is possible to use GRT with snapshots. this article firmly states against it: http://techgenix.com/dont-snapshot-domain-controllers-96/ however this old thread I found: https://vox.veritas.com/t5/Backup-Exec/Backing-up-AD-in-a-VMWare-VM-Using-GRT-Causes-Job-Warnings-Safe/td-p/529685 suggests it's fine to use snapshots to backup AD. moreover it suggest that with "active directory agent license installed on the media server" I will be able to use GRT. so I am left with two main questions: 1) can and should I backup AD with vmware snapshots? 2) what is this "active directory agent license installed on the media server"- does RahulG mean a regular netbackup client installed on the DC or is it an actual agent on the media server capable of expanding the snapshot to restore single users or etc.? thanks in advanced for the helpSolved3.8KViews0likes7CommentsvSphere 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!3.8KViews3likes19Comments
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!