Optimization of resources providing public cloud services based on adjustable inactivity monitor and instance archiver

Patent metadata

Field	Value
Publication number	US-11726952-B2
Application number	US-202017003630-A
Country	US
Kind code	B2
Filing date	Aug 26, 2020
Priority date	Sep 13, 2019
Publication date	Aug 15, 2023
Grant date	Aug 15, 2023

Abstract

Techniques described herein automatically check for persistently inactive instances, based on defined metrics, and auto-archive such instances to lower-cost cloud resources. An inactivity time threshold is dynamically adjustable to a longer or shorter time period based on current load running on limited/more expensive resources to more aggressively or less aggressively archive the inactive instances, thus enabling additional active instances to run on the limited/more expensive resources and supporting more total users.

First claim

What is claimed is:

1. A method comprising:
monitoring activity against a pluggable database (PDB) contained in a container database management system (CDBMS), said CDBMS comprising a plurality of PDBs including said PDB;
based on said activity against said PDB, determining whether one or more first inactivity criteria are satisfied;
in response to determining that said one or more first inactivity criteria are satisfied based on said activity:
unplugging said PDB from a host container database (CDB);
generating a descriptor file containing information to allow said PDB to subsequently plug into said host CDB;
combining said descriptor file and data files associated with said PDB into an archive file;
transferring said archive file to a tier-two storage;
deleting said data files from said host CDB, thereby freeing up tier-one storage used by said PDB;

based on said activity against said PDB, determining whether one or more restart criteria are satisfied; and
in response to determining that said one or more restart criteria are satisfied based on said activity:
importing said archive file to said host CDB; and
uncompressing said archive file to configure another PDB that is plugged into said host CDB.

2. The method of claim 1 , wherein said one or more first inactivity criteria comprise no active connection to said PDB for at least a first period of time.

3. The method of claim 2 , further causing automatically adjusted said first period of time based on CDB load.

4. The method of claim 1 , wherein said tier-one storage is a more expensive storage than said tier-two storage.

5. The method of claim 1 , further comprising, prior to unplugging said PDB from said host CDB, causing to generate an archival warning.

6. The method of claim 1 , further comprising:
based on said activity against said PDB, determining whether one or more second inactivity criteria are satisfied;
in response to determining that said one or more second inactivity criteria are satisfied based on said activity:
deleting said archive file from said tier-two storage, thereby freeing up said tier-two storage used by said PDB.

7. The method of claim 6 , wherein said one or more second inactivity criteria comprise said PDB being archived for at least a second period of time.

8. The method of claim 6 , further comprising, prior to deleting said archive file, causing to generate a delete warning.

9. The method of claim 1 , wherein said one or more restart criteria comprise receipt of a restart trigger after said archive file is transferred to said tier-two storage but before said archive file is deleted from said tier-two storage.

10. One or more non-transitory computer-readable storage media storing one or more sequences of program instructions which, when executed by one or more computing devices, cause:
monitoring activity against a pluggable database (PDB) contained in a container database management system (CDBMS), said CDBMS comprising a plurality of PDBs including said PDB;
based on said activity against said PDB, determining whether one or more first inactivity criteria are satisfied;
in response to determining that said one or more first inactivity criteria are satisfied based on said activity:
unplugging said PDB from a host container database (CDB);
generating a descriptor file containing information to allow said PDB to subsequently plug into said host CDB;
combining said descriptor file and data files associated with said PDB into an archive file;
transferring said archive file to a tier-two storage;
deleting said data files from said host CDB, thereby freeing up tier-one storage used by said PDB;

based on said activity against said PDB, determining whether one or more restart criteria are satisfied; and
in response to determining that said one or more restart criteria are satisfied based on said activity:
importing said archive file to said host CDB; and
uncompressing said archive file to configure another DB that is plugged into said host CDB.

11. The one or more non-transitory computer-readable storage media of claim 10 , wherein said one or more first inactivity criteria comprise no active connection to said PDB for at least a first period of time.

12. The one or more non-transitory computer-readable storage media of claim 11 , wherein said one or more sequences of said program instructions, which when executed by said one or more computing devices, further cause automatically adjusting said first period of time based on CDB load.

13. The one or more non-transitory computer-readable storage media of claim 10 , wherein said tier-one storage is a more expensive storage than said tier-two storage.

14. The one or more non-transitory computer-readable storage media of claim 10 , wherein said one or more sequences of said program instructions, which when executed by said one or more computing devices, further cause, prior to unplugging said PDB from said host CDB, causing to generate an archival warning.

15. The one or more non-transitory computer-readable storage media of claim 10 , wherein said one or more sequences of said program instructions, which when executed by said one or more computing devices, further cause:
based on said activity against said PDB, determining whether one or more second inactivity criteria are satisfied;
in response to determining that said one or more second inactivity criteria are satisfied based on said activity:
deleting said archive file from said tier-two storage, thereby freeing up said tier-two storage used by said PDB.

16. The one or more non-transitory computer-readable storage media of claim 15 , wherein said one or more second inactivity criteria comprise said PDB being archived for at least a second period of time.

17. The one or more non-transitory computer-readable storage media of claim 15 , wherein said one or more sequences of said program instructions, which when executed by said one or more computing devices, further cause, prior to deleting said archive file, causing to generate a delete warning.

18. The one or more non-transitory computer-readable storage media of claim 10 , wherein said one or more restart criteria comprise receipt of a restart trigger after said archive file is transferred to said tier-two storage but before said archive file is deleted from said tier-two storage.

Assignees

• Oracle Int Corp

Inventors

• Bottger Todd A
• Hung Hochak
• Rajamani Kumar

Classifications

• H04L67/06

  specially adapted for file transfer, e.g. file transfer protocol [FTP] · CPC title

• 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

• H04L67/10 Primary

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• G06F16/162

  Delete operations (erasing in storage systems G06F3/0652) · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title