Patent Grant
11847026
Businesses worldwide recognize the commercial value of their data and seek reliable, cost-effective ways to protect the information stored on their computer networks while minimizing impact on productivity. Protecting information is often part of a routine process that is performed within an organization.
A company might back up critical computing systems such as databases, file servers, web servers, and so on as part of a daily, weekly, or monthly maintenance schedule. The company may similarly protect computing systems used by each of its employees, such as those used by an accounting department, marketing department, engineering department, and so forth.
Given the rapidly expanding volume of data under management, companies also continue to seek innovative techniques for managing data growth, in addition to protecting data. For instance, companies often implement migration techniques for moving data to lower cost storage over time and data reduction techniques for reducing redundant data, pruning lower priority data, etc.
Enterprises also increasingly view their stored data as a valuable asset. Along these lines, customers are looking for solutions that not only protect and manage, but also leverage their data. For instance, solutions providing data analysis capabilities, improved data presentation and access features, and the like, are in increasing demand.
Snapshots can provide point-in-time copies of production data that can be restored for reference at a future time. In certain systems, a single logical volume of data (e.g., LUN) may have data stored therein associated with a plurality of different applications/agents. Snapshots are often taken of an entire logical volume even when only one of the associated applications is requesting the snapshot. If a snapshot is taken of the entire volume in order to accommodate a request of one application, or a subset of applications associated with the volume, the snapshot data not associated with the requesting application may be unused, thereby creating system inefficiency.
A data storage system according to certain aspects can share a single snapshot for multiple applications and/or agents. For example, the data storage system can receive snapshot commands from multiple applications and/or agents, and can group them for a single snapshot (e.g., based on time of receipt of the snapshot commands). Data associated with the multiple applications and/or agents may reside on a single LUN or volume. The data storage system can take a single snapshot of the LUN or volume, and generate metadata regarding which portion of the snapshot is related to which application. The single snapshot can be stored in one or more secondary storage devices. In some embodiments, the single snapshot may be partitioned into portions relating to different applications and stored separately.
According to some embodiments, a data storage system configured to generate a snapshot of data relating to a plurality of applications is provided. The system may include computer hardware and a snapshot manager executing on the computer hardware. The snapshot manager may be configured to group a plurality of snapshot requests associated with a plurality of applications based on a respective time of receipt of the plurality of snapshot requests, wherein the plurality of applications are executing on a client computing device and data generated by the plurality of applications is stored in a logical volume in primary storage. The snapshot manager may also be configured to obtain a snapshot of the logical volume storing the data generated by the plurality of applications associated with the grouped snapshot requests. The snapshot manager may be further configured to generate mapping data between a particular one of the plurality of applications and a portion of the snapshot relating to the particular one of the plurality of applications. The snapshot manager can additionally be configured to store the snapshot of the logical volume in secondary storage.
According to certain embodiments, a method of generating a snapshot of data relating to a plurality of applications is provided. The method may include grouping, using computer hardware, a plurality of snapshot requests associated with a plurality of applications based on a respective time of receipt of the plurality of snapshot requests, wherein the plurality of applications are executing on a client computing device and data generated by the plurality of applications is stored in a logical volume in primary storage. The method can also include obtaining a snapshot of the logical volume storing the data generated by the plurality of applications associated with the grouped snapshot requests. The method may further include generating, using computer hardware, mapping data between a particular one of the plurality of applications and a portion of the snapshot relating to the particular one of the plurality of applications. The method can additionally include storing the snapshot of the logical volume in secondary storage.
For purposes of summarizing the disclosure, certain aspects, advantages and novel features of the inventions have been described herein. It is to be understood that not necessarily all such advantages may be achieved in accordance with any particular embodiment of the invention. Thus, the invention may be embodied or carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other advantages as may be taught or suggested herein.
Information Management System Overview
With the increasing importance of protecting and leveraging data, organizations simply cannot afford to take the risk of losing critical data. Moreover, runaway data growth and other modern realities make protecting and managing data an increasingly difficult task. There is therefore a need for efficient, powerful, and user-friendly solutions for protecting and managing data.
Depending on the size of the organization, there are typically many data production sources which are under the purview of tens, hundreds, or even thousands of employees or other individuals. In the past, individual employees were sometimes responsible for managing and protecting their data. A patchwork of hardware and software point solutions have been applied in other cases. These solutions were often provided by different vendors and had limited or no interoperability.
Certain embodiments described herein provide systems and methods capable of addressing these and other shortcomings of prior approaches by implementing unified, organization-wide information management.
The organization which employs the information management system 100 may be a corporation or other business entity, non-profit organization, educational institution, household, governmental agency, or the like.
Generally, the systems and associated components described herein may be compatible with and/or provide some or all of the functionality of the systems and corresponding components described in one or more of the following U.S. patents and patent application publications assigned to CommVault Systems, Inc., each of which is hereby incorporated in its entirety by reference herein:
The illustrated information management system 100 includes one or more client computing device 102 having at least one application 110 executing thereon, and one or more primary storage devices 104 storing primary data 112. The client computing device(s) 102 and the primary storage devices 104 may generally be referred to in some cases as a primary storage subsystem 117.
Depending on the context, the term “information management system” can refer to generally all of the illustrated hardware and software components. Or, in other instances, the term may refer to only a subset of the illustrated components.
For instance, in some cases information management system 100 generally refers to a combination of specialized components used to protect, move, manage, manipulate and/or process data and metadata generated by the client computing devices 102. However, the term may generally not refer to the underlying components that generate and/or store the primary data 112, such as the client computing devices 102 themselves, the applications 110 and operating system residing on the client computing devices 102, and the primary storage devices 104.
As an example, “information management system” may sometimes refer only to one or more of the following components and corresponding data structures: storage managers, data agents, and media agents. These components will be described in further detail below.
Client Computing Devices
There are typically a variety of sources in an organization that produce data to be protected and managed. As just one illustrative example, in a corporate environment such data sources can be employee workstations and company servers such as a mail server, a web server, or the like. In the information management system 100, the data generation sources include the one or more client computing devices 102.
The client computing devices 102 may include, without limitation, one or more: workstations, personal computers, desktop computers, or other types of generally fixed computing systems such as mainframe computers and minicomputers.
The client computing devices 102 can also include mobile or portable computing devices, such as one or more laptops, tablet computers, personal data assistants, mobile phones (such as smartphones), and other mobile or portable computing devices such as embedded computers, set top boxes, vehicle-mounted devices, wearable computers, etc.
In some cases, each client computing device 102 is associated with one or more users and/or corresponding user accounts, of employees or other individuals.
The term “client computing device” is used herein because the information management system 100 generally “serves” the data management and protection needs for the data generated by the client computing devices 102. However, the use of this term does not imply that the client computing devices 102 cannot be “servers” in other respects. For instance, a particular client computing device 102 may act as a server with respect to other devices, such as other client computing devices 102. As just a few examples, the client computing devices 102 can include mail servers, file servers, database servers, and web servers.
The client computing devices 102 may additionally include virtualized and/or cloud computing resources. For instance, one or more virtual machines may be provided to the organization by a third-party cloud service vendor. Or, in some embodiments, the client computing devices 102 include one or more virtual machine(s) running on a virtual machine host computing device operated by the organization. As one example, the organization may use one virtual machine as a database server and another virtual machine as a mail server. A virtual machine manager (VMM) (e.g., a Hypervisor) may manage the virtual machines, and reside and execute on the virtual machine host computing device.
Each client computing device 102 may have one or more applications 110 (e.g., software applications) executing thereon which generate and manipulate the data that is to be protected from loss.
The applications 110 generally facilitate the operations of an organization (or multiple affiliated organizations), and can include, without limitation, mail server applications (e.g., Microsoft Exchange Server), file server applications, mail client applications (e.g., Microsoft Exchange Client), database applications (e.g., SQL, Oracle, SAP, Lotus Notes Database), word processing applications (e.g., Microsoft Word), spreadsheet applications, financial applications, presentation applications, browser applications, mobile applications, entertainment applications, and so on.
The applications 110 can include at least one operating system (e.g., Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-based operating systems, etc.), which may support one or more file systems and host the other applications 110.
As shown, the client computing devices 102 and other components in the information management system 100 can be connected to one another via one or more communication pathways 114. The communication pathways 114 can include one or more networks or other connection types including as any of following, without limitation: the Internet, a wide area network (WAN), a local area network (LAN), a Storage Area Network (SAN), a Fibre Channel connection, a Small Computer System Interface (SCSI) connection, a virtual private network (VPN), a token ring or TCP/IP based network, an intranet network, a point-to-point link, a cellular network, a wireless data transmission system, a two-way cable system, an interactive kiosk network, a satellite network, a broadband network, a baseband network, other appropriate wired, wireless, or partially wired/wireless computer or telecommunications networks, combinations of the same or the like. The communication pathways 114 in some cases may also include application programming interfaces (APIs) including, e.g., cloud service provider APIs, virtual machine management APIs, and hosted service provider APIs.
Primary Data and Exemplary Primary Storage Devices
Primary data 112 according to some embodiments is production data or other “live” data generated by the operating system and other applications 110 residing on a client computing device 102. The primary data 112 is stored on the primary storage device(s) 104 and is organized via a file system supported by the client computing device 102. For instance, the client computing device(s) 102 and corresponding applications 110 may create, access, modify, write, delete, and otherwise use primary data 112.
Primary data 112 is generally in the native format of the source application 110. According to certain aspects, primary data 112 is an initial or first (e.g., created before any other copies or before at least one other copy) stored copy of data generated by the source application 110. Primary data 112 in some cases is created substantially directly from data generated by the corresponding source applications 110.
The primary data 112 may sometimes be referred to as a “primary copy” in the sense that it is a discrete set of data. However, the use of this term does not necessarily imply that the “primary copy” is a copy in the sense that it was copied or otherwise derived from another stored version.
The primary storage devices 104 storing the primary data 112 may be relatively fast and/or expensive (e.g., a disk drive, a hard-disk array, solid state memory, etc.). In addition, primary data 112 may be intended for relatively short term retention (e.g., several hours, days, or weeks).
According to some embodiments, the client computing device 102 can access primary data 112 from the primary storage device 104 by making conventional file system calls via the operating system. Primary data 112 representing files may include structured data (e.g., database files), unstructured data (e.g., documents), and/or semi-structured data. Some specific examples are described below with respect to
It can be useful in performing certain tasks to break the primary data 112 up into units of different granularities. In general, primary data 112 can include files, directories, file system volumes, data blocks, extents, or any other types or granularities of data objects. As used herein, a “data object” can refer to both (1) any file that is currently addressable by a file system or that was previously addressable by the file system (e.g., an archive file) and (2) a subset of such a file.
As will be described in further detail, it can also be useful in performing certain functions of the information management system 100 to access and modify metadata within the primary data 112. Metadata generally includes information about data objects or characteristics associated with the data objects.
Metadata can include, without limitation, one or more of the following: the data owner (e.g., the client or user that generates the data), the last modified time (e.g., the time of the most recent modification of the data object), a data object name (e.g., a file name), a data object size (e.g., a number of bytes of data), information about the content (e.g., an indication as to the existence of a particular search term), to/from information for email (e.g., an email sender, recipient, etc.), creation date, file type (e.g., format or application type), last accessed time, application type (e.g., type of application that generated the data object), location/network (e.g., a current, past or future location of the data object and network pathways to/from the data object), frequency of change (e.g., a period in which the data object is modified), business unit (e.g., a group or department that generates, manages or is otherwise associated with the data object), and aging information (e.g., a schedule, such as a time period, in which the data object is migrated to secondary or long term storage), boot sectors, partition layouts, file location within a file folder directory structure, user permissions, owners, groups, access control lists [ACLs]), system metadata (e.g., registry information), combinations of the same or the like.
In addition to metadata generated by or related to file systems and operating systems, some of the applications 110 maintain indices of metadata for data objects, e.g., metadata associated with individual email messages. Thus, each data object may be associated with corresponding metadata. The use of metadata to perform classification and other functions is described in greater detail below.
Each of the client computing devices 102 are associated with and/or in communication with one or more of the primary storage devices 104 storing corresponding primary data 112. A client computing device 102 may be considered to be “associated with” or “in communication with” a primary storage device 104 if it is capable of one or more of: storing data to the primary storage device 104, retrieving data from the primary storage device 104, and modifying data retrieved from a primary storage device 104.
The primary storage devices 104 can include, without limitation, disk drives, hard-disk arrays, semiconductor memory (e.g., solid state drives), and network attached storage (NAS) devices. In some cases, the primary storage devices 104 form part of a distributed file system. The primary storage devices 104 may have relatively fast I/O times and/or are relatively expensive in comparison to the secondary storage devices 108. For example, the information management system 100 may generally regularly access data and metadata stored on primary storage devices 104, whereas data and metadata stored on the secondary storage devices 108 is accessed relatively less frequently.
In some cases, each primary storage device 104 is dedicated to an associated client computing devices 102. For instance, a primary storage device 104 in one embodiment is a local disk drive of a corresponding client computing device 102. In other cases, one or more primary storage devices 104 can be shared by multiple client computing devices 102. As one example, a primary storage device 104 can be a disk array shared by a group of client computing devices 102, such as one of the following types of disk arrays: EMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV, NetApp FAS, HP EVA, and HP 3PAR.
The information management system 100 may also include hosted services (not shown), which may be hosted in some cases by an entity other than the organization that employs the other components of the information management system 100. For instance, the hosted services may be provided by various online service providers to the organization. Such service providers can provide services including social networking services, hosted email services, or hosted productivity applications or other hosted applications).
Hosted services may include software-as-a-service (SaaS), platform-as-a-service (PaaS), application service providers (ASPs), cloud services, or other mechanisms for delivering functionality via a network. As it provides services to users, each hosted service may generate additional data and metadata under management of the information management system 100, e.g., as primary data 112. In some cases, the hosted services may be accessed using one of the applications 110. As an example, a hosted mail service may be accessed via browser running on a client computing device 102.
Secondary Copies and Exemplary Secondary Storage Devices
The primary data 112 stored on the primary storage devices 104 may be compromised in some cases, such as when an employee deliberately or accidentally deletes or overwrites primary data 112 during their normal course of work. Or the primary storage devices 104 can be damaged or otherwise corrupted.
For recovery and/or regulatory compliance purposes, it is therefore useful to generate copies of the primary data 112. Accordingly, the information management system 100 includes one or more secondary storage computing devices 106 and one or more secondary storage devices 108 configured to create and store one or more secondary copies 116 of the primary data 112 and associated metadata. The secondary storage computing devices 106 and the secondary storage devices 108 may be referred to in some cases as a secondary storage subsystem 118.
Creation of secondary copies 116 can help meet information management goals, such as: restoring data and/or metadata if an original version (e.g., of primary data 112) is lost (e.g., by deletion, corruption, or disaster); allowing point-in-time recovery; complying with regulatory data retention and electronic discovery (e-discovery) requirements; reducing utilized storage capacity; facilitating organization and search of data; improving user access to data files across multiple computing devices and/or hosted services; and implementing data retention policies.
Types of secondary copy operations can include, without limitation, backup operations, archive operations, snapshot operations, replication operations (e.g., continuous data replication [CDR]), data retention policies such as information lifecycle management and hierarchical storage management operations, and the like. These specific types operations are discussed in greater detail below.
Regardless of the type of secondary copy operation, the client computing devices 102 access or receive primary data 112 and communicate the data, e.g., over the communication pathways 114, for storage in the secondary storage device(s) 108.
A secondary copy 116 can comprise a separate stored copy of application data that is derived from one or more earlier created, stored copies (e.g., derived from primary data 112 or another secondary copy 116). Secondary copies 116 can include point-in-time data, and may be intended for relatively long-term retention (e.g., weeks, months or years), before some or all of the data is moved to other storage or is discarded.
In some cases, a secondary copy 116 is a copy of application data created and stored subsequent to at least one other stored instance (e.g., subsequent to corresponding primary data 112 or to another secondary copy 116), in a different storage device than at least one previous stored copy, and/or remotely from at least one previous stored copy. Secondary copies 116 may be stored in relatively slow and/or low cost storage (e.g., magnetic tape). A secondary copy 116 may be stored in a backup or archive format, or in some other format different than the native source application format or other primary data format.
In some cases, secondary copies 116 are indexed so users can browse and restore at another point in time. After creation of a secondary copy 116 representative of certain primary data 112, a pointer or other location indicia (e.g., a stub) may be placed in primary data 112, or be otherwise associated with primary data 112 to indicate the current location on the secondary storage device(s) 108.
Since an instance a data object or metadata in primary data 112 may change over time as it is modified by an application 110 (or hosted service or the operating system), the information management system 100 may create and manage multiple secondary copies 116 of a particular data object or metadata, each representing the state of the data object in primary data 112 at a particular point in time. Moreover, since an instance of a data object in primary data 112 may eventually be deleted from the primary storage device 104 and the file system, the information management system 100 may continue to manage point-in-time representations of that data object, even though the instance in primary data 112 no longer exists.
For virtualized computing devices the operating system and other applications 110 of the client computing device(s) 102 may execute within or under the management of virtualization software (e.g., a VMM), and the primary storage device(s) 104 may comprise a virtual disk created on a physical storage device. The information management system 100 may create secondary copies 116 of the files or other data objects in a virtual disk file and/or secondary copies 116 of the entire virtual disk file itself (e.g., of an entire .vmdk file).
Secondary copies 116 may be distinguished from corresponding primary data 112 in a variety of ways, some of which will now be described. First, as discussed, secondary copies 116 can be stored in a different format (e.g., backup, archive, or other non-native format) than primary data 112. For this or other reasons, secondary copies 116 may not be directly useable by the applications 110 of the client computing device 102, e.g., via standard system calls or otherwise without modification, processing, or other intervention by the information management system 100.
Secondary copies 116 are also often stored on a secondary storage device 108 that is inaccessible to the applications 110 running on the client computing devices 102 (and/or hosted services). Some secondary copies 116 may be “offline copies,” in that they are not readily available (e.g. not mounted to tape or disk). Offline copies can include copies of data that the information management system 100 can access without human intervention (e.g. tapes within an automated tape library, but not yet mounted in a drive), and copies that the information management system 100 can access only with at least some human intervention (e.g. tapes located at an offsite storage site).
The secondary storage devices 108 can include any suitable type of storage device such as, without limitation, one or more tape libraries, disk drives or other magnetic, non-tape storage devices, optical media storage devices, solid state storage devices, NAS devices, combinations of the same, and the like. In some cases, the secondary storage devices 108 are provided in a cloud (e.g. a private cloud or one operated by a third-party vendor).
The secondary storage device(s) 108 in some cases comprises a disk array or a portion thereof. In some cases, a single storage device (e.g., a disk array) is used for storing both primary data 112 and at least some secondary copies 116. In one example, a disk array capable of performing hardware snapshots stores primary data 112 and creates and stores hardware snapshots of the primary data 112 as secondary copies 116.
The Use of Intermediary Devices for Creating Secondary Copies
Creating secondary copies can be a challenging task. For instance, there can be hundreds or thousands of client computing devices 102 continually generating large volumes of primary data 112 to be protected. Also, there can be significant overhead involved in the creation of secondary copies 116. Moreover, secondary storage devices 108 may be special purpose components, and interacting with them can require specialized intelligence.
In some cases, the client computing devices 102 interact directly with the secondary storage device 108 to create the secondary copies 116. However, in view of the factors described above, this approach can negatively impact the ability of the client computing devices 102 to serve the applications 110 and produce primary data 112. Further, the client computing devices 102 may not be optimized for interaction with the secondary storage devices 108.
Thus, in some embodiments, the information management system 100 includes one or more software and/or hardware components which generally act as intermediaries between the client computing devices 102 and the secondary storage devices 108. In addition to off-loading certain responsibilities from the client computing devices 102, these intermediary components can provide other benefits. For instance, as discussed further below with respect to
The intermediary components can include one or more secondary storage computing devices 106 as shown in
The secondary storage computing device(s) 106 can comprise any appropriate type of computing device and can include, without limitation, any of the types of fixed and portable computing devices described above with respect to the client computing devices 102. In some cases, the secondary storage computing device(s) 106 include specialized hardware and/or software componentry for interacting with the secondary storage devices 108.
To create a secondary copy 116, the client computing device 102 communicates the primary data 112 to be copied (or a processed version thereof) to the designated secondary storage computing device 106, via the communication pathway 114. The secondary storage computing device 106 in turn conveys the received data (or a processed version thereof) to the secondary storage device 108. In some such configurations, the communication pathway 114 between the client computing device 102 and the secondary storage computing device 106 comprises a portion of a LAN, WAN or SAN. In other cases, at least some client computing devices 102 communicate directly with the secondary storage devices 108 (e.g., via Fibre Channel or SCSI connections).
Exemplary Primary Data and an Exemplary Secondary Copy
Some or all primary data objects are associated with a primary copy of object metadata (e.g., “Meta1-11”), which may be file system metadata and/or application specific metadata. Stored on the secondary storage device(s) 108 are secondary copy objects 134A-C which may include copies of or otherwise represent corresponding primary data objects and metadata.
As shown, the secondary copy objects 134A-C can individually represent more than one primary data object. For example, secondary copy data object 134A represents three separate primary data objects 133C, 122 and 129C (represented as 133C′, 122′ and 129C′, respectively). Moreover, as indicated by the prime mark (′), a secondary copy object may store a representation of a primary data object or metadata differently than the original format, e.g., in a compressed, encrypted, deduplicated, or other modified format.
Exemplary Information Management System Architecture
The information management system 100 can incorporate a variety of different hardware and software components, which can in turn be organized with respect to one another in many different configurations, depending on the embodiment. There are critical design choices involved in specifying the functional responsibilities of the components and the role of each component in the information management system 100. For instance, as will be discussed, such design choices can impact performance as well as the adaptability of the information management system 100 to data growth or other changing circumstances.
Storage Manager
As noted, the number of components in the information management system 100 and the amount of data under management can be quite large. Managing the components and data is therefore a significant task, and a task that can grow in an often unpredictable fashion as the quantity of components and data scale to meet the needs of the organization.
For these and other reasons, according to certain embodiments, responsibility for controlling the information management system 100, or at least a significant portion of that responsibility, is allocated to the storage manager 140.
By distributing control functionality in this manner, the storage manager 140 can be adapted independently according to changing circumstances. Moreover, a host computing device can be selected to best suit the functions of the storage manager 140. These and other advantages are described in further detail below with respect to
The storage manager 140 may be a software module or other application. The storage manager generally initiates, coordinates and/or controls storage and other information management operations performed by the information management system 100, e.g., to protect and control the primary data 112 and secondary copies 116 of data and metadata.
As shown by the dashed, arrowed lines, the storage manager 140 may communicate with and/or control some or all elements of the information management system 100, such as the data agents 142 and media agents 144. Thus, in certain embodiments, control information originates from the storage manager 140, whereas payload data and metadata is generally communicated between the data agents 142 and the media agents 144 (or otherwise between the client computing device(s) 102 and the secondary storage computing device(s) 106), e.g., at the direction of the storage manager 140. In other embodiments, some information management operations are controlled by other components in the information management system 100 (e.g., the media agent(s) 144 or data agent(s) 142), instead of or in combination with the storage manager 140.
According to certain embodiments, the storage manager provides one or more of the following functions:
The storage manager 140 may maintain a database 146 of management-related data and information management policies 148. The database 146 may include a management index 150 or other data structure that stores logical associations between components of the system, user preferences and/or profiles (e.g., preferences regarding encryption, compression, or deduplication of primary or secondary copy data, preferences regarding the scheduling, type, or other aspects of primary or secondary copy or other operations, mappings of particular information management users or user accounts to certain computing devices or other components, etc.), management tasks, media containerization, or other useful data. For example, the storage manager 140 may use the index 150 to track logical associations between media agents 144 and secondary storage devices 108 and/or movement of data from primary storage devices 104 to secondary storage devices 108.
Administrators and other employees may be able to manually configure and initiate certain information management operations on an individual basis. But while this may be acceptable for some recovery operations or other relatively less frequent tasks, it is often not workable for implementing on-going organization-wide data protection and management.
Thus, the information management system 100 may utilize information management policies 148 for specifying and executing information management operations (e.g., on an automated basis). Generally, an information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with storage or other information management operations.
The storage manager database 146 may maintain the information management policies 148 and associated data, although the information management policies 148 can be stored in any appropriate location. For instance, a storage policy may be stored as metadata in a media agent database 152 or in a secondary storage device 108 (e.g., as an archive copy) for use in restore operations or other information management operations, depending on the embodiment. Information management policies 148 are described further below.
According to certain embodiments, the storage manager database 146 comprises a relational database (e.g., an SQL database) for tracking metadata, such as metadata associated with secondary copy operations (e.g., what client computing devices 102 and corresponding data were protected). This and other metadata may additionally be stored in other locations, such as at the secondary storage computing devices 106 or on the secondary storage devices 108, allowing data recovery without the use of the storage manager 140.
As shown, the storage manager 140 may include a jobs agent 156, a user interface 158, and a management agent 154, all of which may be implemented as interconnected software modules or application programs.
The jobs agent 156 in some embodiments initiates, controls, and/or monitors the status of some or all storage or other information management operations previously performed, currently being performed, or scheduled to be performed by the information management system 100. For instance, the jobs agent 156 may access information management policies 148 to determine when and how to initiate and control secondary copy and other information management operations, as will be discussed further.
The user interface 158 may include information processing and display software, such as a graphical user interface (“GUI”), an application program interface (“API”), or other interactive interface through which users and system processes can retrieve information about the status of information management operations (e.g., storage operations) or issue instructions to the information management system 100 and its constituent components.
The storage manager 140 may also track information that permits it to select, designate, or otherwise identify content indices, deduplication databases, or similar databases or resources or data sets within its information management cell (or another cell) to be searched in response to certain queries. Such queries may be entered by the user via interaction with the user interface 158.
Via the user interface 158, users may optionally issue instructions to the components in the information management system 100 regarding performance of storage and recovery operations. For example, a user may modify a schedule concerning the number of pending secondary copy operations. As another example, a user may employ the GUI to view the status of pending storage operations or to monitor the status of certain components in the information management system 100 (e.g., the amount of capacity left in a storage device).
In general, the management agent 154 allows multiple information management systems 100 to communicate with one another. For example, the information management system 100 in some cases may be one information management subsystem or “cell” of a network of multiple cells adjacent to one another or otherwise logically related in a WAN or LAN. With this arrangement, the cells may be connected to one another through respective management agents 154.
For instance, the management agent 154 can provide the storage manager 140 with the ability to communicate with other components within the information management system 100 (and/or other cells within a larger information management system) via network protocols and application programming interfaces (“APIs”) including, e.g., HTTP, HTTPS, FTP, REST, virtualization software APIs, cloud service provider APIs, and hosted service provider APIs. Inter-cell communication and hierarchy is described in greater detail in U.S. Pat. No. 7,035,880, which is incorporated by reference herein.
Data Agents
As discussed, a variety of different types of applications 110 can reside on a given client computing device 102, including operating systems, database applications, e-mail applications, and virtual machines, just to name a few. And, as part of the as part of the process of creating and restoring secondary copies 116, the client computing devices 102 may be tasked with processing and preparing the primary data 112 from these various different applications 110. Moreover, the nature of the processing/preparation can differ across clients and application types, e.g., due to inherent structural and formatting differences between applications 110.
The one or more data agent(s) 142 are therefore advantageously configured in some embodiments to assist in the performance of information management operations based on the type of data that is being protected, at a client-specific and/or application-specific level.
The data agent 142 may be a software module or component that is generally responsible for managing, initiating, or otherwise assisting in the performance of information management operations. For instance, the data agent 142 may take part in performing data storage operations such as the copying, archiving, migrating, replicating of primary data 112 stored in the primary storage device(s) 104. The data agent 142 may receive control information from the storage manager 140, such as commands to transfer copies of data objects, metadata, and other payload data to the media agents 144.
In some embodiments, a data agent 142 may be distributed between the client computing device 102 and storage manager 140 (and any other intermediate components) or may be deployed from a remote location or its functions approximated by a remote process that performs some or all of the functions of data agent 142. In addition, a data agent 142 may perform some functions provided by a media agent 144, e.g., encryption and deduplication.
As indicated, each data agent 142 may be specialized for a particular application 110, and the system can employ multiple data agents 142, each of which may backup, migrate, and recover data associated with a different application 110. For instance, different individual data agents 142 may be designed to handle Microsoft Exchange data, Lotus Notes data, Microsoft Windows file system data, Microsoft Active Directory Objects data, SQL Server data, SharePoint data, Oracle database data, SAP database data, virtual machines and/or associated data, and other types of data.
A file system data agent, for example, may handle data files and/or other file system information. If a client computing device 102 has two or more types of data, one data agent 142 may be used for each data type to copy, archive, migrate, and restore the client computing device 102 data. For example, to backup, migrate, and restore all of the data on a Microsoft Exchange server, the client computing device 102 may use one Microsoft Exchange Mailbox data agent 142 to backup the Exchange mailboxes, one Microsoft Exchange Database data agent 142 to backup the Exchange databases, one Microsoft Exchange Public Folder data agent 142 to backup the Exchange Public Folders, and one Microsoft Windows File System data agent 142 to backup the file system of the client computing device 102. In such embodiments, these data agents 142 may be treated as four separate data agents 142 even though they reside on the same client computing device 102.
Other embodiments may employ one or more generic data agents 142 that can handle and process data from two or more different applications 110, or that can handle and process multiple data types, instead of or in addition to using specialized data agents 142. For example, one generic data agent 142 may be used to back up, migrate and restore Microsoft Exchange Mailbox data and Microsoft Exchange Database data while another generic data agent may handle Microsoft Exchange Public Folder data and Microsoft Windows File System data.
Each data agent 142 may be configured to access data and/or metadata stored in the primary storage device(s) 104 associated with the data agent 142 and process the data as appropriate. For example, during a secondary copy operation, the data agent 142 may arrange or assemble the data and metadata into one or more files having a certain format (e.g., a particular backup or archive format) before transferring the file(s) to a media agent 144 or other component. The file(s) may include a list of files or other metadata. Each data agent 142 can also assist in restoring data or metadata to primary storage devices 104 from a secondary copy 116. For instance, the data agent 142 may operate in conjunction with the storage manager 140 and one or more of the media agents 144 to restore data from secondary storage device(s) 108.
Media Agents
As indicated above with respect to
Generally speaking, a media agent 144 may be implemented as a software module that manages, coordinates, and facilitates the transmission of data, as directed by the storage manager 140, between a client computing device 102 and one or more secondary storage devices 108. Whereas the storage manager 140 controls the operation of the information management system 100, the media agent 144 generally provides a portal to secondary storage devices 108.
Media agents 144 can comprise logically and/or physically separate nodes in the information management system 100 (e.g., separate from the client computing devices 102, storage manager 140, and/or secondary storage devices 108). In addition, each media agent 144 may reside on a dedicated secondary storage computing device 106 in some cases, while in other embodiments a plurality of media agents 144 reside on the same secondary storage computing device 106.
A media agent 144 (and corresponding media agent database 152) may be considered to be “associated with” a particular secondary storage device 108 if that media agent 144 is capable of one or more of: routing and/or storing data to the particular secondary storage device 108, coordinating the routing and/or storing of data to the particular secondary storage device 108, retrieving data from the particular secondary storage device 108, and coordinating the retrieval of data from a particular secondary storage device 108.
While media agent(s) 144 are generally associated with one or more secondary storage devices 108, the media agents 144 in certain embodiments are physically separate from the secondary storage devices 108. For instance, the media agents 144 may reside on secondary storage computing devices 106 having different housings or packages than the secondary storage devices 108. In one example, a media agent 144 resides on a first server computer and is in communication with a secondary storage device(s) 108 residing in a separate, rack-mounted RAID-based system.
In operation, a media agent 144 associated with a particular secondary storage device 108 may instruct the secondary storage device 108 (e.g., a tape library) to use a robotic arm or other retrieval means to load or eject a certain storage media, and to subsequently archive, migrate, or retrieve data to or from that media, e.g., for the purpose of restoring the data to a client computing device 102. The media agent 144 may communicate with a secondary storage device 108 via a suitable communications link, such as a SCSI or Fiber Channel link.
As shown, each media agent 144 may maintain an associated media agent database 152. The media agent database 152 may be stored in a disk or other storage device (not shown) that is local to the secondary storage computing device 106 on which the media agent 144 resides. In other cases, the media agent database 152 is stored remotely from the secondary storage computing device 106.
The media agent database 152 can include, among other things, an index 153 including data generated during secondary copy operations and other storage or information management operations. The index 153 provides a media agent 144 or other component with a fast and efficient mechanism for locating secondary copies 116 or other data stored in the secondary storage devices 108. In one configuration, a storage manager index 150 or other data structure may store data associating a client computing device 102 with a particular media agent 144 and/or secondary storage device 108, as specified in a storage policy. A media agent index 153 or other data structure associated with the particular media agent 144 may in turn include information about the stored data.
For instance, for each secondary copy 116, the index 153 may include metadata such as a list of the data objects (e.g., files/subdirectories, database objects, mailbox objects, etc.), a path to the secondary copy 116 on the corresponding secondary storage device 108, location information indicating where the data objects are stored in the secondary storage device 108, when the data objects were created or modified, etc. Thus, the index 153 includes metadata associated with the secondary copies 116 that is readily available for use in storage operations and other activities without having to be first retrieved from the secondary storage device 108. In yet further embodiments, some or all of the data in the index 153 may instead or additionally be stored along with the data in a secondary storage device 108, e.g., with a copy of the index 153.
Because the index 153 maintained in the database 152 may operate as a cache, it can also be referred to as an index cache. In such cases, information stored in the index cache 153 typically comprises data that reflects certain particulars about storage operations that have occurred relatively recently. After some triggering event, such as after a certain period of time elapses, or the index cache 153 reaches a particular size, the index cache 153 may be copied or migrated to a secondary storage device(s) 108. This information may need to be retrieved and uploaded back into the index cache 153 or otherwise restored to a media agent 144 to facilitate retrieval of data from the secondary storage device(s) 108. In some embodiments, the cached information may include format or containerization information related to archives or other files stored on the storage device(s) 108. In this manner, the index cache 153 allows for accelerated restores.
In some alternative embodiments the media agent 144 generally acts as a coordinator or facilitator of storage operations between client computing devices 102 and corresponding secondary storage devices 108, but does not actually write the data to the secondary storage device 108. For instance, the storage manager 140 (or the media agent 144) may instruct a client computing device 102 and secondary storage device 108 to communicate with one another directly. In such a case the client computing device 102 transmits the data directly to the secondary storage device 108 according to the received instructions, and vice versa. In some such cases, the media agent 144 may still receive, process, and/or maintain metadata related to the storage operations. Moreover, in these embodiments, the payload data can flow through the media agent 144 for the purposes of populating the index cache 153 maintained in the media agent database 152, but not for writing to the secondary storage device 108.
The media agent 144 and/or other components such as the storage manager 140 may in some cases incorporate additional functionality, such as data classification, content indexing, deduplication, encryption, compression, and the like. Further details regarding these and other functions are described below.
Distributed, Scalable Architecture
As described, certain functions of the information management system 100 can be distributed amongst various physical and/or logical components in the system. For instance, one or more of the storage manager 140, data agents 142, and media agents 144 may reside on computing devices that are physically separate from one another. This architecture can provide a number of benefits.
For instance, hardware and software design choices for each distributed component can be targeted to suit its particular function. The secondary computing devices 106 on which the media agents 144 reside can be tailored for interaction with associated secondary storage devices 108 and provide fast index cache operation, among other specific tasks. Similarly, the client computing device(s) 102 can be selected to effectively service the applications 110 residing thereon, in order to efficiently produce and store primary data 112.
Moreover, in some cases, one or more of the individual components in the information management system 100 can be distributed to multiple, separate computing devices. As one example, for large file systems where the amount of data stored in the storage management database 146 is relatively large, the management database 146 may be migrated to or otherwise reside on a specialized database server (e.g., an SQL server) separate from a server that implements the other functions of the storage manager 140. This configuration can provide added protection because the database 146 can be protected with standard database utilities (e.g., SQL log shipping or database replication) independent from other functions of the storage manager 140. The database 146 can be efficiently replicated to a remote site for use in the event of a disaster or other data loss incident at the primary site. Or the database 146 can be replicated to another computing device within the same site, such as to a higher performance machine in the event that a storage manager host device can no longer service the needs of a growing information management system 100.
The distributed architecture also provides both scalability and efficient component utilization.
Additional components can be added or subtracted based on the evolving needs of the information management system 100. For instance, depending on where bottlenecks are identified, administrators can add additional client computing devices 102, secondary storage devices 106 (and corresponding media agents 144), and/or secondary storage devices 108.
Moreover, each client computing device 102 in some embodiments can communicate with any of the media agents 144, e.g., as directed by the storage manager 140. And each media agent 144 may be able to communicate with any of the secondary storage devices 108, e.g., as directed by the storage manager 140. Thus, operations can be routed to the secondary storage devices 108 in a dynamic and highly flexible manner. Further examples of scalable systems capable of dynamic storage operations are provided in U.S. Pat. No. 7,246,207, which is incorporated by reference herein.
In alternative configurations, certain components are not distributed and may instead reside and execute on the same computing device. For example, in some embodiments one or more data agents 142 and the storage manager 140 reside on the same client computing device 102. In another embodiment, one or more data agents 142 and one or more media agents 144 reside on a single computing device.
Exemplary Types of Information Management Operations
In order to protect and leverage stored data, the information management system 100 can be configured to perform a variety of information management operations. As will be described, these operations can generally include secondary copy and other data movement operations, processing and data manipulation operations, and management operations.
Data Movement Operations
Data movement operations according to certain embodiments are generally operations that involve the copying or migration of data (e.g., payload data) between different locations in the information management system 100. For example, data movement operations can include operations in which stored data is copied, migrated, or otherwise transferred from primary storage device(s) 104 to secondary storage device(s) 108, from secondary storage device(s) 108 to different secondary storage device(s) 108, or from primary storage device(s) 104 to different primary storage device(s) 104.
Data movement operations can include by way of example, backup operations, archive operations, information lifecycle management operations such as hierarchical storage management operations, replication operations (e.g., continuous data replication operations), snapshot operations, deduplication operations, single-instancing operations, auxiliary copy operations, and the like. As will be discussed, some of these operations involve the copying, migration or other movement of data, without actually creating multiple, distinct copies. Nonetheless, some or all of these operations are referred to as “copy” operations for simplicity.
Backup Operations
A backup operation creates a copy of primary data 112 at a particular point in time. Each subsequent backup copy may be maintained independently of the first. Further, a backup copy in some embodiments is stored in a backup format. This can be in contrast to the version in primary data 112 from which the backup copy is derived, and which may instead be stored in a native format of the source application(s) 110. In various cases, backup copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format. For example, a backup copy may be stored in a backup format that facilitates compression and/or efficient long-term storage.
Backup copies can have relatively long retention periods as compared to primary data 112, and may be stored on media with slower retrieval times than primary data 112 and certain other types of secondary copies 116. On the other hand, backups may have relatively shorter retention periods than some other types of secondary copies 116, such as archive copies (described below). Backups may sometimes be stored at on offsite location.
Backup operations can include full, synthetic or incremental backups. A full backup in some embodiments is generally a complete image of the data to be protected. However, because full backup copies can consume a relatively large amount of storage, it can be useful to use a full backup copy as a baseline and only store changes relative to the full backup copy for subsequent backup copies.
For instance, a differential backup operation (or cumulative incremental backup operation) tracks and stores changes that have occurred since the last full backup. Differential backups can grow quickly in size, but can provide relatively efficient restore times because a restore can be completed in some cases using only the full backup copy and the latest differential copy.
An incremental backup operation generally tracks and stores changes since the most recent backup copy of any type, which can greatly reduce storage utilization. In some cases, however, restore times can be relatively long in comparison to full or differential backups because completing a restore operation may involve accessing a full backup in addition to multiple incremental backups.
Any of the above types of backup operations can be at the file-level, e.g., where the information management system 100 generally tracks changes to files at the file-level, and includes copies of files in the backup copy. In other cases, block-level backups are employed, where files are broken into constituent blocks, and changes are tracked at the block-level. Upon restore, the information management system 100 reassembles the blocks into files in a transparent fashion.
Far less data may actually be transferred and copied to the secondary storage devices 108 during a block-level copy than during a file-level copy, resulting in faster execution times. However, when restoring a block-level copy, the process of locating constituent blocks can sometimes result in longer restore times as compared to file-level backups. Similar to backup operations, the other types of secondary copy operations described herein can also be implemented at either the file-level or the block-level.
Archive Operations
Because backup operations generally involve maintaining a version of the copied data in primary data 112 and also maintaining backup copies in secondary storage device(s) 108, they can consume significant storage capacity. To help reduce storage consumption, an archive operation according to certain embodiments creates a secondary copy 116 by both copying and removing source data. Or, seen another way, archive operations can involve moving some or all of the source data to the archive destination. Thus, data satisfying criteria for removal (e.g., data of a threshold age or size) from the source copy may be removed from source storage. Archive copies are sometimes stored in an archive format or other non-native application format. The source data may be primary data 112 or a secondary copy 116, depending on the situation. As with backup copies, archive copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format.
In addition, archive copies may be retained for relatively long periods of time (e.g., years) and, in some cases, are never deleted. Archive copies are generally retained for longer periods of time than backup copies, for example. In certain embodiments, archive copies may be made and kept for extended periods in order to meet compliance regulations.
Moreover, when primary data 112 is archived, in some cases the archived primary data 112 or a portion thereof is deleted when creating the archive copy. Thus, archiving can serve the purpose of freeing up space in the primary storage device(s) 104. Similarly, when a secondary copy 116 is archived, the secondary copy 116 may be deleted, and an archive copy can therefore serve the purpose of freeing up space in secondary storage device(s) 108. In contrast, source copies often remain intact when creating backup copies.
Snapshot Operations
Snapshot operations can provide a relatively lightweight, efficient mechanism for protecting data. From an end-user viewpoint, a snapshot may be thought of as an “instant” image of the primary data 112 at a given point in time. In one embodiment, a snapshot may generally capture the directory structure of an object in primary data 112 such as a file or volume or other data set at a particular moment in time and may also preserve file attributes and contents. A snapshot in some cases is created relatively quickly, e.g., substantially instantly, using a minimum amount of file space, but may still function as a conventional file system backup.
A snapshot copy in many cases can be made quickly and without significantly impacting primary computing resources because large amounts of data need not be copied or moved. In some embodiments, a snapshot may exist as a virtual file system, parallel to the actual file system. Users in some cases gain read-only access to the record of files and directories of the snapshot. By electing to restore primary data 112 from a snapshot taken at a given point in time, users may also return the current file system to the state of the file system that existed when the snapshot was taken.
Some types of snapshots do not actually create another physical copy of all the data as it existed at the particular point in time, but may simply create pointers that are able to map files and directories to specific memory locations (e.g., disk blocks) where the data resides, as it existed at the particular point in time. For example, a snapshot copy may include a set of pointers derived from the file system or an application. Each pointer points to a respective stored data block, so collectively, the set of pointers reflect the storage location and state of the data object (e.g., file(s) or volume(s) or data set(s)) at a particular point in time when the snapshot copy was created.
In some embodiments, once a snapshot has been taken, subsequent changes to the file system typically do not overwrite the blocks in use at the time of the snapshot. Therefore, the initial snapshot may use only a small amount of disk space needed to record a mapping or other data structure representing or otherwise tracking the blocks that correspond to the current state of the file system. Additional disk space is usually required only when files and directories are actually modified later. Furthermore, when files are modified, typically only the pointers which map to blocks are copied, not the blocks themselves. In some embodiments, for example in the case of “copy-on-write” snapshots, when a block changes in primary storage, the block is copied to secondary storage or cached in primary storage before the block is overwritten in primary storage. The snapshot mapping of file system data is also updated to reflect the changed block(s) at that particular point in time. In some other cases, a snapshot includes a full physical copy of all or substantially all of the data represented by the snapshot. Further examples of snapshot operations are provided in U.S. Pat. No. 7,529,782, which is incorporated by reference herein.
Replication Operations
Another type of secondary copy operation is a replication operation. Some types of secondary copies 116 are used to periodically capture images of primary data 112 at particular points in time (e.g., backups, archives, and snapshots). However, it can also be useful for recovery purposes to protect primary data 112 in a more continuous fashion, by replicating the primary data 112 substantially as changes occur. In some cases a replication copy can be a mirror copy, for instance, where changes made to primary data 112 are mirrored to another location (e.g., to secondary storage device(s) 108). By copying each write operation to the replication copy, two storage systems are kept synchronized or substantially synchronized so that they are virtually identical at approximately the same time. Where entire disk volumes are mirrored, however, mirroring can require significant amount of storage space and utilizes a large amount of processing resources.
According to some embodiments storage operations are performed on replicated data that represents a recoverable state, or “known good state” of a particular application running on the source system. For instance, in certain embodiments, known good replication copies may be viewed as copies of primary data 112. This feature allows the system to directly access, copy, restore, backup or otherwise manipulate the replication copies as if the data was the “live”, primary data 112. This can reduce access time, storage utilization, and impact on source applications 110, among other benefits.
Based on known good state information, the information management system 100 can replicate sections of application data that represent a recoverable state rather than rote copying of blocks of data. Examples of compatible replication operations (e.g., continuous data replication) are provided in U.S. Pat. No. 7,617,262, which is incorporated by reference herein.
Deduplication/Single-Instancing Operations
Another type of data movement operation is deduplication, which is useful to reduce the amount of data within the system. For instance, some or all of the above-described secondary storage operations can involve deduplication in some fashion. New data is read, broken down into blocks (e.g., sub-file level blocks) of a selected granularity, compared with blocks that are already stored, and only the new blocks are stored. Blocks that already exist are represented as pointers to the already stored data.
In order to stream-line the comparison process, the information management system 100 may calculate and/or store signatures (e.g., hashes) corresponding to the individual data blocks and compare the hashes instead of comparing entire data blocks. In some cases, only a single instance of each element is stored, and deduplication operations may therefore be referred to interchangeably as “single-instancing” operations. Depending on the implementation, however, deduplication or single-instancing operations can store more than one instance of certain data blocks, but nonetheless significantly reduce data redundancy. Moreover, single-instancing in some cases is distinguished from deduplication as a process of analyzing and reducing data at the file level, rather than the sub-file level.
Depending on the embodiment, deduplication blocks can be of fixed or variable length. Using variable length blocks can provide enhanced deduplication by responding to changes in the data stream, but can involve complex processing. In some cases, the information management system 100 utilizes a technique for dynamically aligning deduplication blocks (e.g., fixed-length blocks) based on changing content in the data stream, as described in U.S. Pat. Pub. No. 2012/0084269, which is incorporated by reference herein.
The information management system 100 can perform deduplication in a variety of manners at a variety of locations in the information management system 100. For instance, in some embodiments, the information management system 100 implements “target-side” deduplication by deduplicating data (e.g., secondary copies 116) stored in the secondary storage devices 108. In some such cases, the media agents 144 are generally configured to manage the deduplication process. For instance, one or more of the media agents 144 maintain a corresponding deduplication database that stores deduplication information (e.g., datablock signatures). Examples of such a configuration are provided in U.S. Pat. Pub. No. 2012/0150826, which is incorporated by reference herein. Deduplication can also be performed on the “source-side” (or “client-side”), e.g., to reduce the amount of traffic between the media agents 144 and the client computing device(s) 102 and/or reduce redundant data stored in the primary storage devices 104. Examples of such deduplication techniques are provided in U.S. Pat. Pub. No. 2012/0150818, which is incorporated by reference herein.
Information Lifecycle Management and Hierarchical Storage Management Operations
In some embodiments, files and other data over their lifetime move from more expensive, quick access storage to less expensive, slower access storage. Operations associated with moving data through various tiers of storage are sometimes referred to as information lifecycle management (ILM) operations.
One type of ILM operation is a hierarchical storage management (HSM) operation. A HSM operation is generally an operation for automatically moving data between classes of storage devices, such as between high-cost and low-cost storage devices. For instance, an HSM operation may involve movement of data from primary storage devices 104 to secondary storage devices 108, or between tiers of secondary storage devices 108. With each tier, the storage devices may be progressively relatively cheaper, have relatively slower access/restore times, etc. For example, movement of data between tiers may occur as data becomes less important over time.
In some embodiments, an HSM operation is similar to an archive operation in that creating an HSM copy may (though not always) involve deleting some of the source data. For example, an HSM copy may include data from primary data 112 or a secondary copy 116 that is larger than a given size threshold or older than a given age threshold and that is stored in a backup format.
Often, and unlike some types of archive copies, HSM data that is removed or aged from the source copy is replaced by a logical reference pointer or stub. The reference pointer or stub can be stored in the primary storage device 104 to replace the deleted data in primary data 112 (or other source copy) and to point to or otherwise indicate the new location in a secondary storage device 108.
According to one example, files are generally moved between higher and lower cost storage depending on how often the files are accessed. When a user requests access to the HSM data that has been removed or migrated, the information management system 100 uses the stub to locate the data and often make recovery of the data appear transparent, even though the HSM data may be stored at a location different from the remaining source data. The stub may also include some metadata associated with the corresponding data, so that a file system and/or application can provide some information about the data object and/or a limited-functionality version (e.g., a preview) of the data object.
An HSM copy may be stored in a format other than the native application format (e.g., where the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format). In some cases, copies which involve the removal of data from source storage and the maintenance of stub or other logical reference information on source storage may be referred to generally as “on-line archive copies”. On the other hand, copies which involve the removal of data from source storage without the maintenance of stub or other logical reference information on source storage may be referred to as “off-line archive copies”.
Auxiliary Copy and Disaster Recovery Operations
An auxiliary copy is generally a copy operation in which a copy is created of an existing secondary copy 116. For instance, an initial or “primary” secondary copy 116 may be generated using or otherwise be derived from primary data 112, whereas an auxiliary copy is generated from the initial secondary copy 116. Auxiliary copies can be used to create additional standby copies of data and may reside on different secondary storage devices 108 than initial secondary copies 116. Thus, auxiliary copies can be used for recovery purposes if initial secondary copies 116 become unavailable. Exemplary compatible auxiliary copy techniques are described in further detail in U.S. Pat. No. 8,230,195, which is incorporated by reference herein.
The information management system 100 may also perform disaster recovery operations that make or retain disaster recovery copies, often as secondary, high-availability disk copies. The information management system 100 may create secondary disk copies and store the copies at disaster recovery locations using auxiliary copy or replication operations, such as continuous data replication technologies. Depending on the particular data protection goals, disaster recovery locations can be remote from the client computing devices 102 and primary storage devices 104, remote from some or all of the secondary storage devices 108, or both.
Data Processing and Manipulation Operations
As indicated, the information management system 100 can also be configured to implement certain data manipulation operations, which according to certain embodiments are generally operations involving the processing or modification of stored data. Some data manipulation operations include content indexing operations and classification operations can be useful in leveraging the data under management to provide enhanced search and other features. Other data manipulation operations such as compression and encryption can provide data reduction and security benefits, respectively.
Data manipulation operations can be different than data movement operations in that they do not necessarily involve the copying, migration or other transfer of data (e.g., primary data 112 or secondary copies 116) between different locations in the system. For instance, data manipulation operations may involve processing (e.g., offline processing) or modification of already stored primary data 112 and/or secondary copies 116. However, in some embodiments data manipulation operations are performed in conjunction with data movement operations. As one example, the information management system 100 may encrypt data while performing an archive operation.
Content Indexing
In some embodiments, the information management system 100 “content indexes” data stored within the primary data 112 and/or secondary copies 116, providing enhanced search capabilities for data discovery and other purposes. The content indexing can be used to identify files or other data objects having pre-defined content (e.g., user-defined keywords or phrases), metadata (e.g., email metadata such as “to”, “from”, “cc”, “bcc”, attachment name, received time, etc.).
The information management system 100 generally organizes and catalogues the results in a content index, which may be stored within the media agent database 152, for example. The content index can also include the storage locations of (or pointer references to) the indexed data in the primary data 112 or secondary copies 116, as appropriate. The results may also be stored, in the form of a content index database or otherwise, elsewhere in the information management system 100 (e.g., in the primary storage devices 104, or in the secondary storage device 108). Such index data provides the storage manager 140 or another component with an efficient mechanism for locating primary data 112 and/or secondary copies 116 of data objects that match particular criteria.
For instance, search criteria can be specified by a user through user interface 158 of the storage manager 140. In some cases, the information management system 100 analyzes data and/or metadata in secondary copies 116 to create an “off-line” content index, without significantly impacting the performance of the client computing devices 102. Depending on the embodiment, the system can also implement “on-line” content indexing, e.g., of primary data 112. Examples of compatible content indexing techniques are provided in U.S. Pat. No. 8,170,995, which is incorporated by reference herein.
Classification Operations—Metabase
In order to help leverage the data stored in the information management system 100, one or more components can be configured to scan data and/or associated metadata for classification purposes to populate a metabase of information. Such scanned, classified data and/or metadata may be included in a separate database and/or on a separate storage device from primary data 112 (and/or secondary copies 116), such that metabase related operations do not significantly impact performance on other components in the information management system 100.
In other cases, the metabase(s) may be stored along with primary data 112 and/or secondary copies 116. Files or other data objects can be associated with user-specified identifiers (e.g., tag entries) in the media agent 144 (or other indices) to facilitate searches of stored data objects. Among a number of other benefits, the metabase can also allow efficient, automatic identification of files or other data objects to associate with secondary copy or other information management operations (e.g., in lieu of scanning an entire file system). Examples of compatible metabases and data classification operations are provided in U.S. Pat. Nos. 8,229,954 and 7,747,579, which are incorporated by reference herein.
Encryption Operations
The information management system 100 in some cases is configured to process data (e.g., files or other data objects, secondary copies 116, etc.), according to an appropriate encryption algorithm (e.g., Blowfish, Advanced Encryption Standard [AES], Triple Data Encryption Standard [3-DES], etc.) to limit access and provide data security in the information management system 100.
The information management system 100 in some cases encrypts the data at the client level, such that the client computing devices 102 (e.g., the data agents 142) encrypt the data prior to forwarding the data to other components, e.g., before sending the data media agents 144 during a secondary copy operation. In such cases, the client computing device 102 may maintain or have access to an encryption key or passphrase for decrypting the data upon restore. Encryption can also occur when creating copies of secondary copies, e.g., when creating auxiliary copies. In yet further embodiments, the secondary storage devices 108 can implement built-in, high performance hardware encryption.
Management Operations
Certain embodiments leverage the integrated, ubiquitous nature of the information management system 100 to provide useful system-wide management functions. As two non-limiting examples, the information management system 100 can be configured to implement operations management and e-discovery functions.
Operations management can generally include monitoring and managing the health and performance of information management system 100 by, without limitation, performing error tracking, generating granular storage/performance metrics (e.g., job success/failure information, deduplication efficiency, etc.), generating storage modeling and costing information, and the like.
Such information can be provided to users via the user interface 158 in a single, integrated view. For instance, the integrated user interface 158 can include an option to show a “virtual view” of the system that graphically depicts the various components in the system using appropriate icons. The operations management functionality can facilitate planning and decision-making. For example, in some embodiments, a user may view the status of some or all jobs as well as the status of each component of the information management system 100. Users may then plan and make decisions based on this data. For instance, a user may view high-level information regarding storage operations for the information management system 100, such as job status, component status, resource status (e.g., network pathways, etc.), and other information. The user may also drill down or use other means to obtain more detailed information regarding a particular component, job, or the like.
In some cases the information management system 100 alerts a user such as a system administrator when a particular resource is unavailable or congested. For example, a particular primary storage device 104 or secondary storage device 108 might be full or require additional capacity. Or a component may be unavailable due to hardware failure, software problems, or other reasons. In response, the information management system 100 may suggest solutions to such problems when they occur (or provide a warning prior to occurrence). For example, the storage manager 140 may alert the user that a secondary storage device 108 is full or otherwise congested. The storage manager 140 may then suggest, based on job and data storage information contained in its database 146, an alternate secondary storage device 108.
Other types of corrective actions may include suggesting an alternate data path to a particular primary or secondary storage device 104, 108, or dividing data to be stored among various available primary or secondary storage devices 104, 108 as a load balancing measure or to otherwise optimize storage or retrieval time. Such suggestions or corrective actions may be performed automatically, if desired. Further examples of some compatible operations management techniques and of interfaces providing an integrated view of an information management system are provided in U.S. Pat. No. 7,343,453, which is incorporated by reference herein. In some embodiments, the storage manager 140 implements the operations management functions described herein.
The information management system 100 can also be configured to perform system-wide e-discovery operations in some embodiments. In general, e-discovery operations provide a unified collection and search capability for data in the system, such as data stored in the secondary storage devices 108 (e.g., backups, archives, or other secondary copies 116). For example, the information management system 100 may construct and maintain a virtual repository for data stored in the information management system 100 that is integrated across source applications 110, different storage device types, etc. According to some embodiments, e-discovery utilizes other techniques described herein, such as data classification and/or content indexing.
Information Management Policies
As indicated previously, an information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with secondary copy or other information management operations.
One type of information management policy 148 is a storage policy. According to certain embodiments, a storage policy generally comprises a logical container that defines (or includes information sufficient to determine) one or more of the following items: (1) what data will be associated with the storage policy; (2) a destination to which the data will be stored; (3) datapath information specifying how the data will be communicated to the destination; (4) the type of storage operation to be performed; and (5) retention information specifying how long the data will be retained at the destination.
Data associated with a storage policy can be logically organized into groups, which can be referred to as “sub-clients”. A sub-client may represent static or dynamic associations of portions of a data volume. Sub-clients may represent mutually exclusive portions. Thus, in certain embodiments, a portion of data may be given a label and the association is stored as a static entity in an index, database or other storage location.
Sub-clients may also be used as an effective administrative scheme of organizing data according to data type, department within the enterprise, storage preferences, or the like. Depending on the configuration, sub-clients can correspond to files, folders, virtual machines, databases, etc. In one exemplary scenario, an administrator may find it preferable to separate e-mail data from financial data using two different sub-clients.
A storage policy can define where data is stored by specifying a target or destination storage device (or group of storage devices). For instance, where the secondary storage device 108 includes a group of disk libraries, the storage policy may specify a particular disk library for storing the sub-clients associated with the policy. As another example, where the secondary storage devices 108 include one or more tape libraries, the storage policy may specify a particular tape library for storing the sub-clients associated with the storage policy, and may also specify a drive pool and a tape pool defining a group of tape drives and a group of tapes, respectively, for use in storing the sub-client data.
Datapath information can also be included in the storage policy. For instance, the storage policy may specify network pathways and components to utilize when moving the data to the destination storage device(s). In some embodiments, the storage policy specifies one or more media agents 144 for conveying data (e.g., one or more sub-clients) associated with the storage policy between the source (e.g., one or more host client computing devices 102) and destination (e.g., a particular target secondary storage device 108).
A storage policy can also specify the type(s) of operations associated with the storage policy, such as a backup, archive, snapshot, auxiliary copy, or the like. Retention information can specify how long the data will be kept, depending on organizational needs (e.g., a number of days, months, years, etc.)
The information management policies 148 may also include one or more scheduling policies specifying when and how often to perform operations. Scheduling information may specify with what frequency (e.g., hourly, weekly, daily, event-based, etc.) or under what triggering conditions secondary copy or other information management operations will take place. Scheduling policies in some cases are associated with particular components, such as particular sub-clients, client computing device 102, and the like. In one configuration, a separate scheduling policy is maintained for particular sub-clients on a client computing device 102. The scheduling policy specifies that those sub-clients are to be moved to secondary storage devices 108 every hour according to storage policies associated with the respective sub-clients.
When adding a new client computing device 102, administrators can manually configure information management policies 148 and/or other settings, e.g., via the user interface 158. However, this can be an involved process resulting in delays, and it may be desirable to begin data protecting operations quickly.
Thus, in some embodiments, the information management system 100 automatically applies a default configuration to client computing device 102. As one example, when a data agent(s) 142 is installed on a client computing devices 102, the installation script may register the client computing device 102 with the storage manager 140, which in turn applies the default configuration to the new client computing device 102. In this manner, data protection operations can begin substantially immediately. The default configuration can include a default storage policy, for example, and can specify any appropriate information sufficient to begin data protection operations. This can include a type of data protection operation, scheduling information, a target secondary storage device 108, data path information (e.g., a particular media agent 144), and the like.
Other types of information management policies 148 are possible. For instance, the information management policies 148 can also include one or more audit or security policies. An audit policy is a set of preferences, rules and/or criteria that protect sensitive data in the information management system 100. For example, an audit policy may define “sensitive objects” as files or objects that contain particular keywords (e.g. “confidential,” or “privileged”) and/or are associated with particular keywords (e.g., in metadata) or particular flags (e.g., in metadata identifying a document or email as personal, confidential, etc.).
An audit policy may further specify rules for handling sensitive objects. As an example, an audit policy may require that a reviewer approve the transfer of any sensitive objects to a cloud storage site, and that if approval is denied for a particular sensitive object, the sensitive object should be transferred to a local storage device 104 instead. To facilitate this approval, the audit policy may further specify how a secondary storage computing device 106 or other system component should notify a reviewer that a sensitive object is slated for transfer.
In some implementations, the information management policies 148 may include one or more provisioning policies. A provisioning policy can include a set of preferences, priorities, rules, and/or criteria that specify how clients 102 (or groups thereof) may utilize system resources, such as available storage on cloud storage and/or network bandwidth. A provisioning policy specifies, for example, data quotas for particular client computing devices 102 (e.g. a number of gigabytes that can be stored monthly, quarterly or annually). The storage manager 140 or other components may enforce the provisioning policy. For instance, the media agents 144 may enforce the policy when transferring data to secondary storage devices 108. If a client computing device 102 exceeds a quota, a budget for the client computing device 102 (or associated department) is adjusted accordingly or an alert may trigger.
While the above types of information management policies 148 have been described as separate policies, one or more of these can be generally combined into a single information management policy 148. For instance, a storage policy may also include or otherwise be associated with one or more scheduling, audit, or provisioning policies. Moreover, while storage policies are typically associated with moving and storing data, other policies may be associated with other types of information management operations. The following is a non-exhaustive list of items the information management policies 148 may specify:
Policies can additionally specify or depend on a variety of historical or current criteria that may be used to determine which rules to apply to a particular data object, system component, or information management operation, such as:
As indicated by the dashed box, the second media agent 144B and the tape library 108B are “off-site”, and may therefore be remotely located from the other components in the information management system 100 (e.g., in a different city, office building, etc.). In this manner, information stored on the tape library 108B may provide protection in the event of a disaster or other failure.
The file system sub-client and its associated primary data 112A in certain embodiments generally comprise information generated by the file system and/or operating system of the client computing device 102, and can include, for example, file system data (e.g., regular files, file tables, mount points, etc.), operating system data (e.g., registries, event logs, etc.), and the like. The e-mail sub-client, on the other hand, and its associated primary data 112B, include data generated by an e-mail client application operating on the client computing device 102, and can include mailbox information, folder information, emails, attachments, associated database information, and the like. As described above, the sub-clients can be logical containers, and the data included in the corresponding primary data 112A, 112B may or may not be stored contiguously.
The exemplary storage policy 148A includes a backup copy rule set 160, a disaster recovery copy rule set 162, and a compliance copy rule set 164. The backup copy rule set 160 specifies that it is associated with a file system sub-client 166 and an email sub-client 168. Each of these sub-clients 166, 168 are associated with the particular client computing device 102. The backup copy rule set 160 further specifies that the backup operation will be written to the disk library 108A, and designates a particular media agent 144A to convey the data to the disk library 108A. Finally, the backup copy rule set 160 specifies that backup copies created according to the rule set 160 are scheduled to be generated on an hourly basis and to be retained for 30 days. In some other embodiments, scheduling information is not included in the storage policy 148A, and is instead specified by a separate scheduling policy.
The disaster recovery copy rule set 162 is associated with the same two sub-clients 166, 168. However, the disaster recovery copy rule set 162 is associated with the tape library 108B, unlike the backup copy rule set 160. Moreover, the disaster recovery copy rule set 162 specifies that a different media agent 144B than the media agent 144A associated with the backup copy rule set 160 will be used to convey the data to the tape library 108B. As indicated, disaster recovery copies created according to the rule set 162 will be retained for 60 days, and will be generated on a daily basis. Disaster recovery copies generated according to the disaster recovery copy rule set 162 can provide protection in the event of a disaster or other data-loss event that would affect the backup copy 116A maintained on the disk library 108A.
The compliance copy rule set 164 is only associated with the email sub-client 166, and not the file system sub-client 168. Compliance copies generated according to the compliance copy rule set 164 will therefore not include primary data 112A from the file system sub-client 166. For instance, the organization may be under an obligation to store maintain copies of email data for a particular period of time (e.g., 10 years) to comply with state or federal regulations, while similar regulations do not apply to the file system data. The compliance copy rule set 164 is associated with the same tape library 108B and media agent 144B as the disaster recovery copy rule set 162, although a different storage device or media agent could be used in other embodiments. Finally, the compliance copy rule set 164 specifies that copies generated under the compliance copy rule set 164 will be retained for 10 years, and will be generated on a quarterly basis.
At step 1, the storage manager 140 initiates a backup operation according to the backup copy rule set 160. For instance, a scheduling service running on the storage manager 140 accesses scheduling information from the backup copy rule set 160 or a separate scheduling policy associated with the client computing device 102, and initiates a backup copy operation on an hourly basis. Thus, at the scheduled time slot the storage manager 140 sends instructions to the client computing device 102 to begin the backup operation.
At step 2, the file system data agent 142A and the email data agent 142B residing on the client computing device 102 respond to the instructions received from the storage manager 140 by accessing and processing the primary data 112A, 112B involved in the copy operation from the primary storage device 104. Because the operation is a backup copy operation, the data agent(s) 142A, 142B may format the data into a backup format or otherwise process the data.
At step 3, the client computing device 102 communicates the retrieved, processed data to the first media agent 144A, as directed by the storage manager 140, according to the backup copy rule set 160. In some other embodiments, the information management system 100 may implement a load-balancing, availability-based, or other appropriate algorithm to select from the available set of media agents 144A, 144B. Regardless of the manner the media agent 144A is selected, the storage manager 140 may further keep a record in the storage manager database 140 of the association between the selected media agent 144A and the client computing device 102 and/or between the selected media agent 144A and the backup copy 116A.
The target media agent 144A receives the data from the client computing device 102, and at step 4 conveys the data to the disk library 108A to create the backup copy 116A, again at the direction of the storage manager 140 and according to the backup copy rule set 160. The secondary storage device 108A can be selected in other ways. For instance, the media agent 144A may have a dedicated association with a particular secondary storage device(s), or the storage manager 140 or media agent 144A may select from a plurality of secondary storage devices, e.g., according to availability, using one of the techniques described in U.S. Pat. No. 7,246,207, which is incorporated by reference herein.
The media agent 144A can also update its index 153 to include data and/or metadata related to the backup copy 116A, such as information indicating where the backup copy 116A resides on the disk library 108A, data and metadata for cache retrieval, etc. After the 30 day retention period expires, the storage manager 140 instructs the media agent 144A to delete the backup copy 116A from the disk library 108A.
At step 5, the storage manager 140 initiates the creation of a disaster recovery copy 116B according to the disaster recovery copy rule set 162. For instance, at step 6, based on instructions received from the storage manager 140 at step 5, the specified media agent 144B retrieves the most recent backup copy 116A from the disk library 108A.
At step 7, again at the direction of the storage manager 140 and as specified in the disaster recovery copy rule set 162, the media agent 144B uses the retrieved data to create a disaster recovery copy 116B on the tape library 108B. In some cases, the disaster recovery copy 116B is a direct, mirror copy of the backup copy 116A, and remains in the backup format. In other embodiments, the disaster recovery copy 116C may be generated in some other manner, such as by using the primary data 112A, 112B from the storage device 104 as source data. The disaster recovery copy operation is initiated once a day and the disaster recovery copies 116A are deleted after 60 days.
At step 8, the storage manager 140 initiates the creation of a compliance copy 116C, according to the compliance copy rule set 164. For instance, the storage manager 140 instructs the media agent 144B to create the compliance copy 116C on the tape library 108B at step 9, as specified in the compliance copy rule set 164. In the example, the compliance copy 116C is generated using the disaster recovery copy 116B. In other embodiments, the compliance copy 116C is instead generated using either the primary data 112B corresponding to the email sub-client or using the backup copy 116A from the disk library 108A as source data. As specified, compliance copies 116C are created quarterly, and are deleted after ten years.
While not shown in
In other cases, a media agent may be selected for use in the restore operation based on a load balancing algorithm, an availability based algorithm, or other criteria. The selected media agent 144A retrieves the data from the disk library 108A. For instance, the media agent 144A may access its index 153 to identify a location of the backup copy 116A on the disk library 108A, or may access location information residing on the disk 108A itself.
When the backup copy 116A was recently created or accessed, the media agent 144A accesses a cached version of the backup copy 116A residing in the media agent index 153, without having to access the disk library 108A for some or all of the data. Once it has retrieved the backup copy 116A, the media agent 144A communicates the data to the source client computing device 102. Upon receipt, the file system data agent 142A and the email data agent 142B may unpackage (e.g., restore from a backup format to the native application format) the data in the backup copy 116A and restore the unpackaged data to the primary storage device 104.
Exemplary Secondary Copy Formatting
The formatting and structure of secondary copies 116 can vary, depending on the embodiment. In some cases, secondary copies 116 are formatted as a series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4 GB, or 8 GB chunks). This can facilitate efficient communication and writing to secondary storage devices 108, e.g., according to resource availability. For example, a single secondary copy 116 may be written on a chunk-by-chunk basis to a single secondary storage device 108 or across multiple secondary storage devices 108. In some cases, users can select different chunk sizes, e.g., to improve throughput to tape storage devices.
Generally, each chunk can include a header and a payload. The payload can include files (or other data units) or subsets thereof included in the chunk, whereas the chunk header generally includes metadata relating to the chunk, some or all of which may be derived from the payload. For example, during a secondary copy operation, the media agent 144, storage manager 140, or other component may divide the associated files into chunks and generate headers for each chunk by processing the constituent files.
The headers can include a variety of information such as file identifier(s), volume(s), offset(s), or other information associated with the payload data items, a chunk sequence number, etc. Importantly, in addition to being stored with the secondary copy 116 on the secondary storage device 108, the chunk headers can also be stored to the index 153 of the associated media agent(s) 144 and/or the storage manager index 150. This is useful in some cases for providing faster processing of secondary copies 116 during restores or other operations. In some cases, once a chunk is successfully transferred to a secondary storage device 108, the secondary storage device 108 returns an indication of receipt, e.g., to the media agent 144 and/or storage manager 140, which may update their respective indexes 150, 153 accordingly.
During restore, chunks may be processed (e.g., by the media agent 144) according to the information in the chunk header to reassemble the files. Additional information relating to chunks can be found in U.S. Pat. No. 8,156,086, which is incorporated by reference herein.
Snapshot Sharing System
In certain embodiments, the system 200 includes a storage manager 240, which may include one or more of the following modules or components: a volume replication table, a storage manager index cache, a client, an information store, a data agent, a media agent, a media agent index cache, and a storage device.
The source system 202 may include one or more applications 210, one or more data agents 242, and a snapshot manager 224 executing thereon. The applications 210 can include software applications executing on the source system 202 and may generate and modify production data. As just a few examples, the software applications 210 may include database applications, server software, virtual machine managers, operating systems, file system management software, and other types of applications.
The source system 202 can include a data store 204 for storing the production data generated by the applications 210. The source storage 204 may include any type of physical media capable of storing electronic data. For example, the source storage 204 may comprise magnetic storage, such as a disk drive, or other type of mass storage. In certain embodiments, the source storage 204 may be internal and/or external to (e.g., remote to) one or more other components of the source system 202. In yet other embodiments, the source storage 204 can include a NAS or the like. In certain embodiments, the source storage 204 includes relatively fast access times as compared to tape or other relatively slower or less expensive media. For instance, the destination storage can include hard disk drives (HDD's) including spinning media or solid state drives (SDD's) including solid-state storage, such as flash-based or DRAM-based SSD's.
In certain embodiments, the data agent(s) 242 provide an interface to a source data store 204 to execute copies, snapshots, archiving, migration, recovery and other storage operations on data, for example, in conjunction with one or more media agents. In certain embodiments, a source system 202 runs a number of data agents 242, wherein each data agent is configured to interface with data generated by or from one or more applications 210. For example, a first data agent may be configured to interface with Microsoft Exchange data and a second data agent to interface with Oracle database data. As is explained in greater detail herein, a data agent 242 may be in communication with one or more media agents to effect the distributed storage of snapshots on one or more storage devices that are remote from the information store that is the source of the snapshot.
The storage manager 240 may communicate with data and/or media agents to control and manage snapshot creation, migration, recovery and other storage operations. According to one embodiment, the storage manger 240 maintains data in a storage manager index cache that instructs a given data agent 242 to work in conjunction with a specific media agent to store snapshots on one or more storage devices 208. In certain embodiments, a snapshot is spread over multiple storage devices. In certain embodiments, metadata associated with one or more snapshots is stored in the media agent(s) 252, whereas the storage array 208 provides storage for the snapshots themselves. Storage may be provisioned from the destination storage array 208 to the source system 202. In certain embodiments, application agents of the source system 202 provide requests to the media agent(s) 252, wherein the media agent(s) communicates requests to the storage array 208 for snapshot creation.
The snapshot manager 224 can be a software module that is generally configured to manage interaction with the destination system 216 to carry out snapshot operations. The snapshot operations can include, without limitation, snapshot creation, mounting, unmounting, deletion and reversion. The components of the snapshot manager 224 in some embodiments work together to gather and/or package the appropriate data and metadata related to the requested snapshot operation for transmission to the destination system 216. In certain embodiments, the snapshot management layer 224 or portions thereof are implemented on a proxy system (not shown) that is separate from the source system 202, instead of, or in addition to being implemented on the source system 202. The proxy system can therefore be configured to perform some or all of the snapshot management processing, thereby alleviating the associated burden from the source system 202 and improving performance of the source system 202.
The snapshot manager 224 may utilize a catalog/system table to track multiple snapshots across multiple storage devices. For example, the system may, as directed by a policy or a user, store a first snapshot on a first storage device, such as a tape drive or library, and then store subsequent snapshots containing only the changed cluster(s) on a second storage device, such as an optical drive or library. Alternatively, instructions may be stored within system components, such as the storage manager 240 or media agent 252, directing the storage device(s) 208 used to store snapshots.
The system catalog may provide mapping data for locating and/or identifying data in the snapshot associated with one or more particular applications/agents. Furthermore, the catalog may indicate the number and/or type of applications associated with the snapshot data. In certain embodiments, catalog data is maintained by one or more of the requesting applications associated with the snapshot. For example, a first application associated with the snapshot may initiate population of the catalog by providing information related to itself, wherein subsequent applications associated with the snapshot may provide further data. In certain embodiments, the catalog is used to locate relevant data for restoration of data associated with one or more of the applications.
In certain embodiments, certain storage devices of the system are configured to create and/or store snapshot copies of production data that is generated by applications running on the source system 202, such as the production data stored in the source storage 204. For example, destination storage devices can be capable of performing hardware-based snapshots (e.g., storage array-based hardware snapshots).
The snapshot manager 224 may manage the creation of a snapshot in the corresponding storage array 208. In some embodiments, the snapshot manager 224 is a software module executing on the source system 202, or is implemented in hardware/software on the destination system 216. Furthermore, in certain embodiments, the snapshot manager 224 is a component of the storage manager 240.
The data agents 242 may generally manage the movement of the production data from the applications to the source storage 204 and/or other locations in the storage system 200. In some embodiments, the data agents 242 manage movement of the production data to the storage array 208208, either directly, or indirectly (e.g., from the source storage 204), depending on the embodiment. The data agents 242 can also be responsible for backing up, archiving, migrating or otherwise creating copies of production data on secondary storage, either directly, or via one or more media agents.
Each data agent 242 may be application-specific and associated with a corresponding application, such as any of the applications or types of applications discussed herein. For example, without limitation, applications may be associated with one or more of the following: DB2, Informix, Microsoft Exchange, Microsoft Hyper-V, Microsoft SharePoint Server, Microsoft SQL Server, Oracle, SAP, and for the Microsoft Windows, Linux and Unix file systems. In certain embodiments, the data agents 242 may be generic, where each data agent is capable of handling two or more data types, such as data generated by different applications. The data agents in some embodiments process data to provide application-consistent storage of production data. In some embodiments, the data agents 424 are in communication with the snapshot manager 224 and are responsible for directing data and metadata transfer between the snapshot manager 224 and the source storage 204 during snapshot operations.
The system 200 includes a destination system 216 where snapshots and/or backup copies may be stored. The destination system may include one or more media agents 252, an index cache 253, and a storage array 208 comprising media on which snapshots and/or backup copies may be stored. In certain embodiments, the media agent(s) and/or storage array 208 may be separate from the destination system 216. The destination system 216 may include an index, or index cache 253, which may include data generated during secondary copy operations and other storage or information management operations. The index cache 253 can provide the media agent(s) 252 with a fast and efficient mechanism for locating snapshots located in the storage array 208, or other data stored in the storage array 208. In certain embodiments, the index cache 253 includes metadata or other information relating to data stored in the storage array 208. Such metadata may include, for example, a path to the snapshots 209 stored in the storage array 208, when the snapshots were created or modified, etc. The index cache 253 may, therefore, include metadata associated with the snapshots that is readily available for use in storage operations and other activities without having to be first retrieved from the storage array 208. In certain embodiments, some or all of the data in the index cache 253 may instead or additionally be stored along with the snapshots 209 in the storage array 208.
The media agent 252 may receive snapshots, possibly including the changed data that is tracked by the snapshot, from one or more data agents 242 and determine one or more storage arrays 208 to which the snapshot should be written. According to one embodiment, the media agent 252 applies load-balancing algorithms to select a storage array 208 to which to write the snapshot. Alternatively, the snapshots may be provided directly to the storage array 208 by the source system 202, such as by one or more data agents 242.
In certain embodiments, the storage manager 240 may instruct the media agent 252 as to which storage array 208 the snapshot should be written. In this manner, snapshots from a given source storage device 204 may be written to one or more storage arrays 208, improving data availability for restoration purposes in the event that the source storage fails. Either the media agent 252 or the storage manager 240 may record the storage device on which the snapshot is written in a catalog/system table, thereby allowing the snapshot to be located when required for restoring the source storage 204.
The index cache 253 may be configured to store index data the system generates during snapshot, migration, and restore operations. For example, storage operations for Microsoft Exchange data generate application specific index data regarding the substantive Exchange data. Similarly, other applications may be capable of generating application specific data during a snapshot. Such data may generally be described as metadata. A media agent index cache may track data that includes, for example, information regarding the location of stored data on a given volume. Index data provides the system with an efficient mechanism for locating user files during storage operations such as copying, performing snapshots and recovery. In certain embodiments, the index data may be stored with the snapshot that is backed up to the destination storage 208, and the media agent that controls the storage operation may also write an additional copy of the index data to its media agent index cache.
The destination storage 208 may include any type of physical media capable of storing electronic data. For example, the destination storage 208 may comprise magnetic storage, such as a disk or a tape drive, or other type of mass storage. In certain embodiments, the destination storage 208 may be internal and/or external to (e.g., remote to) one or more other components of the destination system 216. In yet other embodiments, the destination storage 208 can include a NAS or the like. In certain embodiments, the destination storage 208 includes relatively fast access times as compared to tape or other relatively slower or less expensive media. For instance, the destination storage can include hard disk drives (HDD's) including spinning media or solid state drives (SDD's) including solid-state storage, such as flash-based or DRAM-based SSD's. In certain embodiments, the destination system 216 includes one or more separate computing devices (not shown). For instance, where replication is used (e.g., CDR), the destination system 216 may include a separate computing device in communication with the destination system 216 and including a replication module configured to manage replication of the data stored in the source storage 204.
Data Storage Allocation for Snapshots
Certain embodiments disclosed herein provide a system requiring a reduced amount of snapshots, wherein a global snapshot is taken and virtually separated into relevant portions for particular clients and application. A data management/storage system may include one or more destination and/or source storage devices.
In certain systems, multiple applications and/or clients may share a single LUN. For example, multiple databases (e.g., DB1, DB2, DB3) may be stored on the LUN 309 in association with one or more client volumes 313. Furthermore, the LUN 309 may include data generated by both database data and file system data applications, as shown. In certain systems or embodiments, when a snapshot is performed for a particular application/database (e.g., for DB1 associated with Client A), a snapshot may be taken of the entire LUN 309 with which the application is associated. The relevant portions of the snapshot may be subsequently identified and stored in association with the requesting application. However, remaining portions of the snapshot may then be discarded, introducing operational inefficiencies into the snapshot system. Certain embodiments disclosed herein provide systems and methods for reusing global snapshots for multiple applications and/or clients, thereby improving operational efficiency.
Shared Snapshot Generation
The process 400 may further include receiving a request to take a snapshot of the LUN from one or more applications (block 420). For example, such request may be directed by a snapshot manager module as described above. In accordance with the request, a single snapshot may be taken at block 440 of the LUN or a portion thereof, wherein the process 400 further includes grouping snapshot requests from multiple applications in order to partition the single snapshot to be shared among the requesting applications.
In order to track the locations of the various snapshot partitions, the process 400 may include identifying the locations within the snapshot of the data associated with the various applications and cataloging such information in a system table/catalog. With reference to the system catalog, the snapshot may be stored in the storage system as separate snapshots associated with the separate applications/agents.
Grouping Applications for Single Snapshot Applicability
As described above, generation of shared snapshots can involve grouping snapshots requested by multiple applications together in a single snapshot of the LUN on which the relevant volumes of data are maintained.
In certain embodiments, snapshot requests are grouped based on time of receipt. Grouping snapshot requests based on time relative to the time of creation of the global snapshot may increase the likelihood that a particular request with be associated with a state of the source data adequately represented by the global snapshot. For example, if a request is made too far removed in time from the generation of the global snapshot, data changes occurring during the gap in time may be undesirably, or inadequately reflected in the global snapshot. Therefore, blocks 510-550 provide a time-based process for grouping snapshot requests. As illustrated by
As described above, once the related snaps have been grouped together, a single global snap may be performed. It may be necessary or desirable to provide notification of that the grouped snapshot is to be taken in order to allow for snapshot consistency and/or application quiescing. Once the global snap has been taken, associated application I/O may be resumed/unquiesced. Furthermore, the portions of the global snap that relate to each of the grouped snapshots may then be identified and cataloged. The cataloged portions of the general snap may then be stored as separate snaps for each of the grouped snaps.
In certain embodiments, when the system desires to prune data from the backups, the system uses the snap catalog to quickly identify data that can be pruned. For example, if the data associated with a particular application is being pruned the catalog identifies where the data is located in the snap catalog.
At block 570, the snapshot is taken that is associated with each of the group members. For example, a single snapshot may be taken per LUN. In certain embodiments, the master job is responsible to taking the snapshot and storing data in the system catalog identifying the location of the master job within the snapshot. The master job may then pass the catalog to the next job for further additions to the catalog. In certain embodiments, each job maintains its own catalog. For example, a single job may have access to the catalog entries associated with other jobs, but may have no reason or capability to monitor catalog data associated with other jobs.
When a snapshot job has been completed, associated applications/agent processes may receive access to the snapshot for the purposes of verifying the consistency of the snapshot data. In certain embodiments, when a job no longer has a use for the snapshot, the snapshot is not discarded, but is maintained until all group members likewise have no need for the snapshot. At such point, the snapshot may be discarded.
Snapshot Catalog Restoration
In certain embodiments, when the system desires to restore data from the backups, the system uses the snapshot catalog(s) to identify which data to be restored from the global snap. Therefore, it may not be necessary to restore the entire snapshot. When an application requests restoration of a portion of the snapshot, the remainder of the snapshot may be reused by other applications to the extent that the data associated with the applications is valid.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out all together (e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described herein. Software and other modules may reside on servers, workstations, personal computers, computerized tablets, PDAs, and other devices suitable for the purposes described herein. Software and other modules may be accessible via local memory, via a network, via a browser, or via other means suitable for the purposes described herein. Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes or methods, or any combinations thereof, suitable for the purposes described herein. User interface elements described herein may comprise elements from graphical user interfaces, command line interfaces, and other suitable interfaces.
Further, the processing of the various components of the illustrated systems can be distributed across multiple machines, networks, and other computing resources. In addition, two or more components of a system can be combined into fewer components. Various components of the illustrated systems can be implemented in one or more virtual machines, rather than in dedicated computer hardware systems. Likewise, the data repositories shown can represent physical and/or logical data storage, including, for example, storage area networks or other distributed storage systems. Moreover, in some embodiments the connections between the components shown represent possible paths of data flow, rather than actual connections between hardware. While some examples of possible connections are shown, any of the subset of the components shown can communicate with any other subset of components in various implementations.
Embodiments are also described above with reference to flow chart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products. Each block of the flow chart illustrations and/or block diagrams, and combinations of blocks in the flow chart illustrations and/or block diagrams, may be implemented by computer program instructions. Such instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the acts specified in the flow chart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the acts specified in the flow chart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the acts specified in the flow chart and/or block diagram block or blocks.
While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the disclosure. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the described methods and systems may be made without departing from the spirit of the disclosure. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the disclosure.
This application is a continuation of U.S. patent application Ser. No. 15/888,592, filed on Feb. 5, 2018 and entitled “SINGLE SNAPSHOT FOR MULTIPLE AGENTS,” which is a continuation of U.S. patent application Ser. No. 14/151,650, filed on Jan. 9, 2014 and entitled “SINGLE SNAPSHOT FOR MULTIPLE AGENTS,” which claims the benefit of priority under 35 U.S.C. § 119(e) to U.S. Provisional Application No. 61/751,790, filed on Jan. 11, 2013 and entitled “SINGLE SNAPSHOP FOR MULTIPLE AGENTS,” and U.S. Provisional Application No. 61/805,063, filed on Mar. 25, 2013 and entitled “SINGLE SNAPSHOT FOR MULTIPLE AGENTS.” Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 CFR 1.57.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4296465 | Lemak | Oct 1981 | A |
| 4686620 | Ng | Aug 1987 | A |
| 4995035 | Cole et al. | Feb 1991 | A |
| 5005122 | Griffin et al. | Apr 1991 | A |
| 5093912 | Dong et al. | Mar 1992 | A |
| 5133065 | Cheffetz et al. | Jul 1992 | A |
| 5193154 | Kitajima et al. | Mar 1993 | A |
| 5212772 | Masters | May 1993 | A |
| 5226157 | Nakano et al. | Jul 1993 | A |
| 5239647 | Anglin et al. | Aug 1993 | A |
| 5241668 | Eastridge et al. | Aug 1993 | A |
| 5241670 | Eastridge et al. | Aug 1993 | A |
| 5263154 | Eastridge et al. | Nov 1993 | A |
| 5265159 | Kung | Nov 1993 | A |
| 5276860 | Fortier et al. | Jan 1994 | A |
| 5276867 | Kenley et al. | Jan 1994 | A |
| 5287500 | Stoppani, Jr. | Feb 1994 | A |
| 5301351 | Jippo | Apr 1994 | A |
| 5311509 | Heddes et al. | May 1994 | A |
| 5317731 | Dias et al. | May 1994 | A |
| 5321816 | Rogan et al. | Jun 1994 | A |
| 5333315 | Saether et al. | Jul 1994 | A |
| 5347653 | Flynn et al. | Sep 1994 | A |
| 5369757 | Spiro et al. | Nov 1994 | A |
| 5403639 | Belsan et al. | Apr 1995 | A |
| 5410700 | Fecteau et al. | Apr 1995 | A |
| 5448724 | Hayashi et al. | Sep 1995 | A |
| 5455926 | Keele et al. | Oct 1995 | A |
| 5487072 | Kant | Jan 1996 | A |
| 5491810 | Allen | Feb 1996 | A |
| 5495607 | Pisello et al. | Feb 1996 | A |
| 5504873 | Martin et al. | Apr 1996 | A |
| 5544345 | Carpenter et al. | Aug 1996 | A |
| 5544347 | Yanai et al. | Aug 1996 | A |
| 5546536 | Davis et al. | Aug 1996 | A |
| 5555404 | Torbjornsen et al. | Sep 1996 | A |
| 5559957 | Balk | Sep 1996 | A |
| 5559991 | Kanfi | Sep 1996 | A |
| 5604862 | Midgely et al. | Feb 1997 | A |
| 5615392 | Harrison et al. | Mar 1997 | A |
| 5619644 | Crockett et al. | Apr 1997 | A |
| 5638509 | Dunphy et al. | Jun 1997 | A |
| 5642496 | Kanfi | Jun 1997 | A |
| 5673381 | Huai et al. | Sep 1997 | A |
| 5677900 | Nishida et al. | Oct 1997 | A |
| 5682513 | Candelaria et al. | Oct 1997 | A |
| 5687343 | Fecteau et al. | Nov 1997 | A |
| 5689706 | Rao et al. | Nov 1997 | A |
| 5699361 | Ding et al. | Dec 1997 | A |
| 5719786 | Nelson et al. | Feb 1998 | A |
| 5720026 | Uemura et al. | Feb 1998 | A |
| 5729743 | Squibb | Mar 1998 | A |
| 5737747 | Vishlitsky et al. | Apr 1998 | A |
| 5742792 | Yanai et al. | Apr 1998 | A |
| 5751997 | Kullick et al. | May 1998 | A |
| 5758359 | Saxon | May 1998 | A |
| 5761677 | Senator et al. | Jun 1998 | A |
| 5761734 | Pfeffer et al. | Jun 1998 | A |
| 5764972 | Crouse et al. | Jun 1998 | A |
| 5765173 | Cane et al. | Jun 1998 | A |
| 5778395 | Whiting et al. | Jul 1998 | A |
| 5790114 | Geaghan et al. | Aug 1998 | A |
| 5790828 | Jost | Aug 1998 | A |
| 5805920 | Sprenkle et al. | Sep 1998 | A |
| 5812398 | Nielsen | Sep 1998 | A |
| 5813009 | Johnson et al. | Sep 1998 | A |
| 5813017 | Morris | Sep 1998 | A |
| 5819292 | Hitz et al. | Oct 1998 | A |
| 5829046 | Tzelnic et al. | Oct 1998 | A |
| 5835953 | Ohran | Nov 1998 | A |
| 5875478 | Blumenau | Feb 1999 | A |
| 5875481 | Ashton et al. | Feb 1999 | A |
| 5878408 | Van Huben et al. | Mar 1999 | A |
| 5887134 | Ebrahim | Mar 1999 | A |
| 5901327 | Ofek | May 1999 | A |
| 5907621 | Bachman et al. | May 1999 | A |
| 5907672 | Matze et al. | May 1999 | A |
| 5924102 | Perks | Jul 1999 | A |
| 5926836 | Blumenau | Jul 1999 | A |
| 5933104 | Kimura | Aug 1999 | A |
| 5933601 | Fanshier et al. | Aug 1999 | A |
| 5938135 | Sasaki et al. | Aug 1999 | A |
| 5950205 | Aviani, Jr. | Sep 1999 | A |
| 5956519 | Wise et al. | Sep 1999 | A |
| 5958005 | Thorne et al. | Sep 1999 | A |
| 5970233 | Liu et al. | Oct 1999 | A |
| 5970255 | Tran et al. | Oct 1999 | A |
| 5974563 | Beeler, Jr. | Oct 1999 | A |
| 5987478 | See et al. | Nov 1999 | A |
| 5991779 | Bejar | Nov 1999 | A |
| 5995091 | Near et al. | Nov 1999 | A |
| 6003089 | Shaffer et al. | Dec 1999 | A |
| 6009274 | Fletcher et al. | Dec 1999 | A |
| 6012090 | Chung et al. | Jan 2000 | A |
| 6021415 | Cannon et al. | Feb 2000 | A |
| 6021475 | Nguyen et al. | Feb 2000 | A |
| 6023710 | Steiner et al. | Feb 2000 | A |
| 6026414 | Anglin | Feb 2000 | A |
| 6049889 | Steely, Jr. et al. | Apr 2000 | A |
| 6052735 | Ulrich et al. | Apr 2000 | A |
| 6061692 | Thomas et al. | May 2000 | A |
| 6072490 | Bates et al. | Jun 2000 | A |
| 6076148 | Kedem et al. | Jun 2000 | A |
| 6094416 | Ying | Jul 2000 | A |
| 6105129 | Meier et al. | Aug 2000 | A |
| 6112239 | Kenner et al. | Aug 2000 | A |
| 6122668 | Teng et al. | Sep 2000 | A |
| 6131095 | Low et al. | Oct 2000 | A |
| 6131148 | West et al. | Oct 2000 | A |
| 6131190 | Sidwell | Oct 2000 | A |
| 6137864 | Yaker | Oct 2000 | A |
| 6148377 | Carter et al. | Nov 2000 | A |
| 6148412 | Cannon et al. | Nov 2000 | A |
| 6154787 | Urevig et al. | Nov 2000 | A |
| 6154852 | Amundson et al. | Nov 2000 | A |
| 6158044 | Tibbetts | Dec 2000 | A |
| 6161111 | Mutalik et al. | Dec 2000 | A |
| 6163856 | Dion et al. | Dec 2000 | A |
| 6167402 | Yeager | Dec 2000 | A |
| 6175829 | Li et al. | Jan 2001 | B1 |
| 6195695 | Cheston et al. | Feb 2001 | B1 |
| 6205450 | Kanome et al. | Mar 2001 | B1 |
| 6212512 | Barney et al. | Apr 2001 | B1 |
| 6212521 | Minami et al. | Apr 2001 | B1 |
| 6230164 | Rikieta et al. | May 2001 | B1 |
| 6260069 | Anglin | Jul 2001 | B1 |
| 6269431 | Dunham | Jul 2001 | B1 |
| 6275953 | Vahalia et al. | Aug 2001 | B1 |
| 6279078 | Sicola et al. | Aug 2001 | B1 |
| 6292783 | Rohler | Sep 2001 | B1 |
| 6301592 | Aoyama et al. | Oct 2001 | B1 |
| 6304880 | Kishi | Oct 2001 | B1 |
| 6311193 | Sekido et al. | Oct 2001 | B1 |
| 6324581 | Xu et al. | Nov 2001 | B1 |
| 6328766 | Long | Dec 2001 | B1 |
| 6330570 | Crighton | Dec 2001 | B1 |
| 6330642 | Carteau | Dec 2001 | B1 |
| 6343324 | Hubis et al. | Jan 2002 | B1 |
| 6350199 | Williams et al. | Feb 2002 | B1 |
| RE37601 | Eastridge et al. | Mar 2002 | E |
| 6353878 | Dunham | Mar 2002 | B1 |
| 6356801 | Goodman et al. | Mar 2002 | B1 |
| 6363464 | Mangione | Mar 2002 | B1 |
| 6366986 | St. Pierre et al. | Apr 2002 | B1 |
| 6366988 | Skiba et al. | Apr 2002 | B1 |
| 6374336 | Peters et al. | Apr 2002 | B1 |
| 6374363 | Wu et al. | Apr 2002 | B1 |
| 6389432 | Pothapragada et al. | May 2002 | B1 |
| 6397308 | Ofek et al. | May 2002 | B1 |
| 6418478 | Ignatius et al. | Jul 2002 | B1 |
| 6421711 | Blumenau et al. | Jul 2002 | B1 |
| 6434681 | Amangau | Aug 2002 | B1 |
| 6473775 | Kusters et al. | Oct 2002 | B1 |
| 6487561 | Ofek et al. | Nov 2002 | B1 |
| 6487644 | Huebsch et al. | Nov 2002 | B1 |
| 6487645 | Clark et al. | Nov 2002 | B1 |
| 6502205 | Yanai et al. | Dec 2002 | B1 |
| 6519679 | Devireddy et al. | Feb 2003 | B2 |
| 6538669 | Lagueux, Jr. et al. | Mar 2003 | B1 |
| 6539462 | Mikkelsen et al. | Mar 2003 | B1 |
| 6542909 | Tamer et al. | Apr 2003 | B1 |
| 6542972 | Ignatius et al. | Apr 2003 | B2 |
| 6557089 | Reed et al. | Apr 2003 | B1 |
| 6564228 | O'Connor | May 2003 | B1 |
| 6581143 | Gagne et al. | Jun 2003 | B2 |
| 6594744 | Humlicek et al. | Jul 2003 | B1 |
| 6604118 | Kleinman et al. | Aug 2003 | B2 |
| 6604149 | Deo et al. | Aug 2003 | B1 |
| 6606690 | Padovano | Aug 2003 | B2 |
| 6615223 | Shih et al. | Sep 2003 | B1 |
| 6631477 | LeCrone et al. | Oct 2003 | B1 |
| 6631493 | Ottesen et al. | Oct 2003 | B2 |
| 6643671 | Milillo et al. | Nov 2003 | B2 |
| 6647396 | Parnell et al. | Nov 2003 | B2 |
| 6647473 | Golds et al. | Nov 2003 | B1 |
| 6651075 | Kusters et al. | Nov 2003 | B1 |
| 6654825 | Clapp et al. | Nov 2003 | B2 |
| 6658436 | Oshinsky et al. | Dec 2003 | B2 |
| 6658526 | Nguyen et al. | Dec 2003 | B2 |
| 6662198 | Satyanarayanan et al. | Dec 2003 | B2 |
| 6665815 | Goldstein et al. | Dec 2003 | B1 |
| 6681230 | Blott et al. | Jan 2004 | B1 |
| 6721767 | De Meno et al. | Apr 2004 | B2 |
| 6728733 | Tokui | Apr 2004 | B2 |
| 6728736 | Hostetter et al. | Apr 2004 | B2 |
| 6732124 | Koseki et al. | May 2004 | B1 |
| 6732125 | Autrey et al. | May 2004 | B1 |
| 6742092 | Huebsch et al. | May 2004 | B1 |
| 6748504 | Sawdon et al. | Jun 2004 | B2 |
| 6751635 | Chen et al. | Jun 2004 | B1 |
| 6757794 | Cabrera et al. | Jun 2004 | B2 |
| 6760723 | Oshinsky et al. | Jul 2004 | B2 |
| 6763351 | Subramaniam et al. | Jul 2004 | B1 |
| 6789161 | Blendermann et al. | Sep 2004 | B1 |
| 6792518 | Armangau et al. | Sep 2004 | B2 |
| 6799258 | Linde | Sep 2004 | B1 |
| 6836779 | Poulin | Dec 2004 | B2 |
| 6871163 | Hiller et al. | Mar 2005 | B2 |
| 6871271 | Ohran et al. | Mar 2005 | B2 |
| 6877016 | Hart et al. | Apr 2005 | B1 |
| 6880051 | Timpanaro-Perrotta | Apr 2005 | B2 |
| 6886020 | Zahavi et al. | Apr 2005 | B1 |
| 6892211 | Hitz et al. | May 2005 | B2 |
| 6898688 | Martin et al. | May 2005 | B2 |
| 6912482 | Kaiser | Jun 2005 | B2 |
| 6920537 | Ofek et al. | Jul 2005 | B2 |
| 6925512 | Louzoun et al. | Aug 2005 | B2 |
| 6938135 | Kekre et al. | Aug 2005 | B1 |
| 6938180 | Dysert et al. | Aug 2005 | B1 |
| 6941393 | Secatch | Sep 2005 | B2 |
| 6944796 | Joshi et al. | Sep 2005 | B2 |
| 6948038 | Berkowitz et al. | Sep 2005 | B2 |
| 6948089 | Fujibayashi | Sep 2005 | B2 |
| 6952705 | Knoblock et al. | Oct 2005 | B2 |
| 6952758 | Chron et al. | Oct 2005 | B2 |
| 6954834 | Slater et al. | Oct 2005 | B2 |
| 6957362 | Armangau | Oct 2005 | B2 |
| 6968351 | Butterworth | Nov 2005 | B2 |
| 6973553 | Archibald, Jr. et al. | Dec 2005 | B1 |
| 6978265 | Schumacher | Dec 2005 | B2 |
| 6981114 | Wu et al. | Dec 2005 | B1 |
| 6981177 | Beattie | Dec 2005 | B2 |
| 6983351 | Gibble et al. | Jan 2006 | B2 |
| 6993539 | Federwisch et al. | Jan 2006 | B2 |
| 7003519 | Biettron et al. | Feb 2006 | B1 |
| 7003641 | Prahlad et al. | Feb 2006 | B2 |
| 7032131 | Lubbers et al. | Apr 2006 | B2 |
| 7035880 | Crescenti et al. | Apr 2006 | B1 |
| 7039661 | Ranade | May 2006 | B1 |
| 7051050 | Chen et al. | May 2006 | B2 |
| 7062761 | Slavin et al. | Jun 2006 | B2 |
| 7065538 | Aronoff et al. | Jun 2006 | B2 |
| 7072915 | Kaczmarski et al. | Jul 2006 | B2 |
| 7082441 | Zahavi et al. | Jul 2006 | B1 |
| 7085787 | Beier et al. | Aug 2006 | B2 |
| 7085904 | Mizuno et al. | Aug 2006 | B2 |
| 7086787 | Beier et al. | Aug 2006 | B2 |
| 7096315 | Takeda et al. | Aug 2006 | B2 |
| 7100089 | Phelps | Aug 2006 | B1 |
| 7103731 | Gibble et al. | Sep 2006 | B2 |
| 7103740 | Colgrove et al. | Sep 2006 | B1 |
| 7107298 | Prahlad et al. | Sep 2006 | B2 |
| 7107395 | Ofek et al. | Sep 2006 | B1 |
| 7111026 | Sato | Sep 2006 | B2 |
| 7120757 | Tsuge | Oct 2006 | B2 |
| 7130860 | Pachet | Oct 2006 | B2 |
| 7130970 | Devassy et al. | Oct 2006 | B2 |
| 7139887 | Colgrove et al. | Nov 2006 | B2 |
| 7139932 | Watanabe | Nov 2006 | B2 |
| 7155465 | Lee et al. | Dec 2006 | B2 |
| 7155633 | Tuma et al. | Dec 2006 | B2 |
| 7165079 | Chen et al. | Jan 2007 | B1 |
| 7174352 | Kleinman et al. | Feb 2007 | B2 |
| 7181477 | Saika et al. | Feb 2007 | B2 |
| 7188292 | Cordina et al. | Mar 2007 | B2 |
| 7191198 | Asano et al. | Mar 2007 | B2 |
| 7194454 | Hansen et al. | Mar 2007 | B2 |
| 7197665 | Goldstein et al. | Mar 2007 | B2 |
| 7203807 | Urabe et al. | Apr 2007 | B2 |
| 7209972 | Ignatius et al. | Apr 2007 | B1 |
| 7225204 | Manley et al. | May 2007 | B2 |
| 7225208 | Midgley et al. | May 2007 | B2 |
| 7225210 | Guthrie, II | May 2007 | B2 |
| 7228456 | Lecrone et al. | Jun 2007 | B2 |
| 7231544 | Tan et al. | Jun 2007 | B2 |
| 7234115 | Sprauve et al. | Jun 2007 | B1 |
| 7237075 | Welsh et al. | Jun 2007 | B2 |
| 7246140 | Therrien et al. | Jul 2007 | B2 |
| 7246207 | Kottomtharayil et al. | Jul 2007 | B2 |
| 7251713 | Zhang | Jul 2007 | B1 |
| 7257689 | Baird | Aug 2007 | B1 |
| 7202606 | Borthakur et al. | Sep 2007 | B2 |
| 7269612 | Devarakonda et al. | Sep 2007 | B2 |
| 7269641 | Powers et al. | Sep 2007 | B2 |
| 7272606 | Borthakur et al. | Sep 2007 | B2 |
| 7275138 | Saika | Sep 2007 | B2 |
| 7275177 | Amangau et al. | Sep 2007 | B2 |
| 7275277 | Moskovich et al. | Oct 2007 | B2 |
| 7278142 | Bandhole et al. | Oct 2007 | B2 |
| 7284104 | Wu et al. | Oct 2007 | B1 |
| 7287047 | Kavuri | Oct 2007 | B2 |
| 7293133 | Colgrove et al. | Nov 2007 | B1 |
| 7296125 | Ohran | Nov 2007 | B2 |
| 7315923 | Retnamma et al. | Jan 2008 | B2 |
| 7330997 | Odom | Feb 2008 | B1 |
| 7343356 | Prahlad et al. | Mar 2008 | B2 |
| 7343365 | Farnham et al. | Mar 2008 | B2 |
| 7343453 | Prahlad et al. | Mar 2008 | B2 |
| 7343459 | Prahlad et al. | Mar 2008 | B2 |
| 7346623 | Prahlad et al. | Mar 2008 | B2 |
| 7346751 | Prahlad et al. | Mar 2008 | B2 |
| 7356657 | Mikami | Apr 2008 | B2 |
| 7359917 | Winter et al. | Apr 2008 | B2 |
| 7370232 | Safford | May 2008 | B2 |
| 7373364 | Chapman | May 2008 | B1 |
| 7380072 | Kottomtharayil et al. | May 2008 | B2 |
| 7383538 | Bates et al. | Jun 2008 | B2 |
| 7389311 | Crescenti et al. | Jun 2008 | B1 |
| 7392360 | Aharoni et al. | Jun 2008 | B1 |
| 7395282 | Crescenti et al. | Jul 2008 | B1 |
| 7395387 | Berkowitz et al. | Jul 2008 | B2 |
| 7409509 | Devassy et al. | Aug 2008 | B2 |
| 7412583 | Burton et al. | Aug 2008 | B2 |
| 7415488 | Muth et al. | Aug 2008 | B1 |
| 7421554 | Colgrove et al. | Sep 2008 | B2 |
| 7430587 | Malone et al. | Sep 2008 | B2 |
| 7433301 | Akahane et al. | Oct 2008 | B2 |
| 7440982 | Lu et al. | Oct 2008 | B2 |
| 7454569 | Kavuri et al. | Nov 2008 | B2 |
| 7457982 | Rajan et al. | Nov 2008 | B2 |
| 7467167 | Patterson | Dec 2008 | B2 |
| 7467267 | Mayock | Dec 2008 | B1 |
| 7472238 | Gokhale | Dec 2008 | B1 |
| 7475284 | Koike | Jan 2009 | B2 |
| 7484054 | Kottomtharayil et al. | Jan 2009 | B2 |
| 7490207 | Amarendran | Feb 2009 | B2 |
| 7496589 | Jain et al. | Feb 2009 | B1 |
| 7496690 | Beverly et al. | Feb 2009 | B2 |
| 7500053 | Kavuri et al. | Mar 2009 | B1 |
| 7500150 | Sharma et al. | Mar 2009 | B2 |
| 7509316 | Greenblatt et al. | Mar 2009 | B2 |
| 7512601 | Cucerzan et al. | Mar 2009 | B2 |
| 7516088 | Johnson et al. | Apr 2009 | B2 |
| 7519726 | Palliyll et al. | Apr 2009 | B2 |
| 7523276 | Shankar | Apr 2009 | B1 |
| 7523483 | Dogan | Apr 2009 | B2 |
| 7529748 | Wen et al. | May 2009 | B2 |
| 7529782 | Prahlad et al. | May 2009 | B2 |
| 7529898 | Nguyen et al. | May 2009 | B2 |
| 7532340 | Koppich et al. | May 2009 | B2 |
| 7536291 | Vijayan Retnamma et al. | May 2009 | B1 |
| 7539707 | Prahlad et al. | May 2009 | B2 |
| 7539835 | Kaiser | May 2009 | B2 |
| 7543125 | Gokhale | Jun 2009 | B2 |
| 7546324 | Prahlad et al. | Jun 2009 | B2 |
| 7565572 | Yamasaki | Jul 2009 | B2 |
| 7567991 | Armangau et al. | Jul 2009 | B2 |
| 7568080 | Prahlad et al. | Jul 2009 | B2 |
| 7577806 | Rowan | Aug 2009 | B2 |
| 7581077 | Ignatius et al. | Aug 2009 | B2 |
| 7587563 | Teterin et al. | Sep 2009 | B1 |
| 7596586 | Gokhale et al. | Sep 2009 | B2 |
| 7606841 | Ranade | Oct 2009 | B1 |
| 7606844 | Kottomtharayil | Oct 2009 | B2 |
| 7606868 | Le et al. | Oct 2009 | B1 |
| 7610387 | Liskov et al. | Oct 2009 | B1 |
| 7613748 | Brockway et al. | Nov 2009 | B2 |
| 7613750 | Valiyaparambil et al. | Nov 2009 | B2 |
| 7617253 | Prahlad et al. | Nov 2009 | B2 |
| 7617262 | Prahlad et al. | Nov 2009 | B2 |
| 7617541 | Plotkin et al. | Nov 2009 | B2 |
| 7620666 | Root et al. | Nov 2009 | B1 |
| 7627598 | Burke | Dec 2009 | B1 |
| 7627617 | Kavuri et al. | Dec 2009 | B2 |
| 7636743 | Erofeev | Dec 2009 | B2 |
| 7651593 | Prahlad et al. | Jan 2010 | B2 |
| 7661028 | Erofeev | Feb 2010 | B2 |
| 7664771 | Kusters et al. | Feb 2010 | B2 |
| 7668798 | Scanlon et al. | Feb 2010 | B2 |
| 7669029 | Mishra et al. | Feb 2010 | B1 |
| 7672979 | Appellof et al. | Mar 2010 | B1 |
| 7685126 | Patel et al. | Mar 2010 | B2 |
| 7689467 | Belanger et al. | Mar 2010 | B1 |
| 7702533 | Barnard et al. | Apr 2010 | B2 |
| 7707184 | Zhang et al. | Apr 2010 | B1 |
| 7716171 | Kryger | May 2010 | B2 |
| 7734578 | Prahlad et al. | Jun 2010 | B2 |
| 7734669 | Kottomtharayil et al. | Jun 2010 | B2 |
| 7734715 | Hyakutake et al. | Jun 2010 | B2 |
| 7739235 | Rousseau et al. | Jun 2010 | B2 |
| 7747579 | Prahlad et al. | Jun 2010 | B2 |
| 7747660 | Rajan et al. | Jun 2010 | B1 |
| 7810067 | Kaelicke et al. | Oct 2010 | B2 |
| 7831553 | Prahlad et al. | Nov 2010 | B2 |
| 7831622 | Prahlad et al. | Nov 2010 | B2 |
| 7840533 | Prahlad et al. | Nov 2010 | B2 |
| 7840537 | Gokhale et al. | Nov 2010 | B2 |
| 7844577 | Becker et al. | Nov 2010 | B2 |
| 7870355 | Erofeev | Jan 2011 | B2 |
| 7870356 | Veeraswamy et al. | Jan 2011 | B1 |
| 7873806 | Prahlad et al. | Jan 2011 | B2 |
| 7930274 | Hwang et al. | Apr 2011 | B2 |
| 7930476 | Castelli et al. | Apr 2011 | B1 |
| 7962455 | Erofeev | Jun 2011 | B2 |
| 7962709 | Agrawal | Jun 2011 | B2 |
| 8024292 | Thompson et al. | Sep 2011 | B2 |
| 8024294 | Kottomtharayil | Sep 2011 | B2 |
| 8046334 | Hwang et al. | Oct 2011 | B2 |
| 8055625 | Prahlad et al. | Nov 2011 | B2 |
| 8060695 | Lee et al. | Nov 2011 | B1 |
| 8121983 | Prahlad et al. | Feb 2012 | B2 |
| 8156086 | Lu et al. | Apr 2012 | B2 |
| 8166263 | Prahlad | Apr 2012 | B2 |
| 8170995 | Prahlad et al. | May 2012 | B2 |
| 8190565 | Prahlad et al. | May 2012 | B2 |
| 8204859 | Ngo | Jun 2012 | B2 |
| 8205049 | Armangau et al. | Jun 2012 | B1 |
| 8219524 | Gokhale | Jul 2012 | B2 |
| 8229954 | Kottomtharayil et al. | Jul 2012 | B2 |
| 8230195 | Amarendran et al. | Jul 2012 | B2 |
| 8245128 | Ahad et al. | Aug 2012 | B1 |
| 8271830 | Erofeev | Sep 2012 | B2 |
| 8285681 | Prahlad et al. | Oct 2012 | B2 |
| 8307177 | Prahlad et al. | Nov 2012 | B2 |
| 8326803 | Stringham | Dec 2012 | B1 |
| 8346727 | Chester et al. | Jan 2013 | B1 |
| 8352422 | Prahlad et al. | Jan 2013 | B2 |
| 8356013 | Fachan et al. | Jan 2013 | B2 |
| 8364652 | Vijayan et al. | Jan 2013 | B2 |
| 8463751 | Kottomtharayil | Jun 2013 | B2 |
| 8489656 | Erofeev | Jul 2013 | B2 |
| 8490088 | Tang | Jul 2013 | B2 |
| 8510271 | Tsaur et al. | Aug 2013 | B1 |
| 8521694 | Natanzon | Aug 2013 | B1 |
| 8578120 | Attarde et al. | Nov 2013 | B2 |
| 8645320 | Prahlad et al. | Feb 2014 | B2 |
| 8656123 | Lee | Feb 2014 | B2 |
| 8719226 | Jiang et al. | May 2014 | B1 |
| 8725694 | Kottomtharayil | May 2014 | B2 |
| 8789208 | Sundaram et al. | Jul 2014 | B1 |
| 8856079 | Subramanian et al. | Oct 2014 | B1 |
| 8868494 | Agrawal | Oct 2014 | B2 |
| 8886595 | Prahlad et al. | Nov 2014 | B2 |
| 8930497 | Holmes et al. | Jan 2015 | B1 |
| 8954446 | Vijayan Retnamma et al. | Feb 2015 | B2 |
| 9002785 | Prahlad et al. | Apr 2015 | B2 |
| 9015121 | Salamon et al. | Apr 2015 | B1 |
| 9020900 | Vijayan Retnamma et al. | Apr 2015 | B2 |
| 9098495 | Gokhale | Aug 2015 | B2 |
| 9128901 | Nickurak et al. | Sep 2015 | B1 |
| 9208160 | Prahlad et al. | Dec 2015 | B2 |
| 9218252 | Revur et al. | Dec 2015 | B1 |
| 9239687 | Vijayan et al. | Jan 2016 | B2 |
| 9239840 | Acharya | Jan 2016 | B1 |
| 9251198 | Mutalik et al. | Feb 2016 | B2 |
| 9298715 | Kumarasamy et al. | Mar 2016 | B2 |
| 9342537 | Kumarasamy et al. | May 2016 | B2 |
| 9405631 | Prahlad et al. | Aug 2016 | B2 |
| 9448731 | Nallathambi et al. | Sep 2016 | B2 |
| 9471578 | Nallathambi et al. | Oct 2016 | B2 |
| 9495251 | Kottomtharayil et al. | Nov 2016 | B2 |
| 9535907 | Stringham | Jan 2017 | B1 |
| 9619172 | Natanzon et al. | Apr 2017 | B1 |
| 9619341 | Prahlad et al. | Apr 2017 | B2 |
| 9632874 | Pawar et al. | Apr 2017 | B2 |
| 9639426 | Pawar et al. | May 2017 | B2 |
| 9648105 | Nallathambi et al. | May 2017 | B2 |
| 9753812 | Pawar et al. | Sep 2017 | B2 |
| 9774672 | Nallathambi et al. | Sep 2017 | B2 |
| 9852026 | Mitkar et al. | Dec 2017 | B2 |
| 9886346 | Kumarasamy et al. | Feb 2018 | B2 |
| 9892123 | Kottomtharayil et al. | Feb 2018 | B2 |
| 9898371 | Kumarasamy et al. | Feb 2018 | B2 |
| 9921920 | Nallathambi et al. | Mar 2018 | B2 |
| 9928002 | Kumarasamy et al. | Mar 2018 | B2 |
| 9928146 | Nallathambi et al. | Mar 2018 | B2 |
| 9965306 | Natanzon et al. | May 2018 | B1 |
| 9996428 | Nallathambi et al. | Jun 2018 | B2 |
| 10042716 | Nallathambi et al. | Aug 2018 | B2 |
| 10044803 | Nallathambi et al. | Aug 2018 | B2 |
| 10223365 | Kottomtharayil et al. | Mar 2019 | B2 |
| 10228962 | Dornemann et al. | Mar 2019 | B2 |
| 10250679 | Natanzon et al. | Apr 2019 | B1 |
| 10419536 | Nallathambi et al. | Sep 2019 | B2 |
| 10503753 | Mitkar et al. | Dec 2019 | B2 |
| 10521308 | Nallathambi et al. | Dec 2019 | B2 |
| 10572444 | Kottomtharayil et al. | Feb 2020 | B2 |
| 10628266 | Nallathambi et al. | Apr 2020 | B2 |
| 10671484 | Pawar et al. | Jun 2020 | B2 |
| 10698632 | Kumarasamy et al. | Jun 2020 | B2 |
| 10732885 | Gutta et al. | Aug 2020 | B2 |
| 10740022 | Gutta et al. | Aug 2020 | B2 |
| 10798166 | Nallathambi et al. | Oct 2020 | B2 |
| 10853176 | Kumarasamy et al. | Dec 2020 | B2 |
| 10942894 | Kottomtharayil et al. | Mar 2021 | B2 |
| 20010027457 | Yee | Oct 2001 | A1 |
| 20010029512 | Oshinsky et al. | Oct 2001 | A1 |
| 20010029517 | De Meno et al. | Oct 2001 | A1 |
| 20010032172 | Moulinet et al. | Oct 2001 | A1 |
| 20010042222 | Kedem et al. | Nov 2001 | A1 |
| 20010044807 | Kleiman et al. | Nov 2001 | A1 |
| 20010044834 | Bradshaw et al. | Nov 2001 | A1 |
| 20020002557 | Straube et al. | Jan 2002 | A1 |
| 20020004883 | Nguyen et al. | Jan 2002 | A1 |
| 20020023051 | Kunzle et al. | Feb 2002 | A1 |
| 20020040376 | Yamanaka et al. | Apr 2002 | A1 |
| 20020042869 | Tate et al. | Apr 2002 | A1 |
| 20020049626 | Mathias et al. | Apr 2002 | A1 |
| 20020049718 | Kleiman et al. | Apr 2002 | A1 |
| 20020049738 | Epstein | Apr 2002 | A1 |
| 20020049778 | Bell et al. | Apr 2002 | A1 |
| 20020062230 | Morag et al. | May 2002 | A1 |
| 20020069324 | Gerasimov et al. | Jun 2002 | A1 |
| 20020073070 | Morita et al. | Jun 2002 | A1 |
| 20020083055 | Pachet et al. | Jun 2002 | A1 |
| 20020103848 | Giacomini et al. | Aug 2002 | A1 |
| 20020107877 | Whiting et al. | Aug 2002 | A1 |
| 20020112134 | Ohran et al. | Aug 2002 | A1 |
| 20020133511 | Hostetter | Sep 2002 | A1 |
| 20020133512 | Milillo et al. | Sep 2002 | A1 |
| 20020143903 | Uratani et al. | Oct 2002 | A1 |
| 20020152381 | Kuriya et al. | Oct 2002 | A1 |
| 20020161753 | Inaba et al. | Oct 2002 | A1 |
| 20020174107 | Poulin | Nov 2002 | A1 |
| 20020174416 | Bates et al. | Nov 2002 | A1 |
| 20030009431 | Souder et al. | Jan 2003 | A1 |
| 20030018657 | Monday | Jan 2003 | A1 |
| 20030028736 | Berkowitz et al. | Feb 2003 | A1 |
| 20030046270 | Leung et al. | Mar 2003 | A1 |
| 20030061456 | Ofek et al. | Mar 2003 | A1 |
| 20030061491 | Jaskiewicz et al. | Mar 2003 | A1 |
| 20030097296 | Putt | May 2003 | A1 |
| 20030131278 | Fujibayashi | Jul 2003 | A1 |
| 20030135783 | Martin et al. | Jul 2003 | A1 |
| 20030140070 | Kaczmarski et al. | Jul 2003 | A1 |
| 20030158834 | Sawdon et al. | Aug 2003 | A1 |
| 20030167380 | Green et al. | Sep 2003 | A1 |
| 20030177149 | Coombs | Sep 2003 | A1 |
| 20030177321 | Watanabe | Sep 2003 | A1 |
| 20030182313 | Federwisch et al. | Sep 2003 | A1 |
| 20030187847 | Lubbers et al. | Oct 2003 | A1 |
| 20030225800 | Kavuri | Dec 2003 | A1 |
| 20040002934 | Taulbee et al. | Jan 2004 | A1 |
| 20040010487 | Prahlad et al. | Jan 2004 | A1 |
| 20040015468 | Beier et al. | Jan 2004 | A1 |
| 20040039679 | Norton et al. | Feb 2004 | A1 |
| 20040098425 | Wiss et al. | May 2004 | A1 |
| 20040107199 | Dairymple, III et al. | Jun 2004 | A1 |
| 20040117572 | Welsh et al. | Jun 2004 | A1 |
| 20040139128 | Becker et al. | Jul 2004 | A1 |
| 20040143642 | Beckmann et al. | Jul 2004 | A1 |
| 20040148376 | Rangan et al. | Jul 2004 | A1 |
| 20040167972 | Demmon | Aug 2004 | A1 |
| 20040193953 | Callahan et al. | Sep 2004 | A1 |
| 20040205206 | Naik et al. | Oct 2004 | A1 |
| 20040230829 | Dogan et al. | Nov 2004 | A1 |
| 20040236958 | Teicher et al. | Nov 2004 | A1 |
| 20040249883 | Srinivasan et al. | Dec 2004 | A1 |
| 20040250033 | Prahlad et al. | Dec 2004 | A1 |
| 20040254919 | Giuseppini | Dec 2004 | A1 |
| 20040260678 | Verbowski et al. | Dec 2004 | A1 |
| 20040267835 | Zwilling et al. | Dec 2004 | A1 |
| 20040267836 | Amangau et al. | Dec 2004 | A1 |
| 20050005070 | Lam | Jan 2005 | A1 |
| 20050027748 | Kisley | Feb 2005 | A1 |
| 20050027892 | McCabe et al. | Feb 2005 | A1 |
| 20050033800 | Kavuri et al. | Feb 2005 | A1 |
| 20050033878 | Pangal et al. | Feb 2005 | A1 |
| 20050060598 | Klotz et al. | Mar 2005 | A1 |
| 20050066118 | Perry et al. | Mar 2005 | A1 |
| 20050066222 | Rowan et al. | Mar 2005 | A1 |
| 20050066225 | Rowan et al. | Mar 2005 | A1 |
| 20050080928 | Beverly et al. | Apr 2005 | A1 |
| 20050086241 | Ram et al. | Apr 2005 | A1 |
| 20050108292 | Burton et al. | May 2005 | A1 |
| 20050138306 | Panchbudhe et al. | Jun 2005 | A1 |
| 20050144202 | Chen | Jun 2005 | A1 |
| 20050187982 | Sato | Aug 2005 | A1 |
| 20050187992 | Prahlad et al. | Aug 2005 | A1 |
| 20050188254 | Urabe et al. | Aug 2005 | A1 |
| 20050193026 | Prahlad et al. | Sep 2005 | A1 |
| 20050198083 | Saika et al. | Sep 2005 | A1 |
| 20050246376 | Lu et al. | Nov 2005 | A1 |
| 20050246397 | Edwards et al. | Nov 2005 | A1 |
| 20050246510 | Retnamma et al. | Nov 2005 | A1 |
| 20060005048 | Osaki et al. | Jan 2006 | A1 |
| 20060010154 | Prahlad et al. | Jan 2006 | A1 |
| 20060010227 | Atluri | Jan 2006 | A1 |
| 20060020616 | Hardy et al. | Jan 2006 | A1 |
| 20060034454 | Damgaard et al. | Feb 2006 | A1 |
| 20060047805 | Byrd et al. | Mar 2006 | A1 |
| 20060120401 | Harada et al. | Jun 2006 | A1 |
| 20060129537 | Torii et al. | Jun 2006 | A1 |
| 20060136685 | Griv et al. | Jun 2006 | A1 |
| 20060136771 | Watanabe | Jun 2006 | A1 |
| 20060179261 | Rajan | Aug 2006 | A1 |
| 20060224846 | Amarendran et al. | Oct 2006 | A1 |
| 20060242371 | Shono et al. | Oct 2006 | A1 |
| 20060242489 | Brockway et al. | Oct 2006 | A1 |
| 20070005915 | Thompson et al. | Jan 2007 | A1 |
| 20070006018 | Thompson et al. | Jan 2007 | A1 |
| 20070043956 | El Far et al. | Feb 2007 | A1 |
| 20070067263 | Husain et al. | Mar 2007 | A1 |
| 20070094467 | Yamasaki | Apr 2007 | A1 |
| 20070100867 | Celik et al. | May 2007 | A1 |
| 20070112897 | Asano et al. | May 2007 | A1 |
| 20070113006 | Elliott et al. | May 2007 | A1 |
| 20070115738 | Emaru | May 2007 | A1 |
| 20070124347 | Vivian et al. | May 2007 | A1 |
| 20070124348 | Claborn et al. | May 2007 | A1 |
| 20070143371 | Kottomtharayil | Jun 2007 | A1 |
| 20070143756 | Gokhale | Jun 2007 | A1 |
| 20070174569 | Schnapp et al. | Jul 2007 | A1 |
| 20070179990 | Zimran et al. | Aug 2007 | A1 |
| 20070183224 | Erofeev | Aug 2007 | A1 |
| 20070185937 | Prahlad et al. | Aug 2007 | A1 |
| 20070185938 | Prahlad et al. | Aug 2007 | A1 |
| 20070185939 | Prahlad et al. | Aug 2007 | A1 |
| 20070185940 | Prahlad et al. | Aug 2007 | A1 |
| 20070186068 | Agrawal | Aug 2007 | A1 |
| 20070198602 | Ngo et al. | Aug 2007 | A1 |
| 20070226438 | Erofeev | Sep 2007 | A1 |
| 20070244571 | Wilson et al. | Oct 2007 | A1 |
| 20070283111 | Berkowitz et al. | Dec 2007 | A1 |
| 20070288536 | Sen et al. | Dec 2007 | A1 |
| 20070288711 | Chen et al. | Dec 2007 | A1 |
| 20080016293 | Saika | Jan 2008 | A1 |
| 20080028009 | Ngo | Jan 2008 | A1 |
| 20080059515 | Fulton | Mar 2008 | A1 |
| 20080103916 | Camarador et al. | May 2008 | A1 |
| 20080183775 | Prahlad et al. | Jul 2008 | A1 |
| 20080209146 | Imazu et al. | Aug 2008 | A1 |
| 20080229037 | Bunte et al. | Sep 2008 | A1 |
| 20080243914 | Prahlad et al. | Oct 2008 | A1 |
| 20080243953 | Wu et al. | Oct 2008 | A1 |
| 20080243957 | Prahlad et al. | Oct 2008 | A1 |
| 20080243958 | Prahlad et al. | Oct 2008 | A1 |
| 20080244177 | Crescenti et al. | Oct 2008 | A1 |
| 20080244205 | Amano et al. | Oct 2008 | A1 |
| 20080306954 | Hornqvist | Dec 2008 | A1 |
| 20090044046 | Yamasaki | Feb 2009 | A1 |
| 20090070330 | Hwang et al. | Mar 2009 | A1 |
| 20090150462 | McClanahan et al. | Jun 2009 | A1 |
| 20090182963 | Prahlad et al. | Jul 2009 | A1 |
| 20090187944 | White et al. | Jul 2009 | A1 |
| 20090216816 | Basler et al. | Aug 2009 | A1 |
| 20090319534 | Gokhale | Dec 2009 | A1 |
| 20090319582 | Simek et al. | Dec 2009 | A1 |
| 20090319585 | Gokhale | Dec 2009 | A1 |
| 20100005259 | Prahlad | Jan 2010 | A1 |
| 20100011178 | Feathergill et al. | Jan 2010 | A1 |
| 20100036931 | Certain et al. | Feb 2010 | A1 |
| 20100049753 | Prahlad et al. | Feb 2010 | A1 |
| 20100070726 | Ngo et al. | Mar 2010 | A1 |
| 20100094808 | Erofeev | Apr 2010 | A1 |
| 20100100529 | Erofeev | Apr 2010 | A1 |
| 20100122053 | Prahlad et al. | May 2010 | A1 |
| 20100131461 | Prahlad et al. | May 2010 | A1 |
| 20100145909 | Ngo | Jun 2010 | A1 |
| 20100153338 | Ngo et al. | Jun 2010 | A1 |
| 20100179941 | Agrawal et al. | Jul 2010 | A1 |
| 20100205150 | Prahlad et al. | Aug 2010 | A1 |
| 20100228919 | Stabrawa et al. | Sep 2010 | A1 |
| 20100250735 | Andersen | Sep 2010 | A1 |
| 20100257142 | Murphy et al. | Oct 2010 | A1 |
| 20100287141 | Prahlad et al. | Nov 2010 | A1 |
| 20100332990 | Prahlad et al. | Dec 2010 | A1 |
| 20110047195 | Le et al. | Feb 2011 | A1 |
| 20110047340 | Olson et al. | Feb 2011 | A1 |
| 20110066599 | Prahlad et al. | Mar 2011 | A1 |
| 20110161299 | Prahlad et al. | Jun 2011 | A1 |
| 20110161300 | Hwang et al. | Jun 2011 | A1 |
| 20110196957 | Ayachitula et al. | Aug 2011 | A1 |
| 20110246416 | Prahlad et al. | Oct 2011 | A1 |
| 20110246429 | Prahlad et al. | Oct 2011 | A1 |
| 20110276594 | Chong et al. | Nov 2011 | A1 |
| 20110282842 | Popovski et al. | Nov 2011 | A1 |
| 20110295804 | Erofeev | Dec 2011 | A1 |
| 20110295806 | Erofeev | Dec 2011 | A1 |
| 20120079221 | Sivasubramanian et al. | Mar 2012 | A1 |
| 20120084523 | Littlefield et al. | Apr 2012 | A1 |
| 20120124012 | Provenzano et al. | May 2012 | A1 |
| 20120131684 | Lynch | May 2012 | A1 |
| 20120150818 | Vijayan Retnamma et al. | Jun 2012 | A1 |
| 20120150826 | Vijayan Retnamma et al. | Jun 2012 | A1 |
| 20120179886 | Prahlad et al. | Jul 2012 | A1 |
| 20120317074 | Ngo | Dec 2012 | A1 |
| 20130006926 | Erofeev | Jan 2013 | A1 |
| 20130006938 | Prahlad et al. | Jan 2013 | A1 |
| 20130007183 | Sorenson et al. | Jan 2013 | A1 |
| 20130054910 | Vaghani et al. | Feb 2013 | A1 |
| 20130103650 | Natanzon et al. | Apr 2013 | A1 |
| 20130144881 | Sitsky et al. | Jun 2013 | A1 |
| 20130198311 | Tamir et al. | Aug 2013 | A1 |
| 20130218840 | Smith et al. | Aug 2013 | A1 |
| 20130262800 | Goodman et al. | Oct 2013 | A1 |
| 20130282953 | Orme et al. | Oct 2013 | A1 |
| 20140201170 | Vijayan et al. | Jul 2014 | A1 |
| 20140281317 | Garman et al. | Sep 2014 | A1 |
| 20150067231 | Sundarrajan et al. | Mar 2015 | A1 |
| 20150212894 | Pawar et al. | Jul 2015 | A1 |
| 20160350391 | Vijayan et al. | Dec 2016 | A1 |
| 20170168903 | Dornemann et al. | Jun 2017 | A1 |
| 20170185488 | Kumarasamy et al. | Jun 2017 | A1 |
| 20170192860 | Vijayan et al. | Jul 2017 | A1 |
| 20170192861 | Vijayan et al. | Jul 2017 | A1 |
| 20170192866 | Vijayan et al. | Jul 2017 | A1 |
| 20170192867 | Vijayan et al. | Jul 2017 | A1 |
| 20170192868 | Vijayan et al. | Jul 2017 | A1 |
| 20170193003 | Vijayan et al. | Jul 2017 | A1 |
| 20170235647 | Kilaru et al. | Aug 2017 | A1 |
| 20170242871 | Kilaru et al. | Aug 2017 | A1 |
| 20180232278 | Kumarasamy et al. | Aug 2018 | A1 |
| 20180373602 | Nallathambi et al. | Dec 2018 | A1 |
| 20190250827 | Gutta et al. | Aug 2019 | A1 |
| 20200021651 | Nallathambi et al. | Jan 2020 | A1 |
| 20200192912 | Mitkar et al. | Jun 2020 | A1 |
| 20200272543 | Nallathambi et al. | Aug 2020 | A1 |
| 20200341644 | Gutta | Oct 2020 | A1 |
| 20200356443 | Pawar et al. | Nov 2020 | A1 |
| 20200379648 | Kumarasamy et al. | Dec 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2006331932 | Dec 2006 | AU |
| 2632935 | Dec 2006 | CA |
| 0259912 | Mar 1988 | EP |
| 0405926 | Jan 1991 | EP |
| 0467546 | Jan 1992 | EP |
| 0774715 | May 1997 | EP |
| 0809184 | Nov 1997 | EP |
| 0862304 | Sep 1998 | EP |
| 0899662 | Mar 1999 | EP |
| 0981090 | Feb 2000 | EP |
| 1174795 | Jan 2002 | EP |
| 1349089 | Jan 2003 | EP |
| 1349088 | Oct 2003 | EP |
| 1579331 | Sep 2005 | EP |
| 1974296 | Oct 2008 | EP |
| 2256952 | Dec 1992 | GB |
| 2411030 | Aug 2005 | GB |
| 05189281 | Jul 1993 | JP |
| 06274605 | Sep 1994 | JP |
| 09016463 | Jan 1997 | JP |
| 11259348 | Sep 1999 | JP |
| 2000-347811 | Dec 2000 | JP |
| WO 1993003549 | Feb 1993 | WO |
| WO 1995013580 | May 1995 | WO |
| WO 199839707 | Sep 1998 | WO |
| WO 1999012098 | Mar 1999 | WO |
| WO 1999014692 | Mar 1999 | WO |
| WO 2002095632 | Nov 2002 | WO |
| WO 2003028183 | Apr 2003 | WO |
| WO 2004034197 | Apr 2004 | WO |
| WO 2005055093 | Jun 2005 | WO |
| WO 2005086032 | Sep 2005 | WO |
| WO 2007053314 | May 2007 | WO |
| WO 2007075587 | Jul 2007 | WO |
| Entry |
|---|
| Prakash et al, “Maximal global snapshot with concurrent initiators,” Proceedings of 1994 6th IEEE Symposium on Parallel and Distributed Processing, Dallas, TX, USA, 1994, pp. 344-351. (Year: 1994). |
| U.S. Appl. No. 15/981,712 (and its file history), filed May 16, 2018, Gutta et al. |
| Armstead et al., “Implementation of a Campus-Wide Distributed Mass Storage Service: The Dream vs. Reality,” IEEE, 1995, pp. 190-199. |
| Arneson, “Development of Omniserver; Mass Storage Systems,” Control Data Corporation, 1990, pp. 88-93. |
| Arneson, “Mass Storage Archiving in Network Environments” IEEE, 1998, pp. 45-50. |
| Ashton, et al., “Two Decades of policy-based storage management for the IBM mainframe computer”, www.research.ibm.com, 19 pages, published Apr. 10, 2003, printed Jan. 3, 2009., www.research.ibm.com, Apr. 10, 2003, pp. 19. |
| Cabrera, et al. “ADSM: A Multi-Platform, Scalable, Back-up and Archive Mass Storage System,” Digest of Papers, Compcon '95, Proceedings of the 40th IEEE Computer Society International Conference, Mar. 5, 1995-Mar. 9, 1995, 9 pages, San Francisco, CA. |
| “Easy snapshot backup and recovery is here.” Copyright date listed 2014. 6 pages. |
| Eitel, “Backup and Storage Management in Distributed Heterogeneous Environments,” IEEE, 1994, pp. 124-126. |
| Gait, “The Optical File Cabinet: A Random-Access File system for Write-Once Optical Disks,” IEEE Computer, vol. 21, No. 6, pp. 11-22 (1988). |
| Gray (#1 of 2, pp. 646-655), Jim; Reuter, Andreas, Transaction Processing: Concepts and Techniques, Morgan Kaufmann Publisher, USA 1994, 1994,11 pages. |
| Gray (#2 of 2, pp. 604-609), Jim; Reuter Andreas, Transaction Processing Concepts and Techniques, Morgan Kaufmann Publisher, USA 1994, pp. 604-609. |
| Harrington, Lisa H., “The RFP Process: How To Hire a Third Party”, Transportation & Distribution, Sep. 1988, vol. 39, Issue 9, in 5 pages. |
| http://en.wikipedia.org/wiki/Naive_Bayes_classifier, printed on Jun. 1, 2010, in 7 pages. |
| IntelliSnap—Advanced Snapshots—NAS iDataAgent. <http://documentation.commvault.com/commvault/v10/article?p=products/nas ndmp/snap . . . > Retrieved Oct. 24, 2014. 14 pages. |
| Jander, “Launching Storage-Area Net,” Data Communications, US, McGraw Hill, NY, vol. 27, No. 4(Mar. 21, 1998), pp. 64-72. |
| Kashyap, et al., “Professional Services Automation: A knowledge Management approach using LSI and Domain specific Ontologies”, FLAIRS-01 Proceedings, 2001, pp. 300-302. |
| Li et al., “iROW: An Efficient Live Snapshot System for Virtual Machine Disk”, ICPADS 2012, Singapore, Dec. 17-19, 2012, pp. 376-383. |
| Lyon J., Design considerations in replicated database systems for disaster protection, COMPCON 1988, Feb. 29, 1988, pp. 428-430. |
| Microsoft Corporation, “Microsoft Exchange Server: Best Practices for Exchange Database Management,” 1998, 26 pages. |
| Microsoft, “How Volume Shadow Copy Service Works”, date listed Mar. 28, 2003. |
| Oltean, “VSS writers and inconsistent shadow copies”, date listed Sep. 1, 2005, http://blogs.msdn.com/b/adioltean/archive/2005/ 08/31/ 458907.aspx., 2 pages. |
| Rosenblum et al., “The Design and Implementation of a Log-Structure File System,” Operating Systems Review SIGOPS, vol. 25, No. 5, New York, US, pp. 1-14 (May 1991). |
| Simpana Intellisnap Snapshot Management Technology: Exponentially Accelerate Data Protection and Recovery. Copyright date listed 1999-2013. 2 pages. |
| Simpana Intellisnap Technology—Making Snaps Work. Copyright date listed 2014. 2 pages. |
| The Oracle8 Replication Manual, Part No. A58245-01; Chapters 1-2; Dec. 1, 1997; obtained from website: http://download-west.oracle.com/docs/cd/A64702_01/doc/server.805/a58245/toc.htm on May 20, 2009, 58 pages. |
| Veritas Software Corporation, “Veritas Volume Manager 3.2, Administrator's Guide,” Aug. 2001, 360 pages. |
| Waldspurger, Carl, et al., I/O Virtualization, Communications of the ACM, vol. 55, No. 1, Jan. 2012, pp. 66-72. |
| Wiesmann M, Database replication techniques: a three parameter classification, Oct. 16, 2000, pp. 206-215. |
| Examiner's Report for Australian Application No. 2003279847, dated Dec. 9, 2008, 4 pages. |
| European Examination Report; Application No. 06848901.2, dated Apr. 1, 2009, pp. 7. |
| Second Examination Report in EU Appl. No. 06 848 901.2-2201 dated Dec. 3, 2010. |
| Examiner's First Report; Application No. 2006331932 dated May 11, 2011 in 2 pages. |
| Canadian Office Action dated Dec. 10, 2009, Application No. CA2544063, 3 pages. |
| Canadian Office Action dated Dec. 29, 2010, Application No. CA2546304, 4 pages. |
| First Office Action in Indian Application No. 3359/DELNP/2006 dated Feb. 11, 2013, 2 pages. |
| Final Office Action for Japanese Application No. 2003531581, dated Mar. 24, 2009, 6 pages. |
| First Office Action for Japanese Application No. 2003531581, dated Jul. 8, 2008, 8 pages. |
| International Preliminary Report on Patentability, PCT Application No. PCT/US2009/066880, dated Jun. 23, 2011, in 9 pages. |
| International Search Report and Written Opinion dated Nov. 13, 2009, PCT/US2007/081681m, 8 pages. |
| International Search Report and Written Opinion issued in PCT Application No. PCT/US2011/030396, dated Jul. 18, 2011, in 20 pages. |
| International Search Report and Written Opinion issued in PCT Application No. PCT/US2011/38436, dated Sep. 21, 2011, in 18 pages. |
| International Search Report from International Application No. PCT/US2006/048273, dated May 15, 2007, 13 pages. |
| Excerpts from Microsoft Computer Dictionary, Microsoft Press, 5th ed., 2002. 5 pages. |
| Freeley, et al., “Integrating Coherency and Recoverability in Distributed Systems”, Department of Computer Science and Engineering, FR-35, University of Washington, Nov. 1994, 13 pages. |
| Veritas NetBackup™, System Administrator's Guide, Window NT Server, Release 3.2, May 1999, 580 pages. |
| Veritas Volume Manager™ 3.1 for Windows 2000, Aug. 2002, 486 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210011805 A1 | Jan 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61805063 | Mar 2013 | US | |
| 61751790 | Jan 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15888592 | Feb 2018 | US |
| Child | 17037277 | US | |
| Parent | 14151650 | Jan 2014 | US |
| Child | 15888592 | US |
