1. Master Server — Windows 2008 R2 Enterprise Sp1
2. Sp1
3. NTFS Only
4) ok
5) ok
6- Red Hat Enterprise Linux Server release 6.4 Beta (Santiago)
Linux pbad-fsmedia 2.6.32-343.el6.x86_64 #1 SMP Mon Nov 19 16:46:10 EST 2012 x86_64 x86_64 x86_64 GNU/Linux
7- [root@domainName-fsmedia admincmd]# ./bppllist VMWare-vCenter -U
————————————————————
Policy Name: VMWare-vCenter
Policy Type: VMware
Active: yes
Effective date: 07/23/2012 15:58:53
File Restore Raw: yes
Application Consistent: yes
Block Incremental: yes
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: DomainName_fsmedia_Dedup_STU
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: (none specified)
Data Classification: —
Residence is Storage Lifecycle Policy: no
Application Discovery: no
Discovery Lifetime: 28800 seconds
ASC Application and attributes: (none defined)
Granular Restore Info: no
Ignore Client Direct: no
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: yes
HW/OS/Client: vmx-08 windows7Serve pbad-vc
Include: ALL_LOCAL_DRIVES
Schedule: Daily
Type: Full Backup
Calendar sched: Enabled
Included Dates————
Sunday, Week 1
Monday, Week 1
Tuesday, Week 1
Thursday, Week 1
Friday, Week 1
Saturday, Week 1
Sunday, Week 2
Monday, Week 2
Tuesday, Week 2
Thursday, Week 2
Friday, Week 2
Saturday, Week 2
Sunday, Week 3
Monday, Week 3
Tuesday, Week 3
Thursday, Week 3
Friday, Week 3
Saturday, Week 3
Sunday, Week 4
Monday, Week 4
Tuesday, Week 4
Thursday, Week 4
Friday, Week 4
Saturday, Week 4
Sunday, Week 5
Monday, Week 5
Tuesday, Week 5
Thursday, Week 5
Friday, Week 5
Saturday, Week 5
Excluded Dates———-
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 2
Retention Level: 1 (2 weeks)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Sunday 18:40:00 —> Sunday 20:30:00
Monday 18:40:00 —> Monday 20:30:00
Tuesday 18:40:00 —> Tuesday 20:30:00
Thursday 18:40:00 —> Thursday 20:30:00
Friday 18:40:00 —> Friday 20:30:00
Saturday 18:40:00 —> Saturday 20:30:00
Schedule: Weekly_Tape
Type: Full Backup
Calendar sched: Enabled
Included Dates————
Wednesday, Week 1
Wednesday, Week 2
Wednesday, Week 3
Wednesday, Week 4
Wednesday, Week 5
Excluded Dates———-
EXCLUDE DATE 0 — 01/08/2014
EXCLUDE DATE 1 — 12/30/2015
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 2
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: NetBackup_Disk_Tape
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 1
Schedule indexing: 0
Daily Windows:
Wednesday 18:40:00 —> Wednesday 21:40:00
Schedule: Yearly_Tape
Type: Full Backup
Calendar sched: Enabled
Included Dates————
SPECIFIC DATE 0 — 12/26/2014
SPECIFIC DATE 1 — 01/08/2015
SPECIFIC DATE 2 — 12/30/2015
No days of week entered
Excluded Dates———-
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 2
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: NetBackup_Disk_Tape_yearly
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 1
Schedule indexing: 0
Daily Windows:
Wednesday 18:30:00 —> Wednesday 21:30:00
Содержание
- Status snapshot error encountered 156
- Status snapshot error encountered 156
- Status snapshot error encountered 156
- Status snapshot error encountered 156
- Status snapshot error encountered 156
Status snapshot error encountered 156
07-11-2012 01:46 PM
I was running a backup to an OST device (while a restore of earlier backup on the same device is already in progress ).
And the backup fails witht the below error:
Info bpbkar32(pid=4536) done. status: 156: snapshot error encountered
However the policy used for the backup is not configured for any snapshot backups.
Can anyone let me what could have went wrong here?
Using Netbackup 7.5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2012 02:16 PM
To start this investigation, we need to see the bpfis log, at VERBOSE=5 (and GENERAL=2 if Windows), from the client.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2012 02:43 PM
What type of backup is it and what is the client OS and NBU version?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2012 03:13 PM
Backup Type: Full backup (Normal)
Client: Windows 2008 R2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2012 05:58 PM
Here is the log output, could you please let me know what could have went wrong
Источник
Status snapshot error encountered 156
09-25-2014 02:06 AM
I have a VMware policy configured using annotation query to select clients.
Yesterday one of the clients failed with a status code of 156.
Last night the same client completed successfully.
I noticed in the detailed status, I have error’s relating to resource.
23/09/2014 18:00:52 — Info nbrb(pid=2888) Limit has been reached for the logical resource pd-dc2-nbumst.VMware.snapshot.vCenter.pd-dc2-vcenter.pdports.co.uk
What do I need to check/change to stop this from re-occuring?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2014 09:00 AM
23/09/2014 18:56:55 — Critical bpbrm(pid=106712) from client PD-DC2-CITRIX2: FTL — VMware error received: An error occurred while saving the snapshot: Failed to quiesce the virtual machine.
This error looks to be the cause. Look at bpfis log with vmcloglevel = 6 for further logs. (see VMware for NetBackup Administration Guide for more information on vmcloglevel)
This error can occur when The I/O in the virtual machine is very high and the quiesce operation is unable to flush all the data to disk as more and more I/O is being created. There can be different solutions to this including pausing active applications with high I/O or restart the vmware tools service in the guest. I have even seen reinstalling/upgrading to latest version of vmware tools to fix.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2014 02:24 AM
The above is Info message. Not an error.
Please post all text in Details tab of the failed job.
Logs needed on the Backup Host:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2014 07:44 AM
Please see details tab text below as requested.
Источник
Status snapshot error encountered 156
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2012 02:22 PM
Need help in fixing the issue, Error — (156) snapshot error encountered.
Error occurred while performing backup of a VM machine.
This error occurred at 0:02:15 after the backup is triggered. Pasted the detailed status below, The NBU Media and master server are different, we have Windows 2003 R2 as the media server OS and its x86 bit OS and Master Server is IBM AIX 5.3.
This is reoccurring issue, the backup is failing often. There are no environmental changes carried out recently on both the NBU and client end.
The Data Store where this VM resides is on a XIV storage box and the ESX version is 4.
Let me know how to permanently fix this snapshot error issue or need a workaround if the final solution indicates to up gradation.
Let me know what more details required to fix this EC.
Detailed Job Status:
10/31/2012 00:49:38 — requesting resource xx-xxxx-xxx04-b-hcart3-robot-tld-0
10/31/2012 00:49:38 — requesting resource XX-XXXX-XXXX01.NBU_CLIENT.MAXJOBS.
10/31/2012 00:49:38 — requesting resource XX-XXXX-XXXX01.NBU_POLICY.MAXJOBS.VMWARE3-VCB
10/31/2012 00:49:38 — Info nbrb (pid=2162758) Limit has been reached for the logical resource XX-XXXX-XXXX01.NBU_POLICY.MAXJOBS.VMWARE3-VCB_VCB
10/31/2012 00:50:04 — begin Create Snapshot
10/31/2012 00:50:04 — snapshot backup of client using method VMware
10/31/2012 00:49:59 — Waiting for scan drive stop IBM.ULT3580-TD3.018, Media server: xx-xxxx-xxx04-b
10/31/2012 00:50:00 — granted resource XX-XXXX-XXXX01.NBU_CLIENT.MAXJOBS.
10/31/2012 00:50:00 — granted resource XX-XXXX-XXXX01.NBU_POLICY.MAXJOBS.VMWARE3-VCB
10/31/2012 00:50:00 — granted resource 800921
10/31/2012 00:50:00 — granted resource IBM.ULT3580-TD3.018
10/31/2012 00:50:00 — granted resource xx-xxxx-xxx04-b-hcart3-robot-tld-0
10/31/2012 00:50:01 — estimated 1132190 kbytes needed
10/31/2012 00:50:01 — begin Parent Job
10/31/2012 00:50:01 — begin Flash Backup Windows: Start Notify Script
10/31/2012 00:50:02 — started process RUNCMD (pid=1163408)
Operation Status: 0
10/31/2012 00:50:02 — end Flash Backup Windows: Start Notify Script; elapsed time 0:00:01
10/31/2012 00:50:02 — begin Flash Backup Windows: Step By Condition
Operation Status: 0
10/31/2012 00:50:02 — end Flash Backup Windows: Step By Condition; elapsed time 0:00:00
10/31/2012 00:50:02 — begin Flash Backup Windows: Read File List
Operation Status: 0
10/31/2012 00:50:02 — end Flash Backup Windows: Read File List; elapsed time 0:00:00
10/31/2012 00:50:02 — begin Flash Backup Windows: Create Snapshot
10/31/2012 00:50:03 — started process bpbrm (pid=14468)
10/31/2012 00:51:53 — Critical bpbrm (pid=14468) from client : FTL — snapshot creation failed, status 156
10/31/2012 00:51:54 — end Flash Backup Windows: Create Snapshot; elapsed time 0:01:52
10/31/2012 00:51:54 — end writing
Operation Status: 156
10/31/2012 00:51:54 — end Parent Job; elapsed time 0:01:53
10/31/2012 00:51:54 — begin Flash Backup Windows: Stop On Error
Operation Status: 0
10/31/2012 00:51:54 — end Flash Backup Windows: Stop On Error; elapsed time 0:00:00
10/31/2012 00:51:54 — begin Flash Backup Windows: Delete Snapshot On Exit
10/31/2012 00:51:54 — begin Flash Backup Windows: Delete Snapshot On Exit
10/31/2012 00:51:56 — started process bpbrm (pid=11744)
10/31/2012 00:51:57 — end writing
Operation Status: 0
10/31/2012 00:51:57 — end Flash Backup Windows: Delete Snapshot On Exit; elapsed time 0:00:03
10/31/2012 00:51:57 — begin Flash Backup Windows: End Notify Script
10/31/2012 00:51:58 — started process RUNCMD (pid=917528)
Operation Status: 0
10/31/2012 00:51:58 — end Flash Backup Windows: End Notify Script; elapsed time 0:00:01
Operation Status: 156
10/31/2012 00:51:58 — end Flash Backup Windows: Delete Snapshot On Exit; elapsed time 0:00:04
Источник
Status snapshot error encountered 156
03-05-2014 09:49 AM
Guys, help me in resolving the issue.
NBU Master version 7.1.0.4 :: on VCS 5.0 :: 2 nodes :: RHEL5_x86_ 2.6
NBU Media servers verion :: 6.5.6 :: RHEL5 ::Serving as alternate client for snapshot backups.
Snapshot Method :: Legacy Shadowimage for Hitachi USPV — Hitachi AMS
Client OS: RHEL5
VXVM 5.0mp3 on master, media and clients
Policy vaildation fails with below error :
There was an error found with snapshot configuration on clients specified in this policy.
Policy: MBS2_store5 — client: xxxx-xxx-xxx —Snapshot could not be created with ShadowImage method — (Status 223).
Tried running the backup anyway resulting in 156.
Policy Type: FlashBackup (20)
Active: yes
Effective: 01/05/2010 14:44:01
Follow NFS Mounts: no
Cross Mount Points: no
Client Compress: no
Collect TIR info: no
Policy Priority: 0
Ext Security Info: no
File Restore Raw: yes
Client Encrypt: no
Max Jobs/Policy: Unlimited
Mult. Data Stream: yes
Block Level Incremental: no
Perform Snapshot Backup: yes
Snapshot Method: ShadowImage
Snapshot Method Arguments: sync_at_start=0,keep_fi=0,timeout=240,async_resync=0
Perform Offhost Backup: yes
Backup Copy: 0
Use Data Mover: no
Data Mover Type: -1
Use Alternate Client: yes
Alternate Client Name: xxxxxxxxxxxx
Use Virtual Machine: 0
Hyper-V Server: (none)
Enable Instant Recovery: no
Collect BMR Info: no
Max Frag Size: 0 MB
Checkpoint Restart: no
Residence: xxxxxxxxxxxx-hcart-robot-tld-2
Volume Pool: MbsPool
Server Group: *ANY*
Data Classification: —
Residence is storage lifecycle policy: no
Granular Restore: no
Generation: 4
Ignore Client Direct: no
Exchange Source attributes: no
Application Discovery: no
Discovery Lifetime: 0 seconds
Recent changes : A new set of Luns were presented to both client (parent volume) and media servers(clone volume).
Backup process: Involves suspending mirror (Primary to clone), snapshot creation of volume (rdsk), importing VXVMdiskgroup _clone .
Источник
Status snapshot error encountered 156
07-11-2012 01:46 PM
I was running a backup to an OST device (while a restore of earlier backup on the same device is already in progress ).
And the backup fails witht the below error:
Info bpbkar32(pid=4536) done. status: 156: snapshot error encountered
However the policy used for the backup is not configured for any snapshot backups.
Can anyone let me what could have went wrong here?
Using Netbackup 7.5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2012 02:16 PM
To start this investigation, we need to see the bpfis log, at VERBOSE=5 (and GENERAL=2 if Windows), from the client.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2012 02:43 PM
What type of backup is it and what is the client OS and NBU version?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2012 03:13 PM
Backup Type: Full backup (Normal)
Client: Windows 2008 R2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2012 05:58 PM
Here is the log output, could you please let me know what could have went wrong
Источник
Click here follow the steps to fix Netbackup Error 156 and related errors.
|
|
|
|
To Fix (Netbackup Error 156) error you need to |
|
|
Step 1: |
|
|---|---|
| Download (Netbackup Error 156) Repair Tool |
|
|
Step 2: |
|
| Click the «Scan» button | |
|
Step 3: |
|
| Click ‘Fix All‘ and you’re done! | |
|
Compatibility:
Limitations: |
Netbackup Error 156 Error Codes are caused in one way or another by misconfigured system files
in your windows operating system.
If you have Netbackup Error 156 errors then we strongly recommend that you
Download (Netbackup Error 156) Repair Tool.
This article contains information that shows you how to fix
Netbackup Error 156
both
(manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to Netbackup Error 156 error code that you may receive.
Note:
This article was updated on 2023-02-04 and previously published under WIKI_Q210794
Contents
- 1. What is Netbackup Error 156 error?
- 2. What causes Netbackup Error 156 error?
- 3. How to easily fix Netbackup Error 156 errors
What is Netbackup Error 156 error?
The Netbackup Error 156 error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors.
This code is used by the vendor to identify the error caused. This Netbackup Error 156 error code has a numeric error number and a technical description. In some cases the error may have more parameters in Netbackup Error 156 format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error.
What causes Netbackup Error 156 error?
The Netbackup Error 156 error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer.
There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware
attack or by an improper shutdown of the computer. All the above actives
may result in the deletion or corruption of the entries in the windows
system files. This corrupted system file will lead to the missing and wrongly
linked information and files needed for the proper working of the
application.
How to easily fix Netbackup Error 156 error?
There are two (2) ways to fix Netbackup Error 156 Error:
Advanced Computer User Solution (manual update):
1) Start your computer and log on as an administrator.
2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.
3) In the new window, select «Restore my computer to an earlier time» option and then click Next.
4) Select the most recent system restore point from the «On this list, click a restore point» list, and then click Next.
5) Click Next on the confirmation window.
6) Restarts the computer when the restoration is finished.
Novice Computer User Solution (completely automated):
1) Download (Netbackup Error 156) repair utility.
2) Install program and click Scan button.
3) Click the Fix Errors button when scan is completed.
4) Restart your computer.
How does it work?
This tool will scan and diagnose, then repairs, your PC with patent
pending technology that fix your windows operating system registry
structure.
basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.)
Using NetBackup 7.0.1 and vSphere 4. Tried to backup a new v7 VM and got a 156 failure from NetBackup. Within vSphere client the following error was displayed when NetBackup tried to take a snapshot of the VM:
Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.
Within NetBackup the following was shown in the job Detailed Status tab:
29/11/2010 13:59:10 - Critical bpbrm(pid=3360) from client XXXXXXX: FTL - snapshot creation failed, status 156
29/11/2010 13:59:10 - Warning bpbrm(pid=3360) from client XXXXXXX: WRN - ALL_LOCAL_DRIVES is not frozen
...
29/11/2010 13:59:18 - end Flash Backup Windows, Delete Snapshot On Exit; elapsed time: 00:00:05 snapshot error encountered(156)
The VM itself is running Windows Server 2008 R2, has one CPU, a 40GB C drive and 2GB RAM. It has VMware tools installed. Plenty of space on the VMFS volume that the VM lives on.
This error was generated from a vSphere host running 4.0.0 164009. Used vMotion to move the VM to a different host running 4.0.0 208167 and now the VM backs up fine. Further to this, I moved the VM to another host running 4.0.0 164009 and the backup again failed with the same error. Seems as though NetBackup 7.0.1 doesn’t like vSphere 4.0.0 164009.
Update
I’ve now also seen a different cause of status 156 failures, related to the snapshot process taking too long to complete. A quick fix is to remove the VMWare VSS writer, though there’s more diagnostics you can do to work out what’s not working. The suggested method is to uninstall the VMware tools, then re-install choosing a custom install, and de-select the VSS writer. Note that the uninstall will remove all the VMware drivers too, so for example you’ll loose your network card if you’re using VMXNET3 etc. Unfortunately the tools that come with vSphere 4.1 don’t have the modify option, so removing and re-installing is the only option.
The VMware tools service provides the ability to disable VSS writers, for diagnostic purposes.