Netbackup Error 59 Windows
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 Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact access to the client was not allowed 59 netbackup 7 Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas
Host Is Not An Authorized Server For Host Netbackup
Veritas PartnerNet 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
Netbackup Access To The Client Was Not Allowed Restore
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
Server Not Allowed Access (46)
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 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 error code 59 in netbackup 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 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 of the translation. You may also refer to the English Version of this knowledge basSERVICES 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 error code 58 in netbackup Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français netbackup error 48 Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 59 is received on all connection requested by invalid server Windows clients after the master server and clients have received new IP addresses. Article:000028288 Publish: Article URL:http://www.veritas.com/docs/000028288 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas https://www.veritas.com/support/en_US/article.000040440 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 Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 59 is received on all Windows clients after the master server and clients have received new https://www.veritas.com/support/en_US/article.000028288 IP addresses. Error Message <2> hosts_equal: gethostbyname failed for : The requested name is valid and was found in the (0)<16> bpcd valid_server: is not a server<4> bpcd exit_bpcd: FTL - BPCD EXIT STATUS 46 Solution Overview:A Status 59 can occur on all Windows clients after the master server and Windows clients have received new IP addresses, even once the new IP addresses have been assigned properly and appear in DNS. Windows clients can cache the old host names as well as the new host names. This will cause a Status 59 when attempting to back up the clients.Troubleshooting:Run the following command in a command prompt on one of the Windows clients: %
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/Status-Code-59-Access-to-the-Client-was-not-Allowed/td-p/481298 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your http://thekhantastic.blogspot.com/2013/03/netbackup-error-access-to-client-was.html search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Status not allowed Code 59 - Access to the Client was not Allo... VOX : Backup and Recovery : NetBackup : Status 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! access to the 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 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.day
for Client - C002-VM5.flab.com using Media Server - S002.flab.com on Storage Unit - S003-hcart3-robot-tld-1. Error: access to the client was not allowed (59) Job Details: 3/20/2013 3:22:34 AM - Info nbjm(pid=3192) starting backup job (jobid=60) for client C002-VM5.flab.com, policy C002-VM5_Data_VTL-on-S003, schedule Full 3/20/2013 3:22:34 AM - Info nbjm(pid=3192) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=60, request id:{FFEA615D-EA9B-4EFE-8F91-405D8A1725ED}) 3/20/2013 3:22:34 AM - requesting resource S003-hcart3-robot-tld-1 3/20/2013 3:22:34 AM - requesting resource s002-vm2.flab.com.NBU_CLIENT.MAXJOBS.C002-VM5.flab.com 3/20/2013 3:22:34 AM - requesting resource s002-vm2.flab.com.NBU_POLICY.MAXJOBS.C002-VM5_Data_VTL-on-S003 3/20/2013 3:22:34 AM - granted resource s002-vm2.flab.com.NBU_CLIENT.MAXJOBS.C002-VM5.flab.com 3/20/2013 3:22:34 AM - granted resource s002-vm2.flab.com.NBU_POLICY.MAXJOBS.C002-VM5_Data_VTL-on-S003 3/20/2013 3:22:34 AM - granted resource 4_2000 3/20/2013 3:22:34 AM - granted resource CRSTLINK.FIRESTRMRDRIVE.005 3/20/2013 3:22:34 AM - granted resource S003-hcart3-robot-tld-1 3/20/2013 3:22:34 AM - estimated 47792 Kbytes needed 3/20/2013 3:22:34 AM - Info nbjm(pid=3192) started backup job for client C002-VM5.flab.com, policy C002-VM5_Data_VTL-on-S003, schedule Full on storage unit S003-hcart3-robot-tld-1 3/20/2013 3:22:36 AM - started process bpbrm (2252) 3/20/2013 3:22:37 AM - Error bpbrm(pid=2252) bpcd on C002-VM5.flab.com exited with status 59: access to the client was not allowed 3/20/2013 3:22:37 AM - Info bpbrm(pid=2252) C002-VM5.flab.com is the host to backup data from 3/20/2013 3:22:37 AM - end writing access to the client was not allowed(59) I found that I had not added Media Server S003.flab.com to C002-VM2's Host properties as Media Server. That was it. Posted by faizan khan at 4:06 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: NetBackup, NetBackup Master Server, NetBackup Media Server, Storage Unit, Virtual Tape Library Newer Post Older Post Home Subscribe