help • App. L: High Availability Solution for SwyxWare • Options
L.2 Options
With SwyxWare the following high availability solutions can be used:
vSphere HA
vSphere HA + FT
Microsoft Hyper-V Failover Cluster
SwyxON
SwyxWare runs in a VM with the database either in SQL Express or in an existing SQL Server or Cluster.
SwyxWare runs in a VM with the database either in SQL Express or in an existing SQL Server or Cluster.
SwyxWare runs in a VM with the database either in SQL Express or in an existing SQL Server or Cluster.
Customer uses SwyxON
HA/Failover
vSphere HA
HA/Failover
vSphere FT
HA/Failover
MS Hyper-V Cluster
HA/Failover
SwyxON
Back-up
VEEAM VM Back-up
Back-up
VEEAM VM Back-up
Back-up
VEEAM VM Back-up
Back-up
SwyxON
Disaster Recovery
vSphere with geo-redundancy and backup
Disaster Recovery
vSphere with geo-redundancy and backup
Disaster Recovery
MS Hyper-V Cluster
Disaster Recovery
SwyxON
Downtime
Few minutes (depending on the virtualization structure and SwyxWare utilization)
Downtime
Uninterrupted availability through VMWare Fault Tolerance
Downtime
See MS Hyper-V Cluster documentation
Downtime
See SwyxON SLA
Maintenance Downtime
vSphere. Update in a separate VM. Some recorded data is lost, such as call journal entries created during the update period.
Maintenance Downtime
vSphere. Update in a separate VM. Some recorded data is lost, such as call journal entries created during the update period.
Maintenance Downtime
vSphere. Update in a separate VM. Some recorded data is lost, such as call journal entries created during the update period.
Maintenance Downtime
SwyxON
The displayed decision tree should lead you to one of the following solution options:
:
* 
You should use an existing virtualization-based high availability solution such as VMware vSphere to run SwyxWare in a virtual machine.
If you do not have such a virtualization infrastructure, Enreach recommends its own SwyxON Cloud Service instead.