VMware backup failures with status code 200
Having a heck of a time trying to figure this out. 14 of my 21 VMware policies are failing with a status code 200 for some reason. Credentials are good and we can do a test query with no issues. Windows 2012 VMware Backup Host 5.5 Update 2 7.6.0.2 and I verified the VDDK is 5.5.0 I have attached all of the logs that would actually run. I cranked VXMS up to 5, but no log was created as I am guessing it just doesnt get that far into the process. Detailed Job Status: 07/22/2015 11:00:59 - Info nbjm (pid=1310) starting backup job (jobid=3391315) for client MEDIA_SERVER, policy Omaha_VMware_INFOBLOX, schedule Full_Daily 07/22/2015 11:00:59 - Info nbjm (pid=1310) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=3391315, request id:{D84F647C-308A-11E5-9F49-002128A6F97C}) 07/22/2015 11:00:59 - requesting resource XP53TAPE009 07/22/2015 11:00:59 - requesting resource xp53tape001.NBU_POLICY.MAXJOBS.Omaha_VMware_INFOBLOX 07/22/2015 11:00:59 - granted resource xp53tape001.NBU_POLICY.MAXJOBS.Omaha_VMware_INFOBLOX 07/22/2015 11:00:59 - estimated 11832060 kbytes needed 07/22/2015 11:00:59 - begin Parent Job 07/22/2015 11:00:59 - begin Application Resolver: Start Notify Script 07/22/2015 11:01:00 - Info RUNCMD (pid=15674) started 07/22/2015 11:01:00 - Info RUNCMD (pid=15674) exiting with status: 0 Operation Status: 0 07/22/2015 11:01:00 - end Application Resolver: Start Notify Script; elapsed time 0:00:01 07/22/2015 11:01:00 - begin Application Resolver: Step By Condition Operation Status: 0 07/22/2015 11:01:00 - end Application Resolver: Step By Condition; elapsed time 0:00:00 07/22/2015 11:01:00 - begin Application Resolver: Resolver Discovery Operation Status: 0 07/22/2015 12:31:04 - end Application Resolver: Resolver Discovery; elapsed time 1:30:04 07/22/2015 12:31:04 - begin Application Resolver: Policy Execution Manager Preprocessed 07/22/2015 12:31:04 - Warning nbpem (pid=1367) VM retrieval failed, server = [53apps178vm]. Operation Status: 200 07/22/2015 12:31:04 - end Application Resolver: Policy Execution Manager Preprocessed; elapsed time 0:00:00 07/22/2015 12:31:04 - begin Application Resolver: Stop On Error Operation Status: 0 07/22/2015 12:31:04 - end Application Resolver: Stop On Error; elapsed time 0:00:00 07/22/2015 12:31:04 - begin Application Resolver: End Notify Script 07/22/2015 12:31:04 - Info RUNCMD (pid=27555) started 07/22/2015 12:31:04 - Info RUNCMD (pid=27555) exiting with status: 0 Operation Status: 0 07/22/2015 12:31:04 - end Application Resolver: End Notify Script; elapsed time 0:00:00 Operation Status: 200 07/22/2015 12:31:04 - end Parent Job; elapsed time 1:30:05 scheduler found no backups due to run (200)3.3KViews0likes12Commentssnapshot error encountered (156)
Hello Friends, i am facing an issue in VMWare VSphereBackup issue with the error code snampshot error encountered - 156. Master Server :- 7.6.1.1 / Windows 2008 Enterprise 64 bit Media Server:- 7.6.1.1/Red Hat Linux VMWare : - VMWare VSphere 6.0 Job Details: - 5/25/2016 1:31:05 PM - Info nbjm(pid=6932) starting backup job (jobid=872704) for client pbad-vc, policy VMWare-vCenter, schedule Daily 5/25/2016 1:31:05 PM - Info nbjm(pid=6932) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=872704, request id:{02BE2026-FC59-47A1-A179-F4F9CA96A5E3}) 5/25/2016 1:31:05 PM - requesting resource pbad_fsmedia_Dedup_STU 5/25/2016 1:31:05 PM - requesting resource pbad-netbackup.pbad.sbg.com.sa.NBU_CLIENT.MAXJOBS.pbad-vc 5/25/2016 1:31:05 PM - requesting resource pbad-netbackup.pbad.sbg.com.sa.NBU_POLICY.MAXJOBS.VMWare-vCenter 5/25/2016 1:31:05 PM - granted resource pbad-netbackup.pbad.sbg.com.sa.NBU_CLIENT.MAXJOBS.pbad-vc 5/25/2016 1:31:05 PM - granted resource pbad-netbackup.pbad.sbg.com.sa.NBU_POLICY.MAXJOBS.VMWare-vCenter 5/25/2016 1:31:05 PM - granted resource MediaID=@aaaay;DiskVolume=PureDiskVolume;DiskPool=pbad_fsmedia_Dedup_Pool;Path=PureDiskVolume;StorageServer=pbad-fsmedia.pbad.sbg.com.sa;MediaServer=pbad-fsmedia.pbad.sbg.com.sa 5/25/2016 1:31:05 PM - granted resource pbad_fsmedia_Dedup_STU 5/25/2016 1:31:05 PM - estimated 0 Kbytes needed 5/25/2016 1:31:05 PM - begin Parent Job 5/25/2016 1:31:05 PM - begin VMware, Start Notify Script 5/25/2016 1:31:05 PM - started 5/25/2016 1:31:06 PM - Info RUNCMD(pid=15444) started 5/25/2016 1:31:07 PM - Info RUNCMD(pid=15444) exiting with status: 0 Status 0 5/25/2016 1:31:07 PM - end VMware, Start Notify Script; elapsed time: 0:00:02 5/25/2016 1:31:07 PM - begin VMware, Step By Condition Status 0 5/25/2016 1:31:07 PM - end VMware, Step By Condition; elapsed time: 0:00:00 5/25/2016 1:31:07 PM - begin VMware, Read File List Status 0 5/25/2016 1:31:07 PM - end VMware, Read File List; elapsed time: 0:00:00 5/25/2016 1:31:07 PM - begin VMware, Create Snapshot 5/25/2016 1:31:08 PM - started process bpbrm (12023) 5/25/2016 1:33:57 PM - end writing Status 156 5/25/2016 1:33:57 PM - end VMware, Create Snapshot; elapsed time: 0:02:50 5/25/2016 1:33:57 PM - begin VMware, Stop On Error Status 0 5/25/2016 1:33:57 PM - end VMware, Stop On Error; elapsed time: 0:00:00 5/25/2016 1:33:57 PM - begin VMware, Delete Snapshot 5/25/2016 1:33:59 PM - started process bpbrm (13061) 5/25/2016 1:34:01 PM - end writing Status 4207 5/25/2016 1:34:01 PM - end VMware, Delete Snapshot; elapsed time: 0:00:04 5/25/2016 1:34:01 PM - begin VMware, End Notify Script 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) pbad-vc is the host to backup data from 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) reading file list for client 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) start bpfis on client 5/25/2016 1:49:46 PM - Info bpbrm(pid=12023) Starting create snapshot processing 5/25/2016 1:49:48 PM - Info bpfis(pid=12029) Backup started 5/25/2016 1:49:48 PM - snapshot backup of client pbad-vc using method VMware_v2 5/25/2016 1:49:52 PM - Info bpbrm(pid=12023) INF - vmwareLogger: ChangeTracking not supported 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with -1: Unrecognized error 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - VMware error received: The operation is not allowed in the current state. 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - snapshot processing failed, status 156 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - snapshot creation failed, status 156 5/25/2016 1:52:32 PM - Warning bpbrm(pid=12023) from client pbad-vc: WRN - ALL_LOCAL_DRIVES is not frozen 5/25/2016 1:52:32 PM - Info bpfis(pid=12029) done. status: 156 5/25/2016 1:52:32 PM - end VMware, End Notify Script; elapsed time: 0:18:31 5/25/2016 1:52:32 PM - Info bpfis(pid=12029) done. status: 156: snapshot error encountered 5/25/2016 1:52:35 PM - Info bpbrm(pid=13061) Starting delete snapshot processing 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) Backup started 5/25/2016 1:52:35 PM - Critical bpbrm(pid=13061) from client pbad-vc: cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.pbad-vc_1464172265.1.0 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) done. status: 4207 5/25/2016 1:52:35 PM - end Parent Job; elapsed time: 0:21:30 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) done. status: 4207: Could not fetch snapshot metadata or state files 5/25/2016 1:34:01 PM - Info RUNCMD(pid=4756) started 5/25/2016 1:34:02 PM - Info RUNCMD(pid=4756) exiting with status: 0 Status 0 5/25/2016 1:34:02 PM - end Parent Job; elapsed time: 0:02:57 Status 156 5/25/2016 1:34:02 PM - end Parent Job; elapsed time: 0:02:57 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) pbad-vc is the host to backup data from 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) reading file list for client 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) start bpfis on client 5/25/2016 1:49:46 PM - Info bpbrm(pid=12023) Starting create snapshot processing 5/25/2016 1:49:48 PM - Info bpfis(pid=12029) Backup started 5/25/2016 1:49:48 PM - snapshot backup of client pbad-vc using method VMware_v2 5/25/2016 1:49:52 PM - Info bpbrm(pid=12023) INF - vmwareLogger: ChangeTracking not supported 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with -1: Unrecognized error 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - VMware error received: The operation is not allowed in the current state. 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - snapshot processing failed, status 156 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - snapshot creation failed, status 156 5/25/2016 1:52:32 PM - Warning bpbrm(pid=12023) from client pbad-vc: WRN - ALL_LOCAL_DRIVES is not frozen 5/25/2016 1:52:32 PM - Info bpfis(pid=12029) done. status: 156 5/25/2016 1:52:32 PM - end operation 5/25/2016 1:52:32 PM - Info bpfis(pid=12029) done. status: 156: snapshot error encountered 5/25/2016 1:52:35 PM - Info bpbrm(pid=13061) Starting delete snapshot processing 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) Backup started 5/25/2016 1:52:35 PM - Critical bpbrm(pid=13061) from client pbad-vc: cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.pbad-vc_1464172265.1.0 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) done. status: 4207 5/25/2016 1:52:35 PM - end operation 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) done. status: 4207: Could not fetch snapshot metadata or state files snapshot error encountered (156) Please help me to resolve the above issue.Solved8.4KViews1like24CommentsNetbackup single file restore from linux
Hi, I am experiencing an issuewhile doingsingle file restore from Linux VM. I am using the following: Netbackup 7.6.0.2 on Windows 2008 server Backup policy - VMware (enabled file recovery) What i am trying to do is restore a single file using Backup, Archive and Restore client on my Master server. I know that restore on the linux VM doesn't work if i don't have an agent installed, that is why the destination of the restore is the master server itself. Nevertheless, my restore is failing momentarily with errors 2820, 2817,2800.The error number depends on the restore policy I am using (VMware, Standard, Flashbackup). VMware policy restore error (2820) FlashBackup-Windows policy restore error (2817) Standard policy restore error (2800) Can anyone help me with this issue? Regards, JanaSolved3.7KViews0likes6CommentsLow Scratch Script
Hello, I am looking for a Script or way to monitor our scratch poolto send an alert(email) when remaining available tapes reach a threshold of 8. We are running NB 7.6.0.1. I am New to the Netbackup world any advice or direction would be appreciated. ThanksSolved2.6KViews2likes7CommentsMonitoring unfinished replication progress
Hello Have somebody found a way to monitor the progress of unfinished replication ? Know there is some reports in OpsCenter, but they all seem be on the complete images. Where I am looking for: Kilobytes transferred, number of fragments transferred or simllar to tell me how far a long the image in progress is. Have looked at nbstlutil/nbstl list options, the support site, connect and of course google search without luck. Regards Michael1.5KViews1like16CommentsUnable to restore files with unrecognized characters/symbols
NetBackup-RedHat2.6.18 7.6.0.4 There are a few files that I could not recognized e.g.: "5�" "6�" "7�" that will cause restoration failures. At first I though those files are corrupted so I choose another date for other backup images during date selection. A quick google search hinted that these could be chinese characters. Including these files will result in "status: 186 - tar received no data" or "bpcd on backup01 exited with status 21: socket open failed" How do I go about restoring these files? Thanks for any help.909Views0likes3CommentsUpgrading NetBackup 7.6.1 to 8.3
Hi Experts, Please see below queries if you have experienced this: One Customer has NetBackup is 7.6.1 but running in Windows 2008 R2. Their questions are - If we upgrade the NetBackup edition to 8.3, will the 2008 R2 OS be upgraded first and what could be the impact? Or should new install (new windows 2016 or 2019) is advisable? Thank you very much! Leandro926Views0likes3CommentsNetbackup client Debian removal
Hello there! So I'm upgrading NetBackup client, by removing the existing one, and install the new version. For my RedHat systems I follow this documentation: https://www.veritas.com/support/en_US/doc/27801100-127350444-0/v121344818-127350444 I guess for Debian, there are no packages that I need to remove(I don't see them on the system anyway). So my question is, is there any additional steps that I should take on the Debian systems, or I just follow the documentation?1.1KViews0likes5Comments