[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
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
