Error 150 Server Status Termination Requested By Administrator
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 150: Backups fail with a NetBackup Status Code 150 (termination requested by administrator), despite no administrator intervention, after a client is moved from an old master server to a new master server. Article:000032877 Publish: Article URL:http://www.veritas.com/docs/000032877 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 150: Backups fail with a NetBackup Status Code 150 (termination requested by administrator), despite no administrator intervention, after a client is moved from an old master server to a new master server. Solution Overview: Backups fail with a NetBackup Status Code 150 (termination requested by administrator), despite no administrator intervention, after a client is moved from an old master server to a new master server.Troubleshooting: Enable the bpbrm and bptm log files on the media server, and the bpbkar log file on the client server. Log files:A review of the bpbrm and bptm log files (on the media server) and the bpbkar log file on the client shows the backup job going active and the backup image in the process of being transferred from bpbkar to bptm when the problem occurs.The bptm log shows the media mounted and positioned and received data from the only/one stream in the MPX group.16:10:18.148 [1452.3324] <4> write_backup: begin writing backup id
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 BUG REPORT: Backups are failing with status code 150 (termination requested by administrator) although there was no administrator intervention in any of the affected jobs. Versions of NetBackup affected include 5.1MP5 and 5.1MP6. Article:000089770 Publish: Article URL:http://www.veritas.com/docs/000089770 Support / https://www.veritas.com/support/en_US/article.TECH50484 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 BUG REPORT: Backups are failing with status code 150 https://www.veritas.com/support/en_US/article.000089770 (termination requested by administrator) although there was no administrator intervention in any of the affected jobs. Versions of NetBackup affected include 5.1MP5 and 5.1MP6. Solution Bug: ET700724 Symptom(s): In NetBackup versions 5.1MP5 and 5.1MP6, the activity monitor will show multiple jobs exiting with status 150 (termination requested by administrator) without administrator intervention.Log Files:The bpsched log will show the following messages:20:05:55.796 [18942] <16> start_backup_job: fork error: Not enough space (12)20:05:55.796 [18942] <16> run_any_ret_level: failure starting backup job, PID=-1Workaround: Recycling NetBackup periodically will avoid this type of behavior. ETA of Fix:The formal resolution to this issue (ETrack 700724) is included in the following patch release: NetBackup 5.1 Maintenance Pack 7 (MP7)This release is available at the Support Web site at: http://www.symantec.com/enterprise/support/overview.jsp?pid=15143 Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness ofPKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products https://support.symantec.com/en_US/article.TECH7981.html A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries http://serverfault.com/questions/420469/symantec-netbackup-oracle-restore-fails-exited-with-status-13-file-read-fail Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & error 150 Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United error 150 server States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Backup fails with status 150, termination requested by administrator, erroneously. Should have reported status 71. TECH7981 January 25th, 2001 http://www.symantec.com/docs/TECH7981 Support / Backup fails with status 150, termination requested by administrator, erroneously. Should have reported status 71. Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation Backup fails with status 150, termination requested by administrator, erroneously. Should have reported status 71. Error status code 150 Solution Upon verifying that the job in question was not killed by the system administrator, examine the client log files. If the files list for backup requested to backup a non-existent directory, the job can terminate with a status "71" - "none of the files in files list exists." This status is not always properly populated back to the master server, which may misinterpret the end of job as a status "150" - "
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Symantec Netbackup : Oracle restore fails “exited with status 13: file read failed” up vote -1 down vote favorite I am restoring Oracle datafile size of 1200GB. Datafile is read from backup piece size of 4000GB(4TB). Note: As I monitored 4TB is processed totaly to read all blocks of my datafile. I had several problems during restore: Situation 1. There was period when after 2 hours restore was failing (Operation column in Netbackup Database Console was empty at that moment) Situation 2. Drive was mounted before 2 hours and restore process was not failed before 2 hours. But suddenly restore failed after processing 55GB. I don't have old logs. Now I the following problem: Restore has failed after processing 3TB(23 hours was passed)... I will post some log entries, please help : ---------------Details tab shows 8/23/2012 12:56:40 PM - restored image r2n1_1345046880 - (file read failed(13)); restore time 23:36:17 8/23/2012 12:56:44 PM - end Restore; elapsed time: 23:36:26 the restore failed to recover the requested files(5) ------------------------------bpbrm log shows 12:56:35.561 [7344.4804] <2> bpbrm brm_child_done: child 4852 exited with status 13: file read failed 12:56:35.561 [7344.4804] <2> bpbrm send_status_to_parent: bpbrm child is done, but the media manager child is not. 12:56:35.561 [7344.4804] <2> bpbrm tell_mm: sending media manager msg: STOP RESTORE r2n1_1345046880 12:56:40.709 [7344.4804] <2> bpbrm read_media_msg: read from media manager: EXIT r2n1_