NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

EMM interface initialization failed, status = 295

1067 error pop up for starting the service. application log - EMM interface initialization failed, status = 295
TECH189038 | 2014-03-25
Technical Solutions | CMS-XML

NetBackup status code: 295

NetBackup status code : 295
HOWTO90704 | 2013-10-02
How To | CMS-XML

NetBackup status code: 295

NetBackup status code : 295
HOWTO51052 | 2012-11-19
How To | CMS-XML

NetBackup status code: 295

NetBackup status code : 295
HOWTO35163 | 2010-10-29
How To | CMS-XML

NetBackup 7.1 status 2 on catalog backups due to validation failures

10:46:53. 295 [19412] 4 validate_database: Exiting. rc = 11
TECH162601 | 2012-10-04
Technical Solutions | CMS-XML

Restores of large virtual machines are failing with "EXIT STATUS 24: socket write failed"

15:33:47. 295 [9821] 2 readline: EXIT STATUS 24
TECH171144 | 2012-04-04
Technical Solutions | CMS-XML

RMAN backup to sbt_tape is much slower than backup to DISK, may fail with status 13

[8095] 2 xbsa_senddata: INF - entering 16:44:28. 295 [8095] 4 VxBSASendData: INF - entering SendData. 16:44:28.295 [8095] 4 dbc_put: INF - sending 262144 bytes
TECH130209 | 2011-09-21
Technical Solutions | CMS-XML

Many small jobs in a large MPX group may result in slow performance and status 13 or status 6

12:17:32.990 [22497] 4 write_backup: successfully wrote backup id client2_1249906424, copy 1, 545 Kbytes 12:17:33. 295 [22497] 2 write_backup: waiting 10 seconds for start of another backup 12:18:08.512 [22497] 4 write_backup: successfully wrote backup id myclient_1249906097, copy 1, 1058 Kbytes
TECH135606 | 2011-04-26
Technical Solutions | CMS-XML

BUG REPORT: Status 26, Failed to store the results of the backup in the DARS database

In the example below, the Oracle instance has been in production for a significant amount of time and the System Change Number (SCN) has become very large resulting in a Checkpoint Number that is larger than 4,294,967, 295 , which is the largest value expected by NetBackup. Log Files The Job Details
TECH130783 | 2011-03-02
Technical Solutions | CMS-XML

BUG REPORT: A backup job will mount and unmount the same media over and over until manually canceled or the job fails with a Status Code 196.

16:36:53.201 [7400.10204] 2 process_tapealert: TapeAlert returned 0x00000800 0x00000000 (from tapealert_and_release) 16:36:53. 295 [7400.10204] 8 process_tapealert: TapeAlert Code: 0x15, Type:Warning, Flag: CLEAN PERIODIC, from drive (index -1), Media Id 00222l The tape alert at this time should trigger a cleaning request and the robot should mount cleaning media.
TECH53117 | 2010-01-26
Technical Solutions | CMS-XML

GENERAL ERROR: On a Windows 2008 client, backups are failing with one of the following errors: cannot connect on socket (status code 25) or timed out connecting to client (status code 54) or backup job simply hanging

10:36:31. 295 [11529] 2 logconnections: BPDBM CONNECT FROM 1.1.1.100.57105 TO 1.1.1.200.13724
TECH68765 | 2010-01-11
Technical Solutions | CMS-XML

Backups of Novell OES Linux server fail with 'FFFDFFB1 An internal TSA error has occurred.'

The following can be seen in the BPCD log on the NetWare client that is being used to backup the OES Linux server: 4:07:18 PM: [ 295 .662] 2 tar_backup::backup_create: TAR - backup filename = /netware
TECH55415 | 2008-01-08
Technical Solutions | CMS-XML

NDMP bakup failing with status 99 | Symantec Connect

04:51:16.497 [7776] <16> bpbrm main: db_flistsend failed: network connection timed out (41) 06:36:01. 295 [18970] <16> bpbrm main: db_flistsend failed: network connection timed out (41) 07:09:17.084 [1779] <16> bpbrm main: db_flistsend failed: network connection timed out (41)
Connect Forums | HTML

I am getting same error 2826 while restoring | Symantec Connect

11:06:13.227 [13460] <2> vnet_vnetd_daemon_socket: ../../libvlibs/vnet_vnetd.c.397: 0: ipc_string: /tmp/vnet-13376333604170772171000000188-kmaaia 11:06:13. 295 [13460] <2> connect_bprd_socket: [13456] data socket to bprd is connected port = 0, fd = 8, DATAPORT=0, duping to stdin
Connect Forums | HTML

Snapshot error(not in cluster) | Symantec Connect

Snapshot error(not in cluster) 21:02:31. 295 [56968.48260] <2> onlfi_vfms_logf: snapshot services: devicefi:Tue Jun 19 2012 21:02:31.279000 libscsitool: ERROR: CScsiTool::UpdateScsiAddressInfo() failed for device \\.\PHYSICALDRIVE1.
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?