NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 121

Media Manager status code 121
HOWTO90987 | 2013-10-02
How To | CMS-XML

NetBackup status code: 121

NetBackup status code : 121
HOWTO90542 | 2013-10-02
How To | CMS-XML

Media Manager status code 121

Media Manager status code 121
HOWTO51336 | 2012-11-19
How To | CMS-XML

NetBackup status code: 121

NetBackup status code : 121
HOWTO50890 | 2012-11-19
How To | CMS-XML

NetBackup status code: 121

NetBackup status code : 121
HOWTO35000 | 2010-10-29
How To | CMS-XML

Media Manager status code: 121

Media Manager status code : 121
HOWTO35446 | 2010-10-29
How To | CMS-XML

Shadow copy component backup failing with EXIT STATUS 69: invalid filelist specification

Issue occurs when shadow copy components backup is performed and it fails in snapshot creation with ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - Estimate:- 1 -1
TECH224229 | 2014-08-29
Technical Solutions | CMS-XML

Windows BMR client fails with status code 1, "Failed sending the discovery".

v-121-35 BMR information discovery failed. Status 1 Windows client oid= 121 bmrsavecfg log:
TECH192858 | 2014-01-16
Technical Solutions | CMS-XML

If the total length of client name and backup policy name exceeds a certain limit on Windows master servers, backups may fail with error status code 12

The total length of the default Install path (C:\Program Files\Veritas), ctime , _ suffix , fixed path name and the terminating null character is 121 characters. This leaves 139 characters as the maximum total of client name and policy name . Note that if the client name is a VMware display name containing spaces then every space is expanded to %20 and therefore is counted as three characters.
TECH214234 | 2014-01-23
Technical Solutions | CMS-XML

Backup completes with status 1 - BMR not collecting disk configuration

Increased bmrsavecfg unified logging: install_path \netbackup\bin\vxlogcfg -p nb -o 121 -a -s DebugLevel=1 -s DiagnosticLevel=6 then ran the bmrsavecfg command:
TECH162813 | 2014-01-24
Technical Solutions | CMS-XML

GENERAL ERROR: When the backup of a Linux client is initiated, the Bare Metal Restore (BMR) job (bmrsavecfg) fails with "Operation Status: 1" reported. Error v-128-18 can also be found in unified logs.

Obtain the bmrsavecfg (originator id 121 ) log from the client with debug level 5 and diagnostic level 6. Similarly, generate the bmrd (OID 119) log from the master.
TECH60242 | 2014-01-17
Technical Solutions | CMS-XML

BMR Windows client fails at backup time, "Errors were encountered while discovering disk configuration".

Client bmrsavecfg logs (OID 121 ):
TECH181653 | 2014-01-07
Technical Solutions | CMS-XML

Restore sql 2008 failure with status code 2809 on windows 2008 R2 client.

17:00:01. 121 [3488.2912] 16 CDBbackrec::FreeDeviceSet(): ERR - Error in VDS- Close: 0x80770004.
TECH211057 | 2014-01-09
Technical Solutions | CMS-XML

Exchange 2007 backup fails with status 40 "network connection broken"

2:37:35.526 PM: [5372.7288 ] 2 tar_base::v_vtarmsgw: INF - Estimate:- 1 -1 2:37:35.526 PM: [5372.7288] 2 tar_backup_tfi::backup_startfile_state: TAR - Backup: Microsoft Information Store:
TECH75088 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR: Vault does not eject any tapes and the error "Rejected - No frag in robotGroup" is seen in the vault detail log for the session ID.

IMAGE hostname 0 0 7 hostname_1135991212 policy 13 ... HISTO - 1 -1 - 1 -1 - 1 -1 - 1 -1 - 1 -1 FRAG 1 1 14327919 0 2 15 1 c01243
TECH35510 | 2013-10-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?