Vaulting data from a public cloud

Patent metadata

Field	Value
Publication number	US-11829325-B2
Application number	US-202217839110-A
Country	US
Kind code	B2
Filing date	Jun 13, 2022
Priority date	Jul 10, 2019
Publication date	Nov 28, 2023
Grant date	Nov 28, 2023

Abstract

Data moving micro-services are deployed to a public cloud and a cloud vault target (CVT). A first request is issued to the public cloud for a first snapshot of data belonging to a customer tenant. The first snapshot is accessed to write the data to a first cloud volume in the public cloud. Data of the first cloud volume is vaulted to the CVT via the micro-services. The first cloud volume is maintained in the public cloud. A second request is issued to the public cloud for a second snapshot of the data belonging to the customer tenant. The second snapshot is accessed to write the data to a second cloud volume in the public cloud. Data of the second cloud volume is compared against data of the first cloud volume to identify redundant data. Data of the second cloud volume that is not redundant is vaulted to the CVT.

First claim

What is claimed is:

1. A method comprising:
deploying a data moving micro-service to a public cloud, and another data moving micro-service to a cloud vault target, the public cloud being owned by a first entity, and the cloud vault target being owned by a second entity, different from the first entity;
allowing a customer tenant of the public cloud to define a vaulting policy, the vaulting policy specifying data sources in the public cloud to be vaulted, the cloud vault target, a vaulting schedule, credentials to allow a cloud vault service to vault data belonging to the customer tenant, and access authorization by the cloud vault service to the data sources in a cloud account of the customer tenant;
issuing, according to the vaulting schedule, a first request to the public cloud for a first snapshot of the data belonging to the customer tenant of the public cloud;
accessing the first snapshot to write the data to a first cloud volume in the public cloud;
vaulting data of the first cloud volume to the cloud vault target using the data moving micro-services;
maintaining the first cloud volume in the public cloud;
issuing, according to the vaulting schedule, a second request to the public cloud for a second snapshot of the data belonging to the customer tenant;
accessing the second snapshot to write the data to a second cloud volume in the public cloud;
comparing data of the second cloud volume against data of the first cloud volume to identify redundant data; and
based on the comparison, vaulting data of the second cloud volume that is not redundant to the cloud vault target using the data moving micro-services.

2. The method of claim 1 further comprising:
receiving a request from the customer tenant to recall a copy of the vaulted data;
performing deduplication operations between the data vaulted to the cloud vault target and the first cloud volume maintained at the public cloud;
based on the deduplication operations, transmitting first vaulted data from the cloud vault target back to the public cloud, and not transmitting second vaulted data from the cloud vault target back to the public cloud, wherein the first vaulted data is data that was not found in the first cloud volume maintained at the public cloud, and the second vaulted data is data that was found in the first cloud volume maintained at the public cloud; and
copying the first and second vaulted data into the cloud account of the customer tenant.

3. The method of claim 1 wherein the customer tenant is a first customer tenant and the method further comprises:
receiving, by a cloud vault service tenant, the credentials and authorization from the first customer tenant for the cloud vault service tenant to access the cloud account of the first customer tenant and vault data of the first customer tenant; and
receiving, by the cloud vault service tenant, credentials and authorization from a second customer tenant for the cloud vault service tenant to access a cloud account of the second customer tenant and vault data of the second customer tenant.

4. The method of claim 1 wherein the first cloud volume is maintained in a cloud account at the public cloud that belongs to a cloud vaulting service tenant in the public cloud.

5. The method of claim 1 wherein the first cloud volume is maintained in a cloud account of the customer tenant.

6. A system comprising: a processor; and memory configured to store one or more sequences of instructions which, when executed by the processor, cause the processor to carry out the steps of:
deploying a data moving micro-service to a public cloud, and another data moving micro-service to a cloud vault target, the public cloud being owned by a first entity, and the cloud vault target being owned by a second entity, different from the first entity;
allowing a customer tenant of the public cloud to define a vaulting policy, the vaulting policy specifying data sources in the public cloud to be vaulted, the cloud vault target, a vaulting schedule, credentials to allow a cloud vault service to vault data belonging to the customer tenant, and access authorization by the cloud vault service to the data sources in a cloud account of the customer tenant;
issuing, according to the vaulting schedule, a first request to the public cloud for a first snapshot of the data belonging to the customer tenant of the public cloud;
accessing the first snapshot to write the data to a first cloud volume in the public cloud;
vaulting data of the first cloud volume to the cloud vault target using the data moving micro-services;
maintaining the first cloud volume in the public cloud;
issuing, according to the vaulting schedule, a second request to the public cloud for a second snapshot of the data belonging to the customer tenant;
accessing the second snapshot to write the data to a second cloud volume in the public cloud;
comparing data of the second cloud volume against data of the first cloud volume to identify redundant data; and
based on the comparison, vaulting data of the second cloud volume that is not redundant to the cloud vault target using the data moving micro-services.

7. The system of claim 6 wherein the processor further carries out the steps of:
receiving a request from the customer tenant to recall a copy of the vaulted data;
performing deduplication operations between the data vaulted to the cloud vault target and the first cloud volume maintained at the public cloud;
based on the deduplication operations, transmitting first vaulted data from the cloud vault target back to the public cloud, and not transmitting second vaulted data from the cloud vault target back to the public cloud, wherein the first vaulted data is data that was not found in the first cloud volume maintained at the public cloud, and the second vaulted data is data that was found in the first cloud volume maintained at the public cloud; and
copying the first and second vaulted data into the cloud account of the customer tenant.

8. The system of claim 6 wherein the customer tenant is a first customer tenant and the processor further carries out the steps of:
receiving, by a cloud vault service tenant, the credentials and authorization from the first customer tenant for the cloud vault service tenant to access the cloud account of the first customer tenant and vault data of the first customer tenant; and
receiving, by the cloud vault service tenant, credentials and authorization from a second customer tenant for the cloud vault service tenant to access a cloud account of the second customer tenant and vault data of the second customer tenant.

9. The system of claim 6 wherein the first cloud volume is maintained in a cloud account at the public cloud that belongs to a cloud vaulting service tenant in the public cloud.

10. The system of claim 6 wherein the first cloud volume is maintained in a cloud account of the customer tenant.

11. A computer program product, comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein, the computer-readable program code adapted to be executed by one or more processors to implement a method comprising:
deploying a data moving micro-service to a public cloud, and another data moving micro-service to a cloud vault target, the public cloud being owned by a first entity, and the cloud vault target being owned by a second entity, different from the first entity;
allowing a customer tenant of the public cloud to define a vaulting policy, the vaulting policy specifying data sources in the public cloud to be vaulted, the cloud vault target, a vaulting schedule, credentials to allow a cloud vault service to vault data belonging to the c

Assignees

• Emc Ip Holding Co Llc

Inventors

• Marelas Peter

Classifications

• G06F16/113 Primary

  Details of archiving (lifecycle management in storage systems G06F3/0649; point-in-time backing up or restoration of persistent data G06F11/1446) · CPC title

• G06F3/0605

  by facilitating the interaction with a user or administrator · CPC title

• G06F3/065

  Replication mechanisms · CPC title

• G06F3/067

  Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS] · CPC title

• G06F3/0641

  De-duplication techniques · CPC title