Netbackup Error Status 174
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 STATUS CODE 174: Status Code 174 "media manager - system error occurred" occurs when backing up Windows Clients to a Gigabit interface on a SUN Media Server. Article:000026266 Publish: Article URL:http://www.veritas.com/docs/000026266 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 174: Status Code 174 "media manager - system error occurred" occurs when backing up Windows Clients to a Gigabit interface on a SUN Media Server. Error Message Attempt to write 8 gigabytes, 1457249836 bytes, it is not a multiple of 512media manager - system error occurred (174) Solution Overview:During backups, the NetBackup (tm) media server keeps track of the number of bytes received during backup. The media server pads all blocks sent to 512 bytes. After a backup finishes, NetBackup divides the total number of bytes by 512 as an integrity check. If the number does not divide evenly by 512, then it is assumed that some amount of data was not received. A Status 174 error is then seen on Windows clients. UNIX Clients do not experience the 174 error.Troubleshooting:Research has shown that this problem is often associated with Network Interface Card (NIC) configuration issues.Media Server Log Files:The /usr/openv/netbackup/logs/bptm
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 NDMP backups are failing with status 174 (media manager - system error occurred) reported. Status code 14 (file https://www.veritas.com/support/en_US/article.000026266 write failed) can also be seen in logs. Article:000091091 Publish: Article URL:http://www.veritas.com/docs/000091091 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 https://www.veritas.com/support/en_US/article.TECH59140 Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem NDMP backups are failing with status 174 (media manager - system error occurred) reported. Status code 14 (file write failed) can also be seen in logs. Solution Issue:backup: bptm error: exits status code 174.Error Code/Message:From the bptm log on the media server:bptm
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk http://www.tek-tips.com/viewthread.cfm?qid=1374132 With Other Members Be Notified Of ResponsesTo Your Posts Keyword http://systemmanager.ru/nbadmin.en/nbu_174.htm Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis netbackup error posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Symantec: NetBackup Forum at Tek-Tips HomeForumsServer RackBack-up netbackup error status SystemsSymantec: NetBackup Forum Backups ending in Status code 174 thread776-1374132 Forum Search FAQs Links MVPs Backups ending in Status code 174 Backups ending in Status code 174 bpACH (TechnicalUser) (OP) 2 Jun 07 12:19 Hello,We are currently using Veritas Netbackup 6.0 mp3.Our backups are ending with status code 174.When we look at the activity monitor the job reports:NDMP backup failed: path= UNKNOWNLooking at the bptm logs, we find the following error:20:49:18.162 [11713] <2> drivename_open: Called with Create 1, file QUANTUM.SDLT320.00220:49:18.163 [11713] <2> drivename_lock: lock failed20:49:18.163 [11713] <2> drivename_close: Called20:49:18.163 [11723] <2> drivename_open: Called with Create 1, file QUANTUM.SDLT320.00320:49:18.163 [11723] <2> drivename_lock: lock failed20:49:18.163 [11723] <2> drivename_close: CalledThe drives that call this are physically empty and NetBackup will report them as active for a while after the error occurs. RE: Backups ending in Status code 174 bpACH (TechnicalUser) (OP) 3 Jun 07 17:22 Issue resolved.1. Stopped Netbackup2. Deleted the files in /usr/openv/netbackup/db/media/drives3. Started Net
Check the NetBackup Problems report to see if it shows the cause of the problem. If you see a Problems report message similar to the following, save all logs and call &CompanyName; customer support: "attempted to write 32767 bytes, not a multiple of 512" On UNIX and Linux, if this error occurs during a restore, the tape drive may be incorrectly configured. It may be configured to write in fixed length mode when it should write in variable length mode. Verify your drive's configuration by comparing it to what is recommended in the NetBackup Device Configuration Guide. If your configuration incorrectly specifies fixed length mode, change it to variable length mode and suspend the media that were written on that device. The images that were written to those media may be restorable (platform dependent), but single file restores are likely to fail. If the problem occurs with a particular client only, verify that the client binaries are correct, especially for bpcd. If you can read or write any other images on this media, check the following reports for clues: Images on Media report Media Contents report Verify the following: The media, by using the NetBackup image verify option. That you used the correct media type for the device. Check the system or the console log for errors (on UNIX and Linux) or the Event Viewer Application log (on Windows). For detailed debug information, create a debug log directory for either bptm or bpdm (whichever applies) and retry the operation. Check the resulting debug log. On UNIX and Linux, if the bptm debug log shows an error similar to the following, the tape drive is configured to write in fixed length mode rather than variable length mode: 00:58:54 [2304] <16> write_data: write of 32768 bytes indicated only 29696 bytes were written, errno = 0 The image being written encountered the end-of-media. If the backup was configured for an OpenStorage disk storage unit, the OpenStorage vendor's plug-in may not be installed on all media servers in the storage unit's media server list. Either install the vendor plug-in on all of the media servers or remove from the list the servers that do not have the plug-in installed.