Netbackup Error Code 59
Contents |
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
Access To The Client Was Not Allowed 59 Netbackup 7
Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal netbackup error 59 windows Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet
Host Is Not An Authorized Server For Host Netbackup
GENERAL ERROR: access to the client was not allowed (59) Article:000040440 Publish: Article URL:http://www.veritas.com/docs/000040440 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? error code 58 in netbackup 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 When running a backup it fails with an error 59. The job details will show the server not allowed access (46) message: access to the client was not allowed (59) Error Message access to the client was not allowed (59) Cause A status code of 59 commonly occurs when the client does not have the NetBackup master or media server properly defined in the /usr/openv/netbackup/bp.conf file for Unix or in registry "HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config\Server" for Windows. Check to make sure that the master and media server used for the job are present in the server list on the client. Windows: Open the Backup and Restore (BAR) console. Go to the 'File' menu and select 'Specify NetBackup Machines and Policy Type'. The first drop down box ('Server to use for backups and restores') shows you the server list. UNIX: Check in /usr/openv/netbackup/bp.conf Solution Windows: click 'Edit Server List' and add the missing server name. UNIX: Add an entry into the bp.conf. For example for missing media server 'yeti' insert into bp.conf the line: SERVER = YETI Making sure that the master server SERVER line is always the first entry. Terms of use
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
Netbackup Error 48
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as connection requested by invalid server you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : NetBackup status code:
Netbackup Status Code 46
59 VOX : Backup and Recovery : NetBackup : NetBackup status code: 59 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page https://www.veritas.com/support/en_US/article.000040440 Solved! Go to Solution NetBackup status code: 59 Bhushan_w Level 3 04-10-2014 12:16 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, How to resolve the following problem. NetBackup status code: 59 Message: access to the client was not allowedMessage: access to the client was not allowed Solved! Go to Solution. Labels: Backup and Recovery NetBackup Windows Server (2003-2008) https://vox.veritas.com/t5/NetBackup/NetBackup-status-code-59/td-p/657203 2 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! 59 two possible reasons 1) RamNagalla Moderator Partner Trusted Advisor Certified 04-10-2014 12:58 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 59 two possible reasons 1) the Netbackup servers trying to communicate to the client does not listed under the client bp.conf(unix) registory key ( windows). then bpcd though the 59 error 2) the netbackup server that is communicating the client is not resolving the IP of the server or resolving the worg name which is not listed in bp.conf so please check what is the case that you have now... View solution in original post 0 Kudos Reply 5 Replies Hello, try this command muhanad_daher Level 6 Partner Accredited Certified 04-10-2014 12:55 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, try this command "admincmd" on master and media server bptestbpcd.exe -client client_name -debug -verbose. you will see the connectivity go to the client but didn't return back. - if windows stop the firewall and check insert in hosts files master and media ip/name. - if linux check ipfilter and stop it or grant access. check if the connection po
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 https://vox.veritas.com/t5/NetBackup/Status-Code-59-Access-to-the-Client-was-not-Allowed/td-p/481298 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 : Status Code 59 - Access to the Client was not Allo... VOX : Backup and Recovery : NetBackup : Status netbackup error Code 59 - Access to the Client was not Allo... 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 Status Code 59 - Access to the Client was not Allowed RCBrown_DKH Level 4 05-23-2012 12:48 PM Options Mark as New Bookmark Subscribe Subscribe to RSS netbackup error code Feed Highlight Print Email to a Friend Report Inappropriate Content I am receiving this error on a backup job. This is Netbackup 7.1 running on a Windows Server 2008 R2 Enterprise 64bit system. I have looked through other forum discussions on this, but haven't had any luck trying to fix this myself. Below are the job details and i have attached the BPCD log for futher assistance. 5/23/2012 3:41:52 PM - Info nbjm(pid=33196) starting backup job (jobid=200208) for client polaris.daykimball.org, policy PACS.Images.on.Polaris, schedule Incremental 5/23/2012 3:41:52 PM - Info nbjm(pid=33196) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=200208, request id:{206810E6-849C-4247-B470-B23EC1D76E6E}) 5/23/2012 3:41:52 PM - requesting resource PUCK_Scalar24_LTO2_R1 5/23/2012 3:41:52 PM - requesting resource puck1.NBU_CLIENT.MAXJOBS.polaris.daykimball.org 5/23/2012 3:41:52 PM - requesting resource puck1.NBU_POLICY.MAXJOBS.PACS.Images.on.Polaris 5/23/2012 3:41:53 PM - granted resource puck1.NBU_CLIENT.MAXJOBS.polaris.daykimball.org 5/23/2012 3:41:53 PM - granted resource puck1.NBU_POLICY.MAXJOBS.PACS.Images.on.Polaris 5/23/2012 3:41:53 PM - granted resource 000079 5/23/2012 3:41:53 PM - granted resource IBM.ULTRIUM-TD2.000 5/23/2012 3:41:53 PM - granted resource PUCK_Scalar24_LTO2_R1 5/23/2012 3:41:53 PM - estimated 0 Kbytes needed 5/23/2012 3:41:53 PM - begin Parent Job 5/23/2012 3:41:53 PM - begin Snapshot, Start Notify Script 5/23/2012 3:41:53 PM - Info RUNCMD(pi