Agent for VMware Virtual Infrastructure

782 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
VMware backup failed with error 4207
Hello Team, Backup of some vmware clients is getting failed with error 4207. 05/25/2016 19:39:53 - Critical bpbrm (pid=9848) from client TEST67DC.na.aarp.int: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with -1: Unrecognized error 05/25/2016 19:39:53 - Critical bpbrm (pid=9848) from client TEST67DC.na.aarp.int: FTL - VMware error received: An error occurred while saving the snapshot: Failed to quiesce the virtual machine. 05/25/2016 19:39:53 - Critical bpbrm (pid=9848) from client TEST67DC.na.aarp.int: FTL - vfm_freeze: method: VMware, type: FIM, function: VMware_freeze 05/25/2016 19:39:53 - Critical bpbrm (pid=9848) from client TEST67DC.na.aarp.int: FTL - 05/25/2016 19:39:53 - Critical bpbrm (pid=9848) from client TEST67DC.na.aarp.int: FTL - vfm_freeze: method: VMware, type: FIM, function: VMware_freeze 05/25/2016 19:39:53 - Critical bpbrm (pid=9848) from client TEST67DC.na.aarp.int: FTL - 05/25/2016 19:39:53 - Critical bpbrm (pid=9848) from client TEST67DC.na.aarp.int: FTL - snapshot processing failed, status 156 05/25/2016 19:39:53 - Critical bpbrm (pid=9848) from client TEST67DC.na.aarp.int: FTL - snapshot creation failed, status 156 05/25/2016 19:39:53 - Warning bpbrm (pid=9848) from client TEST67DC.na.aarp.int: WRN - ALL_LOCAL_DRIVES is not frozen 05/25/2016 19:39:53 - Info bpfis (pid=5000) done. status: 156 05/25/2016 19:39:53 - end Application Snapshot: Create Snapshot; elapsed time 0:09:18 05/25/2016 19:39:53 - Info bpfis (pid=5000) done. status: 156: snapshot error encountered 05/25/2016 19:39:53 - end writing Operation Status: 156 05/25/2016 19:39:53 - end Parent Job; elapsed time 0:09:18 05/25/2016 19:39:53 - begin Application Snapshot: Stop On Error Operation Status: 0 05/25/2016 19:39:53 - end Application Snapshot: Stop On Error; elapsed time 0:00:00 05/25/2016 19:39:53 - begin Application Snapshot: Cleanup Resources 05/25/2016 19:39:53 - end Application Snapshot: Cleanup Resources; elapsed time 0:00:00 05/25/2016 19:39:53 - begin Application Snapshot: Delete Snapshot 05/25/2016 19:39:54 - started process bpbrm (pid=8888) 05/25/2016 19:39:55 - Info bpbrm (pid=8888) Starting delete snapshot processing 05/25/2016 19:39:57 - Info bpfis (pid=3068) Backup started 05/25/2016 19:39:57 - Critical bpbrm (pid=8888) from client TEST67DC.na.aarp.int: cannot open F:\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TEST67DC.na.aarp.int_1464222635.1.0 05/25/2016 19:39:57 - Info bpfis (pid=3068) done. status: 4207 05/25/2016 19:39:57 - end Application Snapshot: Delete Snapshot; elapsed time 0:00:04 05/25/2016 19:39:57 - Info bpfis (pid=3068) done. status: 4207: Could not fetch snapshot metadata or state files 05/25/2016 19:39:57 - end writing Operation Status: 4207 Operation Status: 156
Sharad_Singh7
6 years ago Place NetBackup
6.7KViews
0likes
8Comments
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
7 years ago Place Backup Exec
4KViews
0likes
5Comments
CIFS share backup in Netbackup
hi Team, I have a plan to take CIFS share backup. The method choosed is to map CIFSto any VMand get backed up as file level . is it possible ? does it require license also ? Regards Brits
Solved
Brits
8 years ago Place NetBackup
5KViews
1like
12Comments
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
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
Quires about Netbackup VMware Backup
NBU Version:- 7.6.0.1 OS: Solaris 10 Currently we have configured a VMware backup using the automatic selection in the policy and the selection is based on the datastore name. Here My question is 1. how to exclude a particular VM server backup when we configured a datastore level backup. 2. Does Netbackup accelator will work with basic disk for VMware backup
Solved
rajkumar3314
9 years ago Place NetBackup
604Views
0likes
2Comments
Is "SYMCquiesce utility" included in Netbackup Client Software?
Hi, I would like to know if SYMCquiesce utility is included in Netbackup (7.6 or later) Client Software or not. Thanks! Iván Yañez
Solved
everis_ITS
9 years ago Place NetBackup
884Views
0likes
2Comments
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
Policy vaildation failed due to EMM status 213 storage units are not available
Hi Problem: ====== Policy vaildation failed due to EMM status 213 storage units are not available. Following the below steps while creating the netbackup policy Steps: ----- 1.Added the ESXI host under master server and 2.Click on virtual machine access and provided ESXI credentials. 3.Restarted netbackup services using below link https://www.veritas.com/support/en_US/article.TECH217024 4.Before trying to take VM backup's running on that host,need to create policy for VM backup 5.while Creating the policy,getting vaidation failed message on the screen. Attached necessary screen shot to this forum.Please let me know your comments on the same. Thanks koti
Solved
chebrolu
9 years ago Place NetBackup
3KViews
0likes
27Comments