NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 192

NetBackup status code : 192
HOWTO104110 | 2014-11-20
How To | CMS-XML

Media Manager status code 192

Media Manager status code 192
HOWTO104543 | 2014-11-20
How To | CMS-XML

DOCUMENTATION: Explanation of bpclntcmd options and recommended troubleshooting when the commands return errors.

client_01.domain.com client_01 192 .168.0.30 3815
TECH50198 | 2013-10-08
Technical Solutions | CMS-XML

Accelerator job fails with status: 24: socket write failed

Error captured in bpbrm: 14:20:44.319 [8864] 2 logconnections: BPCD CONNECT FROM 192 .168.2.48.35229 TO 192.168.2.48.13782 fd = 11
TECH227138 | 2014-12-16
Technical Solutions | CMS-XML

Event manager service is unable to start: [Error] v-231-106 Attempted to start the Event Manager on a non-master Server

client_name = nbserv01 keep_jobs_hours = 192 VERBOSE = 5
TECH67287 | 2014-08-23
Technical Solutions | CMS-XML

Pre Recovery Checks fail with error "Validation tests did not complete due to system error."

For example, http:// 192 .168.1.1/mob/?moid=datastore-546 doPath=summary
TECH209884 | 2014-04-10
Technical Solutions | CMS-XML

NetBackup hyper-v policy client browse fails with status 25

C:\Users\Administrator bpclntcmd -hn hyperv_node01 host hyperv_node01: hyperv_node01.lab.symc at 192 .168.2.48 aliases: hyperv_node01.lab.symc hyperv_node01 192.168.2.48
TECH215728 | 2014-03-12
Technical Solutions | CMS-XML

NDMP restores fail with media error EXIT STATUS 85

09/20 11:22:53.364 (tid 0x2aaaab112130): ddboost- 192 .168.0.21-64800 : JOB START image_read ip= 192 .168.0.210 pid=1220 cd=0
TECH214057 | 2014-02-24
Technical Solutions | CMS-XML

NetBackup automatic remote master replication fails status 84 when target MSDP media server resolves the source MSDP media server hostname to incorrect ipv6/ipv4 address.

-- Of particular note, the target MSDP media server spad/spoold log directory does not contain a directory with a name consisting of the source MSDP media server hostname, but instead a directory with a odd ipv6/ipv4 address that matches the real source MSDP media server ip address, in this example 192 .168.1.10 is the real ipv4 address of the source MSDP media server:
TECH209579 | 2014-02-18
Technical Solutions | CMS-XML

Adding a DataDomain disk pool fails with error "RDSM has encountered an issue with STS where the server was not found"

net hosts add ipaddr host ex. net hosts add 192 .168.1.1 mydd.mycompany.com From the Data Domain Replicator GUI - Please contact your DataDomain Administrator.
TECH161568 | 2014-01-17
Technical Solutions | CMS-XML

Duplications of Granular (GRT) Backups from disk to tape gives error 191

admin log: 11:25:39.105 [23428] 2 logconnections: BPDBM CONNECT FROM 168. 192 .1.2.52139 TO 168. 192 .1.2.1556 fd = 5 11:25:39.130 [23428] 2 db_end: Need to collect reply
TECH208798 | 2014-01-20
Technical Solutions | CMS-XML

Large Backups using PureDisk Stoarage Unit are failing with status 84

07:59:59. 192 [15889] 2 bptm: INITIATING (VERBOSE = 0): -w -c client_1 -dpath PureDiskVolume -stunit pd-stu_1 -cl client_1_policy -bt 1281700793 -b client_1_1281700793 -st 1 -cj 1 -reqid -1272998356 -jm -brm -hostname client_1 -ru root -rclnt client_1 -rclnthostname client_1 -rl 3 -rp 2678400 -sl daily-differential -ct 19 -maxfrag 524288
TECH137988 | 2013-12-26
Technical Solutions | CMS-XML

The command "bmrsetupboot" fails with: [Error] v-128-899 Cannot determine the netmask for interface <IP address>

/usr/openv/netbackup/bin/bpclntcmd -hn testserv host testserv: testserv at 192 .168.100.10 (0xc0a86401) The above commands show:
TECH58518 | 2013-12-13
Technical Solutions | CMS-XML

While running backups in PureDisk, getting error status 129 and status 83.

16:38:48.734 [5012.4612] 16 udcinf-bu01: PDVFS: [1] pdvfs_lib_log: Synchronization to 192 .168.128.160 failed (spool directory out of space or tlog files in spool directory are too old).
TECH168898 | 2013-12-04
Technical Solutions | CMS-XML

VMware Intelligent Policy are failing with "discovery document error (1001)" due to duplicate VM names

Status 1001 nbpem: Named groups 1 parameters do not match, from 192 .168.99.100 to 192 .168.99.100 (../DiscoveredData.cpp:987),21:DiscoveredItem::merge,1
TECH190103 | 2013-11-12
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?