Step-by-Step Guide to Open-E DSS V7 Active-Active iscsi Failover

Similar documents
Step-by-Step Guide to Open-E DSS V7 Active-Active Load Balanced iscsi HA Cluster

Step-by-Step Guide. to configure Open-E DSS V7 Active-Active iscsi Failover on Intel Server Systems R2224GZ4GC4. Software Version: DSS ver. 7.

Step-by-Step Guide to Open-E DSS V7 Active-Passive iscsi Failover

A Step-by-Step Guide to Synchronous Volume Replication (Block Based) over a WAN with Open-E DSS

istorage Server: High Availability iscsi SAN for Windows Server 2012 Cluster

Volume Replication INSTALATION GUIDE. Open-E Data Storage Server (DSS )

istorage Server: High-Availability iscsi SAN for Windows Server 2008 & Hyper-V Clustering

Backup to attached Tape Drive using Open-E DSS V6

High-Availability User s Guide v2.00

Backup to attached Tape Library using Open-E DSS V6

Multiple Public IPs (virtual service IPs) are supported either to cover multiple network segments or to increase network performance.

Data Replication INSTALATION GUIDE. Open-E Data Storage Server (DSS ) Integrated Data Replication reduces business downtime.

StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with Hyper-V Cluster

Windows Host Utilities Installation and Setup Guide

Our target is an EqualLogic PS100 Storage Array with a portal address of

ION-NAS Network Storage Solutions

Introduction to MPIO, MCS, Trunking, and LACP

Package Contents. D-Link DSN-3200/3400 Installation Guide. DSN-3200/3400 xstack Storage Area Network (SAN) Array. CD-ROM with User Guide.

Qsan Document - White Paper. How to use QReplica 2.0

The functionality and advantages of a high-availability file server system

How To Set Up A Two Node Hyperv Cluster With Failover Clustering And Cluster Shared Volume (Csv) Enabled

EXPRESSCLUSTER X for Windows Quick Start Guide for Microsoft SQL Server Version 1

Network Load Balancing

StarWind iscsi SAN Software: Using an existing SAN for configuring High Availability storage with Windows Server 2003 and 2008

Configuring a Microsoft Windows Server 2012/R2 Failover Cluster with Storage Center

Dell Compellent Storage Center

Deploying Windows Streaming Media Servers NLB Cluster and metasan

N5 NETWORKING BEST PRACTICES

Clustering ExtremeZ-IP 4.1

Synology High Availability (SHA)

V310 Support Note Version 1.0 November, 2011

Setup for Failover Clustering and Microsoft Cluster Service

Veritas Cluster Server

How to integrate RSA ACE Server SecurID Authentication with Juniper Networks Secure Access SSL VPN (SA) with Single Node or Cluster (A/A or A/P)

Drobo How-To Guide. What You Will Need. Configure Replication for DR Using Double-Take Availability and Drobo iscsi SAN

Configuring an IP (SIP) Polycom Soundstation on the Avaya IP Office

StarWind iscsi SAN & NAS: Configuring HA Shared Storage for Scale- Out File Servers in Windows Server 2012 January 2013

Setup for Failover Clustering and Microsoft Cluster Service

Replicating VNXe3100/VNXe3150/VNXe3300 CIFS/NFS Shared Folders to VNX Technical Notes P/N h REV A01 Date June, 2011

Package Contents. D-Link DSN-3200/3400 Installation Guide. DSN-3200/3400 xstack Storage Area Network (SAN) Array. CD-ROM with User Guide.

Windows Host Utilities 6.0 Installation and Setup Guide

Setup Guide. network support pc repairs web design graphic design Internet services spam filtering hosting sales programming

Synology High Availability (SHA)

Management Software. Web Browser User s Guide AT-S106. For the AT-GS950/48 Gigabit Ethernet Smart Switch. Version Rev.

Configuring Network Load Balancing with Cerberus FTP Server

If you already have your SAN infrastructure in place, you can skip this section.

StarWind iscsi SAN & NAS: Configuring HA File Server on Windows Server 2012 for SMB NAS January 2013

Compellent Storage Center

Exinda How to Guide: Virtual Appliance. Exinda ExOS Version Exinda, Inc

QNAP and Failover Technologies

StarWind iscsi SAN: Configuring HA File Server for SMB NAS February 2012

StarWind iscsi SAN Configuring HA File Server for SMB NAS

Implementing Storage Concentrator FailOver Clusters

1:1 NAT in ZeroShell. Requirements. Overview. Network Setup

Training module 2 Installing VMware View

StarWind iscsi SAN Software: Providing shared storage for Hyper-V's Live Migration feature on two physical servers

Building Microsoft Windows Server 2012 Clusters on the Dell PowerEdge VRTX

Best Practices: Pass-Through w/bypass (Bridge Mode)

The SSL device also supports the 64-bit Internet Explorer with new ActiveX loaders for Assessment, Abolishment, and the Access Client.

Cloudvue Remote Desktop Client GUI User Guide

SanDisk ION Accelerator High Availability

Acronis Backup & Recovery 11

Bosch Video Management System High Availability with Hyper-V

Administering and Managing Failover Clustering

Using iscsi with BackupAssist. User Guide

PoINT Jukebox Manager Deployment in a Windows Cluster Configuration

HP ProLiant DL380 G5 High Availability Storage Server

Configuring Security for FTP Traffic

Setup for Failover Clustering and Microsoft Cluster Service

SQL Server AlwaysOn. Michal Tinthofer 11. Praha What to avoid and how to optimize, deploy and operate.

StarWind iscsi SAN & NAS: Configuring HA Storage for Hyper-V October 2012

Guide to the LBaaS plugin ver for Fuel

Optimum Business SIP Trunk Set-up Guide

SQL Server Setup for Assistant/Pro applications Compliance Information Systems

Host Integration Tools

SAN Conceptual and Design Basics

How to Create a Virtual Switch in VMware ESXi

Certification Document macle GmbH GRAFENTHAL R2208 S2 01/04/2016. macle GmbH GRAFENTHAL R2208 S2 Storage system

Availability Guide for Deploying SQL Server on VMware vsphere. August 2009

FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection-

Multi-Homing Security Gateway

CA /BrightStor ARCserve9 Backup Software

Setup for Failover Clustering and Microsoft Cluster Service

Digium Switchvox AA65 PBX Configuration

TSM for Windows Installation Instructions: Download the latest TSM Client Using the following link:

Servers and two Client with failover

Redundant Servers. APPolo Redundant Servers User Guide. User Guide. Revision: 1.2 Last Updated: May 2014 Service Contact:

vsphere Networking ESXi 5.0 vcenter Server 5.0 EN

Quick Note 53. Ethernet to W-WAN failover with logical Ethernet interface.

SQL Server Mirroring. Introduction. Setting up the databases for Mirroring

Install and Configure Oracle Outlook Connector

StarWind iscsi SAN: Configuring Global Deduplication May 2012

This techno knowledge paper can help you if: You need to setup a WAN connection between a Patton Router and a NetGuardian.

1 PC to WX64 direction connection with crossover cable or hub/switch

24 Port Gigabit Ethernet Web Smart Switch. Users Manual

Device Interface IP Address Subnet Mask Default Gateway

LOAD BALANCING 2X APPLICATIONSERVER XG SECURE CLIENT GATEWAYS THROUGH MICROSOFT NETWORK LOAD BALANCING

Transcription:

www.open-e.com 1 Step-by-Step Guide to Software Version: DSS ver. 7.00 up10 Presentation updated: June 2013

www.open-e.com 2 TO SET UP ACTIVE-ACTIVE ISCSI FAILOVER, PERFORM THE FOLLOWING STEPS: 1. Hardware configuration 2. Network Configuration: Set server hostnames and Ethernet ports on both nodes (, 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 : 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 ( and node-b) 6. Configure Failover ( and node-b) 7. Start Failover Service 8. Test Failover Function 9. Run Failback Function

Storage client 1 1. Hardware Configuration Storage client 2 IP:192.168.0.101 eth0 eth0 IP:192.168.0.102 IP:192.168.21.101 (MPIO 1) IP:192.168.22.101 (MPIO 2) IP:192.168.1.107 (Ping Node) IP:192.168.31.101 (MPIO 1) IP:192.168.32.101 (MPIO 2) RAID System 1 Port used for WEB GUI management Storage Client Access, Multipath Auxiliary connection (Heartbeat) bond0 IP:192.168.1.220 (eth1, eth2) Storage Client Access, Multipath Auxiliary connection (Heartbeat) bond1 IP:192.168.2.220 (eth3, eth4) Volume Groups (vg00) IP:192.168.0.220 Volume Replication, Auxilliary connection (Heartbeat) IP:192.168.5.220 iscsi volumes (lv0000, lv0001) iscsi targets eth1 eth2 eth0 eth5 Note: Switch 1 Switch 2 RSTP/Port Trunk Note: Please use external tool to monitor failures in connections between switches. Resources Pools and Virtual IP Addresses: Node-a 192.168.21.100; iscsi Target 0 Node-b 192.168.22.100; iscsi Target 1 Resources Pools and Virtual IP Addresses: Node-a 192.168.31.100; iscsi Target 0 Node-b 192.168.32.100; iscsi Target 1 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 (eth5) Data Server (DSS2) node-b IP Address:192.168.0.221 RAID System 2 Port used for WEB GUI management eth0 IP:192.168.0.221 Storage Client Access, Multipath Auxiliary connection (Heartbeat) (eth1, eth2) IP:192.168.1.221 bond0 Storage Client Access, Multipath, Auxiliary connection (Heartbeat) (eth3, eth4) IP:192.168.2.221 bond1 eth5 (MPIO 1) (MPIO 2) Volume Replication, Auxilliary connection (Heartbeat) IP:192.168.5.221 Volume Groups (vg00) iscsi volumes (lv0000, lv0001) NOTE: To prevent switching loops, it's recommended to use RSTP (802.1w) or Port Trunking on network switches used to build A-A Failover network topology. IP:192.168.21.102 IP:192.168.22.102 www.open-e.com 3 eth1 eth2 (MPIO 1) IP:192.168.31.102 (MPIO 2) IP:192.168.32.102 (Ping Node) IP:192.168.2.107 iscsi targets

www.open-e.com 4 Data Server (DSS2) node-b IP Address:192.168.0.221 2. Network Configuration 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 5 Data Server (DSS2) node-b IP Address:192.168.0.221 2. Network Configuration 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 6 Data Server (DSS2) node-b IP Address:192.168.0.221 2. Network Configuration Once again, select Interfaces and in the "Create new bond interface" function check two boxes with eth1 and eth2. Next, in the field Create select a bonding mode. In this example select New balance-alb. Next, in the field Adress IP enter 192.168.1.221 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button.

www.open-e.com 7 Data Server (DSS2) node-b IP Address:192.168.0.221 2. Network Configuration Again, in the "Create new bond interface" function check two boxes with eth3 and eth4. Next, in the field Create select a bonding mode. In this example select New balance-alb. Next, in the Address IP field enter 192.168.2.221 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button.

www.open-e.com 8 Data Server (DSS2) node-b IP Address:192.168.0.221 2. Network Configuration Next, select eth5 interface and in the IP address field, change the IP address from 192.168.5.220 to 192.168.5.221 and click the apply button.

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

www.open-e.com 10 2. Network Configuration Next, select Interfaces and in the "Create new bond interface" function check two boxes with eth1 and eth2. Next, in the field Create select a bonding mode. In this example select New balance-alb. In the field Adress IP enter 192.168.1.220 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button.

www.open-e.com 11 2. Network Configuration Again in the "Create new bond interface" function check two boxes with eth3 and eth4. Next, in the field Create select a bonding mode. In this example select New balance-alb. Next, in the field Adress IP enter 192.168.2.220 and in the Netmask field enter 255.255.255.0 Afterwards, click the create button and confirm this action by clicking the yes button.

www.open-e.com 12 Data Server (DSS2) node-b IP Address:192.168.0.221 3. Configure the node-b Under 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 13 Data Server (DSS2) node-b IP Address:192.168.0.221 3. Configure the node-b Select the appropriate volume group (vg00) from the list on the left and create a new iscsi volume of the required size. Please set 2 logical volumes in the Active-Active option. The 1st logical volume (lv0000) will be a destination of the replication process on node-b. Next, check the box Use volume replication. After assigning an appropriate amount of space for the iscsi volume, click the apply button

www.open-e.com 14 Data Server (DSS2) node-b IP Address:192.168.0.221 3. Configure the node-b Next, create the 2nd logical volume on the node-b. Logical volume (lv0001) will be the source of the replication process on this node. Next, check the box Use volume replication. After assigning an appropriate amount of space for the iscsi volume, click the apply button.

www.open-e.com 15 Data Server (DSS2) node-b IP Address:192.168.0.221 3. Configure the node-b 2 logical iscsi Volume Block I/O are now configured. iscsi volume (lv0000) is set to destination iscsi volume (lv0001) is set to source

www.open-e.com 16 4. Configure the Under 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 17 4. Configure the Select the appropriate volume group (vg00) from the list on the left and create a new iscsi volume of the required size. Please set 2 logical volumes in the Active-Active option. The 1st logical volume (lv0000) will be a source of the replication process on the. Next, check the box for "Use volume replication" After assigning an appropriate amount of space to the iscsi volume, click the apply button. NOTE: The source and destination volumes must be of identical size.

4. Configure the Next, create the 2nd logical volume on the. Logical volume (lv0001) will be a destination of the replication process on this node. Next, check the box for "Use volume replication". After assigning an appropriate amount of space to the iscsi volume, click the apply button. NOTE: The source and destination volumes must be of identical size. www.open-e.com 18

www.open-e.com 19 4. Configure the 2 logical iscsi Volume Block I/O are now configured. iscsi volume (lv0000) is set to source iscsi volume (lv0001) is set to destination

Data Server (DSS2) node-b IP Address:192.168.0.221 3. Configure the node-b Now, on the node-b, go to "Volume replication". Within Volume replication mode function, check the Destination box for lv0000 and check the Source box for lv0001. Then, click the apply button. In the Hosts binding function, enter the IP address of (in our example, this would be 192.168.5.220), enter administrator password and click the apply button. NOTE: The remote node 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: : 192.168.5.220 node-b: 192.168.5.221 www.open-e.com 20

www.open-e.com 21 4. Configure the Next, on the, go to "Volume replication". Within Volume replication mode function, check the Source box for lv0000 and check the Destination box for lv0001. Next, click the apply button.

4. Configure the 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 22

www.open-e.com 23 4. Configure the Now, in the Replication task manager function, click the corresponding "play" button to start the Replication task on the.

www.open-e.com 24 4. Configure the In the Replication tasks manager window, you may view information about currently running replication tasks. When a task is started, a date and time will appear.

www.open-e.com 25 4. Configure the 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 Mirror_0000) to display detailed information on 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 26 Data Server (DSS2) node-b IP Address:192.168.0.221 3. Configure the node-b Next, go to the node-b. Within 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, lv0001). As in the, in the Bandwidth for SyncSource (MB) field you must change the value. In our example 35 MB is used. Next click the create button.

www.open-e.com 27 Data Server (DSS2) node-b IP Address:192.168.0.221 3. Configure the node-b In the Replication tasks manager function, click the corresponding "play" button to start the Replication task on the node-b: Mirror_0001. In this box you can find information about currently running replication tasks. When a task is started a date and time will appear.

www.open-e.com 28 Data Server (DSS2) node-b IP Address:192.168.0.221 5. Create new target on the node-b 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 29 Data Server (DSS2) node-b IP Address:192.168.0.221 5. Create new target on the node-b Next, you must set the 2nd target. Within the Create new target function, uncheck the box Target Default Name. In the Name field, enter a name for the 2nd new target and click apply to confirm. iscsi targets NOTE: Both systems must have the same Target name.

www.open-e.com 30 Data Server (DSS2) node-b IP Address:192.168.0.221 5. Create new target on the node-b After that, select target0 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-0 lv0000) and 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 = lv0000 SCSI ID on node-b. In this case before clickling the attach button please copy the SCSI and LUN# from this node.

www.open-e.com 31 Data Server (DSS2) node-b IP Address:192.168.0.221 5. Create new target on the node-b Next, select target1 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-1 lv0001) and click attach button located under Action. NOTE: Both systems must have the same SCSI ID and LUN#

www.open-e.com 32 5. Create new target on the On the, choose CONFIGURATION, "iscsi target manager" and "Targets" from the top menu. Within 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 33 5. Create new target on the Next, you must set the 2nd target. In the Create new target function, uncheck the box Target Default Name. In the Name field, enter a name for the 2nd new target and click apply to confirm. iscsi targets NOTE: Both systems must have the same Target name.

www.open-e.com 34 5. Create new target on the Select the target0 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-0 lv0000) and 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 35 5. Create new target on the Select the target1 within the Targets field. To assign appropriate volume to the target (iqn.2013-06:mirror-1 lv0001) and click attach button located under Action. NOTE: Before clicking the attach button again, please copy & paste the SCSI ID and LUN# from the node-b.

www.open-e.com 36 6. Configure Failover On the, 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 37 6. Configure Failover 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 38 6. Configure Failover 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 39 6. Configure Failover Next, go to the Resources Pool Manager function (on resources) and click the add virtual IP button. After that, enter Virtual IP, (in this example 192.168.21.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 40 6. Configure Failover Now, still on resources (local node) enter the next Virtual IP address. Click add virtual IP enter Virtual IP, (in this example 192.168.31.100), and select two appropriate interfaces on the local and remote nodes. Then, click the add button.

www.open-e.com 41 6. Configure Failover Then, go to node-b resources and click the add virtual IP button again and enter the Virtual IP (In this example 192.168.22.100 according to the configuration in the third slide) and select two appropriate interfaces on the local and remote nodes. Then, click the add button.

www.open-e.com 42 6. Configure Failover Now, still on node-b resources, click the add virtual IP button and enter the next Virtual IP, (in this example 192.168.32.100, according to the configuration in the third slide) and select two appropriate interfaces on the local and remote nodes. Then, click the add button.

www.open-e.com 43 6. Configure Failover Now you have 4 Virtual IP addresses configured on two interfaces.

www.open-e.com 44 6. Configure Failover 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 45 6. Configure Failover Next, go to the iscsi resources tab on the remote node resources and click the add or remove targets button. After moving the target mirror-1 from Available targets to Targets already in cluster, click the apply button.

www.open-e.com 46 6. Configure Failover 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 47 7. Start Failover Service After clicking the start button, configuration of both nodes is complete. NOTE: You can now connect with iscsi Initiators. The first storage client, in order to connect to target0 please setup multipath with following IP on the initiator side: 192.168.21.101 and 192.168.31.101. In order to connect to target1 please setup multipath with following IP on the initiator side: 192.168.22.101 and 192.168.32.101. For the next storage client please setup multipath accordingly: for access to target0: 192.168.21.102, 192.168.31.102 and for access to target1: 192.168.22.102, 192.168.32.102.

www.open-e.com 48 8. Test Failover Function 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 49 8. Test Failover Function 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 50 9. Run Failback Function 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 51 9. Run Failback Function After completing this step, the status for resources should state "active on (local node)" and the Synchronization status should state "synced". Then, you can apply the same actions for node-b resources. NOTE: The Active-Active option allows configuring resource pools on both nodes and makes it possible to run some active volumes on 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 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 configuration and testing of Active-Active iscsi Failover is now complete.

www.open-e.com 52 Thank you! Follow Open-E: