Andrew,

This is very normal and it's ok.

Basically as long as the last value in the path IS NOT a link, 
netbackup will backup the path properly.

So, if you have say your db dir mounted to some really big fs as 
/nbu_db and it's linked to /usr/openv/netbacup/db, don't specify 
/usr/openv/netbackup/db as the path to backup, else you'll end up with 
just the link backed up and not the data.  You'd want to specify 
/nbu_db as the path instead.  But the default uses a "middle" link and 
NBU is able to figure that one out and backup the real data.  The 
tricky part comes in during a recover.  You need to make sure all the 
links exist else you could fill a fs pretty easily.  Best practices 
would suggest that you backup based on host name:real path...

For example
hostname:/opt/openv/netbackup/db
etc, etc..

HTH
-Tim

If you just list
On Jan 19, 2006, at 1:35 PM, Andrew Stueve wrote:

> I ran into something odd.
>
> I may be suffering from lack of sleep, but Solaris actually installed
> NetBackup in /opt/openv and creates a symlink /usr/openv.  The backup
> catalog all specify /usr/openv/xxxxx.
>
> There won't be a problem with the symlink, will there?  Since the
> directories underneath are specified (ex /usr/openv/netbackup/db ), we
> should be good.  Yes?
>
> Personally, I haven't had to do a recovery from tape on Solaris.  I 
> have
> only done it on Windows.
>
> -- 
> Andrew Stueve
> andrew.stueve AT neovera DOT com
> 571-437-5754
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>