Hi,

You have that problem because I guess MCSG is not NetBackup aware.

For my case, I have configured a cluster pair on HP-UX for the NetBackup
Master server using Veritas Cluster Server.

This is how it works (I'll use your hostname as an example):

If the virtual is currently running on Node 1, then the bp.conf on the
virtual node will looks like:
SERVER = h1adm01ab
SERVER = h1adm02ab
SERVER = v1bkpb

If the virtual node is to failover to Node 2, then the bp.conf on the
virtual node will looks like:
SERVER = h1adm02ab
SERVER = h1adm01ab
SERVER = v1bkpb

That mean VCS is updating the bp.conf everytime a failover occurs. And the
very first entry in the bp.conf should be the hostname of the node that the
virtual host is sitting on.

I guess the work around for your case is to write a script to perform the
above.

You probably you need to insert this script after mounting the lvol in your
/etc/cmcluster/<package name>/<package name>.cntl (hope I'm not wrong, not
very familiar with MCSG) and before starting the NetBackup daemons.

Hope it helps.


ACC



-----Original Message-----
From: support.cphvt-s AT sas DOT dk
To: veritas-bu AT mailman.eng.auburn DOT edu
Sent: 8/8/02 8:39 PM
Subject: [Veritas-bu] Netbackup Master on a Unix cluster - How to use the
virtual backu p network address ?

We have a Netbackup DataCenter version 3.4.1 Master installed on a HP-UX
Service Guard cluster. 

The /usr/openv software is in a software package which can run on either
of
two nodes in the cluster. 

The Netbackup package has a backup network virtual hostname "v1bkpb". 
i.e. v1bkpb is the same ip whichever node the netbackup package is
running
on. 
Node 1 in the Unix cluster has a static backup network name "h1adm01ab"
Node 2 in the Unix cluster has a static backup network name "h1adm02ab"

We wish to configure the bp.conf on the clients to listen for the
virtual
hostname "v1bkpb"...
however only the static hostnames are sent by deamon bpcd. 
i.e. 
bp.conf with SERVER = v1bkpb   fails
bp.conf with SERVER = h1adm01ab works if the package happens to be
running
on Node 1 ..but fails if the package is running on Node 2. 

We can get round this by have both the static names in the bp.conf. But
this
is a bit messy. 

Question: How do we configure netbackup to use the virtual hostname
"v1bkpb"
?  
               Or do we really have to live with static names only ?

Hopefully the above is not completely black talk!

rgds Martyn 
> Martyn Holden
> Scandinavian IT Group
> Department CPHVT-S
> Post Box 1819, Engvej 165, 2300 København S, Denmark
> Phone: +45 3232 4463, Mobile: +45 2322 4463, Fax: +45 3232 2545,
Email:
> martyn.holden AT sas DOT dk
        www.scandinavianIT.com

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu