Open-E DSS Synchronous Volume Replication With Failover Over a LAN August 2009

7/28/2019 Open-E DSS Synchronous Volume Replication With Failover Over a LAN August 2009

1/52

- -

Synchronous(Block Based)

SupportedbyOpen-EDSS

September 2009DSS ver. 5.00 up62 May26, 2009


2/52

SynchronousVolume Replication with Failoverover a LAN

Replication

ModeSource/Destination Data Transfer Volume Type

nous

nous

em

ed

sed iSCSI

Sync

hro

Async

hr

w/Sys

t

LA

WA

File

ba

Bloc

kb

NA F

C

File-I

O

Bloc

k-I

O

Synchronous Volume Replication with Failover over a LAN

Open-E DSS Synchronous Volume Replication with Failover is a fault tolerance processvia iSCSI volume

, .

Data is copied in real-time, and every change is immediately mirrored from the primary server to the secondary storage

server.In case of a failure, scheduled maintenance of the primary server, or loss of the primary data source, failover automatically

switches operations to the secondary storage server, so processes can be continuedas usual.

2


3/52


VOLUME REPLICATIONWITHFAILOVER BETWEENTWO SYSTEMS WITHIN ONE LAN

Recommended Resources Key Hardware(twosystems)

9 x86 compatible

9 RAID Controller withBatery Backup Unit

9 Network InterfaceCards

9 Ping Node(ping node it is any permanently (24/7) available host in the network. In particular

case the in node function can be

erformed b the server storin the data on the iSCSI

failover volume). Software

9 Open-E DSS, 2 units

Benefits

Eliminate business disruption

Switch Redundancy

Disadvanta es

3

High cost of solution Natural disasters (earthquake, fire, flood...) can destroy local systems


4/52


Data is written and read to System 1 (primary)

Data is continually replicated to System 2 (secondary)

Volume Replication

Heartbeat

RAID System 1

Primary

RAID System 2

Secondary

PING NODE

Write Data

Read Data

Control

4


5/52


In case of raid array ordisk drive error on System 1(primary), the server will send an e-mail notificationto the administrator

iSCSI Auto Failover determines there is no connection between the servers

After a few seconds Automatic Failover is executed and users are switched to System 2(secondary)

Heartbeat

RAID System 1

Primary

RAID System 2

Secondary

PING NODE

Write Data

Read Data

Control

5


6/52


After switching, the replicated volume

is available on System 2 (secondary)

RAID System 1

Primary

RAID System 2

Secondary

PING NODE

Write Data

Read Data

6


7/52


TO SET UP VOLUME REPLICATION WITH FAILOVER, PERFORM THE FOLLOWING STEPS:

1. Hardware configuration:

Settings server names, ethernet ports and bonding on secondary and primary node

2. Configure the Secondary node:

Create a Volume Grou iSCSI Volume

Configure Volume Replication mode (destination mode) settings mirror IP address

3. Configure the Primary node

Create a Volume Group, iSCSI Volume

ConfigureVolumeReplicationmode (source mode) settings mirror IP address, creating Volume Replication

task and start replication task.

. reae new arge on econ ary no e

5. Create new target on Primary node

6. Confi ure virtual IP and Auxiliar connection

7. Configure iSCSI Failover

8. StartFailover Service

7

9. Test Failover Function

10. Run FailbackFunction


8/52


To run the Volume Replication with Failover, two DSS systems

are required. Both servers must be located and working in the

Local AreaNetwork. Seebelowconfigurations for examples: PING NODE

1. Hardware Configuration

Data Server (DSS2)

Secondary node

Data Server (DSS1)

Primary nodeAddress IP:192.168.0.220

Control

ress : . . .

LAN

ress : . . .

RAID System 1

Primary

RAID System 2

Secondary

Switch 1Switch 2

Volume Replication ,

Aux il iary con nect ion (Heartbeat)

IP:192.168.1.220 eth1

Port used for WEB GUI m anagementIP:192.168.0.220 eth0

Optional:

This path can be

directl oint-to- oint

Port used for WEB GUI m anagementeth0 IP:192.168.0.221

Volume Replication ,

Aux il iary con nect ion (Heartbeat)

Client Storage Access,

Aux ili ary c onn ecti on (Heartbeat)

bond0 IP:192.168.2.220 (eth2, eth3)

connectedeth1 toeth1

(without theswitch).

Bondin IP

Client Storage Access,

Auxil iary con nect ion (Heartbeat )

(eth2, eth3) IP:192.168.2.221 bond0

. . .

Volume Groups (vg00)o ume roups vg

iSCSI Failover/Volume Replication (eth1)iSCSI volume (lv00) iSCSI volume (lv00)

Virtual AddressIP:192.168.10.230 (iSCSITarget)

8

iSCSI targets

iSCSI targets


9/52


1. Hardware ConfigurationData Server (DSS2)Secondary nodeAddress IP:192.168.0.221

After logging on the DSS

pleasego to SETUP tab,

ne wor an n er aces . n

Server name function enter

Server name, in this example

dss2 and click apply button.

connec on w e

restarted)

9


10/52



Next select eth0 interface and

change address IP from

192.168.0.220 in field IP address

to 192.168 .0.221, andclickapply

button. (This will restart network

configuration).

10


11/52



Next select eth1 interface and

change IP address from

192.168.1.220 in field IP address

to 192.168.1.221and clickapply

button.

11


12/52



Again select Interfaces and inCreate new bond interface

function check two boxes witheth2

andeth3. In fieldCreate select

bonding mode. In this example

select New balance-rr.

Next enter address IP in fieldIP

address 192.168 .2.221, Netmask,

12

.


13/52



After reloading page on the dss2

server ou have confi uredbond0.

Setting of the network interfaces onthe secondary node is finished.

13


14/52


1. Hardware ConfigurationData Server (DSS1)Primary nodeAddress IP:192.168.0.220

After logging on theprimary

nodepleasego to SETUPa , ne wor an

Interfaces. In Server name

function enter Server name. In

this example enterdss1 and

c c app y u on.

connection will be restarted).

14


15/52



Againselect Interfaces and inCreate new bond interface

function check two boxes witheth2

andeth3. In fieldCreate select

mode for bonding. In this example

selected New balance-rr..

Next enter address IP in fieldIP

address 192.168.2.220, Netmask,

15

.


16/52



After reloading page on thedss1

server you have configured

bond0. Setting of the network

interfaces on the secondary node is

finished.

16


17/52


2. Configure the Secondary nodeData Server (DSS2)Secondary nodeAddress IP:192.168.0.221

Under the CONFIGURATION

tab, select volume manager

and next Vol. Groups.

Volume Groups (vg00)

InUnit managerfunction add

the selected physical units

(Unit S000 or other) to create a

new volume group (in this case,vg00) and click apply button

17


18/52


Data Server (DSS2)Secondary node

Address IP:192.168.0.2212. Configure the Secondary node

Select the appropriate volume

group (vg00) from the list on

the left and create anew iSCSI

volume of the required size.

This logical volume will be the

destination of the replication

process.

Next check the box withUse

volume replication

After assigning an appropriate

amount of space for the iSCSI

18

,


19/52




The destination iSCSI Volume

.

iSCSI volume (lv0000)

19


20/52




Now, select theVol. replication

and check the box under

Destination and click theapply

button

Next, underMirror Server IPfunction, enter the IP address of

the Primary node (in our

exampe, s wou e

192.168.1.220) and click the

apply button

NOTE:The Mirror server IPAddressmustbeon thesame

subnet in order for the replicationto communicate.

VPN connections can work rovidin ou are not

20

usingaNAT. Pleasefollowexample:

Source: 192.168.1.220Destination: 192.168.1.221


21/52


Data Server (DSS1)Primarynode

Address IP:192.168.0.2203. Configure the Primary node

Under the CONFIGURATION

tab, select volume manager

and next Vol. Groups

Add the selected physical units

(Unit MD0 or other) to create a

new volume group (in this case,

vg00) and click apply button

21


22/52


Data Server (DSS1)Primary node


Select the appropriate volume

the left and create anew iSCSI

volume of the required size.

This logical volume will be the

process

ex , c ec ox se vo ume

replication

After assigning an appropriate

amount of space for the iSCSI

volume, click theapply button

22

NOTE:The source and destination volumes must be of identical size.


23/52




The destination iSCSI Volume

Block I/O is now confi ured.

iSCSI volume (lv0000)

23


24/52




Now, select Vol. replication,

and check the box under

Source and click theapply

button

Next , underMirror Server IP

function, enter the IP address ofe econ ary no e n our

example this would be

192.168.1.221) andclick the

apply button

24


25/52


Data Server (DSS1)

Primary node


Enter the task name in field

Task name next click on thebutton

In theDestination volume

field select the appropriate

volume (in this example,

lv0000) and clickcreate to

25

confirm.


26/52


Data Server (DSS1)

Primary node


Now, in theReplication task

manager function, clickon

buttonunder to start the

Re lication task on the Primarnode

26


27/52


Data Server (DSS1)

Primary node


In theReplication tasks

manager function information

is available about the current

running replication task.

27


28/52


Data Server (DSS1)

Primary node


Under the STATUS tab,

Replication

Click on the button with

Mirror_00) to display detailed

information on the current

replication task

NOTE:

28

similar to abovewith status being Consistent

beforewritingto theiSCSI LogicalVolume.


29/52


Data Server (DSS2)

Secondary node

Address IP:192.168.0.2214. Create new target on the Secondary node

,

iSCSI target manager and

Targets from the menu

In theCreate new target

function, uncheck the box

Target Default Name, and

enter a name for the new tar et

in the Name field and click

apply to confirm

iSCSI targets

29

NOTE:Both systemsmust havethesame Target name.


30/52


Data Server (DSS2)

Secondary node

Address IP:192.168.0.2214. Create new target on the Secondary node

Select target0 within the

Targets field.

To assign a volume to the

target, click the button

.

NOTE:Bothsystems must have thesame SCSI ID and LUN#

30

WARNING:

Please do not switch on the write back (WB)cache !


31/52


Data Server (DSS1)

Primary node

Address IP:192.168.0.2205. Create new target on the Primary node

oose

and iSCSI target manager

and Targets from the menu

In theCreate new targetfunction, uncheck the box

Target Default Name, and

ener a name or e new arge

in theName field and click

apply to confirm

iSCSI targets

31

NOTE:

Both systemsmust havethesame Target name.


32/52


Data Server (DSS1)

Primary node

Address IP:192.168.0.2205. Createnewtarget on thePrimarynode

Select the target0 within the

Targets field

To assign a volume to the

arge , c c e u on

located underAction.

32

WARNING:

Please do not switch on the write back cache(WB)!


33/52


Data Server (DSS1)

Primary node

Address IP:192.168.0.2206. Configure Virtual IP and Auxillary connection

Now, select the bond0 within

iSCSI Failover.

In theVirtual IP Settingsfunction check box Enable

virtual IP andenterIP

address, Netmask,

Broadcast, and click theapply

button.

In theAuxi liary connect ion

function check boxUse this

network interface to

communicate between the

nodes and click theapply

button.

NOTE:There need to be at least two auxiliary connections. The

interface with the virtual IP can also serve as one of the

auxiliary connections. Please set the Virtual IP Address in

33

a eren newor su ne en ep ysca ress. o

haveadditional iSCSIFailover systems,pleaseset thispair

in a different network subnet fromthe other iSCSI Failoversystems.Thislimitationwill beremovedin thefuture.


34/52


Data Server (DSS1)

Primary node


Now, select theeth1 within

iSCSI Failover.


network interface to


button.

34


35/52


Data Server (DSS2)

Secondary node


Choose, SETUP and

network and Interface

Now, select the bond0 within

iSCSI Failover.

In theVirtual IP Settin s

functioncheckthe boxEnable

virtual IP andenterIPaddress, Netmask,

Broadcast, and click theapply

button.

In theAuxi liary connect ion

function check boxUse thisnetwork interface to



button.

35


36/52


Data Server (DSS2)

Secondary nodeAddress IP:192.168.0.221

6. Configure Virtual IP and Auxillary connection

Now, select the eth1 within

iSCSI Failover.

In theAuxi liary connection


network interface tocommunicate between the


button.

36


37/52


Data Server (DSS1)

PrimarynodeAddress IP:192.168.0.220


Now, select iSCSI Failover

In theFailover configurationfunction, check the boxEnable

iSCSI failover functionality

andenter the Secondary node

IP address and thePing Node

37

IP and click theapply button

S h V l R li ti ith F il LAN


38/52


Data Server (DSS2)

SecondarynodeAddress IP:192.168.0.221


Now, select iSCSI Failover

Now, in Failoverconfiguration function , check

the boxEnable iSCSI failover

functionality andenter Primary

node IP addressand click the

38

apply button



39/52


Data Server (DSS1)



used for the failover service to

theFailover Tasks area by

clicking button

39



40/52


Data Server (DSS1)


8. Start Failover Service

s pon o no es are

ready to start the Failover

service

40

SynchronousVolume Replication with Failover over aLAN


41/52


Data Server (DSS1)



After clicking thestart button

configurationof bothnodes will

be complete

NOTE:You can now connect via your iSCSI initiator and use

41

. .

192.168.10.230 (For example, in a Microsoft Windows

environment, download Microsoft iSCSI Initiator ver 2.0or later).



42/52


Data Server (DSS1)



After start Failover, check the

status in Failover statusfunction. All must read OK. In

the task status, the destination

volume must be consistent

42



43/52


Data Server (DSS1)



In order to test Failover in

Manual Failover function, click

on theManual failoverbutton

43



44/52


Data Server (DSS1)



failoverbutton, primary node

enters suspend mode

44



45/52


Data Server (DSS1)



TheFailover status function

shows theGlobal status of the

prmary no e. aus servce s

insuspend mode and the nodeis inactive.

45



46/52


Data Server (DSS2)

SecondarynodeAddress IP:192.168.0.221 9. Test Failover Function

InFailover status function

Global status shows the status

o e secon ary no e. e

service status isdegraded andNodestatus isactive.

46



47/52


Data Server (DSS2)

SecondarynodeAddress IP:192.168.0.221 10. Run FailbackFunction

In order to runFailback in

Failover managerfunction

click on theSync volumes

buttonfirst.

47



48/52


Data Server (DSS2)


After synchronization the task

s aus o e es na on voume

must beConsistent

48



49/52


Data Server (DSS2)


In order to return the active

server state to the Primary

server click on theFailback

49



50/52


Data Server (DSS1)

Primary nodeAddress IP:192.168.0.220 10. Run FailbackFunction

After clicking onFailback

button (inFailover manager

function on Secondary node)

.

50



51/52

y p

Data Server (DSS1)

Primary nodeAddress IP:192.168.0.220 10. Run FailbackFunction

Primary node is active again

and ready for Failover.

iSCSI Failover/Volume Replication

The configuration and testingof

iSCSI Failover/Failbackis now

51

complete.


52/52

Thank You!

52

Documents

Open-E DSS Synchronous Volume Replication With Failover Over a LAN August 2009