Netbackup Error Code 239
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
[ExtReqTa
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 STATUS CODE 236 or 239 or 245: NetBackup SAP backups with RMAN fail immediately without going active Article:000032151 Publish: Article URL:http://www.veritas.com/docs/000032151 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a https://www.veritas.com/support/en_US/article.TECH215866 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 SAP backups with RMAN are queued but fail immediately with one of these status codes.Status Code 236: the specified client https://www.veritas.com/support/en_US/article.TECH49018 does not exist in an active policy within the configuration databaseStatus Code 239: the specified client does not exist in the specified policyStatus Code 245: the specified policy is not of the correct client type Error Message The dbclient debug log will show the backup parameters that the client is specifying when queuing the backup request to the master server. Notice the fields for the policy and schedule names. The client type is the 4th field after the schedule name. In this example the policy and schedule names are correct, but the client type is '4' (Oracle RMAN) which does not match the policy type on the master server which is '17' (SAP).<4> sendRequest: sending BACKUP request to bprd<4> sendRequest: request = oracle dba myclient myclient myclient myPolicy myAppSchedule 7 oracle9 0 4 0 ...Note: If the policy or schedule fields are set to 'NONE', the master server will try to select an appropriate policy or schedule based on the client name. If a policy is specified, it must be of type SAP. Cause RMAN can be started to backup Oracle either directly or under the con
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/SQL-Backup-Failing-Status-239/td-p/431377 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 http://www.sqlserverf1.com/symantec-netbackup-status-code-236-to-status-code-240/ for Do you mean VOX : Backup and Recovery : NetBackup : SQL Backup Failing Status 239 VOX : Backup and Recovery : NetBackup : SQL Backup Failing Status 239 Subscribe netbackup error 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 SQL Backup Failing Status 239 Stanleyj Level 6 10-24-2011 11:28 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Backups have been running smoothly until last netbackup error code night when 2 of my sql servers are now erroring out with status 239 "the specified client does not exist in the specified policy" This makes absolutly no sense! The two servers along with the other 4 sql server were rebooted yesterday due to regular patch weekend and now they wont backup. I can do a regular file backup on both servers but am unable to run the sql backup. I have reinstalled the client and recreated the sql batch file still with the same results. Bothof these sql servers are VM's but that shouldnt matter considering i have one other sql server that is a vm who is not expeirncing this issue. The parent job seems to hang at this step: Info dbclient(pid=1520) INF - Created VDI object for SQL Server instance and its wierd but on each stream the clients show just the shortname and the schedule has a *NULL* for it. The parent job shows like its suppose to. Event logs on the server show these errors: Event ID: 18210 "BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device" Event ID: 1 "SQLVDI: Loc=TriggerAbo
Symantec NetBackup status code 236 to status code 240 December 28, 2014 SQLServerF1 Leave a comment Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features. Below are some of the NetBackup status error codes from Status Code 236 to Status Code 240 which may be received while using the Symantec NetBackup tool. NetBackup status code: 236 Message: the specified client does not exist in an active policy within the configuration database Explanation: A client name was not specified or the specified client does not exist. Recommended Action: Activate the required policy, correct the client name, or add the client to a policy that meets your needs. After you make the correction, retry the operation. NetBackup status code: 237 Message: the specified schedule does not exist in an active policy in the configuration database Explanation: The specified schedule does not exist in the NetBackup configuration. Recommended Action: Activate the required policy, correct the schedule name, or create a schedule in a policy that meets your needs. After you make the correction, retry the operation. NetBackup status code: 238 Message: the database contains conflicting or erroneous entries Explanation: The catalog has an inconsistent or a corrupted entry. Recommended Action: Obtain detailed troubleshooting information for bpdbm (on UNIX and Linux) or the NetBackup Database Manager service (on Windows) by creating a debug log directory for it. Then, retry the operation, save resulting debug log, and call customer support. NetBackup status code: 239 Message: the specified client does not exist in the specified policy Explanation: The specified client is not a member of the specified policy. Recommended Action: Correct the client name specification, specify a different policy, or add the required client name to the policy. After you make the correction, retry the operation. NetBackup status code: 240 Message: no schedules of the correct type exist in this policy Explanation: The appropriate schedule was not found in the specified policy. For example, a user backup specified a policy name but no user backup schedule exists in that policy. Recommended Action: Specify a different policy or