Netbackup 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 VMCFO_VDR” Thanks,Solved7.1KViews2likes6Comments
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: 1566.7KViews0likes8Comments
Error bpbrm(pid=7528)
Hi all, we found error like this at Netbackup 7. We never found the error when using netbackup 6.5. Herewith the error : 5/31/2010 8:45:24 AM - Error bpbrm(pid=7528) from client netbackup-srv: ERR - failure reading file: E:\DRIB\file-Full Database Backup 20100202 (WIN32 2: The system cannot find the file specified. ) 5/31/2010 8:45:25 AM - Error bpbrm(pid=7528) from client netbackup-srv: ERR - Snapshot Error while reading file: GLOBALROOT\Device\HarddiskVolumeShadowCopy15\DRI\file-Full Database Backup 20100202 5/31/2010 8:45:26 AM - Critical bpbrm(pid=7528) from client netbackup-srv: FTL - Backup operation aborted! 5/31/2010 8:45:35 AM - Error bpbrm(pid=7528) could not send server status message 5/31/2010 8:45:42 AM - end writing; write time: 00:02:06 snapshot error encountered(156) Anyone has ever experienced like this ? Regards, AbbasSolved6.6KViews2likes8Comments
Backup Exec hangs while backing up VMware VMs (snapshot)
We are having this issue for weeks/months now : while processing a backup-to-disk job using Backup Exec 2012 SP1a VMware infrastructure agent the backup process hangs at some point. We are running a VMware 5 (Build 768111) environment with a fibre channel SAN which is being backed up by a Windows 2008 R2 BE2012 SP1a (Verion 14.0 Rev. 1798 64 Bit) VM. At some point in the backup process - and different VMs - I can see that there is no progress anymore for hours or days in my vSphere client (percentage of the job freezes) and in BE the MB/min indicator decreases and no changes to the number of backed up Bytes. This is only when using backup-to-disk, which actually is a (VMFS 5) partition within the BE virtual machine (drive letter V: size 1,5TB). Last time it stopped at 95% of our backend Exchange 2010 server (running, approx. 300GB), last time before it stopped while backing up a powered off Windows Server 2003 test system (approx. 30GB). The only thing to do is hit cancel at the BE machine (which actually wouldn't cancel or stop the job), then reboot the BE machine, cancel the VMware job in vSphere client and then "delete" the VMware snapshot to return to merge the changes on the disks. Gladly we back up all data (non-VMs) separately directly to tape (VMware Direct I/O connected SCSI LTO juke box), so I have at least my data at hand, but I don't understand why even a snapshot of a powered off system halts the Symantec VMware job. Snapshots manually initiated in vSphere client have not been an issue yet, disk space is available, too. Have not found any similar problem desciption in Google... Any help really appreaciated!Solved6.3KViews1like15CommentsBackuping up raw device mapped disk attached to a VM client
I need some knowledge: I'm using Netbackup 7.5.0.3 on Windows Server 2008 with a master and 2 media servers that are my VMWare backup hosts. I. - Backing up VM's with attached RDM disk: I've read the VMWare and snapshot client documentation but I'm still a little unclear about how to backup RDM (raw device mapped) disk. From what I read, I have 2 options: 1. - Install Netbackup client within the VM and backup the VM as I would a physical server. (not preferred.) 2. - Create an alternate backup client that has same OS and patch rev (or higher) that has access to the RDM to utilize offhost snapshot backups. My questions are: a. - Why can't I backup the RDM disk with a VMWare policy? b. - Can I backup the OS filesystem with a VMWare policy and the RDM disk with an alternate client so I can utilize offhost snapshots? c. Are there any differences if the RDM disk is physical or virtual?Solved6.3KViews1like5Comments
Error 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.3KViews0likes8CommentsGRT-Enabled Backups on GPT-Partitioned VMware-VMDKs
Hi, I just run into the Issue, that GRT-Enabled Backups via AVVI on GPT-Partitioned VMDKsin VMware fail with an exception and are not supported as stated in the SCL. Does anyone know the technical background of this limitation and if there might be a chance to get this feature later on with another ServicePack ? I wonder because it seems to be possible with MicsoroftHyper-V based VMs (according to the SCL:http://www.symantec.com/business/support/index?page=content&id=TECH217478&key=15047&basecat=COMPATIBILITY_LIST&actp=LIST ). The problemis, that 2TB+ Volumes are getting more common even for smaller customers and doing agent level backups in VMs prevent me from doing SAN-basedbackups, which are way faster especially with FC. Switching off GRT is also not an option as this is one of the most basic backup features and about 75% of my restore jobs are single-file or directory based restores on file servers. Source:http://www.symantec.com/business/support/index?page=content&id=TECH69498&actp=search&viewlocale=en_US&searchid=1415000582760 Regards, intiSolved6.1KViews3likes20Comments
Status 42 on VMware backups (somewhat inconsistent)
Solaris Master - 7.6.0.3 3 x 5220 appliance media servers - 2.6.0.3 Appliances are the VMware Backup Hosts All VMware backups are done via SAN transport mode Job details from a "representative" Status 42 failure: 11/13/2014 12:06:09 - Info nbjm (pid=19785) starting backup job (jobid=8025958) for client denjsit15, policy RETRY-VMware-DEV, schedule Full 11/13/2014 12:06:09 - estimated 0 kbytes needed 11/13/2014 12:06:09 - Info nbjm (pid=19785) started backup (backupid=denjsit15_1415905569) job for client denjsit15, policy RETRY-VMware-DEV, schedule Full on storage unit stu_disk_densyma02p 11/13/2014 12:06:10 - started process bpbrm (pid=12111) 11/13/2014 12:06:11 - Info bpbrm (pid=12111) denjsit15 is the host to backup data from 11/13/2014 12:06:11 - Info bpbrm (pid=12111) reading file list for client 11/13/2014 12:06:11 - Info bpbrm (pid=12111) starting bpbkar on client 11/13/2014 12:06:11 - Info bpbkar (pid=12146) Backup started 11/13/2014 12:06:11 - connecting 11/13/2014 12:06:11 - connected; connect time: 0:00:00 11/13/2014 12:06:12 - Info bpbrm (pid=12111) bptm pid: 12147 11/13/2014 12:06:12 - Info bptm (pid=12147) start 11/13/2014 12:06:15 - Info bptm (pid=12147) using 524288 data buffer size 11/13/2014 12:06:15 - Info bptm (pid=12147) setting receive network buffer to 262144 bytes 11/13/2014 12:06:15 - Info bptm (pid=12147) using 128 data buffers 11/13/2014 12:06:17 - Info bptm (pid=12147) start backup 11/13/2014 12:06:26 - begin writing 11/13/2014 12:07:24 - Info bpbkar (pid=12146) 0 entries sent to bpdbm 11/13/2014 12:07:24 - Info bpbkar (pid=12146) 90 entries sent to bpdbm 11/13/2014 12:07:24 - Info bpbkar (pid=12146) 91 entries sent to bpdbm 11/13/2014 12:07:31 - Info bpbkar (pid=12146) 95091 entries sent to bpdbm 11/13/2014 12:07:40 - Info bpbkar (pid=12146) 190091 entries sent to bpdbm 11/13/2014 12:07:47 - Info bpbkar (pid=12146) 272387 entries sent to bpdbm 11/13/2014 12:07:47 - Info bpbkar (pid=12146) 272388 entries sent to bpdbm 11/13/2014 12:07:50 - Info bpbkar (pid=12146) 287172 entries sent to bpdbm 11/13/2014 12:07:50 - Info bpbkar (pid=12146) 287173 entries sent to bpdbm 11/13/2014 12:07:50 - Info bpbkar (pid=12146) 287232 entries sent to bpdbm 11/13/2014 12:07:50 - Info bpbkar (pid=12146) 287233 entries sent to bpdbm 11/13/2014 12:07:58 - Info bpbkar (pid=12146) 382233 entries sent to bpdbm 11/13/2014 12:08:06 - Info bpbkar (pid=12146) 477233 entries sent to bpdbm 11/13/2014 12:08:14 - Info bpbkar (pid=12146) 558340 entries sent to bpdbm 11/13/2014 12:08:14 - Info bpbkar (pid=12146) 558341 entries sent to bpdbm 11/13/2014 12:08:14 - Info bpbkar (pid=12146) 558348 entries sent to bpdbm 11/13/2014 12:08:14 - Info bpbkar (pid=12146) INF - Transport Type = san 11/13/2014 12:08:14 - Info bpbkar (pid=12146) 558381 entries sent to bpdbm 11/13/2014 12:09:39 - Info bpbkar (pid=12146) 558382 entries sent to bpdbm 11/13/2014 12:13:20 - Info bpbkar (pid=12146) bpbkar waited 10177 times for empty buffer, delayed 29247 times 11/13/2014 12:13:20 - Info bptm (pid=12147) waited for full buffer 6491 times, delayed 17216 times 11/13/2014 12:22:35 - Error bptm (pid=12147) get_string() failed, Broken pipe (32), premature end of file encountered 11/13/2014 12:22:35 - Info bptm (pid=12147) EXITING with status 42 <---------- 11/13/2014 12:22:38 - Info densyma02p (pid=12147) StorageServer=PureDisk:densyma02p; Report=PDDO Stats (multi-threaded stream used) for (densyma02p): scanned: 23198447 KB, CR sent: 31511 KB, CR sent over FC: 0 KB, dedup: 99.9%, cache hits: 260943 (99.5%) 11/13/2014 12:22:40 - Info bpbkar (pid=0) done 11/13/2014 12:22:40 - Info bpbkar (pid=0) done. status: 42: network read failed 11/13/2014 12:22:40 - end writing; write time: 0:16:14 network read failed (42) I have attached the associated bpbrm, bpbkar, and bptm (I only have included the last 500 lines of the bptm log entries for pid=12147 since on VERBOSE=5 bptm was HUGE for this job). Any help would be greatly appreciated!Solved6KViews1like13CommentsV-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib.
Hello Everyone, Currently we have a server 2008 64bit server with BE 2014 which was upgrade from 2012 and for some strange reason I keep getting this particular error message while backing up a few VMs as you can see below. V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib. VixDiskLib_Read() reported the error: NBD_ERR_DISKLIBV-79-57344-38366 - WARNING: "VMVCB::\\10.0.1.5\VCGuestVm\(DC)ha-datacenter(DC)\vm\SCSMDW\SCSMDW\SM Warehouse-000002.vmdk" is a corrupt file. This file cannot verify. Transport mode 'nbd' was used for the read operation of the disk 'SM Warehouse_1-000002.vmdk' In addition, I have research this particular message and I have not yet found anything online that is exactly what I am having issues with. Furthermore to provide additional background information the issue that I am having with the VM are on an Exsi host that is running version 5.5.5.6KViews0likes17Comments
V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib.
Hello Everyone, Currently we have a server 2008 64bit server with BE 2014 which was upgrade from 2012 and for some strange reason I keep getting this particular error message while backing up a few VMs as you can see below. V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib. VixDiskLib_Read() reported the error: NBD_ERR_DISKLIBV-79-57344-38366 - WARNING: "VMVCB::\\10.0.1.5\VCGuestVm\(DC)ha-datacenter(DC)\vm\SCSMDW\SCSMDW\SM Warehouse-000002.vmdk" is a corrupt file. This file cannot verify. Transport mode 'nbd' was used for the read operation of the disk 'SM Warehouse_1-000002.vmdk' In addition, I have research this particular message and I have not yet found anything online that is exactly what I am having issues with. Furthermore to provide additional background information the issue that I am having with the VM are on an Exsi host that is running version 5.5.