Video Screencast Help

possible to configure VVR (hpux) to a dedicate LAN?

Created: 23 Feb 2012 • Updated: 22 Mar 2012 | 5 comments
This issue has been solved. See solution.

Our product is implemented on HPUX, we use VVR to replicate data from one server to another. The product itself is distributed on 3 servers with some network traffic already.  We are wondering if we can isolate replication traffic to a dedicate lan so it won't conflict with other network traffic and get better performance.

Thanks.

Comments 5 CommentsJump to latest comment

Gaurav Sangamnerkar's picture

Yes, that is possible, you can define alias host name is /etc/hosts and the same defined in vvr config... I.e rlink parameters..

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

SOLUTION
pc1861's picture

Thanks for your input, to make sure I got it correct, did you mean ....

If there is serverA and serverB, then assign a new IP to lan2 on serverA and add that to /etc/hosts as serverA2, and apply the same to serverB.  And use serverB2/serverA2 in any vradmin command instead of serverA/serverB. 

mikebounds's picture

Yes, but once you have configured VVR with serverB2/serverA2 you don't need to refer to these hosts in vradmin commands unless you have more the one secondary (like Server A replicates the same data to both ServerB and ServerC) - for example with just server A and B you would use command

vradmin -g dg migrate RVG-name

to migrate from serverA to serverB, but if you had 2 secondaries then to do the same you would need to use:

vradmin -g dg migrate RVG-name serverB2

You can use the above syntax with just one secondary, but it is not necessary.

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below

mikebounds's picture

Isolating the replication traffic is the norm and is recommended.  The easiest way to do this is to put the VVR network interfaces into a separate network with its own network mask, but alternatively you can use static routes.  Then configure VVR with this network:

  • If creating RDS, then when running vradmin addsec, specifiy IPs or hostnames for the VVR interfaces for prihost and sechost.  
  • If changing an existing RDS, then use vradmin changeip command.

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below