[Veritas-bu] RMAN Backup Error
Netbackup Guru's, We have a hot database backup policy configured to backup an oracle database on two separate unix hosts. Both hosts backup using the same schedules and the exact same RMAN backup script. One host completes successfully, the other started giving us the following error after a recent clone. RMAN-03009: failure of backup command on ch02 channel at 03/24/2011 07:20:54 ORA-27192: skgfcls: sbtclose2 returned error - failed to close file ORA-19511: Error received from media manager layer, error text: Failed to process backup file bk_1305_1_746591618 ORA-19502: write error on file bk_1305_1_746591618, block number 9901857 (bloc k size=8192) ORA-27030: skgfwrt: sbtwrite2 returned error ORA-19511: Error received from media manager layer, error text: VxBSASendData: Failed with error: The block mentioned here is one of 2 that it seems to be having issues with (the other is 9901825) but I'm at a loss as to where I should be looking to tie in the block number and RMAN backup piece information in order to find out what file the bad block is located in. The result from a netbackup perspective is that the hot backup never completes on the failing host. It just sits there until it eventually times out or we kill it. As far as we can tell, there are no differences in the RMAN or netbackup configurations which points to a data error of some kind. I'd really appreciate any guidance on the best way to troubleshoot this. Thanks in advance, Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 mark.glazer...@spartech.com mailto:mark.glazer...@spartech.com http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup w/IBM LTO-5 Question
We are running 7.1 FA for some time now with LTO-5 and have not seen any issue so far. Best Regards, Bart WALLEBROEK Backup Admin Systems Applications Management Support Specialist Enterprise Applications Delivery - Infrastructure Management S.W.I.F.T. SCRL Message: 5 Date: Wed, 23 Mar 2011 06:32:42 -0400 (EDT) From: Justin Piszcz jpis...@lucidpixels.com Subject: [Veritas-bu] NetBackup w/IBM LTO-5 Question To: veritas-bu@mailman.eng.auburn.edu Message-ID: alpine.deb.2.02.1103230627200.14...@p34.internal.lan Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Hi, I was reviewing: http://www.symantec.com/business/support/resources/sites/BUSINESS/content/live/TECHNICAL_SOLUTION/76000/TECH76495/en_US/nbu_7x_hcl.pdf I only see the HP LTO-5 drives in this document. Can anyone confirm if IBM LTO-5 tape drives are supported with NBU 7.0.1? Is anyone using them? If so, what 'hcart' are they defined as? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup reports
What version of Nbu are you using? Sent via BlackBerry from T-Mobile -Original Message- From: Tewksbury, Kevin ktewksb...@limitedbrands.com Sender: veritas-bu-boun...@mailman.eng.auburn.edu Date: Thu, 24 Mar 2011 10:35:13 To: Veritas Forum (veritas-bu@mailman.eng.auburn.edu)veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Netbackup reports ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup reports
Sorry, I should have mentioned that. We are on Netbackup 6.5.4 Kevin R Tewksbury Sr. Database Administrator LimitedBrands Limited Technology Services 3 Limited Pkwy Columbus, OH 43230 office: (614) 415-4541 cell: (614) 582-4882 Email: ktewksb...@limitedbrands.com -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of ccosta@gmail.com Sent: Thursday, March 24, 2011 10:39 AM To: Tewksbury, Kevin; veritas-bu-boun...@mailman.eng.auburn.edu; Veritas Forum (veritas-bu@mailman.eng.auburn.edu) Subject: Re: [Veritas-bu] Netbackup reports What version of Nbu are you using? Sent via BlackBerry from T-Mobile -Original Message- From: Tewksbury, Kevin ktewksb...@limitedbrands.com Sender: veritas-bu-boun...@mailman.eng.auburn.edu Date: Thu, 24 Mar 2011 10:35:13 To: Veritas Forum (veritas-bu@mailman.eng.auburn.edu)veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Netbackup reports ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Notice: This communication may contain privileged and/or confidential information. If you are not the intended recipient, please notify the sender by email, and immediately delete the message and any attachments without copying or disclosing them. LBI may, for any reason, intercept, access, use, and disclose any information that is communicated by or through, or which is stored on, its networks, applications, services, and devices. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup reports
We got around this by modifying a built in script for NBU.
We are running NBU on RedHat but this should work for Solaris without any
changes and Windows with a few changes.
Copy /usr/openv/netbackup/bin/goodies/media_deassign_notify to
/usr/openv/netbackup/bin and make the changes noted below in the * EDIT
* section. I'm sure the code can be cleaner but it works for us and I
don't like to fix things that aren't broken.
The lines that are commented out in the *** EDIT *** section are used to write
a log file of what is being relabeled. We used it for testing before
implementing the relabel just to be sure it was working correctly.
The only edit that should be needed is to change [ $4 -eq x ] where x is your
robot number [TLD (x)]. We have 3 VTL's therefore the 3 if statements.
#! /bin/sh
# $Header: media_deassign_notify.sh,v 1.2 2007/01/29 20:13:15 $
#bcpyrght
#***
#* $VRTScprght: Copyright 1993 - 2010 Symantec Corporation, All Rights Reserved
$ *
#***
#ecpyrght
#
# media_deassign_notify.sh
#
# This script is called by the NetBackup Enterprise Media Manager, after a
# media record has been de-assigned.
#
# NOTE: this script will always be run in background mode, meaning that
#the NetBackup Enterprise Media Manager will NOT wait for it's
#completion.
#
# This script:
# receives 5 parameters:
# MEDIA ID - the ID of the media(e.g. A1)
# LEGACY MEDIA TYPE - the legacy media type (e.g. 3)
# BARCODE - the barcode of the media (e.g. 111222L3)
# ROBOT NUMBER - the robot number (e.g. 0)
# ROBOT TYPE- the robot type (e.g. 8)
# must be executable by the root user
# should exit with 0 upon successful completion
OUTF=/usr/openv/netbackup/logs/label/MEDIA_DEASSIGN_CALLED.`/bin/date
+\%Y\%m\%d`
#
# main script starts here
#
umask 022
dateStr=`date`
if [ $# -lt 5 ]
then
echo ${dateStr} media_deassign_notify expects at least 5 parameters:
$* $OUTF
exit 1
fi
# You may want to delete the output file elsewhere in order to
# accumulate successful deassignment information.
# If so, comment out the following 4 lines.
#if [ -s $OUTF ]
#then
# /bin/rm -rf $OUTF
#fi
if [ ! -f $OUTF ]
then
touch $OUTF
fi
echo ${dateStr} - $OUTF
echo ${dateStr} MEDIA ID: $1 $OUTF
echo ${dateStr} LEGACY MEDIA TYPE: $2 $OUTF
echo ${dateStr} BARCODE: $3 $OUTF
echo ${dateStr} ROBOT NUMBER: $4 $OUTF
echo ${dateStr}ROBOT TYPE: $5 $OUTF
echo ${dateStr} - $OUTF
# * START YOUR EDIT HERE
#
# --
# *** jinfanti added 12/27/2010 ***
# *** Relabels any new scratch media that is in Robot X ***
# --
#
#echo This is for tape library # $4
if [ $4 -eq 0 ]
then
/usr/openv/netbackup/bin/admincmd/bplabel -o -m $1 -d hcart -p Scratch
#echo /usr/openv/netbackup/bin/admincmd/bplabel -o -m $1 -d hcart -p Scratch
$OUTF
elif [ $4 -eq 2 ]
then
/usr/openv/netbackup/bin/admincmd/bplabel -o -m $1 -d hcart -p Scratch
#echo /usr/openv/netbackup/bin/admincmd/bplabel -o -m $1 -d hcart -p Scratch
$OUTF
elif [ $4 -eq 3 ]
then
/usr/openv/netbackup/bin/admincmd/bplabel -o -m $1 -d hcart -p Scratch
#echo /usr/openv/netbackup/bin/admincmd/bplabel -o -m $1 -d hcart -p Scratch
$OUTF
else exit 0
fi
#
# * END YOUR EDIT HERE
#
# might want to mail this info to someone
#
#cat $OUTF | mail -s Media deassigned jinfa...@harris.com
#
exit 0
Thank you,
Joseph A. Infantino II
BackUp/Recovery Administrator
HARRIS IT Services
Assured Infrastructure Management
Office: 321-724-3011 | Fax: 321-724-3392
Email: joseph.infant...@harris.com
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Tewksbury, Kevin
Sent: Thursday, March 24, 2011 10:48 AM
To: 'ccosta@gmail.com'; veritas-bu-boun...@mailman.eng.auburn.edu; Veritas
Forum (veritas-bu@mailman.eng.auburn.edu)
Subject: Re: [Veritas-bu] Netbackup reports
Sorry, I should have mentioned that. We are on Netbackup 6.5.4
Kevin R Tewksbury
Sr. Database Administrator
LimitedBrands
Limited Technology Services
3 Limited Pkwy
Columbus, OH 43230
office: (614) 415-4541
cell: (614) 582-4882
Email: ktewksb...@limitedbrands.com
-Original Message-
From:
[Veritas-bu] 6.5.5 -- 7.0.1 Upgrade - No tapes are expiring
I performed the 6.5.5 to 7.0.1 upgrade on Tuesday, and made the amazing discovery that my tapes are not expiring when the day/time comes. This also means that I am not getting any of my media back from off site. Has anybody else encountered this? Thank you in advance! Scott PLEASE NOTE: The preceding information may be confidential or privileged. It only should be used or disseminated for the purpose of conducting business with Parker. If you are not an intended recipient, please notify the sender by replying to this message and then delete the information from your system. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Linux backup issue
Hello Folks, Below is my netbackup environment: Master - Solaris 10 , Netbackup 7.0.1 Media - Solaris 10, Netbackup 7.0.1 Client - Suse Linux 2.6, Netbackup 7.0.1 Backup for the client is completing with status code 0 but in the detailed status its showing below warnings Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /share is in a different file system from /. Skipping. Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /net is in a different file system from /. Skipping. Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /var is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /sys is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /boot is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /dev is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /opt is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /proc is on file system type PROC. Skipping. Since we upgraded from 6.5.3.1 to 7.0.1, all unix backups are showing these warnings but are completing with status code 0. I googled for the error but not able to find a suitable answer for it. Can anyone please explain why is that so? Thanks in Advance, Saran ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Linux backup issue
The messages seem to indicate you have deselected Cross Mount Points in the policy.Have you checked that? It is saying it didn't back up these items as they are on separate mount points. If you do df -h on the Linux host it should show you what mounts exist. We actually had an issue here recently on 6.5.4 where we found something had caused that to be deselected in several of our policies. We think it was due to an attempt to manually edit the policies from command line a few months back. At the time that happened it caused other issues as well. Apparently there is a checksum NBU stores internally for what is in the policies so it didn't like that manual modification. Also FYI: We typically add /net, /sys and /proc to our exclude lists for Linux. /net is a shortcut to NFS mounts so unless you intend to back them up via /net probably good to exclude that. /proc and /sys aren't actual disk filesystems so can't be backed up - attempts to do so typically result in a status 1 rather than status 0 on your backup. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Saran Brar Sent: Thursday, March 24, 2011 2:25 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Linux backup issue Hello Folks, Below is my netbackup environment: Master - Solaris 10 , Netbackup 7.0.1 Media - Solaris 10, Netbackup 7.0.1 Client - Suse Linux 2.6, Netbackup 7.0.1 Backup for the client is completing with status code 0 but in the detailed status its showing below warnings Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /share is in a different file system from /. Skipping. Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /net is in a different file system from /. Skipping. Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /var is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /sys is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /boot is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /dev is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /opt is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /proc is on file system type PROC. Skipping. Since we upgraded from 6.5.3.1 to 7.0.1, all unix backups are showing these warnings but are completing with status code 0. I googled for the error but not able to find a suitable answer for it. Can anyone please explain why is that so? Thanks in Advance, Saran Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Linux backup issue
I get all those same warnings on redhat hosts whether I've got cross mount points selected or not... I'm using ALL_LOCAL_DRIVES so it does appear to be backing stuff up, as I do have data in /boot and one or two others it's complaining about... Scott Chapman Senior Technical Specialist Storage and Database Administration ICBC - Victoria Ph: 250.414.7650 Cell: 250.213.9295 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Lightner, Jeff Sent: Thursday, March 24, 2011 11:46 AM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Linux backup issue The messages seem to indicate you have deselected Cross Mount Points in the policy.Have you checked that? It is saying it didn't back up these items as they are on separate mount points. If you do df -h on the Linux host it should show you what mounts exist. We actually had an issue here recently on 6.5.4 where we found something had caused that to be deselected in several of our policies. We think it was due to an attempt to manually edit the policies from command line a few months back. At the time that happened it caused other issues as well. Apparently there is a checksum NBU stores internally for what is in the policies so it didn't like that manual modification. Also FYI: We typically add /net, /sys and /proc to our exclude lists for Linux. /net is a shortcut to NFS mounts so unless you intend to back them up via /net probably good to exclude that. /proc and /sys aren't actual disk filesystems so can't be backed up - attempts to do so typically result in a status 1 rather than status 0 on your backup. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Saran Brar Sent: Thursday, March 24, 2011 2:25 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Linux backup issue Hello Folks, Below is my netbackup environment: Master - Solaris 10 , Netbackup 7.0.1 Media - Solaris 10, Netbackup 7.0.1 Client - Suse Linux 2.6, Netbackup 7.0.1 Backup for the client is completing with status code 0 but in the detailed status its showing below warnings Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /share is in a different file system from /. Skipping. Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /net is in a different file system from /. Skipping. Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /var is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /sys is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /boot is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /dev is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /opt is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /proc is on file system type PROC. Skipping. Since we upgraded from 6.5.3.1 to 7.0.1, all unix backups are showing these warnings but are completing with status code 0. I googled for the error but not able to find a suitable answer for it. Can anyone please explain why is that so? Thanks in Advance, Saran Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- This email and any attachments are intended only for the named recipient and may contain confidential and/or privileged material. Any unauthorized copying, dissemination or other use by a person other than the named recipient of this communication is prohibited. If you received this in error or are not named as a recipient, please notify the sender and destroy all copies of this email immediately. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Linux backup issue
We don't use ALL_LOCAL_DRIVES on our Unix and Linux systems. We specify / (root filesystem) for our OS backups then use exclude lists to leave out the things we don't want. Usually our databases and applications have their own policies starting at their mount points OR aren't backed up because they are test/dev and our policy is to refresh them from Production backups if they have issues. It may be the reason you're seeing the messages is that ALL_LOCAL_DRIVES is essentially being seen as all mount points by NBU so it first backs up / and gives the error from / perspective then moves on to /boot then /var etc... That is it may be NBU behind the scenes is doing: / backup - complains about all submounts not part of / itself /boot backup /var backup You might test that theory by create a small submount of one of the others e.g. /var/test then see if you get complaint about /var/test not being part of /var (as opposed to not being part of /). From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Chapman, Scott Sent: Thursday, March 24, 2011 3:14 PM To: Lightner, Jeff; 'veritas-bu@mailman.eng.auburn.edu' Subject: Re: [Veritas-bu] Linux backup issue I get all those same warnings on redhat hosts whether I've got cross mount points selected or not... I'm using ALL_LOCAL_DRIVES so it does appear to be backing stuff up, as I do have data in /boot and one or two others it's complaining about... Scott Chapman Senior Technical Specialist Storage and Database Administration ICBC - Victoria Ph: 250.414.7650 Cell: 250.213.9295 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Lightner, Jeff Sent: Thursday, March 24, 2011 11:46 AM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Linux backup issue The messages seem to indicate you have deselected Cross Mount Points in the policy.Have you checked that? It is saying it didn't back up these items as they are on separate mount points. If you do df -h on the Linux host it should show you what mounts exist. We actually had an issue here recently on 6.5.4 where we found something had caused that to be deselected in several of our policies. We think it was due to an attempt to manually edit the policies from command line a few months back. At the time that happened it caused other issues as well. Apparently there is a checksum NBU stores internally for what is in the policies so it didn't like that manual modification. Also FYI: We typically add /net, /sys and /proc to our exclude lists for Linux. /net is a shortcut to NFS mounts so unless you intend to back them up via /net probably good to exclude that. /proc and /sys aren't actual disk filesystems so can't be backed up - attempts to do so typically result in a status 1 rather than status 0 on your backup. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Saran Brar Sent: Thursday, March 24, 2011 2:25 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Linux backup issue Hello Folks, Below is my netbackup environment: Master - Solaris 10 , Netbackup 7.0.1 Media - Solaris 10, Netbackup 7.0.1 Client - Suse Linux 2.6, Netbackup 7.0.1 Backup for the client is completing with status code 0 but in the detailed status its showing below warnings Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /share is in a different file system from /. Skipping. Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /net is in a different file system from /. Skipping. Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /var is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /sys is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /boot is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /dev is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /opt is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /proc is on file system type PROC. Skipping. Since we upgraded from 6.5.3.1 to 7.0.1, all unix backups are showing these warnings but are completing with status code 0. I googled for the error but not able to find a suitable answer for it. Can anyone please explain why is that so? Thanks in Advance, Saran Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or
Re: [Veritas-bu] Linux backup issue
Thanks for the replies. We have setup following entries in the backup selection without cross mount points selected. / /boot /opt /var I double checked in the backup image and it seems it is skipping some files which I am not sure of. By using exclude lists we will not backup at all which we do not want. Please help how to get it done. Thanks, Saran On Thu, Mar 24, 2011 at 12:29 PM, Lightner, Jeff jlight...@water.comwrote: We don’t use ALL_LOCAL_DRIVES on our Unix and Linux systems. We specify / (root filesystem) for our OS backups then use exclude lists to leave out the things we don’t want. Usually our databases and applications have their own policies starting at their mount points OR aren’t backed up because they are test/dev and our policy is to refresh them from Production backups if they have issues. It may be the reason you’re seeing the messages is that “ALL_LOCAL_DRIVES” is essentially being seen as “all mount points” by NBU so it first backs up / and gives the error from / perspective then moves on to /boot then /var etc… That is it may be NBU behind the scenes is doing: / backup – complains about all submounts not part of / itself /boot backup /var backup You might test that theory by create a small submount of one of the others e.g. /var/test then see if you get complaint about /var/test not being part of /var (as opposed to not being part of /). -- *From:* veritas-bu-boun...@mailman.eng.auburn.edu [mailto: veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Chapman, Scott *Sent:* Thursday, March 24, 2011 3:14 PM *To:* Lightner, Jeff; 'veritas-bu@mailman.eng.auburn.edu' *Subject:* Re: [Veritas-bu] Linux backup issue I get all those same warnings on redhat hosts whether I’ve got cross mount points selected or not… I’m using ALL_LOCAL_DRIVES so it does appear to be backing stuff up, as I do have data in /boot and one or two others it’s complaining about… *Scott Chapman* Senior Technical Specialist Storage and Database Administration ICBC - Victoria Ph: 250.414.7650 Cell: 250.213.9295 *From:* veritas-bu-boun...@mailman.eng.auburn.edu [mailto: veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Lightner, Jeff *Sent:* Thursday, March 24, 2011 11:46 AM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* Re: [Veritas-bu] Linux backup issue The messages seem to indicate you have deselected “Cross Mount Points” in the policy.Have you checked that? It is saying it didn’t back up these items as they are on separate mount points. If you do “df –h” on the Linux host it should show you what mounts exist. We actually had an issue here recently on 6.5.4 where we found something had caused that to be deselected in several of our policies. We think it was due to an attempt to manually edit the policies from command line a few months back. At the time that happened it caused other issues as well. Apparently there is a checksum NBU stores internally for what is in the policies so it didn’t like that manual modification. Also FYI: We typically add /net, /sys and /proc to our exclude lists for Linux. /net is a shortcut to NFS mounts so unless you intend to back them up via /net probably good to exclude that. /proc and /sys aren’t actual disk filesystems so can’t be backed up – attempts to do so typically result in a status 1 rather than status 0 on your backup. -- *From:* veritas-bu-boun...@mailman.eng.auburn.edu [mailto: veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Saran Brar *Sent:* Thursday, March 24, 2011 2:25 PM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Linux backup issue Hello Folks, Below is my netbackup environment: Master - Solaris 10 , Netbackup 7.0.1 Media - Solaris 10, Netbackup 7.0.1 Client - Suse Linux 2.6, Netbackup 7.0.1 Backup for the client is completing with status code 0 but in the detailed status its showing below warnings Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /share is in a different file system from /. Skipping. Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /net is in a different file system from /. Skipping. Mar 24, 2011 8:00:23 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /var is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /sys is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /boot is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /dev is in a different file system from /. Skipping. Mar 24, 2011 8:00:24 AM - Info bpbrm (pid=12275) from client whplmoscyc1: TRV - /opt is in a different file system from
Re: [Veritas-bu] 6.5.5 -- 7.0.1 Upgrade - No tapes are expiring
Scott, There are some known expiration issues at 7.0.1. One of them is in our late breaking news and has a fix if you have a Windows master: 7.0.1 Late Breaking News http://www.symantec.com/docs/TECH139092 (ET2106924)[cid:image001.jpg@01CBEA3E.2037C970] Duplications fail with a Status Code 191/233/44, Image expiration also does not occur on Windows Master servers http://www.symantec.com/docs/TECH138266 The other problem has to do with tapes not deassigning after the images have expired. If this command frees up the tapes you may need the fix below: - /usr/openv/netbackup/bin/admincmd/bpexpdate -deassignempty -force Contact Symantec Technical Support and reference Etrack 2174639 to obtain a fix for this issue for 7.0.1. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of scott.geo...@parker.com Sent: Thursday, March 24, 2011 11:16 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] 6.5.5 -- 7.0.1 Upgrade - No tapes are expiring I performed the 6.5.5 to 7.0.1 upgrade on Tuesday, and made the amazing discovery that my tapes are not expiring when the day/time comes. This also means that I am not getting any of my media back from off site. Has anybody else encountered this? Thank you in advance! Scott PLEASE NOTE: The preceding information may be confidential or privileged. It only should be used or disseminated for the purpose of conducting business with Parker. If you are not an intended recipient, please notify the sender by replying to this message and then delete the information from your system. Thank you for your cooperation. inline: image001.jpg___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
