Adjusting replication operations in a distributed environment
AssigneeVeritas Technologies LLC
InventorsTushar Doshi, Anish A. Vaidya, Kushal B. Shah
Life of this patent
Estimating the term…
Abstract
Disclosed herein are methods, systems, and processes to adjust replication operations in a distributed environment. A set of replicated data is received from a first appliance as a result of a replication operation. The replication operation is initiated by the first appliance and the set of replicated data includes a first timestamp. A write operation is performed to store the set of replicated data and a second timestamp is recorded. Recovery point information is generated based on the first timestamp and the second timestamp. The recovery point information is configured to be utilized in adjusting replication parameters of a subsequent replication operation.
Claims13
A computer-implemented method comprising:
- receiving, at a node at a recovery site, a set of replicated data from a first appliance,
- wherein
- the set of replicated data is received as a result of a replication operation initiated by the first appliance, and
- the set of replicated data comprises a first timestamp recorded by the first appliance indicating a time at which the set of replicated data was transmitted by the first appliance;
- performing a write operation on the recovery site, wherein
- the write operation comprises
- storing the set of replicated data on the recovery site, and
- recording a second timestamp that indicates a time at which the write operation was completed on the recovery site;
- generating recovery point information, wherein
- the recovery point information indicates a lag time, and
- the lag time is a difference in time between the time recorded by the first timestamp and the time recorded by the second timestamp;
- subsequent to generating the recovery point information, determining whether one or more requirements regarding replication of data generated by a host can be met by a subsequent replication operation, wherein
- the determining comprises comparing the recovery point information to a threshold lag time defined in Service Level Agreement (SLA) information,
- the SLA information is associated with the host,
- the host is communicatively coupled to the first appliance, and
- the threshold lag time corresponds to one or more requirements regarding replication of data generated by the host;
- in response to a determination that the one or more requirements can be met by the subsequent replication operation, sending the recovery point information to the first appliance, wherein
- the lag time is configured to be utilized in adjusting one or more replication parameters of the subsequent replication operation, wherein
- the one or more replication parameters comprises
- a network bandwidth associated with the first appliance, and
- an input/output (I/O) bandwidth associated with the recovery site;
- and
- in response to a determination that the one or more requirements cannot be met by the subsequent replication operation,
- determining whether the one or more requirements cannot be met because of either an in-flight data backlog on the first appliance or a replicated data backlog on the recovery site, and
- sending a notification with one or more instructions to adjust at least one of the one or more replication parameters, wherein
- in response to a determination that the one or more requirements cannot be met because of an in-flight data backlog on the first appliance, the one or more instructions comprise instructions to increase the network bandwidth associated with the first appliance, and
- in response to a determination that the one or more requirements cannot be met because of a replicated data backlog on the recovery site, the one or more instructions comprise instructions to increase the I/O bandwidth associated with the recovery site.
A non-transitory computer readable storage medium storage program instructions executable to perform a method comprising:
- receiving, at a node at a recovery site, a set of replicated data from a first appliance,
- wherein
- the set of replicated data is received as a result of a replication operation initiated by the first appliance, and
- the set of replicated data comprises a first timestamp recorded by the first appliance indicating a time at which the set of replicated data was transmitted by the first appliance;
- performing a write operation on the recovery site, wherein
- the write operation comprises
- storing the set of replicated data on the recovery site, and
- recording a second timestamp that indicates a time at which the write operation was completed on the recovery site;
- generating recovery point information, wherein
- the recovery point information indicates a lag time, and
- the lag time is a difference in time between the time recorded by the first timestamp and the time recorded by the second timestamp;
- subsequent to generating the recovery point information, determining whether one or more requirements regarding replication of data generated by a host can be met by a subsequent replication operation, wherein
- the determining comprises comparing the recovery point information to a threshold lag time defined in Service Level Agreement (SLA) information,
- the SLA information is associated with the host,
- the host is communicatively coupled to the first appliance, and
- the threshold lag time corresponds to one or more requirements regarding replication of data generated by the host;
- in response to a determination that the one or more requirements can be met by the subsequent replication operation, sending the recovery point information to the first appliance, wherein
- the lag time is configured to be utilized in adjusting one or more replication parameters of the subsequent replication operation, wherein
- the one or more replication parameters comprises
- a network bandwidth associated with the first appliance, and
- an input/output (I/O) bandwidth associated with the recovery site;
- in response to a determination that the one or more requirements cannot be met by the subsequent replication operation,
- determining whether the one or more requirements cannot be met because of either an in-flight data backlog on the first appliance or a replicated data backlog on the recovery site, and
- sending a notification with one or more instructions to adjust at least one of the one or more replication parameters, wherein
- in response to a determination that the one or more requirements cannot be met because of an in-flight data backlog on the first appliance, the one or more instructions comprise instructions to increase the network bandwidth associated with the first appliance, and
- in response to a determination that the one or more requirements cannot be met because of a replicated data backlog on the recovery site, the one or more instructions comprise instructions to increase the I/O bandwidth associated with the recovery site.
A system comprising:
- one or more processors;
- and
- a memory coupled to the one or more processors, wherein the memory stores program instructions executable by the one or more processors to perform a method comprising:
- receiving, at a node at a recovery site, a set of replicated data from a first appliance,
- wherein
- the set of replicated data is received as a result of a replication operation initiated by the first appliance, and
- the set of replicated data comprises a first timestamp recorded by the first appliance indicating a time at which the set of replicated data was transmitted by the first appliance;
- performing a write operation on the recovery site, wherein
- the write operation comprises
- storing the set of replicated data on the recovery site, and
- recording a second timestamp that indicates a time at which the write operation was completed on the recovery site;
- generating recovery point information, wherein
- the recovery point information indicates a lag time,
- the lag time is a difference in time between the time recorded by the first timestamp and the time recorded by the second timestamp;
- subsequent to generating the recovery point information, determining whether one or more requirements regarding replication of data generated by a host can be met by a subsequent replication operation, wherein
- the determining comprises comparing the recovery point information to a threshold lag time defined in Service Level Agreement (SLA) information,
- the SLA information is associated with the host,
- the host is communicatively coupled to the first appliance, and
- the threshold lag time corresponds to one or more requirements regarding replication of data generated by the host;
- in response to a determination that the one or more requirements can be met by the subsequent replication operation, sending the recovery point information to the first appliance, wherein
- the lag time is configured to be utilized in adjusting one or more replication parameters of the subsequent replication operation, wherein
- the one or more replication parameters comprises
- a network bandwidth associated with the first appliance, and
- an input/output (I/O) bandwidth associated with the recovery site;
- in response to a determination that the one or more requirements cannot be met by the subsequent replication operation,
- determining whether the one or more requirements cannot be met because of either an in-flight data backlog on the first appliance or a replicated data backlog on the recovery site, and
- sending a notification with one or more instructions to adjust at least one of the one or more replication parameters, wherein
- in response to a determination that the one or more requirements cannot be met because of an in-flight data backlog on the first appliance, the one or more instructions comprise instructions to increase the network bandwidth associated with the first appliance, and
- in response to a determination that the one or more requirements cannot be met because of a replicated data backlog on the recovery site, the one or more instructions comprise instructions to increase the I/O bandwidth associated with the recovery site.
Dependencies are inferred from the claim text.