NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Robotic status code 224

Robotic status code 224
HOWTO104729 | 2014-11-20
How To | CMS-XML

NetBackup status code: 224

NetBackup status code : 224
HOWTO104139 | 2014-11-20
How To | CMS-XML

BUG REPORT: Vault eject fails with error 224 (Control daemon connect or protocol error) due to tapes being in_transit.

BUG REPORT: Vault eject fails with error 224 (Control daemon connect or protocol error ) due to tapes being in_transit.
TECH125927 | 2013-10-24
Technical Solutions | CMS-XML

Robotic status code 224

Robotic status code 224
HOWTO91226 | 2013-10-02
How To | CMS-XML

NetBackup status code: 224

NetBackup status code : 224
HOWTO90636 | 2013-10-02
How To | CMS-XML

NetBackup status code: 224

NetBackup status code : 224
HOWTO50984 | 2012-11-19
How To | CMS-XML

Robotic status code 224

Robotic status code 224
HOWTO51576 | 2012-11-19
How To | CMS-XML

NetBackup status code: 224

NetBackup status code : 224
HOWTO35095 | 2010-10-29
How To | CMS-XML

Robotic status code: 224

Robotic status code : 224
HOWTO35686 | 2010-10-29
How To | CMS-XML

Since upgrading to NetBackup 7.0.x restore of NDMP fails with status 5 and bptm core dumps

8/19/2011 12:39:09 PM - Error ndmpagent(pid=31284) 10.54. 224 .200: Recovery status ndmp_recovery_failed_not_found for file path / file
TECH155417 | 2013-11-12
Technical Solutions | CMS-XML

Duplications to ndmp device fail with status 90

12:06:40.193 [7672.7764] 2 read_data: Total Kbytes transferred 13956288 12:06:40. 224 [7672.7764] 2 read_position: read position on drive index 32, is LBA 156255 12:06:40.224 [7672.7764] 2 ndmp_setup_for_read: CINDEX 0, twin_index 0 is_tir 0 is_ndmp 0
TECH206010 | 2013-10-01
Technical Solutions | CMS-XML

Shadow Copy Components backup with DFSR ends with EXIT STATUS 69: invalid filelist specification

bpbkar log snip at General Level = 2: 20:22:56.064: [6004.3724] 2 ov_log::v_globallog: INF - Status fs_writer_metadata_failure (0xe000fec9) generating logical directory tree when attaching to Shadow?Copy?Components Dle 20:22:56.079: [6004.3724] 2 ov_log::v_globallog: INF - SS: Status fs_writer_metadata_failure (0xe000fec9) attaching Shadow?Copy?Components in SystemState::InitializeShadowCopy: 224
TECH209425 | 2013-08-12
Technical Solutions | CMS-XML

Backup to MSDP randomly failing with status 252

Number of containers : 21438 Average container size : 235299825 bytes ( 224 .40mb) Space allocated for containers : 5044357666677 bytes (4.59TB)
TECH141991 | 2012-08-18
Technical Solutions | CMS-XML

All backups are failing with status 63 (process was killed by a signal)

log on the media server shows the following error: 20:36:58. 224 [14884] 16 write_data: media manager exiting because bpbrm is no longer active 20:36:58.225 [14884] 2 check_error_history: just tpunmount: called from bptm line 17945, exit_status = 174
TECH65012 | 2012-01-06
Technical Solutions | CMS-XML

Full backups fail intermittently with status 40 when they run for several hours

...snip... 21:17:15. 224 [16154734] 2 process_cpr_message: Sent bpdbm the CPR info. 21:25:34.865 [16154734] 2 bpbrm main: client myclient EXIT STATUS = 40: network connection broken
TECH176851 | 2011-12-13
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?