Agent for VMware Virtual Infrastructure

198 Topics

How to backup Powered Off VM in 7.5.0.6
Hi, I Would like to know how the powered off VM backup is working with VADP concept in Netbackup 7.5.0.6? I know VM tools services is important concept to backup VM, if VM is powered off VMtools will be also down because it run in it runs in virtual machine. Please let me know how to backup powered off VM. -Chan
Solved
Chan_backup
11 years ago Place NetBackup
4.3KViews
5likes
3Comments
Netbackup Appliance VMWare configuration / Zoning
Hi All, I'm just looking for some clarification on configuring VMWare backups using the agent. My master is running 7.6.1.1 as are our 5230 Appliances and vSphere is 5.5 so support is not an issue. I've set aside two ports on each appliance for vmware backups so I know where I want to zone to on that end but what else do I zone to ? Do I need to zone in the ESX servers or just the WWN's of the storage arrays ? The VMWare admin guide states the following but isn't very clear. "To use the SAN transport type, set up the datastore on Fibre Channel or iSCSI. In this configuration, the VMware backup host must be able to access the datastore over the SAN." The ESX boxes are already san connected. We tested the agent a few years ago to VTL with a Windows Off-Host server and found it to be slower than just sending it across the LAN but need and want to test it again especially with the 5230's now bedded in. Thanks in advance.
Solved
Kevin_O_Connor
10 years ago Place NetBackup
3.7KViews
4likes
11Comments
vStorage API backups fail with status code 13
vStorage API backup, nbd transfer mode, is failing with error code 13 for the most of the VMs. I get only few successful backups - all on same ESX host. backup speed only max to 1MB/sec so I guess it must be caused by the slowness on the network, and I'm trying to get it fixed on network side. while I'm doing that, I wonder if there are any tunables / settings that I can adjust in NetBackup, so that vStorage API backup waits long enough for the retransmit of data from the datastore, rather than simply throwing out status 13? 7.1.0.3 on Win2kR2x64, media server is the backup host.
Abesama
13 years ago Place NetBackup
372Views
4likes
1Comment
NBU 7.6 for VMware and transport mode SAN
Hi This is my enviroment: Master / Media server on the same host: Windows 2012 R2 physical server with FC dual port connected to a two fabric SAN Brocade 6505. vCenter 5.1 on a virtual machine Windows 2012 R2. Backup virtual machines from 15 ESXi 5.1 host. I want to use SAN transport mode. I find that the only method is configure FC zoning to let's NBU media server access to VMFS-5 formated LUNS by ESXi host. Then, from windows disk administrator console, I found these LUNS and appears like the image I attach to this post. I'm afraid if someone decides mistakenly put online the disk and reformat to NTFS. Is there any way to prevent this problem? My configuration method is correct? Now, I can backup my virtual machines faster than NBD tranport mode, but I need to trust on these settings to aboid problems.
Solved
larjona
10 years ago Place NetBackup
947Views
3likes
2Comments
VMWare Backup Snapshots Incorrectly being cleaned up
Our backups of VMs seem to complete successfully, the snapshots are created and deleted completed according to the NBU logs, but our monitoring tool indicates that some snapshot data is being left behind. Description: Finds VMSN files on the datastore that aren't listed in a Virtual Machine's snapshots Time Executed: Tue, 11 Nov 2014 20:25:13 Current Overall Alert State: ACTIVE Recommendation: It is possible that when some of your snapshots were removed, all associated snapshot file were not cleaned up correctly. There may be opportunities to reclaim storage by removing these files. Alert Active for: 1. Datastore: datastore and vmdk info. The snapshots are not being deleted at all on the host.
Solved
arctics2
10 years ago Place NetBackup
467Views
3likes
1Comment
VADP Snapshot Handling - Remove NBU
NBU 7.1.0.4 (LINUX) / vSphere 5.0 Hi all, I have a couple of questions... We are using the 'Remove NBU' snapshot option within our VADP policies. I just wanted to clarify..will this remove only snapshots that were created by NBU? Or manual snapshots too? Also, some of our VMs seem to crash after a backup if they have existing deltas files... Within vCenter we can see thata create snapshot/remove snapshot task completes successfully, but the next task initiated by NetBackup - 'Consolidate virtual machine disk files'fails with 'The parent virtual disk has been modified since the child was created'. The VM shuts down at this point, and can't be brought back up without some hassle. NetBackup appears to be having issues consolidating snapshots after a backup if deltas are present. Can anyone please explain the process of what should happen when NetBackup encounters this scenario? Thanks! OldMate
old_mate
12 years ago Place NetBackup
558Views
3likes
1Comment
vmware backups status code 13
Hello All Vmware backupscontinuouslyget the error13, before getting status code 156 . Also ndmp backups getting status code 13 What can I do for this issue Thank you Jan 19, 2012 10:04:27 AM - requesting resource dc1bckapp01-hcart3-robot-tld-5 Jan 19, 2012 10:04:27 AM - requesting resource xxxxxx_CLIENT.MAXJOBS.PREVMHKTWEB01 Jan 19, 2012 10:04:27 AM - requesting resource bcksrv01.NBU_POLICY.MAXJOBS.xxxxxx_ALL_DRV_SNAP Jan 19, 2012 10:04:28 AM - granted resource xxxx.NBU_CLIENT.MAXJOBS.xxxxxx Jan 19, 2012 10:04:28 AM - granted resource bcksrv01.NBU_POLICY.MAXJOBS.DC1_VMWARE_xxxxxxx_SNAP Jan 19, 2012 10:04:28 AM - granted resource 002700 Jan 19, 2012 10:04:28 AM - granted resource HP.ULTRIUM4-SCSI.022 Jan 19, 2012 10:04:28 AM - granted resource xxxxx-hcart3-robot-tld-5 Jan 19, 2012 10:04:28 AM - estimated 0 kbytes needed Jan 19, 2012 10:04:28 AM - begin Parent Job Jan 19, 2012 10:04:28 AM - begin Flash Backup Windows: Start Notify Script Jan 19, 2012 10:04:28 AM - started process RUNCMD (pid=14995) Jan 19, 2012 10:04:28 AM - ended process 0 (pid=14995) Operation Status: 0 Jan 19, 2012 10:04:28 AM - end Flash Backup Windows: Start Notify Script; elapsed time 0:00:00 Jan 19, 2012 10:04:28 AM - begin Flash Backup Windows: Step By Condition Operation Status: 0 Jan 19, 2012 10:04:28 AM - end Flash Backup Windows: Step By Condition; elapsed time 0:00:00 Jan 19, 2012 10:04:28 AM - begin Flash Backup Windows: Read File List Operation Status: 0 Jan 19, 2012 10:04:28 AM - end Flash Backup Windows: Read File List; elapsed time 0:00:00 Jan 19, 2012 10:04:28 AM - begin Flash Backup Windows: Create Snapshot Jan 19, 2012 10:03:31 AM - begin Create Snapshot Jan 19, 2012 10:03:32 AM - snapshot backup of client xxxxxx using method VMware Jan 19, 2012 10:04:29 AM - started process bpbrm (pid=6136) Jan 19, 2012 10:05:43 AM - Error bpbrm (pid=6136) socket read failed, An existing connection was forcibly closed by the remote host. (10054) Jan 19, 2012 10:05:44 AM - Error bpbrm (pid=6136) cannot send mail to Jan 19, 2012 10:06:44 AM - end writing Operation Status: 13 Jan 19, 2012 10:06:44 AM - end Create Snapshot; elapsed time 0:03:13 Jan 19, 2012 10:06:44 AM - begin Flash Backup Windows: Stop On Error Operation Status: 0 Jan 19, 2012 10:06:44 AM - end Flash Backup Windows: Stop On Error; elapsed time 0:00:00 Jan 19, 2012 10:06:44 AM - begin Flash Backup Windows: Delete Snapshot On Exit Operation Status: 0 Jan 19, 2012 10:06:44 AM - end Flash Backup Windows: Delete Snapshot On Exit; elapsed time 0:00:00 Jan 19, 2012 10:06:44 AM - begin Flash Backup Windows: End Notify Script Jan 19, 2012 10:06:44 AM - started process RUNCMD (pid=15134) Jan 19, 2012 10:06:44 AM - ended process 0 (pid=15134) Operation Status: 0 Jan 19, 2012 10:06:44 AM - end Flash Backup Windows: End Notify Script; elapsed time 0:00:00 Operation Status: 13 Jan 19, 2012 10:06:44 AM - end Flash Backup Windows: Create Snapshot; elapsed time 0:02:16 file read failed (13)
Nas_lGidiyor
13 years ago Place NetBackup
730Views
3likes
4Comments
VMware backups are failing with status 23 and 6 after Vcenter server upgrade from 5.1 to 5.5 U3B
Issue:- VMwarebackups are failing with status 23 and 6 after Vcenter server upgrade from 5.5 U 3B As per the Netbackup VMware comatibility Matrix, we upgraded our Master and VMware backup host (Windows) from 7.5.0.4 to 7.6.0.4to support Vsphere 5.5 U 3B https://sort.veritas.com/checklist/install/nbu_compatibilityListUpdates Description of Change Date NetBackup Version Start of Support Added support for vSphere 5.5 U3 10/22/2015 NetBackup 7.6.0.2 After the upgrade to Netbackup 7.6.0.4 - VADP backups were started failing with status 6 (23) and later we came to know that Vsphere 5.5 U3b is not supported with Netbackup 7.6.0.2 and there is no official annoncement yet from Veritas related to the support for 5.5 U3b VxMS Logs:- 04:45:29.0441 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2016-01-19T04:45:29.441Z [51500 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to <cs p:000000000246f1a0, TCP:server-vc-01:443>; cnx: (null), error: class Vmacore::Ssl::SSLException(SSL Exception: error:140000DB:SSL routines:SSL routines:short read) 04:45:29.0441 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2016-01-19T04:45:29.441Z [51500 trivia 'Default'] Setting error in state 1 : class Vmacore::Ssl::SSLException(SSL Exception: error:140000DB:SSL routines:SSL routines:short read) 04:45:29.0441 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2016-01-19T04:45:29.441Z [51500 trivia 'ThreadPool'] HandleWork() leaving 04:45:29.0441 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2016-01-19T04:45:29.441Z [51500 trivia 'HttpConnectionPool-000000'] [DecConnectionCount] Number of connections to <cs p:000000000246f1a0, TCP:pru-swi-vc-01:443> decremented to 0 04:45:29.0441 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2016-01-19T04:45:29.441Z [49468 trivia 'transport'] Initializing SSL context 04:45:29.0441 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2016-01-19T04:45:29.441Z [59120 trivia 'ThreadPool'] ThreadPool[idle:4, busy_io:0, busy_long:0] HandleWork(type: 0, fun: class boost::_bi::bind_t<void,class boost::_mfi::mf3<void,class Vmacore::System::ThreadPoolAsio,class boost::shared_ptr<class Vmacore::Exception> const & __ptr64,int,class Vmacore::Functor<void,class Vmacore::Exception * __ptr64,int,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil> const & __ptr64>,class boost::_bi::list4<class boost::_bi::value<class Vmacore::Ref<class Vmacore::System::ThreadPoolAsio> >,class boost::_bi::value<class boost::shared_ptr<class Vmacore::Exception> >,class boost::_bi::value<int>,class boost::_bi::value<class Vmacore::Functor<void,class Vmacore::Exception * __ptr64,int,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil> > > >) 04:45:29.0441 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2016-01-19T04:45:29.441Z [49468 info 'transport'] Connecting to host server-vc-01 on port 443 using protocol https via vim.version.version3 Log from the KM article:-https://www.veritas.com/support/en_US/article.TECH228283 (w.r.t. this article fix for this issue is available from 7.6.1.1, but there is no such document from Veritas saying that Vsphere 5.5 U3b suite is supported from 7.6.1.1 14:58:36.0093 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2015-02-11T14:58:36.093-05:00 [06836 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to <cs p:0000000002854f00, TCP:vcenter5:443>; cnx: (null), error: class Vmacore::Ssl::SSLException(SSL Exception: error:140000DB:SSL routines:SSL routines:short read) 14:58:36.0093 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2015-02-11T14:58:36.093-05:00 [06836 trivia 'Default'] Setting error in state 1 : class Vmacore::Ssl::SSLException(SSL Exception: error:140000DB:SSL routines:SSL routines:short read) 14:58:36.0093 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2015-02-11T14:58:36.093-05:00 [06836 trivia 'vmomi.soapStub[1]'] Request completed [class Vmacore::Http::UserAgentImpl::AsyncSendRequestHelper:0000000003562E98] 14:58:36.0093 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2015-02-11T14:58:36.093-05:00 [06836 trivia 'ThreadPool'] HandleWork() leaving 14:58:36.0093 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2015-02-11T14:58:36.093-05:00 [06836 trivia 'HttpConnectionPool-000000'] [DecConnectionCount] Number of connections to <cs p:0000000002854f00, TCP:vcenter5:443> decremented to 0 14:58:36.0093 : g_vixInterfaceLogger:libvix.cpp:1825 <DEBUG> : [VFM_ESINFO] 2015-02-11T14:58:36.093-05:00 [07260 trivia 'ThreadPool'] ThreadPool[idle:4, busy_io:0, busy_long:0] HandleWork(type: 0, fun: class boost::_bi::bind_t<void,class boost::_mfi::mf3<void,class Vmacore::System::ThreadPoolAsio,class boost::shared_ptr<class Vmacore::Exception> const & __ptr64,int,class Vmacore::Functor<void,class Vmacore::Exception * __ptr64,int,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil> const & __ptr64>,class boost::_bi::list4<class boost::_bi::value<class Vmacore::Ref<class Vmacore::System::ThreadPoolAsio> >,class boost::_bi::value<class boost::shared_ptr<class Vmacore::Exception> >,class boost::_bi::value<int>,class boost::_bi::value<class Vmacore::Functor<void,class Vmacore::Exception * __ptr64,int,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil,class Vmacore::Nil> > > >) Update from Veritas Support:- 1. Customers quite often misinterpret our compatibility lists that show 5.5 U3 as supported from 7.6.0.2 onwards. After releasing U3B VMware decided to rename U3 to U3A which our support statement applies to – but not 3B. 2.Currently Netbackup is not supporting Vsphere 5.5 3b version. With the vSphere 5.5 update 3b release, the support for SSLv3 is disabled by default for all services and ports as a protection against the POODLE vulnerability. Update 3b disables SSLv3 and breaks VDDK communications to vCenter and ESXi.There is a workaround for this problem which might work, but it is still unsupported. You would have to manually re-enable SSLv3 protocol on port 902 on ESXi and port 443 on vCenter. Please refer to TN below for more information. I would have to reiterate, the workaround may be considered as an option instead of rolling back Vcenter upgrade but it is still unsupported by Netbackup. Workaround/Solution:- 1. Do not disable SSLv3 in vCenter until all VMware backup hosts are upgraded to NetBackup version 7.6.1.1 includes VDDK 5.5.4 or above. 2. Upgraded our Master and VMware backup host to 7.6.1.2 and backups are working fine (Our Solution) Knowledge BaseArticles Referred:- https://www.veritas.com/support/en_US/article.TECH228283 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2139396 https://www.veritas.com/support/en_US/article.000025159
kams_240
9 years ago Place NetBackup
1.8KViews
2likes
3Comments
San based data store backup from netbackup
Hi team, I read somewhere , In order to take San based data store backup we need to present those datastore luns to media server . We only need to present the luns to media server or some other step also required?…...those luns should be in read only mode or read/write both?
Solved
Brits
10 years ago Place NetBackup
2.8KViews
2likes
11Comments
VM restore from Incremental backup
Hi Experts, I have recent incremental backups on july 5 and july 4 and full backup on july 3. I want july 5 version of VM. How do i select the vmdk file in java BAR console in netbackup. Can i select only july 5 incremental(such that itwill automatically select july 3 full backup)or do i have to restore july 3 full backup first continued by july 5 incremental backup. Thanks in advance.
Solved
kumarantg
10 years ago Place NetBackup
962Views
2likes
4Comments