A separate hardware component designed to host a specific computing resource. onQ Appliance is a separate computer system hosting a virtualization hypervisor, OS, Quorum-specific monitoring and other software, and sufficient resources to be able to support intermediate backups and when recovery is required, able to run a large number of nodes as virtual machines.

The totality of policies and actions put in place by a business in order to maintain its operations and relationships with partners and clients even when interruptions or disasters occur.

The elimination of redundant blocks of data across PNs to reduce storage and bandwidth requirements. De-duplication is important in backup systems where timely recovery is a concern.

The ability to recover business systems at an off-site facility in the event of a primary site failure.

The DR Appliance provides disaster recovery protection for your nodes. Often the DR Appliance is truly remote, being located in a different geographical location and connected through a separate WAN, but a more important distinction is the role it plays as the provider of disaster recovery protection.

The HA is the one connected directly to the network on which the Protected Nodes are located. The HA provides high availability protection.

Protection of nodes by onQ located on the same LAN as the nodes it protects. When HA recovery is required, Recovery Nodes are started on the HA.

hypervisor is software platform that allows multiple operating systems to run concurrently as virtual machines on a host computer.

onQ uses a backup scheme wherein a full backup is followed by a series of incremental backups, meaning backups that consist only of changes since the preceding backup. A Recovery Node can be quickly updated by simply merging the latest changes.

onQ Appliance refers to the hardware on which onQ Manager runs.

onQ Central is Quorum’s support management system. onQ Central manages alert notifications, licenses, and updates.

onQ Manager is the service that runs on an onQ Appliance coordinating all protection activities. onQ Manager sends alerts to onQ Central for processing.

onQ Service is the secure, lightweight software agent running on an agent‑based Protected Node. It communicates with the onQ Manager.

onQ Monitor is a tool designed to enable you to monitor multiple onQ Appliances from one user interface.

onQ Portal is the Web-based user interface used for all monitoring and management functions.

onQ virtual machine (also known as the onQ instance) is a separate operating system implemented in software. An onQ Appliance can host more than one onQ virtual machine. Each onQ instance provides an onQ Portal. An MSP (Managed Service Provider) configuration hosted by a single onQ Appliance can have several onQ instance

Any node on your network for which onQ provides a virtual image that can be run is said to be protected by onQ.

The physical or virtual machine to be protected by onQ. Abbreviated PN.

client process launched at the onQ side to push data to the target (in the case of FLR the target is the running PN and, in the case of a BMR, the target is the BMR target machine).

The up-to-date ready-to-run copy of the Protected Node. Abbreviated RN.

The process of reproducing a Recovery Node where the original image is on an HA and is replicated on the DR Appliance.

The deduplicated archive of all snapshots of all of your Protected Nodes. From the repository (aka snapshot repository), onQ can reproduce a complete system image from any snapshot.

onQ’s backup utility/client. squirtcopy performs backups of the PNs to squirtserver. squirtcopy is packaged with linpy/winpy.

Test mode means that a Recovery Node runs in a private network environment isolated from production facilities.

Bandwidth throttling is a technique for limiting the amount of transfer bandwidth available for data transfer on a network.

a server process launched at the target (in the case of FLR the target is the running PN and, in the case of a BMR, the target is the BMR target machine) side waiting for data.