Netbackup Error Code 156
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations snapshot error encountered(156) vmware Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português snapshot error encountered 156 hyper-v Español USA Site: Veritas Veritas PartnerNet STATUS CODE: 156 "snapshot error encountered" occurs when utilizing VSP or VSS for open
Snapshot Error Encountered 156 Netbackup 7 Vmware
file backups. Article:000029295 Publish: Article URL:http://www.veritas.com/docs/000029295 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign
Netbackup Error 156 Hyper-v
in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE: 156 "snapshot error encountered" occurs when utilizing VSP or VSS for open file backups. Error Message snapshot error encountered (156) Cause Troubleshooting:If a backup on a Windows NetBackup (tm) 5.0 or later client netbackup snapshot error 156 vmware fails with status code 156, this indicates that the client is using Windows Open File Backups to protect open or active files. The volume "snapshot" that occurs to facilitate open file backup has failed. 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. These systems will need to utilize the VSS provider for snapshots.Overview: STATUS CODE: 156 "snapshot error encountered" occurs when utilizing VERITAS Volume Snapshot Provider (VSP) or Microsoft Volume Shadow Copy Service (VSS) for a client backup.Master Log Files: N/A Media Server Log Files: N/AClient Log Files: bpbkar6:00:14.156 AM: [452.976] <2> tar_base::V_vTarMsgW: ERR - Snapshot Error while reading file: Volume{43877774-d2zz-4rar-r5id-fg9i49fuje7815}\Accounts\Akerfeldt\data\Amm.txt6:00:14.171 AM: [452.976] <2> tar_base::V_vTarMsgW: FTL - Backup operation aborted!6:00:14.218 AM: [452.976] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 156: snapshot error encounteredResolution: Firstly, if Open file backups are not desired for the client, disable them. This will decrease the resources used by the client during backup and resolve any Status 156 errors. The default NetBackup install options are to have open file backups enabled.To confirm if VSS or VSP open file backups
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom
Netbackup Error 156 Linux
Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français netbackup error 156 windows 2008 Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet NetBackup VSS snapshot error encountered (156) Article:000040337 Publish: vmware_freeze: vixapi freeze (vmware snapshot) failed with -1: unrecognized error Article URL:http://www.veritas.com/docs/000040337 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to https://www.veritas.com/support/en_US/article.TECH38709 Subscribe Please sign in to set up your subscription. 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: end Persistent Frozen Image, Delete Snapshot On Exit; elapsed time: 00:01:09 snapshot error encountered(156). Exact Error Message https://www.veritas.com/support/en_US/article.TECH75214 snapshot error encountered (156) Troubleshooting: If a backup of a Windows NetBackup (tm) client fails with status code 156, this indicates that the client is using Windows Open File Backups to protect open or active files. The volume "snapshot" that occurs to facilitate open file backup has failed. 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 failed, status 156 10/1/2009 4:30:24 PM - end Create Snapshot; elapsed time: 00:08:48 10/1/2009 4:30:30 PM - end writing Status 156 10/1/2009 4:31:39 PM - end Persistant Frozen Image, End Notify Script; elapsed time: 00:00:00 Status 156 10/1/2009 4:31:39 PM - end Persistent Frozen Image, Delete Snapshot On Exit; elapsed time: 00:01:09 snapshot error encountered(156) Client Log Files (bpfis): 04:42:19.542 [840.5892] <2> onlfi_vfms_logf: snapshot services: vss:Fri Oct 2 2009 04:42:19.542000
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT https://www.veritas.com/support/en_US/article.000084792 About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers https://www.veritas.com/support/en_US/article.000110467 Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Possible causes of and remedies for status code 156 failures in Hyper-V backups Article:000084792 Publish: Article URL:http://www.veritas.com/docs/000084792 Support / Article Sign In Remember me Forgot netbackup error Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem When Hyper-V snapshot jobs are unsuccessful, frequently snapshot error encountered it is status code 156 (snapshot error encountered) reported. This error is very commonly reported when snapshots start for a specific volume when something is wrong in configuration. To resolve this issue, the configuration needs to be corrected at the VMware/Hyper-V snapshot client level. This document provides some common causes of Hyper-V VM snapshot failure with status code 156 reported and the remedies which may be used to resolve them. Error Message snapshot error encountered Status Code: 156 Solution Refer to the table below: Causes of status code 156 Description and recommended action The virtual machine name is incorrectly specified in the NetBackup policy. Indicates a mismatch between the virtual machine names that are specified on the policy Clients tab and the actual names on the Hyper-V server. Check the actual names as listed in the Hyper-V Manager on the Hyper-V server. The following are the recommended actions: In the NetBackup policy, the virtual machines must be specified as fully qualified names.In the NetBackup
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet NetBackup status code: 156 Article:000110467 Publish: Article URL:http://www.veritas.com/docs/000110467 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Description Message: snapshot error encounteredExplanation: The following are possible causes of this status code:Errors related to VMwareAn error related to the Enterprise Vault Agent. The following errors can result in a status code 156: VSS_E_BAD_STATE snapshot errorVSS_E_INSUFFICIENT_STORAGE snapshot errorA snapshot-backup related error regarding Windows Open File Backup or Snapshot Client.Multiple volumes are mounted to the same mount pointRecommended Action: Do the following, as appropriate:For NetBackup for VMware: NetBackup cannot obtain the volume ID of a driveNetBackup may not be able to obtain the volume ID of a drive. In that case, none of the virtual machine drives are backed up. The backup fails with NetBackup status code 156.The drive may be down.A backup of the virtual machine is already activeYou cannot run more than one backup per virtual machine at a time. If you start a second backup of the virtual machine while the first backup is active, the second job fails with a status 156.Recommended action: Wait until the first job completes, then run the second one.Cannot find virtual machine nameNetBackup cannot find the host name or VM display name of a virtual machine that is listed in the backup policy. The detailed status log may include the following error message:Critical bpbrm (pid=