You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
Home > Access It! Universal.NET > Access It! Universal.NET Redundancy Solutions
Access It! Universal.NET Redundancy Solutions
print icon

Overview

When referring to redundancy within Access It! Universal.NET there are several options available. Some may require purchasing additional dongle licenses, while others are transparent to the application. Each solution differs in the amount of downtime that will occur in the event of a failure. Below is a list of common solutions used.

High-Availability

Summary

A High-Availability virtual machine is a VM hosted over two or more physical servers. In the event one of the physical machines encounters an issue, the VM itself is moved to a new host. As this is redundancy on the hardware level, this solution is transparent to Access It! Universal.NET and does not require any additional dongle licenses.
Consult the Virtual Machine software manufacturer for more information on High-Availability requirements.

System Downtime

If a High-Availability VM is manually transitioned between host or safely shutdown there is zero downtime. In the event of a complete failure of a host, the VM will automatically move to the new host and reboot.

Recovery

No recovery is required.

Standby Server

Summary

A second physical or virtual server can be utilized in the event of the primary server failing. This solution would require a backup licensing dongle to be purchased and installed on the standby server. In the event of a failure, the most recent database backup must be manually restored to the standby server and then the services started. All client computers will then need to be redirected to the standby server in order to login.

If using a separate SQL server no backup needs to be restored.

System Downtime

While panels will continue to function in the field, clients will be unable to make any database updates nor receive panel events until the service on the standby server is started and the clients are redirected to the standalone server.

Recovery

Once the primary server is recovered, the service should be stopped on the standby server and a database backup should be made. Once the database is then restored on the primary server the service can be started and client machines can be redirected back to the primary server.

Microsoft Failover Clustering

Summary

Microsoft Failover Clustering is composed of two or more machines hosting a Microsoft's cluster enviroment to manage the Access It! Universal.NET service.  Upon a node failover the service is automatically moved across nodes as needed. The Access It! Universal.NET software must be installed and individually licensed on each node. All client machines will use the cluster name as the server name.

System Downtime

While the service is transitioned between nodes the software will be unresponsive for less than a minute. All panels will continue to function in the field.

Recovery

No recovery is required.


scroll to top icon