NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Device configuration status code 51

Device configuration status code 51
HOWTO91085 | 2013-10-02
How To | CMS-XML

Media Manager status code 51

Media Manager status code 51
HOWTO90929 | 2013-10-02
How To | CMS-XML

NetBackup status code: 51

NetBackup status code : 51
HOWTO90480 | 2013-10-02
How To | CMS-XML

Media Manager status code 51

Media Manager status code 51
HOWTO51278 | 2012-11-19
How To | CMS-XML

NetBackup status code: 51

NetBackup status code : 51
HOWTO50828 | 2012-11-19
How To | CMS-XML

Device configuration status code 51

Device configuration status code 51
HOWTO51434 | 2012-11-19
How To | CMS-XML

NetBackup status code: 51

NetBackup status code : 51
HOWTO34937 | 2010-10-29
How To | CMS-XML

Media Manager status code: 51

Media Manager status code : 51
HOWTO35388 | 2010-10-29
How To | CMS-XML

Device configuration status code: 51

Device configuration status code : 51
HOWTO35544 | 2010-10-29
How To | CMS-XML

NetBackup status code 51: timed out waiting for database information

51
TECH59045 | 2009-01-12
Technical Solutions | CMS-XML

Unable to perform Alternate Path restore from Windows 2003 Master to AIX client - Exit Status 51

51
TECH47503 | 2008-01-11
Technical Solutions | CMS-XML

Netbackup Error 41 and 51. Connection issue? | Symantec Connect

Netbackup Error 41 and 51. Connection issue? All jobs start up fine, status goes from "Mounting tape" to "Writing". Only 40960kb is written before the job exited on Error 51 : Timed out waiting for database information ( seer.entsupport.symantec.com/docs/302068.htm )
Connect Forums | HTML

When selecting the Symantec NetBackup Application in the vCenter, the following error is seen “VI SDK invoke exception:java.net.UnknownHostException:

[http-9445-6] 22 Jul 2014 15: 51 :43 ERROR NBvcplugin : Application threw exception java.rmi.RemoteException: VI SDK invoke exception:java.net.UnknownHostException: vcenterhostnamehere
TECH211596 | 2014-07-23
Technical Solutions | CMS-XML

Instant Recovery of a Virtual Machine failing with a Status 5.

c:\Program Files\Veritas\NetBackup\bin nbrestorevm -vmw -ir_activate -C SQL12 -temp_location storage2 -vmproxy backup02 -vmpo Restore image time = 06/03/14 18:01: 51 VM restore request returned with status = 0
TECH218051 | 2014-06-05
Technical Solutions | CMS-XML

After upgrading to 7.6.0.1/2.6.0.1, VMware backups via SAN may fail with Status 130 due to bpbkar core dump

17-1-2014 21:51:51 - Error bpbrm(pid=61074) from client VMCLIENT: aborting... 17-1-2014 21: 51 :52 - Critical bpbrm(pid=61074) from client VMCLIENT: FTL - terminated by signal 6 17-1-2014 21:51:52 - Critical bpbrm(pid=61074) from client VMCLIENT: FTL - cleanup() failed, status 130
TECH214512 | 2014-05-08
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?