Snapshot Error Encountered 156 Netbackup 7.1
No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Vision 2016 Vision Is this a standard Windows snapshot or is this a VCB backup, this will make a huge determination in how to move forward with troubleshooting. 0 Kudos Reply For snapshot error You must provide credentials for NetBackup to access the vCenter server. See Adding NetBackup credentials for VMware. have a peek here
Notify me of follow-up comments via email. The virtual machine has one or more independent disks and is in a suspended state If a virtual machine with independent disks is in a suspended state, snapshot jobs fail. So anyway my backups were failing to backup a client server with a "Snapshot error encountered (156)" error message and this is what I had to do to fix it. For Volume Shadow Copy (VSS) (Windows 2003 and later versions of windows):Use the following steps to increase the cache size when VSS is used on Windows 2003 Server clients. 1. https://www.veritas.com/support/en_US/article.TECH38709
You may also refer to the English Version of this knowledge base article for up-to-date information. Please show us policy config. View solution in original post 0 Kudos Reply 6 Replies There could be many reasons AlGon Level 6 08-12-2009 09:15 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed July 7, 2014 | Ali Hassan Post a New Comment Enter your information below to add a new comment.
- This issue results from a VMware limitation (SR#15583458301).
- No Yes Did this article save you the trouble of contacting technical support?
- D:/) 2.
- Look for 156 in the following: Andy_Welburn Moderator Trusted Advisor 08-13-2009 03:23 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate
- At the end of the day, it all depends on your environment &what you are trying to do - the more info you supply the easier it will be to provide
- No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES
My response is on my own website » Author: (forget stored information) Author Email (optional): Author URL (optional): Post: ↓ | ↑ Some HTML allowed: Look for 156 in the following: Andy_Welburn Moderator Trusted Advisor 08-13-2009 03:23 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Also verify that client has latestVSS hotfix installed. In that case, make sure that the display names are unique and that they do not contain special characters.
Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Windows open file backup using VSS snapshots fail Error Message Status 1, Status The method we follow to clear this issue, is rebooting the server in its maintenance window. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical https://www.veritas.com/support/en_US/article.TECH156750 Marianne Moderator Partner Trusted Advisor Accredited Certified 06-10-2012 07:32 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Please help
Examples of the environments that do not use static IP addresses are clusters, and the networks that assign IP addresses dynamically. See this TechNote for more info (although the status code is not the same): http://seer.support.veritas.com/docs/317730.htm By default any new client added to a backup policy will use a Windows Open File What is the client O/S? The backup fails.
OS version on master, media server backup host and/or client? https://www.veritas.com/support/en_US/article.v37089113_v118238945 No Yes Did this article save you the trouble of contacting technical support? Target : Windows Server 2003 Ent. In most cases, NetBackup will be able to create a large enough VSP cache file for backups if this is not selected.
This failure is often caused by the VSS cache file running out of allocated space. Master Log Files: 10/1/2009 4:30:20 PM - Critical bpbrm(pid=1548) from client myclilent: FTL - snapshot creation http://whistlemedia.net/snapshot-error/snapshot-error-encountered-156-netbackup-vmware.html In the Settings dialog box, change the Maximum Size setting to either No Limit or a size large enough to suit the requirements of the installation and usage of VSS Exact NBU version on Master, media server, backup host and/or client? Error Message snapshot error encountered (156) Cause Troubleshooting:If a backup on a Windows NetBackup (tm) 5.0 or later client fails with status code 156, this indicates that the client is using
If it is not listed, add and click on the client name. 5. No Yes How can we make this article more helpful? No Yes How can we make this article more helpful?
If NetBackup uses credentials for an ESX server instead of vCenter, it may not be able to identify a turned off virtual machine.
Your reference will not appear until it has been cleared by a website editor. Thank You! Thank You! In the NetBackup Administration console go to Host Properties, Master Server. 2.
This will decrease the resources used by the client during backup and resolve any Status 156 errors. What is the policy type of the failing backup? Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem NetBackup VSS snapshot error encountered (156) Error Message Status Code: 156 Solution Overview: http://whistlemedia.net/snapshot-error/snapshot-error-encountered-156-netbackup.html You may also refer to the English Version of this knowledge base article for up-to-date information.
Note: If the client name is LEVEL in the policy do not add the client name LeVeL in host properties. This failure is often caused by the VSP/VSS cache file running out of allocated space. Solution Note:In versions 7.0 and later VSP is no longer a valid snapshot method. Open the Netbackup Admin Console (with admin rights) and expand Host Properties Click on Master Servers and then in the right pane right click the master server and go to properties Note: A restart of services or daemons is not required for this action.