TRUE ZERO RTO ELIMINATING OS AND APP LOAD TIMES
One example method includes performing a cloning process that includes cloning an OS disk and a data disk of a source VM to create a replica VM having an OS disk and a data disk that correspond, respectively, to the OS disk and data disk of the source VM. A replication process is then performed that includes replicating an application from the data disk of the source VM to the data disk of the replica VM, and the replication process does not include any replication of the OS disk of the source VM to the OS disk of the replica VM. Finally, the replica VM is powered up so that the OS of the replica VM is running, and the application is running on the replica VM. When performing a recovery with the replica VM, the RTO does not include an OS boot time.
1 . A method comprising:
performing a cloning process that comprises cloning an OS disk and a data disk of a source VM to create a replica VM that comprises an OS disk and a data disk that correspond, respectively, to the OS disk and data disk of the source VM;
performing a replication process that comprises replicating an application from the data disk of the source VM to the data disk of the replica VM, and the replication process does not include any replication of the OS disk of the source VM to the OS disk of the replica VM; and
powering up the replica VM so that the OS of the replica VM is running, and the application is running on the replica VM.
2 . The method as recited in claim 1 , wherein after the replica VM is powered up, the data disk of the replica VM is not accessible to the OS disk of the replica VM.
3 . The method as recited in claim 1 , further comprising replicating, to the data disk of the replica VM, an IO that was written to the data disk of the source VM.
4 . The method as recited in claim 3 , further comprising logging the IO in a replication journal.
5 . The method as recited in claim 1 , further comprising verifying that the source VM is operating correctly, and then powering off the application that is running on the replica VM.
6 . The method as recited in claim 1 , wherein after the replica VM is powered up, the application of the source VM is protected by replication to the replica VM, and the OS of the source VM is not protected by replication to the replica VM.
7 . The method as recited in claim 1 , wherein the cloning process comprises cloning all disks of the source VM to the replica VM.
8 . A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
cloning an OS disk and a data disk of a source VM to create a replica VM that comprises an OS disk and a data disk that correspond, respectively, to the OS disk and data disk of the source VM;
performing a replication process that comprises replicating an application from the data disk of the source VM to the data disk of the replica VM, and the replication process does not include any replication of the OS disk of the source VM to the OS disk of the replica VM; and
powering up the replica VM so that the OS of the replica VM is running, and the application is running on the replica VM.
9 . The non-transitory storage medium as recited in claim 8 , wherein after the replica VM is powered up, the data disk of the replica VM is not accessible to the OS disk of the replica VM.
10 . The non-transitory storage medium as recited in claim 8 , further comprising replicating, to the data disk of the replica VM, an IO that was written to the data disk of the source VM.
11 . The non-transitory storage medium as recited in claim 8 , further comprising logging the IO in a replication journal.
12 . The non-transitory storage medium as recited in claim 8 , further comprising verifying that the source VM is operating correctly, and then powering off the application that is running on the replica VM.
13 . The non-transitory storage medium as recited in claim 8 , wherein after the replica VM is powered up, the application of the source VM is protected by replication to the replica VM, and the OS of the source VM is not protected by replication to the replica VM.
14 . The non-transitory storage medium as recited in claim 8 , wherein the cloning process comprises cloning all disks of the source VM to the replica VM.
15 . A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
for a replica VM with an OS that is running, receiving an identification of a PIT to recover the replica VM to;
using information from a replication journal to roll a data disk of the replica VM to the PIT;
rescanning the replica VM to discover a new data disk of the replica VM;
determining whether an application on the data disk of the replica VM is running, and if the application is not already running, starting the application;
finding, with the application, the new data disk of the replica VM; and
exposing, with the application, services which the application is configured to provide.
16 . The non-transitory storage medium as recited in claim 15 , wherein the rescanning is performed either by an agent of the replica VM OS, or by an API of the application on the replica VM.
17 . The non-transitory storage medium as recited in claim 15 , wherein the recited operations collectively define an RTO that does not include a replica VM OS boot time.
18 . The non-transitory storage medium as recited in claim 17 , wherein when the application on the data disk of the replica VM is already running, the RTO does not include a start time of the application.
19 . The non-transitory storage medium as recited in claim 15 , wherein the operations further comprise implementing a failover from a source VM to the replica VM.
20 . The non-transitory storage medium as recited in claim 19 , wherein the operations further comprise receiving, after the failover is completed, an IO at the replica VM and replicating that IO from the replica VM to another VM.