NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 72

Media Manager status code 72
HOWTO104452 | 2014-11-20
How To | CMS-XML

Device management status code 72

Device management status code 72
HOWTO104693 | 2014-11-20
How To | CMS-XML

Device configuration status code 72

Device configuration status code 72
HOWTO104608 | 2014-11-20
How To | CMS-XML

NetBackup status code: 72

NetBackup status code : 72
HOWTO104000 | 2014-11-20
How To | CMS-XML

NetBackup backup of an Enterprise Vault database fails with status 130 or 72 when the SQL server is configured to use an alias.

The Status code for a failed job in the NetBackup Activity Monitor is either Status 130 (System error occurred) or Status 72 (The client type is incorrect in the configuration database). Example of the error logged in the bpfis log on the EV SQL server:
TECH215621 | 2014-11-12
Technical Solutions | CMS-XML

GENERAL ERROR: Exchange Server 2010 backup fails with status code 72

the client type is incorrect in the configuration database( 72 )
TECH128589 | 2014-06-06
Technical Solutions | CMS-XML

Set up the master to use a new Automated Cartridge System Library Software or Library Station library and getting status 72 status_pending

Set up the master to use a new Automated Cartridge System Library Software or Library Station library and getting status 72 status_pending
TECH35471 | 2013-10-23
Technical Solutions | CMS-XML

Backup of EV databases fail with status 72 and 1542 when the EV SQL Server is configured to use a non-default port number.

Backup of EV databases fail with status 72 and 1542 when the EV SQL Server is configured to use a non-default port number.
TECH201654 | 2013-09-26
Technical Solutions | CMS-XML

SharePoint backup failed: FTL - snapshot preparation failed - No SharePoint objects to backup., status 72

SharePoint deployed with SQL in an MSCS cluster, after the database switched to another node, SharePoint application GRT backup failed: 16 bpfis main: FTL - snapshot preparation failed - No SharePoint objects to backup., status 72
TECH202327 | 2013-08-27
Technical Solutions | CMS-XML

Backup of Enterprise Vault(EV) databases, where EV and SQL servers are clustered may fail with Status 72 and Status 1542

Backup of Enterprise Vault(EV) databases, where EV and SQL servers are clustered may fail with Status 72 and Status 1542
TECH204301 | 2013-07-15
Technical Solutions | CMS-XML

Inventory error for acs robot "multiple errors" status = 72 status_pending, 204 initialization failed, and 225

Relevant info: If the ACSLS server cannot route to the media server s host name, override the default behavior by using acs_ssi_hostname = hostname in the /usr/openv/volmgr/vm.conf file where the value for hostname is a host name associated with an IP address the ACSLS can reach on the media server. STATUS CODES: 225 204 72
TECH67982 | 2009-01-25
Technical Solutions | CMS-XML

NetBackup status code 72: the client type is incorrect in the configuration database

72
TECH57926 | 2008-01-20
Technical Solutions | CMS-XML

acsd will not start: "ACS status = 72, status_pending"

acsd will not start: "ACS status = 72 , status_pending"
TECH34668 | 2005-01-29
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.

47 49 4f 50 01 00 00 01 00 00 02 04 00 00 00 00 GIOP............ 00 00 00 01 00 00 00 03 00 00 00 1b 49 44 4c 3a ............IDL: 56 65 72 69 74 61 73 2f 45 4d 4d 2f 53 65 72 76 Veritas/EMM/Serv
TECH69625 | 2009-01-15
Technical Solutions | CMS-XML

Exit status 72? | Symantec Connect

Exit status 72 ?
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?