NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code 39

NetBackup status code 39
HOWTO92250 | 2013-10-03
How To | CMS-XML

hyper-v backup fails with, "exited with status 39: client name mismatch"

hyper-v backup fails with, "exited with status 39 : client name mismatch"
TECH130605 | 2014-12-29
Technical Solutions | CMS-XML

Media Manager status code 39

Media Manager status code 39
HOWTO104420 | 2014-11-20
How To | CMS-XML

Device management status code 39

Device management status code 39
HOWTO104667 | 2014-11-20
How To | CMS-XML

Device configuration status code 39

Device configuration status code 39
HOWTO104581 | 2014-11-20
How To | CMS-XML

NetBackup status code: 39

NetBackup status code : 39
HOWTO103969 | 2014-11-20
How To | CMS-XML

Netbackup Console Media or Device mangement gives "error connecting to OPRD on :network protocol error (39)"

When expanding device or media sections of the Netbackup Console, error 39 is observed. Devices are inoperable and Media Server with configured tape drive is in state Active for disk only. The LTID process appears to be hung
TECH138493 | 2012-08-18
Technical Solutions | CMS-XML

hyper-v Backups using the cluster name for the hyper-v host fails with Status 39 "client name mismatch"

16:36:50.451 [12535] 2 ConnectToBPCD: bpcd_connect_and_verify(vmclient01, hyperv-cluster.symantec.com) failed: 39
TECH162842 | 2011-12-19
Technical Solutions | CMS-XML

network protocol error(39) and oprd returned abnormal status(96)

Network protocol error ( 39 ) or oprd returned abnormal status
TECH143943 | 2010-11-11
Technical Solutions | CMS-XML

GENERAL ERROR: When accessing Media or Devices in the NetBackup Administration Console, the message "network protocol error (39)" is returned.

GENERAL ERROR : When accessing Media or Devices in the NetBackup Administration Console, the message "network protocol error ( 39 )" is returned.
TECH50318 | 2008-01-13
Technical Solutions | CMS-XML

MSDP media write error (84)

optimized duplication failed, media write error (84). 2/12/2013 2:33: 39 AM - Info msdp.symantecs.org(pid=25204) StorageServer=PureDisk:msdp.symantecs.org;
HOWTO89078 | 2013-10-01
How To | CMS-XML

Active Directory GRT restore failing with status code 2808 and 5

10/8/2013 19: 39 :58.920 [[fsys\adgran] ] FROM BEDS ADGran : Restoring object DC=com,DC=testdomain/DC=com/OU=hq_users/CN=nbu_user, property whenCreated in adgran_writeobj:269 (../BEDSContext.cpp:124)
TECH211394 | 2015-01-21
Technical Solutions | CMS-XML

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

07/11/2013 11:25:30 - requesting resource @aaaaV 07/11/2013 11:25: 39 - granted resource G42488 07/11/2013 11:25:39 - granted resource HP.ultrium4-scsi.010.8
TECH208798 | 2014-12-30
Technical Solutions | CMS-XML

Backup jobs fail with error: Failed to get status code information (2505)

Error bpbrm(pid=1480) db_flistsend failed: Unable to connect to the database (2505) 12/05/2013 15: 39 :45 - job 63389 was restarted as job 63390 Failed to get status code information (2505)
TECH213131 | 2014-12-18
Technical Solutions | CMS-XML

VMWare Application State Capture backup fails with the following error: host is unreachable

6/26/2014 17:02: 39 .429 [Application] NB 51216 ncfnbcs 366 PID:7068 TID:6752 File ID:366 [No context] [Error] v-366-2 Socket I/O error to exchvm01.test.lab, error mangleConnect: error:00000005
TECH194457 | 2014-12-03
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?