NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 92

Media Manager status code 92
HOWTO104470 | 2014-11-20
How To | CMS-XML

Device configuration status code 92

Device configuration status code 92
HOWTO104627 | 2014-11-20
How To | CMS-XML

NetBackup status code: 92

NetBackup status code : 92
HOWTO104019 | 2014-11-20
How To | CMS-XML

GENERAL ERROR: On a new installation of NetBackup 6.5, the NetBackup daemons will not start an "EMM interface initialization failed" status 92 message is given.

GENERAL ERROR : On a new installation of NetBackup 6.5, the NetBackup daemons will not start an "EMM interface initialization failed" status 92 message is given.
TECH57351 | 2010-01-22
Technical Solutions | CMS-XML

Unable to use "nbemmcmd" command to decommission a media server that failed with error message: "cannot delete assigned volume (92)".

ISSUE: Unable to use nbemmcmd command: cannot delete assigned volume ( 92 ) . ERROR CODE/ MESSAGE:
TECH67038 | 2010-01-14
Technical Solutions | CMS-XML

NetBackup status code 92: media manager detected image that was not in tar format

92
TECH58021 | 2009-01-12
Technical Solutions | CMS-XML

STATUS CODE 92 and 183: An error will occur when restoring or verifying data backed up on Windows clients using the Veritas NetBackup (tm) Encryption Option.

A restore of the image will fail with a Status 92 (media manager detected image that was not in tar format). The following messages will appear in the install_path \VERITAS\NetBackup\logs\bpbrm\ date .LOG
TECH44803 | 2007-01-14
Technical Solutions | CMS-XML

Restoring images at the subdirectory level fails. Restore fails with status 5; bpbrm 186 (tar received no data) and 92 (not in tar format); tar exit 6 "no data in archive"

Restoring images at the subdirectory level fails. Restore fails with status 5; bpbrm 186 (tar received no data) and 92 (not in tar format); tar exit 6 "no data in archive"
TECH33323 | 2005-01-28
Technical Solutions | CMS-XML

VMWare Application State Capture backup fails with the following error: host is unreachable

12:13:26.193 [5948.3840] 8 process_service_socket: [.\vnetd.c:1539] service_name nbcs 12:13:26.193 [5948.3840] 2 vtext_failure: ../../libvlibs/vtext.c. 92 : Function vtext_open failed: 7 12:13:26.193 [5948.3840] 2 vnet_read_service: vnet_text.c.554: 0: Function failed: 19 0x00000013
TECH194457 | 2014-12-03
Technical Solutions | CMS-XML

DOCUMENTATION: The NetBackup DB2 Administrator's Guide contains an error in the "Preparing the master server for an alternate restore" section of the document.

Veritas NetBackup™ 6.0 for DB2 on UNIX System Administrator s Guide (page 92 ) Veritas NetBackup™
TECH51846 | 2013-10-24
Technical Solutions | CMS-XML

BUG REPORT: Vault eject fails with error 224 (Control daemon connect or protocol error) due to tapes being in_transit.

08:08:09.667 [21243] 2 vltrun@SingleMapMediaList::setEjectElemStat()^107: setting the eject status of a70176 to 1 08:08:09.667 [21243] 2 vltrun@VaultApiRobot::gatherRobotInfo()^107: Adding: BC=a70179, vendMedTyp=30, MmStat=0, location=0,2,1,12 STATUS =status_volume_in_transit ( 92 ) The eject then failed with status 224:
TECH125927 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR: ltid hangs on media server. Many oprd processes found running on media server.

19:55:04.250 [15163] 4 QueueMsg: Data.Pid=4255, Type=101, param1=-65, param2=-3504, LongParam=1 19:55:09.210 [15163] 4 QueueMsg: Data.Pid=15185, Type= 92 , param1=13, param2=30, LongParam=15163
TECH56642 | 2013-08-29
Technical Solutions | CMS-XML

Catalog backups fail with status 2 - none of the requested files were backed up

Creating indexes for ( 92 /93) dars_main . dars_query_controlfile_backups
TECH191598 | 2012-06-25
Technical Solutions | CMS-XML

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

The current time is: 14:17:59.07 The current time is: 14:17:59. 92 TCP
TECH156471 | 2011-03-24
Technical Solutions | CMS-XML

BUG REPORT: The Oracle backup process may fault if certain other errors occur during the data transfer

bsa_put()+ 92 call dbc_put() 003fc50c0 ? 000040000 ?
TECH77618 | 2010-12-01
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?