Method and apparatus for automated orchestration of long distance protection of virtualized storage
AssigneeEMC IP Holding Company LLC
InventorsWilliam J. Elliott, IV, Bradley J. Hughes, Sean R. Gallacher, Bharath Sreekanth, Anoop Ninan, Joseph A. Condlin, Michael G. Hegerich, Thomas L. Watson
Life of this patent
Estimating the term…
Abstract
Example embodiments of the present invention relate to a method, a system, and a computer program product for replicating a virtual volume. The method includes creating a volume in a first datacenter, the volume in the first datacenter accessible as a virtual volume exposed to the first datacenter and a second datacenter, and establishing replication of the virtual volume to a third datacenter.
Claims17
A computer-implemented method to automate orchestration of storage for remote data centers comprising:
- receiving, by a storage management API, parameters for creation of a source volume with high availability and data protection, wherein the parameters includes at least one of a storage size, a storage protocol, a source location, and a target location;
- creating the source volume in a first datacenter automatically by the storage management API, the source volume in the first datacenter accessible as a virtual volume exposed to the first datacenter and a second datacenter for high availability of the source volume between the first datacenter and the second datacenter;
- and
- establishing, by the storage management API, replication of the virtual volume to a third datacenter for data protection of the source volume between the second datacenter and the third datacenter;
- wherein the first datacenter, the second datacenter, and the third datacenter are each in a different geographic location, and further wherein the storage management API to enable automated establishment of virtualized storage automatically over long distances to meet a service level objective;
- wherein creating the source volume in a first datacenter causes creation of a target volume at the second datacenter exposed as a virtual volume at the first datacenter and the second datacenter, a replication target volume at the third datacenter, and journal volumes at the second datacenter and the third datacenter, and
- selecting the source volume for failover;
- and initiating failover of the replication target volume to the source volume to cause the source volume to operate as an active failover volume.
A system comprising:
- a first datacenter;
- a second datacenter;
- a third datacenter wherein the first datacenter, the second datacenter, and the third datacenter are each in a different geographic location;
- and
- computer executable logic configured to enable one or more processors of the system to perform operations of:
- receiving, by a storage management API, parameters for creation of a source volume with high availability and data protection, wherein the parameters includes at least one of a storage size, a storage protocol, a source location, and a target location;
- creating the source volume in the first datacenter automatically by the storage management API, the source volume in the first datacenter accessible as a virtual volume exposed to the first datacenter and the second datacenter for high availability of the source volume between the first datacenter and the second datacenter;
- and
- establishing, by the storage management API, replication of the virtual volume to the third datacenter for data protection of the source volume between the second datacenter and the third datacenter, wherein the first datacenter, the second datacenter, and the third datacenter are each in a different geographic location, and further wherein the storage management API to enable automated establishment of virtualized storage automatically over long distances to meet a service level objective;
- wherein creating the source volume in a first datacenter causes creation of a target volume at the second datacenter exposed as a virtual volume at the first datacenter and the second datacenter, a replication target volume at the third datacenter, and journal volumes at the second datacenter and the third datacenter;
- and
- selecting the source volume for failover;
- and initiating failover of the replication target volume to the source volume to cause the source volume to operate as an active failover volume.
A computer program product including a non-transitory computer readable storage medium have computer program code encoded thereon that, when executed on one or more processors of a system, causes the system to automate orchestration of storage for remote datacenters, the computer program code comprising:
- computer program code for receiving, by a storage management API, parameters for creation of a source volume with high availability and data protection, wherein the parameters includes at least one of a storage size, a storage protocol, source location, and a target location;
- computer program code for creating the source volume in a first datacenter, automatically by the storage management API, the source volume in the first datacenter accessible as a virtual volume exposed to the first datacenter and a second datacenter for high availability of the source volume between the first datacenter and the second datacenter;
- and
- computer program code for establishing, by the storage management API, replication of the virtual volume to a third datacenter for data protection of the source volume between the second datacenter and the third datacenter wherein the first datacenter, the second datacenter, and the third datacenter are each in a different geographic location, and further wherein the storage management API to enable automated establishment of virtualized storage automatically over long distances to meet a service level objective;
- wherein creating the source volume in a first datacenter causes creation of a target volume at the second datacenter exposed as a virtual volume at the first datacenter and the second datacenter, a replication target volume at the third datacenter, and journal volumes at the second datacenter and the third datacenter;
- and
- selecting the source volume for failover;
- and initiating failover of the replication target volume to the source volume to cause the source volume to operate as an active failover volume.
Dependencies are inferred from the claim text.