background image

 

 

Astaro Deployment Guide 

High Availability Options 

© 2011 Astaro GmbH & Co. KG – a Sophos company. Subject to change without notice.  

 

HA Roles and Failover 

Each node within the cluster can assume one of the following roles: 

 

Master:

 The primary system in a standby/cluster setup and responsible for synchronizing and 

distribution of data within the HA system.  

 

Slave:

 The standby system in a standby/cluster setup which takes over operations if the master fails.  

 

Worker:

 A simple node in a cluster setup, responsible for data processing only.  

All nodes monitor each other by means of a heartbeat signal, a periodically sent multicast UDP packet used to 
check if the other nodes are still alive. If any node fails to send this packet due to a technical error, the node 
will  be  declared  dead.  Depending  on  the  role  the  failed  node  had  assumed,  the  configuration  of  the  setup 
changes as follows: 

 

Failover in Astaro HA systems 

 

 

Summary of Contents for 220

Page 1: ...A Hot Standby 2 Active Active HA Cluster 2 Astaro s HA Act as One 2 Deploying a Hot Standby System 2 Installation 3 Automatic Configuration 3 Manual Configuration 4 Total Synchronization 4 Failover 5 Update Process 5 Monitoring 5 Reporting and Logging 6 Deploying a Cluster System 6 Installation 7 Initial Setup 7 Extending a Cluster 7 Integrated Load Balancing 8 Distributed Network Traffic 8 HA Rol...

Page 2: ...iances Astaro s HA Act as One Comparing Astaro s HA architecture to other high availability technologies like external load balancers or IP based NLB systems many advantages become visible While the following chapters will detail on how easy it is to setup an Astaro HA system with automatic configuration it s worth noting that once up and running the HA environment acts as only one system This is ...

Page 3: ...e automatic configuration feature offers a straight forward way to easily build an Active Passive HA Astaro Hardware Appliances always come with automatic HA configuration preconfigured and a dedicated HA interface eth3 for communication between the two devices Here are the three steps of the process To start the automatic setup you only need to connect two Astaro Gateways of the same type via the...

Page 4: ...Total Synchronization Astaro Gateways working in either high availability mode continuously exchange data over the HA interface to stay totally synchronized Synchronization only is effected between the master and slave node Worker nodes are not part of the synchronization process The synchronization is key when a hardware failure occurs and the surviving node takes over at the exact point where th...

Page 5: ...nt or application Update Process Each time new updates are available a special process will be started to ensure uninterrupted operation throughout the whole update process and safe transition to new versions of firmware and patches on all nodes of the system Whenever an update is started first the slave node and half of the worker nodes in clusters are updated Only if this initial update was succ...

Page 6: ...de Last status change of each HA node Real time hardware resource usage for CPU RAM and disk space Resource Monitoring in a Cluster Reporting and Logging All reporting data is consolidated on the master node and is synchronized to the other cluster nodes at intervals of five minutes In the case of a failover you will therefore lose not more than five minutes of reporting data However there is a di...

Page 7: ...er Performance Improvements below Cluster System Initial Setup To build a cluster of two or more Astaro devices you need to first identify and manually configure the first system in the Active Active HA environment Besides choosing Cluster as an operation mode the configuration is very similar to the manual configuration of an Active Passive HA system You need to provide the same configuration inf...

Page 8: ...er node Adding an additional node to a cluster Integrated Load Balancing In a clustered Astaro HA environment the load is evenly distributed between the participating cluster nodes Astaro s patent pending load balancing technology automatically makes use of all hardware resources in a cluster whereas the master node takes the responsibility to distribute the load between the slave and worker nodes...

Page 9: ...lave The standby system in a standby cluster setup which takes over operations if the master fails Worker A simple node in a cluster setup responsible for data processing only All nodes monitor each other by means of a heartbeat signal a periodically sent multicast UDP packet used to check if the other nodes are still alive If any node fails to send this packet due to a technical error the node wi...

Page 10: ...ng the performance of the overall system The matrix below shows how additional nodes increase overall performance in a cluster Note that between three and four nodes the performance increase is lower due to the fact that with adding the 4th node the master node will be dedicated to handle load balancing and synchronization tasks leaving the workload to the slave and worker nodes Also in sizing you...

Page 11: ... the eth3 interfaces of all ASG units forming the cluster to a network switch 3 Connect the ASG units to at least two uplink switches or routers and configure Astaro uplink load balancing on the designated master node to create a redundant WAN connection With the uplink load balancing feature you also gain automatic network traffic load balancing by using both WAN connections 4 To setup a redundan...

Page 12: ...ardware investments like external load balancers or high availability switches these HA solutions are very affordable Whereas most of the scenarios described in this guide where based on Astaro hardware appliances all HA options are also available with the Astaro software and virtual appliances offering you even more flexibility to design a secure and highly available network infrastructure This d...

Reviews: