Disaster Recovery

Companies are vulnerable to an array of outages and disasters that can cause unplanned downtime. Types of disasters can be a result of natural disasters and/or technical disasters, and can create outages such as Network Outages, Data Center Outages (Partial or Complete), Denial of Service attacks, Virus / Malware attacks.

When creating a disaster recovery plan, you need to ensure that all your critical IT systems and data can be quickly restored to normal operations. A typical comprehensive recovery plan will contain the following items:

  •    Hardware acquisition
  •    Communication Plan
  •    Key Contacts in the event of a disaster
  •    Standard Operating Procedures specific to a disaster recovery situation
  •    Overall owner of the recovery plan
  •    Checklists of required tasks which is then converted into a progress status list during the recovery period

Caradigm has a Disaster Recovery (DR) service for its hosted version of Caradigm Intelligence Platform (CIP) and Caradigm offered applications (Apps) hosted within Caradigm’s datacenters. For each customer, Caradigm hosts CIP, CIP Apps and data at a primary data center. The CIP Disaster Recovery service provides organizations with geographical redundancy in case the primary data center fails or is interrupted beyond normal functions.

Caradigm’s standard hosting configuration offers Local High-Availability (LHA) at a 99.5% availability service level, daily backups of data, and server redundancy at the primary data center.

Customers that subscribe to DR gain Geographic High-Availability (GHA) through a remote passive backup, residing in a secondary data center as pictured and described below.

 

 

Data is asynchronously replicated between the primary and secondary data centers–the Disaster Recovery copy is a virtual mirror image of your production environment–to provide high availability and failover. Failover is a backup mode in which the functions of a system are assumed by a secondary system when the primary component becomes unavailable. Any failover from the primary to the secondary data center is expected to result in a recovery timeframe of no more than 24 hours, assuming all customer dependent activities are complete.