Logging detail information about unrecoverable/recoverable error
Hello all, Have you anybody experience with logging detail information during read/write to medium. So, the log /db/media/error has some information about any drive and medium error throught TapeAlert with SCSI code or code of tape drive. I am lookup for detail information like - read byte, write byte, recoverable error, unrecoverable error, ..... In the moment we can to use any solution from library management (Quantum Advanced Reporting , IBM ERMM, Quotium StorSentry) Many thanksSolved865Views6likes4Comments
ImageCleanup Not Running on Catalog Backups Causing Error 129
Hello, We are having an issue with our Catalog Backups that I am hoping somebody can shed some light into. When the disk usage of our catalog backups reach the high-water mark, it is my understanding that an ImageCleanup automatically runs that brings the disk usage back to the low-water mark. We are using ~13GB/day for the catalog backup. The available storage is 100GB. Our high-water mark is currently set to 90%, and the low-water mark is set to 60%. Our retention time is set to 4 days. However, once the disk usage for our catalog passes the 90% mark, an imageCleanup is not running; therefore, once the storage is full, the backup fails with error code 129. We then have to manually remove the images at the Unix level.Solved892Views5likes4Comments
netbackup starter
Hi ALL, I am very new to this Netbackup tool.Currently i have been sent on a training for thi tool for a month.I am also reading the manuals and foruums of netbackups.How ever I have few doubts,If any body has time to clarify them. 1. If I stop BPRD..Scheduled and manual backups all will be stopped?Yes or no. 2.Media server will be only visible in host properties when devices have been attached to them?not by after nbemmcmd -addhost command? 3. VSS is used in vmware backup policy type to freeze the snapshot? 4.media from drive needs to be returned to the same slot from which it came ? 5 if some other tapes on that slot then library drive will be down? 6.Can i add a client with ip address?if yes then there must not be name resolution requirement?Solved839Views4likes7Comments
Netbackup code 155 occurring on an AIX client
Hello, We have one Backup client that’s getting the code 155 disk full error NetBackup status code: 155 Message: disk is full Explanation: The write to the catalog file failed because the disk that contains the catalog database is full, or the track log folder is full. Recommended Action: Free up space on the disks where NetBackup catalogs reside or where the track log folder resides and retry the operation. Question for freeing up space on where the track log folder resides are there specific files that we can delete without the intervention of the AIX sysadmin? I don’t want to delete something that is important. I check the /usr and it only has 1.77GB of space left root)/> df -g /usr Filesystem GB blocks Free %Used Iused %Iused Mounted on /dev/hd2 10.38 1.77 83% 84616 17% /usr The Code 155 error is only occurring one backup client the bkpkar.log is below Bkpkar 20:54:24.375 [22413352] <16> fwrite_and_log: fail to write <fix size entry block> for track journal, backup id:<NULL>, file:<11000232fb.tif>, err_num:<28>, to write:<1>, wrote:<0> 20:54:24.400 [22413352] <16> bpbkar SelectFile: fscp_add_full_entry() failed, error : disk is full 20:54:24.400 [22413352] <16> bpbkar: ERR - bpbkar FATAL exit status = 155: disk is full 20:54:24.400 [22413352] <4> bpbkar: INF - EXIT STATUS 155: disk is full 20:54:33.258 [22413352] <16> bpbkar: ERR - read server exit status = 155: disk is full 20:54:33.473 [22413352] <16> ct_cat_close: failed to fflush for file in dir(/datasink/importDRM/backup_0315/15069/03/359832/), error is -1 20:54:33.485 [22413352] <2> ct_cat_close: close current track journal 20:54:33.485 [22413352] <2> ct_cat_close: close previous track journal 20:54:33.485 [22413352] <16> bpbkar: ct_cat_close() failed, error (14) 20:54:24.375 [22413352] <16> fwrite_and_log: fail to write <fix size entry block> for track journal, backup id:<NULL>, file:<11000232fb.tif>, err_num:<28>, to write:<1>, wrote:<0> 20:54:24.400 [22413352] <16> bpbkar SelectFile: fscp_add_full_entry() failed, error : disk is full 20:54:24.400 [22413352] <16> bpbkar: ERR - bpbkar FATAL exit status = 155: disk is full 20:54:24.400 [22413352] <4> bpbkar: INF - EXIT STATUS 155: disk is full 20:54:33.258 [22413352] <16> bpbkar: ERR - read server exit status = 155: disk is full 20:54:33.473 [22413352] <16> ct_cat_close: failed to fflush for file in dir(/datasink/importDRM/backup_0315/15069/03/359832/), error is -1 20:54:33.485 [22413352] <2> ct_cat_close: close current track journal 20:54:33.485 [22413352] <2> ct_cat_close: close previous track journal 20:54:33.485 [22413352] <16> bpbkar: ct_cat_close() failed, error (14) 21:04:42.097 [34275332] <4> is_excluded: Excluded /datasink/importDRM/backup/2015/15035/04/337763/core by exclude_list entry core 21:27:57.930 [34275332] <16> fwrite_and_log: fail to write <fix size entry block> for track journal, backup id:<NULL>, file:<21000522rb.tif>, err_num:<28>, to write:<1>, wrote:<0> 21:27:57.946 [34275332] <16> bpbkar SelectFile: fscp_add_full_entry() failed, error : disk is full 21:27:57.946 [34275332] <16> bpbkar: ERR - bpbkar FATAL exit status = 155: disk is full 21:27:57.947 [34275332] <4> bpbkar: INF - EXIT STATUS 155: disk is full 21:28:05.949 [34275332] <16> bpbkar: ERR - read server exit status = 155: disk is full 21:28:06.197 [34275332] <16> ct_cat_close: failed to fflush for file in dir(/datasink/importDRM/backup_0315/15069/03/359834/), error is -1 21:28:06.211 [34275332] <2> ct_cat_close: close current track journal 21:28:06.211 [34275332] <2> ct_cat_close: close previous track journal 21:28:06.211 [34275332] <16> bpbkar: ct_cat_close() failed, error (14) The Client is a AIX Server running O.S 7.1 The backup client is 7.6.0.3 Thanks in Advance!Solved9.2KViews3likes14Comments
VMware VM "needs consolidation" after backup failure
Has anyone else run into this issue? VM backup fails with a "Status 13" or "Status 156" or "Status 40" - I have several hundred VMs and only a few end up in this state during a backup window. No snapshots show up in Snapshot Manager on the VMs that have this error. When consolidation is attempted VMware throws a "Unable to access file <unspecified filename> since it is locked" error. The "fix" for us has been to run "services.sh restart" on the ESXi server - this unlocks the file - then manually consolidating the VM. Sounds a lot like this issue: https://www-secure.symantec.com/connect/forums/problem-backup-virtual-machine-when-vm-convert-status-consolidate Master: 7.6.0.2 on Solaris 10 Media: 2.6.0.2 on 5220 Appliances17KViews3likes11Comments
How to get the lost media report from Unix CLI without using vltopmenu?
I see that vlteject command can be used, but am not sure about the syntax. I need to write a script which will send the lost media report as anEmail attachmentto the tape librarian daily. Can any one help me in this?Solved1.3KViews3likes14Comments
Netbackup 7.5.0.6 Clients for AIX & Linux
Hi, I've upgraded my Master Server from v7.5.0.3 to v7.5.0.6 which is running Solaris. Now i'm backing up Servers of different platforms (Solaris, Linux, AIX and HP-UX). For Solaris servers, i was able to 'FTP' the client software and installed it with no issues. Now i want to upgrade the other servers (Linux & AIX) but there's no install file on the clients folder under those 2 platforms and others, i only have a client for Solaris. root:/opt/openv/netbackup/client/RS6000/AIX53# ls -l total 0 root:/opt/openv/netbackup/client/RS6000/AIX53# How does the install work?? Does it only install the packages of the Master Server (Solaris)?... becuase i had all the clients in my inatial install folder root:/netbackup/Softwares/NBU_7.5.0.6# ls NB_7.5.0.6.solaris.tar VrtsNB_7.5.0.6.preuninstall VrtsNB_CLT_7.5.0.6.MACINTOSH.tar.gz NB_CLT_7.5.0.6.tar VrtsNB_7.5.0.6.solaris.tar.gz VrtsNB_CLT_7.5.0.6.README NB_update.install VrtsNB_CLT_7.5.0.6.HP-UX-IA64.tar.gz VrtsNB_CLT_7.5.0.6.RS6000.tar.gz VrtsNB_7.5.0.6.README VrtsNB_CLT_7.5.0.6.HP9000-800.tar.gz VrtsNB_CLT_7.5.0.6.Solaris.tar.gz VrtsNB_7.5.0.6.postinstall VrtsNB_CLT_7.5.0.6.INTEL.tar.gz VrtsNB_CLT_7.5.0.6.postinstall VrtsNB_7.5.0.6.postuninstall VrtsNB_CLT_7.5.0.6.Linux-IA64.tar.gz VrtsNB_CLT_7.5.0.6.postuninstall VrtsNB_7.5.0.6.preinstall VrtsNB_CLT_7.5.0.6.Linux.tar.gz VrtsNB_CLT_7.5.0.6.preinstall So now, how do i upgrade my other servers? i remember i had the same problem with v7.5, i had to download Netbackup 7.5 CLIENTS separately. If this is still the case, then where do i find them been looking everywhere. Thanks in advanceSolved1.7KViews3likes2Comments
How to view debug_dump_f file
Hi, I want to read the file generated while applying the TECH below http://www.symantec.com/business/support/index?page=content&id=TECH58549 I got generated debug files as below: OSS_HACS_ROOT_oss1_bk_oss2_bk_1388376722_INCR_debug_dump.f Could you please advice on how to read this file in order to troubleshoot an issue hapening during a backup of multiplexed policy using Netbackup. Thanks &BR752Views3likes7Comments
How to view debug_dump_f file
Hi, I want to read the file generated while applying the TECH below http://www.symantec.com/business/support/index?page=content&id=TECH58549 I got generated debug files as below: OSS_HACS_ROOT_oss1_bk_oss2_bk_1388376722_INCR_debug_dump.f Could you please advice on how to read this file in order to troubleshoot an issue hapening during a backup of multiplexed policy using Netbackup. Thanks &BR