SlideShare ist ein Scribd-Unternehmen logo
1 von 36
Downloaden Sie, um offline zu lesen
Step-by-Step Guide
to
Open-E DSS V7 Active-Passive iSCSI Failover
Software Version: DSS ver. 7.00 up10

Presentation updated: June 2013

www.open-e.com

1
Open-E DSS V7 Active-Passive iSCSI Failover

TO SET UP ACTIVE-PASSIVE ISCSI FAILOVER, PERFORM THE
FOLLOWING STEPS:
1.

Hardware configuration

2.

Network Configuration:
• Set server hostnames and Ethernet ports on both nodes (node-a, node-b)

3.

Configure the node-b:
• Create a Volume Group, iSCSI Volume
• Configure Volume Replication mode (destination and source mode) – define remote mode of binding, create Volume Replication
task and start the replication task

4.

Configure the node-a:
• Create a Volume Group, iSCSI Volume
• Configure Volume Replication mode (source and destination mode), create Volume Replication task and start the replication
task.

5.

Create targets (node-a and node-b)

6.

Configure Failover (node-a and node-b)

7.

Start Failover Service

8.

Test Failover Function

9.

Run Failback Function
www.open-e.com

2
Open-E DSS V7 Active-Passive iSCSI Failover
Storage client

IP:192.168.20.101 (MPIO 1)
IP:192.168.1.107 (Ping Node)

eth1

IP:192.168.21.101 (MPIO 2)
IP:192.168.2.107 (Ping Node)

1. Hardware Configuration

eth0

eth2

LAN

IP:192.168.0.101

Data Server (DSS1)

Data Server (DSS2)

node-a

Switch 1

IP Address:192.168.0.220

node-b

Switch 2

IP Address:192.168.0.221
RAID System 2

RAID System 1
Port used for WEB GUI management
IP:192.168.0.220

Port used for WEB GUI management

eth0

eth0

Storage Client Access, Multipath
Auxiliary connection (Heartbeat)
IP:192.168.1.220

Storage Client Access, Multipath
Auxiliary connection (Heartbeat)

eth1

Virtual IP Address:
192.168.20.100 (iSCSI Target)

Storage Client Access, Multipath
Auxiliary connection (Heartbeat)
IP:192.168.2.220

eth2
Virtual IP Address:
192.168.21.100 (iSCSI Target)

Volume Replication,
Auxilliary connection (Heartbeat)
IP:192.168.3.220
Volume Groups (vg00)
iSCSI volumes (lv0000)
iSCSI targets

eth3

IP:192.168.0.221

Note:
It is strongly recommended to use direct point-to-point and if possible 10GbE
connection for the volume replication. Optionally Round-Robin-Bonding with 1GbE
or 10GbE ports can be configured for the volume replication. The volume
replication connection can work over the switch, but the most reliable is a direct
connection.

iSCSI Failover/Volume Replication (eth3)

eth1

IP:192.168.1.221
Storage Client Access, Multipath,
Auxiliary connection (Heartbeat)

eth2

IP:192.168.2.221
Volume Replication ,
Auxilliary connection (Heartbeat)

eth3

IP:192.168.3.221
Volume Groups (vg00)
iSCSI volumes (lv0000)

iSCSI targets

NOTE:
For additional layer of redundancy, you may add an extra connection between switches and ping nodes.

www.open-e.com

3
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS2)

node-b

1. Hardware Configuration

IP Address:192.168.0.221

After logging on to the
Open-E DSS V7 (node-b), please
go to SETUP and choose the
"Network interfaces" option.
In the Hostname box, replace the
"dss" letters in front of the numbers
with "node-b" server, in this
example "node-b-59979144" and
click the apply button (this will
require a reboot).

www.open-e.com

4
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS2)

node-b

1. Hardware Configuration

IP Address:192.168.0.221

Next, select eth0 interface and in
the IP address field, change the IP
address from 192.168.0.220 to
192.168.0.221
Then click apply (this will restart
network configuration).

www.open-e.com

5
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS2)

node-b

1. Hardware Configuration

IP Address:192.168.0.221

Afterwards, select eth1 interface
and change the IP address from
192.168.1.220 to 192.168.1.221 in
the IP address field and click the
apply button.
Next, change the IP addresses in
eth2 and eth3 interfaces
accordingly.

www.open-e.com

6
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

1. Hardware Configuration

IP Address:192.168.0.220

After logging in to node-a, please
go to SETUP and choose the
"Network interfaces" option.
In the Hostname box, replace the
"dss" letters in front of the numbers
with "node-a" server, in this
example "node-a-39166501" and
click apply (this will require a
reboot).

www.open-e.com

7
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS2)

node-b

2. Configure the node-b

IP Address:192.168.0.221

In CONFIGURATION, select
"Volume manager", then click on
"Volume groups".

In the Unit manager function
menu, add the selected physical
units (Unit MD0 or other) to create
a new volume group (in this case,
vg00) and click the apply button.

www.open-e.com

8
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS2)

node-b

2. Configure the node-b

IP Address:192.168.0.221

Select the appropriate volume
group (vg00) from the list on the
left and create a new iSCSI
volume of the required size.
The logical volume (lv0000) will be
the destination of the replication
process on node-b.

Next, check "Use volume
replication" checkbox.

After assigning an appropriate
amount of space for the iSCSI
volume, click the apply button.

www.open-e.com

9
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS2)

node-b

2. Configure the node-b

IP Address:192.168.0.221

Logical iSCSI Volume Block I/O is
now configured.

iSCSI volume (lv0000)

www.open-e.com

10
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

3. Configure the node-a

IP Address:192.168.0.220

Go to the node-a system. In
CONFIGURATION, select
"Volume manager" and then click
on "Volume groups".

Add the selected physical units
(Unit S001 or other) to create a
new volume group (in this case,
vg00) and click apply button.

Volume Groups (vg00)

www.open-e.com

11
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

3. Configure the node-a

IP Address:192.168.0.220

Select the appropriate volume
group (vg00) from the list on the
left and create a new iSCSI
volume of the required size.
The logical volume (lv0000) will be
a source of the replication process
on the node-a.

Next, check the box for "Use
volume replication"
After assigning an appropriate
amount of space for the iSCSI
volume, click the apply button
NOTE:
The source and destination volumes must be of
identical size.

www.open-e.com

12
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

3. Configure the node-a

IP Address:192.168.0.220

Logical iSCSI Volume Block I/O is
now configured.

iSCSI volume (lv0000)

www.open-e.com

13
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS2)

node-b

2. Configure the node-b

IP Address:192.168.0.221

Now, on the node-b, go to
"Volume replication".
Within Volume replication mode
function, check "Destination"
checkbox for lv0000.
Then, click the apply button.
In the Hosts Binding function,
enter the IP address of node-a (in
our example, this would be
192.168.3.220), enter node-a
administrator password and click
the apply button.
After applying all the changes, the
status should be: Reachable.
NOTE:
The Mirror server IP Address must be on the same
subnet in order for the replication to communicate.
VPN connections can work providing you are not
using a NAT. Please follow example:
• Source:
192.168.3.220
• Destination: 192.168.3.221

www.open-e.com

14
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

3. Configure the node-a

IP Address:192.168.0.220

In the Create new volume
replication task, enter the task
name in the Task name field, then
click on the
button.
In the Destination volume field,
select the appropriate volume (in
this example, lv0000).
In the Bandwidth for SyncSource
(MB) field you must change the
value. In the example, 35MB is
used. Next, click the create button.
NOTE:
The “Bandwidth for SyncSource (MB)” need to be
calculated based on available Ethernet Network
throughput and number of replication tasks and the
limitation factor (about 0.7).
For example: 1 Gbit Ethernet and 2 replication tasks
(assuming 1 Gbit provides about 100 MB/sec sustained
network throughput)
• Bandwidth for SyncSource (MB): = 0.7 * 100/ 2 = 35
For example: 10 Gbit Ethernet and 10 replication tasks
(assuming 10 Gbit provides about 700 MB/sec sustained
network throughput)
• Bandwidth for SyncSource (MB): = 0.7 * 700/10 = 49

www.open-e.com

15
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

3. Configure the node-a

IP Address:192.168.0.220

Now, in the Replication task
manager function, click the
corresponding "play" button to start
the Replication task on the node-a.

www.open-e.com

16
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

3. Configure the node-a

IP Address:192.168.0.220

You may view information about
currently running replication tasks
in the Replication tasks manager
function window.
When a task is started, a date and
time will appear.

www.open-e.com

17
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

3. Configure the node-a

IP Address:192.168.0.220

You can check the status of
Volume Replication anytime in
STATUS → "Tasks" → "Volume
Replication" menu.

Click on the
button, located
next to a task name (in this case
MirrorTask-a) to display detailed
information about the current
replication task.

NOTE:
Please allow the replication task to complete
(similar to above with status being ”Consistent”)
before writing to the iSCSI Logical Volume.

www.open-e.com

18
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS2)

node-b

4. Create new target on the node-b

IP Address:192.168.0.221

Choose CONFIGURATION, "iSCSI
target manager" and "Targets"
from the top menu.

In the "Create new target"
function, uncheck the box Target
Default Name.
In the Name field, enter a name for
the new target and click apply to
confirm.

iSCSI targets

NOTE:
Both systems must have the same Target name.

www.open-e.com

19
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS2)

node-b

4. Create new target on the node-b

IP Address:192.168.0.221

After that, select target0 from the
Targets field.

To assign appropriate volume to
the target (iqn.2013-06:mirror-0
→ lv0000) click attach button
located under Action.

NOTE:
Volumes on both sides must have the same SCSI ID and
LUN# for example: lv0000 SCSI ID on node-a = lv0000
SCSI ID on node-b.
In this case before clicking the attach button please
copy the SCSI ID and LUN# from this node.

www.open-e.com

20
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

5. Create new target on the node-a

IP Address:192.168.0.220

Next, go to node-a, click on
CONFIGURATION and choose
"iSCSI target manager" →
"Targets" from the menu.

In the "Create new target"
function, uncheck the box Target
Default Name.
In the Name field, enter a name for
the new target and click apply to
confirm.

iSCSI targets

NOTE:
Both systems must have the same Target name.

www.open-e.com

21
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

5. Create new target on the node-a

IP Address:192.168.0.220

After that, select target0 from the
Targets field.

To assign appropriate volume to
the target (iqn.2013-06:mirror-0
→ lv0000) click attach button
located under Action.

NOTE:
Before clicking the attach button again, please
paste the SCSI ID and LUN# (previously copied)
from the node-b.

www.open-e.com

22
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

6. Configure Failover

IP Address:192.168.0.220

On the node-a go to Setup and
select „Failover”

In the "Auxiliary paths" function,
select the 1st New auxiliary path
on the local and remote node and
click the add new auxiliary path
button.

www.open-e.com

23
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

6. Configure Failover

IP Address:192.168.0.220

In the Auxiliary paths function,
select the 2nd New auxiliary path
on the local and remote node and
click the add new auxiliary path
button.

www.open-e.com

24
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

6. Configure Failover

IP Address:192.168.0.220

In the "Ping nodes" function,
enter two ping nodes.
In the IP address field enter IP
address and click the add new
ping node button (according to the
configuration in the third slide).
In this example, IP address of the
first ping node is: 192.168.1.107
and the second ping node:
192.168.2.107

www.open-e.com

25
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

6. Configure Failover

IP Address:192.168.0.220

Next, go to the Resources Pool
Manager function (on node-a
resources) and click the add
virtual IP button. After that, enter
1st Virtual IP, (in this example
192.168.20.100 according to the
configuration in the third slide) and
select two appropriate interfaces
on local and remote nodes. Then,
click the add button.

www.open-e.com

26
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

6. Configure Failover

IP Address:192.168.0.220

Now, still on node-a resources
(local node) enter the next Virtual
IP address. Click add virtual IP
enter 2nd Virtual IP, (in this
example 192.168.21.100), and
select two appropriate interfaces
on the local and remote nodes.
Then, click the add button.

www.open-e.com

27
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

6. Configure Failover

IP Address:192.168.0.220

Now you have 2 Virtual IP
addresses configured on two
interfaces.

www.open-e.com

28
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

6. Configure Failover

IP Address:192.168.0.220

When you are finished with setting
the virtual IP, go to the "iSCSI
resources" tab on the local node
resources and click the add or
remove targets button.
After moving the target mirror-0
from "Available targets" to
"Targets already in cluster" click
the apply button.

www.open-e.com

29
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

6. Configure Failover

IP Address:192.168.0.220

After that, scroll to the top of the
Failover manager function.
At this point, both nodes are ready
to start the Failover.
In order to run the Failover service,
click the start button and confirm
this action by clicking the start
button again.

NOTE:
If the start button is grayed out, the setup has not been
completed.

www.open-e.com

30
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

7. Start Failover Service

IP Address:192.168.0.220

After clicking the start button,
configuration of both nodes is
complete.

NOTE:
You can now connect with iSCSI Initiators. The storage
client, in order to connect to target0 please setup
multipath with following IP on the initiator side:
192.168.20.100 and 192.168.21.100.

www.open-e.com

31
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

8. Test Failover Function

IP Address:192.168.0.220

In order to test Failover,
go to the Resources pool
manager function.
Then, in the local node resources,
click on the move to remote node
button and confirm this action by
clicking the move button.

www.open-e.com

32
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

8. Test Failover Function

IP Address:192.168.0.220

After performing this step, the
status for local node resources
should state "active on node-b
(remote node)" and the
Synchronization status should
state "synced".

www.open-e.com

33
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

9. Run Failback Function

IP Address:192.168.0.220

In order to test failback, click the
move to local node button in the
Resources pool manager box for
local node resources and confirm
this action by clicking the move
button.

www.open-e.com

34
Open-E DSS V7 Active-Passive iSCSI Failover
Data Server (DSS1)

node-a

9. Run Failback Function

IP Address:192.168.0.220

After completing this step the
status for node-a resources should
state "active on node-a" (local
node) and the Synchronization
status should state: synced.

NOTE:
The Active-Passive option allows configuring a
resource pool only on one of the nodes. In such a
case, all volumes are active on a single node only.
The Active-Active option allows configuring resource
pools on both nodes and makes it possible to run
some active volumes on node-a and other active
volumes on node-b. The Active-Active option is
enabled with the TRIAL mode for 60 days or when
purchasing the Active-Active Failover Feature Pack.

The configuration and testing of
Active-Passive iSCSI Failover
is now complete.
www.open-e.com

35
Thank you!

Follow Open-E:
www.open-e.com

36

Weitere ähnliche Inhalte

Was ist angesagt?

Tutorial on using CoreOS Flannel for Docker networking
Tutorial on using CoreOS Flannel for Docker networkingTutorial on using CoreOS Flannel for Docker networking
Tutorial on using CoreOS Flannel for Docker networkingLorisPack Project
 
Understanding docker networking
Understanding docker networkingUnderstanding docker networking
Understanding docker networkingLorenzo Fontana
 
Open Source Backup Cpnference 2014: Bareos in scientific environments, by Dr....
Open Source Backup Cpnference 2014: Bareos in scientific environments, by Dr....Open Source Backup Cpnference 2014: Bareos in scientific environments, by Dr....
Open Source Backup Cpnference 2014: Bareos in scientific environments, by Dr....NETWAYS
 
Known basic of NFV Features
Known basic of NFV FeaturesKnown basic of NFV Features
Known basic of NFV FeaturesRaul Leite
 
VyOS Users Meeting #2, VyOSのVXLANの話
VyOS Users Meeting #2, VyOSのVXLANの話VyOS Users Meeting #2, VyOSのVXLANの話
VyOS Users Meeting #2, VyOSのVXLANの話upaa
 
Building a Virtualized Continuum with Intel(r) Clear Containers
Building a Virtualized Continuum with Intel(r) Clear ContainersBuilding a Virtualized Continuum with Intel(r) Clear Containers
Building a Virtualized Continuum with Intel(r) Clear ContainersMichelle Holley
 
Web scale infrastructures with kubernetes and flannel
Web scale infrastructures with kubernetes and flannelWeb scale infrastructures with kubernetes and flannel
Web scale infrastructures with kubernetes and flannelpurpleocean
 
02 install cluster using npaci rocks
02 install cluster using npaci rocks02 install cluster using npaci rocks
02 install cluster using npaci rocksEni Budiyarti
 
Hadoop Cluster - Basic OS Setup Insights
Hadoop Cluster - Basic OS Setup InsightsHadoop Cluster - Basic OS Setup Insights
Hadoop Cluster - Basic OS Setup InsightsSruthi Kumar Annamnidu
 
Docker Setting for Static IP allocation
Docker Setting for Static IP allocationDocker Setting for Static IP allocation
Docker Setting for Static IP allocationJi-Woong Choi
 
Docker Container: isolation and security
Docker Container: isolation and securityDocker Container: isolation and security
Docker Container: isolation and security宇 傅
 
Accelerating Neutron with Intel DPDK
Accelerating Neutron with Intel DPDKAccelerating Neutron with Intel DPDK
Accelerating Neutron with Intel DPDKAlexander Shalimov
 
Seamless migration from nova network to neutron in e bay production
Seamless migration from nova network to neutron in e bay productionSeamless migration from nova network to neutron in e bay production
Seamless migration from nova network to neutron in e bay productionChengyuan Li
 
Openstack Testbed_ovs_virtualbox_devstack_single node
Openstack Testbed_ovs_virtualbox_devstack_single nodeOpenstack Testbed_ovs_virtualbox_devstack_single node
Openstack Testbed_ovs_virtualbox_devstack_single nodeYongyoon Shin
 
Open Source Backup Conference 2014: Workshop bareos introduction, by Philipp ...
Open Source Backup Conference 2014: Workshop bareos introduction, by Philipp ...Open Source Backup Conference 2014: Workshop bareos introduction, by Philipp ...
Open Source Backup Conference 2014: Workshop bareos introduction, by Philipp ...NETWAYS
 
Raid designs in Qsan Storage
Raid designs in Qsan StorageRaid designs in Qsan Storage
Raid designs in Qsan Storageqsantechnology
 
Docker Meetup: Docker Networking 1.11, by Madhu Venugopal
Docker Meetup: Docker Networking 1.11, by Madhu VenugopalDocker Meetup: Docker Networking 1.11, by Madhu Venugopal
Docker Meetup: Docker Networking 1.11, by Madhu VenugopalMichelle Antebi
 
High Performance Linux Virtual Machine on Microsoft Azure: SR-IOV Networking ...
High Performance Linux Virtual Machine on Microsoft Azure: SR-IOV Networking ...High Performance Linux Virtual Machine on Microsoft Azure: SR-IOV Networking ...
High Performance Linux Virtual Machine on Microsoft Azure: SR-IOV Networking ...LinuxCon ContainerCon CloudOpen China
 
[네이버오픈소스세미나] Maglev Hashing Scheduler in IPVS, Linux Kernel - 송인주
[네이버오픈소스세미나] Maglev Hashing Scheduler in IPVS, Linux Kernel - 송인주[네이버오픈소스세미나] Maglev Hashing Scheduler in IPVS, Linux Kernel - 송인주
[네이버오픈소스세미나] Maglev Hashing Scheduler in IPVS, Linux Kernel - 송인주NAVER Engineering
 

Was ist angesagt? (20)

Tutorial on using CoreOS Flannel for Docker networking
Tutorial on using CoreOS Flannel for Docker networkingTutorial on using CoreOS Flannel for Docker networking
Tutorial on using CoreOS Flannel for Docker networking
 
Understanding docker networking
Understanding docker networkingUnderstanding docker networking
Understanding docker networking
 
Open Source Backup Cpnference 2014: Bareos in scientific environments, by Dr....
Open Source Backup Cpnference 2014: Bareos in scientific environments, by Dr....Open Source Backup Cpnference 2014: Bareos in scientific environments, by Dr....
Open Source Backup Cpnference 2014: Bareos in scientific environments, by Dr....
 
Known basic of NFV Features
Known basic of NFV FeaturesKnown basic of NFV Features
Known basic of NFV Features
 
VyOS Users Meeting #2, VyOSのVXLANの話
VyOS Users Meeting #2, VyOSのVXLANの話VyOS Users Meeting #2, VyOSのVXLANの話
VyOS Users Meeting #2, VyOSのVXLANの話
 
Building a Virtualized Continuum with Intel(r) Clear Containers
Building a Virtualized Continuum with Intel(r) Clear ContainersBuilding a Virtualized Continuum with Intel(r) Clear Containers
Building a Virtualized Continuum with Intel(r) Clear Containers
 
Web scale infrastructures with kubernetes and flannel
Web scale infrastructures with kubernetes and flannelWeb scale infrastructures with kubernetes and flannel
Web scale infrastructures with kubernetes and flannel
 
02 install cluster using npaci rocks
02 install cluster using npaci rocks02 install cluster using npaci rocks
02 install cluster using npaci rocks
 
Hadoop Cluster - Basic OS Setup Insights
Hadoop Cluster - Basic OS Setup InsightsHadoop Cluster - Basic OS Setup Insights
Hadoop Cluster - Basic OS Setup Insights
 
Docker Setting for Static IP allocation
Docker Setting for Static IP allocationDocker Setting for Static IP allocation
Docker Setting for Static IP allocation
 
Docker Container: isolation and security
Docker Container: isolation and securityDocker Container: isolation and security
Docker Container: isolation and security
 
Accelerating Neutron with Intel DPDK
Accelerating Neutron with Intel DPDKAccelerating Neutron with Intel DPDK
Accelerating Neutron with Intel DPDK
 
Seamless migration from nova network to neutron in e bay production
Seamless migration from nova network to neutron in e bay productionSeamless migration from nova network to neutron in e bay production
Seamless migration from nova network to neutron in e bay production
 
Openstack Testbed_ovs_virtualbox_devstack_single node
Openstack Testbed_ovs_virtualbox_devstack_single nodeOpenstack Testbed_ovs_virtualbox_devstack_single node
Openstack Testbed_ovs_virtualbox_devstack_single node
 
OVS v OVS-DPDK
OVS v OVS-DPDKOVS v OVS-DPDK
OVS v OVS-DPDK
 
Open Source Backup Conference 2014: Workshop bareos introduction, by Philipp ...
Open Source Backup Conference 2014: Workshop bareos introduction, by Philipp ...Open Source Backup Conference 2014: Workshop bareos introduction, by Philipp ...
Open Source Backup Conference 2014: Workshop bareos introduction, by Philipp ...
 
Raid designs in Qsan Storage
Raid designs in Qsan StorageRaid designs in Qsan Storage
Raid designs in Qsan Storage
 
Docker Meetup: Docker Networking 1.11, by Madhu Venugopal
Docker Meetup: Docker Networking 1.11, by Madhu VenugopalDocker Meetup: Docker Networking 1.11, by Madhu Venugopal
Docker Meetup: Docker Networking 1.11, by Madhu Venugopal
 
High Performance Linux Virtual Machine on Microsoft Azure: SR-IOV Networking ...
High Performance Linux Virtual Machine on Microsoft Azure: SR-IOV Networking ...High Performance Linux Virtual Machine on Microsoft Azure: SR-IOV Networking ...
High Performance Linux Virtual Machine on Microsoft Azure: SR-IOV Networking ...
 
[네이버오픈소스세미나] Maglev Hashing Scheduler in IPVS, Linux Kernel - 송인주
[네이버오픈소스세미나] Maglev Hashing Scheduler in IPVS, Linux Kernel - 송인주[네이버오픈소스세미나] Maglev Hashing Scheduler in IPVS, Linux Kernel - 송인주
[네이버오픈소스세미나] Maglev Hashing Scheduler in IPVS, Linux Kernel - 송인주
 

Andere mochten auch

Open-E DSS V7 Asynchronous Data Replication within a System
Open-E DSS V7 Asynchronous Data Replication within a SystemOpen-E DSS V7 Asynchronous Data Replication within a System
Open-E DSS V7 Asynchronous Data Replication within a Systemopen-e
 
Open-E DSS V7 Synchronous Volume Replication over a LAN
Open-E DSS V7 Synchronous Volume Replication over a LANOpen-E DSS V7 Synchronous Volume Replication over a LAN
Open-E DSS V7 Synchronous Volume Replication over a LANopen-e
 
Open-E DSS V7 Asynchronous Data Replication over a LAN
Open-E DSS V7 Asynchronous Data Replication over a LANOpen-E DSS V7 Asynchronous Data Replication over a LAN
Open-E DSS V7 Asynchronous Data Replication over a LANopen-e
 
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding)Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding)open-e
 
StarWind Virtual SAN Overview
StarWind Virtual SAN OverviewStarWind Virtual SAN Overview
StarWind Virtual SAN OverviewStarWind Software
 

Andere mochten auch (6)

Open-E DSS V7 Asynchronous Data Replication within a System
Open-E DSS V7 Asynchronous Data Replication within a SystemOpen-E DSS V7 Asynchronous Data Replication within a System
Open-E DSS V7 Asynchronous Data Replication within a System
 
Open-E DSS V7 Synchronous Volume Replication over a LAN
Open-E DSS V7 Synchronous Volume Replication over a LANOpen-E DSS V7 Synchronous Volume Replication over a LAN
Open-E DSS V7 Synchronous Volume Replication over a LAN
 
Open-E DSS V7 Asynchronous Data Replication over a LAN
Open-E DSS V7 Asynchronous Data Replication over a LANOpen-E DSS V7 Asynchronous Data Replication over a LAN
Open-E DSS V7 Asynchronous Data Replication over a LAN
 
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding)Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (with bonding)
 
StarWind_V_SAN_product_presentation
StarWind_V_SAN_product_presentationStarWind_V_SAN_product_presentation
StarWind_V_SAN_product_presentation
 
StarWind Virtual SAN Overview
StarWind Virtual SAN OverviewStarWind Virtual SAN Overview
StarWind Virtual SAN Overview
 

Ähnlich wie Open-E DSS V7 Active-Passive iSCSI Failover

Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server SystemsOpen-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systemsopen-e
 
Open-E Backup to iSCSI Target Volume over a LAN
Open-E Backup to iSCSI Target Volume over a LANOpen-E Backup to iSCSI Target Volume over a LAN
Open-E Backup to iSCSI Target Volume over a LANopen-e
 
Open-E DSS V7 Asynchronous Data Replication over a WAN
Open-E DSS V7 Asynchronous Data Replication over a WANOpen-E DSS V7 Asynchronous Data Replication over a WAN
Open-E DSS V7 Asynchronous Data Replication over a WANopen-e
 
Open-E DSS V6 MPIO with ESXi 4.x
Open-E DSS V6 MPIO with ESXi 4.xOpen-E DSS V6 MPIO with ESXi 4.x
Open-E DSS V6 MPIO with ESXi 4.xopen-e
 
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft WindowsHow to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windowsopen-e
 
Automating auto-scaled load balancer based on linux and vm orchestrator
Automating auto-scaled load balancer based on linux and vm orchestratorAutomating auto-scaled load balancer based on linux and vm orchestrator
Automating auto-scaled load balancer based on linux and vm orchestratorAndrew Yongjoon Kong
 
Network Automation Tools
Network Automation ToolsNetwork Automation Tools
Network Automation ToolsEdwin Beekman
 
Open-E Backup to Attached Tape Drive
Open-E Backup to Attached Tape DriveOpen-E Backup to Attached Tape Drive
Open-E Backup to Attached Tape Driveopen-e
 
The Basic Introduction of Open vSwitch
The Basic Introduction of Open vSwitchThe Basic Introduction of Open vSwitch
The Basic Introduction of Open vSwitchTe-Yen Liu
 
Ato2019 weave-services-istio
Ato2019 weave-services-istioAto2019 weave-services-istio
Ato2019 weave-services-istioLin Sun
 
Weave Your Microservices with Istio
Weave Your Microservices with IstioWeave Your Microservices with Istio
Weave Your Microservices with IstioAll Things Open
 
All Things Open 2019 weave-services-istio
All Things Open 2019 weave-services-istioAll Things Open 2019 weave-services-istio
All Things Open 2019 weave-services-istioLin Sun
 
Sharing-Knowledge-OAM-3G-Ericsson .ppt
Sharing-Knowledge-OAM-3G-Ericsson   .pptSharing-Knowledge-OAM-3G-Ericsson   .ppt
Sharing-Knowledge-OAM-3G-Ericsson .pptwafawafa52
 
Deep Dive into AWS Fargate - CON333 - re:Invent 2017
Deep Dive into AWS Fargate - CON333 - re:Invent 2017Deep Dive into AWS Fargate - CON333 - re:Invent 2017
Deep Dive into AWS Fargate - CON333 - re:Invent 2017Amazon Web Services
 
Openstack installation using rdo multi node
Openstack installation using rdo multi nodeOpenstack installation using rdo multi node
Openstack installation using rdo multi nodeNarasimha sreeram
 
Istio Playground
Istio PlaygroundIstio Playground
Istio PlaygroundQAware GmbH
 
Open-E Backup to Attached Tape Library
Open-E Backup to Attached Tape LibraryOpen-E Backup to Attached Tape Library
Open-E Backup to Attached Tape Libraryopen-e
 

Ähnlich wie Open-E DSS V7 Active-Passive iSCSI Failover (20)

Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server SystemsOpen-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Passive iSCSI Failover on Intel Server Systems
 
Open-E Backup to iSCSI Target Volume over a LAN
Open-E Backup to iSCSI Target Volume over a LANOpen-E Backup to iSCSI Target Volume over a LAN
Open-E Backup to iSCSI Target Volume over a LAN
 
Open-E DSS V7 Asynchronous Data Replication over a WAN
Open-E DSS V7 Asynchronous Data Replication over a WANOpen-E DSS V7 Asynchronous Data Replication over a WAN
Open-E DSS V7 Asynchronous Data Replication over a WAN
 
Open-E DSS V6 MPIO with ESXi 4.x
Open-E DSS V6 MPIO with ESXi 4.xOpen-E DSS V6 MPIO with ESXi 4.x
Open-E DSS V6 MPIO with ESXi 4.x
 
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft WindowsHow to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
How to Connect to a DSS V6 iSCSI Target Volume from a Microsoft Windows
 
Automating auto-scaled load balancer based on linux and vm orchestrator
Automating auto-scaled load balancer based on linux and vm orchestratorAutomating auto-scaled load balancer based on linux and vm orchestrator
Automating auto-scaled load balancer based on linux and vm orchestrator
 
Network Automation Tools
Network Automation ToolsNetwork Automation Tools
Network Automation Tools
 
Nat 03
Nat 03Nat 03
Nat 03
 
Lksn2017 itnsa modul2
Lksn2017 itnsa modul2Lksn2017 itnsa modul2
Lksn2017 itnsa modul2
 
Open-E Backup to Attached Tape Drive
Open-E Backup to Attached Tape DriveOpen-E Backup to Attached Tape Drive
Open-E Backup to Attached Tape Drive
 
The Basic Introduction of Open vSwitch
The Basic Introduction of Open vSwitchThe Basic Introduction of Open vSwitch
The Basic Introduction of Open vSwitch
 
Ato2019 weave-services-istio
Ato2019 weave-services-istioAto2019 weave-services-istio
Ato2019 weave-services-istio
 
Weave Your Microservices with Istio
Weave Your Microservices with IstioWeave Your Microservices with Istio
Weave Your Microservices with Istio
 
All Things Open 2019 weave-services-istio
All Things Open 2019 weave-services-istioAll Things Open 2019 weave-services-istio
All Things Open 2019 weave-services-istio
 
Sharing-Knowledge-OAM-3G-Ericsson .ppt
Sharing-Knowledge-OAM-3G-Ericsson   .pptSharing-Knowledge-OAM-3G-Ericsson   .ppt
Sharing-Knowledge-OAM-3G-Ericsson .ppt
 
Deep Dive into AWS Fargate - CON333 - re:Invent 2017
Deep Dive into AWS Fargate - CON333 - re:Invent 2017Deep Dive into AWS Fargate - CON333 - re:Invent 2017
Deep Dive into AWS Fargate - CON333 - re:Invent 2017
 
Openstack installation using rdo multi node
Openstack installation using rdo multi nodeOpenstack installation using rdo multi node
Openstack installation using rdo multi node
 
Istio Playground
Istio PlaygroundIstio Playground
Istio Playground
 
Open-E Backup to Attached Tape Library
Open-E Backup to Attached Tape LibraryOpen-E Backup to Attached Tape Library
Open-E Backup to Attached Tape Library
 
Nat 07
Nat 07Nat 07
Nat 07
 

Mehr von open-e

Open-E DSS V7 Remote Snapshot Control with CLI/API
Open-E DSS V7 Remote Snapshot Control with CLI/APIOpen-E DSS V7 Remote Snapshot Control with CLI/API
Open-E DSS V7 Remote Snapshot Control with CLI/APIopen-e
 
Description of Open-E Snapshot
Description of Open-E SnapshotDescription of Open-E Snapshot
Description of Open-E Snapshotopen-e
 
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...open-e
 
Open-E DSS V6 How to Setup iSCSI Failover with XenServer
Open-E DSS V6 How to Setup iSCSI Failover with XenServerOpen-E DSS V6 How to Setup iSCSI Failover with XenServer
Open-E DSS V6 How to Setup iSCSI Failover with XenServeropen-e
 
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...open-e
 
Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...
Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...
Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...open-e
 
Open-E DSS Synchronous Volume Replication over a WAN
Open-E DSS Synchronous Volume Replication over a WANOpen-E DSS Synchronous Volume Replication over a WAN
Open-E DSS Synchronous Volume Replication over a WANopen-e
 
Backup of Data Residing on DSS V6 with Backup Exec
Backup of Data Residing on DSS V6 with Backup ExecBackup of Data Residing on DSS V6 with Backup Exec
Backup of Data Residing on DSS V6 with Backup Execopen-e
 

Mehr von open-e (8)

Open-E DSS V7 Remote Snapshot Control with CLI/API
Open-E DSS V7 Remote Snapshot Control with CLI/APIOpen-E DSS V7 Remote Snapshot Control with CLI/API
Open-E DSS V7 Remote Snapshot Control with CLI/API
 
Description of Open-E Snapshot
Description of Open-E SnapshotDescription of Open-E Snapshot
Description of Open-E Snapshot
 
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...
Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported ...
 
Open-E DSS V6 How to Setup iSCSI Failover with XenServer
Open-E DSS V6 How to Setup iSCSI Failover with XenServerOpen-E DSS V6 How to Setup iSCSI Failover with XenServer
Open-E DSS V6 How to Setup iSCSI Failover with XenServer
 
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN with Un...
 
Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...
Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...
Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Br...
 
Open-E DSS Synchronous Volume Replication over a WAN
Open-E DSS Synchronous Volume Replication over a WANOpen-E DSS Synchronous Volume Replication over a WAN
Open-E DSS Synchronous Volume Replication over a WAN
 
Backup of Data Residing on DSS V6 with Backup Exec
Backup of Data Residing on DSS V6 with Backup ExecBackup of Data Residing on DSS V6 with Backup Exec
Backup of Data Residing on DSS V6 with Backup Exec
 

Open-E DSS V7 Active-Passive iSCSI Failover

  • 1. Step-by-Step Guide to Open-E DSS V7 Active-Passive iSCSI Failover Software Version: DSS ver. 7.00 up10 Presentation updated: June 2013 www.open-e.com 1
  • 2. Open-E DSS V7 Active-Passive iSCSI Failover TO SET UP ACTIVE-PASSIVE ISCSI FAILOVER, PERFORM THE FOLLOWING STEPS: 1. Hardware configuration 2. Network Configuration: • Set server hostnames and Ethernet ports on both nodes (node-a, node-b) 3. Configure the node-b: • Create a Volume Group, iSCSI Volume • Configure Volume Replication mode (destination and source mode) – define remote mode of binding, create Volume Replication task and start the replication task 4. Configure the node-a: • Create a Volume Group, iSCSI Volume • Configure Volume Replication mode (source and destination mode), create Volume Replication task and start the replication task. 5. Create targets (node-a and node-b) 6. Configure Failover (node-a and node-b) 7. Start Failover Service 8. Test Failover Function 9. Run Failback Function www.open-e.com 2
  • 3. Open-E DSS V7 Active-Passive iSCSI Failover Storage client IP:192.168.20.101 (MPIO 1) IP:192.168.1.107 (Ping Node) eth1 IP:192.168.21.101 (MPIO 2) IP:192.168.2.107 (Ping Node) 1. Hardware Configuration eth0 eth2 LAN IP:192.168.0.101 Data Server (DSS1) Data Server (DSS2) node-a Switch 1 IP Address:192.168.0.220 node-b Switch 2 IP Address:192.168.0.221 RAID System 2 RAID System 1 Port used for WEB GUI management IP:192.168.0.220 Port used for WEB GUI management eth0 eth0 Storage Client Access, Multipath Auxiliary connection (Heartbeat) IP:192.168.1.220 Storage Client Access, Multipath Auxiliary connection (Heartbeat) eth1 Virtual IP Address: 192.168.20.100 (iSCSI Target) Storage Client Access, Multipath Auxiliary connection (Heartbeat) IP:192.168.2.220 eth2 Virtual IP Address: 192.168.21.100 (iSCSI Target) Volume Replication, Auxilliary connection (Heartbeat) IP:192.168.3.220 Volume Groups (vg00) iSCSI volumes (lv0000) iSCSI targets eth3 IP:192.168.0.221 Note: It is strongly recommended to use direct point-to-point and if possible 10GbE connection for the volume replication. Optionally Round-Robin-Bonding with 1GbE or 10GbE ports can be configured for the volume replication. The volume replication connection can work over the switch, but the most reliable is a direct connection. iSCSI Failover/Volume Replication (eth3) eth1 IP:192.168.1.221 Storage Client Access, Multipath, Auxiliary connection (Heartbeat) eth2 IP:192.168.2.221 Volume Replication , Auxilliary connection (Heartbeat) eth3 IP:192.168.3.221 Volume Groups (vg00) iSCSI volumes (lv0000) iSCSI targets NOTE: For additional layer of redundancy, you may add an extra connection between switches and ping nodes. www.open-e.com 3
  • 4. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS2) node-b 1. Hardware Configuration IP Address:192.168.0.221 After logging on to the Open-E DSS V7 (node-b), please go to SETUP and choose the "Network interfaces" option. In the Hostname box, replace the "dss" letters in front of the numbers with "node-b" server, in this example "node-b-59979144" and click the apply button (this will require a reboot). www.open-e.com 4
  • 5. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS2) node-b 1. Hardware Configuration IP Address:192.168.0.221 Next, select eth0 interface and in the IP address field, change the IP address from 192.168.0.220 to 192.168.0.221 Then click apply (this will restart network configuration). www.open-e.com 5
  • 6. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS2) node-b 1. Hardware Configuration IP Address:192.168.0.221 Afterwards, select eth1 interface and change the IP address from 192.168.1.220 to 192.168.1.221 in the IP address field and click the apply button. Next, change the IP addresses in eth2 and eth3 interfaces accordingly. www.open-e.com 6
  • 7. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 1. Hardware Configuration IP Address:192.168.0.220 After logging in to node-a, please go to SETUP and choose the "Network interfaces" option. In the Hostname box, replace the "dss" letters in front of the numbers with "node-a" server, in this example "node-a-39166501" and click apply (this will require a reboot). www.open-e.com 7
  • 8. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS2) node-b 2. Configure the node-b IP Address:192.168.0.221 In CONFIGURATION, select "Volume manager", then click on "Volume groups". In the Unit manager function menu, add the selected physical units (Unit MD0 or other) to create a new volume group (in this case, vg00) and click the apply button. www.open-e.com 8
  • 9. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS2) node-b 2. Configure the node-b IP Address:192.168.0.221 Select the appropriate volume group (vg00) from the list on the left and create a new iSCSI volume of the required size. The logical volume (lv0000) will be the destination of the replication process on node-b. Next, check "Use volume replication" checkbox. After assigning an appropriate amount of space for the iSCSI volume, click the apply button. www.open-e.com 9
  • 10. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS2) node-b 2. Configure the node-b IP Address:192.168.0.221 Logical iSCSI Volume Block I/O is now configured. iSCSI volume (lv0000) www.open-e.com 10
  • 11. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 3. Configure the node-a IP Address:192.168.0.220 Go to the node-a system. In CONFIGURATION, select "Volume manager" and then click on "Volume groups". Add the selected physical units (Unit S001 or other) to create a new volume group (in this case, vg00) and click apply button. Volume Groups (vg00) www.open-e.com 11
  • 12. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 3. Configure the node-a IP Address:192.168.0.220 Select the appropriate volume group (vg00) from the list on the left and create a new iSCSI volume of the required size. The logical volume (lv0000) will be a source of the replication process on the node-a. Next, check the box for "Use volume replication" After assigning an appropriate amount of space for the iSCSI volume, click the apply button NOTE: The source and destination volumes must be of identical size. www.open-e.com 12
  • 13. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 3. Configure the node-a IP Address:192.168.0.220 Logical iSCSI Volume Block I/O is now configured. iSCSI volume (lv0000) www.open-e.com 13
  • 14. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS2) node-b 2. Configure the node-b IP Address:192.168.0.221 Now, on the node-b, go to "Volume replication". Within Volume replication mode function, check "Destination" checkbox for lv0000. Then, click the apply button. In the Hosts Binding function, enter the IP address of node-a (in our example, this would be 192.168.3.220), enter node-a administrator password and click the apply button. After applying all the changes, the status should be: Reachable. NOTE: The Mirror server IP Address must be on the same subnet in order for the replication to communicate. VPN connections can work providing you are not using a NAT. Please follow example: • Source: 192.168.3.220 • Destination: 192.168.3.221 www.open-e.com 14
  • 15. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 3. Configure the node-a IP Address:192.168.0.220 In the Create new volume replication task, enter the task name in the Task name field, then click on the button. In the Destination volume field, select the appropriate volume (in this example, lv0000). In the Bandwidth for SyncSource (MB) field you must change the value. In the example, 35MB is used. Next, click the create button. NOTE: The “Bandwidth for SyncSource (MB)” need to be calculated based on available Ethernet Network throughput and number of replication tasks and the limitation factor (about 0.7). For example: 1 Gbit Ethernet and 2 replication tasks (assuming 1 Gbit provides about 100 MB/sec sustained network throughput) • Bandwidth for SyncSource (MB): = 0.7 * 100/ 2 = 35 For example: 10 Gbit Ethernet and 10 replication tasks (assuming 10 Gbit provides about 700 MB/sec sustained network throughput) • Bandwidth for SyncSource (MB): = 0.7 * 700/10 = 49 www.open-e.com 15
  • 16. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 3. Configure the node-a IP Address:192.168.0.220 Now, in the Replication task manager function, click the corresponding "play" button to start the Replication task on the node-a. www.open-e.com 16
  • 17. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 3. Configure the node-a IP Address:192.168.0.220 You may view information about currently running replication tasks in the Replication tasks manager function window. When a task is started, a date and time will appear. www.open-e.com 17
  • 18. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 3. Configure the node-a IP Address:192.168.0.220 You can check the status of Volume Replication anytime in STATUS → "Tasks" → "Volume Replication" menu. Click on the button, located next to a task name (in this case MirrorTask-a) to display detailed information about the current replication task. NOTE: Please allow the replication task to complete (similar to above with status being ”Consistent”) before writing to the iSCSI Logical Volume. www.open-e.com 18
  • 19. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS2) node-b 4. Create new target on the node-b IP Address:192.168.0.221 Choose CONFIGURATION, "iSCSI target manager" and "Targets" from the top menu. In the "Create new target" function, uncheck the box Target Default Name. In the Name field, enter a name for the new target and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 19
  • 20. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS2) node-b 4. Create new target on the node-b IP Address:192.168.0.221 After that, select target0 from the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-0 → lv0000) click attach button located under Action. NOTE: Volumes on both sides must have the same SCSI ID and LUN# for example: lv0000 SCSI ID on node-a = lv0000 SCSI ID on node-b. In this case before clicking the attach button please copy the SCSI ID and LUN# from this node. www.open-e.com 20
  • 21. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 5. Create new target on the node-a IP Address:192.168.0.220 Next, go to node-a, click on CONFIGURATION and choose "iSCSI target manager" → "Targets" from the menu. In the "Create new target" function, uncheck the box Target Default Name. In the Name field, enter a name for the new target and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 21
  • 22. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 5. Create new target on the node-a IP Address:192.168.0.220 After that, select target0 from the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-0 → lv0000) click attach button located under Action. NOTE: Before clicking the attach button again, please paste the SCSI ID and LUN# (previously copied) from the node-b. www.open-e.com 22
  • 23. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 On the node-a go to Setup and select „Failover” In the "Auxiliary paths" function, select the 1st New auxiliary path on the local and remote node and click the add new auxiliary path button. www.open-e.com 23
  • 24. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 In the Auxiliary paths function, select the 2nd New auxiliary path on the local and remote node and click the add new auxiliary path button. www.open-e.com 24
  • 25. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 In the "Ping nodes" function, enter two ping nodes. In the IP address field enter IP address and click the add new ping node button (according to the configuration in the third slide). In this example, IP address of the first ping node is: 192.168.1.107 and the second ping node: 192.168.2.107 www.open-e.com 25
  • 26. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Next, go to the Resources Pool Manager function (on node-a resources) and click the add virtual IP button. After that, enter 1st Virtual IP, (in this example 192.168.20.100 according to the configuration in the third slide) and select two appropriate interfaces on local and remote nodes. Then, click the add button. www.open-e.com 26
  • 27. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Now, still on node-a resources (local node) enter the next Virtual IP address. Click add virtual IP enter 2nd Virtual IP, (in this example 192.168.21.100), and select two appropriate interfaces on the local and remote nodes. Then, click the add button. www.open-e.com 27
  • 28. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 Now you have 2 Virtual IP addresses configured on two interfaces. www.open-e.com 28
  • 29. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 When you are finished with setting the virtual IP, go to the "iSCSI resources" tab on the local node resources and click the add or remove targets button. After moving the target mirror-0 from "Available targets" to "Targets already in cluster" click the apply button. www.open-e.com 29
  • 30. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 6. Configure Failover IP Address:192.168.0.220 After that, scroll to the top of the Failover manager function. At this point, both nodes are ready to start the Failover. In order to run the Failover service, click the start button and confirm this action by clicking the start button again. NOTE: If the start button is grayed out, the setup has not been completed. www.open-e.com 30
  • 31. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 7. Start Failover Service IP Address:192.168.0.220 After clicking the start button, configuration of both nodes is complete. NOTE: You can now connect with iSCSI Initiators. The storage client, in order to connect to target0 please setup multipath with following IP on the initiator side: 192.168.20.100 and 192.168.21.100. www.open-e.com 31
  • 32. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 8. Test Failover Function IP Address:192.168.0.220 In order to test Failover, go to the Resources pool manager function. Then, in the local node resources, click on the move to remote node button and confirm this action by clicking the move button. www.open-e.com 32
  • 33. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 8. Test Failover Function IP Address:192.168.0.220 After performing this step, the status for local node resources should state "active on node-b (remote node)" and the Synchronization status should state "synced". www.open-e.com 33
  • 34. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 9. Run Failback Function IP Address:192.168.0.220 In order to test failback, click the move to local node button in the Resources pool manager box for local node resources and confirm this action by clicking the move button. www.open-e.com 34
  • 35. Open-E DSS V7 Active-Passive iSCSI Failover Data Server (DSS1) node-a 9. Run Failback Function IP Address:192.168.0.220 After completing this step the status for node-a resources should state "active on node-a" (local node) and the Synchronization status should state: synced. NOTE: The Active-Passive option allows configuring a resource pool only on one of the nodes. In such a case, all volumes are active on a single node only. The Active-Active option allows configuring resource pools on both nodes and makes it possible to run some active volumes on node-a and other active volumes on node-b. The Active-Active option is enabled with the TRIAL mode for 60 days or when purchasing the Active-Active Failover Feature Pack. The configuration and testing of Active-Passive iSCSI Failover is now complete. www.open-e.com 35