NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

STATUS CODE 236 or 239 or 245: NetBackup SAP backups with RMAN fail immediately without going active

236
TECH49018 | 2013-10-03
Technical Solutions | CMS-XML

Robotic status code 236

Robotic status code 236
HOWTO91236 | 2013-10-02
How To | CMS-XML

NetBackup status code: 236

NetBackup status code : 236
HOWTO90648 | 2013-10-02
How To | CMS-XML

NetBackup status code: 236

NetBackup status code : 236
HOWTO50996 | 2012-11-19
How To | CMS-XML

Robotic status code 236

Robotic status code 236
HOWTO51586 | 2012-11-19
How To | CMS-XML

NetBackup status code: 236

NetBackup status code : 236
HOWTO35107 | 2010-10-29
How To | CMS-XML

Robotic status code: 236

Robotic status code : 236
HOWTO35696 | 2010-10-29
How To | CMS-XML

STATUS CODE: 236: A user initiated backup is failing with an error "the specified client does not exist in an active policy within the configuration database"

The specified client does not exist in an active policy within the configuration database( 236 ).
TECH36720 | 2008-01-25
Technical Solutions | CMS-XML

GENERAL ERROR: <16> vltrun@DoCatalogBu^XXX: Catalog Backup step is failed! the specified client does not exist in an active policy within the configuration database (236)

16 vltrun@DoCatalogBu^XXX: Catalog Backup step is failed! the specified client does not exist in an active policy within the configuration database ( 236 )
TECH46742 | 2007-01-15
Technical Solutions | CMS-XML

Database RMAN backup timeout with BPBRM STATUS 41: network connection timed out

11:31:16.082 [892974] bpbrm main: wrote CONTINUE on comm_sock 11:32:38. 236 [892974] bpbrm mm_sig: received ready signal from media manager 11:32:38.237 [892974] bpbrm readline: retrying partial read from fgets ::
TECH57679 | 2013-10-24
Technical Solutions | CMS-XML

Active Directory GRT restore failing with status code 2808 and 5

10/8/2013 19:39:58.967 [[fsys\adgran] ] FROM BEDS ADProv:executing an add on CN=nbu_user,OU=hq_users,DC=com,DC=testdomain at L: 236 (../BEDSContext.cpp:124)
TECH211394 | 2013-10-14
Technical Solutions | CMS-XML

Backup fails with error (status code: 98): "Error requesting media (tpreq)" or "TpErrno = Request terminated because host is not validated for volume pool.error requesting media (tpreq)(98)"

2 mount_open_media: Waiting for mount of media id s00001 on server xxxxx.xx.xx.com 16:10:44 [203.222] 2 getsockconnected: host=xxxx.xxx.xxx.com service=bpdbm address=130.63. 236 .131 protocol=tcp non-reserved port=13721 16:10:45 [203.222] 16 mount_open_media: error requesting media, TpErrno = Request terminated because host not validated for volume pool
TECH17423 | 2013-05-08
Technical Solutions | CMS-XML

Shadow Copy Components / System State backup fails with status code 13 (file read failed)

2:26:16. 236 PM: [13388.16224] 2 ov_log::v_globallog: ERR - beds_attachtodle():fs_attachtodle() DeviceName: System?State BackupReason:0x2 Failed! (0xe000fec9:A failure occurred accessing the Writer metadata.
TECH161331 | 2012-04-27
Technical Solutions | CMS-XML

NetBackup catalog recovery fails with STATUS 13, if the previous EMM database used an alternative staging directory other than default /usr/openv/db/staging

but during do_nbdb_recovery step, NetBackup looks for the restored files under the local file system on /usr/openv/db/staging and immediately after we have the STATUS 13. 10:21:10. 236 [27530] 16 readvxdbms_conffile: Can t open configuration file: /usr/openv/db/staging/vxdbms.conf
TECH62929 | 2012-01-17
Technical Solutions | CMS-XML

Oracle RMAN backups with Oracle metadata collection fail with status 26 and status 1.

the requested operation was successfully completed 15:45:34. 236 [5258] 8 check_for_failed_metadata_cataloging_jobs: WRN - Metadata cataloging for a child job failed 15:45:34.236 [5258] 16 bphdb Exit: ERR - bphdb exit status = 1: the requested operation was partially successful
TECH170966 | 2012-01-04
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?