SlideShare una empresa de Scribd logo
1 de 52
Step-by-Step Guide to
                 Synchronous
          Volume Replication
                (Block Based)
      with Failover over a LAN
             (with broadcast)
  Supported by Open-E ® DSS™



Software Version: DSS ver. 6.00 up50
Presentation updated: September 2010
Synchronous Volume Replication with Failover over a LAN




    Open-E DSS Synchronous Volume Replication with Failover is a fault tolerance process via iSCSI volume
     replication, that creates mirrored target data volumes.

   • 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 continued as usual.




                                                        www.open-e.com                                                          2
Synchronous Volume Replication with Failover over a LAN
   VOLUME REPLICATION WITH FAILOVER BETWEEN TWO SYSTEMS
   WITHIN ONE LAN
   Recommended Resources
          • Key Hardware (two systems)
                  x86 compatible
                  RAID Controller with Battery Backup Unit
                  HDD‘s
                  Network Interface Cards
                  Ping Node (ping node it is any permanently (24/7) available host in the network. In particular
                   case the ping node function can be performed by the server storing the data on the iSCSI
                   failover volume).
          • Software
                Open-E DSS V6, 2 units

   Benefits
          • Eliminate business disruption
          • Data Redundancy over a LAN
          • Switch Redundancy

   Disadvantages
          • High cost of solution
          • Natural disasters (earthquake, fire, flood...) can destroy local systems
                                      www.open-e.com                                                       3
Synchronous Volume Replication with Failover over a LAN
                                    • Data is written and read to System 1 (primary)
                                    • Data is continually replicated to System 2 (secondary)



                            Heartbeat

                               Volume Replication


            RAID System 1                                                        RAID System 2
            Primary                                                              Secondary

PING NODE




                 Control                                                                Write Data

                                                                    Read Data




                            www.open-e.com                                                           4
Synchronous Volume Replication with Failover over a LAN
                            • In case system malfunction or power failure or lost network connection of the System1 (primary), the
                              server will send an e-mail Notification to the administrator.
                            • After a few seconds Automatic Failover is executed and users are switched to System 2 (secondary).




                  X
                                          Heartbeat




            RAID System 1                                                                              RAID System 2
            Primary                                                                                    Secondary

PING NODE




                 Control                                                                                       Write Data

                                                                                        Read Data




                                         www.open-e.com                                                                      5
Synchronous Volume Replication with Failover over a LAN
                                 • After switching, the replicated volume
                                   is available on System 2 (secondary)




                  X
            RAID System 1
            Primary
                                                                              RAID System 2
                                                                              Secondary

PING NODE




                                                                                    Write Data

                                                                  Read Data




                            www.open-e.com                                                       6
Synchronous Volume Replication with Failover over a LAN
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 Group, iSCSI Volume
    •    Configure Volume Replication mode (destination mode) – settings mirror IP address
    3.   Configure the Primary node
    •    Create a Volume Group, iSCSI Volume
    •    Configure Volume Replication mode (source mode) – settings mirror IP address, creating Volume Replication
         task and start replication task.
    •    Create new target on Secondary node
    •    Create new target on Primary node
    •    Configure iSCSI Failover (primary and secondary node)
    •    Configure virtual IP and Auxiliary connection
    •    Start Failover Service
    •    Test Failover Function
    •    Run Failback Function
                                                   www.open-e.com                                                    7
Synchronous Volume Replication with Failover over a LAN
Hardware Requirements:
To run the Volume Replication with Failover, two DSS systems                                1. Hardware Configuration
are required. Both servers must be located and working in the
Local Area Network. See below configurations for examples:                                                PING NODE
                                                                                                          IP Address : 192.168.2.106

Data Server (DSS1)                                                                                                                              Data Server (DSS2)
Primary node                                                                            Control                                                 Secondary node
IP Address:192.168.0.220                                                                                                                        IP Address:192.168.0.221
                                                                   Switch 1
             RAID System 1                                                                                                                        RAID System 2
                                                                                            Switch 2
             Primary                                                                                                                              Secondary


 Port used for WEB GUI management                                                                                                         Port used for WEB GUI management
                      IP:192.168.0.220   eth0                                                                                      eth0   IP:192.168.0.221

 Volume Replication ,                                                         Optional:                                                                    Volume Replication ,
 Auxiliary connection (Heartbeat)                                             This path can be                                                 Auxiliary connection (Heartbeat)
                      IP:192.168.1.220   eth1                                 directly point-to-point                              eth1   IP:192.168.1.221
                                                                              connected eth1 to eth1
  Client Storage Access,                                                                                                                                Client Storage Access,
  Auxiliary connection (Heartbeat)
                                                                              (without the switch).
                                                                                                                                               Auxiliary connection (Heartbeat)
  bond0      IP:192.168.2.220       (eth2, eth3)                                                                                   (eth2, eth3)    IP:192.168.2.221   bond0

                                                   Bonding IP                                           Bonding IP
   Volume Groups (vg00)
                                                                                                                                              Volume Groups (vg00)
                                                       Virtual IP Address:192.168.10.230 (iSCSI Target)

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


   iSCSI targets                                                                                                                                  iSCSI targets


                                                                        www.open-e.com                                                                                 8
Synchronous Volume Replication with Failover over a LAN
                            Data Server (DSS2)
                            Secondary node                      1. Hardware Configuration
                            IP Address:192.168.0.221




 After logging on the DSS V6
 please go to „SETUP” tab,
 „network” and „Interfaces”. In
 „Server name” function enter
 Server name, in this example
 „dss2” and click apply button.
 (All connections will be
 restarted)




                                                       www.open-e.com                       9
Synchronous Volume Replication with Failover over a LAN
                             Data Server (DSS2)
                             Secondary node                      1. Hardware Configuration
                             IP Address:192.168.0.221




 Next select eth0 interface and
 change IP Address from
 192.168.0.220 in field IP address
 to 192.168 .0.221, and click apply
 button. (This will restart network
 configuration).




                                                        www.open-e.com                       10
Synchronous Volume Replication with Failover over a LAN
                             Data Server (DSS2)
                             Secondary node                      1. Hardware Configuration
                             IP Address:192.168.0.221




 Next select eth1 interface and
 change IP address from
 192.168.1.220 in field IP address
 to 192.168 .1.221 and click apply
 button.




                                                        www.open-e.com                       11
Synchronous Volume Replication with Failover over a LAN
                             Data Server (DSS2)
                             Secondary node                      1. Hardware Configuration
                             IP Address:192.168.0.221




 Again select „Interfaces” and in
 Create new bond interface
 function check two boxes with eth2
 and eth3. In field Create select
 bonding mode. In this example
 select New balance-rr.




 Next enter IP Address in field
 Adress IP 192.168 .2.221,
 Netmask, and click create button.


                                                        www.open-e.com                       12
Synchronous Volume Replication with Failover over a LAN
                              Data Server (DSS2)
                              Secondary node                      1. Hardware Configuration
                              IP Address:192.168.0.221




 After reloading page on the dss2
 server you have configured bond0.
 Setting of the network interfaces on
 the secondary node is finished.




                                                         www.open-e.com                       13
Synchronous Volume Replication with Failover over a LAN
                            Data Server (DSS1)
                            Primary node                        1. Hardware Configuration
                            IP Address:192.168.0.220




 After logging on the primary
 node please go to „SETUP”
 tab, „network” and
 „Interfaces”. In „Server name”
 function enter Server name. In
 this example enter dss1 and
 click apply button. (All
 connection will be restarted).




                                                       www.open-e.com                       14
Synchronous Volume Replication with Failover over a LAN
                             Data Server (DSS1)
                             Primary node                        1. Hardware Configuration
                             IP Address:192.168.0.220




 Again select „Interfaces” and in
 Create new bond interface
 function check two boxes with eth2
 and eth3. In field Create select
 mode for bonding. In this example
 selected New balance-rr..




 Next enter IP Address in field
 Address IP 192.168 .2.220,
 Netmask, and click create button.


                                                        www.open-e.com                       15
Synchronous Volume Replication with Failover over a LAN
                             Data Server (DSS1)
                             Primary node                        1. Hardware Configuration
                             IP Address:192.168.0.220




 After reloading page on the dss1
 server you have configured
 bond0. Setting of the network
 interfaces on the secondary node is
 finished.




                                                        www.open-e.com                       16
Synchronous Volume Replication with Failover over a LAN
                                Data Server (DSS2)
                                Secondary node                      2. Configure the Secondary node
                                IP Address:192.168.0.221




 Under the
 „CONFIGURATION” tab,
 select „volume manager” and
 next Vol. Groups.




         Volume Groups (vg00)



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




                                                           www.open-e.com                             17
Synchronous Volume Replication with Failover over a LAN
                              Data Server (DSS2)
                              Secondary node                      2. Configure the Secondary node
                              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.
 This logical volume will be the
 destination of the replication
 process.




 Next check the box with Use
 volume replication



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


                                                         www.open-e.com                             18
Synchronous Volume Replication with Failover over a LAN
                                 Data Server (DSS2)
                                 Secondary node                      2. Configure the Secondary node
                                 IP Address:192.168.0.221




 The destination iSCSI Volume
 Block I/O is now configured.



         iSCSI volume (lv0000)




                                                            www.open-e.com                             19
Synchronous Volume Replication with Failover over a LAN
                                    Data Server (DSS2)
                                    Secondary node                      2. Configure the Secondary node
                                    IP Address:192.168.0.221




  Now, select the Vol.
  replication and check the box
  under Destination and click the
  apply button


  Next, under Mirror Server IP
  function, enter the IP address of
  the Primary node (in our
  example, this would be
  192.168.1.220) and click the
  apply button

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.1.220
•Destination: 192.168.1.221
                                                               www.open-e.com                             20
Synchronous Volume Replication with Failover over a LAN
                                 Data Server (DSS1)
                                 Primary node                        3. Configure the Primary node
                                 IP Address:192.168.0.220




 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




          Volume Groups (vg00)




                                                            www.open-e.com                           21
Synchronous Volume Replication with Failover over a LAN
                                 Data Server (DSS1)
                                 Primary node                        3. Configure the Primary node
                                 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.
 This logical volume will be the
 source of the replication
 process.


 Next , check box 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                           22
Synchronous Volume Replication with Failover over a LAN
                                Data Server (DSS1)
                                Primary node                        3. Configure the Primary node
                                IP Address:192.168.0.220




 The source iSCSI Volume Block
 I/O is now configured.



        iSCSI volume (lv0000)




                                                           www.open-e.com                           23
Synchronous Volume Replication with Failover over a LAN
                              Data Server (DSS1)
                              Primary node                        3. Configure the Primary node
                              IP Address:192.168.0.220




 Now, select Vol. replication,
 and check the box under
 Source and click the apply
 button




 Next , under Mirror Server IP
 function, enter the IP address of
 the Secondary node (in our
 example this would be
 192.168.1.221) and click the
 apply button




                                                         www.open-e.com                           24
Synchronous Volume Replication with Failover over a LAN
                                Data Server (DSS1)
                                Primary node                        3. Configure the Primary node
                                IP Address:192.168.0.220




 Enter the task name in field
 Task name next click on the
    button




 In the Destination volume
 field select the appropriate
 volume (in this example,
 lv0000) and click create to
 confirm


                                                           www.open-e.com                           25
Synchronous Volume Replication with Failover over a LAN
                             Data Server (DSS1)
                             Primary node                        3. Configure the Primary node
                             IP Address:192.168.0.220




 Now, in the Replication task
 manager function, click on
     button under to start the
 Replication task on the Primary
 node




                                                        www.open-e.com                           26
Synchronous Volume Replication with Failover over a LAN
                             Data Server (DSS1)
                             Primary node                        3. Configure the Primary node
                             IP Address:192.168.0.220




 In the Replication tasks
 manager function information
 is available about the current
 running replication task.




                                                        www.open-e.com                           27
Synchronous Volume Replication with Failover over a LAN
                                     Data Server (DSS1)
                                     Primary node                        3. Configure the Primary node
                                     IP Address:192.168.0.220




  Under the „STATUS” tab,
  select „tasks” and Volume
  Replication




  Click on the     button with
  task name (in this case
  MirrorTask) 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                           28
Synchronous Volume Replication with Failover over a LAN
                                Data Server (DSS2)
                                Secondary node                      4. Create new target on the Secondary node
                                IP Address:192.168.0.221




  Choose „CONFIGURATION”,
  „iSCSI target manager” and
  „Targets” from the menu



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



  iSCSI targets



NOTE:
Both systems must have the same Target name.
                                                           www.open-e.com                                        29
Synchronous Volume Replication with Failover over a LAN
                                      Data Server (DSS2)
                                      Secondary node                      4. Create new target on the Secondary node
                                      IP Address:192.168.0.221




  Select target0 within the
  Targets field.




  To assign a volume to the
  target, click the button
  located under Action




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




                                                                 www.open-e.com                                        30
Synchronous Volume Replication with Failover over a LAN
                                Data Server (DSS1)
                                Primary node                        5. Create new target on the Primary node
                                IP Address:192.168.0.220




  Choose „CONFIGURATION”
  and „iSCSI target manager”
  and „Targets” from the menu


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



  iSCSI targets


NOTE:
Both systems must have the same Target name.

                                                           www.open-e.com                                      31
Synchronous Volume Replication with Failover over a LAN
                                      Data Server (DSS1)
                                      Primary node                        5. Create new target on the Primary node
                                      IP Address:192.168.0.220




  Select the target0 within the
  Targets field


  To assign a volume to the
  target, click the button
  located under Action




NOTE:
Both systems must have the same SCSI ID and LUN#




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



                                                                 www.open-e.com                                      32
Synchronous Volume Replication with Failover over a LAN
                            Data Server (DSS1)
                            Primary node                        6. Configure iSCSI Failover
                            IP Address:192.168.0.220




 Now, choose the „SETUP” tab,
 next „network” and select
 iSCSI Failover




 In the Failover configuration
 function, check the box Enable
 iSCSI failover functionality.
 Select Network connection
 mode (in this example
 Broadcast). Next enter the
 Secondary node IP and the
 Ping Node IP (must be on the
 same subnet) and click the
 apply button.


                                                       www.open-e.com                         33
Synchronous Volume Replication with Failover over a LAN
                             Data Server (DSS2)
                             Secondary node                      6. Configure iSCSI Failover
                             IP Address:192.168.0.221




 In this node, choose the
 „SETUP” tab, next „network”
 and select iSCSI Failover.



 Now, in Failover
 configuration function , check
 the box Enable iSCSI failover
 functionality. Select Network
 connection mode (in this
 example Broadcast). After
 choose Secondary node on
 localhost enter Primary node
 IP address and click the apply
 button.

                                                        www.open-e.com                         34
Synchronous Volume Replication with Failover over a LAN
                                           Data Server (DSS1)
                                           Primary node                        7. Configure Virtual IP and Auxillary connection
                                           IP Address:192.168.0.220




   Next, select the bond0 within
   iSCSI Failover. In the Virtual
   IP Settings function check box
   Enable virtual IP and enter IP
   address, Netmask, Broadcast,
   and click the apply button.



   By setting the address of the
   secondary node in a Failover
   configuration, automatic
   detection of the interface for
   communication.

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 a
different network subnet then the physical IP Address. To have
additional iSCSI Failover systems, please set this pair in a
different network subnet from the other iSCSI Failover
systems. This limitation will be removed in the future.

                                                                      www.open-e.com                                         35
Synchronous Volume Replication with Failover over a LAN
                               Data Server (DSS1)
                               Primary node                        7. Configure Virtual IP and Auxillary connection
                               IP Address:192.168.0.220




 Now, select the eth1 within
 iSCSI Failover.
 In the Auxiliary connection
 function check box Use this
 network interface to
 communicate between the
 nodes and click the apply
 button.




                                                          www.open-e.com                                         36
Synchronous Volume Replication with Failover over a LAN
                                  Data Server (DSS2)
                                  Secondary node                      7. Configure Virtual IP and Auxillary connection
                                  IP Address:192.168.0.221




 Choose, „SETUP” and
 „network” and „Interfaces”
 from the menu


 Now, select the bond0 within
 iSCSI Failover.
 In the Virtual IP Settings
 function check the box Enable
 virtual IP and enter IP
 address, Netmask, Broadcast,
 and click the apply button.



 By setting the address of the
 primary node in a Failover
 configuration, automatic
 detection of the interface for
 communication.



                                                             www.open-e.com                                         37
Synchronous Volume Replication with Failover over a LAN
                               Data Server (DSS2)
                               Secondary node                      7. Configure Virtual IP and Auxillary connection
                               IP Address:192.168.0.221




 Now, select the eth1 within
 iSCSI Failover.
 In the Auxiliary connection
 function check box Use this
 network interface to
 communicate between the
 nodes and click the apply
 button.




                                                          www.open-e.com                                         38
Synchronous Volume Replication with Failover over a LAN
                               Data Server (DSS1)
                               Primary node                        7. Start Failover Service
                               IP Address:192.168.0.220




 Next, select the iSCSI
 Failover. Move the iSCSI
 Tasks to be used for the
 failover service to the Failover
 Tasks area by clicking
 button       and click apply




                                                          www.open-e.com                       39
Synchronous Volume Replication with Failover over a LAN
                                Data Server (DSS1)
                                Primary node                        8. Start Failover Service
                                IP Address:192.168.0.220




 At this point both nodes are
 ready to start the Failover
 service




                                                           www.open-e.com                       40
Synchronous Volume Replication with Failover over a LAN
                                      Data Server (DSS1)
                                      Primary node                        8. Start Failover Service
                                      IP Address:192.168.0.220




  After clicking the start button
  configuration of both nodes will
  be complete


NOTE:
You can now connect via your iSCSI initiator and use
your targets via the Virtual IP address e.g.
192.168.10.230 (For example, in a Microsoft Windows
environment, download Microsoft iSCSI Initiator ver 2.0
or later).
                                                                 www.open-e.com                       41
Synchronous Volume Replication with Failover over a LAN
                                 Data Server (DSS1)
                                 Primary node                        8. Start Failover Service
                                 IP Address:192.168.0.220




 After start Failover, check the
 status in Failover status
 function. All must read OK. In
 the task status, the destination
 volume must be consistent



  iSCSI Failover/Volume Replication




                                                            www.open-e.com                       42
Synchronous Volume Replication with Failover over a LAN
                                Data Server (DSS1)
                                Primary node                        9. Test Failover Function
                                IP Address:192.168.0.220




 In order to test Failover in
 Manual Failover, function,
 click on the Manual failover
 button.



                                                           www.open-e.com                       43
Synchronous Volume Replication with Failover over a LAN
                             Data Server (DSS1)
                             Primary node                        9. Test Failover Function
                             IP Address:192.168.0.220




 After clicking on the Manual
 failover button, primary node
 enters suspend mode




                                                        www.open-e.com                       44
Synchronous Volume Replication with Failover over a LAN
                             Data Server (DSS1)
                             Primary node                        9. Test Failover Function
                             IP Address:192.168.0.220




 The Failover status function
 shows the Global status of the
 primary node. Status service is
 in suspend mode and the node
 is inactive.




                                                        www.open-e.com                       45
Synchronous Volume Replication with Failover over a LAN
                            Data Server (DSS2)
                            Secondary node                      9. Test Failover Function
                            IP Address:192.168.0.221




 In Failover status function
 Global status shows the status
 of the secondary node. The
 service status is degraded and
 Node status is active.




                                                       www.open-e.com                       46
Synchronous Volume Replication with Failover over a LAN
                            Data Server (DSS2)
                            Secondary node                      10. Run Failback Function
                            IP Address:192.168.0.221




 In order to run Failback in
 Failover manager function click
 on the Sync volumes button
 first.




                                                       www.open-e.com                       47
Synchronous Volume Replication with Failover over a LAN
                              Data Server (DSS2)
                              Secondary node                      10. Run Failback Function
                              IP Address:192.168.0.221




 After synchronization the task
 status of the destination volume
 must be Consistent




                                                         www.open-e.com                       48
Synchronous Volume Replication with Failover over a LAN
                                 Data Server (DSS2)
                                 Secondary node                      10. Run Failback Function
                                 IP Address:192.168.0.221




 In order to return the active
 server state to the Primary
 server click on the Failback
 button



                                                            www.open-e.com                       49
Synchronous Volume Replication with Failover over a LAN
                               Data Server (DSS1)
                               Primary node                        10. Run Failback Function
                               IP Address:192.168.0.220




 After clicking on Failback
 button (in Failover manager
 function on Secondary node)
 Primary node is now active.




                                                          www.open-e.com                       50
Synchronous Volume Replication with Failover over a LAN
                                 Data Server (DSS1)
                                 Primary node                        10. Run Failback Function
                                 IP Address:192.168.0.220




 Primary node is active again
 and ready for Failover.



 iSCSI Failover/Volume Replication




 The configuration and testing of
 iSCSI Failover/Failback is now
           complete.

                                                            www.open-e.com                       51
Thank you!




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

Más contenido relacionado

La actualidad más candente

Intel ESB2 ASF Firmware Update
Intel ESB2 ASF Firmware UpdateIntel ESB2 ASF Firmware Update
Intel ESB2 ASF Firmware Updatewebhostingguy
 
Exadata db node update
Exadata db node updateExadata db node update
Exadata db node updatepat2001
 
Storage interface sata_pata
Storage interface sata_pataStorage interface sata_pata
Storage interface sata_pataPREMAL GAJJAR
 
managing your network environment
managing your network environmentmanaging your network environment
managing your network environmentscooby_doo
 
Exadata cell update
Exadata cell updateExadata cell update
Exadata cell updatepat2001
 
Cellular technology with Embedded Linux - COSCUP 2016
Cellular technology with Embedded Linux - COSCUP 2016Cellular technology with Embedded Linux - COSCUP 2016
Cellular technology with Embedded Linux - COSCUP 2016SZ Lin
 
DPDK & Layer 4 Packet Processing
DPDK & Layer 4 Packet ProcessingDPDK & Layer 4 Packet Processing
DPDK & Layer 4 Packet ProcessingMichelle Holley
 
Saad baig practical file
Saad baig practical fileSaad baig practical file
Saad baig practical fileSaadBaig33
 
DPDK summit 2015: It's kind of fun to do the impossible with DPDK
DPDK summit 2015: It's kind of fun  to do the impossible with DPDKDPDK summit 2015: It's kind of fun  to do the impossible with DPDK
DPDK summit 2015: It's kind of fun to do the impossible with DPDKLagopus SDN/OpenFlow switch
 
Linux advanced concepts - Part 1
Linux advanced concepts - Part 1Linux advanced concepts - Part 1
Linux advanced concepts - Part 1NAILBITER
 
DPDK Summit - 08 Sept 2014 - 6WIND - High Perf Networking Leveraging the DPDK...
DPDK Summit - 08 Sept 2014 - 6WIND - High Perf Networking Leveraging the DPDK...DPDK Summit - 08 Sept 2014 - 6WIND - High Perf Networking Leveraging the DPDK...
DPDK Summit - 08 Sept 2014 - 6WIND - High Perf Networking Leveraging the DPDK...Jim St. Leger
 
DPDK Summit 2015 - Aspera - Charles Shiflett
DPDK Summit 2015 - Aspera - Charles ShiflettDPDK Summit 2015 - Aspera - Charles Shiflett
DPDK Summit 2015 - Aspera - Charles ShiflettJim St. Leger
 
Sonifex netlog-dscribe-products
Sonifex netlog-dscribe-productsSonifex netlog-dscribe-products
Sonifex netlog-dscribe-productsRadikal Ltd.
 

La actualidad más candente (20)

Technotrend
TechnotrendTechnotrend
Technotrend
 
Intel ESB2 ASF Firmware Update
Intel ESB2 ASF Firmware UpdateIntel ESB2 ASF Firmware Update
Intel ESB2 ASF Firmware Update
 
Exadata db node update
Exadata db node updateExadata db node update
Exadata db node update
 
Userspace networking
Userspace networkingUserspace networking
Userspace networking
 
Storage interface sata_pata
Storage interface sata_pataStorage interface sata_pata
Storage interface sata_pata
 
managing your network environment
managing your network environmentmanaging your network environment
managing your network environment
 
Exadata cell update
Exadata cell updateExadata cell update
Exadata cell update
 
100 M pps on PC.
100 M pps on PC.100 M pps on PC.
100 M pps on PC.
 
Cellular technology with Embedded Linux - COSCUP 2016
Cellular technology with Embedded Linux - COSCUP 2016Cellular technology with Embedded Linux - COSCUP 2016
Cellular technology with Embedded Linux - COSCUP 2016
 
IBM Flex System EN4023 10Gb Scalable Switch
IBM Flex System EN4023 10Gb Scalable Switch IBM Flex System EN4023 10Gb Scalable Switch
IBM Flex System EN4023 10Gb Scalable Switch
 
DPDK & Layer 4 Packet Processing
DPDK & Layer 4 Packet ProcessingDPDK & Layer 4 Packet Processing
DPDK & Layer 4 Packet Processing
 
Saad baig practical file
Saad baig practical fileSaad baig practical file
Saad baig practical file
 
Rac on NFS
Rac on NFSRac on NFS
Rac on NFS
 
DPDK summit 2015: It's kind of fun to do the impossible with DPDK
DPDK summit 2015: It's kind of fun  to do the impossible with DPDKDPDK summit 2015: It's kind of fun  to do the impossible with DPDK
DPDK summit 2015: It's kind of fun to do the impossible with DPDK
 
Linux advanced concepts - Part 1
Linux advanced concepts - Part 1Linux advanced concepts - Part 1
Linux advanced concepts - Part 1
 
DPDK Summit - 08 Sept 2014 - 6WIND - High Perf Networking Leveraging the DPDK...
DPDK Summit - 08 Sept 2014 - 6WIND - High Perf Networking Leveraging the DPDK...DPDK Summit - 08 Sept 2014 - 6WIND - High Perf Networking Leveraging the DPDK...
DPDK Summit - 08 Sept 2014 - 6WIND - High Perf Networking Leveraging the DPDK...
 
DPDK Summit 2015 - Aspera - Charles Shiflett
DPDK Summit 2015 - Aspera - Charles ShiflettDPDK Summit 2015 - Aspera - Charles Shiflett
DPDK Summit 2015 - Aspera - Charles Shiflett
 
Batel f re v66
Batel f re v66Batel f re v66
Batel f re v66
 
Sonifex netlog-dscribe-products
Sonifex netlog-dscribe-productsSonifex netlog-dscribe-products
Sonifex netlog-dscribe-products
 
Dpdk performance
Dpdk performanceDpdk performance
Dpdk performance
 

Destacado

Reference: Umeng Insight Report: China Mobile Internet 2012 Review
Reference: Umeng Insight Report: China Mobile Internet 2012 ReviewReference: Umeng Insight Report: China Mobile Internet 2012 Review
Reference: Umeng Insight Report: China Mobile Internet 2012 ReviewC. Keiko Funahashi
 
xcel energy PSCO_Q106_10Q
xcel energy PSCO_Q106_10Qxcel energy PSCO_Q106_10Q
xcel energy PSCO_Q106_10Qfinance26
 
Brokers guide to selling hud homes
Brokers guide to selling hud homesBrokers guide to selling hud homes
Brokers guide to selling hud homesJack Gross
 
10 things to learn from Bokete
10 things to learn from Bokete10 things to learn from Bokete
10 things to learn from BoketeYusuke Wada
 

Destacado (7)

Science Project MC
Science Project MCScience Project MC
Science Project MC
 
Reference: Umeng Insight Report: China Mobile Internet 2012 Review
Reference: Umeng Insight Report: China Mobile Internet 2012 ReviewReference: Umeng Insight Report: China Mobile Internet 2012 Review
Reference: Umeng Insight Report: China Mobile Internet 2012 Review
 
xcel energy PSCO_Q106_10Q
xcel energy PSCO_Q106_10Qxcel energy PSCO_Q106_10Q
xcel energy PSCO_Q106_10Q
 
Notacd11
Notacd11Notacd11
Notacd11
 
Digitale Kruimels v2b
Digitale Kruimels v2bDigitale Kruimels v2b
Digitale Kruimels v2b
 
Brokers guide to selling hud homes
Brokers guide to selling hud homesBrokers guide to selling hud homes
Brokers guide to selling hud homes
 
10 things to learn from Bokete
10 things to learn from Bokete10 things to learn from Bokete
10 things to learn from Bokete
 

Similar a Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Broadcast

12 christian ferber xen_server_advanced
12 christian ferber xen_server_advanced12 christian ferber xen_server_advanced
12 christian ferber xen_server_advancedDigicomp Academy AG
 
Shak larry-jeder-perf-and-tuning-summit14-part2-final
Shak larry-jeder-perf-and-tuning-summit14-part2-finalShak larry-jeder-perf-and-tuning-summit14-part2-final
Shak larry-jeder-perf-and-tuning-summit14-part2-finalTommy Lee
 
Introduction to National Supercomputer center in Tianjin TH-1A Supercomputer
Introduction to National Supercomputer center in Tianjin TH-1A SupercomputerIntroduction to National Supercomputer center in Tianjin TH-1A Supercomputer
Introduction to National Supercomputer center in Tianjin TH-1A SupercomputerFörderverein Technische Fakultät
 
Oracle Database Appliance RAC in a box Some Strings Attached
Oracle Database Appliance RAC in a box Some Strings AttachedOracle Database Appliance RAC in a box Some Strings Attached
Oracle Database Appliance RAC in a box Some Strings AttachedFuad Arshad
 
Os Madsen Block
Os Madsen BlockOs Madsen Block
Os Madsen Blockoscon2007
 
Network Troubleshooting - Part 2
Network Troubleshooting - Part 2Network Troubleshooting - Part 2
Network Troubleshooting - Part 2SolarWinds
 
NetApp C-mode for 7 mode engineers
NetApp C-mode for 7 mode engineersNetApp C-mode for 7 mode engineers
NetApp C-mode for 7 mode engineerssubtitle
 
Cache-partitioning
Cache-partitioningCache-partitioning
Cache-partitioningdavidkftam
 
Key-value databases in practice Redis @ DotNetToscana
Key-value databases in practice Redis @ DotNetToscanaKey-value databases in practice Redis @ DotNetToscana
Key-value databases in practice Redis @ DotNetToscanaMatteo Baglini
 
イマドキなNetwork/IO
イマドキなNetwork/IOイマドキなNetwork/IO
イマドキなNetwork/IOTakuya ASADA
 
VDI storage and storage virtualization
VDI storage and storage virtualizationVDI storage and storage virtualization
VDI storage and storage virtualizationSisimon Soman
 
L3DSR - Overcoming Layer 2 Limitations of Direct Server Return Load Balancing
L3DSR - Overcoming Layer 2 Limitations of Direct Server Return Load BalancingL3DSR - Overcoming Layer 2 Limitations of Direct Server Return Load Balancing
L3DSR - Overcoming Layer 2 Limitations of Direct Server Return Load BalancingJan Schaumann
 
Challenges in mixed signal
Challenges in mixed signal Challenges in mixed signal
Challenges in mixed signal chiportal
 
Pentesting layer 2 protocols
Pentesting layer 2 protocolsPentesting layer 2 protocols
Pentesting layer 2 protocolsAbdessamad TEMMAR
 
ArcGIS Server a Brief Synopsis
ArcGIS Server a Brief SynopsisArcGIS Server a Brief Synopsis
ArcGIS Server a Brief Synopsisewug
 
Approaches for Power Management Verification of SOC
Approaches for Power Management Verification of SOC Approaches for Power Management Verification of SOC
Approaches for Power Management Verification of SOC DVClub
 
3.5 SDN CloudStack Developer Day
3.5  SDN CloudStack Developer Day3.5  SDN CloudStack Developer Day
3.5 SDN CloudStack Developer DayKimihiko Kitase
 
Practice and challenges from building IaaS
Practice and challenges from building IaaSPractice and challenges from building IaaS
Practice and challenges from building IaaSShawn Zhu
 

Similar a Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Broadcast (20)

12 christian ferber xen_server_advanced
12 christian ferber xen_server_advanced12 christian ferber xen_server_advanced
12 christian ferber xen_server_advanced
 
Shak larry-jeder-perf-and-tuning-summit14-part2-final
Shak larry-jeder-perf-and-tuning-summit14-part2-finalShak larry-jeder-perf-and-tuning-summit14-part2-final
Shak larry-jeder-perf-and-tuning-summit14-part2-final
 
Introduction to National Supercomputer center in Tianjin TH-1A Supercomputer
Introduction to National Supercomputer center in Tianjin TH-1A SupercomputerIntroduction to National Supercomputer center in Tianjin TH-1A Supercomputer
Introduction to National Supercomputer center in Tianjin TH-1A Supercomputer
 
Oracle Database Appliance RAC in a box Some Strings Attached
Oracle Database Appliance RAC in a box Some Strings AttachedOracle Database Appliance RAC in a box Some Strings Attached
Oracle Database Appliance RAC in a box Some Strings Attached
 
Os Madsen Block
Os Madsen BlockOs Madsen Block
Os Madsen Block
 
Network Troubleshooting - Part 2
Network Troubleshooting - Part 2Network Troubleshooting - Part 2
Network Troubleshooting - Part 2
 
NetApp C-mode for 7 mode engineers
NetApp C-mode for 7 mode engineersNetApp C-mode for 7 mode engineers
NetApp C-mode for 7 mode engineers
 
Cache-partitioning
Cache-partitioningCache-partitioning
Cache-partitioning
 
Key-value databases in practice Redis @ DotNetToscana
Key-value databases in practice Redis @ DotNetToscanaKey-value databases in practice Redis @ DotNetToscana
Key-value databases in practice Redis @ DotNetToscana
 
イマドキなNetwork/IO
イマドキなNetwork/IOイマドキなNetwork/IO
イマドキなNetwork/IO
 
VDI storage and storage virtualization
VDI storage and storage virtualizationVDI storage and storage virtualization
VDI storage and storage virtualization
 
L3DSR - Overcoming Layer 2 Limitations of Direct Server Return Load Balancing
L3DSR - Overcoming Layer 2 Limitations of Direct Server Return Load BalancingL3DSR - Overcoming Layer 2 Limitations of Direct Server Return Load Balancing
L3DSR - Overcoming Layer 2 Limitations of Direct Server Return Load Balancing
 
Challenges in mixed signal
Challenges in mixed signal Challenges in mixed signal
Challenges in mixed signal
 
Pentesting layer 2 protocols
Pentesting layer 2 protocolsPentesting layer 2 protocols
Pentesting layer 2 protocols
 
Server 2008 R2 Yeniliklər
Server 2008 R2 YeniliklərServer 2008 R2 Yeniliklər
Server 2008 R2 Yeniliklər
 
ArcGIS Server a Brief Synopsis
ArcGIS Server a Brief SynopsisArcGIS Server a Brief Synopsis
ArcGIS Server a Brief Synopsis
 
Approaches for Power Management Verification of SOC
Approaches for Power Management Verification of SOC Approaches for Power Management Verification of SOC
Approaches for Power Management Verification of SOC
 
Ibm cell
Ibm cell Ibm cell
Ibm cell
 
3.5 SDN CloudStack Developer Day
3.5  SDN CloudStack Developer Day3.5  SDN CloudStack Developer Day
3.5 SDN CloudStack Developer Day
 
Practice and challenges from building IaaS
Practice and challenges from building IaaSPractice and challenges from building IaaS
Practice and challenges from building IaaS
 

Más de open-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 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 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 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
 
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
 
Open-E DSS V7 Active-Passive iSCSI Failover
Open-E DSS V7 Active-Passive iSCSI FailoverOpen-E DSS V7 Active-Passive iSCSI Failover
Open-E DSS V7 Active-Passive iSCSI Failoveropen-e
 
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)open-e
 
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 DSS V7 Active-Active iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Active iSCSI Failover on Intel Server SystemsOpen-E DSS V7 Active-Active iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Active iSCSI Failover on Intel Server Systemsopen-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
 
Description of Open-E Snapshot
Description of Open-E SnapshotDescription of Open-E Snapshot
Description of Open-E Snapshotopen-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 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
 
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
 
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
 
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
 

Más de open-e (19)

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 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 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 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
 
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 DSS V7 Active-Passive iSCSI Failover
Open-E DSS V7 Active-Passive iSCSI FailoverOpen-E DSS V7 Active-Passive iSCSI Failover
Open-E DSS V7 Active-Passive iSCSI Failover
 
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
Open-E DSS V7 Active-Active Load Balanced iSCSI HA Cluster (without bonding)
 
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 DSS V7 Active-Active iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Active iSCSI Failover on Intel Server SystemsOpen-E DSS V7 Active-Active iSCSI Failover on Intel Server Systems
Open-E DSS V7 Active-Active iSCSI Failover on Intel Server Systems
 
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
 
Description of Open-E Snapshot
Description of Open-E SnapshotDescription of Open-E Snapshot
Description of Open-E Snapshot
 
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 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
 
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
 
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
 
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
 

Último

Designing IA for AI - Information Architecture Conference 2024
Designing IA for AI - Information Architecture Conference 2024Designing IA for AI - Information Architecture Conference 2024
Designing IA for AI - Information Architecture Conference 2024Enterprise Knowledge
 
WordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your BrandWordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your Brandgvaughan
 
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr LapshynFwdays
 
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationBeyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationSafe Software
 
Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024Scott Keck-Warren
 
DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsSergiu Bodiu
 
Commit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyCommit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyAlfredo García Lavilla
 
Training state-of-the-art general text embedding
Training state-of-the-art general text embeddingTraining state-of-the-art general text embedding
Training state-of-the-art general text embeddingZilliz
 
Search Engine Optimization SEO PDF for 2024.pdf
Search Engine Optimization SEO PDF for 2024.pdfSearch Engine Optimization SEO PDF for 2024.pdf
Search Engine Optimization SEO PDF for 2024.pdfRankYa
 
CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):comworks
 
Vector Databases 101 - An introduction to the world of Vector Databases
Vector Databases 101 - An introduction to the world of Vector DatabasesVector Databases 101 - An introduction to the world of Vector Databases
Vector Databases 101 - An introduction to the world of Vector DatabasesZilliz
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024Lorenzo Miniero
 
Streamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupStreamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupFlorian Wilhelm
 
AI as an Interface for Commercial Buildings
AI as an Interface for Commercial BuildingsAI as an Interface for Commercial Buildings
AI as an Interface for Commercial BuildingsMemoori
 
Install Stable Diffusion in windows machine
Install Stable Diffusion in windows machineInstall Stable Diffusion in windows machine
Install Stable Diffusion in windows machinePadma Pradeep
 
Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Manik S Magar
 
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024BookNet Canada
 
Dev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebDev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebUiPathCommunity
 
Developer Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLDeveloper Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLScyllaDB
 
Unleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubUnleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubKalema Edgar
 

Último (20)

Designing IA for AI - Information Architecture Conference 2024
Designing IA for AI - Information Architecture Conference 2024Designing IA for AI - Information Architecture Conference 2024
Designing IA for AI - Information Architecture Conference 2024
 
WordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your BrandWordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your Brand
 
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
 
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationBeyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
 
Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024
 
DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platforms
 
Commit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyCommit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easy
 
Training state-of-the-art general text embedding
Training state-of-the-art general text embeddingTraining state-of-the-art general text embedding
Training state-of-the-art general text embedding
 
Search Engine Optimization SEO PDF for 2024.pdf
Search Engine Optimization SEO PDF for 2024.pdfSearch Engine Optimization SEO PDF for 2024.pdf
Search Engine Optimization SEO PDF for 2024.pdf
 
CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):
 
Vector Databases 101 - An introduction to the world of Vector Databases
Vector Databases 101 - An introduction to the world of Vector DatabasesVector Databases 101 - An introduction to the world of Vector Databases
Vector Databases 101 - An introduction to the world of Vector Databases
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024
 
Streamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project SetupStreamlining Python Development: A Guide to a Modern Project Setup
Streamlining Python Development: A Guide to a Modern Project Setup
 
AI as an Interface for Commercial Buildings
AI as an Interface for Commercial BuildingsAI as an Interface for Commercial Buildings
AI as an Interface for Commercial Buildings
 
Install Stable Diffusion in windows machine
Install Stable Diffusion in windows machineInstall Stable Diffusion in windows machine
Install Stable Diffusion in windows machine
 
Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!
 
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
Transcript: New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
 
Dev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebDev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio Web
 
Developer Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLDeveloper Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQL
 
Unleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubUnleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding Club
 

Open-E DSS V6 Synchronous Volume Replication With Failover over a LAN with Broadcast

  • 1. Step-by-Step Guide to Synchronous Volume Replication (Block Based) with Failover over a LAN (with broadcast) Supported by Open-E ® DSS™ Software Version: DSS ver. 6.00 up50 Presentation updated: September 2010
  • 2. Synchronous Volume Replication with Failover over a LAN  Open-E DSS Synchronous Volume Replication with Failover is a fault tolerance process via iSCSI volume replication, that creates mirrored target data volumes. • 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 continued as usual. www.open-e.com 2
  • 3. Synchronous Volume Replication with Failover over a LAN VOLUME REPLICATION WITH FAILOVER BETWEEN TWO SYSTEMS WITHIN ONE LAN Recommended Resources • Key Hardware (two systems)  x86 compatible  RAID Controller with Battery Backup Unit  HDD‘s  Network Interface Cards  Ping Node (ping node it is any permanently (24/7) available host in the network. In particular case the ping node function can be performed by the server storing the data on the iSCSI failover volume). • Software  Open-E DSS V6, 2 units Benefits • Eliminate business disruption • Data Redundancy over a LAN • Switch Redundancy Disadvantages • High cost of solution • Natural disasters (earthquake, fire, flood...) can destroy local systems www.open-e.com 3
  • 4. Synchronous Volume Replication with Failover over a LAN • Data is written and read to System 1 (primary) • Data is continually replicated to System 2 (secondary) Heartbeat Volume Replication RAID System 1 RAID System 2 Primary Secondary PING NODE Control Write Data Read Data www.open-e.com 4
  • 5. Synchronous Volume Replication with Failover over a LAN • In case system malfunction or power failure or lost network connection of the System1 (primary), the server will send an e-mail Notification to the administrator. • After a few seconds Automatic Failover is executed and users are switched to System 2 (secondary). X Heartbeat RAID System 1 RAID System 2 Primary Secondary PING NODE Control Write Data Read Data www.open-e.com 5
  • 6. Synchronous Volume Replication with Failover over a LAN • After switching, the replicated volume is available on System 2 (secondary) X RAID System 1 Primary RAID System 2 Secondary PING NODE Write Data Read Data www.open-e.com 6
  • 7. Synchronous Volume Replication with Failover over a LAN 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 Group, iSCSI Volume • Configure Volume Replication mode (destination mode) – settings mirror IP address 3. Configure the Primary node • Create a Volume Group, iSCSI Volume • Configure Volume Replication mode (source mode) – settings mirror IP address, creating Volume Replication task and start replication task. • Create new target on Secondary node • Create new target on Primary node • Configure iSCSI Failover (primary and secondary node) • Configure virtual IP and Auxiliary connection • Start Failover Service • Test Failover Function • Run Failback Function www.open-e.com 7
  • 8. Synchronous Volume Replication with Failover over a LAN Hardware Requirements: To run the Volume Replication with Failover, two DSS systems 1. Hardware Configuration are required. Both servers must be located and working in the Local Area Network. See below configurations for examples: PING NODE IP Address : 192.168.2.106 Data Server (DSS1) Data Server (DSS2) Primary node Control Secondary node IP Address:192.168.0.220 IP Address:192.168.0.221 Switch 1 RAID System 1 RAID System 2 Switch 2 Primary Secondary Port used for WEB GUI management Port used for WEB GUI management IP:192.168.0.220 eth0 eth0 IP:192.168.0.221 Volume Replication , Optional: Volume Replication , Auxiliary connection (Heartbeat) This path can be Auxiliary connection (Heartbeat) IP:192.168.1.220 eth1 directly point-to-point eth1 IP:192.168.1.221 connected eth1 to eth1 Client Storage Access, Client Storage Access, Auxiliary connection (Heartbeat) (without the switch). Auxiliary connection (Heartbeat) bond0 IP:192.168.2.220 (eth2, eth3) (eth2, eth3) IP:192.168.2.221 bond0 Bonding IP Bonding IP Volume Groups (vg00) Volume Groups (vg00) Virtual IP Address:192.168.10.230 (iSCSI Target) iSCSI volume (lv00) iSCSI Failover/Volume Replication (eth1) iSCSI volume (lv00) iSCSI targets iSCSI targets www.open-e.com 8
  • 9. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 1. Hardware Configuration IP Address:192.168.0.221 After logging on the DSS V6 please go to „SETUP” tab, „network” and „Interfaces”. In „Server name” function enter Server name, in this example „dss2” and click apply button. (All connections will be restarted) www.open-e.com 9
  • 10. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 1. Hardware Configuration IP Address:192.168.0.221 Next select eth0 interface and change IP Address from 192.168.0.220 in field IP address to 192.168 .0.221, and click apply button. (This will restart network configuration). www.open-e.com 10
  • 11. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 1. Hardware Configuration IP Address:192.168.0.221 Next select eth1 interface and change IP address from 192.168.1.220 in field IP address to 192.168 .1.221 and click apply button. www.open-e.com 11
  • 12. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 1. Hardware Configuration IP Address:192.168.0.221 Again select „Interfaces” and in Create new bond interface function check two boxes with eth2 and eth3. In field Create select bonding mode. In this example select New balance-rr. Next enter IP Address in field Adress IP 192.168 .2.221, Netmask, and click create button. www.open-e.com 12
  • 13. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 1. Hardware Configuration IP Address:192.168.0.221 After reloading page on the dss2 server you have configured bond0. Setting of the network interfaces on the secondary node is finished. www.open-e.com 13
  • 14. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 1. Hardware Configuration IP Address:192.168.0.220 After logging on the primary node please go to „SETUP” tab, „network” and „Interfaces”. In „Server name” function enter Server name. In this example enter dss1 and click apply button. (All connection will be restarted). www.open-e.com 14
  • 15. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 1. Hardware Configuration IP Address:192.168.0.220 Again select „Interfaces” and in Create new bond interface function check two boxes with eth2 and eth3. In field Create select mode for bonding. In this example selected New balance-rr.. Next enter IP Address in field Address IP 192.168 .2.220, Netmask, and click create button. www.open-e.com 15
  • 16. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 1. Hardware Configuration IP Address:192.168.0.220 After reloading page on the dss1 server you have configured bond0. Setting of the network interfaces on the secondary node is finished. www.open-e.com 16
  • 17. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 2. Configure the Secondary node IP Address:192.168.0.221 Under the „CONFIGURATION” tab, select „volume manager” and next Vol. Groups. Volume Groups (vg00) In Unit manager function add the selected physical units (Unit S000 or other) to create a new volume group (in this case, vg00) and click apply button www.open-e.com 17
  • 18. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 2. Configure the Secondary node 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. This logical volume will be the destination of the replication process. Next check the box with Use volume replication After assigning an appropriate amount of space for the iSCSI volume, click the apply button www.open-e.com 18
  • 19. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 2. Configure the Secondary node IP Address:192.168.0.221 The destination iSCSI Volume Block I/O is now configured. iSCSI volume (lv0000) www.open-e.com 19
  • 20. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 2. Configure the Secondary node IP Address:192.168.0.221 Now, select the Vol. replication and check the box under Destination and click the apply button Next, under Mirror Server IP function, enter the IP address of the Primary node (in our example, this would be 192.168.1.220) and click the apply button 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.1.220 •Destination: 192.168.1.221 www.open-e.com 20
  • 21. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 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 Volume Groups (vg00) www.open-e.com 21
  • 22. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node 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. This logical volume will be the source of the replication process. Next , check box 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 22
  • 23. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 The source iSCSI Volume Block I/O is now configured. iSCSI volume (lv0000) www.open-e.com 23
  • 24. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 Now, select Vol. replication, and check the box under Source and click the apply button Next , under Mirror Server IP function, enter the IP address of the Secondary node (in our example this would be 192.168.1.221) and click the apply button www.open-e.com 24
  • 25. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 Enter the task name in field Task name next click on the button In the Destination volume field select the appropriate volume (in this example, lv0000) and click create to confirm www.open-e.com 25
  • 26. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 Now, in the Replication task manager function, click on button under to start the Replication task on the Primary node www.open-e.com 26
  • 27. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 In the Replication tasks manager function information is available about the current running replication task. www.open-e.com 27
  • 28. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 Under the „STATUS” tab, select „tasks” and Volume Replication Click on the button with task name (in this case MirrorTask) 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 28
  • 29. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 4. Create new target on the Secondary node IP Address:192.168.0.221 Choose „CONFIGURATION”, „iSCSI target manager” and „Targets” from the menu In the Create new target function, uncheck the box Target Default Name, and enter a name for the new target in the Name field and click apply to confirm. iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 29
  • 30. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 4. Create new target on the Secondary node IP Address:192.168.0.221 Select target0 within the Targets field. To assign a volume to the target, click the button located under Action WARNING: Please do not switch on the write back (WB) cache ! www.open-e.com 30
  • 31. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 5. Create new target on the Primary node IP Address:192.168.0.220 Choose „CONFIGURATION” and „iSCSI target manager” and „Targets” from the menu In the Create new target function, uncheck the box Target Default Name, and enter a name for the new target in the Name field and click apply to confirm iSCSI targets NOTE: Both systems must have the same Target name. www.open-e.com 31
  • 32. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 5. Create new target on the Primary node IP Address:192.168.0.220 Select the target0 within the Targets field To assign a volume to the target, click the button located under Action NOTE: Both systems must have the same SCSI ID and LUN# WARNING: Please do not switch on the write back cache (WB) ! www.open-e.com 32
  • 33. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 6. Configure iSCSI Failover IP Address:192.168.0.220 Now, choose the „SETUP” tab, next „network” and select iSCSI Failover In the Failover configuration function, check the box Enable iSCSI failover functionality. Select Network connection mode (in this example Broadcast). Next enter the Secondary node IP and the Ping Node IP (must be on the same subnet) and click the apply button. www.open-e.com 33
  • 34. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 6. Configure iSCSI Failover IP Address:192.168.0.221 In this node, choose the „SETUP” tab, next „network” and select iSCSI Failover. Now, in Failover configuration function , check the box Enable iSCSI failover functionality. Select Network connection mode (in this example Broadcast). After choose Secondary node on localhost enter Primary node IP address and click the apply button. www.open-e.com 34
  • 35. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 7. Configure Virtual IP and Auxillary connection IP Address:192.168.0.220 Next, select the bond0 within iSCSI Failover. In the Virtual IP Settings function check box Enable virtual IP and enter IP address, Netmask, Broadcast, and click the apply button. By setting the address of the secondary node in a Failover configuration, automatic detection of the interface for communication. 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 a different network subnet then the physical IP Address. To have additional iSCSI Failover systems, please set this pair in a different network subnet from the other iSCSI Failover systems. This limitation will be removed in the future. www.open-e.com 35
  • 36. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 7. Configure Virtual IP and Auxillary connection IP Address:192.168.0.220 Now, select the eth1 within iSCSI Failover. In the Auxiliary connection function check box Use this network interface to communicate between the nodes and click the apply button. www.open-e.com 36
  • 37. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 7. Configure Virtual IP and Auxillary connection IP Address:192.168.0.221 Choose, „SETUP” and „network” and „Interfaces” from the menu Now, select the bond0 within iSCSI Failover. In the Virtual IP Settings function check the box Enable virtual IP and enter IP address, Netmask, Broadcast, and click the apply button. By setting the address of the primary node in a Failover configuration, automatic detection of the interface for communication. www.open-e.com 37
  • 38. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 7. Configure Virtual IP and Auxillary connection IP Address:192.168.0.221 Now, select the eth1 within iSCSI Failover. In the Auxiliary connection function check box Use this network interface to communicate between the nodes and click the apply button. www.open-e.com 38
  • 39. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 7. Start Failover Service IP Address:192.168.0.220 Next, select the iSCSI Failover. Move the iSCSI Tasks to be used for the failover service to the Failover Tasks area by clicking button and click apply www.open-e.com 39
  • 40. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 8. Start Failover Service IP Address:192.168.0.220 At this point both nodes are ready to start the Failover service www.open-e.com 40
  • 41. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 8. Start Failover Service IP Address:192.168.0.220 After clicking the start button configuration of both nodes will be complete NOTE: You can now connect via your iSCSI initiator and use your targets via the Virtual IP address e.g. 192.168.10.230 (For example, in a Microsoft Windows environment, download Microsoft iSCSI Initiator ver 2.0 or later). www.open-e.com 41
  • 42. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 8. Start Failover Service IP Address:192.168.0.220 After start Failover, check the status in Failover status function. All must read OK. In the task status, the destination volume must be consistent iSCSI Failover/Volume Replication www.open-e.com 42
  • 43. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 9. Test Failover Function IP Address:192.168.0.220 In order to test Failover in Manual Failover, function, click on the Manual failover button. www.open-e.com 43
  • 44. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 9. Test Failover Function IP Address:192.168.0.220 After clicking on the Manual failover button, primary node enters suspend mode www.open-e.com 44
  • 45. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 9. Test Failover Function IP Address:192.168.0.220 The Failover status function shows the Global status of the primary node. Status service is in suspend mode and the node is inactive. www.open-e.com 45
  • 46. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 9. Test Failover Function IP Address:192.168.0.221 In Failover status function Global status shows the status of the secondary node. The service status is degraded and Node status is active. www.open-e.com 46
  • 47. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 10. Run Failback Function IP Address:192.168.0.221 In order to run Failback in Failover manager function click on the Sync volumes button first. www.open-e.com 47
  • 48. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 10. Run Failback Function IP Address:192.168.0.221 After synchronization the task status of the destination volume must be Consistent www.open-e.com 48
  • 49. Synchronous Volume Replication with Failover over a LAN Data Server (DSS2) Secondary node 10. Run Failback Function IP Address:192.168.0.221 In order to return the active server state to the Primary server click on the Failback button www.open-e.com 49
  • 50. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 10. Run Failback Function IP Address:192.168.0.220 After clicking on Failback button (in Failover manager function on Secondary node) Primary node is now active. www.open-e.com 50
  • 51. Synchronous Volume Replication with Failover over a LAN Data Server (DSS1) Primary node 10. Run Failback Function IP Address:192.168.0.220 Primary node is active again and ready for Failover. iSCSI Failover/Volume Replication The configuration and testing of iSCSI Failover/Failback is now complete. www.open-e.com 51
  • 52. Thank you! Follow Open-E: www.open-e.com 52