Service archive support

• US 9,542,400 B2
• Filed: 05/31/2013
• Issued: 01/10/2017
• Est. Priority Date: 09/07/2012
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Doering, Jeffrey R., Gao, Ying, Cao, Vicky, Arun, Gopalan
• Primary Examiner(s): NGUYEN, THU N
• Application Number:
  US13/907,728
• Publication Number:
  US 20140074793A1
• Time in Patent Office: 1,320 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/182 Distributed file systems

Abstract

Embodiments of the present invention are directed to systems and methods for providing archival support for one or more services provided by a cloud infrastructure system. One such method comprises receiving a message corresponding to an archive trigger event, and determining based on the message one or more services subscribed to by a customer of a cloud infrastructure system which are to be archived. The method further comprises sending an instruction to the one or more services to archive customer information, and storing each archive in an archive directory accessible to the customer.

Claims

1. A method comprising:

receiving, by a cloud infrastructure system comprising one or more computing devices, a message corresponding to an archive trigger event, the archive trigger event including a request for archiving a first service and a second service, both of the first service and the second service being subscribed by a customer through a subscription;

obtaining, by the one or more computing devices, information regarding the subscription, the information indicating one or more services for which archival support is available;

determining, by the one or more computing devices, that customer information related to the first service is to be archived based on the first service being included in the one or more services;

determining, by the one or more computing devices, that customer information related to the second service is not to be archived based on the second service not being included in the one or more services;

based on the determination that the customer information related to the first service is to be archived, sending, by the one or more computing devices, an instruction to the first service to create an archive for the customer, the archive including the customer information related to the first service subscribed to by the customer; and

storing, by the one or more computing devices, the archive in an archive directory accessible to the customer.

2. The method of claim 1 wherein the archive trigger event includes a request to terminate at least one service from a subscription of the customer.

3. The method of claim 1 wherein the archive is stored in a Secure File Transfer Protocol file server.

4. The method of claim 1 wherein the instruction includes a location to store the archive, and wherein the location is accessible to the one or more computing devices and the one or more services.

5. The method of claim 1 wherein determining the first service to be archived is further based on an archive policy.

6. The method of claim 5 wherein the archive policy is based on the subscription of the customer.

16. The method of claim 5, wherein the archive policy specifies a level of archive support for the customer in accordance with a subscription of the first service by the customer, and wherein the instruction includes the level of archive support for the customer.

17. The method of claim 1, wherein the archive trigger event includes a request to suspend at least one service.

18. The method of claim 1, wherein the archive trigger event includes a periodically scheduled backup request.

19. The method of claim 1, wherein the archive trigger event includes an on-demand backup request.

7. A system comprising:

a cloud infrastructure system comprising one or more computing devices, wherein the cloud infrastructure system provides a plurality of services;

a tenant automation system (TAS) module, that executes on the one or more computing devices, wherein upon execution of the TAS module, the TAS module performs one or more operations to;

receive a message corresponding to an archive trigger event, the archive trigger event including a request for archiving a first service and a second service, both of the first service and the second service being subscribed by a customer through a subscription;

obtain information regarding the subscription, the information indicating one or more services for which archival support is available;

determine that customer information related to the first service is to be archived based on the first service being included in the one or more services; and

determine that customer information related to the second service is not to be archived based on the second service not being included in the one or more services; and

a service deployment infrastructure (SDI) module, that executes on the one or more computing devices, wherein upon execution of the SDI module, the SDI module performs one or more operations to;

based on the determination that the customer information related to the first service is to be archived by the TAS module, send an instruction to the first service to create an archive for the customer, the archive including the customer information related to the first service as subscribed to by the customer; and

store the archive in an archive directory accessible to the customer.

8. The system of claim 7 wherein the archive trigger event is one of a request to terminate at least one service from a subscription of the customer, a request to suspend the one or more services, a periodically scheduled backup, and an on-demand backup.

9. The system of claim 7 wherein the archive is stored in a Secure File Transfer Protocol file server.

10. The system of claim 7 wherein the instruction includes a location to store the archive, wherein the location is accessible to the computing device and/or the one or more services.

11. The system of claim 7, wherein the TAS module is further configured such that identifying the first service to archive is further based on an archive policy.

12. The system of claim 11 wherein the archive policy is based on a subscription of the customer.

13. A non-transitory computer readable storage medium including instructions stored thereon which, when executed by a computer, cause the computer to perform the steps of:

receiving, by a infrastructure system comprising a computer system, a message corresponding to an archive trigger event, the archive trigger event including a request for archiving a first service and a second service, both of the first service and the second service being subscribed by a customer through a subscription;

obtaining, by the computer system, information regarding the subscription, the information indicating one or more services for which archival support is available;

determining, by the computer system, that customer information related to the first service is to be archived based on the first service being included in the one or more services;

determining, by the computer system, that customer information related to the second service is not to be archived based on the second service not being included in the one or more services;

based on the determination that the customer information related to the first service is to be archived, sending, by the computer system, an instruction to the first service to create an archive for the customer, the archive including the customer information related to the first service as subscribed to by the customer; and

storing, by the computer system, the archive in an archive directory accessible to the customer.

14. The non-transitory computer readable storage medium of claim 13 wherein the archive is stored in a Secure File Transfer Protocol file server.

15. The non-transitory computer readable storage medium of claim 13 wherein identifying the first service to archive is further based on associated with an archive policy.