High speed Backup and Recovery for Business

High Availability

This is a typical HA configuration including onQ Archive Vault for long term retention. In this example, three critical servers (SQL, Exchange and Linux) are protected by a single onQ appliance which is monitored and managed by our web based administration portal.

Failure Scenario: In this example, the production Exchange server has experienced some level of failure. Using a single click, an IT staff member is able to start the virtual copy (VM clone or Recovery Node) of the failed Exchange server on the locally deployed onQ HA appliance. If the users are accessing the application using a browser, they need only refresh their interface to the application in order to immediately continue their work. This works for single and multiple servers.

Disaster Recovery

When deploying onQ in a DR configuration, in addition to the local onQ HA appliance, a second onQ appliance must be deployed at the organization’s DR location. Changes to locally protected servers (data, applications, and server images) captured by onQ HA are first deduplicated, and then replicated to the onQ DR or DRaaS appliance at the secondary location.

Failure Scenario: In this example, the production Exchange server has experienced some level of failure. Using a single click, an IT staff member is able to start the virtual copy (VM clone or Recovery Node) of the failed Exchange server on the locally deployed onQ HA appliance. If the users are accessing the application using a browser, they need only refresh their interface to the application in order to immediately continue their work. This works for single and multiple servers.

Dr As A Service (DRaaS)

An onQ DRaaS deployment resembles an onQ DR deployment in some ways. But instead of deploying a second onQ appliance at an organization’s own DR site, they choose to leverage the Quorum Cloud. Server, application and data changes captured by the locally deployed onQ HA appliance are encrypted and replicated to the onQ appliance in the Quorum Cloud.

DRaaS deployments help organizations avoid the high costs of funding, designing, staffing and maintaining a replicated datacenter – empowering them to achieve both local HA and remote DR in a more cost-effective way.

Failure Scenario: Complete Datacenter failure. DC failures can happen for several reasons like power outages, flooding and other disasters. In the event of a complete datacenter outage, IT staff can power on and spin up all Recovery Nodes on the onQ appliance deployed at the remote DR site - on any web browser, including web-enabled mobile devices.The servers will start in a preconfigured sequence, including necessary time delays. Users can then use VPN to access the servers, applications and data on the remote onQ appliance located in the Quorum Cloud.

The result: downtime is limited only to the time it takes the VMs to spin up.

Your Last Line of Defense Against Ransomware

Relying solely on prevention to avoid Ransomware is only a partial solution. So how should you protect yourself? That can be a tricky question. IT admins will want to build a wall around their systems in the form of a next gen firewall, IPS, host/server antivirus, access controls, etc. There are multiple ‘defense in depth’ guides you can follow.

These defense in-depth guides do a great a job preventing known threat signatures and behaviors. But what happens when an ill-advised user circumvents your security barriers? Or when that zero-day ransomware exploit makes its way inside your system?

That's where onQ comes in. It's hardened appliance hardware and encrypted snapshots can immediately boot a snapshot of your production servers in the event of an infection. Our scalable hardware is designed to deliver the same levels of workload performance as your production systems, to seamlessly take over for the compromised server. onQ gives you the time to you need to clean the infected server and get it back online.

How to mitigate a ransomware disaster with Quorum:

Turn it off. As soon as you realize you’ve been breached with the malware, do your best to isolate the affected servers. Take them offline immediately. Search for Patient Zero - this may not be easy and may take some time.

Keep working. From the Quorum dashboard, start a clone of your production server from a time that you know is clean. Remember–Quorum’s snapshot is encrypted. Run that clone in production for as long as you need.

Clean your systems. Take as long as you need to fix your production systems while the clone is running. We continue to back up your data even when the clone is running.

Failback to production. Once your production systems are cleaned and back online, simply failover from onQ back to production. All changes that occurred while running on our solution will be migrated back to production.

Notice the theme with this recovery scenario? Minimal downtime.
You never consider paying the ransom and you look like a rock star because you have a fix in place as soon as you realize you have a problem.

Learn more about Quorum Ransomware Recovery