# Patent

## Title
Scalable de-duplication mechanism

## Abstract

A method for removing redundant data from a backup storage system is presented. In one example, the method may include receiving the application layer data object, selecting a de-duplication domain from a plurality of de-duplication domains based at least in part on a data object characteristic associated with the de-duplication domain, determining that the application layer data object has the characteristic and directing the application layer data object to the de-duplication domain.

## Background
RELATED APPLICATIONS
This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Application Ser. No. 61/021,501, entitled “Scalable De-duplication Mechanism,” filed on Jan. 16, 2008, and is a continuation-in-part of, and claims priority under 35 U.S.C. §120 to, pending U.S. patent application Ser. No. 11/771,245 filed Jun. 29, 2007, entitled “Emulated Storage System” which is a continuation-in-part of, and claims priority under 35 U.S.C. §120 to, U.S. patent application Ser. No. 11/593,266 filed Nov. 6, 2006, entitled “Emulated Storage System” and now U.S. Pat. No. 7,430,647, which is a continuation of, and claims priority under 35 U.S.C. §120 to, U.S. patent application Ser. No. 10/911,987, filed Aug. 5, 2004, entitled “Emulated Storage System” and now U.S. Pat. No. 7,146,476, which claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Application No. 60/492,576, entitled “Synthetic Full Back-up Method,” filed on Aug. 5, 2003 and U.S. Provisional Application No. 60/492,827, entitled “End-User File Restore Method,” filed on Aug. 6, 2003, each of which is hereby incorporated by reference in its entirety.


BACKGROUND
1. Field of Invention
Aspects of the present invention relate to data storage, and more particularly to apparatus and methods for providing scalable data de-duplication services.
2. Discussion of Related Art
Many computer systems include one or more host computers and one or more data storage systems that store data used by the host computers. These host computers and storage systems are typically networked together using a network such as a Fibre Channel network, an Ethernet network, or another type of communication network. Fibre Channel is a standard that combines the speed of channel-based transmission schemes and the flexibility of network-based transmission schemes and allows multiple initiators to communicate with multiple targets over a network, where the initiator and the target may be any device coupled to the network. Fibre Channel is typically implemented using a fast transmission media such as optical fiber cables, and is thus a popular choice for storage system networks where large amounts of data are transferred.
An example of a typical networked computing environment including several host computers and back-up storage systems is shown in FIG. 1. One or more application servers 102 are coupled via a local area network (LAN) 103 to a plurality of user computers 104. Both the application servers 102 and the user computers 104 may be considered “host computers.” The application servers 102 are coupled to one or more primary storage devices 106 via a storage area network (SAN) 108. The primary storage devices 106 may be, for example, disk arrays such as are available from companies like EMC Corporation, IBM Corporation and others. Alternatively, a bus (not shown) or other network link may provide an interconnect between the application servers and the primary storage system 106. The bus and/or Fibre Channel network connection may operate using a protocol, such as the Small Component System Interconnect (SCSI) protocol, which dictates a format of packets transferred between the host computers (e.g., the application servers 102) and the storage system(s) 106.
It is to be appreciated that the networked computing environment illustrated in FIG. 1 is typical of a large system as may be used by, for example, a large financial institution or large corporation. It is to be understood that many networked computing environments need not include all the elements illustrated in FIG. 1. For example, a smaller networked computing environment may simply include host computers connected directly, or via a LAN, to a storage system. In addition, although FIG. 1 illustrates separate user computers 104, application servers 102 and media servers 114, these functions may be combined into one or more computers.
In addition to primary storage devices 106, many networked computer environments include at least one secondary or back-up storage system 110. The back-up storage system 110 may typically be a tape library, although other large capacity, reliable secondary storage systems may be used. Typically, these secondary storage systems are slower than the primary storage devices, but include some type of removable media (e.g., tapes, magnetic or optical disks) that may be removed and stored off-site.
In the illustrated example, the application servers 102 may be able to communicate directly with the back-up storage system 110 via, for example, an Ethernet or other communication link 112. However, such a connection may be relatively slow and may also use up resources, such as processor time or network bandwidth. Therefore, a system such as illustrated may include one or more media servers 114 that may provide a communication link 115, using for example, Fibre Channel, between the SAN 108 and the back-up storage system 110.
The media servers 114 may run software that includes a back-up/restore application that controls the transfer of data between host computers (such as user computers 104, the media servers 114, and/or the application servers 102), the primary storage devices 106 and the back-up storage system 110. Examples of back-up/restore applications are available from companies like Veritas, Legato and others. For data protection, data from the various host computers and/or the primary storage devices in a networked computing environment may be periodically backed-up onto the back-up storage system 110 using a back-up/restore application, as is known in the art.
Of course, it is to be appreciated that, as discussed above, many networked computer environments may be smaller and may include fewer components than does the exemplary networked computer environment illustrated in FIG. 1. Therefore, it is also to be appreciated that the media servers 114 may in fact be combined with the application servers 102 in a single host computer, and that the back-up/restore application may be executed on any host computer that is coupled (either directly or indirectly, such as through a network) to the back-up storage system 110.
One example of a typical back-up storage system is a tape library that includes a number of tape cartridges and at least one tape drive, and a robotic mechanism that controls loading and unloading of the cartridges into the tape drives. The back-up/restore application provides instructions to the robotic mechanism to locate a particular tape cartridge, e.g., tape number 0001, and load the tape cartridge into the tape drive so that data may be written onto the tape. The back-up/restore application also controls the format in which data is written onto the tapes. Typically, the back-up/restore application may use SCSI commands, or other standardized commands, to instruct the robotic mechanism and to control the tape drive(s) to write data onto the tapes and to recover previously written data from the tapes.
Conventional tape library back-up systems suffer from a number of problems including speed, reliability and fixed capacity. Many large companies need to back-up Terabytes of data each week. However, even expensive, high-end tapes can usually only read/write data at speeds of 30-40 Megabytes per second (MB/s), which translates to about 50 Gigabyte per hour (GB/hr). Thus, to back-up one or two Terabytes of data to a tape back-up system may take at least 10 to 20 hours of continuous data transfer time.
In addition, most tape manufacturers will not guarantee that it will be possible to store (or restore) data to/from a tape if the tape is dropped (as may happen relatively frequently in a typical tape library because either a human operator or the robotic mechanism may drop a tape during a move or load operation) or if the tape is exposed to non-ideal environmental conditions, such as extremes in temperature or moisture. Therefore, a great deal of care needs to be taken to store tapes in a controlled environment. Furthermore, the complex machinery of a tape library (including the robotic mechanism) is expensive to maintain and individual tape cartridges are relatively expensive and have limited lifespans.
Given the costs associated with conventional tape libraries and other sorts of back-up storage media, vendors often incorporate de-duplication processes into their product offerings to decrease the total back-up media requirements. De-duplication is a process of identifying repeating sequences of data over time—that is, it is a manifestation of delta compression. De-duplication is typically implemented as a function of a target device, such as a back-up storage device. The act of identifying redundant data within back-up data streams is complex, and in the current state-of-the-art, is conventionally solved using either hash fingerprinting and pattern recognition.
In hash fingerprinting, the incoming data stream first undergoes an alignment process (which attempts to predict good “breakpoints”, also known as edges, in the data stream that will provide the highest probability of subsequent matches) and then is subject to a hashing process (usually SHA-1 in the current state-of-the-art). The data stream is broken into chunks (usually about 8 kilobytes-12 kilobytes in size) by the hashing process; each chunk is assigned its resultant hash value. This hash value is compared against a memory-resident table. If the hash entry is found, the data is assumed to be redundant and replaced with a pointer to the existing block of data already stored in a disk storage system; the location of the existing data is given in the table. If the hash entry is not found; the data is stored in a disk storage system and its location recorded in the memory-resident table along with its hash. Some examples that illustrate this mechanism can be found in U.S. Pat. Nos. 7,065,619 assigned to Data Domain and 5,990,810 assigned to Quantum Corporation. Hash fingerprinting is typically executed in-line; that is, data is processed in real-time prior to being written to disk.
According to pattern recognition, the incoming data stream is first “chunked” or segmented into relatively large data blocks (on the order of about 32 MB). The data is then processed by a simple rolling hash method whereby a list of hash values is assembled. A transformation is made on the hash values where a resulting small list of values represents a data block “fingerprint.” A search is then made on a table of hashes to look for at least a certain number of fingerprint hashes to be found in any other given stored block. If a minimum number of matches is not met, then the block is considered unique and stored directly to disk. The corresponding fingerprint hashes are added to a memory-resident table. Should the minimum number of matches be met, then there is a probability that the current data block matches a previously-stored data block. In this case, the block of disk storage assigned by a matching fingerprint is read into memory and compared byte-for-byte against the candidate block that had been hashed. If the full sequence of data is equal, then the data block is replaced by a pointer to the physically addressed block of storage. If the full block does not match, then a delta-differencing mechanism is employed to determine a minimal data set within the block that need be stored. The result is a combination of unique data plus references to a closely-matching block of previously-stored data. An example that illustrates this mechanism can be found in U.S. Patent Application US2006/0059207 assigned to Diligent Corporation. As above, this operation is typically executed in-line.
SUMMARY OF INVENTION
Aspects and embodiments of the present invention provide a data storage system that overcomes or alleviates some or all of the problems of conventional data de-duplication techniques and that may provide greater efficacy and scalability than do data storage systems that incorporate conventional de-duplication techniques.
In broad overview, aspects and embodiments of the present invention provide a random-access based storage system that emulates a conventional tape back-up storage system such that a back-up/restore application sees the same view of devices and media as with a physical tape library. The storage system of the invention uses software and hardware to emulate physical tape media and replace them with one or more random-access disk arrays, translating tape format, linear, sequential data to data that is suitable for storage on disk.
According to some aspects and embodiments of the present invention, there is provided a mechanism for decoding existing back-up data sets and storing the metadata (i.e., data that represents information about user data) in a searchable metadata cache, a mechanism to allow searching and/or viewing of the metadata cache for files or objects, and a mechanism for downloading these files or objects via a web connection from data stored through existing back-up policies and practices of typical back-up software. Also included may be a mechanism for authenticating a user through existing authentication mechanisms, and for limiting the view of the metadata cache based on a current user's credentials.
Aspects and embodiments of the present invention also provide for removal of redundant data from back-up data objects. This removal process, which may be termed “de-duplication,” decreases the storage capacity required to maintain copies of back-up data and thus decreases the amount of electronic media required to store back-up data. Embodiments of the de-duplication process in accordance with at least some aspects of the present invention make efficient use of computing resources by using metadata to optimize de-duplication processing.
As is discussed further below, some embodiments are directed to intelligent direction of the overall de-duplication process. In some of these embodiments, a data storage system uses software and hardware to direct data objects to one of several de-duplication domains for de-duplication and storage. In addition, applications implemented in hardware and/or software are provided for configuring the de-duplication domains that manage the de-duplication of data within the constraints presented by a given data storage system. Some embodiments manifest an appreciation that conventional hash fingerprinting techniques are constrained by the amount of available memory. Other embodiments reflect an appreciation that random I/O workload is a substantial limitation under the pattern recognition approach. Thus, these embodiments manifest an appreciation of the limitations imposed by the conventional hash fingerprinting and pattern recognition de-duplication techniques.
According to other aspects and embodiments of the invention, there is provided a mechanism for performing a logical merge of multiple cartridge representations in a metadata cache, and a mechanism for appropriately labeling and barcoding a newly synthesized cartridge such that it is accepted by back-up/restore software as a valid data set. Also, according to further aspects and embodiments of the invention, there is provided a mechanism for either storing multiple copies of data elements that represent a synthetic cartridge, or for storing only pointers to existing data represented in the metadata cache.
According to one embodiment, a method for directing de-duplication of an application layer data object is provided. The method includes acts of receiving the application layer data object, selecting a de-duplication domain from a plurality of de-duplication domains based at least in part on a data object characteristic associated with the de-duplication domain, determining that the application layer data object has the characteristic and directing the application layer data object to the selected de-duplication domain.
In one example, the act of receiving the application layer data object may include acts of receiving a data stream and identifying the application layer data object using metadata included in the data stream. In another example, the act of receiving the data stream may include an act of receiving a multiplexed data stream. According to another example, the method may further include an act of extracting metadata included in the data stream with the application layer data object. In yet another example, the act of selecting the de-duplication domain from the plurality of de-duplication domains may include an act of comparing the extracted metadata associated with the application layer data object to the at least one characteristic associated with the de-duplication domain. According to a further example, the act of extracting the metadata included in the data stream may include an act of extracting at least one of a back-up policy name, a data source type, a data source name, a back-up application name, an operating system type, a data type, a back-up type, a filename, a directory structure and chronological information.
In another example, the method may further include an act of configuring each of the plurality of de-duplication domains to use one of a plurality of de-duplication methods. According to another example, the act of configuring each of the plurality of de-duplication domains may include an act of configuring each of the plurality of de-duplication domains to use one de-duplication method selected from the group comprising hash-fingerprinting, pattern recognition and content aware de-duplication. In still another example, the method may further include an act of associating each of the plurality of de-duplication domains with at least one data object characteristic. According to an additional example, the method may further include acts of de-duplicating, within the selected de-duplication domain, the application layer data object and adjusting the data object characteristic associated with at least one of the plurality of de-duplication domains based on a result of the act of de-duplicating. In a further example, the act of adjusting the data object characteristic may include storing data in a de-duplication domain database.
According to another embodiment, a grid computing environment is provided to execute the acts of the method for directing de-duplication of an application layer data object discussed above.
According to another embodiment, a back-up storage system is provided to execute the acts of the method for directing de-duplication of an application layer data object discussed above. In this embodiment, the method is executed while data is not being backed-up to the backup storage system.
According to another embodiment, a back-up storage system is provided to execute the acts of the method for directing de-duplication of an application layer data object discussed above. In this embodiment, the method is executed while data is being backed-up to the backup storage system.
According to another embodiment, a computer-readable medium having computer-readable signals stored thereon that define instructions is provided. These instructions, as a result of being executed by a computer, instruct the computer to perform acts of receiving the application layer data object, selecting a de-duplication domain from a plurality of de-duplication domains based at least in part on a data object characteristic associated with the de-duplication domain, determining that the application layer data object has the characteristic and directing the application layer data object to the selected de-duplication domain.
According to another embodiment a system for directing de-duplication of an application layer data object is provided. The system includes a plurality of de-duplication domains, each de-duplication domain of the plurality of de-duplication domains associated with at least one characteristic common to a plurality of application layer data objects and a controller coupled to the plurality of de-duplication domains and configured to receive the application layer data object, determine that the application layer data object has the at least one characteristic associated with a de-duplication domain and direct the application layer data object to the de-duplication domain.
In an example, the controller may be further configured to receive a data stream and identify the application layer data object using metadata included in the data stream. In another example, the data stream may be multiplexed. In another example, the controller may be further configured to extract metadata included in the data stream with the application layer data object. In still another example, the controller may be further configured to determine that the application layer data object has the at least one characteristic associated with the de-duplication domain by comparing the extracted metadata associated with the application layer data object to the at least one characteristic associated the with de-duplication domain. In a further example, the controller may be further configured to extract at least one of a back-up policy name, a data source type, a data source name, a back-up application name, an operating system type, a data type, a back-up type, a filename, a directory structure and chronological information. In an additional example, the controller may be further arranged to configure each of the plurality of de-duplication domains to use one of a plurality of de-duplication methods. In yet another example, the controller may be further arranged to configure each of the plurality of de-duplication domains to use one de-duplication method selected from the group comprising hash-fingerprinting, pattern recognition and content aware de-duplication.
According to another example, the controller may be further configured to associate each of the plurality of de-duplication domains with at least one data object characteristic. In another example, the controller may be further configured to cause, within the selected de-duplication domain, de-duplication of the application layer data object and adjust the data object characteristic associated with at least one of the plurality of de-duplication domains based on a result of the act of de-duplicating. In still another example, the controller may be further configured to store data in a de-duplication domain database. In another example the system may be included in a grid computing environment. In yet another example, the controller may be further configured to receive the application layer data object, determine that the application layer data object has the at least one characteristic associated with a de-duplication domain and direct the application layer data object to the de-duplication domain while data is not being backed-up to the system. Additionally, according to an example, the controller may be further configured to receive the application layer data object, determine that the application layer data object has the at least one characteristic associated with a de-duplication domain and direct the application layer data object to the de-duplication domain while data is being backed-up to the system.
Still other aspects, embodiments, and advantages of these exemplary aspects and embodiments, are discussed in detail below. Moreover, it is to be understood that both the foregoing information and the following detailed description are merely illustrative examples of various aspects and embodiments, and are intended to provide an overview or framework for understanding the nature and character of the claimed aspects and embodiments. The accompanying drawings are included to provide illustration and a further understanding of the various aspects and embodiments, and are incorporated in and constitute a part of this specification. The drawings, together with the remainder of the specification, serve to explain principles and operations of the described and claimed aspects and embodiments.



BRIEF DESCRIPTION OF DRAWINGS
Various aspects of at least one embodiment are discussed below with reference to the accompanying figures. In the figures, which are not intended to be drawn to scale, each identical or nearly identical component that is illustrated in various figures is represented by a like numeral. For purposes of clarity, not every component may be labeled in every drawing. The figures are provided for the purposes of illustration and explanation and are not intended as a definition of the limits of the invention. In the figures:
FIG. 1 is a block diagram of one example of a large-scale networked computing environment that includes a back-up storage system;
FIG. 2 is a block diagram of one example of a networked computing environment including a storage system according to aspects of the invention;
FIG. 3 is a block diagram of one example of a storage system according to aspects of the invention;
FIG. 4 is a block diagram illustrating a virtual layout of one example of a storage system according to aspects of the invention;
FIG. 5 is a schematic layout of one example of a system file according to aspects of the invention;
FIG. 6 is one example of a tape directory structure according to aspects of the invention;
FIG. 7 is a diagram depicting one example of a method of creating a synthetic full back-up according to aspects of the invention;
FIG. 8 is a schematic diagram of one example, of a series of back-up data sets including a synthetic full back-up according to aspects of the invention;
FIG. 9 is a diagram of one example, of a metadata cache structure;
FIG. 10 is a diagram of one example of a virtual cartridge storing a synthetic full back-up data set;
FIG. 11 is a diagram of another examples of a virtual cartridge storing a synthetic full back-up data set;
FIG. 12 is a flow diagram of a method of de-duplicating data objects in accordance with the present invention;
FIG. 13A is a diagram of two back-up data objects;
FIG. 13B is a diagram of de-duplicated copies of the back-up data objects depicted in FIG. 13A;
FIG. 13C is another diagram of de-duplicated copies of the back-up data objects depicted in FIG. 13A;
FIG. 14 is a block diagram of one example of a de-duplication director according to aspects of the invention; and
FIG. 15 is a flow diagram of a method of directing de-duplication of data objects in accordance with the present invention.



DETAILED DESCRIPTION
Various embodiments and aspects thereof will now be described in more detail with reference to the accompanying figures. It is to be appreciated that this invention is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the drawings. The invention is capable of other embodiments and of being practiced or of being carried out in various ways. Examples of specific implementations are provided herein for illustrative purposes only and are not intended to be limiting. In particular, acts, elements and features discussed in connection with any one or more embodiments are not intended to be excluded from a similar role in any other embodiments. Also, the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including,” “comprising,” “having,” “containing,” “involving,” and variations thereof herein, is meant to encompass the items listed thereafter and equivalents thereof as well as additional items.
Any embodiment disclosed herein may be combined with any other embodiment, and references to “an embodiment,” “some embodiments,” “an alternate embodiment,” “various embodiments,” “one embodiment,” “at least one embodiment,” “this and other embodiments” or the like are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment. Such terms as used herein are not necessarily all referring to the same embodiment. Any embodiment may be combined with any other embodiment in any manner consistent with the aspects disclosed herein. References to “or” may be construed as inclusive so that any terms described using “or” may indicate any of a single, more than one, and all of the described terms.
As used herein, the term “host computer” refers to any computer that has at least one processor, such as a personal computer, a workstation, a mainframe, a networked client, a server, etc. that is capable of communication with other devices, such as a storage system or other host computers. Host computers may include media servers and application servers (as described previously with reference to FIG. 1) as well as user computers (which may be user workstations, PCs, mainframes, etc.). In addition, within this disclosure, the term “networked computer environment” includes any computing environment in which a plurality of host computers are connected to one or more shared storage systems in such a manner that the storage system(s) can communicate with each of the host computers. Fibre Channel is one example of a communication network that may be used with embodiments of the present invention. However, it is to be appreciated that the networks described herein are not limited to Fibre Channel, and that the various network components may communicate with each other over any network connection, such as Token Ring or Ethernet instead of, or in addition to Fibre Channel, or over combinations of different network connections. Moreover, aspects of the present invention may also be used in bus topologies, such as SCSI or parallel SCSI.
According to various embodiments and aspects of the present invention, there is provided a virtual removable media library back-up storage system that may use one or more disk arrays to emulate a removable media based storage system. Using embodiments of the invention, data may be backed-up onto the disk array(s) using the same back-up/restore application as would have been used to back-up the data onto removable media (such as tapes, magnetic disks, optical disks, etc.), without a user having to make any modifications or adjustments to the existing back-up procedures or having to purchase a new back-up/restore application. In one embodiment, described in detail herein, the removable media that are emulated are tapes, and the back-up storage system of the invention emulates a tape library system including tapes and the robotic mechanism used to handle tapes in a conventional tape library system.
The data that may be backed-up and restored using embodiments of the invention may be organized into various data objects. These data objects may include any structure into which data may be stored. A non-limiting list of exemplary data objects includes bits, bytes, data files, data blocks, data directories, back-up data sets and virtual cartridges, which are discussed further below. Although the bulk of this disclosure refers to back-up and restore of data files, embodiments of the invention may manipulate any data object and it is to be appreciated that the term “data file” is interchangeable with “data object.” In addition, as would be appreciated by one of ordinary skill in the art, embodiments described herein operate at the application layer of the Open System Interconnection (OSI) model and are built with reliance on other software and/or hardware to provide the basic network services represented by the other OSI model layers.
In addition, embodiments may de-duplicate backed-up data to more efficiently utilize available computing resources. According to some embodiments, data de-duplication may be performed in-line, i.e. while a data storage system is receiving data to be de-duplicated and stored. In other embodiments, data de-duplication may be performed off-line, i.e. after the data storage system has already stored the data to be de-duplicated. As is detailed further below, embodiments may intelligently direct a variety of conventional and non-conventional de-duplication techniques to provide highly scalable de-duplication services.
A storage system according to aspects of the invention includes hardware and software that together interface with a host computer (running the back-up/restore application) and a back-up storage media. The storage system may be designed to emulate tapes, or other types of removable storage media, such that the back-up/restore application sees the same view of devices and media as with a physical tape library, and to translate linear, sequential, tape format data into data that is suitable for storage on random-access disks. In this manner, the storage system of the invention may provide enhanced functionality (such as, allowing users to search for individual back-up user files, as discussed below) without requiring new back-up/restore application software or policies.
Referring to FIG. 2, there is illustrated in block diagram form, one embodiment of a networked computing environment including a back-up storage system 170 according to aspects of the invention. As illustrated, a host computer 120 is coupled to the storage system 170 via a network connection 121. This network connection 121 may be, for example a Fibre Channel connection to allow high-speed transfer of data between the host computer 120 and the storage system 170. It is to be appreciated that the host computer 120 may be, or may include, one or more application servers 102 (see FIG. 1) and/or media servers 114 (see FIG. 1) and may enable back-up of data from either any of the computers present in the networked computing environment or from a primary storage device 106 (see FIG. 1). In addition, one or more user computers 136 may also be coupled to the storage system 170 via another network connection 138, such as an Ethernet connection. As discussed in detail below, the storage system may enable users of the user computer 136 to view and optionally restore back-up user files from the storage system.
The storage system includes back-up storage media 126 that may be, for example, one or more disk arrays, as discussed in more detail below. The back-up storage media 126 provide the actual storage space for back-up data from the host computer(s) 120. However, the storage system 170 may also include software and additional hardware that emulates a removable media storage system, such as a tape library, such that, to the back-up/restore application running on the host computer 120, it appears as though data is being backed-up onto conventional removable storage media. Thus, as illustrated in FIG. 2, the storage system 170 may include “emulated media” 134 which represent, for example, virtual or emulated removable storage media such as tapes. These “emulated media” 134 are presented to the host computer by the storage system software and/or hardware and appear to the host computer 120 as physical storage media. Further interfacing between the emulated media 134 and the actual back-up storage media 126 may be a storage system controller (not shown) and a switching network 132 that accepts the data from the host computer 120 and stores the data on the back-up storage media 126, as discussed more fully in detail below. In this manner, the storage system “emulates” a conventional tape storage system to the host computer 120.
According to one embodiment, the storage system may include a “logical metadata cache” 242 that stores metadata relating to user data that is backed-up from the host computer 120 onto the storage system 170. As used herein, the term “metadata” refers to data that represents information about user data and describes attributes of actual user data. A non-limiting exemplary list of metadata regarding data objects may include data object size, logical and/or physical location of the data object in primary storage, the creation date of the data object, the date of the last modification of the data object, the back-up policy name under which the data objected was stored, an identifier, e.g. a name or watermark, of the data object and the data type of the data object, e.g. a software application associated with the data object. The logical metadata cache 242 represents a searchable collection of data that enables users and/or software applications to randomly locate back-up user files, compare user files with one another, and otherwise access and manipulate back-up user files. Two examples of software applications that may use the data stored in the logical metadata cache 242 include a synthetic full back-up application 240 and an end-user restore application 300 that are discussed more fully below. In addition, a de-duplication director, which is discussed in more detail below, may use metadata to provide scalable de-duplication services within a storage system.
In brief overview, the synthetic full back-up application 240 is capable of creating a synthetic full back-up data set from one existing full back-up data set and one or more incremental back-up data sets. The synthetic full backup may obviate the need to perform periodic (e.g., weekly) full back-ups, thereby saving considerable time and network resources. Details of the synthetic full back-up application 240 are described further below. The end-user restore application 300, also described more fully in detail below, enables end-users (e.g., operators of the user computers 136) to browse, locate, view and/or restore previously backed-up user files from the storage system 170.
As discussed above, the storage system 170 includes hardware and software that interface with the host computer 120 and the back-up storage media 126. Together, the hardware and software of embodiments of the invention may emulate a conventional tape library back-up system such that, from the point of view of the host computer 120, data appears to be backed-up onto tape, but is in fact backed-up onto another storage medium, such as, for example, a plurality of disk arrays.
Referring to FIG. 3, there is illustrated in block diagram form, one example of a storage system 170 according to aspects of the invention. In one example, the hardware of the storage system 170 includes a storage system controller 122 and a switching network 132 that connects the storage system controller 122 to the back-up storage media 126. The storage system controller 122 includes a processor 127 (which may be a single processor or multiple processors) and a memory 129 (such as RAM, ROM, PROM, EEPROM, Flash memory, etc. or combinations thereof) that may run all or some of the storage system software. The memory 129 may also be used to store metadata relating to the data stored on the back-up storage media 126. Software, including programming code that implements embodiments of the present invention, is generally stored on a computer readable and/or writeable nonvolatile recording medium, such as RAM, ROM, optical or magnetic disk or tape, etc., and then copied into memory 129 wherein it may then be executed by the processor 127. Such programming code may be written in any of a plurality of programming languages, for example, Assembler, Java, Visual Basic, C, C#, or C++, Fortran, Pascal, Eiffel, Basic, COBOL, or combinations thereof, as the present invention is not limited to a particular programming language. Typically, in operation, the processor 127 causes data, such as code that implements embodiments of the present invention, to be read from a nonvolatile recording medium into another form of memory, such as RAM, that allows for faster access to the information by the processor than does the nonvolatile recording medium.
As shown in FIG. 3, the controller 122 also includes a number of port adapters that connect the controller 122 to the host computer 120 and to the switching network 132. As illustrated, the host computer 120 is coupled to the storage system via a port adapter 124a, which may be, for example, a Fibre Channel port adapter. Via a storage system controller 122, the host computer 120 backs up data onto the back-up storage media 126 and can recover data from the back-up storage media 126.
In the illustrated example, the switching network 132 may include one or more Fibre Channel switches 128a, 128b. The storage system controller 122 includes a plurality of Fibre Channel port adapters 124b and 124c to couple the storage system controller to the Fibre Channel switches 128a, 128b. Via the Fibre Channel switches 128a, 128b, the storage system controller 122 allows data to be backed-up onto the back-up storage media 126. As illustrated in FIG. 3, the switching network 132 may further include one or more Ethernet switches 130a, 130b that are coupled to the storage system controller 122 via Ethernet port adapters 125a, 125b. In one example, the storage system controller 122 further includes another Ethernet port adapter 125c that may be coupled to, for example, a LAN 103 to enable the storage system 170 to communicate with host computes (e.g., user computers), as discussed below.
In the example illustrated in FIG. 3, the storage system controller 122 is coupled to the back-up storage media 126 via a switching network that includes two Fibre Channel switches and two Ethernet switches. Provision of at least two of each type of switch within the storage system 170 eliminates any single points of failure in the system. In other words, even if one switch (for example, Fibre Channel switch 128a) were to fail, the storage system controller 122 would still be able to communicate with the back-up storage media 126 via another switch. Such an arrangement may be advantageous in terms of reliability and speed. For example, as discussed above, reliability is improved through provision of redundant components and elimination of single points of failure. In addition, in some embodiments, the storage system controller is able to back-up data onto the back-up storage media 126 using some or all of the Fibre Channel switches in parallel, thereby increasing the overall back-up speed. However, it is to be appreciated that there is no requirement that the system comprise two or more of each type of switch, nor that the switching network comprise both Fibre Channel and Ethernet switches. Furthermore, in examples wherein the back-up storage media 126 comprises a single disk array, no switches at all may be necessary.
As discussed above, in one embodiment, the back-up storage media 126 may include one or more disk arrays. In one preferred embodiment, the back-up storage media 126 include a plurality of ATA or SATA disks. Such disks are “off the shelf” products and may be relatively inexpensive compared to conventional storage array products from manufacturers such as EMC, IBM, etc. Moreover, when one factors in the cost of removable media (e.g., tapes) and the fact that such media have a limited lifetime, such disks are comparable in cost to conventional tape-based back-up storage systems. In addition, such disks can read/write data substantially faster than can tapes. For example, over a single Fibre Channel connection, data can be backed-up onto a disk at a speed of at least about 150 MB/s, which translates to about 540 GB/hr, significantly faster (e.g., by an order of magnitude) than tape back-up speeds. In addition, several Fibre Channel connections may be implemented in parallel, thereby increasing the speed even further. In accordance with an embodiment of the present invention, back-up storage media may be organized to implement any one of a number of RAID (Redundant Array of Independent Disks) schemes. For example, in one embodiment, the back-up storage media may implement a RAID-5 implementation.
As discussed above, embodiments of the invention emulate a conventional tape library back-up system using disk arrays to replace tape cartridges as the physical back-up storage media, thereby providing a “virtual tape library.” Physical tape cartridges that would be present in a conventional tape library are replaced by what is termed herein as “virtual cartridges.” It is to be appreciated that for the purposes of this disclosure, the term “virtual tape library” refers to an emulated tape library which may be implemented in software and/or physical hardware as, for example, one or more disk array(s). It is further to be appreciated that although this discussion refers primarily to emulated tapes, the storage system may also emulate other storage media, for example, a CD-ROM or DVD-ROM, and that the term “virtual cartridge” refers generally to emulated storage media, for example, an emulated tape or emulated CD. In one embodiment, the virtual cartridge in fact corresponds to one or more hard disks.
Therefore, in one embodiment, a software interface is provided to emulate the tape library such that, to the back-up/restore application, it appears that the data is being backed-up onto tape. However, the actual tape library is replaced by one or more disk arrays such that the data is in fact being backed-up onto these disk array(s). It is to be appreciated that other types of removable media storage systems may be emulated and the invention is not limited to the emulation of tape library storage systems. The following discussion will now explain various aspects, features and operation of the software included in the storage system 170.
It is to be appreciated that although the software may be described as being “included” in the storage system 170, and may be executed by the processor 127 of the storage system controller 122 (see FIG. 3), there is no requirement that all the software be executed on the storage system controller 122. The software programs such as the synthetic full back-up application and the end-user restore application may be executed on the host computers and/or user computers and portions thereof may be distributed across all or some of the storage system controller, the host computer(s), and the user computer(s). Thus, it is to be appreciated that there is no requirement that the storage system controller be a contained physical entity such as a computer. The storage system 170 may communicate with software that is resident on a host computer such as, for example, the media server(s) 114 or application servers 102. In addition, the storage system may contain several software applications that may be run or resident on the same or different host computers. Moreover, it is to be appreciated that the storage system 170 is not limited to a discrete piece of equipment, although in some embodiments, the storage system 170 may be embodied as a discrete piece of equipment. In one example, the storage system 170 may be provided as a self-contained unit that acts as a “plug and play” (i.e., no modification need be made to existing back-up procedures and policies) replacement for conventional tape library back-up systems. Such a storage system unit may also be used in a networked computing environment that includes a conventional back-up system to provide redundancy or additional storage capacity. In another embodiment, the storage system 116 may be implemented in a distributed computing environment, such as a clustered or a grid environment.
As discussed above, according to one embodiment, the host computer 120 (which may be, for example, an application server 102 or media server 114, see FIG. 1) may back-up data onto the back-up storage media 126 via the network link (e.g., a Fibre Channel link) 121 that couples the host computer 120 to the storage system 170. It is to be appreciated that although the following discussion will refer primarily to the back-up of data onto the emulated media, the principles apply also to restoring back-up data from the emulated media. The flow of data between the host computer 120 and the emulated media 134 may be controlled by the back-up/restore application, as discussed above. From the view point of the back-up/restore application, it may appear that the data is actually being backed-up onto a physical version of the emulated media.
Referring to FIG. 4, the storage system software 150 may include one or more logical abstraction layer(s) that represent the emulated media and provide an interface between a back-up/restore application 140 resident on the host computer 120 and the back-up storage media 126. The software 150 accepts tape format data from the back-up/restore application 140 and translates that data into data suitable for storage on random-access disks (e.g., hard disks, optical disks and the like). In one example, this software 150 is executed on the processor 127 of the storage system controller 122 and may be stored in memory 129 (see FIG. 3).
According to one embodiment, the software 150 may include a layer, referred to herein as the virtual tape library (VTL) layer 142 that may provide a SCSI emulation of tapes, tape drives, and also the robotic mechanisms used to transfer tapes to and from the tape drives. The back-up/restore application 140 may communicate (e.g., back-up or write data to the emulated media) with the VTL 142 using, for example, SCSI commands, represented by arrows 144. Thus, the VTL may form a software interface between the other storage system software and hardware and the back-up/restore application, presenting the emulated storage media 134 (FIG. 2) to a back-up/restore application and allowing the emulated media to appear to the back-up/restore application as conventional removable back-up storage media.
A second software layer referred to herein as the file system layer 146 may provide an interface between the emulated storage media (represented in the VTL) and the physical back-up storage media 126. In one example, the file system, 146 acts as a mini operating system to communicate with the back-up storage media 126 using, for example, SCSI commands, represented by arrows 148, to read and write data to and from the back-up storage media 126.
In one embodiment, the VTL provides generic tape library support and may support any SCSI media changer. Emulated tape devices may include, but are not limited to, an IBM LTO-1 and LTO-2 tape device, a QUANTUM SuperDLT320 tape device, a QUANTUM P3000 tape library system, or a STORAGETEK L180 tape library system. Within the VTL, each virtual cartridge is a file that may grow dynamically as data is stored. This is in contrast to conventional tape cartridges which have a fixed size. One or more virtual cartridges may be stored in a system file as described further below with respect to FIG. 5.
FIG. 5 illustrates one example of a data structure within the file system software 146 that illustrates a system file 200 in accordance with an embodiment of the present invention. In this embodiment, the system file 200 includes a header 202 and data 204. The header 202 may include information that identifies each of the virtual cartridges that are stored in that system file. The header may also contain information such as, whether a virtual cartridge is write protected, the dates of creation/modification of the virtual cartridges, etc. In one example, the header 202 includes information uniquely identifying each virtual cartridge and distinguishing each virtual cartridge from other virtual cartridges stored in the storage system. For example, this information may include a name and an identifying number (corresponding to a barcode that would typically be present on a physical tape so that the tape could be identified by the robotic mechanism) of the virtual cartridge. The header 202 may also contain additional information such as a capacity of each of the virtual cartridges, a date of last modification, etc.
According to one embodiment of the present invention, the size of the header 202 may be optimized to reflect the type of data being stored (e.g., virtual cartridges representing data back-up from one or more host computer systems) and the number of distinct sets of such data (e.g., virtual cartridges) that the system can track. For example, data that is typically backed-up to a tape storage system is typically characterized by larger data sets representing numerous system and user files. Because the data sets are so large, the number of discrete data files to be tracked may be correspondingly small. Accordingly, in one embodiment, the size of the header 202 may be selected based on a compromise between storing too much data to efficiently keep track of (i.e., the header being too big) and not having space to store a sufficient number of cartridge identifiers (i.e., header being too small). In one exemplary embodiment, the header 202 utilizes the first 32 MB of the system file 200. However it is to be appreciated that the header 202 may have a different size based on system needs and characteristics and that, depending on system needs and capacity, one may select a different size for the header 202.
It is to be appreciated that, from the point of view of the back-up/restore application, the virtual cartridges appear as physical tape cartridges with all the same attributes and features. That is, to the back-up restore application, the virtual cartridges appear as sequentially written tapes. However, in one preferred embodiment, the data stored in the virtual cartridges is not stored in a sequential format on back-up storage media 126. Rather, the data that appears to be written to the virtual cartridges is in fact stored in the storage system's files as randomly accessible, disk-format data. Metadata is used to link the stored data to virtual cartridges so that the back-up/restore application can read and write data in cartridge format.
Thus, in broad overview of one preferred embodiment, user and/or system data (referred to herein as “file data”) is received by the storage system 170 from the host computer 120 and is stored on the disk array(s) making up the back-up storage media 126. The software 150 (see FIG. 4) and/or hardware of the storage system writes this file data to the back-up storage media 126 in the form of system files, as is described in more detail below. Metadata is extracted as the data file is being backed-up by the storage system controller to keep track of attributes of the user and/or system files that are backed-up. For example, such metadata for each file may include the file name, a date of creation or last modification of the file, any encryption information relating to the file, and other information. In addition, metadata may be created by the storage system for each file that links the file to a virtual cartridge. Using such metadata, the software provides to the host computer an emulation of tape cartridges; however the file data is in fact not stored in tape format, but rather in the system files, as discussed below. Storing the data in system files, rather than in sequential cartridge format, may be advantageous in that it allows fast, efficient and random access to individual files without the need to scan through sequential data to find a particular file.
As discussed above, according to one embodiment, file data (i.e., user and/or system data) is stored on the back-up storage media as system files, each system file including a header and data, the data being the actual user and/or system files. The header 202 of each system file 200 includes a tape directory 206 that contains metadata linking the user and/or system files to virtual cartridges. The term “metadata” as used herein refers not to user or system file data, but to data that describes attributes of actual user and/or system data. According to one example, the tape directory may define, down to the byte level, the layout of data on the virtual cartridges.
In one embodiment, the tape directory 206 has a table structure, as illustrated in FIG. 6. The table includes a column 220 for the type of information stored (e.g., data, a file marker (FM), etc.), a column 222 for the size of the disk blocks used in bytes, and a column 224 that counts the number of disk blocks in which the file data is stored. Thus, the tape directory allows the controller to have random (as opposed to sequential) access to any data file stored on back-up storage media 126. For example, referring to FIG. 6, the data file 226 may be quickly located on the virtual tape because the tape directory indicates that the data of file 226 begins one block from the beginning of the system file 200. This one block has no size because it corresponds to a file marker (FM). File markers are not stored in the system file, i.e., file markers correspond to zero data. The tape directory includes file markers because they are used by conventional tapes and the back-up/restore application thus writes file markers along with data files and expects to see file markers when viewing a virtual cartridge. Therefore, file markers are kept track of in the tape directory. However, file markers do not represent any data and are therefore not stored in the data section of the system file. Thus, the data of file 226 begins at the beginning of the data section of the system file, indicated by arrow 205 (see FIG. 5), and is 1024 bytes in length (i.e., one disk block that is 1024 bytes in size). It should be appreciated that other file data may be stored in a block size other than 1024 bytes, depending on the amount of data, i.e., the size of the data file. For example, larger data files may be stored using larger data block sizes for efficiency.
In one example, the tape directory may be contained in a “file descriptor” that is associated with each data file backed-up onto the storage system. The file descriptor contains metadata relating the data files 204 stored on the storage system. In one embodiment, the file descriptor may be implemented in accordance with a standardized format, such as the tape archive (tar) format used by most UNIX based systems. Each file descriptor may include information such as the name of the corresponding user file, the date the user file was created/modified, the size of the user file, any access restrictions on the user file, etc. Additional information stored in the file descriptor may further include information describing the directory structure from which the data was copied. Thus, the file descriptor may contain searchable metadata about a corresponding data file, as is discussed in more detail below.
From the point of view of the back-up/restore application, any virtual cartridge may contain a plurality of data files and corresponding file descriptors. From the point of view of the storage system software, the data files are stored in system files that may be linked to, for example, a particular back-up job. For example, a back-up executed by one host computer at a particular time may generate one system file that may correspond to one or more virtual cartridges. Virtual cartridges may thus be of any size and may grow dynamically as more user files are stored on the virtual cartridges.
Referring again to FIG. 2, as discussed above, the storage system 170 may include a synthetic full back-up software application 240. In one embodiment, the host computer 120 backs-up data onto the emulated media 134, forming one or more virtual cartridges. In some computing environments, a “full back-up,” i.e., a back-up copy of all data stored on the primary storage system in the network (see FIG. 1), may be accomplished periodically (e.g., weekly). This process is typically very lengthy due to the large amount of data that is to be copied. Therefore, in many computing environments, additional back-ups, termed incremental back-ups, may be performed between consecutive full back-ups, e.g., daily. An incremental back-up is a process whereby only data that has changed since the last back-up was executed (whether incremental or full) is backed-up. Typically, this changed data is backed-up on a file basis, even though frequently much of the data in the file has not changed. Thus, incremental back-ups are typically much smaller, and therefore much faster to accomplish, than are full back-ups. It is to be appreciated that although many environments typically execute full back-ups once a week and incremental back-ups daily during the week, there is no requirement that such time frames are used. For example, certain environments may require incremental back-ups several times a day. The principles of the invention apply to any environment using full back-ups (and optionally incremental back-ups); regardless of how often they are executed. Frequent execution of full and/or incremental back-ups may result in a large amount of redundant data being stored on the storage system 170. To alleviate the burden associated with this redundant data, the storage system 170 may harness the data de-duplication systems and processes discussed further below.
During a full back-up procedure, the host computer may create one or more virtual cartridges containing the back-up data that comprises a plurality of data files. For clarity, the following discussion will assume that the full back-up generates only one virtual cartridge. However, it is to be appreciated that a full back-up may generate more than one virtual cartridge, and that the principles of the invention apply to any number of virtual cartridges.
According to one embodiment, there is provided a method for creating a synthetic full back-up data set from one existing full back-up data set and one or more incremental back-up data sets. This method may obviate the need to perform periodic (e.g., weekly) full back-ups, thereby saving the user considerable time and network resources. Furthermore, as known to those of skill in the art, restoring data based on a full back-up and one or more incremental back-ups can be a time consuming process because, for example, if the most recent version of a file exists in an incremental back-up, the back-up/restore application will typically restore the file based on the last full back-up and then apply any changes from the incremental back-ups. Providing a synthetic full back-up, therefore, may have an additional advantage of allowing the back-up restore application to more quickly restore data files based on the synthetic full back-up alone, without the need to perform multiple restores from a full back-up and one or more incremental back-ups. It is to be appreciated that the phrase “most recent version” as used herein refers generally to the most recent copy of a data file (i.e., the most recent time that the data file was saved), whether or not the file has a new version number. The term “version” is used generally herein to refer to copies of the same file which may be modified in some way or may have been saved multiple times.
Referring to FIG. 7, there is illustrated a schematic representation of a synthetic full back-up procedure. The host computer 120 may execute a full back-up 230 at a first moment in time, for example, on a weekend. The host computer 120 may then execute subsequent incremental back-ups 232a, 232b, 232c, 232d, 232e, for example, on each day during the week. The storage system 170 may then create a synthetic full back-up data set 234, as discussed below.
According to one embodiment, the storage system 170 may include a software application referred to herein as a synthetic full back-up application 240 (see FIG. 3). The synthetic full back-up application 240 may be run on the storage system controller 122 (see FIG. 2) or may be run on the host computer 120. The synthetic full back-up application includes software commands and interfaces necessary for creating the synthetic full back-up data set 234. In one example, the synthetic full back-up application may perform a logical merge of metadata representations of each of the full back-up data set 230 and the incremental back-up data sets 232 to generate a new virtual cartridge that contains the synthetic full back-up data set 234.
For example, referring to FIG. 8, the existing full back-up data set may include user files F1, F2, F3 and F4. A first incremental back-up data set 232a may include user files F2′, a modified version of F2, and F3′, a modified version of F3. A second incremental back-up data set 232b may include user files F1′, a modified version of F1, and F2′′, a further modified version of F2, and a new user file F5. Therefore, the synthetic full back-up data set 234 formed from a logical merge of the full back-up data set 230 and the two incremental data sets 232a and 232b, contains the latest version of each of user files F1, F2, F3, F4 and F5. As seen in FIG. 8, the synthetic full back-up data set therefore contains user files F1′, F2′′, F3′, F4 and F5.
Referring again to FIGS. 3 and 4, the file system software 146 may create a logical metadata cache 242 that stores metadata relating to each user file stored on the emulated media 134. It is to be appreciated that the logical metadata cache is not required to be a physical data cache, but may instead be a searchable collection of data stored on the storage media 126. In another example, the logical metadata cache 242 can be implemented as a database. Where the metadata is stored in a database, conventional database commands (e.g., SQL commands) can be used to perform the logical merge of the full back-up data set and the one or more incremental back-up data sets to create the synthetic full back-up data set.
In another embodiment, a portion of the metadata may be stored in a database, and another portion may be stored in storage system files. For example, back-up data set metadata, including back-up data set name and data objects it comprises, may be included in the conventional database, while metadata specific to the data objects, such as, for example in the case where the data object is a data file, data file size, security information and location in primary storage may be included in storage system files. Storing metadata in this fashion enables flexible retrieval of frequently queried data from a conventional database and promotes system scalability by enabling faster storage of less frequently queried data in storage system files.
As discussed above, each data file stored on the emulated media 134 may include a file descriptor that contains metadata relating to the data file, including a location of the file on the back-up storage media 126. In one embodiment, the back-up/restore application running on the host computer 120 stores data in a streaming tape format on the emulated media 134. An example of a data structure 250 representing this tape format is illustrated in FIG. 9. As discussed above, the system file data structure includes headers which may contain information about the data file(s), such as the file descriptor for the data files, the dates of creation and/or modification of the files, security information, the directory structure of the host system from whence the file(s) came, as well as other information linking the files to a virtual cartridge. These headers are associated with the data 254 which is actual user and system files that have been backed-up (copied) from the host computer, the primary storage system, etc. The system file data structure may also optionally include pads 256 which may appropriately align the next header to a block boundary.
As shown in FIG. 9, in one example, the header data is located in the logical metadata cache 242 to permit rapid searching and random access to the otherwise sequential tape data format. The use of the logical metadata cache, implemented using the file system software 146 on the storage system controller 122, allows translation of the linear, sequential tape data format, stored on the emulated media 134, into the random-access data format stored on physical disks making up the back-up storage media 126. The logical metadata cache 242 stores the headers 252 which include the file descriptors for the data files, security information which may be used to control access to the data files, as is discussed in more detail below, and pointers 257 to the actual locations of the data files on the virtual cartridges and the back-up storage media 126. In one embodiment, the logical metadata cache stores data relating to all the data files backed-up in the full back-up data set 230 and each of the incremental data sets 232.
According to one embodiment, the synthetic full back-up application software 240 uses the information stored in the logical metadata cache to create a synthetic full back-up data set. This synthetic full back-up data set is then linked to a synthetic virtual cartridge, created by the synthetic full back-up application 240. To the back-up/restore application, the synthetic full back-up data set appears to be stored on this synthetic virtual cartridge. As discussed above, the synthetic full back-up data set may be created by performing a logical merge of the existing full back-up data set and the incremental back-up data sets. This logical merge may include comparing each of the data files included in each of the existing full back-up data set and the incremental back-up data sets and creating a composite of the latest-modified version of each user file, as discussed above in reference to FIG. 8.
According to one embodiment, the synthetic virtual cartridge 260 includes pointers that point to locations of data files on other virtual cartridges, specifically, the virtual cartridges that contain the existing full back-up data set and the incremental back-up data sets, as shown in FIG. 10. Considering the example given with respect to FIG. 8 above, the synthetic virtual cartridge 260 includes pointers 266 that point (indicated by arrows 268) to the locations in the existing full back-up data set, on virtual cartridge 262, of user file F4 (because the existing full back-up data set contained the latest version of F4) and to the location of, for example, user file F3′ in incremental data set 232a on virtual cartridge 264.
The synthetic virtual cartridge also includes a list 270 that contains the identifying numbers (and optionally the names) of all the virtual cartridges that contain data to which the pointers 266 point. This dependent cartridge list 270 may be important for reference, such as keeping track of where the actual data is stored, and for preventing the dependent virtual cartridges from being erased. In this embodiment, the synthetic full back-up data set does not contain any actual user files, but rather a set of pointers that indicate the locations of the user files on the back-up storage media 126. Therefore, it may be desirable to prevent the actual user files (stored on other virtual cartridges) from being deleted. This may be accomplished in part by keeping a record (dependent cartridge list 270) of the virtual cartridges that contain the data and protecting each of those virtual cartridges from being over-written or deleted. The synthetic virtual cartridge may also include cartridge data 272 such as, the size of the synthetic virtual cartridge, its location on the back-up storage media 126, etc. In addition, the synthetic virtual cartridge may have an identifying number and/or name 274.
According to another embodiment, the synthetic virtual cartridge may include a combination of pointers and actual stored user files. Referring to FIG. 11, in one example, the synthetic virtual cartridge includes pointers 266 that point to locations of data files (the latest versions, as discussed above in reference to FIG. 9) in the existing full back-up data set 230 on virtual cartridge 262. The synthetic virtual cartridge may also include data 278 containing actual data files copied from the incremental data sets 232, as indicated by arrows 280. In this manner, the incremental back-up data sets can be deleted after the synthetic full back-up data set 276 has been created, thereby saving storage space. The synthetic virtual cartridges are relatively small as they contain all or partly pointers rather than copies of all the user files.
It is to be appreciated that synthetic full back-ups may include any combination of pointers and stored file data and are not limited to the examples given above. For example, synthetic full back-ups may include pointers to data files for some files stored on certain incremental and/or full back-ups and may include stored file data copied from other existing full and/or incremental back-ups. Alternatively still, a synthetic full back-up may be created based upon a prior full back-up and any relevant incremental back-ups that does not include any pointers, but rather includes the latest version of actual file data copied from the appropriate full and/or incremental back-ups.
In one embodiment, the synthetic full back-up application software may include a differencing algorithm that enables it to compare the user and system file metadata for each of the existing full back-up data set and the incremental back-up data sets to determine where the latest version of each of the data files is located. For example, a differencing algorithm could be used to compare the dates of creation and/or modification, the version number (if applicable), etc. between different versions of the same data files in the different back-up sets to select the most recent version of the data file. However, users may often open a user file and save the file (thereby changing its data of modification) without actually changing any of the data inside the file. Therefore, the system may implement a more advanced differencing algorithm that may analyze the data inside the system or user files to determine whether the data has in fact changed. Variations of such differencing algorithms and other types of compare algorithms may be known to those skilled in the art. In addition, as discussed above, where the metadata is stored in a database format, database commands such as SQL commands can also be used to perform the logical merge. The invention may apply any of such algorithms to ensure that the most recent or latest version of each user file may be selected from all compared existing back-up sets so as to properly create the synthetic full back-up data set.
As should be appreciated by those skilled in the art, the synthetic full back-up application enables full back-up data sets to be created and made available without requiring the host computer to execute a physical full back-up. Not only does this avoid burdening the host computer with the processor overhead of transferring the data to the back-up storage system, but in embodiments where the synthetic full back-up application is executed on the storage system, it significantly reduces the utilization of network bandwidth. As illustrated in FIG. 7, further synthetic full back-up data sets may be created using a first synthetic full back-up data set 234 and subsequent incremental back-up data sets 236. This may provide a significant time advantage in that files or objects that are not frequently modified may not be frequently copied. Instead, the synthetic full back-up data sets may maintain pointers to these files that have just been copied once.
Some aspects in accord with the present invention are directed toward a scalable de-duplication system that removes redundant data from data objects. For example, according to some embodiments, a de-duplication system is configured to manage data de-duplication using pre-processed metadata included in the data. More specifically, embodiments may direct data to de-duplication domains based on the presence or absence of specific metadata values within the data to be de-duplicated. Each of these de-duplication domains may employ specific de-duplication techniques that are tailored to efficiently de-duplicate particular types of data.
For example, FIG. 14 presents a block diagram of a de-duplication director 1400 that is specially configured to provide scalable de-duplication services. The de-duplication director 1400 may be implemented as software, hardware or a combination thereof on a variety of computer systems. For example, according to one embodiment, the de-duplication director 1400 is implemented as a part of the storage system controller 122 discussed above with regard to FIG. 3. The particular configuration of de-duplication director 1400 depicted in FIG. 14 is used for illustration purposes only and is not intended to be limiting, as embodiments of the invention may be architected in a variety of configurations without departing from the scope of the invention. While some of the examples discussed herein focus on embodiments with a single de-duplication director 1400, other embodiments may include two or more de-duplication directors without departing from the scope of the invention.
Referring to FIG. 14, the de-duplication director 1400 includes a data interface 1402, a directing engine 1404, a de-duplication domain database 1406, de-duplication domains 1408, 1410 and 1412 and a de-duplication database interface 1414. In the example shown, the data interface 1402 includes facilities, e.g. executable code, data, data structures or objects, configured to exchange, e.g. provide and receive, information with one or more data sources. Also, in the illustrated example, the data interface 1402 can bi-directionally communicate with the directing engine 1404.
As shown, the directing engine 1404 can exchange a variety of information with the data interface 1402, the de-duplication domain database 1406 and de-duplication domains 1408, 1410 and 1412. The de-duplication domain database 1406, in turn, may communicate data with both the directing engine 1404 and the de-duplication database interface 1414. The de-duplication database interface 1414 includes facilities configured to exchange information with a variety of external entities. These external entities may include, among others, users and/or systems. In the example shown, the de-duplication database interface 1414 can also exchange information with the de-duplication domain database 1406. Each of the de-duplication domains 1408, 1410 and 1412 includes facilities configured to exchange information with both the directing engine 1404 and various external entities. For example, in one embodiment, the de-duplication domains 1408, 1410 and 1412 can exchange information with data storage media, such as the back-up storage media 126 discussed with regard to FIG. 3.
Information may flow between the elements, components and subsystems described herein using any technique. Such techniques include, for example, passing the information over the network using standard protocols, such as TCP/IP, passing the information between modules in memory and passing the information by writing to a file, database, or some other non-volatile storage device. In addition, pointers or other references to information may be transmitted and received in place of, or in addition to, copies of the information. Conversely, the information may be exchanged in place of, or in addition to, pointers or other references to the information. Other techniques and protocols for communicating information may be used without departing from the scope of the invention.
In the example shown in FIG. 14, the de-duplication domain database 1406 includes facilities configured to store and retrieve information describing attributes of one or more de-duplication domains. Examples of this information may include, for each de-duplication domain, the amount of computing resources belonging to, or to be allocated to, the de-duplication domain, a particular de-duplication method to be used by the de-duplication domain, and one or more data object characteristics that are associated with the de-duplication domain. The de-duplication domain database 1406 may also hold artifacts associated with the de-duplication method used by the de-duplication domain, e.g. hash tables.
The de-duplication domain database 1406 may take the form of any logical construction capable of storing information on a computer readable medium including flat files, indexed files, hierarchical databases, relational databases or object oriented databases. The data may be modeled using unique and foreign key relationships and indexes. The unique and foreign key relationships and indexes may be established between the various fields and tables to ensure both data integrity and data interchange performance.
In the illustrated example, the data interface 1402 includes facilities configured to exchange information, in a variety of forms and formats, with various data sources. These data sources may include any provider of information that will be subject to de-duplication processing, such as primary storage devices 106 discussed above with regard to FIG. 1. The data interface 1402 can receive, among other data formats, discrete blocks of data, continuous streams of data and data streams multiplexed from a multiple storage locations. In addition, the data interface 1402 can receive data in-line, i.e. while a data storage system that includes the data interface 1402 is receiving data to be de-duplicated and stored, or off-line, i.e. after the data storage device has already stored the data to be de-duplicated.
In the illustrated example, the de-duplication domains 1408, 1410 and 1412 each include one or more individual de-duplication domains. A de-duplication domain may include software and/or hardware with facilities configured to perform de-duplication processing on data objects. Each de-duplication domain may include dedicate data storage. In the example shown, each de-duplication domain can be associated with one or more characteristics common to several data objects. In addition, in this example, each de-duplication domain can employ a particular de-duplication method. These traits allow individual de-duplication domains to provide a highly effective de-duplication environment for related data objects.
For example, according to one embodiment, the de-duplication domains 1408, 1410 and 1412 each employ a content aware de-duplication process, such as process 1200 discussed below. While in other embodiments, the de-duplication domain 1408 may utilize a hash fingerprinting process, the de-duplication domain 1410 may use a pattern recognition process and 1412 may employ process 1200. Thus, embodiments are not limited to a particular de-duplication method or arrangement of de-duplication methods.
In various embodiments, the directing engine 1404 includes facilities configured to direct data objects to de-duplication domains that are associated with one or more characteristics of the data objects. According to one embodiment, these characteristics include metadata associated with the data objects. In the illustrated embodiment, the directing engine 1404 can receive data objects from the data interface 1402. The directing engine 1404 can select which of de-duplication domains 1408, 1410 and 1412 is suitable to de-duplicate the received data objects. As shown, the directing engine 1404 can also direct the data object to the selected de-duplication domain. The directing engine 1404 also has facilities configured to evaluate the results of the de-duplication activities that are conducted by the de-duplication domains 1408, 1410 and 1412 and, based on this evaluation, the directing engine and consolidate redundant data that spans several de-duplication domains into a single de-duplication domain, thereby conserving additional computing resources.
In various embodiments, the directing engine 1404 includes facilities configured to receive data from the data interface 1402 in a variety of forms and formats, including discrete data blocks, data streams and multiplexed data streams. In these embodiments, the directing engine 1404 can extract preprocessed metadata from the received data. This metadata may include the types of information discussed above with regard to the logical metadata cache, and thus, in some embodiments, may include, among other metadata, back-up policy names, data source types, data source names, back-up application names, operating system types, data types, back-up types, filenames, directory structure and chronological information such as dates and times.
Furthermore, in some embodiments, the directing engine 1404 has facilities configured to identify alignment points within a data stream or multiplexed data stream based on the extracted metadata. In these embodiments, the directing engine 1404 can segment the data stream or multiplexed data stream along these alignment points to create data objects. Also, in some embodiments, the directing engine 1404 can associate metadata with data objects. This associated metadata may include, among other metadata, the metadata used to create the data objects.
For example, according to one embodiment, the directing engine 1404 can align data streams into data objects based on the data objects being subsequent back-ups of a particular server. Similarly, in another embodiment, the directing engine 1404 can align data objects including files with the same file name and directory location. In further embodiments, the directing engine 1404 can create data objects and associate metadata based on a policy that was executed by a back-up/restore program to create the data objects or based on what type of data, for example data created by an Oracle database, is included in the data objects.
According to one embodiment, the directing engine 1404 has facilities configured to direct data objects by evaluating the metadata associated with the data objects. In this embodiment, the directing engine 1404 can compare the metadata associated with a data object to data object characteristics that are associated with individual de-duplication domains. When a match of a sufficient quality is found, the directing engine 1404 can forward the data object to the matching de-duplication domain for further processing. According to one embodiment, the directing engine 1404 can forward the data object by either providing a copy of the data object to the de-duplication domain or by providing a reference to the data object, such as a pointer, to the de-duplication domain. According to some embodiments, both the metadata associated with the data objects and the data object characteristics associated with the de-duplication domains are information regarding the content of the data object.
For example, in one embodiment, the metadata associated with the data objects and the data object characteristics associated with the de-duplication domains is a software application that created the data objects, e.g. MICROSOFT OUTLOOK. In this example, when encountering data objects created by MICROSOFT OUTLOOK, the directing engine 1404 can direct those data objects to a de-duplication domain associated with MICROSOFT OUTLOOK data objects. In other embodiments, the metadata and data object characteristics may be other types of information.
According to several embodiments, the directing engine 1404 includes facilities configured to further consolidate redundant data across de-duplication domains. In some embodiments, the directing engine can evaluate the results of, and artifacts associated with, de-duplication processing to determine redundant data that spans de-duplication domains. For example, in one embodiment, the directing engine 1404 can periodically “scrub” or search hash tables associated with de-duplication domains that employ hash fingerprinting for any hash fingerprints that the de-duplication domains may have in common. In this embodiment, the directing engine 1404 can consolidate storage of data processed by different de-duplication domains, but having these common fingerprints, by directing one or more of the de-duplication domains to replace copies of the redundant data with references to a single copy of the redundant data.
In other embodiments, the directing engine 1404 can create a new de-duplication domain, or modify the configuration of an existing de-duplication domain, to consolidate future processing of data related to the redundant data found by the scrubbing process discussed above. For example, in one embodiment the directing engine 1404 can shift future processing of data objects including data related to the redundant data from one de-duplication domain to another by changing the data object characteristics associated with particular de-duplication domains.
For example, in one embodiment, the directing engine 1404 includes facilities configured to find metadata that is common to the data objects including the redundant data found through scrubbing. Further, in this example, the directing engine can determine, based on the common metadata, one or more data object characteristics that correspond with the common metadata. The directing engine 1404 can also associate these newly determined data object characteristics with a new or existing de-duplication domain, i.e. the de-duplication domain under which future processing will be consolidated, by storing the association in the de-duplication domain database 1406. Conversely, the directing engine 1404 can interact with the de-duplication domain database 1406 to disassociate one or more data object characteristics from existing de-duplication domains to prevent these de-duplication domains from receiving the data objects including data related to the redundant data in the future. In this way, the directing engine 1404 can adjust the flow of data objects associated with the newly found common metadata to de-duplication domains associated with the newly determined data object characteristics.
In some embodiments, the directing engine 1404 includes facilities configured to use additional information when directing data objects to a particular de-duplication domain. For example, according to one embodiment, the directing engine 1404 can detect that storage dedicated to a particular de-duplication domain has less than a threshold level of remaining capacity. In this case, the directing engine 1404 can direct data objects to other de-duplication domains or can allocate additional storage capacity to the de-duplication domain. In another embodiment, the directing engine 1404 can direct a data object to a particular de-duplication domain based on the amount of time remaining until the data object expires. For example, in this embodiment, the directing engine 1404 can direct a data object with little remaining life to a de-duplication domain with little processing overhead, regardless of the efficacy of the de-duplication domain with regard to the data object as the data object will be erased from storage within a short period of time.
According to various embodiments, the de-duplication database interface 1414 has facilities configured to exchange information with a variety of external entities. According to the illustrated embodiment, the de-duplication database interface 1414 can provide a user with a variety of user interface metaphors that enable the user to create, modify and delete de-duplication domains such as the de-duplication domains 1408, 1410 and 1412. More specifically, when displaying a metaphor for creating a new de-duplication domain, the de-duplication database interface 1414 can present a user with interface elements that allow the user to specify the characteristics of data objects that are associated with the new de-duplication domain. Additionally, the de-duplication database interface 1414 can provide the user with interface elements that enable the user to specify the de-duplication method to be employed by the new de-duplication domain.
In other embodiments, the de-duplication database interface 1414 has facilities configured to receive data from an external system, such as a back-up/restore program, and to automatically configure, based on the received data, de-duplication domains to process data coming from the external system. For example, in several embodiments, the de-duplication database interface 1414 can determine commonalities in the types of data objects that will be received, or that are being received, and configure the de-duplication domains 1408, 1410 and 1412 to increase de-duplication efficiency. In one embodiment, the de-duplication database interface 1414 can determine, based on a back-up policy supplied by a back-up/restore program, the primary storage location of data objects that will be received as a result of execution of the back-up policy. In this embodiment, the de-duplication database interface 1414 can store a configuration of de-duplication domains 1408, 1410 and 1412, based on this primary storage location information. In another embodiment, the configuration stored by the de-duplication database interface 1414 can be based on the software applications that created the data objects, rather than their storage locations. Other embodiments may use other types of data to determine suitable de-duplication domain structures and configurations.
As discussed above, the de-duplication director 1400 may use one of several de-duplication methods to remove redundant data from data objects. One particular de-duplication technique that may be used by a de-duplication domain is content aware de-duplication. FIG. 12 illustrates an example content aware process 1200 for de-duplicating data from a data object according to one embodiment of the present invention. FIG. 13 illustrates advanced referencing techniques that yield additional processing efficiencies when used in conjunction with data de-duplication. De-duplication processes may be implemented using a single back-up storage system or within a distributed storage system environment, such as a grid environment as discussed above.
In general, a system conducting the process 1200 may cull through metadata associated with a series of data objects to identify those data objects that will be subject to further de-duplication process steps, such as, for example, data objects that are likely to share duplicate data. The system may inspect the data objects identified for additional processing to locate any redundant data. Further, the system may construct copies of the identified data objects that point to a single copy of the redundant data and, optionally, validate the integrity of these copies. To reclaim storage capacity occupied by redundant data, the system may delete the originally identified data objects. Aspects and embodiments of de-duplication methods and apparatus are discussed in more detail below.
Still referring to FIG. 12, at step 1202, the data de-duplication process 1200 begins. At step 1204, a system identifies data objects that will be subject to further de-duplication processing. In one embodiment, the system may identify data objects that are likely to contain redundant data. Various methods and metadata may be employed to make this identification. For example, in one embodiment the physical location of a back-up data object in primary storage may indicate that it is likely to have data with another back-up data object. More particularly, if two back-up data objects originated from the same primary storage device, e.g. a particular server, then the data objects may be identified as likely including copies of redundant data. Similarly, in another embodiment, two data objects may be identified as likely to have redundant data if both were created by a particular software application. In still another embodiment, whether data objects were stored as part of a full or incremental back-up policy may indicate a likelihood of redundant data. Identification of data objects that are likely to contain duplicate data increases the overall efficiency of the process 1200 by enabling scarce computer resources, such as CPU cycles, to be focused on those data objects that will most benefit from removal of redundant data.
In another embodiment, a system may be configured to automatically include certain data objects in, or exclude certain data objects from, further de-duplication processing based on metadata associated with these data objects. For instance, a system may be configured to include data objects created by a particular software application in de-duplication processing. Likewise, a system may be configured to include data objects backed-up as part of a particular policy in further de-duplication processing. Conversely, the system may be configured to exclude all data objects backed-up by a particular policy and/or specifically name data objects from further de-duplication processing. These configuration options enable system behavior to be tailored to suit the particular needs of any client environment, thus promoting system efficiency, performance and scalability.
At step 1206, the system conducting the process 1200 locates redundant data in the data objects that were identified for further de-duplication processing. This analysis may be accomplished by using metadata and/or by inspecting the actual contents of the identified data objects. In one embodiment, data objects with similar metadata are assumed to comprise the same data. For instance, if the data objects are data files and both share the same name, physical location in primary storage and cyclic redundancy check (CRC), hash or some other metadata generated during de-duplication processing, then the two data objects may be recorded as being redundant. Using metadata to identify redundant data provides several advantages. Using metadata promotes efficiency because only the metadata of the data objects rather than the entirety of the data objects may be processed.
In another embodiment, data objects may be compared on a bit by bit basis to guarantee redundancy before being so recorded. While this type of comparison may be computing resource intensive, it also provides strong assurance that any data identified as redundant is, in fact, completely redundant. This approach to determining redundancy may be useful, for example, when handling data objects whose integrity is particularly important, such as financial information.
In still another embodiment, some portion of the data included in the data object is analyzed to establish redundancy of the entire object. For example, certain software applications may relegate modified data to certain locations within data objects that they modify, e.g. at the beginning or the end of the object. Thus, using this data distribution pattern, the system may focus its de-duplication processing on those portions of the data object that are more likely to be static, thus increase system efficiency.
Embodiments of the present invention may employ a combination of these techniques to locate redundant data. More specifically, a system may direct particular techniques to particular data objects based on metadata such as that used to identify the data objects for further de-duplication processing above. This metadata may include, among others, location in primary storage, policy that caused the data object to be backed-up and software application associated with the data objects. As with data object identification, the ability to tune the system with respect to manner of locating duplicate data promotes system scalability and performance.
At step 1208, a system executing the process 1200 may create de-duplicated copies of previously identified data objects that include redundant data. These de-duplicated copies may include little or no redundant data. In one embodiment, the identified data objects may include, for example, virtual cartridges. In this instance, the system may create one or more de-duplicated virtual cartridges that, when fully resolved, include all of the data included in the identified virtual cartridges. As with the synthetic virtual cartridges discussed above, these de-duplicated virtual cartridges may comprise both data objects and pointers to data objects.
During the creation of these de-duplicated data copies, the system may store copies of duplicated data within a particular data object and create and/or modify pointers within other data objects to store the duplicated data within those data objects. The system may follow various methodologies when storing the duplicated data and the pointers. In one embodiment, the duplicated data is housed in the oldest data object, and pointers identifying the location of the duplicated data are stored in younger data objects including the duplicated data. This technique, referred to in the art as backward referencing, is common where hashing indexes are built to summarize data objects for de-duplication processing.
In another embodiment, the duplicated data is housed in the youngest data object, and pointers identifying the location of the duplicated data are stored in older data objects including the duplicated data. This technique may be termed forward referencing. Forward referencing increases data restoration performance where data is restored from the last back-up because reduced dereferencing of pointers is required to resolve all the data contained in the back-up data object. This increased performance is particularly beneficial due to the fact that the most recent, i.e. youngest, back-up is usually used when data must be restored to primary storage.
FIGS. 13A, 13B and 13C illustrate both forward and backward referencing as described above. FIG. 13A shows the back-up data objects 1302 and 1304 prior to de-duplication processing. For purposes of this illustration, please assume the back-up data object 1302 was stored prior to the back-up data object 1304. The back-up data object 1302 includes a unique data portion 1306 and a redundant data portion 1310A. The back-up data object 1304 includes a unique data portion 1308 and a redundant data portion 1310B.
FIG. 13B illustrates de-duplicated copies of the data objects 1302 and 1304 under a forward referencing scheme. The data object 1304, which is the more recently stored of the two, includes a copy of the redundant data portion 1310B. The data object 1302, which is the less recently stored of the two, includes a pointer 1312 which points to the redundant data portion 1310B. Thus, after the de-duplicated copies are created, the younger data object includes a copy of the redundant data, and the older data object includes a pointer to the redundant data in the younger data object.
FIG. 13C illustrates de-duplicated copies of the data objects 1302 and 1304 under a backward referencing scheme. The data object 1302, which is the less recently stored of the two, includes a copy of the redundant data 1310A. The data object 1302, which is the more recently stored of the two, includes a pointer 1312 which points to the redundant data portion 1310A. Thus, after the de-duplicated copies are created, the older data object includes a copy of the redundant data, and the younger data object includes a pointer to the redundant data in the older data object.
At step 1210, the system may compare the de-duplicated copies against the previously identified data objects to ensure data integrity has been preserved. This comparison may require dereferencing of data object pointers and may include a bit by bit comparison of the data included in the data objects. After this integrity check is performed, in one embodiment, the system may swap the pointers that identify the de-duplicated copies and their respective previously identified data objects so that the de-duplicated data object becomes the primary data object and the previously identified data object may be deleted without disrupting the integrity of any data objects that reference it. The system may also make other adjustments to metadata to ensure it accurately reflects the characteristics of the de-duplicated copy.
At step 1212, the storage capacity utilized by the previously identified data objects is reclaimed for use by other data objects. In one embodiment, this may be accomplished by simply deleting the previously identified data objects. At step 1214, process 1200 ends.
The process 1200 depicts a preferable sequence of events. Other actions can be added, or the order of actions can be altered in the process 1200 without departing from the spirit of the present invention. In one embodiment, the process 1200 may be executed for each data object included in a back-up storage system. In another embodiment, a system may execute the process 1200 for a subset of the data objects in the back-up storage system.
The process 1200 may be executed on demand or scheduled as a one-time or reoccurring process. Further subsets of the process 1200 may be executed when the space reclaimed by de-duplication will meet or exceed a certain threshold. For example, in one embodiment the process 1200 may execute only when de-duplication will free at least a specified number (e.g., 50) terabytes or a specified percentage (e.g., 25%) the utilized back-up storage capacity. When implemented as event driven computing actions, the acts that comprise process 1200 may be executed in a distributed computing environment, such as a grid environment.
Thus, in summary, embodiments of the de-duplication process 1200 may decrease the storage capacity required to maintain copies of back-up data and thus, decrease the amount of electronic media required to store back-up data. Further, embodiments of the de-duplication process 1200 may make efficient use of computing resources by using metadata to optimize de-duplication processing. Finally, by storing de-duplicated data in a forward referencing scheme, de-duplication can enhance the performance of commonly used data restoration functionality.
Various embodiments include processes for a computer system to provide scalable de-duplication services. FIG. 15 illustrates an example of one such process 1500 that includes acts of receiving data, selecting a de-duplication domain to process the data and directing the data to the selected de-duplication domain. Process 1500 begins at 1502.
In act 1504, a computer system receives data to be de-duplicated. As discussed above, according to one embodiment, the data may take a variety of forms including a block of data, a data stream and a multiplexed data stream. In the example shown in FIG. 14, the data is received by the data interface 1402 and provided to the directing engine 1404 for further processing. According to this example, the directing engine 1404 receives the data and segments the data into one or more data objects based on pre-processed metadata included in the data stream. Further, in this example, the directing engine 1404 associates metadata with the data object that it creates.
In act 1506, a computer system selects a de-duplication domain to process the received data. According to the example shown in FIG. 14, the directing engine 1404 selects one of the de-duplication domains 1408, 1410 and 1412 to process a particular data object by comparing metadata associated with the data object to a data object characteristic associated with the de-duplication domain. In addition, the directing engine 1404 may select, or not select, a particular de-duplication domain based on other information, such as the amount of storage capacity remaining in the particular de-duplication domain.
In act 1508, a computer system directs the received data to the selected de-duplication domain. According to the illustrated example in FIG. 14, the directing engine 1404 may provide a data object to a selected de-duplication domain by passing a reference to the data object, or a copy of the data object, to the de-duplication domain.
Process 1500 ends at 1510.
Process 1500 exemplifies one particular sequence of acts in a particular embodiment. The acts included in each of these processes may be performed by, or using, one or more computer systems specially configured as discussed herein. Additionally, the order of acts can be altered, or other acts can be added, without departing from the scope of the present invention.
As discussed above in reference to FIG. 3, the storage system may also include a software application referred to as the end-user restore application 300. Thus, according to another embodiment, there is provided a method for end users to locate and restore back-up data without IT staff intervention and without requiring any changes to existing back-up/restore procedures and/or policies. In a typical back-up storage system, the back-up/restore application running on the host computer 120 is controlled by IT staff and it may be impossible or very difficult for an end-user to access back-up data without intervention by the IT staff. According to aspects and embodiments of the invention, storage system software is provided that allows end users to locate and restore their files via, for example, a web-based or other interface with the back-up storage media 126.
It is to be appreciated that, as with the synthetic full back-up application 240, the end-user restore application 300 may be run on the storage system controller 122 (see FIG. 2) or may be run on the host computer 120. The end-user restore application includes software commands and interfaces necessary to allow an authorized user to search the logical metadata cache to locate, and optionally restore, back-up files from the back-up storage media 126.
According to one embodiment, there is provided software including a user interface that is installed and/or executed on the user computer 136. The user interface may be any type of interface that allows a user to locate files on the back-up storage media. For example, the user interface may be a graphical user interface, may be web-based, or may be a text interface. The user computer is coupled to the storage system 170 via a network connection 138 which may be, for example, an Ethernet connection. Through this network connection 138, an operator of the user computer 136 can access the data stored on the storage system 170.
In one example, the end-user restore application 300 includes a user authentication and/or authorization feature. For example, a user may be asked to login via the user interface on the user computer using a username and password. The user computer may communicate the username and password to the storage system (e.g., to the end-user restore application) which may use an appropriate user authentication mechanism to determine whether the user has access to the storage system. Some examples of user authentication mechanisms that may be used include, but are not limited to, a MICROSOFT Active Directory server, a UNIX “yellow pages” server or a Lightweight Directory Access Protocol. The login/user authentication mechanism may communicate with the end-user restore application to exchange the user privileges. For example, some users may be allowed to search only those files that have been created by themselves or for which they have certain privileges or are identified as an owner. Other users such as, for example, system operators or administrators may be allowed access to all back-up files, etc.
According to one embodiment, the end-user restore application uses the logical metadata cache to obtain information about all the data files backed-up on the back-up storage media. The end-user restore application presents to the user, via the user interface, a hierarchical directory structure of the user's files sorted by, for example, back-up time/date, username, original user computer directory structure (that may have been obtained when the files were backed-up), or other file characteristics. In one example, the directory structure presented to the user may vary according to the privileges enabled for that user. The end-user restore application may accept browse requests (i.e., through the user interface, the user may browse the directory structure to locate a desired file) or the user may search for a file by name, date, etc.
According to one embodiment, the user may restore back-up files from the storage system. For example, once the user has located a desired file, as described above, the user may download the file from the storage system via the network connection 138. In one example, this download procedure may be implemented in a manner comparable to any web-based download, as known to those skilled in the art.
By allowing end users to access those files for which they have permission to view/download, and by enabling such access through a user interface (e.g., web-based technology), the end-user restore application can enable user to search for and restore their own files without there being any need to alter any back-up policies or procedures.
It should be appreciated that although aspects of the present invention, such as the synthetic full back-up application and the end-user restore application are described herein primarily in terms of software, it should be appreciated that they may alternatively be implemented in software, hardware or firmware, or any combination thereof.
Thus, for example, embodiments of the present invention may comprise any computer-readable medium (e.g., a computer memory, a floppy disk, a compact disk, a tape, etc.) encoded with a computer program (i.e., a plurality of instructions), which, when executed, at least in part, on a processor of a storage system, performs the functions of the synthetic full back-up application and/or the end-user restore application as described in detail above.
In general summary, embodiments and aspects of the invention thus include a storage system and methods that emulate a conventional tape back-up system but may provide enhanced functionality such as being able to create synthetic back-ups and allowing end users to view and restore back-up files. However, it should be appreciated that various aspects of the present invention may be used for other than the back-up of computer data. Because the storage system of the present invention may be used to economically store vast amounts of data, and that stored data can be accessed randomly, as opposed to sequentially, and at hard disk access times, embodiments of the present invention may find use outside of traditional back-up storage systems. For example, embodiments of the present invention may be used to store video or audio data representing a wide selection of movies and music and enable video and/or audio on demand.
Having thus described several aspects of at least one embodiment of this invention, it is to be appreciated various alterations, modifications, and improvements will readily occur to those skilled in the art. Such alterations, modifications, and improvements are intended to be part of this disclosure, and are intended to be within the scope of the invention. Accordingly, the foregoing description and drawings are by way of example only.

## Claims

1. A computerized method for classifying data from a backup application for de-duplication of redundant data based on one or more characteristics of the data, the method comprising:
receiving, by a computing device, a backup data object from a backup application, wherein the backup application created the backup data object, and a data object characteristic of the backup data object is not known to the computing device;
determining the data object characteristic of the backup data object based on metadata associated with the backup data object;
selecting a de-duplication domain from a plurality of de-duplication domains based at least in part on the data object characteristic of the backup data object, wherein each de-duplication domain from the plurality of de-duplication domains is associated with:
a data object characteristic that defines a data object type;
a de-duplication method selected from a plurality of de-duplication methods that is tailored to de-duplicate redundant data among backup data objects of the data object type, wherein backup data objects of the data object type have redundant data because they share the same data object characteristic; and
a data object type that is different than each data object type associated with the remaining de-duplication domains from the plurality of de-duplication domains; and

directing the backup data object to the selected de-duplication domain for de-duplication, wherein the selected de-duplication domain executes the de-duplication method that is associated with the selected de-duplication domain to de-duplicate redundant data among the backup data object, and one or more other backup data objects also directed to the selected de-duplication domain, based on the data object characteristic associated with the selected de-duplication domain.

2. The method according to claim 1, wherein receiving the backup data object comprises:
receiving a data stream; and
identifying the backup data object using metadata included in the data stream.

3. The method according to claim 2, wherein receiving the data stream includes receiving a multiplexed data stream.

4. The method according to claim 2, further comprising extracting metadata included in the data stream with the backup data object.

5. The method according to claim 4, wherein selecting the de-duplication domain from the plurality of de-duplication domains includes comparing the extracted metadata associated with the backup data object to each set of data object characteristics associated with each de-duplication domain.

6. The method according to claim 4, wherein extracting the metadata included in the data stream includes extracting at least one of a back-up policy name, a data source type, a data source name, a back-up application name, an operating system type, a data type, a back-up type, a filename, a directory structure and chronological information.

7. The method according to claim 1, further comprising configuring each of the plurality of de-duplication domains to use one of a plurality of de-duplication methods.

8. The method according to claim 7, wherein configuring each of the plurality of de-duplication domains includes configuring each of the plurality of de-duplication domains to use one de-duplication method selected from the group comprising hash-fingerprinting, pattern recognition and content aware de-duplication.

9. The method according to claim 1, further comprising:
de-duplicating, within the selected de-duplication domain, the backup data object; and
adjusting the data object characteristic associated with at least one of the plurality of de-duplication domains based on a result of the act of de-duplicating.

10. The method according to claim 9, wherein adjusting the data object characteristic includes storing data in a de-duplication domain database.

11. The method according to claim 1, wherein the method is executed in a grid computing environment.

12. The method according to claim 1, wherein the method is executed on a back-up storage system while data is not being backed-up to the back-up storage system.

13. The method according to claim 1, wherein the method is executed on a back-up storage system while data is being backed-up to the back-up storage system.

14. The method of claim 1, wherein directing the backup data object to the selected de-duplication domain for de-duplication comprises providing a reference to the backup data object to the selected de-duplication domain instead of providing a copy of the data object to the de-duplication domain.

15. A computer program product, tangibly embodied in a non-transitory computer readable medium, the computer program product including instructions being configured to cause a data processing apparatus to:
receive a backup data object from a backup application, wherein the backup application created the backup data object, and a data object characteristic of the backup data object is not known to the computing device;
determine the data object characteristic of the backup data object based on metadata associated with the backup data object;
select a de-duplication domain from a plurality of de-duplication domains based at least in part on the data object characteristic of the backup data object, wherein each de-duplication domain from the plurality of de-duplication domains is associated with
a data object characteristic that defines a data object type;
a de-duplication method selected from a plurality of de-duplication methods that is tailored to de-duplicate redundant data among backup data objects of the data object type, wherein backup data objects of the data object type have redundant data because they share the same data object characteristic; and
a data object type that is different than each data object type associated with the remaining de-duplication domains from the plurality of de-duplication domains; and

direct the backup data object to the selected de-duplication domain for de-duplication, wherein the selected de-duplication domain executes the de-duplication method that is associated with the selected de-duplication domain to de-duplicate redundant data among the backup data object, and one or more other backup data objects also directed to the selected de-duplication domain, based on the data object characteristic associated with the selected de-duplication domain.

16. A system for classifying data from a backup application for de-duplication of redundant data based on one or more characteristics of the data, the system comprising:
a plurality of de-duplication domains, wherein each de-duplication domain from the plurality of de-duplication domains is associated with
a data object characteristic that defines a data object type;
a de-duplication method selected from a plurality of de-duplication methods that is tailored to de-duplicate redundant data among backup data objects of the data object type, wherein backup data objects of the data object type have redundant data because they share the same data object characteristic; and
a data object type that is different than each data object type associated with the remaining de-duplication domains from the plurality of de-duplication domains; and

a controller coupled to the plurality of de-duplication domains and configured to:
receive a backup data object from a backup application, wherein the backup application created the backup data object, and a data object characteristic of the backup data object is not known to the computing device;
determine the data object characteristic of the backup data object based on metadata associated with the backup data object;
select a de-duplication domain from a plurality of de-duplication domains based at least in part on the data object characteristic of the backup data object; and
direct the backup data object to the selected de-duplication domain for de-duplication, wherein the selected de-duplication domain executes the de-duplication method that is associated with the selected de-duplication domain to de-duplicate redundant data among the backup data object, and one or more other backup data objects also directed to the selected de-duplication domain, based on the data object characteristic associated with the selected de-duplication domain.

17. The system according to claim 16, wherein the controller is further configured to:
receive a data stream; and
identify the backup data object using metadata included in the data stream.

18. The system according to claim 17, wherein the data stream is multiplexed.

19. The system according to claim 17, wherein the controller is further configured to extract metadata included in the data stream with the backup data object.

20. The system according to claim 19, wherein the controller is further configured to determine that the backup data object has the at least one characteristic associated with the de-duplication domain by comparing the extracted metadata associated with the backup data object to each set of data object characteristics associated with each de-duplication domain.

21. The system according to claim 19, wherein the controller is further configured to extract at least one of a back-up policy name, a data source type, a data source name, a back-up application name, an operating system type, a data type, a back-up type, a filename, a directory structure and chronological information.

22. The system according to claim 16, wherein the controller is further arranged to configure each of the plurality of de-duplication domains to use one of a plurality of de-duplication methods.

23. The system according to claim 22, wherein the controller is further arranged to configure each of the plurality of de-duplication domains to use one de-duplication method selected from the group comprising hash-fingerprinting, pattern recognition and content aware de-duplication.

24. The system according to claim 16, wherein the controller is further configured to associate each of the plurality of de-duplication domains with a set of one or more data object characteristics.

25. The system according to claim 16, wherein the controller is further configured to:
cause, within the selected de-duplication domain, de-duplication of the backup data object; and
adjust the data object characteristic associated with at least one of the plurality of de-duplication domains based on a result of the act of de-duplicating.

26. The system according to claim 25, wherein the controller is further configured to store data in a de-duplication domain database.

27. The system according to claim 16, wherein the system is included in a grid computing environment.

28. The system according to claim 16, wherein the controller is further configured to receive the backup data object, determine that the backup data object has the at least one characteristic associated with a de-duplication domain and direct the backup data object to the de-duplication domain while data is not being backed-up to the system.

29. The system according to claim 16, wherein the controller is further configured to receive the backup data object, determine that the backup data object has the at least one characteristic associated with a de-duplication domain and direct the backup data object to the de-duplication domain while data is being backed-up to the system.