NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 63

Media Manager status code 63
HOWTO104444 | 2014-11-20
How To | CMS-XML

Device management status code 63

Device management status code 63
HOWTO104686 | 2014-11-20
How To | CMS-XML

Device configuration status code 63

Device configuration status code 63
HOWTO104599 | 2014-11-20
How To | CMS-XML

NetBackup status code: 63

NetBackup status code : 63
HOWTO103991 | 2014-11-20
How To | CMS-XML

STATUS CODE 63: Vault job fails with status 63 (process killed by a signal)

STATUS CODE 63 : Vault job fails with status 63 (process killed by a signal)
TECH87105 | 2013-10-24
Technical Solutions | CMS-XML

All backups are failing with status 63 (process was killed by a signal)

All backups are failing with status 63 (process was killed by a signal)
TECH65012 | 2012-01-06
Technical Solutions | CMS-XML

Status 63: process was killed by a signal(63)

Activity Monitor job details shows message: process was killed by a signal( 63 ) Windows client bpbkar log shows:
TECH142904 | 2010-10-28
Technical Solutions | CMS-XML

DOCUMENTATION: Multiple communication errors are reported causing a high percentage of backup failing with errors: 811, 26, 25, 63, and 193

status code 25 status code 63 status code 193
TECH67270 | 2010-01-28
Technical Solutions | CMS-XML

Status 63 Several Windows client Shadow Copy backups failing to one media server.

Status 63 Several Windows client Shadow Copy backups failing to one media server.
TECH128068 | 2010-01-27
Technical Solutions | CMS-XML

Shadow Copy backup fails with error 63: process was killed by signal.

Shadow Copy backup fails with error 63 : process was killed by signal.
TECH124595 | 2010-01-12
Technical Solutions | CMS-XML

STATUS CODE 63: A hp-ux 11.23 client fails with status 63 (process was killed by a signal) reported when backing up more than 20gb, on a "Standard" backup, when the data is written to an online JFS (journaled file system).

STATUS CODE 63 : A hp-ux 11.23 client fails with status 63 (process was killed by a signal) reported when backing up more than 20gb, on a "Standard" backup, when the data is written to an online JFS (journaled file system).
TECH59146 | 2009-01-04
Technical Solutions | CMS-XML

STATUS CODE: 11 Advanced Client snapshot backups fail with Status 11 due to a Veritas File System (tm) issue with a volume name larger than 63 characters.

When using Veritas NetBackup (tm) to back up a client that is running Veritas File System (VxFS) 4.1, a volume name must not exceed 63 characters. If a volume name exists that is greater than 63 characters, the volume name will be truncated. Since the full volume name is not handled properly, any Advanced Client snapshot backups of the volume will fail with Status 11 and dump core.
TECH44458 | 2008-01-31
Technical Solutions | CMS-XML

STATUS CODE: 63 and 13 are encountered when running a Veritas NetBackup (tm) FlashBackup on a client with a loopback file system (lofs) mounted.

A FlashBackup of a client can fail with a Status 63 . This will occur when backing up a volume that has a loopback file system associated with it. The bpfis
TECH42872 | 2006-01-09
Technical Solutions | CMS-XML

How to enable debug logging on a NetApp NDMP device when NDMP backup fails with Status Code 99 - DUMP: could not create "backup" snapshot : No space left on device.

6. After manually mounting the media on the desired drive run the following command from the NetApp Filer to initiate a data dump directly to tape: dump 0ufb nrst1a 63 /vol/vol1 7. The following error message can be observed on the NetApp Filer:
TECH68849 | 2014-01-20
Technical Solutions | CMS-XML

DOCUMENTATION: How to troubleshoot and correct problems with media servers when the status changes in the Media Servers area of the NetBackup Administration GUI.

00 00 01 cc 00 01 02 00 00 00 00 10 73 63 74 63 ...I........mast ----- packet information with name 6c 62 6b 30 32 2e 6c 6f 63 61 6c 00 06 14 3a e8 node2.local...:¿ ----- packet information with name continued
TECH69625 | 2009-01-15
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?