NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Robotic status code 205

Robotic status code 205
HOWTO104711 | 2014-11-20
How To | CMS-XML

NetBackup status code: 205

NetBackup status code : 205
HOWTO104123 | 2014-11-20
How To | CMS-XML

STATUS CODE: 205, Backups fail with an intermittent status 205

STATUS CODE : 205 , Backups fail with an intermittent status 205
TECH33382 | 2013-10-23
Technical Solutions | CMS-XML

Error code 205 encountered during restores.

When attempting to restore data the restore fails or goes to the incomplete state, inside the job s details on the detailed status tab you can see the status code 205 with the message, cannot connect to server backup restore manager . The status code 205 means that the media server is unavailable, the backup restore manager refers to the process bpbrm, which is a media server layer process. Verify that the master server is resolving the host-name of the media server to the media server s configured IP address.
TECH75192 | 2010-01-22
Technical Solutions | CMS-XML

STATUS CODE 205: cannot connect to server backup restore manager

18:54:08.105 [5332.5864] 16 start_bptm: bpcd exit: cannot connect to server backup restore manager ( 205 )
TECH55499 | 2008-01-06
Technical Solutions | CMS-XML

GENERAL ERROR: Backups and restores may fail, or troubleshooting may be hindered if the NetBackup log directories are not readable and writeable by user and application processes.

or 13:26:43. 205 [14081] 2 create_sap_file_list: Creating file list container /usr/openv/netbackup/logs/user_ops/sap/.filelist.1204633602.14081 13:26:43.205 [14081] 16 create_sap_file_list: ERROR: couldn t open file container path: /usr/openv/netbackup/logs/user_ops/sap/.filelist.1204633602.14081
TECH52446 | 2013-11-21
Technical Solutions | CMS-XML

GENERAL ERROR: Backups and restores may fail, or troubleshooting may be hindered if the NetBackup log directories are not readable and writeable by user and application processes.

or 13:26:43. 205 [14081] 2 create_sap_file_list: Creating file list container /usr/openv/netbackup/logs/user_ops/sap/.filelist.1204633602.14081 13:26:43.205 [14081] 16 create_sap_file_list: ERROR: couldn t open file container path: /usr/openv/netbackup/logs/user_ops/sap/.filelist.1204633602.14081
TECH172344 | 2013-03-08
Technical Solutions | CMS-XML

VMware backups failing with Status 23 and Status 6

09:13:09.051 [9028.8948] 2 onlfi_vfms_logf: INF - VixDiskLibVim: vixdisklibvim_allowvmotion: Disable VMotion. 09:13:10. 205 [9028.8948] 2 onlfi_vfms_logf: INF - VixDiskLibVim: Licenses could not be retrieved for supplied user credentials. 09:13:10.439 [9028.8948] 2 onlfi_vfms_logf: INF - lockVM: vixdisklib_prepareforaccess returned:3014 [Insufficient permissions in the host operating system]
TECH227160 | 2014-12-17
Technical Solutions | CMS-XML

Exchange snapshot backup completes with a status code 130

If any errors are reported, these need to be cleared out as they could be contributing to the status code 130. Ref page 205 of the Netbackup 7.1 Exchange admin guide or page 218 of the 7.5 Exchange admin guide.
TECH191343 | 2013-10-29
Technical Solutions | CMS-XML

Lotus point-in-time restore via SAN client fails with status 5 without restoring logs

...snip... 13:41:45. 205 [4055] 2 parse_ft_resource_strings: FTRANS 0 1 28 myclient 43 SYMANTECFATPIPE 1.0 mymm 1 48 0
TECH160320 | 2013-10-24
Technical Solutions | CMS-XML

SAP automatic and application backup jobs fail with status 6 before transferring any data

13:26:43. 205 [14081] 2 create_sap_file_list: Creating file list container /usr/openv/netbackup/logs/user_ops/sap/.filelist.1204633602.14081 13:26:43.205 [14081] 16 create_sap_file_list: ERROR: couldn t open file container path: /usr/openv/netbackup/logs/user_ops/sap/.filelist.1204633602.14081 13:27:13.836 [14081] 4 find_file_name: input_file_list:
TECH58234 | 2013-10-24
Technical Solutions | CMS-XML

After upgrade to 7.1, catalog backups fail with a status code: 2 [ System call failed with status: 512 ]

16:45:54.205 [7997] 16 NBDBsystem: System call failed with status: 512 16:45:54. 205 [7997] 16 validate_database: Database validation failed for database NBDB 16:45:54.205 [7997] 4 db_error_add_to_file: Database validation failed for database NBDB.
TECH175134 | 2012-12-17
Technical Solutions | CMS-XML

All backups via media servers exited with status 811 (failed to communicate with resource requester)

09:41:28.191 [31329] 16 RequestInitialResources: MultiResReq.cpp:2395 resource request failed [150] 09:41:30. 205 [31329] 16 catch_signal: media manager terminated by parent process 09:41:30.205 [31329] 2 send_mds_msg: media_done 0 -1308195655 0 *NULL* 0 0
TECH163911 | 2012-06-25
Technical Solutions | CMS-XML

BUG REPORT: bpcatlist faults with Bus error core dump on hp-ux IA64 after application of the 6.5.4 patch release

#1 0x40000000000072d0:0 in buildQuery () at imagearc.c:559 #2 0x4000000000003f50:0 in main () at bpcatlist.c: 205 Workaround:
TECH76310 | 2009-01-02
Technical Solutions | CMS-XML

GENERAL ERROR: A "faulting application" error occurs in bpdbm.exe, before or during a catalog backup.

16:53:29. 205 [2820.2124] 16 delete_expired_backups: Bad image header: div-prod_1058639874_full
TECH38189 | 2005-01-04
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?