Software vault

• US 6,163,859 A
• Filed: 12/02/1998
• Issued: 12/19/2000
• Est. Priority Date: 12/02/1998
• Status: Expired due to Term

• Current Assignee: Avolin LLC
• Original Assignee: Support.com Incorporated (Greenidge Generation Holdings, Inc.)
• Inventors: Dale, Scott William, Lee, Cadir Batista
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): Bonzo, Bryce P.
• Application Number:
  US09/205,418
• Time in Patent Office: 748 Days
• Field of Search: 714/4, 714/5, 714/20, 714/38, 714/47, 714/1, 709/212, 709/220, 709/221, 709/223, 709/224
• US Class Current: 714/38.14
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A computer-implemented vault centrally archives an application from a client. Each application may be formed from one or more files, and each application has a unique meta description for reconstructing the application using the one or more files. The vault has one or more files which may be shared among applications; an access controller for allowing the client to retrieve a file from the vault based on the meta description; and a post controller for allowing the client to store a single instance of a uniquely indexed file based on the meta description.

Claims

1. A computer-implemented vault for archiving software components, where only a single instance of each component that is multiply-used is stored in the vault, comprising:

unique instances of the one or more software components;

an access controller for performing a direct, random access retrieval of the one or more software components from the vault; and

a post controller for performing a direct, random access insertion of a software component to the vault wherein the post controller generates a unique key from the new component and optimizes storage if the unique key exists.

2. A computer-implemented vault for archiving software components, where only a single instance of each component that is multiply-used is stored in the vault, comprising:

unique instances of the one or more software components;

an access controller for performing a direct, random access retrieval of the one or more software components from the vault; and

a client coupled to the vault, the client having a physical software component residing on the client, the client generating a key from the physical software component.

3. A computer-implemented vault for archiving software components, where only a single instance of each component that is multiply-used is stored in the vault, comprising:

unique instances of the one or more software components;

an access controller for performing a direct, random access retrieval of the one or more software components from the vault;

one or more secondary vaults coupled to the vault; and

a fault-tolerant rollover system for sequentially searching each vault for the presence of a target software component.

4. The computer-implemented vault of claim 3, wherein the secondary vaults are ordered based on accessibility of the vaults.

5. The computer-implemented vault of claim 3, further comprising a client for generating a key, the client applying the key to recover the target software component from the most accessible of the vaults.

6. The computer-implemented vault of claim 5, wherein the client uses a metadata description to generate the key.

7. The computer-implemented vault of claim 5, wherein the search of a determined vault fails to locate the target software component, and wherein the client skips the determined vault and modifies the search order of the vaults in recovering the target software component.

8. A computer-implemented vault for archiving software components, where only a single instance of each component that is multiply-used is stored in the vault, comprising:

means for storing unique instances of the one or more software components on the vault;

access means for performing a direct, random access retrieval of the one or more software components from the vault; and

a post means for performing a direct, random access insertion of a software component to the vault wherein the post means generates a unique key from the new component and optimizes storage if the unique key exists.

9. A computer-implemented vault for archiving software components, where only a single instance of each component that is multiply-used is stored in the vault, comprising:

means for storing unique instances of the one or more software components on the vault;

access means for performing a direct, random access retrieval of the one or more software components from the vault; and

a client coupled to the vault, the client having a physical software component residing on the client, the client generating a key from the physical software component.

10. A computer-implemented vault for archiving software components, where only a single instance of each component that is multiply-used is stored in the vault, comprising:

means for storing unique instances of the one or more software components on the vault;

access means for performing a direct, random access retrieval of the one or more software components from the vault;

one or more secondary vaults coupled to the vault; and

means for sequentially searching each vault for the presence of a target software component.

11. The computer-implemented vault of claim 10, wherein the secondary vaults are ordered based on accessibility of the vaults.

12. The computer-implemented vault of claim 10, further comprising a client for generating a key, the client having a means for applying the key to recover the target software component from the most accessible of the vaults.

13. The computer-implemented vault of claim 12, wherein the client uses a metadata description to generate the key.

14. The computer-implemented vault of claim 12, wherein the search of a determined vault fails to locate the target software component, and wherein the client skips the determined vault and modifies the search order of the vaults in recovering the target software component.

19. The method of claim 12, further comprising a client for generating a key, the client applying the key to recover the target software component from the most accessible of the vaults.

20. The method of claim 19, wherein the client uses a metadata description to generate the key.

21. The method of claim 19, wherein the search of a determined vault fails to locate the target software component, and wherein the client skips the determined vault and modifies the search order of the vaults in recovering the target software component.

15. A method for archiving software components where only a single instance of each component that is multiply-used is stored in a vault, comprising the steps of:

storing unique instances of the one or more software components in the vault; and

performing a direct, random access retrieval of the one or more software components from the vault; and

performing a direct, random access insertion of a software component to the vault wherein said step of performing an insertion generates a unique key from the new component and optimizes storage if the key exists.

16. A method for archiving software components where only a single instance of each component that is multiply-used is stored in a vault, comprising the steps of:

storing unique instances of the one or more software components in the vault;

performing a direct, random access retrieval of the one or more software components from the vault; and

generating a key from a physical software component residing on a client coupled to the vault.

17. A method for archiving software components where only a single instance of each component that is multiply-used is stored in a vault, and wherein one or more secondary vaults are coupled to the vault, comprising the steps of:

storing unique instances of the one or more software components in the vault; and

performing a direct, random access retrieval of the one or more software components from the vault; and

sequentially searching each vault for the presence of a target software component.

18. The method of claim 17, wherein the secondary vaults are ordered based on accessibility of the vaults.