NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 129

Media Manager status code 129
HOWTO104494 | 2014-11-20
How To | CMS-XML

NetBackup status code: 129

NetBackup status code : 129
HOWTO104051 | 2014-11-20
How To | CMS-XML

While running backups in PureDisk, getting error status 129 and status 83.

While running backups in PureDisk, getting error status 129 and status 83.
TECH168898 | 2013-12-04
Technical Solutions | CMS-XML

Vault not deleting backups after duplicating tape. Backups failing with status 129: disk storage unit is full

Vault not deleting backups after duplicating tape. Backups failing with status 129 : disk storage unit is full
TECH77025 | 2013-10-24
Technical Solutions | CMS-XML

NetBackup backups and/or duplications report status 129 'Disk storage unit is full' when targeting windows-based Media Server Deduplication (MSDP).

status 129 Disk storage unit is full
TECH148008 | 2013-09-24
Technical Solutions | CMS-XML

STATUS CODE: 129 - Backups to disk storage units fail with a VERITAS NetBackup (tm) Status 129 because the storage unit is full.

STATUS CODE : 129 - Backups to disk storage units fail with a VERITAS NetBackup (tm) Status 129 because the storage unit is full.
TECH44663 | 2013-08-23
Technical Solutions | CMS-XML

BUG REPORT: After an update of the OpenStorage (OST) plug-in to version 2.2.1.1, NetBackup may report status code 129 and "EMM status: Insufficient disk space or High Water Mark would be exceeded Disk storage unit is full(129)" more frequently due to a change in the method of calculation of free space on the storage unit.

129
TECH135174 | 2011-05-18
Technical Solutions | CMS-XML

BUG REPORT: pre-6.x Images on Staging DSUs are not cleaned up after an upgrade to NetBackup 6.5, causing backups to fail reporting status code 129: Disk storage unit is full

129
TECH59006 | 2009-01-10
Technical Solutions | CMS-XML

BUG REPORT: Backups to Disk Staging Storage Units (DSSU) in NetBackup 6.5 fail with Status 129 (disk storage unit is full). Relocated DSSU images are not deleted from the file system.

BUG REPORT: Backups to Disk Staging Storage Units (DSSU) in NetBackup 6.5 fail with Status 129 (disk storage unit is full). Relocated DSSU images are not deleted from the file system.
TECH55351 | 2009-01-04
Technical Solutions | CMS-XML

BUG REPORT: When using Veritas NetBackup 6.0 (tm), a backup to Disk Staging Storage Unit (DSSU) fails with status code 129 (disk storage unit is full).

129
TECH48105 | 2007-01-22
Technical Solutions | CMS-XML

Snapshot errors encountered with ibm4000 arrays (NetBackup status code 156)

command [create FlashCopyLogicalDrive baseLogicalDrive= drive-claix11-1 userLabel= drive-claix11-1_flcp ;]. Mon Mar 31 2008 14:25:23.037164 Pid - 1065104 / Thread id - 1 OUTPUT=[Could not create a flashcopy logical drive using the Create FlashCopyLogicalDrive command at line 1. Error 129 - The operation cannot complete because the maximum number of flashcopy logical drives have been created for this base logical drive.
HOWTO88357 | 2013-09-30
How To | CMS-XML

ImageCleanup Not Running on Catalog Backups Causing Error 129 | Symantec Connect

ImageCleanup Not Running on Catalog Backups Causing Error 129
Connect Forums | HTML

netbackup 129 error & storage unit's high water mark | Symantec Connect

netbackup 129 error & storage unit's high water mark
Connect Forums | HTML

Netbackup 6.5.6 bug (error code 129) | Symantec Connect

Netbackup 6.5.6 bug ( error code 129 )
Connect Forums | HTML

Status 129 [DSSU Full] - Can I restore data from an incomplete backup? | Symantec Connect

Status 129 [DSSU Full] - Can I restore data from an incomplete backup?
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?