Disaster recovery of cloud resources

Patent metadata

Field	Value
Publication number	US-11290318-B2
Application number	US-202017096878-A
Country	US
Kind code	B2
Filing date	Nov 12, 2020
Priority date	Dec 13, 2015
Publication date	Mar 29, 2022
Grant date	Mar 29, 2022

Abstract

Embodiments of the present invention are directed to methods by which different services registered with cloud infrastructure may recover in case of disaster. Also directs procedures with which a resource provider may recover and rebuild its cloud resource information by scanning actual resources available. A resource provider will synchronize resources with a central service to get updated consumer and subscription information. In the scenario in which a central service fails and is recovered from backup, the central service should synchronize with resource providers to update its resource information.

First claim

What is claimed is:

1. A method for recovering from a failure of a resource provider within a distributed computer network, the method being performed by the resource provider, the method comprising:
registering the resource provider with a central service;
associating resources on the distributed computer network with specific information that uniquely identifies the resources and enables the resource provider to determine resource owners; and
in response to the failure of the resource provider:
scanning the resources and the specific information that is associated with the resources;
recreating metadata records in a metadata store based at least in part on the specific information, wherein the metadata records and the specific information are different;
synchronizing the resources with the central service to obtain updated subscription information from the central service; and
updating subscription information in the metadata records based at least in part on the updated subscription information obtained from the central service.

2. The method of claim 1 , wherein the specific information that is associated with a particular resource enables a metadata record corresponding to the particular resource to be recreated.

3. The method of claim 1 , further comprising:
detecting that at least one recreated metadata record violates a business rule; and
marking the at least one recreated metadata record for manual action.

4. The method of claim 1 , further comprising exposing, to the central service, consumer subscriptions that have access to the resource provider and one or more resources owned by each consumer subscription.

5. The method of claim 1 , further comprising restoring the resource provider from a backup in response to the failure of the resource provider.

6. The method of claim 1 , further comprising:
creating the resources on behalf of consumers; and
maintaining metadata about the resources.

7. A method for recovering from a failure of a central service within a distributed computer network, the method being performed by the central service, the method comprising:
re-registering a plurality of resource providers, wherein the plurality of resource providers enable consumers to create resources, and wherein the plurality of resource providers are previously registered with the central service prior to the failure of the central service;
receiving resource information and subscription information from the plurality of resource providers;
recreating metadata records associated with the resources during recovery of the central service using the resource information and the subscription information received from the plurality of resource providers, wherein the metadata records are different from the resource information and the subscription information; and
routing, by the central service, cloud consumer requests to the plurality of resource providers that have re-registered with the central service.

8. The method of claim 7 , further comprising synchronizing the metadata records at the central service with corresponding metadata records maintained by the plurality of resource providers.

9. The method of claim 7 , further comprising validating that the central service is able to communicate with the plurality of resource providers.

10. The method of claim 7 , further comprising restoring the central service from a backup in response to the failure of the central service.

11. The method of claim 7 , further comprising requesting a service provider to initiate a manual recovery when information about a subscription is missing and the information cannot be automatically recovered.

12. The method of claim 11 , wherein the manual recovery requires creating a new subscription.

13. The method of claim 11 , wherein the manual recovery requires moving a resource from a recovered subscription to a newly recreated subscription upon verification of resource ownership.

14. The method of claim 7 , further comprising:
synchronizing the central service with a billing system that approves subscription creation; and
suspending any newly created subscriptions that are not included in the billing system.

15. The method of claim 7 , wherein the distributed computer network enters a disaster recovery mode in response to the failure of the central service.

16. A system for recovering from a failure of a central service within a distributed computer network, comprising:
one or more processors;
memory in electronic communication with the one or more processors; and
instructions stored in the memory, the instructions being executable by the one or more processors to:
re-register a plurality of resource providers, wherein the plurality of resource providers enable consumers to create resources, and wherein the plurality of resource providers are previously registered with the central service prior to the failure of the central service;
receive resource information and subscription information from the plurality of resource providers;
recreate metadata records associated with the resources during recovery of the central service using the resource information and the subscription information received from the plurality of resource providers, wherein the metadata records are different from the resource information and the subscription information; and
route, by the central service, cloud consumer requests to the plurality of resource providers that have re-registered with the central service.

17. The system of claim 16 , further comprising additional instructions that are executable by the one or more processors to synchronize the metadata records at the central service with corresponding metadata records maintained by the plurality of resource providers.

18. The system of claim 16 , further comprising additional instructions that are executable by the one or more processors to validate that the central service is able to communicate with the plurality of resource providers.

19. The system of claim 16 , further comprising additional instructions that are executable by the one or more processors to restore the central service from a backup in response to the failure of the central service.

20. The system of claim 16 , further comprising additional instructions that are executable by the one or more processors to request a service provider to initiate a manual recovery when information about a subscription is missing and the information cannot be automatically recovered.

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Pogrebinsky Vladimir

Classifications

• G06F11/2097

  maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups) · CPC title

• G06F11/2025

  using centralised failover control functionality · CPC title

• G06F11/1658

  Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit · CPC title

• G06F11/1482

  using middleware or operating system [OS] functionalities · CPC title

• G06F11/1471

  involving logging of persistent data for recovery · CPC title