DRaaS Frequently Asked Questions
A: For ON Cloud DRaaS, ScerIS will recover your servers with the same public IP addresses as in production and will ensure they can be contacted via the same external processes. For OFF Cloud DRaaS, ScerIS will recover your servers with different public IP addresses than those used in production. These different public IP addresses will be assigned during the set up process and will remain unchanged during term of this Agreement.
A: You are responsible for any external networking management and configuration including redirection of networking names, public IP addresses, shortcuts, or other routing configurations for your compute environment.
A: ScerIS DRaaS recovers servers. The recovery point used to recover your server is a replication of the entire storage volume specified for a single server. ScerIS DRaaS does not recover individual files. A single recovery point with a dataset that is no older than 15 minutes is maintained constantly. This recovery point is used for server recovery.
A: ScerIS uses an intelligent Constant Data Protection (CDP) technology that enables near synchronous updating of the recovery point dataset. Rather than creating individual archived volumes, a single volume is constantly updated and provides the ability to deliver access to a recovery point no older than the specified RPO while minimizing the storage capacities required to support your DR solution saving costs.
A: OFF Cloud DR Service can consume a significant amount of bandwidth between the production location and the ScerIS cloud. ScerIS assists with this by specifying configurations available in the agents that can help control bandwidth demands and requires the use of these specified configurations. Managing the cost, performance, and priority of bandwidth used by such services in the production location is entirely the customer’s responsibility. ScerIS strongly recommends that if purchasing OFF Cloud DR Service that customers coordinate with their networking teams to modify these network configuration settings along with any router or connection settings to find a configuration that works most efficiently.
A: Once you authorize ScerIS to initiate a recovery, ScerIS will recover your server(s) within the four hour RTO. At this point you have a server with an operational operating system, access to the dataset and communications for accessing the server. Customers can then deploy workloads and applications and access to the applications and workloads.
A: Here is an example. Assume that the ScerIS DRaaS has the appropriate connectivity to support a 15 minute RPO. The ScerIS DRaaS will maintain a single restore point dataset that is representative of the protected server storage volume every 15 minutes. Assume that the initial restore point is created at 1:00PM and the sequential updates occur on 15 minute intervals—the first being 1:15PM. Assume that there is an event that takes the server off line at 1:59PM. The last restore point is at 1:45, so the restore point would be 14 minutes old. But, the server was not discovered to be off-line until 3:00PM. At 3:15, your IT team authorizes ScerIS to recover the server. ScerIS uses the 1:45PM restore point (the last restore point completed) to recover the server and accomplishes the server recovery in 2 hours. It is now 5:15PM and the server is recovered. You now can resume business with having lost the data from 1:45PM through 1:59PM—14 minutes of data is lost. This is less than the 15 minute recovery point objective—the RPO has been met. However, the server has been off line from 1:59PM until 5:15PM—3 hours and 16 minutes off line/downtime. This example shows the difference between Server Downtime and RPO.
