SlideShare ist ein Scribd-Unternehmen logo
1 von 54
Step-by-Step Guide to
           NAS (NFS) Failover
    over a LAN (with unicast)
  Supported by Open-E ® DSS™




Software Version: DSS ver. 6.00 up65
Presentation updated: March 2011
NAS (NFS) Failover over a LAN




 Open-E DSS NAS (NFS) Failover is a fault tolerance process via NAS volume replication, that creates
  mirrored 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
NAS (NFS) 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 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
NAS (NFS) Failover over a LAN
                                      • Data is written and read to System 1 (primary)
                                      • Data is continually replicated to System 2 (secondary)

RAID System 1                                                                           RAID System 2
Primary                                                                                 Secondary
                              Heartbeat

                                 Volume Replication




   PING NODEs




          Control                                                                         Write Data

                                                                      Read Data




                             www.open-e.com                                                             4
NAS (NFS) 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).


RAID System 1                                                                                            RAID System 2
Primary                                                                                                  Secondary




        X
                                      Heartbeat




   PING NODEs




          Control                                                                                          Write Data

                                                                                    Read Data




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

RAID System 1                                                                  RAID System 2
Primary                                                                        Secondary




        X
   PING NODEs




                                                                                Write Data

                                                                   Read Data




                             www.open-e.com                                                    6
NAS (NFS) Failover over a LAN
TO SET UP NAS (NFS) 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, NAS Volume
    •    Configure Volume Replication mode (destination mode) – settings mirror IP address
    •    NFS settings

    3.   Configure the Primary node
    •    Create a Volume Group, NAS Volume
    •    Configure Volume Replication mode (source mode) – settings mirror IP address, creating Volume Replication task and start
         replication task.
    •    NFS settings,
    •    Create and settings new share on primary node.

    4.   Configure Failover (primary and secondary node)
    5.   Select services used in Failover
    6.   Configure virtual IP and Auxiliary connection
    7.   Start Failover Service
    8.   Test Failover Function
    9.   Run Failback Function
                                                          www.open-e.com                                                            7
NAS (NFS) 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 NODEs
                                                                                                            IP Address : 192.168.2.106; 192.168.2.107
Data Server (DSS1)                                                                                                                       Data Server (DSS2)
Primary node                                                                                                                             Secondary node
IP Address:192.168.0.220                                                                                                                  IP Address:192.168.0.221
                                                                                     Control
                                                                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

   NAS volume (lv00)                                      NFS Failover/Volume Replication (eth1)                                           NAS volume (lv00)


   Share (data)                                                                                                                                Share (data)


                                                                    www.open-e.com                                                                                  8
NAS (NFS) 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
NAS (NFS) 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
NAS (NFS) 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
NAS (NFS) 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
NAS (NFS) 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
NAS (NFS) 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
NAS (NFS) 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
NAS (NFS) 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
NAS (NFS) 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
NAS (NFS) 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 NAS
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 NAS
volume, click the apply button


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




The destination NAS Volume is
now configured.



        NAS volume (lv0000)




                                                         www.open-e.com                             19
NAS (NFS) 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 if you are not using a
NAT. Please follow example:
•Source:         192.168.1.220
•Destination: 192.168.1.221
                                                               www.open-e.com                             20
NAS (NFS) Failover over a LAN
                            Data Server (DSS2)
                            Secondary node                      2. Configure the Secondary node
                            IP Address:192.168.0.221




Choose „CONFIGURATION”,
and „NAS settings” from the
menu on the secondary node




In the NAS settings function,
check the box Use NFS, click
apply to confirm.




                                                       www.open-e.com                             21
NAS (NFS) 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                           22
NAS (NFS) 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 NAS
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 NAS
volume, click the apply button

NOTE:
The source and destination volumes must be of
identical size.
                                                           www.open-e.com                           23
NAS (NFS) Failover over a LAN
                             Data Server (DSS1)
                             Primary node                        3. Configure the Primary node
                             IP Address:192.168.0.220




The source NAS Volume is now
configured.



       NAS volume (lv0000)




                                                        www.open-e.com                           24
NAS (NFS) 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                           25
NAS (NFS) 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                           26
NAS (NFS) 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                           27
NAS (NFS) 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                           28
NAS (NFS) 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 NAS Logical Volume via NFS.

                                                              www.open-e.com                           29
NAS (NFS) Failover over a LAN
                            Data Server (DSS1)
                            Primary node                        3. Configure the Primary node
                            IP Address:192.168.0.220




Choose „CONFIGURATION”,
and „NAS settings” from the
menu




In the NAS settings function,
check the box Use NFS, click
apply to confirm.




                                                       www.open-e.com                           30
NAS (NFS) Failover over a LAN
                            Data Server (DSS1)
                            Primary node                        3. Configure the Primary node
                            IP Address:192.168.0.220




Next, choose
„CONFIGURATION”, „NAS
resources” and „Shares” from
the menu.




Enter share name in field
„Name” and click apply to
confirm.




                                                       www.open-e.com                           31
NAS (NFS) Failover over a LAN
                              Data Server (DSS1)
                              Primary node                        3. Configure the Primary node
                              IP Address:192.168.0.220




In the NFS share acces
function, check the box Use
NFS, and click apply to
confirm.




                                                         www.open-e.com                           32
NAS (NFS) Failover over a LAN
                           Data Server (DSS1)
                           Primary node                        4. Configure Failover
                           IP Address:192.168.0.220




Next choose „SETUP”,
„network”, end select Failover
on the primary node.




In the Failover configuration
function, check the box Enable
Failover functionality. Select
Network connection mode (in
this example Unicast) and
select Network interface for
unicast (bond0). 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
NAS (NFS) Failover over a LAN
                              Data Server (DSS2)
                              Secondary node                      4. Configure Failover
                              IP Address:192.168.0.221




Now, select Failover on the
secondary node



Now, in Failover
configuration function , check
the box Enable Failover
functionality. Select Network
connection mode (in this
example Unicast) and select
Network interface for unicast
(bond0). After choose
Secondary node on localhost
enter Primary node IP address
and click the apply button
                                                         www.open-e.com                   34
NAS (NFS) Failover over a LAN
                                                   Data Server (DSS1)
                                                   Primary node                        5. Configure Virtual IP and Auxillary connection
                                                   IP Address:192.168.0.220




   Now, select the bond0 within
   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. This step is
 necessary to complement the
 destination IP address used in
 unicast.
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 Failover systems, please set
this pair in a different network subnet from the other Failover systems. If
the virtual IP must be in the same network subnet, there will be extra
configuration steps required. Please refer to other document which
describe configuration with static routing.

                                                                              www.open-e.com                                         35
NAS (NFS) Failover over a LAN
                           Data Server (DSS1)
                           Primary node                        5. Configure Virtual IP and Auxillary connection
                           IP Address:192.168.0.220




Now, select the eth1 within
Failover.
In the Auxiliary connection
function check box Use this
network interface to
communicate between the
nodes next enter IP address for
Unicast remote IP and click the
apply button.




                                                      www.open-e.com                                         36
NAS (NFS) Failover over a LAN
                             Data Server (DSS2)
                             Secondary node                      5. 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
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. This step is
necessary to complement the
destination IP address used in
unicast.
                                                        www.open-e.com                                         37
NAS (NFS) Failover over a LAN
                           Data Server (DSS2)
                           Secondary node                      5. Configure Virtual IP and Auxillary connection
                           IP Address:192.168.0.221




Now, select the eth1 within
Failover.
In the Auxiliary connection
function check box Use this
network interface to
communicate between the
nodes next enter IP address for
Unicast remote IP and click the
apply button.




                                                      www.open-e.com                                         38
NAS (NFS) Failover over a LAN
                                  Data Server (DSS1)
                                  Primary node                        6. Select services used in Failover
                                  IP Address:192.168.0.220




  Now, in Failover services
  function (on primary node),
  uncheck the box with iSCSI,
  then check box witch NFS, and
  click the apply button




NOTE:
Selecting NFS in Failover service will reduce the
access to shares on volumes used in Failover
Tasks to NFS access only. Activating Failover
Service will automatically deactivate all other
services for those shares.

                                                             www.open-e.com                                 39
NAS (NFS) Failover over a LAN
                             Data Server (DSS1)
                             Primary node                        7. Start Failover Service
                             IP Address:192.168.0.220




Next, in the Failover Tasks
function, move the Failover
Tasks to be used for the failover
service to the Failover Tasks
area clicking      button and
click apply




                                                        www.open-e.com                       40
NAS (NFS) Failover over a LAN
                               Data Server (DSS1)
                               Primary node                        7. 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                       41
NAS (NFS) Failover over a LAN
                                 Data Server (DSS1)
                                 Primary node                        7. 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 mount the NFS client computers.


                                                            www.open-e.com                       42
NAS (NFS) Failover over a LAN
                               Data Server (DSS1)
                               Primary node                        7. Start Failover Service
                               IP Address:192.168.0.220




After start Failover, check the
status in Failover status
function. All must read OK



 NAS Failover/Volume Replication




                                                          www.open-e.com                       43
NAS (NFS) Failover over a LAN
                               Data Server (DSS1)
                               Primary node                        7. Start Failover Service
                               IP Address:192.168.0.220




In the Task status, (after
clickling    button) the
destination volumes must be
consistent.



 NAS Failover/Volume Replication




                                                          www.open-e.com                       44
NAS (NFS) Failover over a LAN
                               Data Server (DSS1)
                               Primary node                        8. 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                       45
NAS (NFS) Failover over a LAN
                            Data Server (DSS1)
                            Primary node                        8. 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                       46
NAS (NFS) Failover over a LAN
                            Data Server (DSS1)
                            Primary node                        8. 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                       47
NAS (NFS) Failover over a LAN
                           Data Server (DSS2)
                           Secondary node                      8. 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                       48
NAS (NFS) Failover over a LAN
                           Data Server (DSS2)
                           Secondary node                      9. 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                      49
NAS (NFS) Failover over a LAN
                             Data Server (DSS2)
                             Secondary node                      9. 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                      50
NAS (NFS) Failover over a LAN
                                Data Server (DSS2)
                                Secondary node                      9. 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                      51
NAS (NFS) Failover over a LAN
                              Data Server (DSS1)
                              Primary node                        9. 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                      52
NAS (NFS) Failover over a LAN
                               Data Server (DSS1)
                               Primary node                        9. Run Failback Function
                               IP Address:192.168.0.220




Primary node is active again
and ready for Failover.



Failover/Volume Replication




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

                                                          www.open-e.com                      53
Thank you!




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

Weitere ähnliche Inhalte

Was ist angesagt?

Intel DPDK Step by Step instructions
Intel DPDK Step by Step instructionsIntel DPDK Step by Step instructions
Intel DPDK Step by Step instructionsHisaki Ohara
 
Linux advanced concepts - Part 1
Linux advanced concepts - Part 1Linux advanced concepts - Part 1
Linux advanced concepts - Part 1NAILBITER
 
Lagopus presentation on 14th Annual ON*VECTOR International Photonics Workshop
Lagopus presentation on 14th Annual ON*VECTOR International Photonics WorkshopLagopus presentation on 14th Annual ON*VECTOR International Photonics Workshop
Lagopus presentation on 14th Annual ON*VECTOR International Photonics WorkshopLagopus SDN/OpenFlow switch
 
OVS and DPDK - T.F. Herbert, K. Traynor, M. Gray
OVS and DPDK - T.F. Herbert, K. Traynor, M. GrayOVS and DPDK - T.F. Herbert, K. Traynor, M. Gray
OVS and DPDK - T.F. Herbert, K. Traynor, M. Grayharryvanhaaren
 
In-Network Acceleration with FPGA (MEMO)
In-Network Acceleration with FPGA (MEMO)In-Network Acceleration with FPGA (MEMO)
In-Network Acceleration with FPGA (MEMO)Naoto MATSUMOTO
 
Intel ESB2 ASF Firmware Update
Intel ESB2 ASF Firmware UpdateIntel ESB2 ASF Firmware Update
Intel ESB2 ASF Firmware Updatewebhostingguy
 
DPDK & Layer 4 Packet Processing
DPDK & Layer 4 Packet ProcessingDPDK & Layer 4 Packet Processing
DPDK & Layer 4 Packet ProcessingMichelle Holley
 
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
 
RHCE FINAL Questions and Answers
RHCE FINAL Questions and AnswersRHCE FINAL Questions and Answers
RHCE FINAL Questions and AnswersRadien software
 
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 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
 
Storage interface sata_pata
Storage interface sata_pataStorage interface sata_pata
Storage interface sata_pataPREMAL GAJJAR
 
IPv6 Fundamentals & Securities
IPv6 Fundamentals & SecuritiesIPv6 Fundamentals & Securities
IPv6 Fundamentals & SecuritiesDon Anto
 

Was ist angesagt? (20)

Intel DPDK Step by Step instructions
Intel DPDK Step by Step instructionsIntel DPDK Step by Step instructions
Intel DPDK Step by Step instructions
 
Linux advanced concepts - Part 1
Linux advanced concepts - Part 1Linux advanced concepts - Part 1
Linux advanced concepts - Part 1
 
Technotrend
TechnotrendTechnotrend
Technotrend
 
Lagopus presentation on 14th Annual ON*VECTOR International Photonics Workshop
Lagopus presentation on 14th Annual ON*VECTOR International Photonics WorkshopLagopus presentation on 14th Annual ON*VECTOR International Photonics Workshop
Lagopus presentation on 14th Annual ON*VECTOR International Photonics Workshop
 
Nextserver Evo
Nextserver EvoNextserver Evo
Nextserver Evo
 
OVS and DPDK - T.F. Herbert, K. Traynor, M. Gray
OVS and DPDK - T.F. Herbert, K. Traynor, M. GrayOVS and DPDK - T.F. Herbert, K. Traynor, M. Gray
OVS and DPDK - T.F. Herbert, K. Traynor, M. Gray
 
In-Network Acceleration with FPGA (MEMO)
In-Network Acceleration with FPGA (MEMO)In-Network Acceleration with FPGA (MEMO)
In-Network Acceleration with FPGA (MEMO)
 
Intel ESB2 ASF Firmware Update
Intel ESB2 ASF Firmware UpdateIntel ESB2 ASF Firmware Update
Intel ESB2 ASF Firmware Update
 
100 M pps on PC.
100 M pps on PC.100 M pps on PC.
100 M pps on PC.
 
DPDK & Layer 4 Packet Processing
DPDK & Layer 4 Packet ProcessingDPDK & Layer 4 Packet Processing
DPDK & Layer 4 Packet Processing
 
Userspace networking
Userspace networkingUserspace networking
Userspace networking
 
IPSflexresponse-eng
IPSflexresponse-engIPSflexresponse-eng
IPSflexresponse-eng
 
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 kernel modules
Linux kernel modulesLinux kernel modules
Linux kernel modules
 
Ccnp3 lab 3_3_en
Ccnp3 lab 3_3_enCcnp3 lab 3_3_en
Ccnp3 lab 3_3_en
 
RHCE FINAL Questions and Answers
RHCE FINAL Questions and AnswersRHCE FINAL Questions and Answers
RHCE FINAL Questions and Answers
 
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
 
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...
 
Storage interface sata_pata
Storage interface sata_pataStorage interface sata_pata
Storage interface sata_pata
 
IPv6 Fundamentals & Securities
IPv6 Fundamentals & SecuritiesIPv6 Fundamentals & Securities
IPv6 Fundamentals & Securities
 

Ähnlich wie Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported by Open-E ® DSS™

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
 
Network Troubleshooting - Part 2
Network Troubleshooting - Part 2Network Troubleshooting - Part 2
Network Troubleshooting - Part 2SolarWinds
 
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
 
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
 
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
 
FIWARE Lab architecture, an open point to start the installation of a new region
FIWARE Lab architecture, an open point to start the installation of a new regionFIWARE Lab architecture, an open point to start the installation of a new region
FIWARE Lab architecture, an open point to start the installation of a new regionFernando Lopez Aguilar
 
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
 
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
 
CCNA Routing and Switching Lesson 06 - IOS Basics - Eric Vanderburg
CCNA Routing and Switching Lesson 06 - IOS Basics - Eric VanderburgCCNA Routing and Switching Lesson 06 - IOS Basics - Eric Vanderburg
CCNA Routing and Switching Lesson 06 - IOS Basics - Eric VanderburgEric Vanderburg
 
Practice and challenges from building IaaS
Practice and challenges from building IaaSPractice and challenges from building IaaS
Practice and challenges from building IaaSShawn Zhu
 
Porting Xen Paravirtualization to MIPS Architecture
Porting Xen Paravirtualization to MIPS ArchitecturePorting Xen Paravirtualization to MIPS Architecture
Porting Xen Paravirtualization to MIPS ArchitectureThe Linux Foundation
 
Considerations when implementing_ha_in_dmf
Considerations when implementing_ha_in_dmfConsiderations when implementing_ha_in_dmf
Considerations when implementing_ha_in_dmfhik_lhz
 
ArcGIS Server a Brief Synopsis
ArcGIS Server a Brief SynopsisArcGIS Server a Brief Synopsis
ArcGIS Server a Brief Synopsisewug
 
Strata + Hadoop World 2012: HDFS: Now and Future
Strata + Hadoop World 2012: HDFS: Now and FutureStrata + Hadoop World 2012: HDFS: Now and Future
Strata + Hadoop World 2012: HDFS: Now and FutureCloudera, Inc.
 
延伸Linux关键业务到双活高速NVMe-oF存储-OpenInfraDays-China2018
延伸Linux关键业务到双活高速NVMe-oF存储-OpenInfraDays-China2018延伸Linux关键业务到双活高速NVMe-oF存储-OpenInfraDays-China2018
延伸Linux关键业务到双活高速NVMe-oF存储-OpenInfraDays-China2018Roger Zhou 周志强
 
VDI storage and storage virtualization
VDI storage and storage virtualizationVDI storage and storage virtualization
VDI storage and storage virtualizationSisimon Soman
 
Android Mind Reading: Android Live Memory Analysis with LiME and Volatility
Android Mind Reading: Android Live Memory Analysis with LiME and VolatilityAndroid Mind Reading: Android Live Memory Analysis with LiME and Volatility
Android Mind Reading: Android Live Memory Analysis with LiME and VolatilityJoe Sylve
 
イマドキなNetwork/IO
イマドキなNetwork/IOイマドキなNetwork/IO
イマドキなNetwork/IOTakuya ASADA
 
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
 

Ähnlich wie Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported by Open-E ® DSS™ (20)

12 christian ferber xen_server_advanced
12 christian ferber xen_server_advanced12 christian ferber xen_server_advanced
12 christian ferber xen_server_advanced
 
Network Troubleshooting - Part 2
Network Troubleshooting - Part 2Network Troubleshooting - Part 2
Network Troubleshooting - Part 2
 
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
 
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
 
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
 
FIWARE Lab architecture, an open point to start the installation of a new region
FIWARE Lab architecture, an open point to start the installation of a new regionFIWARE Lab architecture, an open point to start the installation of a new region
FIWARE Lab architecture, an open point to start the installation of a new region
 
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
 
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
 
CCNA Routing and Switching Lesson 06 - IOS Basics - Eric Vanderburg
CCNA Routing and Switching Lesson 06 - IOS Basics - Eric VanderburgCCNA Routing and Switching Lesson 06 - IOS Basics - Eric Vanderburg
CCNA Routing and Switching Lesson 06 - IOS Basics - Eric Vanderburg
 
Practice and challenges from building IaaS
Practice and challenges from building IaaSPractice and challenges from building IaaS
Practice and challenges from building IaaS
 
Porting Xen Paravirtualization to MIPS Architecture
Porting Xen Paravirtualization to MIPS ArchitecturePorting Xen Paravirtualization to MIPS Architecture
Porting Xen Paravirtualization to MIPS Architecture
 
Considerations when implementing_ha_in_dmf
Considerations when implementing_ha_in_dmfConsiderations when implementing_ha_in_dmf
Considerations when implementing_ha_in_dmf
 
ArcGIS Server a Brief Synopsis
ArcGIS Server a Brief SynopsisArcGIS Server a Brief Synopsis
ArcGIS Server a Brief Synopsis
 
Strata + Hadoop World 2012: HDFS: Now and Future
Strata + Hadoop World 2012: HDFS: Now and FutureStrata + Hadoop World 2012: HDFS: Now and Future
Strata + Hadoop World 2012: HDFS: Now and Future
 
延伸Linux关键业务到双活高速NVMe-oF存储-OpenInfraDays-China2018
延伸Linux关键业务到双活高速NVMe-oF存储-OpenInfraDays-China2018延伸Linux关键业务到双活高速NVMe-oF存储-OpenInfraDays-China2018
延伸Linux关键业务到双活高速NVMe-oF存储-OpenInfraDays-China2018
 
VDI storage and storage virtualization
VDI storage and storage virtualizationVDI storage and storage virtualization
VDI storage and storage virtualization
 
Android Mind Reading: Android Live Memory Analysis with LiME and Volatility
Android Mind Reading: Android Live Memory Analysis with LiME and VolatilityAndroid Mind Reading: Android Live Memory Analysis with LiME and Volatility
Android Mind Reading: Android Live Memory Analysis with LiME and Volatility
 
イマドキなNetwork/IO
イマドキなNetwork/IOイマドキなNetwork/IO
イマドキなNetwork/IO
 
Hadoop, Taming Elephants
Hadoop, Taming ElephantsHadoop, Taming Elephants
Hadoop, Taming Elephants
 
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
 

Mehr von 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 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
 

Mehr von open-e (18)

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 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
 

Kürzlich hochgeladen

Spring Boot vs Quarkus the ultimate battle - DevoxxUK
Spring Boot vs Quarkus the ultimate battle - DevoxxUKSpring Boot vs Quarkus the ultimate battle - DevoxxUK
Spring Boot vs Quarkus the ultimate battle - DevoxxUKJago de Vreede
 
Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024The Digital Insurer
 
AXA XL - Insurer Innovation Award Americas 2024
AXA XL - Insurer Innovation Award Americas 2024AXA XL - Insurer Innovation Award Americas 2024
AXA XL - Insurer Innovation Award Americas 2024The Digital Insurer
 
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot TakeoffStrategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoffsammart93
 
Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...apidays
 
Corporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptxCorporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptxRustici Software
 
[BuildWithAI] Introduction to Gemini.pdf
[BuildWithAI] Introduction to Gemini.pdf[BuildWithAI] Introduction to Gemini.pdf
[BuildWithAI] Introduction to Gemini.pdfSandro Moreira
 
Strategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a FresherStrategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a FresherRemote DBA Services
 
Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native ApplicationsWSO2
 
Ransomware_Q4_2023. The report. [EN].pdf
Ransomware_Q4_2023. The report. [EN].pdfRansomware_Q4_2023. The report. [EN].pdf
Ransomware_Q4_2023. The report. [EN].pdfOverkill Security
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FMESafe Software
 
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...apidays
 
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdfRising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdfOrbitshub
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FMESafe Software
 
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAndrey Devyatkin
 
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerHow to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerThousandEyes
 
ICT role in 21st century education and its challenges
ICT role in 21st century education and its challengesICT role in 21st century education and its challenges
ICT role in 21st century education and its challengesrafiqahmad00786416
 
Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...
Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...
Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...Orbitshub
 
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...apidays
 
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, AdobeApidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobeapidays
 

Kürzlich hochgeladen (20)

Spring Boot vs Quarkus the ultimate battle - DevoxxUK
Spring Boot vs Quarkus the ultimate battle - DevoxxUKSpring Boot vs Quarkus the ultimate battle - DevoxxUK
Spring Boot vs Quarkus the ultimate battle - DevoxxUK
 
Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024
 
AXA XL - Insurer Innovation Award Americas 2024
AXA XL - Insurer Innovation Award Americas 2024AXA XL - Insurer Innovation Award Americas 2024
AXA XL - Insurer Innovation Award Americas 2024
 
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot TakeoffStrategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
 
Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...
 
Corporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptxCorporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptx
 
[BuildWithAI] Introduction to Gemini.pdf
[BuildWithAI] Introduction to Gemini.pdf[BuildWithAI] Introduction to Gemini.pdf
[BuildWithAI] Introduction to Gemini.pdf
 
Strategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a FresherStrategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a Fresher
 
Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
 
Ransomware_Q4_2023. The report. [EN].pdf
Ransomware_Q4_2023. The report. [EN].pdfRansomware_Q4_2023. The report. [EN].pdf
Ransomware_Q4_2023. The report. [EN].pdf
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
 
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
 
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdfRising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
 
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
 
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerHow to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
 
ICT role in 21st century education and its challenges
ICT role in 21st century education and its challengesICT role in 21st century education and its challenges
ICT role in 21st century education and its challenges
 
Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...
Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...
Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...
 
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
 
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, AdobeApidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
 

Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported by Open-E ® DSS™

  • 1. Step-by-Step Guide to NAS (NFS) Failover over a LAN (with unicast) Supported by Open-E ® DSS™ Software Version: DSS ver. 6.00 up65 Presentation updated: March 2011
  • 2. NAS (NFS) Failover over a LAN  Open-E DSS NAS (NFS) Failover is a fault tolerance process via NAS volume replication, that creates mirrored 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. NAS (NFS) 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 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. NAS (NFS) Failover over a LAN • Data is written and read to System 1 (primary) • Data is continually replicated to System 2 (secondary) RAID System 1 RAID System 2 Primary Secondary Heartbeat Volume Replication PING NODEs Control Write Data Read Data www.open-e.com 4
  • 5. NAS (NFS) 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). RAID System 1 RAID System 2 Primary Secondary X Heartbeat PING NODEs Control Write Data Read Data www.open-e.com 5
  • 6. NAS (NFS) Failover over a LAN • After switching, the replicated volume is available on System 2 (secondary) RAID System 1 RAID System 2 Primary Secondary X PING NODEs Write Data Read Data www.open-e.com 6
  • 7. NAS (NFS) Failover over a LAN TO SET UP NAS (NFS) 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, NAS Volume • Configure Volume Replication mode (destination mode) – settings mirror IP address • NFS settings 3. Configure the Primary node • Create a Volume Group, NAS Volume • Configure Volume Replication mode (source mode) – settings mirror IP address, creating Volume Replication task and start replication task. • NFS settings, • Create and settings new share on primary node. 4. Configure Failover (primary and secondary node) 5. Select services used in Failover 6. Configure virtual IP and Auxiliary connection 7. Start Failover Service 8. Test Failover Function 9. Run Failback Function www.open-e.com 7
  • 8. NAS (NFS) 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 NODEs IP Address : 192.168.2.106; 192.168.2.107 Data Server (DSS1) Data Server (DSS2) Primary node Secondary node IP Address:192.168.0.220 IP Address:192.168.0.221 Control 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 NAS volume (lv00) NFS Failover/Volume Replication (eth1) NAS volume (lv00) Share (data) Share (data) www.open-e.com 8
  • 9. NAS (NFS) 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. NAS (NFS) 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. NAS (NFS) 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. NAS (NFS) 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. NAS (NFS) 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. NAS (NFS) 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. NAS (NFS) 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. NAS (NFS) 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. NAS (NFS) 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. NAS (NFS) 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 NAS 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 NAS volume, click the apply button www.open-e.com 18
  • 19. NAS (NFS) Failover over a LAN Data Server (DSS2) Secondary node 2. Configure the Secondary node IP Address:192.168.0.221 The destination NAS Volume is now configured. NAS volume (lv0000) www.open-e.com 19
  • 20. NAS (NFS) 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 if 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. NAS (NFS) Failover over a LAN Data Server (DSS2) Secondary node 2. Configure the Secondary node IP Address:192.168.0.221 Choose „CONFIGURATION”, and „NAS settings” from the menu on the secondary node In the NAS settings function, check the box Use NFS, click apply to confirm. www.open-e.com 21
  • 22. NAS (NFS) 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 22
  • 23. NAS (NFS) 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 NAS 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 NAS volume, click the apply button NOTE: The source and destination volumes must be of identical size. www.open-e.com 23
  • 24. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 The source NAS Volume is now configured. NAS volume (lv0000) www.open-e.com 24
  • 25. NAS (NFS) 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 25
  • 26. NAS (NFS) 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 26
  • 27. NAS (NFS) 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 27
  • 28. NAS (NFS) 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 28
  • 29. NAS (NFS) 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 NAS Logical Volume via NFS. www.open-e.com 29
  • 30. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 Choose „CONFIGURATION”, and „NAS settings” from the menu In the NAS settings function, check the box Use NFS, click apply to confirm. www.open-e.com 30
  • 31. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 Next, choose „CONFIGURATION”, „NAS resources” and „Shares” from the menu. Enter share name in field „Name” and click apply to confirm. www.open-e.com 31
  • 32. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 3. Configure the Primary node IP Address:192.168.0.220 In the NFS share acces function, check the box Use NFS, and click apply to confirm. www.open-e.com 32
  • 33. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 4. Configure Failover IP Address:192.168.0.220 Next choose „SETUP”, „network”, end select Failover on the primary node. In the Failover configuration function, check the box Enable Failover functionality. Select Network connection mode (in this example Unicast) and select Network interface for unicast (bond0). 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. NAS (NFS) Failover over a LAN Data Server (DSS2) Secondary node 4. Configure Failover IP Address:192.168.0.221 Now, select Failover on the secondary node Now, in Failover configuration function , check the box Enable Failover functionality. Select Network connection mode (in this example Unicast) and select Network interface for unicast (bond0). After choose Secondary node on localhost enter Primary node IP address and click the apply button www.open-e.com 34
  • 35. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 5. Configure Virtual IP and Auxillary connection IP Address:192.168.0.220 Now, select the bond0 within 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. This step is necessary to complement the destination IP address used in unicast. 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 Failover systems, please set this pair in a different network subnet from the other Failover systems. If the virtual IP must be in the same network subnet, there will be extra configuration steps required. Please refer to other document which describe configuration with static routing. www.open-e.com 35
  • 36. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 5. Configure Virtual IP and Auxillary connection IP Address:192.168.0.220 Now, select the eth1 within Failover. In the Auxiliary connection function check box Use this network interface to communicate between the nodes next enter IP address for Unicast remote IP and click the apply button. www.open-e.com 36
  • 37. NAS (NFS) Failover over a LAN Data Server (DSS2) Secondary node 5. 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 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. This step is necessary to complement the destination IP address used in unicast. www.open-e.com 37
  • 38. NAS (NFS) Failover over a LAN Data Server (DSS2) Secondary node 5. Configure Virtual IP and Auxillary connection IP Address:192.168.0.221 Now, select the eth1 within Failover. In the Auxiliary connection function check box Use this network interface to communicate between the nodes next enter IP address for Unicast remote IP and click the apply button. www.open-e.com 38
  • 39. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 6. Select services used in Failover IP Address:192.168.0.220 Now, in Failover services function (on primary node), uncheck the box with iSCSI, then check box witch NFS, and click the apply button NOTE: Selecting NFS in Failover service will reduce the access to shares on volumes used in Failover Tasks to NFS access only. Activating Failover Service will automatically deactivate all other services for those shares. www.open-e.com 39
  • 40. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 7. Start Failover Service IP Address:192.168.0.220 Next, in the Failover Tasks function, move the Failover Tasks to be used for the failover service to the Failover Tasks area clicking button and click apply www.open-e.com 40
  • 41. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 7. 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 41
  • 42. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 7. 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 mount the NFS client computers. www.open-e.com 42
  • 43. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 7. Start Failover Service IP Address:192.168.0.220 After start Failover, check the status in Failover status function. All must read OK NAS Failover/Volume Replication www.open-e.com 43
  • 44. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 7. Start Failover Service IP Address:192.168.0.220 In the Task status, (after clickling button) the destination volumes must be consistent. NAS Failover/Volume Replication www.open-e.com 44
  • 45. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 8. 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 45
  • 46. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 8. 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 46
  • 47. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 8. 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 47
  • 48. NAS (NFS) Failover over a LAN Data Server (DSS2) Secondary node 8. 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 48
  • 49. NAS (NFS) Failover over a LAN Data Server (DSS2) Secondary node 9. 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 49
  • 50. NAS (NFS) Failover over a LAN Data Server (DSS2) Secondary node 9. 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 50
  • 51. NAS (NFS) Failover over a LAN Data Server (DSS2) Secondary node 9. 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 51
  • 52. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 9. 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 52
  • 53. NAS (NFS) Failover over a LAN Data Server (DSS1) Primary node 9. Run Failback Function IP Address:192.168.0.220 Primary node is active again and ready for Failover. Failover/Volume Replication The configuration and testing of NAS Failover/Failback is now complete. www.open-e.com 53
  • 54. Thank you! Follow Open-E: www.open-e.com 54