SG and DP three subnets.

[J Turner]

Here is the scenario.
hpux 11.23 (all servers..patched.)
Latest Ver Service Gaurd.
DP 6.0

Three subnets on every machine.
For the sake of this forum the layout is:

10.x.x.x Management We use the 10 Net to push patches, update hosts files, etc

172.x.x.x Backup Strictly for use by the DP server for data transport to Libraries

192.x.x.x Forward Facing IP This is where Oracle 10g sits.

Currently all Lans are working and all subnets reachable.
ServerA is Primary and I have added a virtual IP address(192.x) to the config files of SG.
I have also had some luck at configuring the package. It is a simple failover to serverB
ServerC is my DP server (172.x)
I can fail a test PKG over to serverB and it all works.
My question is:
I am not sure how to backup my serviceguard pkg using my 172 subnet.
By the customers layout I can NOT use 192 subnet to backup on.

Any help would be appreciated.
Thanks

[melvyn burnard]

why not add a virtual ip for the package that goes onto the 172 subnet?

[Steven E. Protter]

Shalom,

I'd set up a dns entry pointing to the floating IP address on the 172 network. Then your backup software will be able to connect via name or number.

Your SG package will need a floating IP address added if it already doesn't have one.

SEP

[J Turner]

Thanks for the replies...
I am not sure I can use a 172.
All of the customers apps come in strictly from 192. Isnt the floating IP for the function of allowing apps to see the same IP no matter where the package is?

[Stephen Doud · Accepted solution]

Your statement was:
'I am not sure how to backup my serviceguard pkg using my 172 subnet.
By the customers layout I can NOT use 192 subnet to backup on.'
But you continue to refer to the customer apps using the 192 network.
In what way are the backups that you want to do using the 172 network affected by the 192 network? Why do you relate the 192 network to the 172 network which you want to use for transferring backup files?

Perhaps it is because the files that you want to backup move with the 192 network?
If so, then add a relocatable IP to the same package but for the 172 network NIC... this is certainly feasable. You can also assign an alias to that IP, such as dpnet - and add that alias to the /etc/hosts on all 3 nodes.
Then, as the Oracle package is moved from node to node, the dpnet will also move and dataprotector will always be looking to the server where the data files are currently open.

[J Turner]

Thanks much.
That sounds like the approach I will use.
You hit the nail on the head...

[J Turner]

add a relocatable IP to the same package but for the 172 network NIC... this is certainly feasable. You can also assign an alias to that IP, such as dpnet - and add that alias to the /etc/hosts on all 3 nodes.