Zero Downtime (Erl, Naserpour)
How can we accomplish a zero down time when both virtual and physical servers failures occur?
ProblemIt is challenging to provide zero downtime guarantees when a physical host acts as a single point of failure for virtual servers.
SolutionA fault tolerance system is established so that when a physical server fails, virtual servers are migrated to another physical server.
ApplicationA combination of virtual server fault tolerance, replication, clustering and load balancing are applied and all virtual servers are stored in a shared volume allowing different physical hosts to access their files.
MechanismsAudit Monitor, Cloud Storage Device, Cloud Usage Monitor, Failover System, Hypervisor, Logical Network Perimeter, Resource Cluster, Resource Replication, Virtual Server
Compound PatternsBurst In, Burst Out to Private Cloud, Burst Out to Public Cloud, Cloud Authentication and Access Management, Elastic Environment, Infrastructure-as-a-Service (IaaS), Multitenant Environment, Platform-as-a-Service (PaaS), Private Cloud, Public Cloud, Resilient Environment, Secure Burst Out to Private Cloud/Public Cloud, Software-as-a-Service (SaaS)
Physical Server A fails triggering the live VM migration program to dynamically move Virtual Server A to Physical Server B.
NIST Reference Architecture Mapping
This pattern relates to the highlighted parts of the NIST reference architecture, as follows: