You will see this message when / is getting backed up:
"/u02 is in a different file system from /. Skipping."

This is perfectly normal. /u02 should be backed up on its own.

Have you tried looking for /u02 in BAR?

Easiest way to prove is to "Allow multiple data streams" in policy attributes combined with ALL_LOCAL_DRIVES. (ONLY do this prior to a Full backup, otherwise Incrementals will run as Full.)
You will see a backup job being generated for each mount point.

Please see this discussion: https://www-secure.symantec.com/connect/forums/net...

Try to backup an internal file or folder in /u02 in a test policy something like /u02/tmp/ and see how it goes, also what is your NBU version? and how are you exclude_lists is /u02 in there?

 you is that it is backing up / (root) and in doing so it  sees that /u02 is a separate file system, and it knows you are doing  multiply jobs, so it will not backup /u02 with root but will do it as a  separate job. 

I have this problem before, you have to check the option "Cross mount points" in properts of your policy.

Do this and the backup will work fine.

I have also seen this in the past and it usually gets around it by having the policy for the specific directory - it seems to force it down that path - would still check the cross mount point box as well though

DO NOT check 'Cross mount points' when ALL_LOCAL_DRIVES is in backup selection.

This will result in duplicate backups - as part of / and when it gets to the mount point.

Seeing the message when / is backed up is perfectly normal. Separate filesystems must not be backed as part of /.

The only time that it would be okay to select 'Cross mount points' is when you only have "/" in the Backup Selection.

See page 613 of NBU Admin Guide for UNIX and Linux, Volume I  http://www.symantec.com/docs/DOC3650

"Note: Do not use the Cross mount points attribute in policies on UNIX systems where
you use the ALL_LOCAL_DRIVES directive in the backup selection list."

Thanks for all the replies.

However, in the original post I stated:

We have tried checking and unchecking multiple combinations of the "Cross Mount Points" and "Follow NFS" options on the Attributes tab.  And on the Backup Selections tab also tried  selecting "All_Local_Drives" and/or "/" and/or separate entries for each mounted volume, and none of these result in backing up the volumes.

Which I think covers most of the responses given.  It's quite possible we've missed setting the correct combination of options in the policy, so was hoping someone could point us in the right direction based on the information we've submitted.

Thanks again!

@Marianne

If you mean "Backup and Restore", I have tried running restores on the Solaris server and all I see is  - for example - is /u01, but there is nothing underneath it when I try to "zoom in".

Thanks.

What is the output of  bpmount -i on the SPARC servers?

Please check if you have exclude_list file in place on the client.

Please post your current policy config. ALL_LOCAL_DRIVES should be sufficient for LOCAL filesystems.
On master: bppllist <policy_name> -U

Please post output of 'bpmount' on the client as per Bill's request.

Please post output of 'df -h' on the client.

Please ensure bpbkar log folder exists on the client. Post log as attachment after the next backup.

Happy New Year.

Did this get resolved?