Unified replication and recovery
In one example, a system and method for replication and recovery of protected resources may include one or more vendor neutral components that identify a corresponding vendor specific replication and/or recovery tool. The vendor specific tool is then executre to obtain replication data related to the protected logical entity. The replication data is formatted in a vendor neutral format, and forwarded to a target site over a data transport mechanism. The target site can then reformat the replication data into the appropriate vendor specific formats required on the target site (which may not be the same vendor or vendor formats on the source site), and proceed to recover and/or replicate the protected resources.
1. A method for replication and/or recovery of protected resources located at a source site to a destination site comprising:
at the source site,
executing a vendor-neutral Discovery Component to identify one or more vendor-specific discovery tools for discovering aspects of the protected resources, including one or more aspects of infrastructure, platform, storage, network, or virtual machine protected resources;
executing a Deployment Component, for deploying the one or more vendor-specific discovery tools on the source site according to a deployment schedule, to obtain data related to the protected resources;
generating one or more Replication Data Units from the data related to the protected resources and/or user input, the Replication Data Units containing data representing artifacts of the protected resources in a vendor-neutral data format;
forwarding the Replication Data Units to a transport mechanism;
at the destination site,
receiving the Replication Data Units from the transport mechanism;
executing a Recovery Component for converting the Replication Data Units to vendor-specific Deployment Recovery Units; and
executing a Deployment Component, using the vendor-specific Deployment Recovery Units to orchestrate a set of destination resources, thereby recovering the protected resources.
2. The method of claim 1 additionally comprising:
at the destination site,
executing a second Discovery Component to identify one or more vendor-specific discovery tools for discovering aspects of the destination resources, including one or more aspects of infrastructure, platform, storage, network, or virtual machine resources.
3. The method of claim 2 wherein the Deployment Component is further for:
deploying storage for the Replication Data Units.
4. The method of claim 1 wherein
the step of converting the Replication Data Units is initiated either:
immediately before the step of executing the Deployment Component, or
any time after receipt from the transport mechanism via a lazy conversion process.
5. The method of claim 1 wherein the vendor-neutral Discovery Component is selected based on a Service Level Agreement with a Disaster Recovery service that provides the destination site.
6. The method of claim 1 wherein the Replication Data Units include one or more virtual machine identifiers, networks, storage associations, application states and protected data.
7. A system for replication and/or recovery of protected resources located at a source site to a destination site comprising:
at a source site that includes one or more of the protected resources,
one or more source site processors for
executing a Discovery Component, to identify one or more vendor-specific discovery tools for discovering aspects of the protected resources, including one or more aspects of infrastructure, platform, storage, network, or virtual machine protected resources;
executing a Deployment Component, to deploy the one or more vendor-specific discovery tools on the source site according to a deployment schedule, to obtain data related to the protected resources;
executing one or more other components, to
generate one or more Replication Data Units from the data related to the protected resources and/or user input, the Replication Data Units containing data representing artifacts of the protected resources in a vendor-neutral data format; and
forward the Replication Data Units to a transport mechanism;
at the destination site,
one or more destination site processors for executing program code to receive the Replication Data Units from the transport mechanism;
execute a Recovery Component for converting the Replication Data Units to vendor-specific Deployment Recovery Units; and
execute a Deployment Component, using the vendor-specific Deployment Recovery Units to orchestrate a set of destination resources, thereby recovering the protected resources.
8. The system of claim 7 additionally comprising:
at the destination site, additional code to
execute a second Discovery Component to identify one or more vendor-specific discovery tools for discovering aspects of the destination resources, including one or more aspects of infrastructure, platform, storage, network, or virtual machine resources.
9. The system of claim 7 wherein the Deployment Component is further for
deploying storage for the Replication Data Units.
10. The system of claim 7 wherein
converting the Replication Data Units is initiated either:
immediately before the step of executing the Deployment Component, or
any time after receipt from the transport mechanism via a lazy conversion process.
11. The system of claim 7 wherein the Discovery Component is selected based on a Service Level Agreement with a Disaster Recovery service that provides the destination site.
12. The system of claim 7 wherein the step of executing the Discovery Component further comprises:
initiating the step of executing the Discovery Component through a generic interface that is not specific to any of the one or more vendor-specific discovery tools.
13. The system of claim 7 wherein the vendor-neutral Discovery Component is selected based on a Service Level Agreement with a Disaster Recovery service that provides the destination site.