NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 22

Media Manager status code 22
HOWTO104409 | 2014-11-20
How To | CMS-XML

Device management status code 22

Message: IPC Error : Daemon may not be running Explanation:
HOWTO104653 | 2014-11-20
How To | CMS-XML

NetBackup status code: 22

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 could have returned this status code . Then, retry the operation and check the resulting debug logs.
HOWTO103952 | 2014-11-20
How To | CMS-XML

Device configuration status code 22

Windows hosts have multiple ways to configure robots (changer names or port, bus, target, LUN). Check the operating system configuration or registry for changer names and their associated SCSI paths. Check for detailed errors from the command or the user interface output.
HOWTO104567 | 2014-11-20
How To | CMS-XML

Symantec Private Branch Exchange fail to start with "The Symantec Private Branch Exchange service terminated with service-specific error 22 (0x16)" due to missing or incorrect localhost entry

Symantec Private Branch Exchange fail to start with The Symantec Private Branch Exchange service terminated with service-specific error 22 (0x16) due to missing or incorrect localhost entry in the host file
TECH183113 | 2012-05-06
Technical Solutions | CMS-XML

PBX fails to start with the following error: "service-specific error code 22"

03-10-2011,15:00:46 : Internal Error 2769. immediate_createsupportfilesserver, 22
TECH155341 | 2011-03-10
Technical Solutions | CMS-XML

Status 89, Job status is showing error: Could not attached shared memory. Errno = 22: Invalid argument

Status 89, Job status is showing error : Could not attached shared memory. Errno = 22: Invalid argument
TECH66886 | 2009-01-11
Technical Solutions | CMS-XML

Veritas Storage Migrator (VSM) BUG REPORT: migcons fails with ERROR: migtrans failure 22 when running 6.5.2

Bug ID: et1460990: migcons command exits with status code due to changes made in the 6.5.2 patch. Exact Error Message
TECH87162 | 2009-01-05
Technical Solutions | CMS-XML

Status 40 when backing up a hp-ux 11.22 client

Exclude the /dev directory when backing up hp-ux 11. 22 clients as it is not required. For further instructions on how to create exclude lists please refer to the Veritas NetBackup (TM) 6.5 Administrator s Guide, Volume 1 for Unix and Linux, page 195 (refer to link in Supplemental Material section below).
TECH71070 | 2010-01-02
Technical Solutions | CMS-XML

error 22 system call received a parameter that is not valid | Symantec Connect

error 22 system call received a parameter that is not valid
Connect Forums | HTML

MSDP media write error (84)

Look at the replication logs on the source storage server for more information. v-454-105 2/12/2013 2:33: 22 AM - Critical bpdm(pid=25204) sts_copy_extent failed: error 2060014 operation aborted 2/12/2013 2:33: 22 AM - end writing; write time: 3:39:53 2/12/2013 2:33:39 AM - Error bpduplicate(pid=5300) host msdp.symantecs.org backup id msdp.symantecs.org_1360303271
HOWTO89078 | 2013-10-01
How To | CMS-XML

BUG REPORT: Duplication jobs fail with status code 50 (Client process aborted) reported

07:00:38.094 [7504.732] 2 bpduplicate: Received read status: 0, 0, 1, 0 07:01: 22 .790 [7504.732] 2 dupreadline: read: WROTE server1_1199761207 30208 0 148807,882 1 07:01:22.790 [7504.732] 2 process_progress_msgs: try message: KBW 1199775682 30208 148807,000
TECH56753 | 2010-09-07
Technical Solutions | CMS-XML

DOCUMENATION: An breakdown of TapeAlert flags to assist with troubleshooting TapeAlert errors

0000 0000 0000 0000 0000 0000 0000 0000 0 0 0 0 0 0 0 0 (0x00000000) Taking the converted number ( 22 since there is a digit in the 22nd field) and referencing page 8 we find 22 converts to Expired Cleaning Media - The cleaning tape has expired.
TECH48603 | 2010-01-29
Technical Solutions | CMS-XML

NDMP backup fails with status 99 when port 10000 is also open

08/28/14 00:55:35.475 Using hostname from config file: ndmp_data_connection_host_name=10. 22 .35.98
TECH215719 | 2015-02-19
Technical Solutions | CMS-XML

Backups failing with status 83; - Client Direct plugin not available (2060009)

- Do so from the Netbackup Activity Monitor or the job details; e.g. 11/19/2010 9:37: 22 AM - granted resource netbackupmaster.nbu_client.MAXJOBS.netbackupclient 2. In the NetBackup Admin Console, navigate to Host Properties
TECH144779 | 2015-02-18
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?