CloudRecovery with Failover
CloudRecovery with Failover gives customers the necessary tools to ensure that mission critical applications remain available during a disaster, whether on-site or larger surrounding area. CloudRecovery focuses on the key servers housing the applications that a business needs in order to survive. Once initiated, CloudRecovery brings a business back up to production mode in Convergia’s Cloud within minutes or hours, as compared to traditional recovery methods that can take hours, days or weeks.
CloudRecovery with Failover – How it Works
Convergia’s servers are provisioned in a shadow or hot standby mode with minimal CPU (Computer Processing Units) or Cores and minimal RAM (Random Access Memory) resources; this keeps costs down. The customer’s on-site primary servers are set to replicate data to the shadow server(s) at a rate determined by the customer that is within the customer’s designated Recovery Point Objective (RPO). The rate at which data can replicate is limited to the amount of bandwidth the customer has assigned for this operation. The majority of customers use a low percentage of their bandwidth for data replication during business hours, and then utilize a higher percentage of the bandwidth during non-peak hours for this purpose. There are situations in which the RPO is extremely high, meaning the business requires that very little data will be lost in the event of an outage and real time replication is needed. In these cases, a separate bandwidth is designated for full time data replications so that there is no impact on their normal bandwidth needs for other operations. As data goes through the shadow server(s), it is stored in Convergia’s SAN environment. All of the data is in the Convergia Cloud, accessible by the shadow servers in the event of a major failure or disaster.
Once it is determined that the customer will failover to Convergia’s CloudRecovery service, either the customer’s IT team or Convergia’s support team logs into the Control Panel and assigns additional computing resources (CPUs and RAM) to the shadow server(s) and moves them into production mode (on average, this can take anywhere from 4- 15 minutes. The next step is to re-point end users to the Cloud by re-pointing the external DNS to Convergia. End users are then able to initiate connections and authenticate using their credentials to the virtual server(s) so that they can log into the system and resume work. End user performance is dependent upon bandwidth connectivity at the remote sites, but once connectivity is established the ability to function is restored.