How to Plan for Replication
Planning for replication doesn’t have to be difficult. It’s a simple matter of understanding your needs and environment.
Understand your RPO and RTO
Recovery Point Objective (RPO) – This is the amount of data that you can afford to lose if you have an emergency. For years, most companies backed up nightly. As a result, if they lost the network at the end of business (prior to the next backup) they would lose that day’s data. That’s a 24-hour RPO.
Recovery Time Objective (RTO) – RTO is the measure of how long it will take to get critical systems back up and running. For many companies, a 24-hour RTO is still appropriate. The problem is that recovery from tape could take hours, days, or even a week, depending on the data footprint in the environment. That is not acceptable in today’s business environment.
Which Solution is Right for You?
For most companies, a 24-hour RPO is acceptable if the RTO is very low. VMs that are replicated to InFlight have an extremely low RTO and can be spun up almost immediately in the event of an emergency. If a nightly replication with a fast recovery time is right for you, then Envision recommends Scheduled Replication to our InFlight cloud platform.
In some cases, regulatory or business obligations could require a much shorter RPO. In those situations, Envision recommends Live Replication to our InFlight cloud platform. To learn more about Scheduled Replication vs Live Replication, review our replication services summary or ask one of our solutions engineers for more details.
Understand Your Environment
To plan for replication, gather information about your current virtualized systems. Information you will need includes:
- Total number of vCPUs assigned to your VMs
- Total amount of assigned vRAM and the average amount of vRAM used at any given time
- Total amount of storage assigned to your VMs
Cloud contracts are priced based on the amount of storage, vCPU, and vRAM in your environment. Right-sizing your VM’s (assigning only the resources they actually need) will help keep your costs under control.
You will also need to understand your change rate and available bandwidth in order to size your environment for replication. See our sizing guide for more information.