Thanks to all who replied on and off the list.  I took one of the 
suggestions and have done some scripting, especially since it got me 
more than halfway complete on another project I've wanted to do: ad hoc, 
user driven, manual full and incrmental backups.

I started with a table consisting of, among other things, clientname, 
full or incr, linux or windows, along with the corresponding policyname 
and schedule name. It is used by a script that accepts the 1st 3 items 
as parms and initiates a backup with bpbackup, after verifying the 
client and appropriate platform are up using bpgetconfig.

For my machine that can't decide whether its Linux or Windows, I just 
run the script at key times during the week, scheduled with cron.  

For my clients that need ad hoc full and incremental "manual" backups, I 
now have a little we page that invokes the above script after a little 
parameter checking.  I still think NetBackup should support client 
initiated manual backups, but this does the trick for now.

Thanks again, for everyone's help and ideas.    cheeers, wayne

>I have a machine to backup that is sometimes booted with Windows and
>sometimes booted with Linux.  The file systems are complely different and
>each need to be backed up. 
>
>My problem is that we don't want or otherwise need a second IP address for
>the machine.
>
>Can I (How do I) set this up so that NetBackup will make a Windows backup
>when Windows is booted and Linux is backed up when Linux is booted?  (Now,
>for example, if Linux is booted and a Windows backup is attempted, I get
>"invalid filelist specification" or some such error).  
>  
>