NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

BMR backup is failing with status 26

BMR backup is failing with status 26
TECH185690 | 2014-01-08
Technical Solutions | CMS-XML

Exchange 2010 DAG backup fails with a status code 26

**The Backup, Archive and Restore needs to have the node names in the host property clients.** Minimum of Netbackup 7.0.1. to resolve all known issues with status 26 . Please reference the Netbackup 7.x Database compatibility guide (http://www.symantec.com/docs/tech126904
TECH181426 | 2013-10-24
Technical Solutions | CMS-XML

Device management status code 26

Device management status code 26
HOWTO91154 | 2013-10-02
How To | CMS-XML

Media Manager status code 26

Media Manager status code 26
HOWTO90909 | 2013-10-02
How To | CMS-XML

NetBackup status code: 26

A process on the server encountered an error when it communicated with the client. This error indicates that the client and server were able to initiate communications, but encountered difficulties and the communications did not complete. This problem can occur during a backup or a restore.
HOWTO90455 | 2013-10-02
How To | CMS-XML

BMR enabled backup job is partially successful (status code 1) after upgrade to Netbackup 7.5.0.4, Parent job fails reporting status code 26

BMR enabled backup job is partially successful (1) after upgrading to Netbackup 7.5.0.4, Parent job details shows Status 26
TECH200322 | 2013-07-01
Technical Solutions | CMS-XML

STATUS CODE 26 and 46: When using Veritas NetBackup (tm) for Vault, a catalog backup fails with status 26 (client / server handshaking failed) when backing up a Media Server and the exit status 46 (server not allowed access) is found in the admin log.

STATUS CODE 26 and 46: When using Veritas NetBackup (tm) for Vault, a catalog backup fails with status 26 (client / server handshaking failed) when backing up a Media Server and the exit status 46 (server not allowed access) is found in the admin log.
TECH38931 | 2013-04-25
Technical Solutions | CMS-XML

Media Manager status code 26

Media Manager status code 26
HOWTO51258 | 2012-11-19
How To | CMS-XML

NetBackup status code: 26

A process on the server encountered an error when it communicated with the client. This error indicates that the client and server were able to initiate communications, but encountered difficulties and the communications did not complete. This problem can occur during a backup or a restore.
HOWTO50803 | 2012-11-19
How To | CMS-XML

Device management status code 26

Device management status code 26
HOWTO51504 | 2012-11-19
How To | CMS-XML

Backup jobs failing with error 26

Backup jobs failing with error 26
TECH192186 | 2012-09-24
Technical Solutions | CMS-XML

ERROR CODE: error 26 bpbrm jobs failing with status 26.

ERROR CODE: error 26 bpbrm jobs failing with status 26 .
TECH70191 | 2012-01-06
Technical Solutions | CMS-XML

Oracle RMAN backups with Oracle metadata collection fail with status 26 and status 1.

But then there was a problem gathering and cataloging the Oracle metadata for the backup. Exit status 1 is returned to the media and master servers for this job. 15:43:20.213 [5258] 2 logparams: -sb -rdbms oracle ... -b myclient_1316529799 -jobid 178517
TECH170966 | 2012-01-04
Technical Solutions | CMS-XML

Backups failing with a Status 26 and relation to Open File Descriptors.

Backups failing with a Status 26 and relation to Open File Descriptors.
TECH176664 | 2011-12-11
Technical Solutions | CMS-XML

GENERAL ERROR: Vault policy fails with exit status 26: client/server handshaking failed

Symptoms: When a vault POLICY is run by a scheduled job or manually, the vault job fails with a status 26 (client/server handshaking failed). The vault PROFILE can be run manually using Start Session and completes vault processing normally.
TECH62837 | 2011-08-15
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?