High Availability
For added redundancy and reliability against interruptions and business continuation, we provide high availability across all of our services including NAT VPS.
Automatic Failover
Should a server in a HA cluster fail for any reason, your VM will live migrate to another compute with zero downtime allowing you and your team to continue business as usual without being impacted by the failure.
To achieve this, SiteHUB uses a converged vSAN to pool all available storage from each host which are confiured with RAID 5.
A witness server is added to the cluster to monitor all members and fence host nodes should a failure be detected. This ensures maximum uptime for our clients and their projects at no extra costs.
Our prices are lower than our competitors and our support is superior. Try the SiteHUB difference today and experience what true web hosting should feel like where our priority is our clients.
HA Cluster
3 or more storage member hosts would be required to create a cluster in a specific location. All storage, RAM and CPU across nodes is then pooled and shared amongst VMs.
Quorum
Quorum reduces the occurrence of split brain after a hardware or network failure. A witness server (quorum) monitors and maintains writes and uptime thus avoiding split brain.
Failover
If a failure should occur and only affect a few hosts leaving a majority vote of hosts available, then your VM will automatically fail over to a host with available compute with minimal downtime.
IP Retention
During a failover to another compute, your IP will remain (as will your data) the same including cross site internal IPs and any private additional NIC IPs your VM may have had provisioned.
Is High Availability Hosting Expensive?
With SiteHUB, HA hosting is affordable (not cheap, but far from expensive). By incorporating RAID 50, we can afford a failure of one or more host per HA cluster and 2 disks per host.
This means we can offer cheaper plans than if we were using RAID 10 and we pass those savings to you.
HA hosting does not mean one should forget about hosting best practices always keeping your own personal off-site backup.
Frequently Asked Questions
High availability (HA) is the ability of a system to operate continuously for a designated period of time even if components within the system fail. A highly available system eliminates single points of failure. This is accomplished by including redundant components that serve as backups that can assume processing if failure should occur. In information technology (IT), a widely held but difficult-to-achieve standard of availability is known as five-nines availability, which means the system or product is available 99.999% of the time.
High Availability describes systems that are dependable enough to operate continuously without disruption due to the underlying hosts failing.
“Availability” includes two periods of time: how much time a service is accessible, and how much time the system needs to respond to user requests. High availability refers to those systems that offer a high level of operational performance and quality over a relevant time period.
To reduce interruptions and downtime, it is essential to be ready for unexpected events that can bring down servers. At times, emergencies will bring down even the most robust, reliable software and systems. Highly available systems minimize the impact of these events, and can often recover automatically from component or even server failures.
If your server is deployed in a location with 3 of more physical hosts in a cluster, then it is very likely your server has HA functionality.
You should not notice the feature as it should run silently in the background.
If you notice the host of your server randomly changes without downtime recorded, this can be a sign that you are in a HA cluster.
- Eliminates single points of failure. A single point of failure is a component that would cause the whole system to fail if that component failed. For example, if a business uses only one server to run an application, that server represents a single point of failure. Should the server fail, the application will be unavailable.
- When a component fails, it is possible for data to be lost if data protections have not been put into place. An HA system includes the mechanisms necessary to avoid or minimize data loss or disruption during system failure.
- Failures or faults must be immediately detected and acted upon.
- If a system component fails, a similar component must be immediately available to take over for the failed component. For this reason, the system must include redundant components and ensure reliable failover, which is the process of switching from one component to another without losing data or affecting performance, availability or operations.
Our Global Partners
Upstreams providing capacity, transit, additional locations, colocation, CDN, peering and much of our backbone that enables us to provide our services.
Experience The SiteHUB Difference
Outside of excellent hosting services, SiteHUB also provide support that is second to none!!
Links
- Knowledgebase
- Contact Us
- Affiliate
- Uptime Status
- Terms & Policies
- Data Centers
- Looking Glass
- Who Is Hosting Your Site?
- Blog