NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 75

Media Manager status code 75
HOWTO104455 | 2014-11-20
How To | CMS-XML

Device management status code 75

Device management status code 75
HOWTO104696 | 2014-11-20
How To | CMS-XML

Device configuration status code 75

Device configuration status code 75
HOWTO104611 | 2014-11-20
How To | CMS-XML

NetBackup status code: 75

NetBackup status code : 75
HOWTO104003 | 2014-11-20
How To | CMS-XML

NetBackup restore and backup status codes

Status Code 75 . Client timed out waiting for bpend_notify
HOWTO89629 | 2013-10-02
How To | CMS-XML

Backups or restores fail with SQL GetConfiguration errors: 0x80770003 and 0x80770004.

If the test succeeds, click on OK and follow the procedures on pages 72 through to 75 in the VERITAS NetBackup for Microsoft SQL Server on Windows NT/2000 System Administrator s Guide. Once the above has been completed please make sure you start the NetBackup Client Services as a non-system user, The user selected to start the services should also be the user that is logged on when the DSN is created.
TECH11378 | 2015-02-02
Technical Solutions | CMS-XML

How to configure email notification and the different methods to email backup exit statuses from a UNIX master in NetBackup

daemon does check to see if the script exits successfully. A backup job can exit with a status 75 if the bpend_notify
TECH32539 | 2014-07-08
Technical Solutions | CMS-XML

VMware Intelligent Policy Test Query operation is failing with "error parsing discovered XML data(1)"

0,51216,132,132,6593,1395775593654,53436,139780432148224,0:, 75 :Could not able to parse XML data recieved.(NCFManagementFacetsImpl.cpp:793),43:DiscoveryFacetImpl::ProcessDiscoveredData(),1 Review the XML statement prior to the error and found: prm_snapshot_resource Group= vmfs:ds:///vmfs/volumes/52bc487d-80a7e3f7-7ca6-0017a4770400 idx= 4 vmfs:ds:///vmfs/volumes/58n#!2bc487d-80a7e3f7-7ca6-0017a4770400 /prm_snapshot_resource
TECH216148 | 2014-04-14
Technical Solutions | CMS-XML

Job fails with status 232 after going active on RHEL media server using NIS/YP

03:30:31.891 [Debug] 51216 137 PID:25000 TID:3 File ID:117 [No context] 3 [parseData] not enough data to parse: dataAvail = (37)64 6f 5f 79 70 63 61 6c 6c 3a 20 63 6c 6e 74 5f 63 61 6c 6c 3a 20 52 50 43 3a 20 54 69 6d 65 64 20 6f 75 74 a ...snip...
TECH145022 | 2014-03-24
Technical Solutions | CMS-XML

Netbackup Administration Console crashes with Application error 1000 and 1004

0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 4e 42 43 ure NBC 0018: 6f 6e 73 6f 6c 65 2e 45 onsole.E
TECH144245 | 2013-11-15
Technical Solutions | CMS-XML

Exchange 2007 backup fails with status 40 "network connection broken"

2:39:29.468 PM: [5372.7288] 16 dtcp_write: TCP - failure: attempted to send 75 bytes
TECH75088 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR: NetBackup exits with Status 0 but RMAN exits with ora-27192

21:03:00.702 [985] 2 bptm: dssu_name: free space = 258822676480, total space = 1181144190976 utilization = 78 % 21:03:00.702 [985] 2 request_image_drain: Requesting drain of DSSU dssu_name- total_space=1181144190976 free_space=258822676480 total-free=922321514496 calc hwm=885858143175 hwm= 75 lwm=5 utilization=78 % ...
TECH62019 | 2013-10-23
Technical Solutions | CMS-XML

Exchange 2010 GRT restore fails with status 5: Faulting application bpresolver.exe

08:58:00.796 [23136.30776] 2 vnet_cached_getaddrinfo: ../../libvlibs/vnet_addrinfo.c.1260: 0: found in file cache service: NULL 08:58:00.796 [23136.30776] 2 vnet_cached_getaddrinfo: ../../libvlibs/vnet_addrinfo.c.1259: 0: found in file cache name: 10.40.168. 75
TECH160404 | 2013-10-24
Technical Solutions | CMS-XML

NetBackup STATUS 23, NDMP backups fail after the data has been transferred to the tape storage

port 3571 ...( 75 second delay)... 05:26:57.930 [1420] 2 NdmpMoverSession[0]: ndmp_mover_connect failed, status = ndmp_connect_err
TECH202406 | 2013-10-16
Technical Solutions | CMS-XML

Device Monitor or vmoprcmd output shows that the drive is in PEND status.

If this conflict occurs, some sort of mis-configuration is present (for example, the tape drive is reserved, but should not be) and the configuration problem should be corrected. A possible cause of this conflict is if an operating system crashes or a hardware failure has left a device reserved (see Issuing the Release on page 75 of the NetBackup 4.5 Shared Storage Option System Administrator s Guide for UNIX and Windows ).
TECH23205 | 2013-10-23
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?