System and method for PaaS replication

• US 10,235,249 B1
• Filed: 07/01/2016
• Issued: 03/19/2019
• Est. Priority Date: 07/01/2016
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Natanzon, Assaf, Lake, Brian, Garvin, Cody, Saad, Yossef
• Primary Examiner(s): Contino, Paul
• Application Number:
  US15/200,805
• Time in Patent Office: 991 Days
• CPC Class Codes: G06F 11/1428 with loss of hardware functionality
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/2082 Data synchronisation
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0644 Management of space entities, e.g. partitions, extents, pools
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

A method, computer program product, and computing system for defining a group of availability zones within a Platform-as-a-Service environment. A user is allowed to define a level of availability for the Platform-as-a-Service environment by selecting a plurality of availability zones from the group of availability zones.

Claims

1. A computer-implemented method, executed on a computing device, comprising:

defining a group of availability zones within a Platform-as-a-Service environment;

allowing a user to define a level of availability for the Platform-as-a-Service environment by selecting a plurality of availability zones from the group of availability zones, wherein each availability zone corresponds to a data site that provides one or more backend services and includes a frontend volume presentation and a backend data volume;

deploying a microservice within the Platform-as-a-Service environment;

associating the deployed microservice with one of the availability zones selected by the user and a backend service provided by that respective availability zone, wherein the backend service is a redundant microservice;

intercepting an IO request to one of the frontend volume presentations defined within one of the availability zones; and

processing the IO request on one or more of the backend data volumes defined within the plurality of availability zones selected by the user, wherein the IO request is a data write request that concerns a to-be-stored data portion and processing the IO request on one or more of the backend data volumes includes;

locking all of the backend data volumes defined within all of the availability zones;

writing the to-be-stored data portion to one of the backend data volumes defined within one of the availability zones;

replicating the to-be-stored data portion across all of the backend data volumes defined within all of the availability zones; and

unlocking all of the backend data volumes defined within all of the availability zones.

2. The computer-implemented method of claim 1 further comprising:

monitoring the plurality of availability zones to detect the failure of one or more of the plurality of availability zones, thus identifying one or more failed availability zones and one or more operational availability zones.

3. The computer-implemented method of claim 2 further comprising:

in the event that a failure is detected, restarting any microservices that were associated with the backend services running on the one or more failed availability zones so that they are associated with backend services running on the one or more operational availability zones.

4. The computer-implemented method of claim 1 wherein the IO request is a data read request that concerns a previously-stored data portion and processing the IO request on one or more of the backend data volumes includes:

obtaining the previously-stored data portion from one of the backend data volumes defined within one of the availability zones.

5. A computer program product residing on a non-transitory computer readable medium having a plurality of instructions stored thereon which, when executed by a processor, cause the processor to perform operations comprising:

defining a group of availability zones within a Platform-as-a-Service environment;

allowing a user to define a level of availability for the Platform-as-a-Service environment by selecting a plurality of availability zones from the group of availability zones, wherein each availability zone corresponds to a data site that provides one or more backend services and includes a frontend volume presentation and a backend data volume;

deploying a microservice within the Platform-as-a-Service environment;

associating the deployed microservice with one of the availability zones selected by the user and a backend service provided by that respective availability zone, wherein the backend service is a redundant microservice;

intercepting an IO request to one of the frontend volume presentations defined within one of the availability zones; and

processing the IO request on one or more of the backend data volumes defined within the plurality of availability zones selected by the user, wherein the IO request is a data write request that concerns a to-be-stored data portion and processing the IO request on one or more of the backend data volumes includes;

locking all of the backend data volumes defined within all of the availability zones;

writing the to-be-stored data portion to one of the backend data volumes defined within one of the availability zones;

replicating the to-be-stored data portion across all of the backend data volumes defined within all of the availability zones; and

unlocking all of the backend data volumes defined within all of the availability zones.

6. The computer program product of claim 5 further comprising instructions for:

monitoring the plurality of availability zones to detect the failure of one or more of the plurality of availability zones, thus identifying one or more failed availability zones and one or more operational availability zones.

7. The computer program product of claim 6 further comprising instructions for:

in the event that a failure is detected, restarting any microservices that were associated with the backend services running on the one or more failed availability zones so that they are associated with backend services running on the one or more operational availability zones.

8. The computer program product of claim 5 wherein the IO request is a data read request that concerns a previously-stored data portion and processing the IO request on one or more of the backend data volumes includes:

obtaining the previously-stored data portion from one of the backend data volumes defined within one of the availability zones.

9. A computing system including a processor and memory configured to perform operations comprising:

defining a group of availability zones within a Platform-as-a-Service environment;

allowing a user to define a level of availability for the Platform-as-a-Service environment by selecting a plurality of availability zones from the group of availability zones, wherein each availability zone corresponds to a data site that provides one or more backend services and includes a frontend volume presentation and a backend data volume;

deploying a microservice within the Platform-as-a-Service environment;

associating the deployed microservice with one of the availability zones selected by the user and a backend service provided by that respective availability zone, wherein the backend service is a redundant microservice;

intercepting an IO request to one of the frontend volume presentations defined within one of the availability zones; and

processing the IO request on one or more of the backend data volumes defined within the plurality of availability zones selected by the user, wherein the IO request is a data write request that concerns a to-be-stored data portion and processing the IO request on one or more of the backend data volumes includes;

locking all of the backend data volumes defined within all of the availability zones;

writing the to-be-stored data portion to one of the backend data volumes defined within one of the availability zones;

replicating the to-be-stored data portion across all of the backend data volumes defined within all of the availability zones; and

unlocking all of the backend data volumes defined within all of the availability zones.

10. The computing system of claim 9 further configured to perform operations comprising:

monitoring the plurality of availability zones to detect the failure of one or more of the plurality of availability zones, thus identifying one or more failed availability zones and one or more operational availability zones.

11. The computing system of claim 10 further configured to perform operations comprising:

in the event that a failure is detected, restarting any microservices that were associated with the backend services running on the one or more failed availability zones so that they are associated with backend services running on the one or more operational availability zones.

12. The computing system of claim 9 wherein the IO request is a data read request that concerns a previously-stored data portion and processing the IO request on one or more of the backend data volumes includes:

obtaining the previously-stored data portion from one of the backend data volumes defined within one of the availability zones.