Exludes Lsit Aobut /Tmp & /Proc

like for one particular client we have something like this.

the pocliy in which this client is residing does not have "cross mount point" checked.

backup selection path:

/
/home
/var
/tmp
/apps
/boot
 

excludes on this client:

/proc/*
/tmp/*
 

/tmp, /proc (& /sys?) etc are usually excluded by default, but that could depend on the OS in question.

Use bpmount -i to to show the 'kind' of filesystems.

Also curious that you say you have /tmp in your backup selection & are also excluding it?

http://www.symantec.com/business/support/index?page=content&id=TECH52350
http://www.symantec.com/business/support/index?page=content&id=HOWTO33702

regardless of crossmount point? can you tell me little about this crossmount point check if i did that in regrad to the above example? :O

OS are Solaris 9 and 10. Linux and AIX too.

Yeah Andy its a weird world, can you please tell me what would be output of this example?

when setting up a unix client

the NB install puts /tmp and /proc in the exclude list by default.

it has to be in the exclude list to be excluded ( this is a file in <installdir>/netbackup)

if it is NOT in the exclude list it would get backed up - so if you modified the exclude list on the unix client and took out /tmp and /proc it would try to back the up.

the reason it tires to back them up

in unix you have filesystems ( kind of think of them as windows drives)  file systems are MOUNTED on top of some place else

so say you have the file system / (slash - called root)

in /  you have a dir called tmp

now a file system is created called tmp and is MOUNTED in /tmp   - this now becomes a cross mount point.

if you said to yes cross mount points then when the backup does / it will get all sub dirs including /tmp that is MOUNTED there.  It will then go and backup all other file systems as well including the file system /tmp  - so now it has backed it up twice - this is why we say do not cross mount points by default.

if we do not cross mount points when the filesystem / is backed it will see that a filesystem has been mounted on tmp and will say "hey that is a separate file system so I will not get it now, but will get it latter"

so this would apply to all mounted file systems like var, usr, proc, opt and anything else you might have created but will skip any that are listed in the exclude file.

so /tmp and /proc should be added to the exclude list by default when you install NB on a unix client.  If it is not there it will back it up.

cross mount points are backed up as separate file systems so they only get backed up once.

I totally agree with you, but how valid is your statement? as Andy posted and the links proves, it won't be backed up regardless if /tmp /proc is mentioned in the exludes or not. :(. can you have a look at those small TNs. :(

and yes, its not there mentioned in my exludes but now it is. so it will not be backed up now? it wasn't there before so i assume it was bbeing backed up before. and thanks for explaining that. :)

if its there and there is a clash between the backup selection and the exsclude then what happens?

have a lok at J.Hinchcliffe reply below. is that valid?