NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 79

Media Manager status code 79
HOWTO104458 | 2014-11-20
How To | CMS-XML

Device management status code 79

Device management status code 79
HOWTO104700 | 2014-11-20
How To | CMS-XML

Device configuration status code 79

Device configuration status code 79
HOWTO104615 | 2014-11-20
How To | CMS-XML

NetBackup status code: 79

NetBackup status code : 79
HOWTO104007 | 2014-11-20
How To | CMS-XML

Synthetic backup failing with status code 79 | Symantec Connect

Synthetic backup failing with status code 79 "unsupported image format for the requested database query( 79 )" According to Symantec Support, this error message is telling me that one or more of the images to be synthesized was encrypted and that these images cannot be synthesized.
Connect Forums | HTML

NetBackup status code: 1

No images were found to synthesize (status code = 607). TIR information has been pruned from component images (status code = 136). Image format is unsupported ( status code = 79 ).
HOWTO103931 | 2014-11-20
How To | CMS-XML

Getting error "failed to create shared memory" when starting Netbackup Sybase ASA

2345: umask(022) = 077 2345: fstatvfs(8, 0xffbfee10) Err# 79 EOVERFLOW 2345: close(8) = 0
TECH128454 | 2014-03-28
Technical Solutions | CMS-XML

Job fails with status 232 after going active on RHEL media server using NIS/YP

03:30:31.891 [Debug] 51216 137 PID:25000 TID:3 File ID:117 [No context] 3 [parseData] not enough data to parse: dataAvail = (37)64 6f 5f 79 70 63 61 6c 6c 3a 20 63 6c 6e 74 5f 63 61 6c 6c 3a 20 52 50 43 3a 20 54 69 6d 65 64 20 6f 75 74 a ...snip...
TECH145022 | 2014-03-24
Technical Solutions | CMS-XML

BUG REPORT: Vault session files greater than 2GB will cause a status 289 when generating reports and the bprd daemon will not clean up the Vault session directory.

2 recursive_dir_delete: lstat() failed: Value too large for defined data type ( 79 ) 2 recursive_dir_delete: cannot delete /usr/openv/netbackup/vault/sessions//sid: File exists (17)
TECH38203 | 2013-10-23
Technical Solutions | CMS-XML

NDMP restore fails with status 5 and bptm core dumps when switching to the next media.

write(3, 11:05:30.797 [15835] 2 signal_ ..., 79 ) = 79
TECH178587 | 2013-10-25
Technical Solutions | CMS-XML

Quantum DXi VTL; Status Code 83; Backup jobs are getting failed,storage units are not available.

8/19/2011 9:05:05 AM - requesting resource @aaaaO 8/19/2011 9:05:05 AM - granted resource MediaID=@aaaaO;DiskVolume=MyLSU;DiskPool=MyPool;Path=MyLSU;StorageServer=ostb_10.10.11. 79 ;MediaServer=hosta 8/19/2011 9:05:12 AM - Info Duplicate(pid=14097) Initiating optimized duplication from @aaaaO to @aaaaQ
TECH167803 | 2012-01-09
Technical Solutions | CMS-XML

Full backups fail intermittently with status 40 when they run for several hours

kwrite(3, 2 1 : 2 5 : 3 3 . 8 7 9 .., 79 )
TECH176851 | 2011-12-13
Technical Solutions | CMS-XML

Backup or restore fails with status 5/6/21/25 at either the beginning or end of the job

The current time is: 14:17:31.95 The current time is: 14:17:32. 79 TCP
TECH156471 | 2011-03-24
Technical Solutions | CMS-XML

nbu_snap method with UFS is limited to disks sizes of 1 TB and may fail on larger disks with (failed err=-1 snerrno=79) overflow when a snapshot is attempted.

The nbu_snap method for taking snapshots on Solaris systems can fail with an overflow error when trying to snap a partition of any size on a disk over 1TB in size. The disks must use the VTOC or SMI label structure and not the unsupported EFI labels that are normally used for larger disks.
TECH225220 | 2014-10-13
Technical Solutions | CMS-XML

Disk Storage Unit Full Error | Symantec Connect

Disk Storage Unit Full Error When I look at the detailed status I can confim that the right DSU has been requested and granted. It says “estimated 214619400 kbytes needed, yet it runs out of space. When I look at the DSU there’s 79 .2GB free.
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?