Bpcd Error 59
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision access to the client was not allowed 59 netbackup 7 2016 Developers Blogs Groups Vision 2016 Sign In
Netbackup Error 59 Windows
CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow host is not an authorized server for host netbackup down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : server not allowed access (46) NetBackup : ERROR 59 Access to the client was not allowed VOX : Backup and Recovery : NetBackup : ERROR 59 Access to the client was not allowed Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page ERROR
Netbackup Restore Access To The Client Was Not Allowed
59 Access to the client was not allowed snawaz3 Level 6 08-01-2013 07:31 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content one of my servers stopped backing up with an error code 59. i have attached the bpcd from the client nduhbss01 10.0.9.46. my master/media server is ndumgt001 10.0.9.171. i am not sure how to interept the log but i see 2 entries which do not seem write to me. 02:16:18.992 [4848.8064] <2> bpcd peer_hostname: Connection from host ndumgt007.ndu.edu (10.0.9.65) port 63031 02:16:18.992 [4848.8064] <2> bpcd valid_server: comparing NDUMGT001 and ndumgt007.ndu.edu 02:16:19.004 [4848.8064] <4> bpcd valid_server: ndumgt007.ndu.edu is not a master server 02:16:19.004 [4848.8064] <16> bpcd valid_server: ndumgt007.ndu.edu is not a media server either mdumgt007 is the retina scan server. ndumgt001 10.0.9.171 is the netbackup server 15:13:01.291 [10232.10236] <4> bpcd valid_server: 10.0.9.171 is not a master server 15:13:01.291 [10232.10236] <16> bpcd valid_serv
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 netbackup error 48 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down netbackup error code 58 your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean
Bptestbpcd
VOX : Backup and Recovery : NetBackup : error 59 when doing a restore. VOX : Backup and Recovery : NetBackup : error 59 when doing a restore. Subscribe to RSS Feed Mark https://vox.veritas.com/t5/NetBackup/ERROR-59-Access-to-the-client-was-not-allowed/td-p/599298 Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution error 59 when doing a restore. cyberninja Level 6 09-25-2014 07:55 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, We are trying to do a restore of a file from a https://vox.veritas.com/t5/NetBackup/error-59-when-doing-a-restore/td-p/713821 incremental WMware backup. The media server is a Windows 2008 and the client is a Suse 11 server. We are trying to retore the file to anther server that has a NetBcakup client installed. What we have done so far At first we tried to restore the the file to the Windows media server and it didn't work. My co-worker put in a ticket to Symantec (07351850) and they say that you can't restore a Linux file to a windows machine. The tech said to restore to another Linux/Unix based client? He also sent us this tech note http://www.symantec.com/docs/TECH31677. My co-worker sent this to the tech working the case after we tryied to restore to the Linux client. Made several attempts, but they failed. Seems I have a connectivity issue between the media server (B) that originally performed the backup and the client (C) I am attempting to restore to. For the client (C) I am attempting to restore to, a different media server (A) is used. Connectivity between media server A and client C is obviously OK. bpclntcmd output (-pn -hn and -ip) is as expected on B and C. I just d
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas https://www.veritas.com/support/en_US/article.TECH18551 Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) https://vox.veritas.com/t5/NetBackup/Status-Code-59-Access-to-the-Client-was-not-Allowed/td-p/481298 English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backups fail with a status code 59: "access to the client not allowed 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 Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In access to the 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 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 t
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 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 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 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