Netbackup Error 239 Codes
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 MS SQL and other XBSA Backups fail with status code 239 reported after applying the NetBackup 7.5.0.7 maintenance release. Article:000021155 Publish: Article URL:http://www.veritas.com/docs/000021155 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 NetBackup for Microsoft SQL Server backups fail with status code 239 (the specified client does not exist in the specified policy) reported after applying the NetBackup 7.5.0.7 maintenance release. Other XBSA based backups such as DB2 and Oracle RMAN have also been reported to fail for the same reason. Error Message Sample log snippets: Progress log:INF - BACKUP STARTED USING
Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1
Batch = SQL_BCK_LOGS.bch, Op# = 1
INF - Using backup image
INF - backup log "BA_SupplyChain" to VIRTUAL_DEVICE='VNBU0-6976-2800-1392709178'
with stats = 10, checksum, stop_on_error, blocksize = 65536, maxtransfersize =
4194304, buffercount = 2
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance
is <300> seconds.
Backup started Tue Feb 18 18:39:38 2014 nbpem log:2/18/2014 15:39:47.524 [Debug] NB 51216 nbpem 116 PID:6768 TID:5360 File ID:116
[jobid=-1 job_group_id=-1 client=sydssql05 type=2 server=*NULL*
task=ID:000000000570B848 CTX:000000000570B848 policy=P-P21-BE-SQL-LOGS] 4
[ExtReqTask::taskCompleted] (ID:000000000570B848 CTX:0000000
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 : BPARCHIVE : the specified client does not exist in... VOX : Backup and Recovery : NetBackup https://www.veritas.com/support/en_US/article.TECH215866 : BPARCHIVE : the specified client does not exist in... 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 BPARCHIVE : the specified client does not exist in the specified policy error code 239 righthanded Level 4 12-03-2012 09:01 PM Options Mark as https://vox.veritas.com/t5/NetBackup/BPARCHIVE-the-specified-client-does-not-exist-in-the-specified/td-p/576861 New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Good Day Hi Everyone, Anybody could help me resolve this issue? I already add/specify the client in the policy. the command that i issued was: /usr/openv/netbackup/bin/bparchive -p
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 https://vox.veritas.com/t5/NetBackup/Error-239/td-p/764054 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 : Error 239 http://www.tek-tips.com/viewthread.cfm?qid=1487021 VOX : Backup and Recovery : NetBackup : Error 239 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 netbackup error Solution Error 239 MagMan Level 3 01-25-2016 07:20 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content hi, some backups failed with error code 239. these client are correct on the NBU Policy, and, the DNS resolution is OK. the resolution with bpclntcmd -hn and with -ip are correct. the communication is OK too. when i lanch the backup from command netbackup error 239 line with a lowercase of the client name that give the error : EXIT STATUS 239: the specified client does not exist in the specified policy. when i changed the client name to the uppercase, and lanched again, it's pass. when launching from GUI, it's OK. when launching with all fqdn name it's pass, same if launching from command line with IP adress. the issue appear just when launching with lowercase... the backups are launched from a scheduler (that run the command bpbackup...). the Issue appear aleatory, after we upgraded the Master; media servers from 7.5.0.6 to 7.7.1 (Netbackup Enterprise). master is windows 2008 R2 Standard Edition. please help Solved! Go to Solution. Labels: 7.7 Backing Up Backup and Recovery NetBackup Troubleshooting Upgrade Windows Server (2003-2008) 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! Re: Error 239 Marianne Moderator Partner Trusted Advisor Accredited Certified 01-27-2016 12:08 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content So, on master server you have something like this in hosts file (according to bpclntcmd output): 10.11.18.53 server-A.dm.ok.domain server-A Is this right? I don't see any alias for all uppercase in bpclntcmd output? If you have added another alias in the meantime
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Symantec: NetBackup Forum at Tek-Tips HomeForumsServer RackBack-up SystemsSymantec: NetBackup Forum User Initiated - Exit Status 239 - Abnormal exit? thread776-1487021 Forum Search FAQs Links MVPs User Initiated - Exit Status 239 - Abnormal exit? User Initiated - Exit Status 239 - Abnormal exit? Dorga (MIS) (OP) 14 Jul 08 17:27 Server: ntabcd622bpbackup command ran from server: ntabcd622Problem - Policy exists as below, client is listed in policy, and policy has two user backup schedules. yet, I still get this.D:\NetBackup\bin>bpbackup -p SQL -s SQL -w c:\autoexec.batEXIT STATUS 239: the specified client does not exist in the specified policyIf I disable the policy, and then run the job, I get a 247 (Policy not active). If I remove the client from the policy, I get a 236. If I add a normal schedule, and kick a job off from the master, it works fine.Ideas? Symantic support can not see past the 239 and insist I need to add the client name.D:\NetBackup\bin>bppllist sql -U------------------------------------------------------------Policy Name:sqlPolicy Type:StandardActive:yesEffective date:06/17/2008 12:30:00Client Compress:noFollow NFS Mounts:yesCross Mount Points:yesCollect TIR info:noBlock Incremental:noMult. Data Streams:yesClient Encrypt:noCheckpoint:yesInterval:15Pol