NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 288

NetBackup status code : 288
HOWTO104200 | 2014-11-20
How To | CMS-XML

NetBackup status code 288: vault eject partially succeeded

288
TECH58787 | 2009-01-12
Technical Solutions | CMS-XML

NBU Automated Vaulting issue : 287/288 error code | Symantec Connect

NBU Automated Vaulting issue : 287/ 288 error code
Connect Forums | HTML

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

Bug ID Parent Etrack 1915250 - Tape in_transit causes vault eject error 224 (final status 288 ) and incorrect Robot Pick List report. Defect Etrack 1918715 - Tape in_transit causes vault eject error 224 (final status 288) and incorrect Robot Pick List report.
TECH125927 | 2013-10-24
Technical Solutions | CMS-XML

Backups of the same client using some media servers fail with status 21: socket open failed

on the client host confirms that the media server host can connect to the client host and start the bpcd service. 14:20:34.319 [9621694] 2 ProcessRequests: vnetd.c. 288 : msg: VNETD ACCEPT FROM 2.2.2.2.59499 TO 2.2.2.2.13724 fd = 4 14:20:34.344 [9621694] 2 ProcessRequests: vnetd.c.349: msg: Request vn_request_service_socket(6)
TECH129303 | 2013-10-24
Technical Solutions | CMS-XML

NetBackup online catalog backups complete with STATUS 2 on NBDB database validation

08:03:05. 288 [12101] 4 validate_database: Executing . /usr/openv/db/vxdbms_env.sh /usr/openv/db/bin/dbvalid -q -fx -c UID=dba;PWD=******;ENG=validation_eng;LINKS=shmem;START=/usr/openv/db/bin/dbeng11 \ /usr/openv/db/staging/NBDB.db\ -ds \ /usr/openv/db/staging\
TECH141061 | 2012-01-19
Technical Solutions | CMS-XML

A NetBackup Master/Media Server or NetBackup Media Server, running Microsoft Cluster Server (MSCS), freezes after displaying an error - “desktop heap exhausted”

24 bpcd 288 bpcompatd 199 bpdbm
TECH145367 | 2011-08-15
Technical Solutions | CMS-XML

Restore data transfer hangs after the tar header is transferred and fails with status 13 and status 5.

on the client host shows the IP addresses and port numbers associated with the DATA socket when it was created. 07:45:51.068 [46661754] 2 ProcessRequests: vnetd.c. 288 : msg: VNETD ACCEPT FROM 2.2.2.2.36320 TO 3.3.3.3.13724 fd = 4
TECH162318 | 2011-06-14
Technical Solutions | CMS-XML

Catalog Backup is failing with status code 25/40

18:50:49.287 [5186] 2 job_monitoring_exex: ACK disconnect 18:50:49. 288 [5186] 2 job_disconnect: Disconnected 18:50:49.288 [5186] 4 db_error_add_to_file: cannot get server s peername on client veritas
TECH148416 | 2011-01-18
Technical Solutions | CMS-XML

For a status 48, how to identify the hostname and host that cannot resolve it.

15:00:33.272 [5424.4232] 2 bpcr_vnetd_connect_forward_socket_end: vnet_vnetd_connect_forward_socket_end() failed: 10 15:00:33.272 [5424.4232] 2 vnet_vnetd_disconnect: ../../libvlibs/vnet_vnetd.c. 288 : 0: vn_request_disconnect: 1 0x00000001 15:00:33.272 [5424.4232] 2 vnet_sock_ready: ../../libvlibs/vnet.c.434: 0: Function failed: 2 0x00000002
TECH142526 | 2010-10-22
Technical Solutions | CMS-XML

Attempts to configure client host properties from the master server fail with connection errors.

14:06:41.158 [3016.1348] 2 vnet_version_accept: .\vnetd.c.1121: Function failed: 43 0x0000002b 14:06:41.158 [3016.1348] 2 ProcessRequests: .\vnetd.c. 288 : version_accept failed: 43 0x0000002b 14:06:41.158 [3016.1348] 2 ListenForConnection: .\vnetd.c.605: Function failed: 43 0x0000002b
TECH56944 | 2010-01-11
Technical Solutions | CMS-XML

BUG REPORT: Multiple Key Management Service (KMS) enabled restores initiated at the same time fail with status 1.

17:43:07 ( 288 .xxx) Restore job id 288 will require 4 images.
TECH126549 | 2010-01-10
Technical Solutions | CMS-XML

RMAN Backup completed without generating child stream or sometime failing with error code 6 | Symantec Connect

13:35:48.142 [10504] <2> int_getmminfo: INF - support for Proxy Copy enabled 13:35:53. 288 [10504] <4> sbtend: INF - --- END of SESSION --- 18:01:09.025 [23359] <8> xbsa_getenv: WRN - nbbsa_schedule not found in environment block
Connect Forums | HTML

The status code 58 Can’t connect to client | Symantec Connect

The status code 58 Can’t connect to client 01:27:59.686 [2796.5276] <2> ProcessRequests: .\vnetd.c. 288 : msg: VNETD ACCEPT FROM 130.1.5.23.64316 TO 10.112.136.91.13724 fd = 616
Connect Forums | HTML

Getting error “FILE WRITE READ” CODE 59 | Symantec Connect

Getting error “FILE WRITE READ” CODE 59 64 bytes from s00asr07.xxx.xx.xxx (127.x.x.xxx): icmp_seq=6 ttl=128 time=0. 288 ms
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?