NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 324

NetBackup status code : 324
HOWTO104236 | 2014-11-20
How To | CMS-XML

NetBackup status code: 324

NetBackup status code : 324
HOWTO90733 | 2013-10-02
How To | CMS-XML

NetBackup status code: 324

NetBackup status code : 324
HOWTO51081 | 2012-11-19
How To | CMS-XML

NetBackup status code: 324

NetBackup status code : 324
HOWTO35192 | 2010-10-29
How To | CMS-XML

Windows 2008r2 server server failing with status 24

------------------------------------------------- OS Error: 10054 (An existing connection was forcibly closed by the remote host. 5:13:24.971 PM: [ 324 .10196] 2 tar_base::v_vtarmsgw: INF - EXIT STATUS 24: socket write failed
TECH216943 | 2014-04-26
Technical Solutions | CMS-XML

NDMP restores fail with media error EXIT STATUS 85

11:36:10. 324 [4712.6328] 16 read_data: cannot read image from disk, Invalid argument
TECH214057 | 2014-02-24
Technical Solutions | CMS-XML

GENERAL ERROR: If static Network Address Translation (NAT) is configured on the firewall binding the firewall's external IP with the NetBackup master/media server ports, then the DMZ client must be able to perform reverse name lookups of the firewall's public IP address to the name of the NetBackup master/media server.

22:42:36.171 [1640.2132] 2 vnet_pop_signed: vnet.c.234: Function failed: 9 0x00000009 22:42:36.171 [1640.2132] 2 vnet_pop_status: vnet.c. 324 : Function failed: 9 0x00000009 22:42:36.171 [1640.2132] 2 vnet_begin_connect_back: vnet_vnetd.c.501: status: 9 0x00000009
TECH39431 | 2013-10-29
Technical Solutions | CMS-XML

After upgrade to NetBackup 7.5.0.5, the Hot Catalog backup fails with status code 50 and 25

20:37:06.169 [30680] 2 local_bpcr_connect: bpcr.c.278: connect_opts = 0x01020001 connect_opts2 = 0x01020001 20:37:06.169 [30680] 2 local_bpcr_connect: bpcr.c.285: connect_opts = 0x01020001 20:37:06.169 [30680] 2 local_bpcr_connect: bpcr.c. 324 : daemon_port_type = 2
TECH207452 | 2013-06-21
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:42. 324 [7997] 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 -c
TECH175134 | 2012-12-17
Technical Solutions | CMS-XML

NetBackup Catalog Recovery fails with a status 2850.

10:14:40.781 [3484.4480] 4 sendRequest: end_date = 06/20/2012 12:59:49 10:14:40.781 [3484.4480] 4 sendRequest: waiting for restore complete status 10:14:40.781 [3484.4480] 4 sendRequest: calling get_bprdeswto(): sockfd= 324 , timeout= 0
TECH191623 | 2012-06-25
Technical Solutions | CMS-XML

MPX DB extension backups fail intermittently with status 54.

07:21:12.323 [18037] 2 child_wait: waitpid returned zero, no children waiting (tmcommon.c:5552) 07:21:13. 324 [18037] 2 child_wait: waitpid returned zero, no children waiting (tmcommon.c:5552) 07:21:14
TECH138071 | 2011-02-22
Technical Solutions | CMS-XML

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

14:59:39.561 [6056.5828] 2 init_connect_recs: ../../libvlibs/vnet_connect.c.484: 0: vnet_cached_getaddrinfo() host: GUIclient 14:59:39.561 [6056.5828] 2 connect_to_service: ../../libvlibs/vnet_connect.c. 324 : 0: init_connect_recs() failed: 6 0x00000006
TECH142526 | 2010-10-22
Technical Solutions | CMS-XML

GENERAL ERROR: bpdbm core dumps every 12 hours due to SIGBUS in free_image_info_list() during cleanup delete_expired_backups()

... 06:45:43. 324 [16749] 2 gen_image_list_file: directory /usr/openv/netbackup/db/images/some_client file image_list lockfile fd 19 06:45:47.983 [16749] 2 db_get_image_info: Job in progress, found image file .../images/some_client/1192000000/tmp/some_client_1192388405_incr
TECH55672 | 2008-01-27
Technical Solutions | CMS-XML

Dreaded Status 25 and 58 | Symantec Connect

Dreaded Status 25 and 58 <2> vnet_pop_string: vnet.c.274: Function failed: 43 0x0000002b <2> vnet_pop_signed: vnet.c. 324 : Function failed: 43 0x0000002b <2> version_connect: vnet_vnetd.c.1803: Function failed: 43 0x0000002b
Connect Forums | HTML

Backup failing with status 59 | Symantec Connect

Backup failing with status 59 16:28:08. 324 [25373] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1776: 0: via PBX: VNETD CONNECT FROM 10.207.80.10.51143 TO 10.203.2.44.1556 fd = 5
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?