SFHA/DR with 2 replications

[Zahid_Haseeb]

Environment

Primary Site = 2 nodes

DR Site = 1 node

OS = RHEL 5.x

SFHA version = 5.1 SP1

Replication connectivity = on Layer-II

Query

Primary Site is going to move to a new site. This required around 20 hours downtime in moving the hardware from Primary Site to New Site.

While 20 hours application will be run from DR site. While running from DR Site the application data will be at risk as there will be no replication as Primary Site hardware will be offline as to move to a New Site.

My Plan

Before moving the hardware to a New Site. I want to place a node on a New Site and want to configure replication between DR Site and New Site (Dont have a plan to control new replication under cluster control). Through this my data will be secure while 20 hours downtime.

When the hardware will reach to New Site we plugged in and online the old Primary Site both nodes and resume replication.

[mikebounds · Accepted solution]

This plan sounds fine to me - do you have any specific questions?

Mike

[Zahid_Haseeb]

We can replicate a Diskgroup with two sites. Right ?
 

[mikebounds]

Yes, but of course this depends on any limitations of the replication product.  This would fine with VVR and you can also use VVR to one site and h/w replication to other site. I think most h/w replication products also support 2 targets.  As you have said, VCS won't be on temporary secondary replication site, so in the unlikely event you did loose DR during migration, recovery from repliction would have to be manual.

Mike

[Zahid_Haseeb]

Mike. We will be using VVR. Additionally Team will be on alert as no HA will be on both sites

[Zahid_Haseeb]

One more question required:

We need a different SRL volume for new replication. Right ?

------x-----x---x

CURRENT CONFIGURATION

# vxprint
Disk group: APP-DG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
dg APP-DG       APP-DG       -        -        -        -        -       -

dm APP-DG01     san_vc3_1    -        524103024 -       -        -       -
dm APP-DG02     san_vc3_2    -        314406576 -       -        -       -

v  APP-LOGS     fsgen        ENABLED  251658240 -       ACTIVE   -       -
pl APP-LOGS-01  APP-LOGS     ENABLED  251658240 -       ACTIVE   -       -
sd APP-DG01-02  APP-LOGS-01  ENABLED  209530224 0       -        -       -
sd APP-DG02-02  APP-LOGS-01  ENABLED  42128016 209530224 -       -       -

rv APP-RVG      -            ENABLED  -        -        ACTIVE   -       -
rl rlk_192.168.4.6_APP-RVG APP-RVG CONNECT -   -        ACTIVE   -       -
v  APP-DATA     APP-RVG      ENABLED  262144000 -       ACTIVE   -       -
pl APP-DATA-01  APP-DATA     ENABLED  262144000 -       ACTIVE   -       -
sd APP-DG02-01  APP-DATA-01  ENABLED  262144000 0       -        -       -
pl APP-DATA-02  APP-DATA     ENABLED  LOGONLY  -        ACTIVE   -       -
sd APP-DG02-03  APP-DATA-02  ENABLED  512      LOG      -        -       -
v  APP-DATA-SRL APP-RVG      ENABLED  314572800 SRL     ACTIVE   -       -
pl APP-DATA-SRL-01 APP-DATA-SRL ENABLED 314572800 -     ACTIVE   -       -
sd APP-DG01-01  APP-DATA-SRL-01 ENABLED 314572800 0     -        -       -

------x-----x---x

STEPS TO BE PERFORMED

vradmin -g APP-DG APP-NEW-RVG APP-DATA APP-DATA-SRL-NEW

vradmin -g APP-DG addsec APP-NEW-RVG PRIMARY-HOST-IP SECONDARY-HOST-IP prlink=prilink-new srlink=srlink-new

OR

only addsec command need to run ?

[Zahid_Haseeb]

Done Finally.

1- vradmin -g APP-DG addsec APP-RVG 192.168.4.5 192.168.4.7 prlink=PRIMARY-LINK-NEW srlink=SECONDARY-LINK-NEW

2- vxrlink -a -g PHX-DG -r PHX-RVG att PRIMARY-LINK-NEW

3- vradmin -g PHX-DG -a startrep PHX-RVG 192.168.4.7
(Second step may not needed)

(specifing "192.168.4.7" started replication only with New Machine )