VMware VM "needs consolidation" after backup failure
Has anyone else run into this issue? VM backup fails with a "Status 13" or "Status 156" or "Status 40" - I have several hundred VMs and only a few end up in this state during a backup window. No snapshots show up in Snapshot Manager on the VMs that have this error. When consolidation is attempted VMware throws a "Unable to access file <unspecified filename> since it is locked" error. The "fix" for us has been to run "services.sh restart" on the ESXi server - this unlocks the file - then manually consolidating the VM. Sounds a lot like this issue: https://www-secure.symantec.com/connect/forums/problem-backup-virtual-machine-when-vm-convert-status-consolidate Master: 7.6.0.2 on Solaris 10 Media: 2.6.0.2 on 5220 Appliances17KViews3likes11CommentsVirtual Machines going out of network during snapshot backup
Has anyone experienced the Virtual machines going out of network during the backup using "VMware" policy. Apparently , the Windows VMs losing connectivity for a little while and coming back online and the Linux VMs becoming unresponsive.Solved12KViews1like7CommentsVery Slow VM Backups
Hi, We are currently using Network based VM backups rather than SAN based, the Backup Host is a Windows 2008 server running NBU7.5.0.5 and has full access to the ESX servers, I have several policies set up including VIP's for covering the VM's. The back bone is a 1Gb LAN, the Backup Host is SAN attached to an HP VLS12000 which is emulating LTO4 drives, this is on 4Gb F/C When backing up the VM's I am only seeing on average 1.5M/s throughput, we have standard clients that are using the conventional NBU method whuch reach over 40M/s through the same medium. Just wondered if there were any tuning or other paramaters that we need to look at with the VM backups to speed them up. KevSolved9.8KViews1like22CommentsMinimum permission to backup a MS-SQL database using NetBackup
Any bad-developed application is avoiding the permission issues using the most intrusive role. In a security strategy, the main goal is to assign the minimum necessary roles for each login. The RDBMS MS-SQL Server allows to maintaing several specific databases in one specific instance, with a correct permission granularity. To maintain this granularity, SQL Server 2005 splited the system admin role in several less intrusive server roles and db roles. Now, a backup operator is able to backup a database without accessing to the data of this database. The db_backupoperator database role is only necessary. The list of the databases is available through the public permission in the master..sysdatabases system table. In the document "Veritas NetBackup™ for Microsoft SQL Server Administrator’s Guide", the permission issue is evasive : "When the NetBackup scheduler is used, backup operations are launched from a daemon process called the NetBackup Client Service. You must ensure that the Client Service has SQL Server privileges to perform backup and restore operations. If you are using integrated security, then you must ensure that the NetBackup Client Service specifies a Windows account that has been granted SQL Server administrative privileges." In the technote http://www.symantec.com/docs/TECH43512, you're specifying "Any logon that requires permissions to perform backup or restore operations should be provided membership in the following SQL Server roles: Server Role : sysadmin DB role : db_backupoperator, dbo_owner Permissions required for performing restore - Server role : sysadmin, dbcreator DB role : db_owner" My question : do you really understand something about the MS-SQL permission ? Why do you need the sysadmin permission ? If it's really necessary, why do you need the dbcreator (included in the sysadmin) ? Why the db_backupoperator and the db_owner ? In fact, only the db role db_backupoperator is necessary, in a MS-SQL point of view. We experimented some hard failure on production applying the sysadmin permission in the Netbackup Logins (client VaultAdmin) : a modification in the sysusers tables is done, replacing the db_owner database role with and changing the db owner to an non-existent dbo user (technically, the dbo'sysusers.sid was replace on each database from 0x01 to the vaultadmin'sid.) Did you plan to implement a correct security in a future version of your product ? Did you already provide a patch for this issue ? Thanks in advance for your answer. Fadace9KViews1like6CommentsVmware backup failed - error code 156
Setup: Master server netbackup version : 7.5 Vcenter server : windows 2008 r2 Esxi version : 5.1 Proxy server : windows 2008 r2 ( NBU client 7.5) There are 8 esxi servers and more than 30 VMs. Backup is taken for around 20 VMs, in which backup is failing for 5 vms with the same error. Troubleshooting steps followed till now: 1) The backup is failing with the below error. Netbackup job details Critical bpbrm (pid=2361) from client XXXXX: FTL - VMware snapshot failed: SYM_VMC_TASK_REACHED_ERROR_STATE 10/07/2013 16:21:38 - Critical bpbrm (pid=2361) from client XXXXX: FTL - VMware error received: An error occurred while quiescing the virtual machine. See the virtual machine's event log for details. 10/07/2013 16:21:38 - Critical bpbrm (pid=2361) from client XXXXX: FTL - snapshot creation failed, status 156 10/07/2013 16:21:38 - Warning bpbrm (pid=2361) from client XXXXX: WRN - ALL_LOCAL_DRIVES is not frozen VMWARE snap shot creation failed: Vmware error: The guest OS has reported an error during quiescing. The error code was: 3 The error message was: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. 2) Tried to take snapshot(with quiesce option enabled) in the VM from Vsphere client GUI and it completed successfully. 3) Verified the disk space availability more than 70 GB available. 4) Rebooted one of the VM and retired the backup. But still backup failed with same error. http://www.symantec.com/connect/forums/status-code-156 5) In the above article they have faced the same issue, after reinstalling the vmware tools it worked. 6) Reinstalled the VM tools but still same issue.Solved8.4KViews1like4CommentsHow to find VMware API version used?
We are discussing a matter with VMware support, and they want to verify which VMware VDDK is being used by NetBackup (backup hosts Unix and Windows performing VMware backups), is there a matrix documenting this or a way to verify the version used on the backup hosts? I would like a universal solution, so I know this for future reference as well...Solved7.7KViews0likes3CommentsVMware delete snapshot failed
We are running Netbackup 7.6.0.2 on windows server 2008 SP1 R2. My problem is with the VMs backup to msdp disk. The msdp disk is located in media server that also got Netbackup 7.6.0.2. Before we upgraded to 7.6.0.2 everything worked fine. Since the upgrade, I get now in some clients errors in delete snapshot after the backup. This is the Detiales status of the job that shows the error: 23/06/2014 18:35:36 - end Application Snapshot, Resources For Cleanup; elapsed time: 0:00:00 23/06/2014 18:35:36 - begin Application Snapshot, Delete Snapshot 23/06/2014 18:35:38 - started process bpbrm (10352) 23/06/2014 18:35:40 - Info bpbrm(pid=10352) Starting delete snapshot processing 23/06/2014 18:35:41 - Info bpfis(pid=11064) Backup started 23/06/2014 18:35:48 - Info bpbrm(pid=10352) INF - vmwareLogger: RegisterExtensionAPI: SYM_VMC_ERROR: SOAP_ERROR 23/06/2014 18:35:48 - Info bpbrm(pid=10352) INF - vmwareLogger: SOAP 1.1 fault: "":ServerFaultCode [no subcode] 23/06/2014 18:50:57 - Critical bpbrm(pid=10352) from client san-manager: VMware_thaw: VMware delete snapshot failed: Unrecognized error 23/06/2014 18:51:00 - Info bpfis(pid=11064) done. status: 0 23/06/2014 18:51:00 - end Application Snapshot, Delete Snapshot; elapsed time: 0:15:24 23/06/2014 18:51:00 - Info bpfis(pid=11064) done. status: 0: the requested operation was successfully completed 23/06/2014 18:51:00 - end writing Status 0 23/06/2014 18:51:00 - end operation Status 0 23/06/2014 18:51:00 - end operation the requested operation was successfully completed(0) Please adviseSolved7.1KViews2likes11CommentsNetbackup VMWARE backups failing with snapshot error 156
Hi All, Please can someone urgently assist, I currently setup a brand new Netbackup Environment, -Netbackup 7.5.0.4. -Clustered Solaris Master Server -Windows 2008 R2 Backup Host -Vcenter 5.1 VM Datastores have been presented to the Backup Host, Diskpart automount disable and automount scrub have been run on the Backup Host, Credentials for the Vcenter Server have been entered and vailidated successfully, The Vmware policy can browse for The Vm's, Transport type set to SAN and using Display name. Once a backup kicks off it fails with a 156 error, The bpfis log shows the below message “VMware_freeze: Unable to locate VM CFO_VDR” Thanks,Solved7.1KViews2likes6CommentsError 156 and 4207
Hi I am encountering an error in Netbackup with the VmWare snapshot. Had a peak and i find 2 errors, 156 which is generally an error getting the snapshot, and the another error which says the following: Critical bpbrm (pid=35437) from client SVVTPOBBE03: FTL - cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.SVVTPOBBE03_1436968819.1.0 What i dont understand is that this client is a Windows 2008 server, why is it looking up for the state file in /usr/openv...... location? Sins this client is a windows server, it should have been looking for this state file in something similar to C:/programfiles........ location. Will appreciate help here. Thanks.Solved6.4KViews0likes8Comments