Netbackup Error 156 The System Cannot Find The File Specified
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 Backups fail with error "VSS Snapshot error. A Microsoft Volume Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot can run at a time. Try running the job later." - Status Code 156 Article:000020486 Publish: Article URL:http://www.veritas.com/docs/000020486 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 Problem System state and/or shadow copy component backups fail with errors below: Error Message BPBKAR Snip: 11:10:23.963 PM: [6416.10484] <2> tar_base::V_vTarMsgW: ERR - failure reading file: C:\Precision\P2009\output\3007483317+50UPS_DOM+PCNTMS1C+4GLLISTENER.prn (WIN32 2: The system cannot find the file specified. ) 11:10:23.963 PM: [6416.10484] <4> dos_backup::tfs_readdata: INF - will skip file when clearing archive bits: 'C:\Precision\P2009\output\3007483317+50UPS_DOM+PCNTMS1C+4GLLISTENER.prn' 11:10:24.977 PM: [6416.10484] <4> V_VSS_CheckForError: INF - Error Checking for GLOBALROOT\Device\HarddiskVolumeShadowCopy33 11:10:24.977 PM: [6416.10484] <4> V_VSS_CheckForError: INF - Error Status (GLOBALROOT\Device\HarddiskVolumeShadowCopy33): 2 11:10:24.977 PM: [6416.10484] <4> tar_base::V_vTarMsgW: INF - tar message received from dos_backup::tfs_readdata 11:10:24.977 PM: [6416.10484] <2> tar_base::V_vTarMsgW: ERR - Snapshot Error while reading file: GLOBALROOT\Device\HarddiskVolumeShadowCopy33\Precision\P2009\output\3007483317+50UPS_DOM+PCNTMS1C+4GLLISTENER.prn Event Log: Log Name: Application Source: VSS Date: Event ID: 8193 Task Category:
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Netbackup 7.1 Status Code 156 VOX : Backup and https://www.veritas.com/support/en_US/article.000020486 Recovery : NetBackup : Netbackup 7.1 Status Code 156 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Netbackup 7.1 Status Code 156 RCBrown_DKH Level 4 06-01-2012 07:32 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight https://vox.veritas.com/t5/NetBackup/Netbackup-7-1-Status-Code-156/td-p/507261 Print Email to a Friend Report Inappropriate Content My Master/Media server is Windows 2008 R2 running Netbackup 7.1. The client having the problem is a Windows Server 2003 running Netbackup 7.0. I am getting a a status code 156 error. Job details are below: 5/31/2012 6:33:35 PM - Info nbjm(pid=33196) starting backup job (jobid=203726) for client janus01.daykimball.org, policy Servers.AllLocal, schedule Incremental 5/31/2012 6:33:35 PM - estimated 39939338 Kbytes needed 5/31/2012 6:33:35 PM - Info nbjm(pid=33196) started backup job for client janus01.daykimball.org, policy Servers.AllLocal, schedule Incremental on storage unit STG1 5/31/2012 6:33:35 PM - started 5/31/2012 6:33:36 PM - started process bpbrm (6092) 5/31/2012 6:33:41 PM - Info bpbrm(pid=6092) janus01.daykimball.org is the host to backup data from 5/31/2012 6:33:45 PM - Info bpbrm(pid=6092) reading file list from client 5/31/2012 6:33:45 PM - connecting 5/31/2012 6:33:48 PM - Info bpbrm(pid=6092) starting bpbkar32 on client 5/31/2012 6:33:48 PM - connected; connect time: 00:00:03 5/31/2012 6:33:54 PM - Info bpbkar32(pid=0) Backup started 5/31/2012 6:33:54 PM - Info bptm(pid=7348) start 5/31/2012 6:33:54 PM - I
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 https://vox.veritas.com/t5/NetBackup/Snapshot-error-encountered-status-code-156-ERR-Snapshot-Error/td-p/534587 Developers Blogs Groups Vision 2016 Sign In https://vox.veritas.com/t5/NetBackup/Receiving-error156-quot-Snapshot-error-encountered-quot-for/td-p/685129 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup netbackup error : Snapshot error encountered (status code 156) : ERR... VOX : Backup and Recovery : NetBackup : Snapshot error encountered (status code 156) : ERR... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Snapshot error encountered (status code netbackup error 156 156) : ERR - Snapshot Error while reading file Vivek_Sahu Level 3 Certified 02-08-2013 02:04 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, I configured backups for cluster servers, After writeing around 490 GB data job is failing with Snapshot error for Cluster Drive. Cluster nodes backups are running fine in other policy. We are taking backup of Cluster Drive K:\ using Virtual Cluster Server and IP. Please advise. Master Server Ver : 7.1.0.2 Client OS :Windows 2003 R2 64 bit 02/07/2013 04:04:59 - estimated 0 kbytes needed 02/07/2013 04:04:59 - Info nbjm (pid=14502) started backup job for client m4msqlvs01, policy Metrix4media-s-win-cluster, schedule Weekly-Full on storage unit bu04_adv_01 02/07/2013 04:05:01 - started process bpbrm (pid=19783) 02/07/2013 04:05:05 - connecting 02/07/2013 04:05:07 - connected; connect time: 0:00:00 02/07/2013 04:05:16 - begin writing 02/07/2013 11:04:02 - Warning bptm (pid=19785) disk pool bu04_dp_01 volume /bu04d2d-1
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Receiving error156 "Snapshot error encountered" fo... VOX : Backup and Recovery : NetBackup : Receiving error156 "Snapshot error encountered" fo... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Receiving error156 "Snapshot error encountered" for servers that are not VMs Eric_5279 Level 3 07-02-2014 06:04 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Good Morning, A few days ago I started to receive a 156 "Snapshot error encountered" error for 2 servers. The only thing is... these servers are not virtual machines. They are physical servers doing standard file level backups. This has me a little stumped. We are running version 7601 on the master and either 7.6.0.0 or 7.6.0.1 on the clients. One client runs windows 2003 server and the other runs 2008 server. I have not been able to find much ( anything ) about this happening and how to go about fixing it. The clients were backing up with no issues since they were first added to the backup rotation almost a year ago Here is the job report for one of the policies ( I did