(Solved) Snapshot Error Encountered156 Flash Backup Tutorial

Home > Snapshot Error > Snapshot Error Encountered156 Flash Backup

Snapshot Error Encountered156 Flash Backup

Contents

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. Close this window and log in. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. If backups still abort with error status 156 after making changes to the VSP cache file size configuration, there may not be enough free disk space on the affected client. navigate here

But the issue was persisting due to LUN visibility, The ESX box where unable to see the newly assigned LUN, Because of this the backup job failed. I'll let you know tomorrow if this fixes Regards, Katie 0 Kudos Reply Thanks Mark, old snapshots Katiebee Level 4 ‎11-27-2012 02:05 AM Options Mark as New Bookmark Subscribe Subscribe to 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 Services Overview VIXAPI freeze failed...

Snapshot Error Encountered 156 Netbackup 7

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 Sorry, we couldn't post your feedback right now, please try again later. With this not selected, NetBackup automatically determines the best VSP cache file sizes. Here are some answers to your questions: 1.

  • Create/Manage Case QUESTIONS?
  • I also selected the options tab and took the snapshot method as auto, and under the backup selection selected the disks \\.\C: Seems to be working great now…. 0 Kudos Reply
  • You may also refer to the English Version of this knowledge base article for up-to-date information.
  • Plenty of space on the VMFS volume that the VM lives on.
  • Are you aComputer / IT professional?Join Tek-Tips Forums!
  • You should also be able to test most of these steps in turn too.
  • Couple of TNs: http://www.symantec.com/docs/TECH160314 http://www.symantec.com/docs/HOWTO44492 Handy NetBackup Links 0 Kudos Reply Lots of causes for this - Mark_Solutions Moderator Partner Trusted Advisor Accredited Certified ‎09-20-2013 03:06 AM Options Mark as New
  • The VMware tools service provides the ability to disable VSS writers, for diagnostic purposes.

post that up? 0 Kudos Reply I agree, in my environment thesanman Level 6 ‎10-30-2012 07:38 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Registration on or use of this site constitutes acceptance of our Privacy Policy. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Could Not Fetch Snapshot Metadata Or State Files But the issue was persisting due to LUN visibility, The ESX box where unable to see the newly assigned LUN, Because of this the backup job failed.

And that there are no RDM disks on these VMs? 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 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 https://vox.veritas.com/t5/NetBackup/Error-156-snapshot-error-encountered/td-p/566636 Using policy job limits then spread the load of the job across as many ESX servers you have in the environment.

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : Error - (156) snapshot error encountered VOX : Backup and Recovery : NetBackup : Vmware_freeze: Vixapi Freeze (vmware Snapshot) Failed With -1: Unrecognized Error Thanks for your help on this partto fix this 156 error code. 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 Rate this:Share this:EmailPrintMoreLinkedInGoogleRedditTwitterFacebookPinterestLike this:Like Loading...

Snapshot Error Encountered(156) Vmware

Well I was able to fix this saabsrule Level 3 ‎12-03-2012 08:32 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate https://vox.veritas.com/t5/NetBackup/Snapshot-error-encountered-VIXAPI-freeze-failed-with-1/td-p/561799 This will assist you in finding the right area to focus your troubleshooting efforts in. 0 Kudos Reply Following from MOHAMED_PATEL Level 5 Partner Accredited Certified ‎10-12-2013 02:54 AM Options Mark Snapshot Error Encountered 156 Netbackup 7 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 Snapshot Error Encountered 156 Hyper-v The Data Store where this VM resides is on a XIV storage box and the ESX version is 4.

The default NetBackup install options are to have open file backups enabled.To confirm if VSS or VSP open file backups are activated:  1. check over here We can snapshot manually through VSphere on some vms'but not all, and when a new client was added to the backup policy that backed up okay. 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 in Thanks in advance! (* Note - please scroll down the page all the way to view the continued responses in this thread) Error Received: 1/25/2011 11:04:07 PM - requesting resource webster-dd-stu Snapshot Error Encountered 156 Netbackup 7 Vmware

Veritas does not guarantee the accuracy regarding the completeness of the translation. Try and manually create the snapshot from vCenter or the VM. The VM's are a mixture of 2003 and 2008, Netbackup is 7.1.0.3 11:51:22.392 [1824.5564] <32> onlfi_freeze_fim_fs: FTL - VfMS error 11; see following messages: 11:51:22.392 [1824.5564] <32> onlfi_freeze_fim_fs: FTL - Fatal his comment is here Labels: 7.1.x and Earlier Backing Up Backup and Recovery Error messages NetBackup Troubleshooting Virtualization 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution!

We used to take around 20GB backup and around 300 mb was enough for snapshot creation 0 Kudos Reply Hi XJP5, From the information Mark_Newall Level 3 ‎01-27-2011 05:19 AM Options Netbackup Snapshot Error 156 Vmware If errors still occur with this not selected, it is possible to increase the initial VSP cache size and maximum VSP cache size manually. All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission.

Go to Solution.

Free up as much disk space on the drives of the affected client as possible. Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free. These settings vary depending on the client's requirements. Netbackup Error 156 Hyper-v Can you create the snapshot on the VM?

In one recent environment I saw, the diskspace is getting low on the VM backup host. Once again thanks for your help guys. 0 Kudos Reply Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business 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. http://unordic.com/snapshot-error/snapshot-error-encountered156-netbackup.html D:/) 2.

Katie 0 Kudos Reply There are various reasons Mark_Solutions Moderator Partner Trusted Advisor Accredited Certified ‎11-27-2012 02:58 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email The volume "snapshot" that occurs to facilitate open file backup has failed. No drives are available. 09/19/2013 22:36:45 - granted resource prasagppbck01.prasa.com.NBU_CLIENT.MAXJOBS.PRASAGPPMAR01.mrail.co.za 09/19/2013 22:36:45 - granted resource prasagppbck01.prasa.com.NBU_POLICY.MAXJOBS.VM_backups_VMW02 09/19/2013 22:36:45 - granted resource CTB389 09/19/2013 22:36:45 - granted resource HP.ULTRIUM5-SCSI.001 09/19/2013 22:36:45 - Once again thanks for your help guys.

It's best to use resource limits from Advanced Options of VIP policy configuration to limit 1 snapshot per datastore and 1 per ESX. 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 Thank You! Further to this, I moved the VM to another host running 4.0.0 164009 and the backup again failed with the same error.

Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. By joining you are opting in to receive e-mail. Used vMotion to move the VM to a different host running 4.0.0 208167 and now the VM backs up fine. In Windows, right-click My Computer and select Manage  2.

Veritas does not guarantee the accuracy regarding the completeness of the translation. Thanks for your help on this partto fix this 156 error code. No Yes How can we make this article more helpful? View solution in original post 0 Kudos Reply 1 Reply Accepted Solution!

Do you have the bpfis log from the backup host? Work with you VM administrator and see if you can create snapshots for these VMs using vCenter.