NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 613

NetBackup status code : 613
HOWTO104310 | 2014-11-20
How To | CMS-XML

Windows SAP Oracle backup of files larger than 4 GB fails with status 6 after unable to stat file

10:43:07.098 [1552.4628] 4 do_file_backup: System detected error, operation aborted. The file has a size greater than 4 GB. 06/26/2013 11:51 PM 4, 613 ,734,400 PRODA.DATA1
TECH209820 | 2013-08-23
Technical Solutions | CMS-XML

Backup always failing with socket error | Symantec Connect

Backup always failing with socket error 18:14:50. 613 [15240.16364] <2> bpcd peer_hostname: gethostbyaddr failed:The requested name is valid, but no data of the requested type was found.
Connect Forums | HTML

Backup failing with error 25 - cannot connect on socket | Symantec Connect

Backup failing with error 25 - cannot connect on socket 07:54:17.563 [19208] <2> vnet_pbxconnect: pbxConnectEx Succeeded 07:54:17. 613 [19208] <8> do_pbx_service: [vnet_connect.c:2108] via PBX VNETD CONNECT FROM 10.5.159.8.60928 TO 20.60.103.173.1556 fd = 4
Connect Forums | HTML

Status Code Chart

612 613 614
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

NetBackup messages

cannot connect to read media server See NetBackup status code : 613 cannot connect to server backup restore manager
HOWTO103773 | 2014-11-20
How To | CMS-XML

Exchange 2010/2013 Database restore to Recovery Database succeeds but size is wrong

4:08:48.550 PM: [4776.4348] 2 tar_base::backup_finish: TAR - restore: elapsed time: 365 secs 18390260 bps 4:08:48. 613 PM: [4776.4348] 2 tar_base::v_vtarmsgw: INF - TAR EXITING WITH STATUS = 0 4:08:48.613 PM: [4776.4348] 2 tar_base::v_vtarmsgw: INF - TAR RESTORED 6 OF 6 FILES SUCCESSFULLY
TECH213326 | 2014-05-22
Technical Solutions | CMS-XML

Drive Troubleshooting | Symantec Connect

11:05:49. 613 [7848] <2> io_open: file /usr/openv/netbackup/db/media/tpreq/drive_hp.ultrium1-scsi.000 successfully opened (mode 2)
Connect Forums | HTML

The Backup Archive and Restore (nbwin.exe) console takes a long time to launch

12:13:10 . 613 [5848.3812] 2 ov_log::v_globallog: INF - VirtApi DLL WAS LOADED FROM VirtApi.dll.! 12:14:42
TECH228139 | 2015-02-05
Technical Solutions | CMS-XML

After upgrading to Netbackup 7.5.0.6 or 7.6, bpbkar32.exe may fault on Windows clustered servers.

7.500. 613 .610, faulting module bedsnt5.dll, version 14.1.1003.0, fault address
TECH209546 | 2014-08-12
Technical Solutions | CMS-XML

hyper-v backups may fail with "client/server handshaking failed(26)" when the NetBackup volume on the hyper-v node is full

Faulting application name: bpbrm.exe, version: 7.500. 613 .610, time stamp: 0x51b68fad
TECH215096 | 2014-02-18
Technical Solutions | CMS-XML

VMWare backup with "Enable file recovery from VM backup" causes bpbkar32.exe to application fault

Faulting application name: bpbkar32.exe, version: 7.500. 613 .610, time stamp: 0x51b68fdc
TECH213328 | 2013-12-24
Technical Solutions | CMS-XML

ndmp restore to alternate media server failing in cluster environment

07:47:21.610 [13784] 2 process_request: requesting_clnt_hostname = ccname masterCluster 07:47:21. 613 [13784] 2 restorefiles: mpx_restore_possible = 1 07:47:21.613 [13784] 2 restorefiles: browse_client = ndmp1
TECH71940 | 2013-12-16
Technical Solutions | CMS-XML

BUG REPORT: After upgrade to NetBackup 7.5, access violations are reported if more than one q_image_list is running.

07:41:40. 613 [8438] 2 xpress_image: Compress /usr/openv/netbackup/db/images/CLIENT1/1234000000/client1_1234567890 _FULL.f The second q_image_list_files
TECH193968 | 2012-07-29
Technical Solutions | CMS-XML

Tape Contents report returns cannot connect on socket (25) for non-root users

12:21:44. 613 [13926] 2 getJobId: returning 12:21:44.615 [13926] 16 bpmedialist: Unable to get job id: cannot connect on socket (25) 12:21:44.615 [13926] 16 bpmedialist: cannot connect on socket
TECH191017 | 2012-06-14
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?