All,

I am not sure anyone even has this configuration. It is supported by EMC
and they have confirmed that our configuration is correct but here is
the issue.

We have two storage nodes that are in an active/active UDB DB2 cluster.
This is a 4 partitioned DB with two partitions active on nodeA and two
partitions active on nodeB. 
We have created the virtual client to backup using the DB2 module.
The client has the correct syntax in the backup command. The saveset is
correct. 
The storage node field lists curphyhost than the two physical names of
the storage nodes.
When we backup the two partitions that are active on nodeA it works with
no issues. When we attempt to backup the two partitions on nodeB nothing
happens. 

The problem as I see it and have explained it to EMC is this. 

The virtual name is only running on nodeA. The IP for this virtual name
is up on nodeA only. So when we try and kick in a backup with the
virtual name for the partitions on nodeB it does not find those db
partitions on nodeA which is where the virtual IP resides. 

They have given us some workarounds which I am getting ready to try. Is
there anyone out there running anything remotely close to this setup.
Any thoughts how we can get around this. We have played around with the
local host entries on my backup server with the virtual name being an
alias for the physical but all that does is switch the problem from
nodeB to nodeA.  
        

EDWARD COTY
LEAD STORAGE ENGINEER, LCNA
WORK - 973-533-2098
CELL - 973-296-0918
EDWARD.COTY AT AIG DOT COM

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER