Error 59 Netbackup
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 netbackup error 58 can't connect to client Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語
Netbackup Client Change Master Server
한국어 Português Español USA Site: Veritas Veritas PartnerNet Backups fail with a status code 59: "access to the client
Cannot Connect To Client 58 Netbackup
was not allowed." Article:000084066 Publish: Article URL:http://www.veritas.com/docs/000084066 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile
Netbackup Error 46
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 Backups fail with a status code 59: "access to the client was not allowed." Error Message status code 59: access to client was not allowed Solution NOTE: The contents of this article netbackup error 23 are not relevant in an environment where the VERITAS NetBackup master or media server has the "REQUIRED_INTERFACE" directive specified in the bp.conf file.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. There are a number of well-documented and effective ways to troubleshoot this problem, (e.g., creating a bpcd log on the client and then re-attempting the backup) but the UNIX last command is a quick and simple way to clearly establish the cause of this problem.Connecting to the NetBackup client from the NetBackup server (using any of the standard terminal connection commands: telnet, ssh, rlogin, etc) and immediately running the last command displays the host name that must match a SERVER entry in the client's bp.conf file in order to avoid the status 59 failure.For example, consider a scenario in which a status 59 failure is occurring when attempting a backup of a UNIX NetBackup client named "NBUClient." The NetBackup media server (or the NetBackup master server, in a single-server or NetBackup BusinessServer environment) involved in this backup is named "NBUServer".The
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas netbackup error 49 Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile netbackup error 59 access to the client was not allowed Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English netbackup error code 59 Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 59 is received on all Windows clients after the master https://www.veritas.com/support/en_US/article.TECH18551 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 Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. https://www.veritas.com/support/en_US/article.000028288 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 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 pro
1. Login on http://backupforrestore.blogspot.com/2012/03/netbackup-error-code-59-troubleshooting.html the server which is failing with error code 59. Create folder with name "bpcd" at following location. and Set Verbose level to 5. c: or D: /program file/veritas/netbackup/logs/ (windows) netbackup error usr/openv/netbackup/logs/ (unix) Execute pbtestbpcd command from Media Server . Step 2. Check the " bpcd " folder , which will have log file .Check the file at the end where you will fine the connect to client FQDN of media server whose entry is missing in the Media Server list of you server. Step 3. Add the media server entry a. run ->regedit -->Hkey local Machime-->software-->veritas--> netbackup-->config.file open this file and add media server entry at the end. (windows) b. cd /usr/openv/netbackup/bp.conf add media server entry at the end (unix/linux/solaris) After adding the entry our backup will complete successfully. Posted by RB Singh at 01:47 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Home Subscribe to: Post Comments (Atom) Followers About Me RB Singh View my complete profile Blog Archive Blog Archive May (1) March (1) Awesome Inc. template. Powered by Blogger.