NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 21

Media Manager status code 21
HOWTO104408 | 2014-11-20
How To | CMS-XML

Device management status code 21

Device management status code 21
HOWTO104652 | 2014-11-20
How To | CMS-XML

Device configuration status code 21

Device configuration status code 21
HOWTO104566 | 2014-11-20
How To | CMS-XML

NetBackup status code: 21

Check the NetBackup Problems report for clues on where and why the failure occurred. If you cannot determine the cause from the Problems report, create debug log directories for the processes that returned this status code . Then, retry the operation and check the resulting debug logs.
HOWTO103951 | 2014-11-20
How To | CMS-XML

Backups of the same client using some media servers fail with status 21: socket open failed

Backups of the same client using some media servers fail with status 21 : socket open failed
TECH129303 | 2013-10-24
Technical Solutions | CMS-XML

user-directed backup of thousands of files fails with status 21 or status 25 before the data transfer begins

The job for the user-directed backup is provided with an input file list that contains over 150,000 files. The backup job goes active and the media mounts and positions, but the backup fails with status 25 more than two minutes later without transferring any portion of the backup image from the client to the mediaserver.
TECH168191 | 2011-08-26
Technical Solutions | CMS-XML

Backup or restore fails with status 5/6/21/25 at either the beginning or end of the job

[8716.644] 2 vnet_send_network_socket: ... hash_str2: 8295774714d6f8ee52a2f9a7c9b1abd0 14:17:23.841 [8716.644] 2 vnet_send_network_socket: ... status : 10 0x0000000a 14:17:23.841 [8716.644] 2 process_connect_forward_socket: ... vnet_send_network_socket failed: 10 0x0000000a
TECH156471 | 2011-03-24
Technical Solutions | CMS-XML

client server failing with status 21 errors

16 bpcd main: get_vnetd_forward_socket failed: 21
TECH146731 | 2011-01-27
Technical Solutions | CMS-XML

Error: Status code 21 when trying to backup a Client. Changing the backup destination to another Media Server sometimes works, and the original Media Server that has problems backing up the Client doesn't have any issues while doing backups for another Clients.

Log Files: The following logs might be seen during this error : From the vnetd
TECH135904 | 2010-08-14
Technical Solutions | CMS-XML

STATUS CODE 21: SQL backups fail with a Status Code 21 (socket open failed) in the dbclient log file when the master server is Veritas NetBackup (tm) 6.x and the SQL client is NetBackup 5.x.

In the dbclient log file, the following error message is observed: 11:18:07.671 [232.397] 16 serverResponse: ERR - server exited with status 21: socket open failed
TECH46463 | 2009-01-02
Technical Solutions | CMS-XML

STATUS CODE 21: Oracle backups through a firewall fail with NetBackup Status Code 21 (socket open failed) when using a NetBackup 5.1 Oracle client and a NetBackup 6.0 master server.

rman-00571: =========================================================== rman-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
TECH49867 | 2008-01-28
Technical Solutions | CMS-XML

BUG REPORT: Backups have intermittent error code 21

0,51216,116,116,11,1201500606380,27129,8,13:jobid=4339360,61: stream # = 0 runonce = 1 time = Mon Jan 28 00:10:06 2008 ,1:?,1 0,51216,116,116,12,1201500606387,27129,8,13:jobid=4339360,34: status 21 (socket open failed),1:?,1 SOLUTION/WORKAROUND:
TECH58297 | 2008-01-07
Technical Solutions | CMS-XML

STATUS CODE 21: After upgrading to Veritas NetBackup (tm) 6.0, backup jobs end in a Status 21 (socket open failed).

STATUS CODE 21 : After upgrading to Veritas NetBackup (tm) 6.0, backup jobs end in a Status 21 (socket open failed).
TECH46238 | 2006-01-29
Technical Solutions | CMS-XML

Constant errors 21, 23, and 25 | Symantec Connect

Constant errors 21 , 23, and 25
Connect Forums | HTML

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
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?