Application aware storage appliance archiving

• US 7,827,150 B1
• Filed: 04/30/2007
• Issued: 11/02/2010
• Est. Priority Date: 04/30/2007
• Status: Active Grant

• Current Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Original Assignee: Symantec Corporation (NortonLifeLock Inc.)
• Inventors: Cheng, Kent, Wu, Weibao
• Primary Examiner(s): TO, BAOQUOC N
• Application Number:
  US11/799,506
• Time in Patent Office: 1,282 Days
• Field of Search: None
• US Class Current: 707/674
• CPC Class Codes: G06F 16/164 File meta data generation

Abstract

Various embodiments of a computer system and methods are disclosed. In one embodiment, a computer system includes a host coupled to a backup store. The host backs up a dataset to the backup store. The dataset comprises data entities and application-specific metadata describing the data entities. The application-specific metadata enables an application to use the data entities. The host: mounts the backup store for read/write access by the application, accesses the backup store with the application, selects a data entity, and performs an operation on the data entity in the backup store using the application. The operation may comprise verifying that the data entity is valid and usable in the context of the application or creating an archival backup of the data entity on a backup medium. The backup store may be a disk-based backup store and the backup medium may be a tape-based backup medium.

Claims

1. A computer system comprising:

a client computer;

a host computer coupled to the client and a backup store; and

a server coupled to the host, the client, and an archival backup medium;

wherein the host is configured to;

mount a dataset stored on the client with a first application;

use the first application to perform a backup operation to backup the dataset to the backup store, wherein the dataset on the backup store is mountable for read/write access; and

associate the dataset on the backup store with first metadata that identifies the client as an origin of the dataset, wherein the first metadata enables restoration of the dataset to the client directly from the backup store;

wherein the server is configured to;

mount the dataset stored on the backup store with a second application different from the first application;

use the second application to perform a backup operation to create an archival backup of the dataset stored on the backup store, and store the archival backup on an archival backup medium;

associate the archival backup with second metadata that identifies the backup store as an origin of the dataset; and

modify the second metadata to identify the client as an origin of the dataset rather than the backup store, wherein the second metadata as modified enables restoration of the archival backup directly from the archival backup medium to the client.

2. The system as recited in claim 1, wherein to modify the second metadata, the server is further configured to access and utilize the first metadata to determine particulars regarding how the dataset was originally stored on the client.

3. The system as recited in claim 2, wherein said particulars comprise a hostname of the client, logical data paths of the client, and/or physical data paths of the client.

4. The system as recited in claim 2, wherein the backup store comprises a disk-based backup store and the backup medium is a tape-based backup medium.

5. The system as recited in claim 1, wherein the backup store is further configured to:

store a plurality of data objects and a plurality of data segments, wherein each data object corresponds to a data entity and references one or more of the plurality of data segments; and

de-duplicate the one or more data segments against previously stored data segments prior to storing them.

6. The system as recited in claim 1, further comprising a catalog configured to store metadata describing the plurality of data entities;

wherein the host is further configured to access the backup store through a virtual file system interface; and

wherein the virtual file system interface is configured to use metadata from the catalog to enable the application to write data to data objects in the backup store.

7. The system as recited in claim 6, wherein the application-specific metadata is different from the metadata stored in the catalog.

8. A computer implemented method comprising:

mounting a dataset stored on a client with a first application;

utilizing the first application to perform a backup operation to backup the dataset to a backup store, wherein the dataset on the backup store is mountable for read/write access;

associating the dataset on the backup store with first metadata that identifies the client as an origin of the dataset, wherein the first metadata enables restoration of the dataset to the client directly from the backup store;

mounting the dataset stored on the backup store with a second application different from the first application;

utilizing the second application to perform a backup operation to create an archival backup of the dataset stored on the backup store, and store the archival backup on an archival backup medium;

associating the archival backup with second metadata that identifies the backup store as an origin of the dataset; and

modifying the second metadata to identify the client as an origin of the dataset rather than the backup store, wherein the second metadata as modified enables restoration of the archival backup directly from the archival backup medium to the client.

9. The method of claim 8, wherein said modifying the second metadata comprising accessing and utilizing the first metadata to determine particulars regarding how the dataset was originally stored on the client.

10. The method of claim 9, wherein said particulars comprise a hostname of the client, logical data paths of the client, and/or physical data paths of the client.

11. The method as recited in claim 9, wherein the backup store comprises a disk-based backup store and the backup medium is a tape-based backup medium.

12. The method of claim 8, wherein the backup store stores a data entity as a data object and one or more data segments, wherein the data object includes references to each of the one or more data segments, the method further comprising the backup store de-duplicating the one or more data segments against previously stored data segments prior to storing them.

13. The method as recited in claim 8, further comprising:

storing metadata describing the plurality of data entities in a catalog;

accessing the backup store through a virtual file system interface, wherein the virtual file system interface is configured to use metadata from the catalog to enable the application to write data to data objects in the backup store.

14. The method as recited in claim 13, wherein the application-specific metadata is different from the metadata stored in the catalog.

15. A plurality of computer readable storage media storing computer instructions that are executable by a processor to:

mount a dataset stored on a client with a first application;

use the first application to perform a backup operation to backup the dataset to a backup store, wherein the dataset on the backup store is mountable for read/write access;

associate the dataset on the backup store with first metadata that identifies the client as an origin of the dataset, wherein the first metadata enables restoration of the dataset to the client directly from the backup store;

mount the dataset stored on the backup store with a second application different from the first application;

use the second application to perform a backup operation to create an archival backup of the dataset stored on the backup store, and store the archival backup on an archival backup medium;

associate the archival backup with second metadata that identifies the backup store as an origin of the dataset; and

modify the second metadata to identify the client as an origin of the dataset rather than the backup store, wherein the second metadata as modified enables restoration of the archival backup directly from the archival backup medium to the client.

16. The computer readable medium as recited in claim 15, wherein to modify the second metadata, the program instructions are further executable to access and utilize the first metadata to determine particulars regarding how the dataset was originally stored on the client.

17. The computer readable medium as recited in claim 16, wherein said particulars comprise a hostname of the client, logical data paths of the client, and/or physical data paths of the client.

18. The computer readable medium as recited in claim 16, wherein the backup store comprises a disk-based backup store and the backup medium is a tape-based backup medium.

19. The computer readable medium as recited in claim 15, wherein the backup store is configured to store a data entity as a data object and one or more data segments, wherein the data object includes references to each of the one or more data segments;

and wherein the instructions are further executable to de-duplicate the one or more data segments against previously stored data segments prior to storing them.

20. The computer readable medium as recited in claim 15, wherein the instructions are further executable to:

store metadata describing the plurality of data entities in a catalog;

access the backup store through a virtual file system interface, wherein the virtual file system interface is configured to use metadata from the catalog to enable the application to write data to data objects in the backup store.