Netbackup Error 129
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer exit code 129 linux Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate code128 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 STATUS CODE: 129 - Backups to disk storage units fail with a VERITAS NetBackup (tm) Status 129 because the storage unit is full. Article:000030266 Publish: Article URL:http://www.veritas.com/docs/000030266 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 STATUS CODE: 129 - Backups to disk storage units fail with a VERITAS NetBackup (tm) Status 129 because the storage unit is full. Error Message <32> io_open_disk: storage unit /dsu01 is full...<32> io_open_disk: bp_sts_open_image failed: error 31<2> bpdm: EXITING with status 129 Solution Overview:When using VERITAS NetBackup (tm) Enterprise Server, a backup to a disk storage unit will fail with a Status 129 when the disk storage unit is full. This status code can occur for disk storage units (DSU) and disk staging storage units (DSSU). Troubleshooting:The df -h command can be used to determine the available disk space for a disk storage unit. On the media server where the disk storage resides, run the following command:# df -hFilesystem size used avail capacity Mounted on/dev/dsk/c0t0d0s0
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 : error 129 Disk storage unit full VOX : https://www.veritas.com/support/en_US/article.TECH44663 Backup and Recovery : NetBackup : error 129 Disk storage unit full 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 error 129 Disk storage unit full cyberninja Level 6 08-13-2014 10:43 AM Options Mark as New Bookmark Subscribe https://vox.veritas.com/t5/NetBackup/error-129-Disk-storage-unit-full/td-p/706544 Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, I'm having an issue where my VMware backups are not running. When I run a job it just stays qued up. In the Activity Monitor under the State Details it says Disk media is not active (Dedupe_media01_STU, media01). What do I need to do in order to get the jobs to run? Environment: Server OS NetBackup Version Master server Solaris 10 7.5.0.7 Media server 02 Solaris 10 7.5.0.7 VM Media server 00 Win2008 R2 7.5.0.7 VM Media server 01 Win2008 R2 7.5.0.7 Media server bar-2 SLES 11 7.1 Media server bar0 SLES 11 7.5.0.5 Media server bar1 SLES 11 7.5.0.5 Media server bar2 SLES 11 7.5.0.5 Solved! Go to Solution. Labels: 7.5 Backing Up Backup and Recovery Basics Best Practice Error messages NetBackup Tip-How to Troubleshooting Virtualization Windows Server (2003-2008) 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! nbemmcmd -updatehost RiaanBadenhorst Moderator Partner Trusted Advisor Accredited Certified 08-13-2014 11:18 AM Options Mark as N
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/NetBackup-jobs-failing-with-error-129-insufficient-disk-space/td-p/765841 Developers Blogs Groups Vision 2016 Sign In https://vox.veritas.com/t5/NetBackup/error-129-Disk-storage-unit-full/td-p/670385 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 NetBackup jobs failing with error 129 (insufficien... VOX : Backup and Recovery : NetBackup : NetBackup jobs failing with error 129 (insufficien... 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 jobs failing with netbackup error 129 error 129 (insufficient disk space) bbot Level 4 02-01-2016 09:35 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, We have a couple clients failing to backup to the same storage. There's over 1 TB available on our storage server. The size of all the full client backups are no longer than 300 gb. Watermark is set to 98% high water mark, 80% low water mark. I'm fairly new to netbackup,, where should I be looking to find out the root cause? Solved! Go to Solution. Labels: 7.6 Backup and Recovery NetBackup Windows Server (2003-2008) 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! oh my bad.. i read that Douglas_A Level 6 Partner Accredited Certified 02-02-2016 10:56 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content oh my bad.. i read that wron
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 : error 129 Disk storage unit full VOX : Backup and Recovery : NetBackup : error 129 Disk storage unit full 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 error 129 Disk storage unit full cyberninja Level 6 07-23-2014 09:50 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, I have been getting error 129 on some of my backups. it looks like I have a PureDisk disk pool that has reached it's high water mark. As the Disk Pool is a lun from a NetApp, I asked the SAN admin to give me some more space. After getting more space I got the Solaris 10 media sever to see it with this comand. zpool set autoexpand=on bupool Any way Netbackup still sees the volume at it's old size. How do I get NetBackup see the new space? Also if I needed to do more stuff on the Solaris side let me know. My enviremet. Master server NetBackup 7.5.0.7 Solaris 10 Media server NetBackup 7.5.0.7 Solaris 10 Solved! Go to Solution. Labels: 7.5 Backing Up Backup and Recovery Best Practice Configuring Error messages NetBackup Solaris Tip-How to 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! Run the crcontrol --getmode SymTerry Level 6 Employee Accredited 07-23-2014 02:54 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Run the crcontrol --getmode command again. Does it still say PUT=No? If so, please look at the/log/spoold/spoold.log. Your looking for the line "Storage Cache Manager: load completed" if you don't see that, look for "Reason: ERROR: " If you think the data store is corrupt, please open a support ticket and PM me the case number. View solution in original post 0 Kudos Reply 7 Replies update, I was able to