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-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Saran Brar
Sent: Thursday, March 24, 2011
2:25 PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Linux backup
issue
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?