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

Test Query for a vCloud Director policy may fail with error "VM retrieval failed, server = [vcloudserver.domainname]., nbu status = 1, severity = 1(1)"

10/23/2014 10:56:32.106 [Debug] NB 51216 ncf 309 PID:656 TID:2860 File ID:366 [No context] 1 [CFEObserverMgr::initialize] Async report delivery disallowed by framework components (../CFEObserverMgr.cpp: 129 )
TECH225821 | 2014-10-28
Technical Solutions | CMS-XML

Image Cleanup job failing with error 2060037 and exit status 174

4/3/2013 1:26:21 AM - Critical bptm(pid=3968) image delete failed: error 2060037: access not allowed 4/3/2013 1:26:26 AM - Error bptm(pid=3968) cannot write image to disk, attempted write of 252928 bytes, system wrote 0 4/3/2013 1:26:26 AM - Info bptm(pid=3968) EXITING with status 129 ----------
TECH205365 | 2014-02-10
Technical Solutions | CMS-XML

GENERAL ERROR: Long delays seen for jobs between end-writing and done state, jobs staying queued and not progressing, jobs not disengaging and releasing drives.

07:53:19.223 [1096] 2 available_media: (BPTM) STU label -- num active = 1, num available = 3, num inuse = 3 07:53:19.225 [1096] 2 nb_getsockconnected: host= master hostname service=bpcd address=148. 129 .68.6 protocol=tcp reserved port=13782 07:53:19.225 [1096] 2 nb_getsockconnected: Connect to master hostname on port 945
TECH38012 | 2013-10-23
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?