Systems and methods for continuous data protection
Example embodiments relate generally to systems and methods for continuous data protection (CDP) and more specifically to an input and output (I/O) filtering framework and log management system to seek a near-zero recovery point objective (RPO).
1. A method for establishing a system for continuous data protection, comprising:
capturing, by a driver, continuous inputs and outputs (I/Os) exchanged between a server and a virtual machine (VM) having a virtual disk, wherein the continuous I/Os are captured after a base snapshot in a series of snapshots of the VM is taken;
caching, by the driver, the continuous I/Os;
sending, by the driver, the continuous I/Os as stream logs to one or more clusters, the stream logs forming a log stream;
receiving, by a log receiver service (LRS), that runs on one or more nodes within the one or more clusters, the log stream;
writing, by the LRS, the log stream to a disk, wherein continuous log chains are formed by the stream logs in the log stream and the base snapshot, the base snapshot serving as a base for the stream logs in the continuous log chains, wherein a later stream log depends at least partially on a former stream log in a continuous log chain;
using a set of algorithms to calculate a recoverable range of the VM based at least in part on the continuous log chains, wherein calculating the recoverable range comprises:
affirming a validity of each continuous log chain of the continuous log chains based at least in part on whether an unbroken path to the base snapshot exists, the recoverable range being based at least in part on a first continuous log chain of the continuous log chains that has a shortest unbroken path to the base snapshot and a second continuous log chain of the continuous log chains that has a longest unbroken path to the base snapshot; and
recovering the VM to a continuous point-in-time version based at least in part on the recoverable range of the VM.
2. The method of claim 1 , wherein the validity of one or more continuous log chains is affirmed solely based on an existence of the base snapshot in a path of the one or more continuous log chains.
3. The method of claim 1 , further comprising:
taking a new snapshot in the series of snapshots and designating the new snapshot as the base snapshot.
4. The method of claim 3 , further comprising:
identifying an old or expired continuous log chain based at least in part on a designation of the new snapshot as the base snapshot.
5. The method of claim 4 , further comprising:
assigning a garbage collection (GC) operation to the old or expired continuous log based at least in part on a service level agreement (SLA) policy.
6. The method of claim 1 , further comprising:
configuring the driver to enable an I/O touch point in the captured continuous I/Os.
7. A system for continuous data protection, the system comprising:
at least one processor for executing machine-readable instructions; and
a memory storing instructions configured to cause the at least one processor to cause the system to:
capture, by a driver, continuous inputs and outputs (I/Os) exchanged between a server and a virtual machine (VM) having a virtual disk, wherein the continuous I/Os are captured after a base snapshot in a series of snapshots of the VM is taken;
cache by the driver, the continuous I/Os;
send, by the driver, the continuous I/Os as stream logs to one or more clusters, the stream logs forming a log stream;
receive, by a log receiver service (LRS), that runs on one or more nodes within the one or more clusters, the log stream;
write, by the LRS, the log stream to a disk, wherein continuous log chains are formed by the stream logs in the log stream and the base snapshot, the base snapshot serving as a base for the stream logs in the continuous log chains, wherein a later stream log depends at least partially on a former stream log in a continuous log chain;
use a set of algorithms to calculate a recoverable range of the VM based at least in part on the continuous log chains, wherein, to calculate the recoverable range, the instructions further cause the at least one processor to cause the system to:
affirm a validity of each continuous log chain of the continuous log chains based at least in part on whether an unbroken path to the base snapshot exists, the recoverable range being based at least in part on a first continuous log chain of the continuous log chains that has a shortest unbroken path to the base snapshot and a second continuous log chain of the continuous log chains that has a longest unbroken path to the base snapshot; and
recover the VM to a continuous point-in-time version based at least in part on the recoverable range of the VM.
8. The system of claim 7 , wherein the validity of one or more continuous log chains is affirmed solely based on an existence of the base snapshot in a path of the one or more continuous log chains.
9. The system of claim 7 , wherein the instructions are further configured to cause the at least one processor to cause the system to:
take a new snapshot in the series of snapshots and designating the new snapshot as the base snapshot.
10. The system of claim 9 , wherein the instructions are further configured to cause the at least one processor to cause the system to:
identify an old or expired continuous log chain based at least in part on a designation of the new snapshot as the base snapshot.
11. The system of claim 10 , wherein the instructions are further configured to cause the at least one processor to cause the system to:
assign a garbage collection (GC) operation to the old or expired continuous log chain based at least in part on a service level agreement (SLA) policy.
12. The system of claim 7 , wherein the instructions are further configured to cause the at least one processor to cause the system to:
configure the driver to enable an I/O touch point in the captured continuous I/Os.
13. A non-transitory, machine-readable medium storing instructions which, when read by a machine, cause the machine to:
capture, by a driver, continuous inputs and outputs (I/Os) exchanged between a server and a virtual machine (VM) having a virtual disk, wherein the continuous I/Os are captured after a base snapshot in a series of snapshots of the VM is taken;
cache by the driver, the continuous I/Os;
send, by the driver, the continuous I/Os as stream logs to one or more clusters, the stream logs forming a log stream;
receive, by a log receiver service (LRS), that runs on one or more nodes within the one or more clusters, the log stream;
write, by the LRS, the log stream to a disk, wherein continuous log chains are formed by the stream logs in the log stream and the base snapshot, the base snapshot serving as a base for the stream logs in the continuous log chains, wherein a later stream log depends at least partially on a former stream log in a continuous log chain;
use a set of algorithms to calculate a recoverable range of the VM based at least in part on the continuous log chains, wherein, to calculate the recoverable range, the instructions, when read by the machine, further cause the machine to:
affirm a validity of each continuous log chain of the continuous log chains based at least in part on whether an unbroken path to the base snapshot exists, the recoverable range being based at least in part on a first continuous log chain of the continuous log chains that has a shortest unbroken path to the base snapshot and a second continuous log chain of the continuous log chains that has a longest unbroken path to the base snapshot; and
recover the VM to a continuous point-in-time version based at least in part on the recoverable range of the VM.
14. The medium of claim 13 , wherein the validity of one or more continuous log chains is affirmed solely based on an existence of the base snapshot in a path of the one or more continuous log chains.
15. The medium of claim 13 , wherein the instructions, when read by the machine, further cause the machine to:
take a new snapshot in the series of snapshots and designating the new snapshot as the base snapshot.
16. The medium of claim 15 , wherein the instructions, when read by the machine, further cause the machine to:
identify an old or expired continuous log chain based at least in part on a designation of the new snapshot as the base snapshot.
17. The medium of claim 16 , wherein the instructions, when read by the machine, further cause the machine to:
assign a garbage collection (GC) operation to the old or expired continuous log chain based at least in part on a service level agreement (SLA) policy.
18. The medium of claim 13 , wherein the instructions, when read by the machine, further cause the machine to:
configure the driver to enable an I/O touch point in the captured continuous I/Os.