Patent Grant
12056018
Any and all applications, if any, for which a foreign or domestic priority claim is identified in the Application Data Sheet of the present application are hereby incorporated by reference in their entireties under 37 CFR 1.57.
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document and/or the patent disclosure as it appears in the United States Patent and Trademark Office patent file and/or records, but otherwise reserves all copyrights whatsoever.
Businesses 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. A company might back up critical computing systems such as databases, file servers, web servers, virtual machines, and so on as part of a routine schedule. The company may similarly protect computing systems used by 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.
A Recovery Point Objective (RPO) is a maximum targeted period of time that an enterprise is willing to, or aims to, tolerate data loss. Thus, for large transactional databases that experience large numbers of transactions every minute, even a short disruption can be severe if those transactions are lost. Therefore, database owners sometimes require a very aggressive (short, frequent) RPO to better protect their production databases. However, storage management systems in the prior art may be unable to reliably meet the desired RPO due to overload in certain components or data paths that are involved in database backup operations. Thus, a streamlined approach is needed for meeting an aggressive RPO for a production database.
The present inventors devised a framework enables virtually any aggressive Recovery Point Objective (RPO) to be enforced for a production database, without limitation on type of database management system (DBMS) or size of the production database. The framework overcomes technological barriers of the prior art, such as bottlenecks presented by a storage manager computer that traditionally managed database backups. An illustrative data storage management system is enhanced with features for enforcing an RPO for a production database without concurrently and without necessarily generating secondary copies of the production database. The illustrative system includes a storage manager (hosted by a computing device or by a cloud-based compute resource), which, among other features, comprises key management information about the system. To avoid the bottlenecks of the prior art, an illustrative data storage management system does not engage the storage manager computer in storage operations that could impact the database RPO. Certain components are added and enhanced to autonomously capture database transaction logs, which are stored securely and persistently away from the DBMS. In a separate and less frequent operation, and with involvement of the storage manager computer, the illustrative system generates secondary copies which are indexed and tracked by the system. Meanwhile, temporary backup files can be used in restore operations without first being converted into secondary copies.
One of the enhancements of the illustrative system is that a first system component (e.g., a database data agent) operating at the DBMS host captures database transaction logs that are generated by the DBMS, and packages them into “temporary backup files” in a proprietary backup format. Illustratively, the proprietary backup format includes compression and encryption for added security, as well as proprietary metadata created by the database data agent. The proprietary metadata and the formatting makes the temporary backup files compatible with the illustrative system and reduces processing time at the back end. At least as often as the database RPO interval, the data agent transmits the temporary backup files to another system component (e.g., a media agent) operating at an other computing device (the “secondary storage computing device”), which is configured apart from the DBMS host. The transmission is carried by a proprietary and persistent data pipeline between data agent and media agent, which provides a secure data pathway between the DBMS host and the secondary storage computing device. By using the proprietary and persistent data pipeline, the media agent need not open a data port on demand for receiving data from the data agent, thus boosting security at the secondary storage computing device. This feature is particularly advantageous in configurations where the data pipeline crosses a public data network, such as the Internet. Moreover, the data pipeline can write securely to any target, whether local (e.g., disk) or remote (e.g., cloud storage), and thus enables a variety of system configurations.
The media agent stores the temporary backup files persistently at a specially-configured data storage resource (the “dump repository” or “data repository” or “dump directory”). The “dump repository” is preferably configured as a drive or a folder at the secondary storage computing device. In configurations where the secondary storage computing device is deployed as a compute resource in a cloud computing environment, the “dump repository” is stored persistently in a cloud storage service of the cloud computing environment. The media agent accumulates temporary backup files at its “dump repository” on an ongoing basis, as received via the proprietary and persistent data pipeline. The operations that generate, transmit, and store the temporary backup files occur without involvement of the storage manager, which eliminates the possibility of the storage manager impeding the safeguarding of the transaction logs of the production database.
Periodically, but substantially less frequently than the database RPO interval, the illustrative system performs a so-called “sweep job.” The sweep job generates one or more secondary copies based on the temporary backup files and stores the secondary copies persistently into secondary storage. The sweep job is a data storage job that converts temporary backup files into proper secondary copies that are tracked and indexed in the illustrative system. By way of example, and without limitation, the database RPO interval is one minute, whereas sweep jobs are performed daily. A sweep job involves the storage manager with the temporary backup files for the first time, thus saving substantial processing cycles at the storage manager. The media agent indexes the secondary copies and reports suitable metadata back to the storage manager. Illustratively, the storage manager stores the reported metadata in a management database of the storage manager. The management database (which is distinct from the production database subject to the database RPO) comprises management information about the system, such as the database RPO, preferences for data protection and lifecycle management, metadata from data storage jobs that ran or failed in the system (including sweep jobs), as well as metadata of secondary copies generated by the system, such as the secondary copies of the production database generated in the sweep job. The media agent purges from its “dump repository” the temporary backup files that have been converted into secondary copies, while yet continuing to accumulate new temporary backup files coming in from the database data agent.
The illustrative data storage management system is further enhanced for restoring data to the production database. Accordingly, when a restore is requested, the media agent is enhanced to check its “dump repository” for temporary backup files. In the prior art, a restore operation would retrieve and restore secondary copies from secondary storage. However, according to the disclosed system architecture, the secondary storage computing device (e.g., using the media agent) is enhanced to analyze the “dump repository” to determine whether temporary backup files therein are suitable for the pending restore operation, and if so, use those files in the restore operation. This added feature enables the illustrative system to restore data from any number of temporary backup files, regardless of whether a sweep job has been performed as yet. Because the temporary backup files are persistently and securely stored, they do not detract from the system's ability to restore data as needed. Thus, the temporary backup files need not be converted into secondary copies in order to be used in restore operations.
The disclosed system architecture is suitable for cloud and non-cloud deployments, and combinations thereof, without limitation. Accordingly, any one or more of the following components may be deployed in a traditional non-cloud data center, in a cloud computing environment, and/or in any combination thereof: DBMS and production database; database data agent; media agent; storage for the “dump repository”; secondary storage for secondary copies; file system data agent; and the storage manager.
Detailed descriptions and examples of systems and methods according to one or more illustrative embodiments may be found in the section entitled ENFORCING A RECOVERY POINT OBJECTIVE (RPO) FOR A PRODUCTION DATABASE WITHOUT GENERATING SECONDARY COPIES OF THE PRODUCTION DATABASE, as well as in the section entitled Example Embodiments, and also in
Information Management System Overview
With the increasing importance of protecting and leveraging data, organizations simply cannot risk losing critical data. Moreover, runaway data growth and other modern realities make protecting and managing data increasingly difficult. There is therefore a need for efficient, powerful, and user-friendly solutions for protecting and managing data and for smart and efficient management of data storage. Depending on the size of the organization, there may be many data production sources which are under the purview of tens, hundreds, or even thousands of individuals. In the past, individuals were sometimes responsible for managing and protecting their own data, and a patchwork of hardware and software point solutions may have been used in any given organization. These solutions were often provided by different vendors and had limited or no interoperability. Certain embodiments described herein address these and other shortcomings of prior approaches by implementing scalable, unified, organization-wide information management, including data storage management.
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/publications and patent applications assigned to Commvault Systems, Inc., each of which is hereby incorporated by reference in its entirety herein:
System 100 includes computing devices and computing technologies. For instance, system 100 can include one or more client computing devices 102 and secondary storage computing devices 106, as well as storage manager 140 or a host computing device for it. Computing devices can include, without limitation, one or more: workstations, personal computers, desktop computers, or other types of generally fixed computing systems such as mainframe computers, servers, and minicomputers. Other computing devices can 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. Servers can include mail servers, file servers, database servers, virtual machine servers, and web servers. Any given computing device comprises one or more hardware processors (e.g., CPU and/or single-core or multi-core processors), as well as corresponding non-transitory computer memory (e.g., random-access memory (RAM)) for storing computer programs which are to be executed by the one or more hardware processors. Other computer memory for mass storage of data may be packaged/configured with the computing device (e.g., an internal hard disk) and/or may be external and accessible by the computing device (e.g., network-attached storage, a storage array, etc.). In some cases, a computing device includes cloud computing resources, which may be implemented as virtual machines. For instance, one or more virtual machines may be provided to the organization by a third-party cloud service vendor.
In some embodiments, computing devices can include one or more virtual machine(s) running on a physical host computing device (or “host machine”) 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, both virtual machines operating on the same host machine. A Virtual machine (“VM”) is a software implementation of a computer that does not physically exist and is instead instantiated in an operating system of a physical computer (or host machine) to enable applications to execute within the VM's environment, i.e., a VM emulates a physical computer. AVM includes an operating system and associated virtual resources, such as computer memory and processor(s). A hypervisor operates between the VM and the hardware of the physical host machine and is generally responsible for creating and running the VMs. Hypervisors are also known in the art as virtual machine monitors or a virtual machine managers or “VMMs”, and may be implemented in software, firmware, and/or specialized hardware installed on the host machine. Examples of hypervisors include ESX Server, by VMware, Inc. of Palo Alto, California; Microsoft Virtual Server and Microsoft Windows Server Hyper-V, both by Microsoft Corporation of Redmond, Washington; Sun xVM by Oracle America Inc. of Santa Clara, California; and Xen by Citrix Systems, Santa Clara, California. The hypervisor provides resources to each virtual operating system such as a virtual processor, virtual memory, a virtual network device, and a virtual disk. Each virtual machine has one or more associated virtual disks. The hypervisor typically stores the data of virtual disks in files on the file system of the physical host machine, called virtual machine disk files (“VMDK” in VMware lingo) or virtual hard disk image files (in Microsoft lingo). For example, VMware's ESX Server provides the Virtual Machine File System (VMFS) for the storage of virtual machine disk files. A virtual machine reads data from and writes data to its virtual disk much the way that a physical machine reads data from and writes data to a physical disk. Examples of techniques for implementing information management in a cloud computing environment are described in U.S. Pat. No. 8,285,681. Examples of techniques for implementing information management in a virtualized computing environment are described in U.S. Pat. No. 8,307,177.
Information management system 100 can also include electronic data storage devices, generally used for mass storage of data, including, e.g., primary storage devices 104 and secondary storage devices 108. Storage devices can generally be of any suitable type including, without limitation, disk drives, storage arrays (e.g., storage-area network (SAN) and/or network-attached storage (NAS) technology), semiconductor memory (e.g., solid state storage devices), network attached storage (NAS) devices, tape libraries, or other magnetic, non-tape storage devices, optical media storage devices, combinations of the same, etc. In some embodiments, storage devices form part of a distributed file system. In some cases, storage devices are provided in a cloud storage environment (e.g., a private cloud or one operated by a third-party vendor), whether for primary data or secondary copies or both. Depending on context, the term “information management system” can refer to generally all of the illustrated hardware and software components in
One or more client computing devices 102 may be part of system 100, each client computing device 102 having an operating system and at least one application 110 and one or more accompanying data agents executing thereon; and associated with one or more primary storage devices 104 storing primary data 112. Client computing device(s) 102 and primary storage devices 104 may generally be referred to in some cases as primary storage subsystem 117.
Client Computing Devices, Clients, and Subclients
Typically, a variety of sources in an organization 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, a database server, a transaction server, or the like. In system 100, data generation sources include one or more client computing devices 102. A computing device that has a data agent 142 installed and operating on it is generally referred to as a “client computing device” 102, and may include any type of computing device, without limitation. A client computing device 102 may be associated with one or more users and/or user accounts.
A “client” is a logical component of information management system 100, which may comprise a logical grouping of one or more data agents installed on a client computing device 102. Storage manager 140 recognizes a client as a component of system 100, and in some embodiments, may automatically create a client component the first time a data agent 142 is installed on a client computing device 102. Because data generated by executable component(s) 110 is tracked by the associated data agent 142 so that it may be properly protected in system 100, a client may be said to generate data and to store the generated data to primary storage, such as primary storage device 104. However, the terms “client” and “client computing device” as used herein do not imply that a client computing device 102 is necessarily configured in the client/server sense relative to another computing device such as a mail server, or that a client computing device 102 cannot be a server in its own right. As just a few examples, a client computing device 102 can be and/or include mail servers, file servers, database servers, virtual machine servers, and/or web servers.
Each client computing device 102 may have application(s) 110 executing thereon which generate and manipulate the data that is to be protected from loss and managed in system 100. Applications 110 generally facilitate the operations of an organization, and can include, without limitation, mail server applications (e.g., Microsoft Exchange Server), file system applications, mail client applications (e.g., Microsoft Exchange Client), database applications or database management systems (e.g., SQL, Oracle, SAP, Lotus Notes Database), word processing applications (e.g., Microsoft Word), spreadsheet applications, financial applications, presentation applications, graphics and/or video applications, browser applications, mobile applications, entertainment applications, and so on. Each application 110 may be accompanied by an application-specific data agent 142, though not all data agents 142 are application-specific or associated with only application. A file manager application, e.g., Microsoft Windows Explorer, may be considered an application 110 and may be accompanied by its own data agent 142. Client computing devices 102 can have at least one operating system (e.g., Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-based operating systems, etc.) installed thereon, which may support or host one or more file systems and other applications 110. In some embodiments, a virtual machine that executes on a host client computing device 102 may be considered an application 110 and may be accompanied by a specific data agent 142 (e.g., virtual server data agent). Client computing devices 102 and other components in system 100 can be connected to one another via one or more electronic communication pathways 114. For example, a first communication pathway 114 may communicatively couple client computing device 102 and secondary storage computing device 106; a second communication pathway 114 may communicatively couple storage manager 140 and client computing device 102; and a third communication pathway 114 may communicatively couple storage manager 140 and secondary storage computing device 106, etc. (see, e.g.,
A “subclient” is a logical grouping of all or part of a client's primary data 112. Thus, a subclient is a data source. In general, a subclient may be defined according to how the subclient data is to be protected as a unit in system 100. For example, a subclient may be associated with a certain storage policy. A given client may thus comprise several subclients, each subclient associated with a different storage policy. For example, some files may form a first subclient that requires compression and deduplication and is associated with a first storage policy. Other files of the client may form a second subclient that requires a different retention schedule as well as encryption, and may be associated with a different, second storage policy. As a result, though the primary data may be generated by the same application 110 and may belong to one given client, portions of the data may be assigned to different subclients for distinct treatment by system 100. More detail on subclients is given in regard to storage policies below.
Primary data 112 is generally production data or “live” data generated by the operating system and/or applications 110 executing on client computing device 102. Primary data 112 is generally stored on primary storage device(s) 104 and is organized via a file system operating on the client computing device 102. Thus, 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. Primary data 112 is an initial or first stored body 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 application 110. It can be useful in performing certain tasks to organize primary data 112 into units of different granularities. In general, primary data 112 can include files, directories, file system volumes, data blocks, extents, or any other hierarchies or organizations of data objects. As used herein, a “data object” can refer to (i) 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/or to (ii) a subset of such a file (e.g., a data block, an extent, etc.). Primary data 112 may include structured data (e.g., database files), unstructured data (e.g., documents), and/or semi-structured data. See, e.g.,
It can also be useful in performing certain functions of system 100 to access and modify metadata within primary data 112. Metadata generally includes information about data objects and/or characteristics associated with the data objects. For simplicity herein, it is to be understood that, unless expressly stated otherwise, any reference to primary data 112 generally also includes its associated metadata, but references to metadata generally do not include the primary data. 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), user-supplied tags, 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), geographic location (e.g., GPS coordinates), 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), 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 other similar information related to the data object. In addition to metadata generated by or related to file systems and operating systems, some applications 110 and/or other components of system 100 maintain indices of metadata for data objects, e.g., metadata associated with individual email messages. The use of metadata to perform classification and other functions is described in greater detail below.
Primary storage devices 104 storing primary data 112 may be relatively fast and/or expensive technology (e.g., flash storage, a disk drive, a hard-disk storage array, solid state memory, etc.), typically to support high-performance live production environments. Primary data 112 may be highly changeable and/or may be intended for relatively short term retention (e.g., hours, days, or weeks). According to some embodiments, client computing device 102 can access primary data 112 stored in primary storage device 104 by making conventional file system calls via the operating system. Each client computing device 102 is generally associated with and/or in communication with one or more primary storage devices 104 storing corresponding primary data 112. A client computing device 102 is said to be associated with or in communication with a particular primary storage device 104 if it is capable of one or more of: routing and/or storing data (e.g., primary data 112) to the primary storage device 104, coordinating the routing and/or storing of data to the primary storage device 104, retrieving data from the primary storage device 104, coordinating the retrieval of data from the primary storage device 104, and modifying and/or deleting data in the primary storage device 104. Thus, a client computing device 102 may be said to access data stored in an associated storage device 104. Primary storage device 104 may be dedicated or shared. In some cases, each primary storage device 104 is dedicated to an associated client computing device 102, e.g., a local disk drive. In other cases, one or more primary storage devices 104 can be shared by multiple client computing devices 102, e.g., via a local network, in a cloud storage implementation, etc. As one example, primary storage device 104 can be a storage array shared by a group of client computing devices 102, such as EMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV, NetApp FAS, HP EVA, and HP 3PAR.
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 system 100. For instance, the hosted services may be provided by online service providers. Such service providers can provide social networking services, hosted email services, or hosted productivity applications or other hosted applications such as 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 services users, each hosted service may generate additional data and metadata, which may be managed by 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.
Primary data 112 stored on primary storage devices 104 may be compromised in some cases, such as when an employee deliberately or accidentally deletes or overwrites primary data 112. Or primary storage devices 104 can be damaged, lost, or otherwise corrupted. For recovery and/or regulatory compliance purposes, it is therefore useful to generate and maintain copies of primary data 112. Accordingly, 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 primary data 112 including its associated metadata. The secondary storage computing devices 106 and the secondary storage devices 108 may be referred to as secondary storage subsystem 118.
Secondary copies 116 can help in search and analysis efforts and meet other information management goals as well, such as: restoring data and/or metadata if an original version 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 in the production system and/or in secondary storage; facilitating organization and search of data; improving user access to data files across multiple computing devices and/or hosted services; and implementing data retention and pruning policies. A secondary copy 116 can comprise a separate stored copy of data that is derived from one or more earlier-created stored copies (e.g., derived from primary data 112 or from another secondary copy 116). Secondary copies 116 can include point-in-time data, and may be intended for relatively long-term retention before some or all of the data is moved to other storage or discarded. In some cases, a secondary copy 116 may be in a different storage device than other previously stored copies; and/or may be remote from other previously stored copies. Secondary copies 116 can be stored in the same storage device as primary data 112. For 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. Secondary copies 116 may be stored in relatively slow and/or lower 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 from the native source application format or other format of primary data 112.
Secondary storage computing devices 106 may index secondary copies 116 (e.g., using a media agent 144), enabling users to browse and restore at a later time and further enabling the lifecycle management of the indexed data. After creation of a secondary copy 116 that represents 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 of a particular secondary copy 116. Since an instance of a data object or metadata in primary data 112 may change over time as it is modified by application 110 (or hosted service or the operating system), system 100 may create and manage multiple secondary copies 116 of a particular data object or metadata, each copy 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 primary storage device 104 and the file system, 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 virtual machines, the operating system and other applications 110 of 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. 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 are distinguishable from corresponding primary data 112. First, secondary copies 116 can be stored in a different format from primary data 112 (e.g., backup, archive, or other non-native format). For this or other reasons, secondary copies 116 may not be directly usable by applications 110 or client computing device 102 (e.g., via standard system calls or otherwise) without modification, processing, or other intervention by system 100 which may be referred to as “restore” operations. Secondary copies 116 may have been processed by data agent 142 and/or media agent 144 in the course of being created (e.g., compression, deduplication, encryption, integrity markers, indexing, formatting, application-aware metadata, etc.), and thus secondary copy 116 may represent source primary data 112 without necessarily being exactly identical to the source. Second, secondary copies 116 may be stored on a secondary storage device 108 that is inaccessible to application 110 running on client computing device 102 and/or hosted service. 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 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 system 100 can access only with some human intervention (e.g., tapes located at an offsite storage site).
Using Intermediate Devices for Creating Secondary Copies—Secondary Storage Computing Devices
Creating secondary copies can be challenging when hundreds or thousands of client computing devices 102 continually generate large volumes of primary data 112 to be protected. Also, there can be significant overhead involved in the creation of secondary copies 116. Moreover, specialized programmed intelligence and/or hardware capability is generally needed for accessing and interacting with secondary storage devices 108. Client computing devices 102 may interact directly with a secondary storage device 108 to create secondary copies 116, but in view of the factors described above, this approach can negatively impact the ability of client computing device 102 to serve/service application 110 and produce primary data 112. Further, any given client computing device 102 may not be optimized for interaction with certain secondary storage devices 108.
Thus, system 100 may include one or more software and/or hardware components which generally act as intermediaries between client computing devices 102 (that generate primary data 112) and secondary storage devices 108 (that store secondary copies 116). In addition to off-loading certain responsibilities from client computing devices 102, these intermediate components provide other benefits. For instance, as discussed further below with respect to
Secondary storage computing device(s) 106 can comprise any of the computing devices described above, without limitation. In some cases, secondary storage computing device(s) 106 also include specialized hardware componentry and/or software intelligence (e.g., specialized interfaces) for interacting with certain secondary storage device(s) 108 with which they may be specially associated. To create a secondary copy 116 involving the copying of data from primary storage subsystem 117 to secondary storage subsystem 118, client computing device 102 may communicate the primary data 112 to be copied (or a processed version thereof generated by a data agent 142) to the designated secondary storage computing device 106, via a communication pathway 114. Secondary storage computing device 106 in turn may further process and convey the data or a processed version thereof to secondary storage device 108. One or more secondary copies 116 may be created from existing secondary copies 116, such as in the case of an auxiliary copy operation, described further below.
Secondary copy data 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, and accompanied by corresponding metadata Meta11, Meta3, and Meta8, respectively). Moreover, as indicated by the prime mark (′), secondary storage computing devices 106 or other components in secondary storage subsystem 118 may process the data received from primary storage subsystem 117 and store a secondary copy including a transformed and/or supplemented representation of a primary data object and/or metadata that is different from the original format, e.g., in a compressed, encrypted, deduplicated, or other modified format. For instance, secondary storage computing devices 106 can generate new metadata or other information based on said processing, and store the newly generated information along with the secondary copies. Secondary copy data object 1346 represents primary data objects 120, 1336, and 119A as 120′, 1336′, and 119A′, respectively, accompanied by corresponding metadata Meta2, Meta10, and Meta1, respectively. Also, secondary copy data object 134C represents primary data objects 133A, 1196, and 129A as 133A′, 1196′, and 129A′, respectively, accompanied by corresponding metadata Meta9, Meta5, and Meta6, respectively.
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 system 100. Such design choices can impact how system 100 performs and adapts to data growth and other changing circumstances.
Storage Manager
Storage manager 140 is a centralized storage and/or information manager that is configured to perform certain control functions and also to store certain critical information about system 100—hence storage manager 140 is said to manage system 100. As noted, the number of components in system 100 and the amount of data under management can be large. Managing the components and data is therefore a significant task, which can grow unpredictably as the number of components and data scale to meet the needs of the organization. For these and other reasons, according to certain embodiments, responsibility for controlling system 100, or at least a significant portion of that responsibility, is allocated to storage manager 140. Storage manager 140 can be adapted independently according to changing circumstances, without having to replace or re-design the remainder of the system. Moreover, a computing device for hosting and/or operating as storage manager 140 can be selected to best suit the functions and networking needs of storage manager 140. These and other advantages are described in further detail below and with respect to
Storage manager 140 may be a software module or other application hosted by a suitable computing device. In some embodiments, storage manager 140 is itself a computing device (comprising computer hardware processors and computer memory) that performs the functions described herein. Storage manager 140 comprises or operates in conjunction with one or more associated data structures such as a dedicated database (e.g., management database 146), depending on the configuration. The storage manager 140 generally initiates, performs, coordinates, and/or controls storage and other information management operations performed by system 100, e.g., to protect and control primary data 112 and secondary copies 116. In general, storage manager 140 is said to manage system 100, which includes communicating with, instructing, and controlling in some circumstances components such as data agents 142 and media agents 144, etc. As shown by the dashed arrowed lines 114 in
According to certain embodiments, storage manager 140 provides one or more of the following functions:
Storage manager 140 may maintain an associated database 146 (or “storage manager database 146” or “management database 146”) of management-related data and information management policies 148. Database 146 is stored in computer memory accessible by storage manager 140. Database 146 may include a management index 150 (or “index 150”) or other data structure(s) that may store: logical associations between components of the system; user preferences and/or profiles (e.g., preferences regarding encryption, compression, or deduplication of primary data or secondary copies; preferences regarding the scheduling, type, or other aspects of 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; other useful data; and/or any combination thereof. For example, storage manager 140 may use index 150 to track logical associations between media agents 144 and secondary storage devices 108 and/or movement of data to/from secondary storage devices 108. For instance, index 150 may store data associating a client computing device 102 with a particular media agent 144 and/or secondary storage device 108, as specified in an information management policy 148.
Administrators and others may configure and initiate certain information management operations on an individual basis. But while this may be acceptable for some recovery operations or other infrequent tasks, it is often not workable for implementing on-going organization-wide data protection and management. Thus, system 100 may utilize information management policies 148 for specifying and executing information management operations on an automated basis. Generally, an information management policy 148 can include a stored data structure or other information source that specifies parameters (e.g., criteria and rules) associated with storage management or other information management operations. Storage manager 140 can process an information management policy 148 and/or index 150 and, based on the results, identify an information management operation to perform, identify the appropriate components in system 100 to be involved in the operation (e.g., client computing devices 102 and corresponding data agents 142, secondary storage computing devices 106 and corresponding media agents 144, etc.), establish connections to those components and/or between those components, and/or instruct and control those components to carry out the operation. In this manner, system 100 can translate stored information into coordinated activity among the various computing devices in system 100.
Management database 146 may maintain information management policies 148 and associated data, although information management policies 148 can be stored in computer memory at any appropriate location outside management database 146. For instance, an information management policy 148 such as 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 or other information management operations, depending on the embodiment. Information management policies 148 are described further below. According to certain embodiments, management 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 subclient data were protected and where the secondary copies are stored and which media agent 144 performed the storage operation(s)). This and other metadata may additionally be stored in other locations, such as at secondary storage computing device 106 or on the secondary storage device 108, allowing data recovery without the use of storage manager 140 in some cases. Thus, management database 146 may comprise data needed to kick off secondary copy operations (e.g., storage policies, schedule policies, etc.), status and reporting information about completed jobs (e.g., status and error reports on yesterday's backup jobs), and additional information sufficient to enable restore and disaster recovery operations (e.g., media agent associations, location indexing, content indexing, etc.).
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. These are described further below. Jobs agent 156 in some embodiments initiates, controls, and/or monitors the status of some or all information management operations previously performed, currently being performed, or scheduled to be performed by system 100. A job is a logical grouping of information management operations such as daily storage operations scheduled for a certain set of subclients (e.g., generating incremental block-level backup copies 116 at a certain time every day for database files in a certain geographical location). Thus, jobs agent 156 may access information management policies 148 (e.g., in management database 146) to determine when, where, and how to initiate/control jobs in system 100.
Storage Manager User Interfaces
User interface 158 may include information processing and display software, such as a graphical user interface (GUI), an application program interface (API), and/or other interactive interface(s) through which users and system processes can retrieve information about the status of information management operations or issue instructions to storage manager 140 and other components. Via user interface 158, users may issue instructions to the components in system 100 regarding performance of secondary copy 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 secondary copy jobs or to monitor the status of certain components in system 100 (e.g., the amount of capacity left in a storage device). Storage manager 140 may 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 by interacting with user interface 158.
Various embodiments of information management system 100 may be configured and/or designed to generate user interface data usable for rendering the various interactive user interfaces described. The user interface data may be used by system 100 and/or by another system, device, and/or software program (for example, a browser program), to render the interactive user interfaces. The interactive user interfaces may be displayed on, for example, electronic displays (including, for example, touch-enabled displays), consoles, etc., whether direct-connected to storage manager 140 or communicatively coupled remotely, e.g., via an internet connection. The present disclosure describes various embodiments of interactive and dynamic user interfaces, some of which may be generated by user interface agent 158, and which are the result of significant technological development. The user interfaces described herein may provide improved human-computer interactions, allowing for significant cognitive and ergonomic efficiencies and advantages over previous systems, including reduced mental workloads, improved decision-making, and the like. User interface 158 may operate in a single integrated view or console (not shown). The console may support a reporting capability for generating a variety of reports, which may be tailored to a particular aspect of information management. User interfaces are not exclusive to storage manager 140 and in some embodiments a user may access information locally from a computing device component of system 100. For example, some information pertaining to installed data agents 142 and associated data streams may be available from client computing device 102. Likewise, some information pertaining to media agents 144 and associated data streams may be available from secondary storage computing device 106.
Storage Manager Management Agent
Management agent 154 can provide storage manager 140 with the ability to communicate with other components within system 100 and/or with other information management cells 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, without limitation. Management agent 154 also allows multiple information management cells to communicate with one another. For example, system 100 in some cases may be one information management cell in a network of multiple cells adjacent to one another or otherwise logically related, e.g., in a WAN or LAN. With this arrangement, the cells may communicate with one another through respective management agents 154. Inter-cell communications and hierarchy is described in greater detail in e.g., U.S. Pat. No. 7,343,453.
Information Management Cell
An “information management cell” (or “storage operation cell” or “cell”) may generally include a logical and/or physical grouping of a combination of hardware and software components associated with performing information management operations on electronic data, typically one storage manager 140 and at least one data agent 142 (executing on a client computing device 102) and at least one media agent 144 (executing on a secondary storage computing device 106). For instance, the components shown in
Data Agents
A variety of different applications 110 can operate on a given client computing device 102, including operating systems, file systems, database applications, e-mail applications, and virtual machines, just to name a few. And, as part of the process of creating and restoring secondary copies 116, the client computing device 102 may be tasked with processing and preparing the primary data 112 generated by these various applications 110. Moreover, the nature of the processing/preparation can differ across application types, e.g., due to inherent structural, state, and formatting differences among applications 110 and/or the operating system of client computing device 102. Each data agent 142 is 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.
Data agent 142 is a component of information system 100 and is generally directed by storage manager 140 to participate in creating or restoring secondary copies 116. Data agent 142 may be a software program (e.g., in the form of a set of executable binary files) that executes on the same client computing device 102 as the associated application 110 that data agent 142 is configured to protect. Data agent 142 is generally responsible for managing, initiating, or otherwise assisting in the performance of information management operations in reference to its associated application(s) 110 and corresponding primary data 112 which is generated/accessed by the particular application(s) 110. For instance, data agent 142 may take part in copying, archiving, migrating, and/or replicating of certain primary data 112 stored in the primary storage device(s) 104. Data agent 142 may receive control information from storage manager 140, such as commands to transfer copies of data objects and/or metadata to one or more media agents 144. Data agent 142 also may compress, deduplicate, and encrypt certain primary data 112, as well as capture application-related metadata before transmitting the processed data to media agent 144. Data agent 142 also may receive instructions from storage manager 140 to restore (or assist in restoring) a secondary copy 116 from secondary storage device 108 to primary storage 104, such that the restored data may be properly accessed by application 110 in a suitable format as though it were primary data 112.
Each data agent 142 may be specialized for a particular 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 112, a specialized data agent 142 may be used for each data type. For example, to backup, migrate, and/or restore all of the data on a Microsoft Exchange server, the client computing device 102 may use: (1) a Microsoft Exchange Mailbox data agent 142 to back up the Exchange mailboxes; (2) a Microsoft Exchange Database data agent 142 to back up the Exchange databases; (3) a Microsoft Exchange Public Folder data agent 142 to back up the Exchange Public Folders; and (4) a Microsoft Windows File System data agent 142 to back up the file system of client computing device 102. In this example, these specialized data agents 142 are treated as four separate data agents 142 even though they operate on the same client computing device 102. Other examples may include archive management data agents such as a migration archiver or a compliance archiver, Quick Recovery® agents, and continuous data replication agents. Application-specific data agents 142 can provide improved performance as compared to generic agents. For instance, because application-specific data agents 142 may only handle data for a single software application, the design, operation, and performance of the data agent 142 can be streamlined. The data agent 142 may therefore execute faster and consume less persistent storage and/or operating memory than data agents designed to generically accommodate multiple different software applications 110. Each data agent 142 may be configured to access data and/or metadata stored in the primary storage device(s) 104 associated with data agent 142 and its host client computing device 102, and process the data appropriately. For example, during a secondary copy operation, 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. In some embodiments, a data agent 142 may be distributed between 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 media agent 144. 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.
Media Agents
As noted, off-loading certain responsibilities from client computing devices 102 to intermediate components such as secondary storage computing device(s) 106 and corresponding media agent(s) 144 can provide a number of benefits including improved performance of client computing device 102, faster and more reliable information management operations, and enhanced scalability. In one example which will be discussed further below, media agent 144 can act as a local cache of recently-copied data and/or metadata stored to secondary storage device(s) 108, thus improving restore capabilities and performance for the cached data. Media agent 144 is a component of system 100 and is generally directed by storage manager 140 in creating and restoring secondary copies 116. Whereas storage manager 140 generally manages system 100 as a whole, media agent 144 provides a portal to certain secondary storage devices 108, such as by having specialized features for communicating with and accessing certain associated secondary storage device 108. Media agent 144 may be a software program (e.g., in the form of a set of executable binary files) that executes on a secondary storage computing device 106. Media agent 144 generally manages, coordinates, and facilitates the transmission of data between a data agent 142 (executing on client computing device 102) and secondary storage device(s) 108 associated with media agent 144. For instance, other components in the system may interact with media agent 144 to gain access to data stored on associated secondary storage device(s) 108, (e.g., to browse, read, write, modify, delete, or restore data). Moreover, media agents 144 can generate and store information relating to characteristics of the stored data and/or metadata, or can generate and store other types of information that generally provides insight into the contents of the secondary storage devices 108—generally referred to as indexing of the stored secondary copies 116. Each media agent 144 may operate on a dedicated secondary storage computing device 106, while in other embodiments a plurality of media agents 144 may operate on the same secondary storage computing device 106.
A media agent 144 may 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; coordinating the retrieval of data from the particular secondary storage device 108; and modifying and/or deleting data retrieved from the particular secondary storage device 108. Media agent 144 in certain embodiments is physically separate from the associated secondary storage device 108. For instance, a media agent 144 may operate on a secondary storage computing device 106 in a distinct housing, package, and/or location from the associated secondary storage device 108. In one example, a media agent 144 operates on a first server computer and is in communication with a secondary storage device(s) 108 operating in a separate rack-mounted RAID-based system. A media agent 144 associated with a particular secondary storage device 108 may instruct secondary storage device 108 to perform an information management task. For instance, a media agent 144 may instruct 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 data to a client computing device 102. As another example, a secondary storage device 108 may include an array of hard disk drives or solid state drives organized in a RAID configuration, and media agent 144 may forward a logical unit number (LUN) and other appropriate information to the array, which uses the received information to execute the desired secondary copy operation. Media agent 144 may communicate with a secondary storage device 108 via a suitable communications link, such as a SCSI or Fibre Channel link.
Each media agent 144 may maintain an associated media agent database 152. Media agent database 152 may be stored to a disk or other storage device (not shown) that is local to the secondary storage computing device 106 on which media agent 144 executes. In other cases, media agent database 152 is stored separately from the host secondary storage computing device 106. Media agent database 152 can include, among other things, a media agent index 153 (see, e.g.,
Media agent index 153 (or “index 153”) may be a data structure associated with the particular media agent 144 that includes information about the stored data associated with the particular media agent and which may be generated in the course of performing a secondary copy operation or a restore. Index 153 provides a fast and efficient mechanism for locating/browsing secondary copies 116 or other data stored in secondary storage devices 108 without having to access secondary storage device 108 to retrieve the information from there. For instance, for each secondary copy 116, index 153 may include metadata such as a list of the data objects (e.g., files/subdirectories, database objects, mailbox objects, etc.), a logical path to the secondary copy 116 on the corresponding secondary storage device 108, location information (e.g., offsets) indicating where the data objects are stored in the secondary storage device 108, when the data objects were created or modified, etc. Thus, index 153 includes metadata associated with the secondary copies 116 that is readily available for use from media agent 144. In some embodiments, some or all of the information in index 153 may instead or additionally be stored along with secondary copies 116 in secondary storage device 108. In some embodiments, a secondary storage device 108 can include sufficient information to enable a “bare metal restore,” where the operating system and/or software applications of a failed client computing device 102 or another target may be automatically restored without manually reinstalling individual software packages (including operating systems).
Because index 153 may operate as a cache, it can also be referred to as an “index cache.” In such cases, information stored in index cache 153 typically comprises data that reflects certain particulars about relatively recent secondary copy operations. After some triggering event, such as after some time elapses or index cache 153 reaches a particular size, certain portions of index cache 153 may be copied or migrated to secondary storage device 108, e.g., on a least-recently-used basis. This information may be retrieved and uploaded back into index cache 153 or otherwise restored to 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 storage device(s) 108.
In some alternative embodiments media agent 144 generally acts as a coordinator or facilitator of secondary copy operations between client computing devices 102 and secondary storage devices 108, but does not actually write the data to secondary storage device 108. For instance, storage manager 140 (or 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, client computing device 102 transmits data directly or via one or more intermediary components to secondary storage device 108 according to the received instructions, and vice versa. Media agent 144 may still receive, process, and/or maintain metadata related to the secondary copy operations, i.e., may continue to build and maintain index 153. In these embodiments, payload data can flow through media agent 144 for the purposes of populating index 153, but not for writing to secondary storage device 108. Media agent 144 and/or other components such as 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 system 100 can be distributed amongst various physical and/or logical components. For instance, one or more of storage manager 140, data agents 142, and media agents 144 may operate 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 media agents 144 operate can be tailored for interaction with associated secondary storage devices 108 and provide fast index cache operation, among other specific tasks. Similarly, client computing device(s) 102 can be selected to effectively service applications 110 in order to efficiently produce and store primary data 112. Moreover, in some cases, one or more of the individual components of 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 management database 146 is relatively large, database 146 may be migrated to or may otherwise reside on a specialized database server (e.g., an SQL server) separate from a server that implements the other functions of storage manager 140. This distributed configuration can provide added protection because database 146 can be protected with standard database utilities (e.g., SQL log shipping or database replication) independent from other functions of storage manager 140. Database 146 can be efficiently replicated to a remote site for use in the event of a disaster or other data loss at the primary site. Or 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 computing device can no longer service the needs of a growing system 100.
The distributed architecture also provides scalability and efficient component utilization.
Where system 100 includes multiple media agents 144 (see, e.g.,
In order to protect and leverage stored data, system 100 can be configured to perform a variety of information management operations, which may also be referred to in some cases as storage management operations or storage operations. These operations can generally include (i) data movement operations, (ii) processing and data manipulation operations, and (iii) analysis, reporting, and management operations.
Data Movement Operations, Including Secondary Copy Operations
Data movement operations are generally storage operations that involve the copying or migration of data between different locations in system 100. For example, data movement operations can include operations in which stored data is copied, migrated, or otherwise transferred from one or more first storage devices to one or more second storage devices, such as 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, from secondary storage devices 108 to primary storage devices 104, or from primary storage device(s) 104 to different primary storage device(s) 104, or in some cases within the same primary storage device 104 such as within a storage array. 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), snapshot operations, deduplication or single-instancing operations, auxiliary copy operations, disaster-recovery copy operations, and the like. As will be discussed, some of these operations do not necessarily create distinct copies. Nonetheless, some or all of these operations are generally referred to as “secondary copy operations” for simplicity because they involve secondary copies. Data movement also comprises restoring secondary copies.
Backup Operations
A backup operation creates a copy of a version of primary data 112 at a particular point in time (e.g., one or more files or other data units). Each subsequent backup copy 116 (which is a form of secondary copy 116) may be maintained independently of the first. A backup generally involves maintaining a version of the copied primary data 112 as well as backup copies 116. Further, a backup copy in some embodiments is generally stored in a form that is different from the native format, e.g., a backup format. This contrasts to the version in primary data 112 which may instead be stored in a format native to 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 native application format. For example, a backup copy may be stored in a compressed backup format that facilitates efficient long-term storage. Backup copies 116 can have relatively long retention periods as compared to primary data 112, which is generally highly changeable. Backup copies 116 may be stored on media with slower retrieval times than primary storage device 104. Some backup copies may have shorter retention periods than some other types of secondary copies 116, such as archive copies (described below). Backups may be stored at an offsite location.
Backup operations can include full backups, differential backups, incremental backups, “synthetic full” backups, and/or creating a “reference copy.” A full backup (or “standard 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 afterwards only store changes relative to the full backup copy. A differential backup operation (or cumulative incremental backup operation) tracks and stores changes that occurred since the last full backup. Differential backups can grow quickly in size, but can restore relatively efficiently 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, restoring can be lengthy compared to full or differential backups because completing a restore operation may involve accessing a full backup in addition to multiple incremental backups. Synthetic full backups generally consolidate data without directly backing up data from the client computing device. A synthetic full backup is created from the most recent full backup (i.e., standard or synthetic) and subsequent incremental and/or differential backups. The resulting synthetic full backup is identical to what would have been created had the last backup for the subclient been a standard full backup. Unlike standard full, incremental, and differential backups, however, a synthetic full backup does not actually transfer data from primary storage to the backup media, because it operates as a backup consolidator. A synthetic full backup extracts the index data of each participating subclient. Using this index data and the previously backed up user data images, it builds new full backup images (e.g., bitmaps, or complete backup copies), one for each subclient. The new backup images consolidate the index and user data stored in the related incremental, differential, and previous full backups into a synthetic backup file that fully represents the subclient (e.g., via pointers) but does not necessarily comprise all its constituent data.
Any of the above types of backup operations can be at the volume level, file level, or block level. Volume level backup operations generally involve copying of a data volume (e.g., a logical disk or partition) as a whole. In a file-level backup, information management system 100 generally tracks changes to individual files and includes copies of files in the backup copy. For block-level backups, files are broken into constituent blocks, and changes are tracked at the block level. Upon restore, system 100 reassembles the blocks into files in a transparent fashion. Far less data may actually be transferred and copied to secondary storage devices 108 during a file-level copy than a volume-level copy. Likewise, a block-level copy may transfer less data than a file-level copy, resulting in faster execution. However, restoring a relatively higher-granularity copy can result in longer restore times. For instance, when restoring a block-level copy, the process of locating and retrieving constituent blocks can sometimes take longer than restoring file-level backups.
A reference copy may comprise copy(ies) of selected objects from backed up data, typically to help organize data by keeping contextual information from multiple sources together, and/or help retain specific data for a longer period of time, such as for legal hold needs. A reference copy generally maintains data integrity, and when the data is restored, it may be viewed in the same format as the source data. In some embodiments, a reference copy is based on a specialized client, individual subclient and associated information management policies (e.g., storage policy, retention policy, etc.) that are administered within system 100.
Archive Operations
Because backup operations generally involve maintaining a version of the copied primary data 112 and also maintaining backup copies in secondary storage device(s) 108, they can consume significant storage capacity. To reduce storage consumption, an archive operation according to certain embodiments creates an archive 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) may be removed from source storage. 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 format of the original application or source copy. In addition, archive copies may be retained for relatively long periods of time (e.g., years) and, in some cases are never deleted. In certain embodiments, archive copies may be made and kept for extended periods in order to meet compliance regulations. Archiving can also serve the purpose of freeing up space in primary storage device(s) 104 and easing the demand on computational resources on client computing device 102. Similarly, when a secondary copy 116 is archived, the archive copy can therefore serve the purpose of freeing up space in the source secondary storage device(s) 108. Examples of data archiving operations are provided in U.S. Pat. No. 7,107,298.
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 primary data 112 at a given point in time, and may include state and/or status information relative to an application 110 that creates/manages primary data 112. 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 “hardware snapshot” (or “hardware-based snapshot”) operation occurs where a target storage device (e.g., a primary storage device 104 or a secondary storage device 108) performs the snapshot operation in a self-contained fashion, substantially independently, using hardware, firmware and/or software operating on the storage device itself. For instance, the storage device may perform snapshot operations generally without intervention or oversight from any of the other components of the system 100, e.g., a storage array may generate an “array-created” hardware snapshot and may also manage its storage, integrity, versioning, etc. In this manner, hardware snapshots can off-load other components of system 100 from snapshot processing. An array may receive a request from another component to take a snapshot and then proceed to execute the “hardware snapshot” operations autonomously, preferably reporting success to the requesting component.
A “software snapshot” (or “software-based snapshot”) operation, on the other hand, occurs where a component in system 100 (e.g., client computing device 102, etc.) implements a software layer that manages the snapshot operation via interaction with the target storage device. For instance, the component executing the snapshot management software layer may derive a set of pointers and/or data that represents the snapshot. The snapshot management software layer may then transmit the same to the target storage device, along with appropriate instructions for writing the snapshot. One example of a software snapshot product is Microsoft Volume Snapshot Service (VSS), which is part of the Microsoft Windows operating system.
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 map files and directories to specific memory locations (e.g., to specific 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 from an application. In some other cases, the snapshot may be created at the block-level, such that creation of the snapshot occurs without awareness of the file system. Each pointer points to a respective stored data block, so that 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 the point in time when the snapshot copy was created.
An 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 change later on. Furthermore, when files change, typically only the pointers which map to blocks are copied, not the blocks themselves. For example for “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, and the pointer to that block is changed to reflect the new location of that block. The snapshot mapping of file system data may also be 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. 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.
Replication Operations
Replication is another type of secondary copy operation. Some types of secondary copies 116 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 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 or substantially immediately copied 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, secondary copy 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, back up, or otherwise manipulate the replication copies as if they were 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, system 100 can replicate sections of application data that represent a recoverable state rather than rote copying of blocks of data. Examples of replication operations (e.g., continuous data replication) are provided in U.S. Pat. No. 7,617,262.
Deduplication/Single-Instancing Operations
Deduplication or single-instance storage is useful to reduce the amount of non-primary data. For instance, some or all of the above-described secondary copy operations can involve deduplication in some fashion. New data is read, broken down into data portions of a selected granularity (e.g., sub-file level blocks, files, etc.), compared with corresponding portions that are already in secondary storage, and only new/changed portions are stored. Portions that already exist are represented as pointers to the already-stored data. Thus, a deduplicated secondary copy 116 may comprise actual data portions copied from primary data 112 and may further comprise pointers to already-stored data, which is generally more storage-efficient than a full copy. In order to streamline the comparison process, system 100 may calculate and/or store signatures (e.g., hashes or cryptographically unique IDs) corresponding to the individual source data portions and compare the signatures to already-stored data signatures, instead of comparing entire data portions. In some cases, only a single instance of each data portion is stored, and deduplication operations may therefore be referred to interchangeably as “single-instancing” operations. Depending on the implementation, however, deduplication operations can store more than one instance of certain data portions, yet still significantly reduce stored-data redundancy. Depending on the embodiment, deduplication portions such as data blocks can be of fixed or variable length. Using variable length blocks can enhance deduplication by responding to changes in the data stream, but can involve more complex processing. In some cases, system 100 utilizes a technique for dynamically aligning deduplication blocks based on changing content in the data stream, as described in U.S. Pat. No. 8,364,652.
System 100 can deduplicate in a variety of manners at a variety of locations. For instance, in some embodiments, system 100 implements “target-side” deduplication by deduplicating data at the media agent 144 after being received from data agent 142. In some such cases, 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., data block signatures). Examples of such a configuration are provided in U.S. Pat. No. 9,020,900. Instead of or in combination with “target-side” deduplication, “source-side” (or “client-side”) deduplication can also be performed, e.g., to reduce the amount of data to be transmitted by data agent 142 to media agent 144. Storage manager 140 may communicate with other components within system 100 via network protocols and cloud service provider APIs to facilitate cloud-based deduplication/single instancing, as exemplified in U.S. Pat. No. 8,954,446. Some other deduplication/single instancing techniques are described in U.S. Patent Pub. No. 2006/0224846 and in U.S. Pat. No. 9,098,495.
Information Lifecycle Management and Hierarchical Storage Management
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, which generally automatically moves data between classes of storage devices, such as from high-cost to 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 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 archiving in that creating an HSM copy may (though not always) involve deleting some of the source data, e.g., according to one or more criteria related to the source data. For example, an HSM copy may include primary data 112 or a secondary copy 116 that exceeds a given size threshold or a given age threshold. Often, and unlike some types of archive copies, HSM data that is removed or aged from the source is replaced by a logical reference pointer or stub. The reference pointer or stub can be stored in the primary storage device 104 or other source storage device, such as a secondary storage device 108 to replace the deleted source data and to point to or otherwise indicate the new location in (another) secondary storage device 108.
For 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 HSM data that has been removed or migrated, system 100 uses the stub to locate the data and can make recovery of the data appear transparent, even though the HSM data may be stored at a location different from other source data. In this manner, the data appears to the user (e.g., in file system browsing windows and the like) as if it still resides in the source location (e.g., in a primary storage device 104). The stub may include 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., compressed, encrypted, deduplicated, and/or otherwise modified). 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.” Examples of HSM and ILM techniques are provided in U.S. Pat. No. 7,343,453.
Auxiliary Copy Operations
An auxiliary copy generally comprises a copy of an existing secondary copy 116. For instance, an initial secondary copy 116 may be derived from primary data 112 or from data residing in secondary storage subsystem 118, whereas an auxiliary copy is generated from the initial secondary copy 116. Auxiliary copies provide additional standby copies of data and may reside on different secondary storage devices 108 than the initial secondary copies 116. Thus, auxiliary copies can be used for recovery purposes if initial secondary copies 116 become unavailable. Example auxiliary copy techniques are described in further detail in U.S. Pat. No. 8,230,195.
Disaster-Recovery Copy Operations
System 100 may also make and retain disaster recovery copies, often as secondary, high-availability disk copies. System 100 may create secondary copies and store them 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 Manipulation, Including Encryption and Compression
Data manipulation and processing may include encryption and compression as well as integrity marking and checking, formatting for transmission, formatting for storage, etc. Data may be manipulated “client-side” by data agent 142 as well as “target-side” by media agent 144 in the course of creating secondary copy 116, or conversely in the course of restoring data from secondary to primary.
Encryption Operations
System 100 in some cases is configured to process data (e.g., files or other data objects, primary data 112, 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. System 100 in some cases encrypts the data at the client level, such that client computing devices 102 (e.g., data agents 142) encrypt the data prior to transferring it to other components, e.g., before sending the data to media agents 144 during a secondary copy operation. In such cases, 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 media agent 144 creates auxiliary copies or archive copies. Encryption may be applied in creating a secondary copy 116 of a previously unencrypted secondary copy 116, without limitation. In further embodiments, secondary storage devices 108 can implement built-in, high performance hardware-based encryption.
Compression Operations
Similar to encryption, system 100 may also or alternatively compress data in the course of generating a secondary copy 116. Compression encodes information such that fewer bits are needed to represent the information as compared to the original representation. Compression techniques are well known in the art. Compression operations may apply one or more data compression algorithms. Compression may be applied in creating a secondary copy 116 of a previously uncompressed secondary copy, e.g., when making archive copies or disaster recovery copies. The use of compression may result in metadata that specifies the nature of the compression, so that data may be uncompressed on restore if appropriate.
Data Analysis, Reporting, and Management Operations
Data analysis, reporting, and management operations can differ from data movement operations in that they do not necessarily involve copying, migration or other transfer of data between different locations in the system. For instance, data analysis 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 analysis operations are performed in conjunction with data movement operations. Some data analysis operations include content indexing operations and classification operations which can be useful in leveraging data under management to enhance search and other features.
Classification Operations/Content Indexing
In some embodiments, information management system 100 analyzes and indexes characteristics, content, and metadata associated with primary data 112 (“online content indexing”) and/or secondary copies 116 (“off-line content indexing”). Content indexing can identify files or other data objects based on content (e.g., user-defined keywords or phrases, other keywords/phrases that are not defined by a user, etc.), and/or metadata (e.g., email metadata such as “to,” “from,” “cc,” “bcc,” attachment name, received time, etc.). Content indexes may be searched and search results may be restored. System 100 generally organizes and catalogues the results into a content index, which may be stored within media agent database 152, for example. The content index can also include the storage locations of or pointer references to indexed data in primary data 112 and/or secondary copies 116. Results may also be stored elsewhere in system 100 (e.g., in primary storage device 104 or in secondary storage device 108). Such content index data provides storage manager 140 or other components with an efficient mechanism for locating primary data 112 and/or secondary copies 116 of data objects that match particular criteria, thus greatly increasing the search speed capability of system 100. For instance, search criteria can be specified by a user through user interface 158 of storage manager 140. Moreover, when system 100 analyzes data and/or metadata in secondary copies 116 to create an “off-line content index,” this operation has no significant impact on the performance of client computing devices 102 and thus does not take a toll on the production environment. Examples of content indexing techniques are provided in U.S. Pat. No. 8,170,995.
One or more components, such as a content index engine, can be configured to scan data and/or associated metadata for classification purposes to populate a database (or other data structure) of information, which can be referred to as a “data classification database” or a “metabase.” Depending on the embodiment, the data classification database(s) can be organized in a variety of different ways, including centralization, logical sub-divisions, and/or physical sub-divisions. For instance, one or more data classification databases may be associated with different subsystems or tiers within system 100. As an example, there may be a first metabase associated with primary storage subsystem 117 and a second metabase associated with secondary storage subsystem 118. In other cases, metabase(s) may be associated with individual components, e.g., client computing devices 102 and/or media agents 144. In some embodiments, a data classification database may reside as one or more data structures within management database 146, may be otherwise associated with storage manager 140, and/or may reside as a separate component. In some cases, metabase(s) may be included in separate database(s) and/or on separate storage device(s) from primary data 112 and/or secondary copies 116, such that operations related to the metabase(s) do not significantly impact performance on other components of system 100. In other cases, metabase(s) may be stored along with primary data 112 and/or secondary copies 116. Files or other data objects can be associated with identifiers (e.g., tag entries, etc.) 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. For instance, a metabase can dramatically improve the speed with which system 100 can search through and identify data as compared to other approaches that involve scanning an entire file system. Examples of metabases and data classification operations are provided in U.S. Pat. Nos. 7,734,669 and 7,747,579.
Management and Reporting Operations
Certain embodiments leverage the integrated ubiquitous nature of system 100 to provide useful system-wide management and reporting. Operations management can generally include monitoring and managing the health and performance of 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. As an example, storage manager 140 or another component in system 100 may analyze traffic patterns and suggest and/or automatically route data to minimize congestion. In some embodiments, the system can generate predictions relating to storage operations or storage operation information. Such predictions, which may be based on a trending analysis, may predict various network operations or resource usage, such as network traffic levels, storage media use, use of bandwidth of communication links, use of media agent components, etc. Further examples of traffic analysis, trend analysis, prediction generation, and the like are described in U.S. Pat. No. 7,343,453.
In some configurations having a hierarchy of storage operation cells, a master storage manager 140 may track the status of subordinate cells, such as the status of jobs, system components, system resources, and other items, by communicating with storage managers 140 (or other components) in the respective storage operation cells. Moreover, the master storage manager 140 may also track status by receiving periodic status updates from the storage managers 140 (or other components) in the respective cells regarding jobs, system components, system resources, and other items. In some embodiments, a master storage manager 140 may store status information and other information regarding its associated storage operation cells and other system information in its management database 146 and/or index 150 (or in another location). The master storage manager 140 or other component may also determine whether certain storage-related or other criteria are satisfied, and may perform an action or trigger event (e.g., data migration) in response to the criteria being satisfied, such as where a storage threshold is met for a particular volume, or where inadequate protection exists for certain data. For instance, data from one or more storage operation cells is used to mitigate recognized risks dynamically and automatically, and/or to advise users of risks or suggest actions to mitigate these risks. For example, an information management policy may specify certain requirements (e.g., that a storage device should maintain a certain amount of free space, that secondary copies should occur at a particular interval, that data should be aged and migrated to other storage after a particular period, that data on a secondary volume should always have a certain level of availability and be restorable within a given time period, that data on a secondary volume may be mirrored or otherwise migrated to a specified number of other volumes, etc.). If a risk condition or other criterion is triggered, the system may notify the user of these conditions and may suggest (or automatically implement) a mitigation action to address the risk. For example, the system may indicate that data from a primary copy 112 should be migrated to a secondary storage device 108 to free up space on primary storage device 104. Examples of the use of risk factors and other triggering criteria are described in U.S. Pat. No. 7,343,453.
In some embodiments, system 100 may also determine whether a metric or other indication satisfies particular storage criteria sufficient to perform an action. For example, a storage policy or other definition might indicate that a storage manager 140 should initiate a particular action if a storage metric or other indication drops below or otherwise fails to satisfy specified criteria such as a threshold of data protection. In some embodiments, risk factors may be quantified into certain measurable service or risk levels. For example, certain applications and associated data may be considered to be more important relative to other data and services. Financial compliance data, for example, may be of greater importance than marketing materials, etc. Network administrators may assign priority values or “weights” to certain data and/or applications corresponding to the relative importance. The level of compliance of secondary copy operations specified for these applications may also be assigned a certain value. Thus, the health, impact, and overall importance of a service may be determined, such as by measuring the compliance value and calculating the product of the priority value and the compliance value to determine the “service level” and comparing it to certain operational thresholds to determine whether it is acceptable. Further examples of the service level determination are provided in U.S. Pat. No. 7,343,453.
System 100 may additionally calculate data costing and data availability associated with information management operation cells. For instance, data received from a cell may be used in conjunction with hardware-related information and other information about system elements to determine the cost of storage and/or the availability of particular data. Example information generated could include how fast a particular department is using up available storage space, how long data would take to recover over a particular pathway from a particular secondary storage device, costs over time, etc. Moreover, in some embodiments, such information may be used to determine or predict the overall cost associated with the storage of certain information. The cost associated with hosting a certain application may be based, at least in part, on the type of media on which the data resides, for example. Storage devices may be assigned to a particular cost categories, for example. Further examples of costing techniques are described in U.S. Pat. No. 7,343,453.
Any of the above types of information (e.g., information related to trending, predictions, job, cell or component status, risk, service level, costing, etc.) can generally be provided to users via user interface 158 in a single integrated view or console (not shown). Report types may include: scheduling, event management, media management and data aging. Available reports may also include backup history, data aging history, auxiliary copy history, job history, library and drive, media in library, restore history, and storage policy, etc., without limitation. Such reports may be specified and created at a certain point in time as a system analysis, forecasting, or provisioning tool. Integrated reports may also be generated that illustrate storage and performance metrics, risks and storage costing information. Moreover, users may create their own reports based on specific needs. User interface 158 can include an option to graphically depict the various components in the system using appropriate icons. As one example, user interface 158 may provide a graphical depiction of primary storage devices 104, secondary storage devices 108, data agents 142 and/or media agents 144, and their relationship to one another in system 100.
In general, the operations management functionality of system 100 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 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 secondary copy operations for system 100, such as job status, component status, resource status (e.g., communication 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. Further examples are provided in U.S. Pat. No. 7,343,453. 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 secondary storage devices 108 (e.g., backups, archives, or other secondary copies 116). For example, system 100 may construct and maintain a virtual repository for data stored in 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
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 and/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 data structure or other information source that defines (or includes information sufficient to determine) a set of preferences or other criteria for performing information management operations. Storage policies can include one or more of the following: (1) what data will be associated with the storage policy, e.g., subclient; (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 secondary copy operation to be performed; and (5) retention information specifying how long the data will be retained at the destination (see, e.g.,
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 subclients 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 subclients 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 subclient data. While information in the storage policy can be statically assigned in some cases, some or all of the information in the storage policy can also be dynamically determined based on criteria set forth in the storage policy. For instance, based on such criteria, a particular destination storage device(s) or other parameter of the storage policy may be determined based on characteristics associated with the data involved in a particular secondary copy operation, device availability (e.g., availability of a secondary storage device 108 or a media agent 144), network status and conditions (e.g., identified bottlenecks), user credentials, and the like.
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 associated with the storage policy between the source and destination. A storage policy can also specify the type(s) of associated operations, such as backup, archive, snapshot, auxiliary copy, or the like. Furthermore, retention parameters can specify how long the resulting secondary copies 116 will be kept (e.g., a number of days, months, years, etc.), perhaps depending on organizational needs and/or compliance criteria.
When adding a new client computing device 102, administrators can manually configure information management policies 148 and/or other settings, e.g., via user interface 158. However, this can be an involved process resulting in delays, and it may be desirable to begin data protection operations quickly, without awaiting human intervention. Thus, in some embodiments, system 100 automatically applies a default configuration to client computing device 102. As one example, when one or more data agent(s) 142 are installed on a client computing device 102, the installation script may register the client computing device 102 with 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.
Another type of information management policy 148 is a “scheduling policy,” which specifies when and how often to perform operations. Scheduling parameters 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 are to take place. Scheduling policies in some cases are associated with particular components, such as a subclient, client computing device 102, and the like.
Another type of information management policy 148 is an “audit policy” (or “security policy”), which comprises preferences, rules and/or criteria that protect sensitive data in system 100. For example, an audit policy may define “sensitive objects” which are files or data 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 primary 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.
Another type of information management policy 148 is a “provisioning policy,” which can include preferences, priorities, rules, and/or criteria that specify how client computing devices 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). Storage manager 140 or other components may enforce the provisioning policy. For instance, 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) may be adjusted accordingly or an alert may trigger.
While the above types of information management policies 148 are 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 or operational parameters thereof. 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 that information management policies 148 may specify:
Information management policies 148 can additionally specify or depend on 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:
The file system subclient 112A in certain embodiments generally comprises information generated by the file system and/or operating system of 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 subclient 112B can include data generated by an e-mail application operating on client computing device 102, e.g., mailbox information, folder information, emails, attachments, associated database information, and the like. As described above, the subclients can be logical containers, and the data included in the corresponding primary data 112A and 112B may or may not be stored contiguously. The example storage policy 148A includes backup copy preferences or rule set 160, disaster recovery copy preferences or rule set 162, and compliance copy preferences or rule set 164. Backup copy rule set 160 specifies that it is associated with file system subclient 166 and email subclient 168. Each of subclients 166 and 168 are associated with the particular client computing device 102. Backup copy rule set 160 further specifies that the backup operation will be written to disk library 108A and designates a particular media agent 144A to convey the data to disk library 108A. Finally, backup copy rule set 160 specifies that backup copies created according to rule set 160 are scheduled to be generated hourly and are to be retained for 30 days. In some other embodiments, scheduling information is not included in storage policy 148A and is instead specified by a separate scheduling policy. Disaster recovery copy rule set 162 is associated with the same two subclients 166 and 168. However, disaster recovery copy rule set 162 is associated with tape library 108B, unlike backup copy rule set 160. Moreover, disaster recovery copy rule set 162 specifies that a different media agent, namely 144B, will convey data to tape library 108B. Disaster recovery copies created according to rule set 162 will be retained for 60 days and will be generated daily. Disaster recovery copies generated according to disaster recovery copy rule set 162 can provide protection in the event of a disaster or other catastrophic data loss that would affect the backup copy 116A maintained on disk library 108A. Compliance copy rule set 164 is only associated with the email subclient 168, and not the file system subclient 166. Compliance copies generated according to compliance copy rule set 164 will therefore not include primary data 112A from the file system subclient 166. For instance, the organization may be under an obligation to store and 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 file system data. Compliance copy rule set 164 is associated with the same tape library 108B and media agent 144B as disaster recovery copy rule set 162, although a different storage device or media agent could be used in other embodiments. Finally, compliance copy rule set 164 specifies that the copies it governs will be generated quarterly and retained for 10 years.
Secondary Copy Jobs
A logical grouping of secondary copy operations governed by a rule set and being initiated at a point in time may be referred to as a “secondary copy job” (and sometimes may be called a “backup job,” even though it is not necessarily limited to creating only backup copies). Secondary copy jobs may be initiated on demand as well. Steps 1-9 below illustrate three secondary copy jobs based on storage policy 148A.
Referring to
The target media agent 144A receives the data-agent-processed data from client computing device 102, and at step 4 generates and conveys backup copy 116A to disk library 108A to be stored as backup copy 116A, again at the direction of storage manager 140 and according to backup copy rule set 160. Media agent 144A can also update its index 153 to include data and/or metadata related to backup copy 116A, such as information indicating where the backup copy 116A resides on disk library 108A, where the email copy resides, where the file system copy resides, data and metadata for cache retrieval, etc. Storage manager 140 may similarly update its index 150 to include information relating to the secondary copy operation, such as information relating to the type of operation, a physical location associated with one or more copies created by the operation, the time the operation was performed, status information relating to the operation, the components involved in the operation, and the like. In some cases, storage manager 140 may update its index 150 to include some or all of the information stored in index 153 of media agent 144A. At this point, the backup job may be considered complete. After the 30-day retention period expires, storage manager 140 instructs media agent 144A to delete backup copy 116A from disk library 108A and indexes 150 and/or 153 are updated accordingly. At step 5, storage manager 140 initiates another backup job for a disaster recovery copy according to the disaster recovery rule set 162. Illustratively this includes steps 5-7 occurring daily for creating disaster recovery copy 116B. Illustratively, and by way of illustrating the scalable aspects and off-loading principles embedded in system 100, disaster recovery copy 116B is based on backup copy 116A and not on primary data 112A and 112B. At step 6, illustratively based on instructions received from storage manager 140 at step 5, the specified media agent 144B retrieves the most recent backup copy 116A from disk library 108A. At step 7, again at the direction of storage manager 140 and as specified in disaster recovery copy rule set 162, media agent 1446 uses the retrieved data to create a disaster recovery copy 1166 and store it to tape library 108B. In some cases, disaster recovery copy 116B is a direct, mirror copy of backup copy 116A, and remains in the backup format. In other embodiments, disaster recovery copy 1166 may be further compressed or encrypted, or may be generated in some other manner, such as by using primary data 112A and 112B from primary storage device 104 as sources. The disaster recovery copy operation is initiated once a day and disaster recovery copies 116B are deleted after 60 days; indexes 153 and/or 150 are updated accordingly when/after each information management operation is executed and/or completed. The present backup job may be considered completed. At step 8, storage manager 140 initiates another backup job according to compliance rule set 164, which performs steps 8-9 quarterly to create compliance copy 116C. For instance, storage manager 140 instructs media agent 144B to create compliance copy 116C on tape library 108B, as specified in the compliance copy rule set 164. At step 9 in the example, compliance copy 116C is generated using disaster recovery copy 1166 as the source. This is efficient, because disaster recovery copy resides on the same secondary storage device and thus no network resources are required to move the data. In other embodiments, compliance copy 116C is instead generated using primary data 112B corresponding to the email subclient or using backup copy 116A from disk library 108A as source data. As specified in the illustrated example, compliance copies 116C are created quarterly, and are deleted after ten years, and indexes 153 and/or 150 are kept up-to-date accordingly.
Again referring to
An information governance policy may comprise a classification policy, which defines a taxonomy of classification terms or tags relevant to a compliance task and/or business objective. A classification policy may also associate a defined tag with a classification rule. A classification rule defines a particular combination of criteria, such as users who have created, accessed or modified a document or data object; file or application types; content or metadata keywords; clients or storage locations; dates of data creation and/or access; review status or other status within a workflow (e.g., reviewed or un-reviewed); modification times or types of modifications; and/or any other data attributes in any combination, without limitation. A classification rule may also be defined using other classification tags in the taxonomy. The various criteria used to define a classification rule may be combined in any suitable fashion, for example, via Boolean operators, to define a complex classification rule. As an example, an e-discovery classification policy might define a classification tag “privileged” that is associated with documents or data objects that (1) were created or modified by legal department staff, or (2) were sent to or received from outside counsel via email, or (3) contain one of the following keywords: “privileged” or “attorney” or “counsel,” or other like terms. Accordingly, all these documents or data objects will be classified as “privileged.”
One specific type of classification tag, which may be added to an index at the time of indexing, is an “entity tag.” An entity tag may be, for example, any content that matches a defined data mask format. Examples of entity tags might include, e.g., social security numbers (e.g., any numerical content matching the formatting mask XXX-XX-XXXX), credit card numbers (e.g., content having a 13-16 digit string of numbers), SKU numbers, product numbers, etc. A user may define a classification policy by indicating criteria, parameters or descriptors of the policy via a graphical user interface, such as a form or page with fields to be filled in, pull-down menus or entries allowing one or more of several options to be selected, buttons, sliders, hypertext links or other known user interface tools for receiving user input, etc. For example, a user may define certain entity tags, such as a particular product number or project ID. In some implementations, the classification policy can be implemented using cloud-based techniques. For example, the storage devices may be cloud storage devices, and the storage manager 140 may execute cloud service provider API over a network to classify data stored on cloud storage devices.
Restore Operations from Secondary Copies
While not shown in
As one example, a user may manually initiate a restore of backup copy 116A, e.g., by interacting with user interface 158 of storage manager 140 or with a web-based console with access to system 100. Storage manager 140 may accesses data in its index 150 and/or management database 146 (and/or the respective storage policy 148A) associated with the selected backup copy 116A to identify the appropriate media agent 144A and/or secondary storage device 108A where the secondary copy resides. The user may be presented with a representation (e.g., stub, thumbnail, listing, etc.) and metadata about the selected secondary copy, in order to determine whether this is the appropriate copy to be restored, e.g., date that the original primary data was created. Storage manager 140 will then instruct media agent 144A and an appropriate data agent 142 on the target client computing device 102 to restore secondary copy 116A to primary storage device 104. 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, e.g., 144A, retrieves secondary copy 116A from disk library 108A. For instance, media agent 144A may access its index 153 to identify a location of backup copy 116A on disk library 108A, or may access location information residing on disk library 108A itself.
In some cases, a backup copy 116A that was recently created or accessed, may be cached to speed up the restore operation. In such a case, media agent 144A accesses a cached version of all or part of backup copy 116A residing in index 153, without having to access disk library 108A for some or all of the data. Once it has retrieved backup copy 116A, the media agent 144A communicates the data to the requesting client computing device 102. Upon receipt, file system data agent 142A and email data agent 142B may unpack (e.g., restore from a backup format to the native application format) the data in backup copy 116A and restore the unpackaged data to primary storage device 104. In general, secondary copies 116 may be restored to the same volume or folder in primary storage device 104 from which the secondary copy was derived; to another storage location or client computing device 102; to shared storage, etc. In some cases, the data may be restored so that it may be used by an application 110 of a different version/vintage from the application that created the original primary data 112.
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 one or more 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, media agent 144, storage manager 140, or other component may divide files into chunks and generate headers for each chunk by processing the files. Headers can include a variety of information such as file and/or volume identifier(s), offset(s), and/or other information associated with the payload data items, a chunk sequence number, etc. Importantly, in addition to being stored with secondary copy 116 on secondary storage device 108, chunk headers can also be stored to index 153 of the associated media agent(s) 144 and/or to index 150 associated with storage manager 140. This can be useful for providing faster processing of secondary copies 116 during browsing, 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 media agent 144 and/or storage manager 140, which may update their respective indexes 153, 150 accordingly. During restore, chunks may be processed (e.g., by media agent 144) according to the information in the chunk header to reassemble the files.
Data can also be communicated within system 100 in data channels that connect client computing devices 102 to secondary storage devices 108. These data channels can be referred to as “data streams,” and multiple data streams can be employed to parallelize an information management operation, improving data transfer rate, among other advantages. Example data formatting techniques including techniques involving data streaming, chunking, and the use of other data structures in creating secondary copies are described in U.S. Pat. Nos. 7,315,923, 8,156,086, and 8,578,120.
Referring to
As an example, data structures 180 illustrated in
If the operating system of the secondary storage computing device 106 on which media agent 144 operates supports sparse files, then when media agent 144 creates container files 190/191/193, it can create them as sparse files. A sparse file is a type of file that may include empty space (e.g., a sparse file may have real data within it, such as at the beginning of the file and/or at the end of the file, but may also have empty space in it that is not storing actual data, such as a contiguous range of bytes all having a value of zero). Having container files 190/191/193 be sparse files allows media agent 144 to free up space in container files 190/191/193 when blocks of data in container files 190/191/193 no longer need to be stored on the storage devices. In some examples, media agent 144 creates a new container file 190/191/193 when a container file 190/191/193 either includes 100 blocks of data or when the size of the container file 190 exceeds 50 MB. In other examples, media agent 144 creates a new container file 190/191/193 when a container file 190/191/193 satisfies other criteria (e.g., it contains from approx. 100 to approx. 1000 blocks or when its size exceeds approximately 50 MB to 1 GB). In some cases, a file on which a secondary copy operation is performed may comprise a large number of data blocks. For example, a 100 MB file may comprise 400 data blocks of size 256 KB. If such a file is to be stored, its data blocks may span more than one container file, or even more than one chunk folder. As another example, a database file of 20 GB may comprise over 40,000 data blocks of size 512 KB. If such a database file is to be stored, its data blocks will likely span multiple container files, multiple chunk folders, and potentially multiple volume folders. Restoring such files may require accessing multiple container files, chunk folders, and/or volume folders to obtain the requisite data blocks.
Using Backup Data for Replication and Disaster Recovery (“Live Synchronization”)
There is an increased demand to off-load resource intensive information management tasks (e.g., data replication tasks) away from production devices (e.g., physical or virtual client computing devices) in order to maximize production efficiency. At the same time, enterprises expect access to readily-available up-to-date recovery copies in the event of failure, with little or no production downtime.
At step 4, destination media agent(s) 244b write the received backup/secondary copy data to the destination secondary storage device(s) 208b. At step 5, the synchronization is completed when the destination media agent(s) and destination data agent(s) 242b restore the backup/secondary copy data to the destination client computing device(s) 202b. The destination client computing device(s) 202b may be kept “warm” awaiting activation in case failure is detected at the source. This synchronization/replication process can incorporate the techniques described in U.S. Patent Pub. No. 2016/0350391 entitled “Replication Using Deduplicated Secondary Copy Data.” Where the incremental backups are applied on a frequent, on-going basis, the synchronized copies can be viewed as mirror or replication copies. Moreover, by applying the incremental backups to the destination site 203 using backup or other secondary copy data, the production site 201 is not burdened with the synchronization operations. Because the destination site 203 can be maintained in a synchronized “warm” state, the downtime for switching over from the production site 201 to the destination site 203 is substantially less than with a typical restore from secondary storage. Thus, the production site 201 may flexibly and efficiently fail over, with minimal downtime and with relatively up-to-date data, to a destination site 203, such as a cloud-based failover site. The destination site 203 can later be reverse synchronized back to the production site 201, such as after repairs have been implemented or after the failure has passed.
Integrating With the Cloud Using File System Protocols
Given the ubiquity of cloud computing, it can be increasingly useful to provide data protection and other information management services in a scalable, transparent, and highly plug-able fashion.
Where NFS is used, for example, secondary storage subsystem 218 allocates an NFS network path to the client computing device 202 or to one or more target applications 210 running on client computing device 202. During a backup or other secondary copy operation, the client computing device 202 mounts the designated NFS path and writes data to that NFS path. The NFS path may be obtained from NFS path data 215 stored locally at the client computing device 202, and which may be a copy of or otherwise derived from NFS path data 219 stored in the secondary storage subsystem 218. Write requests issued by client computing device(s) 202 are received by data agent 242 in secondary storage subsystem 218, which translates the requests and works in conjunction with media agent 244 to process and write data to a secondary storage device(s) 208, thereby creating a backup or other secondary copy. Storage manager 240 can include a pseudo-client manager 216, which coordinates the process by, among other things, communicating information relating to client computing device 202 and application 210 (e.g., application type, client computing device identifier, etc.) to data agent 242, obtaining appropriate NFS path data from the data agent 242 (e.g., NFS path information), and delivering such data to client computing device 202. Conversely, during a restore or recovery operation, client computing device 202 reads from the designated NFS network path, and the read request is translated by data agent 242. The data agent 242 then works with media agent 244 to retrieve, re-process (e.g., re-hydrate, decompress, decrypt), and forward the requested data to client computing device 202 using NFS.
By moving specialized software associated with system 200 such as data agent 242 off the client computing devices 202, the illustrative architecture effectively decouples the client computing devices 202 from the installed components of system 200, improving both scalability and plug-ability of system 200. Indeed, the secondary storage subsystem 218 in such environments can be treated simply as a read/write NFS target for primary storage subsystem 217, without the need for information management software to be installed on client computing devices 202. As one example, an enterprise implementing a cloud production computing environment can add VM client computing devices 202 without installing and configuring specialized information management software on these VMs. Rather, backups and restores are achieved transparently, where the new VMs simply write to and read from the designated NFS path. An example of integrating with the cloud using file system protocols or so-called “infinite backup” using NFS share is found in U.S. Patent Pub. No. 2017/0235647 entitled “Data Protection Operations Based on Network Path Information.” Examples of improved data restoration scenarios based on network-path information, including using stored backups effectively as primary data sources, may be found in U.S. Pat. No. 10,684,924 entitled “Data Restoration Operations Based on Network Path Information.”
Highly Scalable Managed Data Pool Architecture
Enterprises are seeing explosive data growth in recent years, often from various applications running in geographically distributed locations.
Media agents SMA1-SMA6 assigned to the secondary tier 233 receive write and read requests from media agents CMA1-CMA3 in control tier 231, and access secondary storage pool 208 to service those requests. Media agents CMA1-CMA3 in control tier 231 can also communicate with secondary storage pool 208, and may execute read and write requests themselves (e.g., in response to requests from other control media agents CMA1-CMA3) in addition to issuing requests to media agents in secondary tier 233. Moreover, while shown as separate from the secondary storage pool 208, deduplication database(s) 247 can in some cases reside in storage devices in secondary storage pool 208. As shown, each of the media agents 244 (e.g., CMA1-CMA3, SMA1-SMA6, etc.) in grid 245 can be allocated a corresponding dedicated partition 251A-251I, respectively, in secondary storage pool 208. Each partition 251 can include a first portion 253 containing data associated with (e.g., stored by) media agent 244 corresponding to the respective partition 251. System 200 can also implement a desired level of replication, thereby providing redundancy in the event of a failure of a media agent 244 in grid 245. Along these lines, each partition 251 can further include a second portion 255 storing one or more replication copies of the data associated with one or more other media agents 244 in the grid.
System 200 can also be configured to allow for seamless addition of media agents 244 to grid 245 via automatic configuration. As one illustrative example, a storage manager (not shown) or other appropriate component may determine that it is appropriate to add an additional node to control tier 231, and perform some or all of the following: (i) assess the capabilities of a newly added or otherwise available computing device as satisfying a minimum criteria to be configured as or hosting a media agent in control tier 231; (ii) confirm that a sufficient amount of the appropriate type of storage exists to support an additional node in control tier 231 (e.g., enough disk drive capacity exists in storage pool 208 to support an additional deduplication database 247); (iii) install appropriate media agent software on the computing device and configure the computing device according to a pre-determined template; (iv) establish a partition 251 in the storage pool 208 dedicated to the newly established media agent 244; and (v) build any appropriate data structures (e.g., an instance of deduplication database 247). An example of highly scalable managed data pool architecture or so-called web-scale architecture for storage and data management is found in U.S. Pat. No. 10,255,143 entitled “Deduplication Replication In A Distributed Deduplication Data Storage System.”
The embodiments and components thereof disclosed in
The embodiments and components thereof disclosed in
Cloud Computing. The National Institute of Standards and Technology (NIST) provides the following definition of Cloud Computing characteristics, service models, and deployment models:
Cloud Computing
Essential Characteristics:
Service Models:
Deployment Models:
Source: Peter Mell, Timothy Grance (September 2011). The NIST Definition of Cloud Computing, National Institute of Standards and Technology: U.S. Department of Commerce. Special publication 800-145. nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf (accessed 26 Apr. 2019). Cloud computing aims to allow those who consume the services (whether individuals or organizations) to benefit from the available technologies without the need for deep knowledge about or expertise with each of them. Wikipedia, Cloud Computing, en.wikipedia.org/wiki/Cloud computing (accessed 26 Apr. 2019). “Cloud computing metaphor: the group of networked elements providing services need not be individually addressed or managed by users; instead, the entire provider-managed suite of hardware and software can be thought of as an amorphous cloud.” Id.
Cloud Service Accounts and Variability in Cloud Services. Cloud service providers such as Amazon, Microsoft, Alibaba, Google, Salesforce, Cisco, etc. provide access to their particular cloud services via cloud service accounts, such as corporate accounts, departmental accounts, individual user accounts, etc. Each cloud service account typically has authentication features, e.g., passwords, certificates, etc., to restrict and control access to the cloud service. Each account also might have service level guarantees and/or other terms and conditions between the cloud service provider and the service subscriber, e.g., a company, a government agency, an individual user. A subscribing entity might have multiple accounts with a cloud service provider, such as an account for the Engineering department, an account for the Finance department, an account for the Human Resources department, other accounts for individual company users, etc., without limitation. Each cloud service account carries different authentication, even though the services subscriber is the same entity. Different cloud service accounts might differ not just in service level guarantees, but might include different services. For example, one account might include long-term storage resources, whereas another account might be limited to ordinary data storage. For example, some accounts might have access to data processing functions supplied by the cloud service provider, such as machine learning algorithms, statistical analysis packages, etc., whereas other accounts might lack such features. Accordingly, the resources available to the user(s) of cloud service accounts can vary as between accounts, even if the accounts have the same subscriber and the same cloud service provider. Thus, the user experience and the technologies available as between cloud service accounts can vary significantly.
Traditional Non-Cloud (“On-Premises”) Data Centers are Distinguishable from Cloud Computing. Traditional data centers generally do not have cloud computing characteristics. For example, the user experience is generally different, for example in regard to the name space(s) used for the storage, computing, and network resources. Moreover, substantial increases in resources needed by a user are not provisioned on demand. A traditional data center is physically located within the enterprise/organization that owns it. A traditional non-cloud data center might comprise computing resources such as servers, mainframes, virtual servers/clusters, etc.; and/or data storage resources, such as network-attached storage, storage area networks, tape libraries, etc. The owner of the traditional data center procures hardware, software, and network infrastructure (including making the associated capital investments); and manages going-forward planning for the data center. A traditional data center is staffed by professional Information Technology (IT) personnel, who are responsible for the data center's configuration, operation, upgrades, and maintenance. Thus, a traditional non-cloud data center can be thought of as self-managed by its owner/operator for the benefit of in-house users, as compared to cloud computing, which is managed by the cloud service provider and supplied as a service to outside subscribers. Clearly, a cloud computing service also has hardware, software, and networking infrastructure and professionals staffing it, as well as having an owner responsible for housing and paying for the infrastructure. However, the cloud computing service is consumed differently, served differently, and deployed differently compared to non-cloud data centers. Traditional non-cloud data centers are sometimes referred to as “on-premises” data centers, because their facilities are literally within the bounds of the organization that owns the data center. Cloud service providers' data centers generally are not within the bounds of the subscriber organization and are consumed “at a distance” “in the cloud.”
Accordingly, when considering cloud computing versus non-cloud data center deployment, the choice can play a role in the availability and/or portability of resources. Crossing boundaries between non-cloud data centers and cloud computing can pose technological barriers. For example, storing a database at a non-cloud data center might require different resources and/or access features/controls than storing the database at a cloud computing service. Thus, moving the database from the non-cloud data center to a cloud service account may require data conversion, re-configuration, and/or adaptation that go above and beyond merely copying the database. Likewise for virtual machines (VMs). Conversely, moving data, applications, VMs, and/or web services from cloud computing to a non-cloud data center also can involve data conversion, re-configuration, and/or adaptation to ensure success.
Enforcing a Recovery Point Objective (RPO) for A Production Database without Generating Secondary Copies of the Production Database
A disclosed framework enables virtually any aggressive Recovery Point Objective (RPO) to be enforced for a production database, without limitation on type of database management system (DBMS) or size of the production database. The framework overcomes technological barriers of the prior art, such as bottlenecks presented by a storage manager computer that traditionally managed database backups. To avoid the bottlenecks, an illustrative data storage management system does not engage the storage manager computer in storage operations that could impact the database RPO. Certain components are added and enhanced to autonomously capture database transaction logs, which are stored securely and persistently away from the DBMS. In a separate and less frequent operation, and with involvement of the storage manager computer, the illustrative system generates secondary copies in their final form. Meanwhile, temporary backup files can be used in restore operations without first being converted into secondary copies.
The disclosed system architecture is suitable for cloud and non-cloud deployments, and combinations thereof, without limitation. Accordingly, in a cloud computing environment, any computer, server, host, and/or computing device described herein is deployed as a compute resource of the cloud computing environment (e.g., a virtual machine instance, a pod in a Kubernetes cluster or in another application orchestrator, etc.). Although the compute resource is accessed as a service, it is provided by one or more hardware processors and associated computer memory. Likewise, in a cloud computing environment, any data storage device or data storage resource described herein may be deployed as a cloud storage service of the cloud computing environment (e.g., “Blob Storage” on Microsoft Azure, Amazon Simple Storage Service (“Amazon S3”), etc.). Although the storage is accessed as a service, it is provided by one or more underlying data storage devices.
System 300 is a data storage management system, which is analogous to systems 100 and/or 200, and which is additionally enhanced with features for enforcing an RPO for a production database (e.g., 312) without concurrently and without necessarily generating secondary copies 116 of the production database. System 300 illustratively comprises the following components, without limitation: client computing device 102 and/or database data agent 342; secondary storage device 106 and/or media agent 344 and/or data agent 442 (shown in
Client computing device (a/k/a DBMS host) 102 is a computing device that comprises one or more hardware processors. In the disclosed system architecture, component 102 hosts DBMS 312, and may be referred to herein as DBMS host 312. Client computing device 102 preferably hosts database data agent 342. Secondary storage computing device 106 is a computing device that comprises one or more hardware processors. In the disclosed system architecture, component 106 hosts media agent 344 and preferably also hosts a file system data agent 442 (shown in
DBMS 310 is a database management system, which is well known in the art. DBMS 310 may be of any type, e.g., DB2, Oracle, SQL, MySQL, etc., without limitation. DBMS 310 is part of a production environment, generating and managing live data. Production database 312 comprises one or more data structures, which are organized, maintained, and populated by DBMS 310 according to a schema (not shown here). Production database 312 is well known in the art. System 300 is not limited as to type of DBMS 310, type of production database 312, or size thereof. DBMS 310 comprises production database 312, but the data structure(s) of database 312 may be physically stored in storage resources that are not physically part of DBMS host 102, without limitation. Transaction logs 314 (e.g., 314-1 . . . 314-N) are data structures that comprise information reflecting one or more transactions applied by DBMS 310 upon production database 312, e.g., add, delete, change, move, etc., without limitation. Transaction logs 314 are typically generated by DBMS 310 in a data format native to DBMS 310 and/or to production database 312. A transaction log 314 may be played back to or applied to or incorporated into database 312 (typically by DBMS 310) to restore the information carried in the transaction log in case of loss or corruption of database 312. In some scenarios, such as a restore operation managed by system 300, database data agent 342 instructs DBMS 310 to play back certain transaction logs 314 to complete the restore operation and restore database 312 to a desired point in time. Transaction logs 314 are shown here as being stored at DBMS host 102, but in some embodiments they are stored in a separate and associated data storage resource instead (not shown here), without limitation.
Database data agent 342 is analogous to data agent 142 and additionally comprises certain features for operating in system 300, e.g., generating temporary backup files in a secure and proprietary format for transmission to media agent 344; operating according to an RPO interval configured for production database 312, etc., without limitation. See also
Pipeline 343 is a proprietary and persistent data communication connection between database data agent 342 and media agent 344. Pipeline 343 thus provides a secure data pathway between DBMS host 102 and secondary storage computing device 106. In configurations where pipeline 343 traverses the public internet or another public data network, the security features of pipeline 343 are especially valuable. By using the proprietary and persistent data pipeline 343, media agent 344 need not open a data port on demand at secondary storage computing device 106 for purposes of receiving data from data agent 342. In a public internet or other public network setting, being able to operate without opening ports on demand boosts communications security. In addition, the data travelling over pipeline 343 is encrypted by database data agent 342, thus adding another security boost. Moreover, pipeline 343 can write securely to any target, whether local (e.g., disk) or remote (e.g., cloud storage), and thus enables a variety of configurations of system 300.
In some embodiments, pipeline 343 comprises a proprietary “DataPipe” from Commvault Systems, Inc., which is described in detail in U.S. Pat. No. 6,418,478, which is incorporated by reference herein. “A DataPipe comprises a named set of tasks executing within one or more computers that cooperate with each other to transfer and process data in a pipelined manner. Within a DataPipe, a pipeline concept is used to improve performance of data transfer across multiple computers in a network. However, within a DataPipe, any stage within the pipeline may have multiple instances, thus greatly increasing the scaleability and performance of the basic pipeline concept.” Id. “In addition to the transferring of data from one computer to another, [DataPipe has] the ability to scale to enable full utilization of the bandwidth of a network, and to fully utilize . . . hardware components such as CPUs. The scaleability of a DataPipe is achieved by using multiple instances of each task in the pipeline.” Id. Additionally, as noted earlier, pipeline 343 provides a secure data pathway between DBMS host 102 and secondary storage computing device 106, which has many advantages.
Media agent 344 is analogous to media agent 144 and additionally comprises features for operating in system 300, e.g., persisting temporary backup files 350 at “dump repository” 345 without processing them further into secondary copies 116; operating according to a sweep interval to perform sweep jobs; checking “dump repository” 345 on restore operations, etc., without limitation. In some embodiments, media agent 344 is programmed or configured with the sweep interval, and based on the sweep interval, media agent 344 initiates sweep jobs or causes sweep jobs to be initiated at secondary storage computing device 106. See also
“Dump repository” or “data repository” 345 is a term used as a convenient shorthand for a specially-configured data storage resource where media agent 344 stores temporary backup files 350 persistently. The “dump repository” 345 in some embodiments is configured as a data storage volume, a drive, or a folder at secondary storage computing device 106 (e.g. occupying one or more disks). A file system (not shown here) at the secondary storage computing device comprises the volume, drive, or folder. Media agent 344 accumulates temporary backup files 350 at its “dump repository” 345 on an ongoing basis, as received via the proprietary and persistent data pipeline 343. Notably in contrast to prior art configurations, the operations that generate, transmit, and store the temporary backup files occur without involvement of storage manager 440, which eliminates the possibility of the storage manager becoming a bottleneck that impedes the timely safeguarding of transaction logs 314 (stored as temporary backup files 350 at “dump repository” 345). Thus, having components 342 and 344 working together to generate and persistently store temporary backup files 350, yet doing so autonomously of storage manager 440, provides an added level of assurance that the desired RPO can be met for production database 312. Temporary backup files 350 (e.g., 350-1 . . . 350-M) are illustrative data structures that comprise one or more transaction logs 314. As noted above, database data agent 342 generates temporary backup files 350 in a compressed and encrypted format for transmission to media agent 344 over pipeline 343. In some embodiments, each temporary backup file 350 comprises only one corresponding transaction log 314, resulting in a one-to-one correspondence with the source data, whereas in other embodiments, a temporary backup file 350 comprises multiple transaction logs 314; or any combination thereof, without limitation.
Secondary storage 108 comprises one or more data storage resources, whether configured in a cloud as a cloud storage service and/or in a non-cloud data center as one or more data storage devices, without limitation. Secondary copies 116 are described in more detail elsewhere herein. Here, secondary copies 116 comprise copies (e.g., backup copies), which are generated or constructed by media agent 344 and/or file system data agent 442 from one or more temporary backup files 350 retrieved from “data repository” 345. According to an embodiment, secondary copies 116 are generated in a sweep job and are indexed by media agent 344, which, for example stores indexing information in media agent index 153 (not shown in the present figure). In contrast, temporary backup files 350 are stored in “dump repository” 345 without indexing in the interest of speed. They reside in “dump repository” 345 until, in a sweep job, they can be fully converted into secondary copies 116, which includes indexing as well as metadata reporting back to storage manager 440.
Storage manager host 402 is a computing device that comprises one or more hardware processors. In the disclosed system architecture, component 402 hosts storage manager 440 and preferably, also hosts management database 146. Storage manager 440 is analogous to storage manager 140 and additionally comprises features for operating in system 300. Storage manager 440 is generally responsible for intaking administrative preferences and parameters for system 300, such as RPO interval, sweep interval, etc., and storing them in management database 146. Storage manager 440 is also generally responsible for managing storage operations in system 300, but as described herein, system 300 provides for some storage operations to be performed autonomously without involvement from storage manager 440, such as the generation, transmission, and persistent storage of temporary backup files 350. In regard to system 300, storage manager 440 receives administrative parameters for an RPO time interval associated with production database 312, e.g., 2 minutes, etc. and in addition to saving the parameter in management database 146, storage manager 440 also configures database data agent 342 with this parameter. Likewise in regard to system 300, storage manager 440 receives a schedule or a time interval for sweep jobs associated with production database 312, e.g., 6 hours, 24 hours, etc. and in addition to saving the schedule or time interval in management database 146, storage manager 440 also configures one or more of file system data agent 442 and media agent 344 with this information. In most embodiments, the sweep interval is much longer than the RPO for the production database. In some embodiments, storage manager 440 is configured to transmit the RPO to database data agent 342, and is further configured to subsequently not cause database data agent 342 to generate temporary backup files 350 for transmission to media agent 344. In some embodiments, storage manager 440 is configured not to initiate a sweep data storage job, whereas the secondary storage computing device 106 is configured to initiate the sweep data storage job based on sweep time interval. Management database 146 is described in more detail in other figures. Management database 146 is a component of system 300 and helps to operate system 300 and is distinguishable from production database 312.
File system data agent 442 is analogous to data agent 142 (e.g., 142A) and additionally comprises features for operating in system 300, e.g., cataloguing “dump repository” 345; obtaining temporary backup files 350 from “dump repository” 345; interoperating with media agent 344 in sweep jobs; etc., without limitation. In some embodiments, file system data agent 442 is programmed or configured with a sweep interval, and based on the sweep interval, file system data agent 442 initiates sweep jobs at secondary storage computing device 106. In other embodiments, media agent 344 is programmed or configured with the sweep interval, and based on the sweep interval, media agent 344 initiates sweep jobs at secondary storage computing device 106. File system data agent 442 represents an addition to system 300 that would not have been needed in the prior art. Adding file system data agent 442 into the process of making secondary copies 116 based on production database 312 is one of the enhancements that enables system 300 to avoid the storage manager becoming a bottleneck. As depicted in
At block 502, system 300 activates a data agent (e.g., database data agent 342, activated by storage manager 440) at DBMS host 102. Further, pipeline 343 is established between database data agent 342 and media agent 344. As noted earlier, pipeline 343 is maintained “open” (persistent) so long as its endpoints, i.e., database data agent 342 and media agent 344, are operational, or unless expressly disabled for other reasons. Further, an RPO time interval for production database 312 is received in administration (e.g., 2 minutes), saved by storage manager 440 to management database 146, and downloaded by storage manager 440 into database data agent 342. A sweep interval or sweep job schedule is received in administration (e.g., 24 hours), saved by storage manager 440 to management database 146, and downloaded by storage manager 440 into one or more of file system data agent 442 or media agent 344 at secondary storage computing device 106. Collectively the timing preferences administered for the RPO and the sweep jobs may be referred to herein as “timing parameters,” e.g., RPO timing parameter, sweep job timing parameter.
At block 504, system 300 (e.g., using database data agent 342) collects database transaction logs 314 from DBMS 310, converts transaction logs 314 into temporary backup files 350 in a secure proprietary backup format, and uses pipeline 343 to transmit temporary backup files 350 to media agent 344 at the RPO interval (e.g., every 2 minutes). At block 506, system 300 (e.g., using media agent 344) persists temporary backup files 350 at the media agent's “dump repository” 345. Preferably, temporary backup files 350 are stored without further processing in the interest of speed, though media agent 344 assigns file names that are unique and provide information for future use, e.g., timestamp, data source identifier(s), data agent identifier, etc., without limitation. Temporary backup files 350 will be processed into secondary copies 116 at another time, when a sweep job is performed. Blocks 504 and 506 iterate indefinitely, so long as production database 312 needs to be protected by system 300. These blocks operate without involvement of storage manager 440, according to the illustrative embodiments.
At block 508, system 300 (e.g., using file system data agent 442 or media agent 344 at secondary storage computing device 106) determines that the sweep interval has arrived (e.g., every 24 hours) and that it is time to check “dump repository” 345 to determine whether any temporary backup files 350 reside therein. In some embodiments, file system data agent 442 performs this task by cataloguing “dump repository” 345. If “dump repository” 345 is empty, no further action is presently required and control passes back to block 504. However, if one or more temporary backup files 350 are found in “dump repository” 345, a sweep job is triggered by passing control to block 510.
Block 510 is triggered by the need to perform a sweep job. Accordingly, system 300 (e.g., using file system data agent 442 or media agent 344 at secondary storage computing device 106) asks storage manager 440 for a job ID for a sweep job. Responsive to this request, storage manager 440 creates a job ID for the sweep job and instructs file system data agent 442 and media agent 344 to perform the sweep job, which converts temporary backup files 350 found in “dump repository” 345 into secondary copies 116. Illustratively, file system data agent 442 picks temporary backup files 350 from “dump repository” 345 in a suitable sequence and passes them to media agent 344 for further processing. Because the temporary backup files 350 are already formatted according to the secure proprietary backup format of system 300 (see, e.g., block 504), relatively little further processing is needed in the sweep job, as compared to traditional prior art backup jobs. The sweep job includes indexing performed by media agent 344 and storing of secondary copies 116 into secondary storage 108, also performed by media agent 344. On completing their tasks, file system data agent 442 and media agent 344 report to storage manager 440, which includes reporting of metadata, such as statistics of the amount of data backed up, the number of files saved as secondary copies, timestamps, identity of secondary storage 108 where secondary copies 116 were stored, etc., without limitation. Preferably, temporary backup files 350 are deleted from “dump repository” 345 substantially concurrently with the sweep job being reported completed to storage manager 440. Preferably, metadata associated with temporary backup files 350 (e.g., timestamps of the transaction logs 314) is retained in generating secondary copies 116 (e.g., stored in media agent index 153), so that in restore operations the transaction logs 314 can be unpacked and restored to a desired point in time.
At block 512, system 300 (e.g., using storage manager 440) updates management database 146 with metadata of the sweep job. Included in this metadata is certain indexing information that associates the secondary copies 116 with the job ID of the sweep job. This and other metadata will enable system 300 to find the secondary copies generated in the present sweep job at a future time, e.g., for a restore or migration operation. At block 514, system 300 considers the present sweep job to be complete. Because the temporary backup files 350 that were processed in the present sweep job were generated based on the RPO established for production database 312, the sweep job is said to also be based on the same RPO, even though the sweep job was performed less frequently, based on the sweep interval. Method 500 ends here.
At block 602, system 300 (e.g., using storage manager 440) receives a request to restore data to production database 312 (or to migrate data to another database). The request may be received via a user interface (not shown) or via an automated request, such as an automated test operation, an automated disaster recovery operation, an automated failover operation, etc., without limitation.
At block 604, system 300 (e.g., using media agent 344 at secondary storage computing device 106) checks whether “dump repository” 345 comprises any temporary backup files 350 that are suitable for the present restore job. For example, media agent 344 may check “dump repository” 345 for contents; alternatively, media agent 344 may instruct file system data agent 442 to report on the contents of “dump repository” 345, e.g., by cataloguing “dump repository” 345. Media agent 344 is configured to determine whether, based on point-in-time information provided by storage manager 440 for the restore request, any temporary backup files 350 are suitable for the present restore job. If “dump repository” 345 is empty or lacks temporary backup files 350 that are suitable for the present restore operation, control passes to block 612. Otherwise, control passes to block 606.
At block 606, system 300 (e.g., using storage manager 440) initiates a restore job responsive to the restore request. Illustratively, storage manager 440 assigns a job ID to the restore job and instructs media agent 344 to perform the requested restore. The instruction may include timeframe information to enable restoring data to a certain desired point in time. Control passes to block 608. At block 608, system 300 (e.g., using media agent 344 at secondary storage computing device 106) obtains (extracts, reads, retrieves) one or more temporary backup files 350 from “dump repository” 345, and control passes to block 610. At block 610, system 300 (e.g., using media agent 344 at secondary storage computing device 106) transmits the one or more temporary backup files 350 to database data agent 342 over pipeline 343. As in block 504, pipeline 343 operates as a secure electronic transportation pathway. From block 610, control passes to block 616. In some embodiments, if secondary copies 116 also are to be restored in the present restore job, control also passes to block 614 for that purpose.
Block 612 is reached by system 300 when block 604 finds no (or no suitable) temporary backup files 350 in “dump repository” 345. At block 612, system 300 (e.g., using storage manager 440) initiates a restore job responsive to the restore request, but based entirely on secondary copies 116 and exclusive of temporary backup files 350. Illustratively, storage manager 440 assigns a job ID to the restore job and instructs media agent 344 to perform the requested restore. The instruction may include timeframe information to enable restoring data to a certain desired point in time. Block 612 is shown in a dotted outline to emphasize the fact that system 300 is configured to restore data from temporary backup files 350 without ever needing to access secondary copies 116 and may never reach block 612. Thus, system 300 can enforce an RPO for a production database such as database 312 without generating secondary copies 116 of the production database and instead creating any number of temporary backup files 350. By correlation, system 300 can restore data to the production database without relying on secondary copies 116, if they have not been created as yet or if they are not needed to reach the desired point-in-time of the restore operation. Instead, in some scenarios, a restore job may be successfully completed in system 300 only from temporary backup files 350 (block 608). Control passes from block 612 to block 614. At block 614, system 300 (e.g., using media agent 344 at secondary storage computing device 106) obtains (extracts, reads, retrieves) one or more secondary copies 116 from secondary storage 108. In some embodiments, media agent 344 uses its media agent index 153 to identify the proper secondary copies 116 that satisfy criteria of the restore request (e.g., point in time, data grouping, subclient, etc.). Media agent 344 processes these secondary copies 116 to prepare them for transmission to database data agent 342 at block 610. Preparation may involve rehydration of deduplicated data, stripping out certain metadata, indexing, and/or headers, decryption and/or decompression, if any, added when secondary copies 116 were created, etc. Like block 612, block 614 is shown in a dotted outline to emphasize the fact that system 300 is configured to restore data from temporary backup files 350 without ever needing to access secondary copies 116. Control passes from block 614 to block 610, where media agent 344 uses pipeline 343 to transmit “prepared” secondary copies 116 to database data agent 342.
At block 616, system 300 (e.g., using database data agent 342 at DBMS host 102) receives the data stream(s) transmitted by media agent 344 over pipeline 343. Database data agent 342 unpacks the received data stream(s). Illustratively, database data agent 342 reverses the encryption and compression applied to the data stream(s) of pipeline 343 at media agent 344. Further, database data agent 342 converts the resultant data from the proprietary backup format of temporary backup files 350 and/or secondary copies 116 received over pipeline 343 into a native format of DBMS 310. Thus, database data agent 342 transforms data received over pipeline 343 into native-formatted restored transaction logs 314. Database data agent 342 stores the restored transaction logs 314 at DBMS host 310. At block 618, system 300 (e.g., using database data agent 342 at DBMS host 102) uses an application programming interface (API) or other feature to instruct DBMS 310 to apply or play back the restored transaction logs 314 to production database 312. Database data agent 342 may use the API or another feature to quiesce production database 312 before playback of the restored transaction logs 314, and to unquiesce production database 314 once playback of all the pending restored transaction logs 314 is complete. Upon completion, database data agent 342 may report completion to media agent 344 and/or to storage manager 440. Media agent 344 may update certain indexing information in its media agent index 153. At the completion of block 618, system 300 considers the present restore job to be complete. Storage manager 440 updates management database 146 accordingly, recording statistics and metadata associated with the restore job. Restore jobs in which temporary backup files 350 were restored, are said to be based on temporary backup files. This aspect contrasts with restore operations in the prior art, in which data is restored from secondary copies 116 and not from temporary backup files 350 (e.g., blocks 612, 614). Method 600 ends here.
In regard to the figures described herein, other embodiments are possible within the scope of the present invention, such that the above-recited components, steps, blocks, operations, messages, requests, queries, and/or instructions are differently arranged, sequenced, sub-divided, organized, and/or combined. In some embodiments, a different component may initiate or execute a given operation. For example, in some embodiments, file system data agent 442 and media agent 344 are not distinct components, and instead collectively form a computer program that executes at secondary storage computing device 106, and thus secondary storage computing device 106 is said to perform the above-recited operations attributed to file system data agent 442 and media agent 344. For example, in some embodiments, the RPO interval and the sweep interval are populated (e.g., by storage manager 440) as operational parameters stored at client computing device 102 and/or at secondary storage computing device 106 and are obtained therefrom by one or more of database data agent 342, media agent 344, and/or file system data agent 442 to trigger block 504 and 508 of method 500.
Some example enumerated embodiments are recited in this section in the form of methods, systems, and non-transitory computer-readable media, without limitation.
According to an example embodiment, a computer-implemented method, which is performed by one or more hardware processors, comprises: activating a first data agent at a first computing device, wherein the first computing device hosts a database management system that comprises a first database, wherein the first data agent is associated with the database management system; by the first data agent, converting a first set of transaction logs generated by the database management system into a first set of temporary backup files, wherein the first set of temporary backup files are in a backup format that comprises encryption; based on a time interval of a recovery point objective (RPO) associated with the first database, transmitting the first set of temporary backup files over a persistent data pipeline connection to a second computing device; by the second computing device, storing the first set of temporary backup files persistently at a data repository of the second computing device. The above-recited embodiment, wherein the method further comprises: based on a second time interval that is greater than the time interval of the RPO, determining by the second computing device whether the data repository comprises any temporary backup files. The above-recited embodiment, wherein the method further comprises: based on the second computing device determining that the data repository comprises at least one temporary backup file, performing a data storage job that converts the at least one temporary backup file into one or more secondary copies and storing the one or more secondary copies at a secondary storage that is distinct from the data repository. The above-recited embodiment, wherein the data storage job comprises indexing the one or more secondary copies in an index maintained at the second computing device. The above-recited embodiment, wherein the data storage job further comprises reporting information about the data storage job to a storage manager that executes on a third computing device, which is distinct from the first computing device and from the second computing device.
The above-recited embodiment, wherein the first data agent generates the first set of temporary backup files without receiving one or more instructions to do so from the storage manager. The above-recited embodiment, wherein the first data agent receives the RPO from the storage manager after the first data agent is activated, and subsequently the first data agent does not receive one or more instructions from the storage manager to generate the first set of temporary backup files. The above-recited embodiment, wherein the first data agent is configured to determine, based on the time interval of the RPO, that the first data agent should initiate the transmitting of the first set of temporary backup files over the persistent data pipeline connection to the second computing device. The above-recited embodiment, wherein the storage manager is configured to transmit the RPO to the first data agent, and is further configured to subsequently not cause the first data agent to generate the first set of temporary backup files. The above-recited embodiment, wherein the storage manager is configured not to initiate the data storage job, and wherein the second computing device is configured to initiate the data storage job based on the second time interval. The above-recited embodiment, wherein the second computing device is configured to determine, based on the second time interval, that the second computing device should initiate the data storage job by requesting a job identifier from the storage manager. The above-recited embodiment, wherein the second computing device is configured to initiate the data storage job, based on the second time interval, wherein initiating the data storage job comprises requesting a job identifier for the data storage job from the storage manager; and further comprising: based on receiving the job identifier from the storage manager, performing the data storage job by a media agent and a second data agent that execute at the second computing device. The above-recited embodiment, wherein the data repository comprises one or more of a data storage volume and a folder configured at the second computing device, and wherein the second data agent is associated with a file system that comprises the one or more of the data storage volume and the folder. The above-recited embodiment, wherein the time interval of the RPO is substantially more frequent than the second time interval.
The above-recited embodiment further comprising: by the storage manager, receiving a request to restore data to the first database; by the second computing device, determining whether the data repository comprises a second set of temporary backup files that comprise the data to be restored to the first database. The above-recited embodiment further comprising: initiating, by the storage manager, a restore job at the second computing device, wherein the restore job is based on the second set of temporary backup files. The above-recited embodiment further comprising: by the second computing device, transmitting the second set of temporary backup files over the persistent data pipeline connection to the first data agent at the first computing device. The above-recited embodiment further comprising: by the first data agent, converting the second set of temporary backup files into a second set of transaction logs, wherein the second set of transaction logs are in a format that is native to the database management system. The above-recited embodiment, wherein the time interval of the RPO is substantially more frequent than the second time interval. The above-recited embodiment further comprising: by the storage manager, maintaining in a management database that is distinct from the first database, the RPO and the second time interval, and wherein the storage manager stores the information about the data storage job received from the second computing device into the management database.
According to another example embodiment, a system comprises: a second computing device comprising one or more hardware processors, wherein the second computing device is communicatively coupled to a first computing device via a persistent data pipeline connection to a first data agent that executes at the first computing device, and wherein the first computing device additionally executes a database management system that comprises a first database, which is associated with a recovery point objective (RPO); wherein the first computing device executing the first data agent is configured to: convert a first set of transaction logs generated by the database management system into a first set of temporary backup files, wherein the first set of temporary backup files are in a backup format that comprises encryption, and based on a time frequency of the RPO, transmit the first set of temporary backup files over the persistent data pipeline connection to the second computing device; wherein the second computing device is configured to: store the first set of temporary backup files persistently at a data repository that comprises one or more of a data storage volume and a folder configured at the second computing device.
The above-recited embodiment further comprising: a third computing device comprising one or more hardware processors, wherein the third computing device executes a storage manager. The above-recited embodiment further comprising: based on a second time frequency that is greater than the time frequency of the RPO, determine whether the data repository comprises any temporary backup files, and based on determining that the data repository comprises at least one temporary backup file, perform a data storage job that: converts the at least one temporary backup file into one or more secondary copies, stores the one or more secondary copies at a secondary storage, which is distinct from the data repository, indexes the one or more secondary copies in an index maintained at the second computing device, and reports information about the data storage job to the storage manager at the third computing device. The above-recited embodiment wherein the third computing device executing the storage manager is configured to: transmit the RPO to the first data agent, and afterwards not cause the first data agent to transmit the first set of temporary backup files over the persistent data pipeline connection to the second computing device, and transmit the second time frequency to the second computing device, and afterwards not initiate the data storage job. The above-recited embodiment wherein the first data agent executing at the first computing device is configured to autonomously and without receiving instructions from the storage manager: determine, based on the time frequency of the RPO, that the first data agent should transmit the first set of temporary backup files over the persistent data pipeline connection to the second computing device. The above-recited embodiment wherein the first data agent executing at the first computing device is configured to autonomously and without receiving instructions from the storage manager: generate the first set of temporary backup files, and transmit the first set of temporary backup files over the persistent data pipeline connection to the second computing device. The above-recited embodiment wherein the second computing device is further configured to: autonomously and without receiving instructions from the storage manager: determine, based on the second time frequency, that the second computing device should initiate the data storage job by requesting a job identifier from the storage manager. The above-recited embodiment wherein the third computing device executing the storage manager is further configured to: based on receiving a request for the job identifier from the second computing device, cause a media agent and a second data agent that execute at the second computing device to perform the data storage job. The above-recited embodiment wherein the second data agent is associated with a file system that comprises the one or more of the data storage volume and the folder of the data repository.
The above-recited embodiment wherein the third computing device executing the storage manager is further configured to: responsive to a request to restore data to the first database, initiate a restore job at the second computing device. The above-recited embodiment wherein the second computing device is further configured to: based on determining that the data repository comprises a second set of temporary backup files that correspond to the data requested to be restored to the first database, transmit the second set of temporary backup files over the persistent data pipeline connection to the first data agent at the first computing device. The above-recited embodiment wherein the first computing device executing the first data agent is further configured to: convert the second set of temporary backup files into a second set of transaction logs, wherein the second set of transaction logs are in a format that is native to the database management system, and cause the database management system to play back the second set of transaction logs to restore data therein to the first database. The above-recited embodiment wherein the third computing device executing the storage manager comprises a management database that is distinct from the first database, wherein the management database comprises: the RPO, the second time frequency, and the information about the data storage job received from the second computing device.
In other embodiments according to the present invention, a system or systems operates according to one or more of the methods and/or computer-readable media recited in the preceding paragraphs. In yet other embodiments, a method or methods operates according to one or more of the systems and/or computer-readable media recited in the preceding paragraphs. In yet more embodiments, a non-transitory computer-readable medium or media causes one or more computing devices having one or more processors and computer-readable memory to operate according to one or more of the systems and/or methods recited in the preceding paragraphs.
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. Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense, i.e., in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words using the singular or plural number may also include the plural or singular number respectively. The word “or” in reference to a list of two or more items, covers all of the following interpretations of the word: any one of the items in the list, all of the items in the list, and any combination of the items in the list. Likewise the term “and/or” in reference to a list of two or more items, covers all of the following interpretations of the word: any one of the items in the list, all of the items in the list, and any combination of the items in the list.
In some embodiments, certain operations, 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 altogether (e.g., not all are necessary for the practice of the algorithms). In certain embodiments, operations, acts, functions, 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. Software and other modules may reside and execute on servers, workstations, personal computers, computerized tablets, PDAs, and other computing devices suitable for the purposes described herein. Software and other modules may be accessible via local computer 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, interactive voice response, command line interfaces, and other suitable interfaces.
Further, processing of the various components of the illustrated systems can be distributed across multiple machines, networks, and other computing resources. 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 and/or computing devices. Likewise, the data repositories shown can represent physical and/or logical data storage, including, e.g., 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, specially-equipped computer (e.g., comprising a high-performance database server, a graphics subsystem, etc.) or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor(s) 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 non-transitory 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 to a computing device or other programmable data processing apparatus to cause operations to be performed on the computing device or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computing device or other programmable apparatus provide steps for implementing the acts specified in the flow chart and/or block diagram block or blocks.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further implementations of the invention. These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain examples of the invention, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.
To reduce the number of claims, certain aspects of the invention are presented below in certain claim forms, but the applicant contemplates other aspects of the invention in any number of claim forms. For example, while only one aspect of the invention is recited as a means-plus-function claim under 35 U.S.C. sec. 112(f) (AIA), other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. Any claims intended to be treated under 35 U.S.C. § 112(f) will begin with the words “means for,” but use of the term “for” in any other context is not intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly, the applicant reserves the right to pursue additional claims after filing this application, in either this application or in a continuing application.
| 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 |
| 5231668 | Kravitz | 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 | 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 |
| 5598546 | Blomgren | Jan 1997 | A |
| 5604862 | Midgely et al. | Feb 1997 | A |
| 5606693 | Nilsen et al. | Feb 1997 | A |
| 5615392 | Harrison et al. | Mar 1997 | A |
| 5619644 | Crockett et al. | Apr 1997 | A |
| 5623599 | Shomler | Apr 1997 | A |
| 5638509 | Dunphy et al. | Jun 1997 | A |
| 5642496 | Kanfi | Jun 1997 | A |
| 5649152 | Ohran et al. | Jul 1997 | A |
| 5664186 | Bennett et al. | Sep 1997 | A |
| 5668986 | Nilsen et al. | Sep 1997 | A |
| 5673381 | Huai et al. | Sep 1997 | A |
| 5675511 | Prasad et al. | Oct 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 |
| 5745753 | Mosher, Jr. | 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 |
| 5802265 | Bressoud et al. | Sep 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 |
| 5829046 | Tzelnic et al. | Oct 1998 | A |
| 5842222 | Lin | Nov 1998 | A |
| 5860104 | Witt et al. | Jan 1999 | 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 |
| 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 |
| 6058066 | Norris et al. | May 2000 | A |
| 6061692 | Thomas et al. | May 2000 | A |
| 6072490 | Bates et al. | Jun 2000 | A |
| 6076148 | Kedem | Jun 2000 | A |
| 6088697 | Crockett et al. | Jul 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 | Mar 2001 | B1 |
| 6212512 | Barney et al. | Apr 2001 | B1 |
| 6212521 | Minami et al. | Apr 2001 | B1 |
| 6230164 | Rekieta et al. | May 2001 | B1 |
| 6260068 | Zalewski et al. | Jul 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 et al. | Sep 2001 | B1 |
| 6301592 | Aoyama et al. | Oct 2001 | B1 |
| 6304880 | Kishi | Oct 2001 | B1 |
| 6311193 | Sekido | 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 | Armangau | Aug 2002 | B1 |
| 6438595 | Blumenau et al. | Aug 2002 | B1 |
| 6466950 | Ono | Oct 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 |
| 6516314 | Birkler et al. | Feb 2003 | B1 |
| 6516327 | Zondervan et al. | Feb 2003 | B1 |
| 6516348 | MacFarlane et al. | Feb 2003 | B1 |
| 6519679 | Devireddy et al. | Feb 2003 | B2 |
| 6538669 | Lagueux, Jr. et al. | Mar 2003 | B1 |
| 6539462 | Mikkelsen et al. | Mar 2003 | B1 |
| 6542468 | Hatakeyama | Apr 2003 | B1 |
| 6542909 | Tamer et al. | Apr 2003 | B1 |
| 6542972 | Ignatius et al. | Apr 2003 | B2 |
| 6564228 | O'Connor | May 2003 | B1 |
| 6564229 | Baweja et al. | May 2003 | B1 |
| 6564271 | Micalizzi, Jr. et al. | May 2003 | B2 |
| 6581143 | Gagne et al. | Jun 2003 | B2 |
| 6604118 | Kleinman et al. | Aug 2003 | B2 |
| 6604149 | Deo et al. | Aug 2003 | B1 |
| 6611849 | Raff et al. | Aug 2003 | B1 |
| 6615223 | Shih et al. | Sep 2003 | B1 |
| 6629189 | Sandstrom et al. | Sep 2003 | B1 |
| 6631477 | LeCrone et al. | Oct 2003 | B1 |
| 6631493 | Ottesen et al. | Oct 2003 | B2 |
| 6647396 | Parnell et al. | Nov 2003 | B2 |
| 6647473 | Golds et al. | Nov 2003 | B1 |
| 6647474 | Yanai et al. | Nov 2003 | B2 |
| 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 |
| 6691209 | O'Connell | Feb 2004 | B1 |
| 6721767 | De Meno et al. | Apr 2004 | B2 |
| 6728733 | Tokui | 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 |
| 6792472 | Otterness et al. | Sep 2004 | B1 |
| 6792518 | Armangau et al. | Sep 2004 | B2 |
| 6799258 | Linde | Sep 2004 | B1 |
| 6820035 | Zahavi | Nov 2004 | B1 |
| 6836779 | Poulin | Dec 2004 | B2 |
| 6839724 | Manchanda et al. | Jan 2005 | B2 |
| 6871163 | Hiller et al. | Mar 2005 | B2 |
| 6871271 | Ohran et al. | Mar 2005 | B2 |
| 6880051 | Timpanaro-Perrotta | Apr 2005 | B2 |
| 6886020 | Zahavi et al. | Apr 2005 | B1 |
| 6892211 | Hitz et al. | May 2005 | B2 |
| 6912482 | Kaiser | Jun 2005 | B2 |
| 6925476 | Multer et al. | Aug 2005 | B1 |
| 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 |
| 6952705 | Knoblock et al. | Oct 2005 | B2 |
| 6952758 | Chron et al. | Oct 2005 | B2 |
| 6954834 | Slater et al. | Oct 2005 | B2 |
| 6968351 | Butterworth | Nov 2005 | B2 |
| 6973553 | Archibald, Jr. et al. | Dec 2005 | B1 |
| 6978265 | Schumacher | Dec 2005 | B2 |
| 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 |
| 7007046 | Manley et al. | Feb 2006 | B2 |
| 7020669 | McCann et al. | Mar 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 |
| 7068597 | Fijolek et al. | Jun 2006 | B1 |
| 7082441 | Zahavi et al. | Jul 2006 | B1 |
| 7085787 | Beier et al. | Aug 2006 | B2 |
| 7085904 | Mizuno et al. | Aug 2006 | B2 |
| 7093012 | Olstad et al. | Aug 2006 | B2 |
| 7096315 | Takeda et al. | Aug 2006 | B2 |
| 7103731 | Gibble et al. | Sep 2006 | B2 |
| 7103740 | Colgrove et al. | Sep 2006 | B1 |
| 7106691 | DeCaluwe et al. | Sep 2006 | B1 |
| 7107298 | Prahlad et al. | Sep 2006 | B2 |
| 7107395 | Ofek et al. | Sep 2006 | B1 |
| 7111021 | Lewis et al. | Sep 2006 | B1 |
| 7111189 | Sicola et al. | Sep 2006 | B1 |
| 7120757 | Tsuge | Oct 2006 | B2 |
| 7130860 | Pachet et al. | Oct 2006 | B2 |
| 7130970 | Devassy et al. | Oct 2006 | B2 |
| 7139932 | Watanabe | Nov 2006 | B2 |
| 7155465 | Lee et al. | Dec 2006 | B2 |
| 7155633 | Tuma et al. | Dec 2006 | B2 |
| 7158985 | Liskov | Jan 2007 | B1 |
| 7165257 | Musoll et al. | Jan 2007 | B2 |
| 7177866 | Holenstein 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 |
| 7194487 | Kekre et al. | Mar 2007 | B1 |
| 7200620 | Gupta | Apr 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 |
| 7231391 | Aronoff et al. | Jun 2007 | B2 |
| 7231544 | Tan et al. | Jun 2007 | B2 |
| 7234115 | Sprauve et al. | Jun 2007 | B1 |
| 7246140 | Therrien et al. | Jul 2007 | B2 |
| 7246207 | Kottomtharayil et al. | Jul 2007 | B2 |
| 7250963 | Yuri et al. | Jul 2007 | B2 |
| 7257689 | Baird | Aug 2007 | B1 |
| 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 | Armangau et al. | Sep 2007 | B2 |
| 7278142 | Bandhole et al. | Oct 2007 | B2 |
| 7284153 | Okbay et al. | Oct 2007 | B2 |
| 7287047 | Kavuri | Oct 2007 | B2 |
| 7293133 | Colgrove et al. | Nov 2007 | B1 |
| 7296125 | Ohran | Nov 2007 | B2 |
| 7315923 | Retnamma et al. | Jan 2008 | B2 |
| 7318134 | Oliveira et al. | Jan 2008 | B1 |
| 7340652 | Jarvis et al. | Mar 2008 | B2 |
| 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 |
| 7363444 | Ji | Apr 2008 | B2 |
| 7370232 | Safford | May 2008 | B2 |
| 7373364 | Chapman | May 2008 | B1 |
| 7380072 | Kottomtharayil et al. | May 2008 | B2 |
| 7383293 | Gupta 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 |
| 7401064 | Arone et al. | Jul 2008 | B1 |
| 7409509 | Devassy et al. | Aug 2008 | B2 |
| 7415488 | Muth et al. | Aug 2008 | B1 |
| 7428657 | Yamasaki | 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 |
| 7457980 | Yang et al. | Nov 2008 | B2 |
| 7461230 | Gupta et al. | Dec 2008 | B1 |
| 7464236 | Sano et al. | Dec 2008 | B2 |
| 7467167 | Patterson | Dec 2008 | B2 |
| 7467267 | Mayock | Dec 2008 | B1 |
| 7469262 | Baskaran et al. | Dec 2008 | B2 |
| 7472238 | Gokhale et al. | Dec 2008 | B1 |
| 7472312 | Jarvis et al. | Dec 2008 | B2 |
| 7475284 | Koike | Jan 2009 | B2 |
| 7484054 | Kottomtharayil et al. | Jan 2009 | B2 |
| 7490207 | Amarendran et al. | 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 |
| 7502902 | Sato 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 | Palliyil et al. | Apr 2009 | B2 |
| 7523483 | Dogan et al. | Apr 2009 | B2 |
| 7529745 | Ahluwalia et al. | May 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 |
| 7533181 | Dawson et al. | May 2009 | B2 |
| 7536291 | Vijayan 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 |
| 7546364 | Raman et al. | Jun 2009 | B2 |
| 7552358 | Asgar-Deen et al. | Jun 2009 | B1 |
| 7565572 | Yamasaki | Jul 2009 | B2 |
| 7581077 | Ignatius et al. | Aug 2009 | B2 |
| 7590668 | Kathuria et al. | Sep 2009 | B2 |
| 7593966 | Therrien et al. | Sep 2009 | B2 |
| 7596586 | Gokhale et al. | Sep 2009 | B2 |
| 7606841 | Ranade | Oct 2009 | B1 |
| 7606844 | Kottomtharavil | Oct 2009 | B2 |
| 7607037 | LeCrone 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 |
| 7617321 | Clark | Nov 2009 | B2 |
| 7617369 | Bezbaruah et al. | Nov 2009 | B1 |
| 7617541 | Plotkin et al. | Nov 2009 | B2 |
| 7627598 | Burke | Dec 2009 | B1 |
| 7627617 | Kavuri et al. | Dec 2009 | B2 |
| 7634477 | Hinshaw | Dec 2009 | B2 |
| 7636743 | Erofeev | Dec 2009 | B2 |
| 7651593 | Prahlad et al. | Jan 2010 | B2 |
| 7661028 | Erofeev | Feb 2010 | B2 |
| 7668798 | Scanlon et al. | Feb 2010 | B2 |
| 7669029 | Mishra et al. | Feb 2010 | B1 |
| 7672979 | Appellof et al. | Mar 2010 | B1 |
| 7673000 | Smoot et al. | Mar 2010 | B2 |
| 7685126 | Patel et al. | Mar 2010 | B2 |
| 7689467 | Belanger et al. | Mar 2010 | B1 |
| 7694086 | Bezbaruah et al. | Apr 2010 | B1 |
| 7702533 | Barnard et al. | Apr 2010 | B2 |
| 7702670 | Duprey et al. | Apr 2010 | B1 |
| 7707184 | Zhang et al. | Apr 2010 | B1 |
| 7716171 | Kryger | May 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 |
| 7765554 | Musoll et al. | Jul 2010 | B2 |
| 7809691 | Karmarkar et al. | Oct 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 |
| 7870355 | Erofeev | Jan 2011 | B2 |
| 7904681 | Bappe et al. | Mar 2011 | B1 |
| 7930476 | Castelli et al. | Apr 2011 | B1 |
| 7962455 | Erofeev | Jun 2011 | B2 |
| 7962709 | Agrawal | Jun 2011 | B2 |
| 8005795 | Galipeau et al. | Aug 2011 | B2 |
| 8019003 | Godwin | Sep 2011 | B2 |
| 8024294 | Kottomtharayil | Sep 2011 | B2 |
| 8121983 | Prahlad et al. | Feb 2012 | B2 |
| 8156086 | Lu et al. | Apr 2012 | B2 |
| 8166263 | Prahlad et al. | Apr 2012 | B2 |
| 8170995 | Prahlad et al. | May 2012 | B2 |
| 8190565 | Prahlad et al. | May 2012 | B2 |
| 8195623 | Prahlad et al. | Jun 2012 | B2 |
| 8204859 | Ngo | Jun 2012 | B2 |
| 8219524 | Gokhale | Jul 2012 | B2 |
| 8230195 | Amarendran et al. | Jul 2012 | B2 |
| 8237008 | Alessandrini | Aug 2012 | B1 |
| 8271830 | Erofeev | Sep 2012 | B2 |
| 8285681 | Prahlad et al. | Oct 2012 | B2 |
| 8285684 | Prahlad et al. | Oct 2012 | B2 |
| 8291101 | Yan et al. | Oct 2012 | B1 |
| 8307177 | Prahlad et al. | Nov 2012 | B2 |
| 8352422 | Prahlad et al. | Jan 2013 | B2 |
| 8364652 | Vijayan et al. | Jan 2013 | B2 |
| 8463751 | Kottomtharayil | Jun 2013 | B2 |
| 8489656 | Erofeev | Jul 2013 | B2 |
| 8504515 | Prahlad et al. | Aug 2013 | B2 |
| 8504517 | Agrawal | Aug 2013 | B2 |
| 8572038 | Erofeev | Oct 2013 | B2 |
| 8578120 | Attarde et al. | Nov 2013 | B2 |
| 8589347 | Erofeev | Nov 2013 | B2 |
| 8655850 | Ngo et al. | Feb 2014 | B2 |
| 8656218 | Erofeev | Feb 2014 | B2 |
| 8666942 | Ngo | Mar 2014 | B2 |
| 8725694 | Kottomtharayil | May 2014 | B2 |
| 8725698 | Prahlad et al. | May 2014 | B2 |
| 8726242 | Ngo | May 2014 | B2 |
| 8745105 | Erofeev | Jun 2014 | B2 |
| 8793221 | Prahlad et al. | Jul 2014 | B2 |
| 8805818 | Zane et al. | Aug 2014 | B2 |
| 8849764 | Long et al. | Sep 2014 | B1 |
| 8868494 | Agrawal | Oct 2014 | B2 |
| 8874508 | Mittal | Oct 2014 | B1 |
| 8935210 | Kottomtharayil | Jan 2015 | B2 |
| 8954446 | Vijayan Retnamma et al. | Feb 2015 | B2 |
| 9002785 | Prahlad et al. | Apr 2015 | B2 |
| 9002799 | Ngo et al. | Apr 2015 | B2 |
| 9003374 | Ngo | Apr 2015 | B2 |
| 9020898 | Prahlad et al. | Apr 2015 | B2 |
| 9020900 | Vijayan Retnamma et al. | Apr 2015 | B2 |
| 9047357 | Ngo | Jun 2015 | B2 |
| 9098495 | Goklhale | Aug 2015 | B2 |
| 9208210 | Erofeev | Dec 2015 | B2 |
| 9239687 | Vijayan et al. | Jan 2016 | B2 |
| 9298382 | Kottomtharayil | Mar 2016 | B2 |
| 9396244 | Ngo | Jul 2016 | B2 |
| 9444811 | Nara et al. | Sep 2016 | B2 |
| 9483511 | Prahlad et al. | Nov 2016 | B2 |
| 9495382 | Agrawal et al. | Nov 2016 | B2 |
| 9639294 | Prahlad et al. | May 2017 | B2 |
| 9971657 | Prahlad et al. | May 2018 | B2 |
| 10592145 | Bedadala et al. | Mar 2020 | B2 |
| 10983873 | Blackard | Apr 2021 | B1 |
| 11042318 | Ausarkar et al. | Jun 2021 | B2 |
| 11237915 | Mehta et al. | Feb 2022 | B2 |
| 20010029512 | Oshinsky et al. | Oct 2001 | A1 |
| 20010029517 | De Meno et al. | Oct 2001 | A1 |
| 20010032172 | Moulinet et al. | Oct 2001 | A1 |
| 20010035866 | Finger et al. | Nov 2001 | A1 |
| 20010042222 | Kedem et al. | Nov 2001 | A1 |
| 20010044807 | Kleiman et al. | Nov 2001 | A1 |
| 20020002557 | Straube et al. | Jan 2002 | A1 |
| 20020004883 | Nguyen et al. | Jan 2002 | A1 |
| 20020018486 | Musoll et al. | Feb 2002 | A1 |
| 20020019909 | D'Errico | Feb 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 |
| 20020083055 | Pachet et al. | Jun 2002 | A1 |
| 20020091712 | Martin et al. | Jul 2002 | A1 |
| 20020103848 | Giacomini et al. | Aug 2002 | A1 |
| 20020107877 | Whiting et al. | Aug 2002 | A1 |
| 20020112134 | Ohran et al. | Aug 2002 | A1 |
| 20020120741 | Webb et al. | Aug 2002 | A1 |
| 20020124137 | Ulrich et al. | Sep 2002 | A1 |
| 20020133511 | Hostetter | Sep 2002 | A1 |
| 20020133512 | Milillo et al. | Sep 2002 | A1 |
| 20020161753 | Inaba et al. | Oct 2002 | A1 |
| 20020174107 | Poulin | Nov 2002 | A1 |
| 20020174139 | Midgley et al. | Nov 2002 | A1 |
| 20020174416 | Bates et al. | Nov 2002 | A1 |
| 20020181395 | Foster et al. | Dec 2002 | A1 |
| 20030005119 | Mercier et al. | Jan 2003 | A1 |
| 20030018657 | Monday | Jan 2003 | A1 |
| 20030023893 | Lee et al. | Jan 2003 | A1 |
| 20030028736 | Berkowitz et al. | Feb 2003 | A1 |
| 20030033308 | Patel et al. | Feb 2003 | A1 |
| 20030061491 | Jaskiewicz et al. | Mar 2003 | A1 |
| 20030079018 | Lolayekar et al. | Apr 2003 | A1 |
| 20030097296 | Putt | May 2003 | A1 |
| 20030126200 | Wolff | Jul 2003 | A1 |
| 20030131278 | Fujibayashi | Jul 2003 | A1 |
| 20030135783 | Martin et al. | Jul 2003 | A1 |
| 20030161338 | Ng et al. | Aug 2003 | A1 |
| 20030167380 | Green et al. | Sep 2003 | A1 |
| 20030177149 | Coombs | Sep 2003 | A1 |
| 20030177321 | Watanabe | Sep 2003 | A1 |
| 20030182312 | Chen et al. | Sep 2003 | A1 |
| 20030187847 | Lubbers et al. | Oct 2003 | A1 |
| 20030225800 | Kavuri | Dec 2003 | A1 |
| 20040006572 | Hoshino et al. | Jan 2004 | A1 |
| 20040006578 | Yu 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 |
| 20040078632 | Infante et al. | Apr 2004 | A1 |
| 20040098425 | Wiss et al. | May 2004 | A1 |
| 20040107199 | Dalrymple, III et al. | Jun 2004 | A1 |
| 20040117438 | Considine et al. | Jun 2004 | A1 |
| 20040117572 | Welsh et al. | Jun 2004 | A1 |
| 20040133634 | Luke et al. | Jul 2004 | A1 |
| 20040139128 | Becker et al. | Jul 2004 | A1 |
| 20040158588 | Pruet, III | Aug 2004 | A1 |
| 20040193625 | Sutoh et al. | Sep 2004 | A1 |
| 20040193953 | Callahan et al. | Sep 2004 | A1 |
| 20040205206 | Naik et al. | Oct 2004 | A1 |
| 20040212639 | Smoot et al. | Oct 2004 | A1 |
| 20040215724 | Smoot et al. | Oct 2004 | A1 |
| 20040225437 | Endo et al. | Nov 2004 | A1 |
| 20040230615 | Blanco et al. | Nov 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 |
| 20040267777 | Sugimura et al. | Dec 2004 | A1 |
| 20040267835 | Zwilling et al. | Dec 2004 | A1 |
| 20040267836 | Armangau et al. | Dec 2004 | A1 |
| 20050015409 | Cheng et al. | Jan 2005 | A1 |
| 20050027892 | McCabe et al. | Feb 2005 | A1 |
| 20050033800 | Kavuri et al. | Feb 2005 | A1 |
| 20050044114 | Kottomtharayil et al. | Feb 2005 | A1 |
| 20050055445 | Gupta et al. | Mar 2005 | A1 |
| 20050060613 | Cheng et al. | Mar 2005 | A1 |
| 20050071389 | Gupta | Mar 2005 | A1 |
| 20050071391 | Fuerderer et al. | Mar 2005 | A1 |
| 20050080928 | Beverly et al. | Apr 2005 | A1 |
| 20050086443 | Mizuno et al. | Apr 2005 | A1 |
| 20050108292 | Burton et al. | May 2005 | A1 |
| 20050114406 | Borthakur et al. | May 2005 | A1 |
| 20050131900 | Palliyll et al. | Jun 2005 | A1 |
| 20050138306 | Panchbudhe et al. | Jun 2005 | A1 |
| 20050144202 | Chen | Jun 2005 | A1 |
| 20050172073 | Voigt et al. | Aug 2005 | A1 |
| 20050187982 | Sato | Aug 2005 | A1 |
| 20050187992 | Prahlad et al. | Aug 2005 | A1 |
| 20050188109 | Shiga 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 |
| 20050228875 | Monitzer et al. | Oct 2005 | A1 |
| 20050246376 | Lu et al. | Nov 2005 | A1 |
| 20050246510 | Retnamma et al. | Nov 2005 | A1 |
| 20050254456 | Sakai et al. | Nov 2005 | A1 |
| 20050268068 | Ignatius et al. | Dec 2005 | A1 |
| 20060005048 | Osaki et al. | Jan 2006 | A1 |
| 20060010154 | Prahlad et al. | Jan 2006 | A1 |
| 20060010227 | Atluri | Jan 2006 | A1 |
| 20060010341 | Kodama | Jan 2006 | A1 |
| 20060020616 | Hardy et al. | Jan 2006 | A1 |
| 20060031854 | Godwin | Feb 2006 | A1 |
| 20060034454 | Damgaard et al. | Feb 2006 | A1 |
| 20060036901 | Yang et al. | Feb 2006 | A1 |
| 20060047805 | Byrd et al. | Mar 2006 | A1 |
| 20060047931 | Saika | Mar 2006 | A1 |
| 20060092861 | Corday et al. | May 2006 | A1 |
| 20060107089 | Jansz et al. | May 2006 | A1 |
| 20060120401 | Harada et al. | Jun 2006 | A1 |
| 20060129537 | Torii et al. | Jun 2006 | A1 |
| 20060136685 | Griv et al. | Jun 2006 | A1 |
| 20060155946 | Ji | Jul 2006 | A1 |
| 20060171315 | Choi et al. | Aug 2006 | A1 |
| 20060174075 | Sutoh | Aug 2006 | A1 |
| 20060215564 | Breitgand et al. | Sep 2006 | A1 |
| 20060224846 | Amarendran et al. | Oct 2006 | A1 |
| 20060230244 | Amarendran et al. | Oct 2006 | A1 |
| 20060242371 | Shono et al. | Oct 2006 | A1 |
| 20060242489 | Brockway et al. | Oct 2006 | A1 |
| 20070033437 | Kawamura et al. | Feb 2007 | A1 |
| 20070043956 | El Far et al. | Feb 2007 | A1 |
| 20070050547 | Sano et al. | Mar 2007 | A1 |
| 20070055737 | Yamashita 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 |
| 20070124347 | Vivian et al. | May 2007 | A1 |
| 20070124348 | Claborn et al. | May 2007 | A1 |
| 20070130373 | Kalwitz | Jun 2007 | A1 |
| 20070143371 | Kottomtharayil | Jun 2007 | A1 |
| 20070143756 | Gokhale | Jun 2007 | A1 |
| 20070179990 | Zimran et al. | Aug 2007 | A1 |
| 20070183224 | Erofeev | Aug 2007 | A1 |
| 20070185852 | 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 |
| 20070186042 | Kottomtharayil et al. | Aug 2007 | A1 |
| 20070186068 | Agrawal | Aug 2007 | A1 |
| 20070198602 | Ngo et al. | Aug 2007 | A1 |
| 20070226438 | Erofeev | Sep 2007 | A1 |
| 20070233756 | D'Souza et al. | Oct 2007 | A1 |
| 20070244571 | Wilson et al. | Oct 2007 | A1 |
| 20070256079 | Musoll et al. | Nov 2007 | A1 |
| 20070260609 | Tulyani | Nov 2007 | A1 |
| 20070276848 | Kim | Nov 2007 | A1 |
| 20070288536 | Sen et al. | Dec 2007 | A1 |
| 20080016126 | Kottomtharayil et al. | Jan 2008 | A1 |
| 20080016293 | Saika | Jan 2008 | A1 |
| 20080028009 | Ngo | Jan 2008 | A1 |
| 20080059515 | Fulton | Mar 2008 | A1 |
| 20080077634 | Quakenbush | Mar 2008 | A1 |
| 20080077636 | Gupta et al. | Mar 2008 | A1 |
| 20080103916 | Camarador et al. | May 2008 | A1 |
| 20080104357 | Kim et al. | May 2008 | A1 |
| 20080114815 | Sutoh et al. | May 2008 | A1 |
| 20080147878 | Kottomtharayil et al. | Jun 2008 | A1 |
| 20080183775 | Prahlad et al. | Jul 2008 | A1 |
| 20080205301 | Burton et al. | Aug 2008 | A1 |
| 20080208933 | Lyon | Aug 2008 | A1 |
| 20080228987 | Yagi et al. | Sep 2008 | A1 |
| 20080229037 | Bunte et al. | Sep 2008 | A1 |
| 20080243914 | Prahlad 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 |
| 20080250178 | Haustein et al. | Oct 2008 | A1 |
| 20080306954 | Hornqvist | Dec 2008 | A1 |
| 20080313497 | Hirakawa et al. | Dec 2008 | A1 |
| 20090013014 | Kern et al. | Jan 2009 | A1 |
| 20090044046 | Yamasaki | Feb 2009 | A1 |
| 20090113056 | Tameshige et al. | Apr 2009 | A1 |
| 20090150462 | McClanahan et al. | Jun 2009 | A1 |
| 20090182963 | Prahlad et al. | Jul 2009 | A1 |
| 20090187944 | White et al. | Jul 2009 | A1 |
| 20090300079 | Shitomi | Dec 2009 | A1 |
| 20090319534 | Gokhale | Dec 2009 | A1 |
| 20090319585 | Gokhale | Dec 2009 | A1 |
| 20100005259 | Prahlad et al. | Jan 2010 | A1 |
| 20100049753 | Prahlad et al. | Feb 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 |
| 20100131467 | 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 |
| 20100211571 | Prahlad et al. | Aug 2010 | A1 |
| 20100306202 | Lee | Dec 2010 | A1 |
| 20110066599 | Prahlad et al. | Mar 2011 | A1 |
| 20110238621 | Agrawal | Sep 2011 | A1 |
| 20110246416 | Prahlad et al. | Oct 2011 | A1 |
| 20110246429 | Prahlad et al. | Oct 2011 | A1 |
| 20110246430 | Prahlad et al. | Oct 2011 | A1 |
| 20110295804 | Erofeev | Dec 2011 | A1 |
| 20110295806 | Erofeev | Dec 2011 | A1 |
| 20120011336 | Saika | Jan 2012 | A1 |
| 20120030171 | Kottomtharayil | Feb 2012 | A1 |
| 20120317074 | Ngo | Dec 2012 | A1 |
| 20130006926 | Erofeev | Jan 2013 | A1 |
| 20130006938 | Prahlad et al. | Jan 2013 | A1 |
| 20130006942 | Prahlad et al. | Jan 2013 | A1 |
| 20140032495 | Erofeev | Jan 2014 | A1 |
| 20140067764 | Prahlad et al. | Mar 2014 | A1 |
| 20140074777 | Agrawal | Mar 2014 | A1 |
| 20140181029 | Erofeev | Jun 2014 | A1 |
| 20140201170 | Vijayan et al. | Jul 2014 | A1 |
| 20140244586 | Ngo | Aug 2014 | A1 |
| 20150199375 | Prahlad et al. | Jul 2015 | A1 |
| 20150248444 | Prahlad et al. | Sep 2015 | A1 |
| 20160350391 | Vijayan et al. | Dec 2016 | A1 |
| 20170168903 | Dornemann et al. | Jun 2017 | A1 |
| 20170185488 | Kumarasamy et al. | Jun 2017 | A1 |
| 20170193003 | Vijayan et al. | Jul 2017 | A1 |
| 20170235647 | Kilaru et al. | Aug 2017 | A1 |
| 20170242871 | Kilaru et al. | Aug 2017 | A1 |
| 20180137139 | Bangalore | May 2018 | A1 |
| 20180329476 | Zhuo | Nov 2018 | A1 |
| 20190087285 | Kumar | Mar 2019 | A1 |
| 20190108341 | Bedhapudi et al. | Apr 2019 | A1 |
| 20200293408 | Mutha | Sep 2020 | A1 |
| 20200409908 | Ahn et al. | Dec 2020 | A1 |
| 20220083228 | Ausarkar et al. | Mar 2022 | A1 |
| 20220083685 | Reyes | Mar 2022 | A1 |
| 20230305934 | Bhagi et al. | Sep 2023 | A1 |
| 20230333777 | Shveidel | Oct 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 2006331932 | Jul 2007 | AU |
| 2632935 | Jul 2007 | 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 |
| H05189281 | Jul 1993 | JP |
| H06274605 | Sep 1994 | JP |
| H0916463 | Jan 1997 | JP |
| H11259348 | Sep 1999 | JP |
| 2000347811 | Dec 2000 | JP |
| 1993003549 | Feb 1993 | WO |
| 1995013580 | May 1995 | WO |
| 1998039707 | Sep 1998 | WO |
| 1999012098 | Mar 1999 | WO |
| 1999014692 | Mar 1999 | WO |
| 2002095632 | Nov 2002 | WO |
| 2003028183 | Apr 2003 | WO |
| 2004034197 | Apr 2004 | WO |
| 2005055093 | Jun 2005 | WO |
| 2005086032 | Sep 2005 | WO |
| 2007053314 | May 2007 | WO |
| 2010068570 | Jun 2010 | WO |
| Entry |
|---|
| Armstead et al., “Implementation of a Campus-wide Distributed Mass Storage Service: The Dream vs. Reality,” IEEE, Sep. 11-14, 1995, pp. 190-199. |
| Arneson, David A., “Development of Omniserver,” Control Data Corporation, Tenth IEEE Symposium on Mass Storage Systems, May 1990, ‘Crisis in Mass Storage’ Digest of Papers, pp. 88-93, Monterey, CA. |
| 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, Backup 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, pp. 420-427, San Francisco, CA. |
| Calvert, Andrew, “SQL Server 2005 Snapshots”, published Apr. 3, 2006, http:/www.simple-talk.com/contnet/print.aspx?article=137, 6 pages. |
| Canadian Office Action dated Dec. 29, 2010, Application No. CA2546304, 04 Pages. |
| Canadian Office Action dated Sep. 24, 2012, Application No. 2,632,935, 2 pages. |
| Eitel, “Backup and Storage Management in Distributed Heterogeneous Environments,” IEEE, Jun. 12-16, 1994, pp. 124-126. |
| European Examination Report; Application No. 06848901.2, Apr. 1, 2009, pp. 7. |
| Exam Report in Australian Application No. 2009324800 dated Jun. 17, 2013, 02 Pages. |
| Examiner's First Report; Application No. 2006331932 May 11, 2011 in 2 pages. |
| Examiner's Report for Australian Application No. 2003279847, Dated Dec. 9, 2008, Examiner Kanwal Pahwa, 4 pages. |
| Final Office Action for Japanese Application No. 2003531581, Examiner Kudoh, Mail Date Mar. 24, 2009, 6 pages. |
| First Office Action for Japanese Application No. 2003531581, Mail Date Jul. 8, 2008, Examiner Kudoh, 8 pages. |
| First Office Action in Canadian application No. 2,632,935 dated Feb. 16, 2012, Examiner Cassidy in 5 pages. |
| Gray, et al. “Transaction processing: concepts andtechniques” 1994, Morgan Kaufmann Publishers, USA, 646-655. |
| IBM, “Intelligent Selection of Logs Required During Recovery Processing”, ip.com, Sep. 16, 2002, 4 pages. |
| IBM, “Near Zero Impact Backup and Data Replication Appliance”, ip.com, Oct. 18, 2004, 5 pages. |
| International Preliminary Report on Patentability and Written Opinion in PCT/US2011/030396 mailed Oct. 2, 2012, 11 Pages. |
| International Preliminary Report on Patentability and Written Opinion in PCT/US2011/038436 mailed Dec. 4, 2012, 10 Pages. |
| International Preliminary Report on Patentability, PCT Application No. PCT/US2009/066880, mailed Jun. 23, 2011, in 09 pages. |
| International Search Report and Written Opinion dated Jan. 11, 2006 , PCT/US2004/038455, 04 Pages. |
| International Search Report and Written Opinion for PCT/US2007/081681 dated Nov. 13, 2009 in 08 pages. |
| International Search Report and Written Opinion issued in PCT Application No. PCT/US2011/030396, mailed Jul. 18, 2011, in 20 pages. |
| International Search Report and Written Opinion issued in PCT Application No. PCT/US2011/38436, mailed Sep. 21, 2011, in 18 pages. |
| International Search Report and Written Opinion, PCT/US2009/066880, dated Mar. 25, 2010, 10 pages. |
| International Search Report dated Dec. 28, 2009, PCT/US2004/038324, 02 pages. |
| International Search Report from International Application No. PCT/US2006/048273, dated May 15, 2007, 13 pages. |
| Lyon J., Design considerations in replicated database systems for disaster protection, COMPCON 1988, Feb. 29, 1988, pp. 428-430. |
| Mell et al., The NIST Definition of Cloud Computing, 800-145, Sep. 2011, 07 Pages. |
| Microsoft Corporation, “Microsoft Exchange Server: Best Practices for Exchange Database Management,” 1998, 26 Pages. |
| Park, et al., “An Efficient Logging Scheme for Recoverable Distributed Shared Memory Systems”, IEEE, 1997, 9 pages. |
| Rosenblum et al., “The Design and Implementation of a Log-Structure File System,” Operating Systems Review SIGOPS, vol. 25, No. 5, May 1991, New York, US, pp. 1-15. |
| Second Examination Report in EU Appl. No. 06 848 901.2-2201 dated Dec. 3, 2010, 05 Pages. |
| Wiesmann M, Database replication techniques: a three parameter classification, Oct. 16, 2000, pp. 206-215. |
| Wikipedia, Cloud Computing, en.wikipedia.org/wiki/Cloud_computing, accessed on Apr. 26, 2019, 13 Pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230409441 A1 | Dec 2023 | US |
