NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 36

Media Manager status code 36
HOWTO104418 | 2014-11-20
How To | CMS-XML

Device management status code 36

Device management status code 36
HOWTO104664 | 2014-11-20
How To | CMS-XML

Device configuration status code 36

Device configuration status code 36
HOWTO104578 | 2014-11-20
How To | CMS-XML

NetBackup status code: 36

NetBackup status code : 36
HOWTO103966 | 2014-11-20
How To | CMS-XML

Status 156 backing up 1 virtual machine "vsphere_freeze: vmcCreateSnapshot failed with 36"

2 onlfi_vfms_logf: INF - vmwareLogger: CreateSnapshot(1): sym_vmc_error: task_reached_error_state 2 onlfi_vfms_logf: INF - vsphere_freeze: vmcCreateSnapshot failed with 36 , retry = 1 2 onlfi_vfms_logf: INF - vsphere_freeze: freeze returned 36
TECH199809 | 2014-09-07
Technical Solutions | CMS-XML

robot inventory failed: unable initialize robot 204 Status 36

robot inventory failed: unable initialize robot 204 Status 36
TECH78043 | 2009-01-30
Technical Solutions | CMS-XML

BUG REPORT: Incremental FlashBackup fails with EXIT STATUS 36: failed trying allocate memory

bpbkar log: 3:57: 36 .349 PM: [2908.7104] 2 tar_backupt_tfi::create: TAR - Incremental backup using file dates since: 3/14/2009 1:42:39 PM 3:57:36.349 PM: [2908.7104] 2 tar_base::v_vtarmsgw: TRV - BACKUP 3/25/2009
TECH72131 | 2009-01-29
Technical Solutions | CMS-XML

Snapshot error encountered (status code 156)

Event Type: Error Event Source: VSS Event Category: None Event ID: 12302 Date: 1/8/2009 Time: 1: 36 :21 AM User: N/A Computer: ARTICTALEVM8 Description: Volume Shadow Copy Service error : An internal inconsistency was detected in trying to contact shadow copy service writers. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.
HOWTO70792 | 2014-12-13
How To | CMS-XML

Backup fails with status 24 after the network stops delivering data to the media server.

log shows a backup in progress and then a delay, after which a broken network socket is reported. 05:14: 36 .502 [23506] 2 bpbkar SelectFile: INF - resolved_path = /export/home/OracleExport 05:14:36.506 [23506] 4 bpbkar PrintFile: /
TECH76201 | 2014-10-16
Technical Solutions | CMS-XML

Storage unit characteristics mismatched to request (status code 154)

11/21/2008 5: 36 :44 PM - requesting resource stu_med 11/21/2008 5: 36 :44 PM - requesting resource lin04- x86.nbu_client.MAXJOBS.hyper_win_5.acme.com 11/21/2008 5:36:44 PM - requesting resource lin04- x86.nbu_policy.MAXJOBS.mapped_vm
HOWTO70804 | 2012-02-08
How To | CMS-XML

Netbackup Issue status code - 36 | Symantec Connect

Netbackup Issue status code - 36 Windows Server. The backup of one of the logical volumes is failing with status code 36 - falied trying to allocate memory.
Connect Forums | HTML

Duplications using Quantum DXi NDMP DirectCopy may intermittently fail with a status 85

12:17: 36 .951 [11544] 2 bptm: INITIATING (VERBOSE = 5): -copy -cmd -nosig -everything -cn 1 -c ab_master -b ab_master_1350946816 -ipc /tmp/vnet-11534351099056104609000000000-o_awhw NULL medsvr1 -jobid 2438931 -priority 0 -v -p @aaaat -mediasvr medsvr1 -ndmp_dc -nh dxi1102b -nu backup -np 886a57176403113f9f102855626b3cf9484319e7fd37847fa45a78bf0fcec978451bc1210db1888fb71e65ace7f00a81a3e8c83f7386e10596f2a084ae6f1103 -nk 2d27576827124c22 -dpath @aaaat
TECH200976 | 2015-02-20
Technical Solutions | CMS-XML

NBCCR fails to run on NetBackup 7.5.x (or higher) systems when bpclntcmd -self exits with status 1

11/07/2012 10:57: 36 : 11/07/2012 10:57:36: 1.0 Determining Veritas Install Path and Veritas Data Path 11/07/2012 10:57:36: NetBackup Install Path /usr/openv
TECH199672 | 2015-02-17
Technical Solutions | CMS-XML

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

...Here, 5.477 delay while Oracle gathers the next buffer. 18: 36 :00.975 [14809] 2 xbsa_senddata: INF - entering
TECH130209 | 2015-02-03
Technical Solutions | CMS-XML

Backups failing with status 83; - Client Direct plugin not available (2060009)

11/19/2010 9:37: 36 AM - Error bpbrm(pid=7436) [ ERROR ][proxy_get_server_prop_byname_v8]STSException is caught in proxy_get_server_prop_byname_v8:.sts errno: 2060009. error message: fail to call sts_get_server_prop_byname
TECH144779 | 2015-02-18
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?