Error 239 Netbackup
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 netbackup error 230 In CommunityCategoryBoardResourcesUsers netbackup error 236 turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you netbackup error code 239 type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : SQL Backup Failing Status 239 VOX : Backup and Recovery : status 239 netbackup NetBackup : SQL Backup Failing Status 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 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 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
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... https://vox.veritas.com/t5/NetBackup/SQL-Backup-Failing-Status-239/td-p/431377 VOX : Backup and Recovery : NetBackup : 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 https://vox.veritas.com/t5/NetBackup/BPARCHIVE-the-specified-client-does-not-exist-in-the-specified/td-p/576861 code 239 righthanded Level 4 12-03-2012 09:01 PM Options Mark as 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
FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • Log in Backup Central Forums Forum Index » Symantec NetBackup » error 239 and virtual hostnames http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/symantec-netbackup-18/error-239-and-virtual-hostnames-51005/ The time now is Mon Oct 10, 2016 4:39 pm View previous topic | View next topic Page 1 of 1 error 239 and virtual hostnames Author Message David Magda Guest error 239 and virtual hostnames http://sysarticles.com/netbackup-status-code-239/ Hello, I'm having a little trouble with jobs returning error 239 which bperror(1M) reports as: the specified client does not exist in the specified policy The specified client is not a member of the specified netbackup error policy. This is with NetBackup 4.5 on Solaris 8, and all the jobs involve going to a 'virtual host' (not the system's real hostname but one of its aliases). All the jobs are Oracle BLIBs but I think that's because we're only using the virtual host with those types of jobs. We would have a policy called 'somedb_blib' under schedules 'oracle_full' and 'oracle_inc' (incremental) going to a virtual hostname of 'somedb'. The error 239 netbackup real hostname would be 'hostdb1'. The 'somedb_blib' policy is running fine to the virtaul hostname. The error 239 comes in for jobs in in policy 'somedb_blib' in schedule 'ALL' going to 'hostdb1'. So basically the policy is trying to go to the real hostname and do the job there. We have multiple jobs that use the virtual hostname: they all run fine to the virtual hostname, but then try to run to the real hostname and return the 239 error code. Any ideas? -- David Magda
Leave a comment Follow Problem Tanımı: Günlerce, haftalarca hatta aylarca düzgün yedek aldıktan sonra birden bire aşağıdaki hata kodunu ve ekran görüntüsünü almaya başladıysanız, bu çözüm sizin için: Hata Kodu: 239 Ekran Görüntüsü: Ana job: 4/19/2014 11:43:48 PM - Info nbjm(pid=5772) starting backup job (jobid=1627586) for client clientname, policy MSSQL_clientname_DBNAME_test, schedule Full_1M 4/19/2014 11:43:48 PM - Info nbjm(pid=5772) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=1627586, request id:{30E2C633-C9C4-4520-9F0B-F291957FDA12}) 4/19/2014 11:43:48 PM - requesting resource stu_disk_sp-nbappliance21 4/19/2014 11:43:48 PM - requesting resource masterserver.domain.com.NBU_CLIENT.MAXJOBS.clientname 4/19/2014 11:43:48 PM - requesting resource masterserver.domain.com.NBU_POLICY.MAXJOBS.MSSQL_clientname_DBNAME_test 4/19/2014 11:43:48 PM - granted resource masterserver.domain.com.NBU_CLIENT.MAXJOBS.clientname 4/19/2014 11:43:48 PM - granted resource masterserver.domain.com.NBU_POLICY.MAXJOBS.MSSQL_clientname_DBNAME_test 4/19/2014 11:43:48 PM - granted resource stu_disk_sp-nbappliance21 4/19/2014 11:43:48 PM - estimated 0 Kbytes needed 4/19/2014 11:43:48 PM - Info nbjm(pid=5772) started backup (backupid=clientname_1397940228) job for client clientname, policy MSSQL_clientname_DBNAME_test, schedule Full_1M on storage unit stu_disk_sp-nbappliance21 4/19/2014 11:43:49 PM - started process bpbrm (9628) 4/19/2014 11:43:54 PM - connecting 4/19/2014 11:43:54 PM - Info bpbrm(pid=9628) clientname is the host to backup data from 4/19/2014 11:43:54 PM - Info bpbrm(pid=9628) reading file list for client 4/19/2014 11:43:55 PM - Info bpbrm(pid=9628) starting bphdb on client 4/19/2014 11:43:55 PM - Info bphdb(pid=15948) Backup started 4/19/2014 11:43:55 PM - connected; connect time: 0:00:01 4/19/2014 11:43:57 PM - Info dbclient(pid=17552) INF - BACKUP STARTED USING 4/19/2014 11:43:57 PM - Info dbclient(pid=17552) Microsoft SQL Server 2012 (SP1) - 11.0.3381.0 (X64) 4/19/2014 11:43:57 PM - Info dbclient(pid=17552) Aug 23 2013 20:08:13 4/19/2014 11:43:57 PM - Info dbclient(pid=17552) Copyright (c) Microsoft Corporation 4/19/2014 11:43:57 PM - Info dbclient(pid=17552) Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.2