NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

MS SQL and other XBSA Backups fail with status code 239 reported after applying the NetBackup 7.5.0.7 maintenance release.

239
TECH215866 | 2014-04-28
Technical Solutions | CMS-XML

STATUS CODE 236 or 239 or 245: NetBackup SAP backups with RMAN fail immediately without going active

239
TECH49018 | 2013-10-03
Technical Solutions | CMS-XML

Robotic status code 239

Robotic status code 239
HOWTO91239 | 2013-10-02
How To | CMS-XML

NetBackup status code: 239

NetBackup status code : 239
HOWTO90651 | 2013-10-02
How To | CMS-XML

NBCC aborts because the nbsvrgrp command exits with status 239

NBCC aborts because the nbsvrgrp command exits with status 239
TECH190433 | 2013-04-17
Technical Solutions | CMS-XML

NetBackup status code: 239

NetBackup status code : 239
HOWTO50999 | 2012-11-19
How To | CMS-XML

Robotic status code 239

Robotic status code 239
HOWTO51589 | 2012-11-19
How To | CMS-XML

Informix logical log backup by the alarm program fail with status 239, all others succeed

Informix logical log backup by the alarm program fail with status 239 , all others succeed
TECH165192 | 2011-07-21
Technical Solutions | CMS-XML

Error code 239.

11/08/2010 05:00:06 master_server_name - CLIENT clientname POLICY policyname SCHED EXIT STATUS 239 (the specified client does not exist in the specified policy)
TECH143859 | 2010-11-10
Technical Solutions | CMS-XML

NetBackup status code: 239

NetBackup status code : 239
HOWTO35110 | 2010-10-29
How To | CMS-XML

Robotic status code: 239

Robotic status code : 239
HOWTO35699 | 2010-10-29
How To | CMS-XML

Vault catalog backup fails with status 294 and 239.

The vault session detail.log will confirm that the vault catalog backup failed with status 239 . STEP = catalog_backup
TECH74021 | 2010-01-17
Technical Solutions | CMS-XML

STATUS CODE 239: NetBackup for Microsoft SQL Server backups fail with Status Code 239 when attempting to back up a SQL Cluster

239
TECH42954 | 2009-01-01
Technical Solutions | CMS-XML

SQL Backup Failing Status 239 | Symantec Connect

SQL Backup Failing Status 239
Connect Forums | HTML

BPARCHIVE : the specified client does not exist in the specified policy error code 239 | Symantec Connect

BPARCHIVE : the specified client does not exist in the specified policy error code 239
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?