US 9,766,989 B2Grant

Creation of virtual machine placeholders in a data storage system

Issue Date:2017-09-19

•20 Claims

•10 Drawing Sheets

Abstract

The data storage system according to certain aspects can manage the archiving of virtual machines to (and restoring of virtual machines from) secondary storage. The system may archive virtual machines (VMs) that are determined to have a low level of utilization. The system may create a virtual machine placeholder for an archived VM, which may be a “light” or minimal version of the VM that acts like the actual VM. By using a VM placeholder, a VM may appear to be active and selectable by the user. When the user selects the VM, the VM placeholder can interact with the user in similar manner as the VM. Accessing the VM placeholder may trigger restore of the archived VM from secondary storage. The restore of the archived VM may be “seamless” to the user since the VM remains available while it is being restored.

Metadata

Assignee

Commvault Systems, Inc.

Inventors

Amit Mitkar
Sumer Dilip Deshpande
Henry Wallace Dornemann
Rahul S. Pawar
Ashwin Gautamchand Sancheti

Application Information

Application Number:US 15/471,952

Filing Date:2017-03-28

Priority Date:2013-01-14

Art Unit:2196

Classifications

IPC:

G06F9/455G06F11/14G06F9/46G06F9/50

Patent Drawings (10 sheets)

Description

Related Applications

[0001] Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet, or any correction thereto, are hereby incorporated by reference into this application under 37 CFR 1.57.

Background

[0002] Businesses worldwide recognize the commercial value of their data and seek reliable, cost-effective ways to protect the information stored on their computer networks while minimizing impact on productivity. Protecting information is often part of a routine process that is performed within an organization.

[0003] A company might back up critical computing systems such as databases, file servers, web servers, and so on as part of a daily, weekly, or monthly maintenance schedule. The company may similarly protect computing systems used by each of its employees, such as those used by an accounting department, marketing department, engineering department, and so forth.

[0004] Given the rapidly expanding volume of data under management, companies also continue to seek innovative techniques for managing data growth, in addition to protecting data. For instance, companies often implement migration techniques for moving data to lower cost storage over time and data reduction techniques for reducing redundant data, pruning lower priority data, etc.

[0005] Enterprises also increasingly view their stored data as a valuable asset. Along these lines, customers are looking for solutions that not only protect and manage, but also leverage their data. For instance, solutions providing data analysis capabilities, improved data presentation and access features, and the like, are in increasing demand.

[0006] Enterprises may use virtual machines in order to utilize physical resources in a more efficient manner. Virtual machines that have low utilization may be archived in order to reduce the amount of unused or underused resources. In some cases, archived virtual machines may need to be restored.

Summary

[0007] Due to the above challenges, there is a need for managing virtual machines, and in particular, virtual machines that do not fully utilize the resources allocated to them. Although many users request large amounts of resources for the virtual machines, in most cases, they do not use the allocated resources frequently, and generally not to the full extent of the allocated resources. In order to address these and other challenges, certain storage systems disclosed herein are configured to archive virtual machines that have low usage. A data storage system according to certain aspects may include a virtual machine (VM) archiving module that manages the archiving of virtual machines to, and restoring of virtual machines from, secondary storage. One or more virtual machines may run on one or more client computers in the system. Each client computer may include a hypervisor that controls and manages the one or more virtual machines on the client.

[0008] The VM archiving module can determine whether to archive virtual machines based on usage data or information. The system may monitor the usage of virtual machines, for example, according to a schedule, based on certain events, at a system administrator's request, etc. The monitoring of virtual machines may be implemented as storage policies. The VM archiving module can obtain the usage data or information from the hypervisor on each client. The VM archiving module may also obtain the usage information from a virtual center that collects information relating to various virtual machines in the system. The usage information may include storage usage, CPU usage, memory usage, network usage, events defined by a virtual machine software or application, etc.

[0009] The VM archiving module may archive the virtual machines that are determined to have a low level of utilization. Such determination may be made when the usage level of a virtual machine is below a threshold level of activity. The VM archiving module can initiate copying of the virtual machine and its associated data from primary storage (e.g., the client computer and/or an information store associated with the client computer) to secondary storage. In some embodiments, the VM archiving module may reduce the amount of resources allocated to a virtual machine (e.g., in increments) until a threshold level of activity is reached. The virtual machine can be archived when the usage level reaches the threshold level. In order to reduce the amount of allocated resources, the VM archiving module may move the low usage virtual machine to low-cost and/or low-speed storage. Once the virtual machine and the associated data are copied to secondary storage, the virtual machine and the associated data in primary storage can be pruned.

[0010] The virtual machine archiving module may create a virtual machine placeholder for an archived virtual machine. A VM placeholder may be a “light” or minimal version of the virtual machine that acts as if it is the actual virtual machine. The VM placeholder may have a reduced set or amount of resources compared to the VM. The VM placeholder can interact with one or more operating systems on the one or more client computers like it is the virtual machine. In this way, a virtual machine may be archived, but still appear to be active and selectable by the user.

[0011] When a user accesses the virtual machine or the VM placeholder after the virtual machine has been archived, at least a portion of the virtual machine and its associated data may be restored to reactivate the virtual machine. Resources may be allocated to the restored virtual machine. The VM placeholder may be deleted after all of the virtual machine and its data are restored to primary storage.

[0012] In this manner, the data storage system according to certain aspects can reduce the amount of resources that are unutilized and/or underutilized by virtual machines. The virtual machines with low usage may also be migrated or moved from high cost storage to low cost storage (e.g., from solid state drive to hard drive). In this way, the system can decrease the costs associated with storage and other resources. The system may also provide seamless archiving and restoring of the virtual machines through the use of virtual machine placeholders. From a user's perspective, the virtual machine may appear to be available at all times, and the archiving and the restoring of a low usage virtual machine can occur in the background.

[0013] According to certain embodiments, a method of archiving virtual machines in a networked data storage system is provided. The method can include determining whether to archive a virtual machine (VM) executing on one or more client computers in primary storage with computer hardware comprising one or more computer processors based on usage data. The method may further include, in response to determining that the VM should be archived, copying the VM and its associated data from the primary storage to secondary storage. The method can additionally include creating a VM placeholder for the VM in the primary storage wherein the VM placeholder appears to be the VM. The method can further include deleting the VM and the associated data from the primary storage. The method may also include restoring at least a portion of the VM and the associated data to the primary storage when the VM placeholder is accessed after the VM and the associated data are deleted.

[0014] In some embodiments, a data storage system configured for archiving virtual machines is provided. The data storage system may include a storage manager module executing on computer hardware comprising one or more computer processors. The storage manager module can be configured to initiate copying of data from primary storage to secondary storage. The data storage system may also include a virtual machine archiving module executing on computer hardware comprising one or more computer processors. The virtual machine archiving module can be configured to determine whether to archive a virtual machine (VM) executing on one or more client computers in the primary storage based on usage data. The virtual machine archiving module may be further configured to, in response to determining that the VM should be archived, initiate copying of the VM and its associated data, by the storage manager, from the primary storage to the secondary storage. The virtual machine archiving module can be further configured to create a VM placeholder for the VM in the primary storage wherein the VM placeholder appears to be the VM. The virtual machine archiving module may also be configured to delete the VM and the associated data from the primary storage. The virtual machine archiving module can also be configured to restore at least a portion of the VM and the associated data to the primary storage when the VM placeholder is accessed after the VM and the associated data are deleted.

[0015] For purposes of summarizing the disclosure, certain aspects, advantages and novel features of the inventions have been described herein. It is to be understood that not necessarily all such advantages may be achieved in accordance with any particular embodiment of the invention. Thus, the invention may be embodied or carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other advantages as may be taught or suggested herein.

Description of the Drawings

[0016] FIG. 1A is a block diagram illustrating an exemplary information management system.

[0017] FIG. 1B is a detailed view of a primary storage device, a secondary storage device, and some examples of primary data and secondary copy data.

[0018] FIG. 1C is a block diagram of an exemplary information management system including a storage manager, one or more data agents, and one or more media agents.

[0019] FIG. 1D is a block diagram illustrating a scalable information management system.

[0020] FIG. 1E illustrates certain secondary copy operations according to an exemplary storage policy.

[0021] FIG. 2 is a data flow diagram illustrative of the interaction between the various components of an exemplary storage system configured to archive virtual machines according to certain embodiments.

[0022] FIG. 3 is a data flow diagram illustrative of the interaction between the various components of another exemplary storage system configured to restore archived virtual machines according to certain embodiments.

[0023] FIG. 4 is a flow diagram illustrative of one embodiment of a routine for archiving virtual machines according to certain embodiments.

[0024] FIG. 5 is a flow diagram illustrative of one embodiment of a routine for restoring archived virtual machines according to certain embodiments.

Detailed Description

[0025] Systems and methods are described herein for archiving virtual machines. Examples of such systems and methods are discussed in further detail herein, e.g., with respect to FIGS. 2-5. Moreover, it will be appreciated virtual machines may be archived, migrated, and/or restored by information management systems such as those that will now be described with respect to FIGS. 1A-1E. And, as will be described, the componentry for implementing virtual machine archiving functionality can be incorporated into such systems.

Information Management System Overview

[0026] With the increasing importance of protecting and leveraging data, organizations simply cannot afford to take the risk of losing critical data. Moreover, runaway data growth and other modern realities make protecting and managing data an increasingly difficult task. There is therefore a need for efficient, powerful, and user-friendly solutions for protecting and managing data.

[0027] Depending on the size of the organization, there are typically many data production sources which are under the purview of tens, hundreds, or even thousands of employees or other individuals. In the past, individual employees were sometimes responsible for managing and protecting their data. A patchwork of hardware and software point solutions have been applied in other cases. These solutions were often provided by different vendors and had limited or no interoperability.

[0028] Certain embodiments described herein provide systems and methods capable of addressing these and other shortcomings of prior approaches by implementing unified, organization-wide information management. FIG. 1A shows one such information management system 100, which generally includes combinations of hardware and software configured to protect and manage data and metadata generated and used by the various computing devices in the information management system 100.

[0029] The organization which employs the information management system 100 may be a corporation or other business entity, non-profit organization, educational institution, household, governmental agency, or the like.

[0030] Generally, the systems and associated components described herein may be compatible with and/or provide some or all of the functionality of the systems and corresponding components described in one or more of the following U.S. patents and patent application publications assigned to CommVault Systems, Inc., each of which is hereby incorporated in its entirety by reference herein:

- [0031] U.S. Pat. Pub. No. 2010-0332456, entitled “DATA OBJECT STORE AND SERVER FOR A CLOUD STORAGE ENVIRONMENT, INCLUDING DATA DEDUPLICATION AND DATA MANAGEMENT ACROSS MULTIPLE CLOUD STORAGE SITES”;
- [0032] U.S. Pat. No. 7,035,880, entitled “MODULAR BACKUP AND RETRIEVAL SYSTEM USED IN CONJUNCTION WITH A STORAGE AREA NETWORK”;
- [0033] U.S. Pat. No. 7,343,453, entitled “HIERARCHICAL SYSTEMS AND METHODS FOR PROVIDING A UNIFIED VIEW OF STORAGE INFORMATION”;
- [0034] U.S. Pat. No. 7,395,282, entitled “HIERARCHICAL BACKUP AND RETRIEVAL SYSTEM”;
- [0035] U.S. Pat. No. 7,246,207, entitled “SYSTEM AND METHOD FOR DYNAMICALLY PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK”;
- [0036] U.S. Pat. No. 7,747,579, entitled “METABASE FOR FACILITATING DATA CLASSIFICATION”;
- [0037] U.S. Pat. No. 8,229,954, entitled “MANAGING COPIES OF DATA”;
- [0038] U.S. Pat. No. 7,617,262, entitled “SYSTEM AND METHODS FOR MONITORING APPLICATION DATA IN A DATA REPLICATION SYSTEM”;
- [0039] U.S. Pat. No. 7,529,782, entitled “SYSTEM AND METHODS FOR PERFORMING A SNAPSHOT AND FOR RESTORING DATA”;
- [0040] U.S. Pat. No. 8,230,195, entitled “SYSTEM AND METHOD FOR PERFORMING AUXILIARY STORAGE OPERATIONS”;
- [0041] U.S. Pat. Pub. No. 2012/0084268, entitled “CONTENT-ALIGNED, BLOCK-BASED DEDUPLICATION”;
- [0042] U.S. Pat. Pub. No. 2006/0224846, entitled “SYSTEM AND METHOD TO SUPPORT SINGLE INSTANCE STORAGE OPERATIONS”;
- [0043] U.S. Pat. Pub. No. 2009/0329534, entitled “APPLICATION-AWARE AND REMOTE SINGLE INSTANCE DATA MANAGEMENT”;
- [0044] U.S. Pat. Pub. No. 2012/0150826, entitled “DISTRIBUTED DEDUPLICATED STORAGE SYSTEM”;
- [0045] U.S. Pat. Pub. No. 2012/0150818, entitled “CLIENT-SIDE REPOSITORY IN A NETWORKED DEDUPLICATED STORAGE SYSTEM”;
- [0046] U.S. Pat. No. 8,170,995, entitled “METHOD AND SYSTEM FOR OFFLINE INDEXING OF CONTENT AND CLASSIFYING STORED DATA”; and
- [0047] U.S. Pat. No. 8,156,086, entitled “SYSTEMS AND METHODS FOR STORED DATA VERIFICATION”.

[0048] The illustrated information management system 100 includes one or more client computing device 102 having at least one application 110 executing thereon, and one or more primary storage devices 104 storing primary data 112. The client computing device(s) 102 and the primary storage devices 104 may generally be referred to in some cases as a primary storage subsystem 117.

[0049] Depending on the context, the term “information management system” can refer to generally all of the illustrated hardware and software components. Or, in other instances, the term may refer to only a subset of the illustrated components.

[0050] For instance, in some cases information management system 100 generally refers to a combination of specialized components used to protect, move, manage, manipulate and/or process data and metadata generated by the client computing devices 102. However, the term may generally not refer to the underlying components that generate and/or store the primary data 112, such as the client computing devices 102 themselves, the applications 110 and operating system residing on the client computing devices 102, and the primary storage devices 104.

[0051] As an example, “information management system” may sometimes refer only to one or more of the following components and corresponding data structures: storage managers, data agents, and media agents. These components will be described in further detail below.

Client Computing Devices

[0052] There are typically a variety of sources in an organization that produce data to be protected and managed. As just one illustrative example, in a corporate environment such data sources can be employee workstations and company servers such as a mail server, a web server, or the like. In the information management system 100, the data generation sources include the one or more client computing devices 102.

[0053] The client computing devices 102 may include, without limitation, one or more: workstations, personal computers, desktop computers, or other types of generally fixed computing systems such as mainframe computers and minicomputers.

[0054] The client computing devices 102 can also include mobile or portable computing devices, such as one or more laptops, tablet computers, personal data assistants, mobile phones (such as smartphones), and other mobile or portable computing devices such as embedded computers, set top boxes, vehicle-mounted devices, wearable computers, etc.

[0055] In some cases, each client computing device 102 is associated with one or more users and/or corresponding user accounts, of employees or other individuals.

[0056] The term “client computing device” is used herein because the information management system 100 generally “serves” the data management and protection needs for the data generated by the client computing devices 102. However, the use of this term does not imply that the client computing devices 102 cannot be “servers” in other respects. For instance, a particular client computing device 102 may act as a server with respect to other devices, such as other client computing devices 102. As just a few examples, the client computing devices 102 can include mail servers, file servers, database servers, and web servers.

[0057] The client computing devices 102 may additionally include virtualized and/or cloud computing resources. For instance, one or more virtual machines may be provided to the organization by a third-party cloud service vendor. Or, in some embodiments, the client computing devices 102 include one or more virtual machine(s) running on a virtual machine host computing device operated by the organization. As one example, the organization may use one virtual machine as a database server and another virtual machine as a mail server. A virtual machine manager (VMM) (e.g., a Hypervisor) may manage the virtual machines, and reside and execute on the virtual machine host computing device.

[0058] Each client computing device 102 may have one or more applications 110 (e.g., software applications) executing thereon which generate and manipulate the data that is to be protected from loss.

[0059] The applications 110 generally facilitate the operations of an organization (or multiple affiliated organizations), and can include, without limitation, mail server applications (e.g., Microsoft Exchange Server), file server applications, mail client applications (e.g., Microsoft Exchange Client), database applications (e.g., SQL, Oracle, SAP, Lotus Notes Database), word processing applications (e.g., Microsoft Word), spreadsheet applications, financial applications, presentation applications, browser applications, mobile applications, entertainment applications, and so on.

[0060] The applications 110 can include at least one operating system (e.g., Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-based operating systems, etc.), which may support one or more file systems and host the other applications 110.

[0061] As shown, the client computing devices 102 and other components in the information management system 100 can be connected to one another via one or more communication pathways 114. The communication pathways 114 can include one or more networks or other connection types including as any of following, without limitation: the Internet, a wide area network (WAN), a local area network (LAN), a Storage Area Network (SAN), a Fibre Channel connection, a Small Computer System Interface (SCSI) connection, a virtual private network (VPN), a token ring or TCP/IP based network, an intranet network, a point-to-point link, a cellular network, a wireless data transmission system, a two-way cable system, an interactive kiosk network, a satellite network, a broadband network, a baseband network, other appropriate wired, wireless, or partially wired/wireless computer or telecommunications networks, combinations of the same or the like. The communication pathways 114 in some cases may also include application programming interfaces (APIs) including, e.g., cloud service provider APIs, virtual machine management APIs, and hosted service provider APIs.

Primary Data and Exemplary Primary Storage Devices

[0062] Primary data 112 according to some embodiments is production data or other “live” data generated by the operating system and other applications 110 residing on a client computing device 102. The primary data 112 is stored on the primary storage device(s) 104 and is organized via a file system supported by the client computing device 102. For instance, the client computing device(s) 102 and corresponding applications 110 may create, access, modify, write, delete, and otherwise use primary data 112.

[0063] Primary data 112 is generally in the native format of the source application 110. According to certain aspects, primary data 112 is an initial or first (e.g., created before any other copies or before at least one other copy) stored copy of data generated by the source application 110. Primary data 112 in some cases is created substantially directly from data generated by the corresponding source applications 110.

[0064] The primary data 112 may sometimes be referred to as a “primary copy” in the sense that it is a discrete set of data. However, the use of this term does not necessarily imply that the “primary copy” is a copy in the sense that it was copied or otherwise derived from another stored version.

[0065] The primary storage devices 104 storing the primary data 112 may be relatively fast and/or expensive (e.g., a disk drive, a hard-disk array, solid state memory, etc.). In addition, primary data 112 may be intended for relatively short term retention (e.g., several hours, days, or weeks).

[0066] According to some embodiments, the client computing device 102 can access primary data 112 from the primary storage device 104 by making conventional file system calls via the operating system. Primary data 112 representing files may include structured data (e.g., database files), unstructured data (e.g., documents), and/or semi-structured data. Some specific examples are described below with respect to FIG. 1B.

[0067] It can be useful in performing certain tasks to break the primary data 112 up into units of different granularities. In general, primary data 112 can include files, directories, file system volumes, data blocks, extents, or any other types or granularities of data objects. As used herein, a “data object” can refer to both (1) any file that is currently addressable by a file system or that was previously addressable by the file system (e.g., an archive file) and (2) a subset of such a file.

[0068] As will be described in further detail, it can also be useful in performing certain functions of the information management system 100 to access and modify metadata within the primary data 112. Metadata generally includes information about data objects or characteristics associated with the data objects.

[0069] Metadata can include, without limitation, one or more of the following: the data owner (e.g., the client or user that generates the data), the last modified time (e.g., the time of the most recent modification of the data object), a data object name (e.g., a file name), a data object size (e.g., a number of bytes of data), information about the content (e.g., an indication as to the existence of a particular search term), to/from information for email (e.g., an email sender, recipient, etc.), creation date, file type (e.g., format or application type), last accessed time, application type (e.g., type of application that generated the data object), location/network (e.g., a current, past or future location of the data object and network pathways to/from the data object), frequency of change (e.g., a period in which the data object is modified), business unit (e.g., a group or department that generates, manages or is otherwise associated with the data object), and aging information (e.g., a schedule, such as a time period, in which the data object is migrated to secondary or long term storage), boot sectors, partition layouts, file location within a file folder directory structure, user permissions, owners, groups, access control lists [ACLs]), system metadata (e.g., registry information), combinations of the same or the like.

[0070] In addition to metadata generated by or related to file systems and operating systems, some of the applications 110 maintain indices of metadata for data objects, e.g., metadata associated with individual email messages. Thus, each data object may be associated with corresponding metadata. The use of metadata to perform classification and other functions is described in greater detail below.

[0071] Each of the client computing devices 102 are associated with and/or in communication with one or more of the primary storage devices 104 storing corresponding primary data 112. A client computing device 102 may be considered to be “associated with” or “in communication with” a primary storage device 104 if it is capable of one or more of: storing data to the primary storage device 104, retrieving data from the primary storage device 104, and modifying data retrieved from a primary storage device 104.

[0072] The primary storage devices 104 can include, without limitation, disk drives, hard-disk arrays, semiconductor memory (e.g., solid state drives), and network attached storage (NAS) devices. In some cases, the primary storage devices 104 form part of a distributed file system. The primary storage devices 104 may have relatively fast I/O times and/or are relatively expensive in comparison to the secondary storage devices 108. For example, the information management system 100 may generally regularly access data and metadata stored on primary storage devices 104, whereas data and metadata stored on the secondary storage devices 108 is accessed relatively less frequently.

[0073] In some cases, each primary storage device 104 is dedicated to an associated client computing devices 102. For instance, a primary storage device 104 in one embodiment is a local disk drive of a corresponding client computing device 102. In other cases, one or more primary storage devices 104 can be shared by multiple client computing devices 102. As one example, a primary storage device 104 can be a disk array shared by a group of client computing devices 102, such as one of the following types of disk arrays: EMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV, NetApp FAS, HP EVA, and HP 3PAR.

[0074] The information management system 100 may also include hosted services (not shown), which may be hosted in some cases by an entity other than the organization that employs the other components of the information management system 100. For instance, the hosted services may be provided by various online service providers to the organization. Such service providers can provide services including social networking services, hosted email services, or hosted productivity applications or other hosted applications).

[0075] Hosted services may include software-as-a-service (SaaS), platform-as-a-service (PaaS), application service providers (ASPs), cloud services, or other mechanisms for delivering functionality via a network. As it provides services to users, each hosted service may generate additional data and metadata under management of the information management system 100, e.g., as primary data 112. In some cases, the hosted services may be accessed using one of the applications 110. As an example, a hosted mail service may be accessed via browser running on a client computing device 102.

Secondary Copies and Exemplary Secondary Storage Devices

[0076] The primary data 112 stored on the primary storage devices 104 may be compromised in some cases, such as when an employee deliberately or accidentally deletes or overwrites primary data 112 during their normal course of work. Or the primary storage devices 104 can be damaged or otherwise corrupted.

[0077] For recovery and/or regulatory compliance purposes, it is therefore useful to generate copies of the primary data 112. Accordingly, the information management system 100 includes one or more secondary storage computing devices 106 and one or more secondary storage devices 108 configured to create and store one or more secondary copies 116 of the primary data 112 and associated metadata. The secondary storage computing devices 106 and the secondary storage devices 108 may be referred to in some cases as a secondary storage subsystem 118.

[0078] Creation of secondary copies 116 can help meet information management goals, such as: restoring data and/or metadata if an original version (e.g., of primary data 112) is lost (e.g., by deletion, corruption, or disaster); allowing point-in-time recovery; complying with regulatory data retention and electronic discovery (e-discovery) requirements; reducing utilized storage capacity; facilitating organization and search of data; improving user access to data files across multiple computing devices and/or hosted services; and implementing data retention policies.

[0079] Types of secondary copy operations can include, without limitation, backup operations, archive operations, snapshot operations, replication operations (e.g., continuous data replication [CDR]), data retention policies such as or information lifecycle management and hierarchical storage management operations, and the like. These specific types operations are discussed in greater detail below.

[0080] Regardless of the type of secondary copy operation, the client computing devices 102 access or receive primary data 112 and communicate the data, e.g., over the communication pathways 114, for storage in the secondary storage device(s) 108.

[0081] A secondary copy 116 can comprise a separate stored copy of application data that is derived from one or more earlier created, stored copies (e.g., derived from primary data 112 or another secondary copy 116). Secondary copies 116 can include point-in-time data, and may be intended for relatively long-term retention (e.g., weeks, months or years), before some or all of the data is moved to other storage or is discarded.

[0082] In some cases, a secondary copy 116 is a copy of application data created and stored subsequent to at least one other stored instance (e.g., subsequent to corresponding primary data 112 or to another secondary copy 116), in a different storage device than at least one previous stored copy, and/or remotely from at least one previous stored copy. Secondary copies 116 may be stored in relatively slow and/or low cost storage (e.g., magnetic tape). A secondary copy 116 may be stored in a backup or archive format, or in some other format different than the native source application format or other primary data format.

[0083] In some cases, secondary copies 116 are indexed so users can browse and restore at another point in time. After creation of a secondary copy 116 representative of certain primary data 112, a pointer or other location indicia (e.g., a stub) may be placed in primary data 112, or be otherwise associated with primary data 112 to indicate the current location on the secondary storage device(s) 108.

[0084] Since an instance a data object or metadata in primary data 112 may change over time as it is modified by an application 110 (or hosted service or the operating system), the information management system 100 may create and manage multiple secondary copies 116 of a particular data object or metadata, each representing the state of the data object in primary data 112 at a particular point in time. Moreover, since an instance of a data object in primary data 112 may eventually be deleted from the primary storage device 104 and the file system, the information management system 100 may continue to manage point-in-time representations of that data object, even though the instance in primary data 112 no longer exists.

[0085] For virtualized computing devices the operating system and other applications 110 of the client computing device(s) 102 may execute within or under the management of virtualization software (e.g., a VMM), and the primary storage device(s) 104 may comprise a virtual disk created on a physical storage device. The information management system 100 may create secondary copies 116 of the files or other data objects in a virtual disk file and/or secondary copies 116 of the entire virtual disk file itself (e.g., of an entire .vmdk file).

[0086] Secondary copies 116 may be distinguished from corresponding primary data 112 in a variety of ways, some of which will now be described. First, as discussed, secondary copies 116 can be stored in a different format (e.g., backup, archive, or other non-native format) than primary data 112. For this or other reasons, secondary copies 116 may not be directly useable by the applications 110 of the client computing device 102, e.g., via standard system calls or otherwise without modification, processing, or other intervention by the information management system 100.

[0087] Secondary copies 116 are also often stored on a secondary storage device 108 that is inaccessible to the applications 110 running on the client computing devices 102 (and/or hosted services). Some secondary copies 116 may be “offline copies,” in that they are not readily available (e.g. not mounted to tape or disk). Offline copies can include copies of data that the information management system 100 can access without human intervention (e.g. tapes within an automated tape library, but not yet mounted in a drive), and copies that the information management system 100 can access only with at least some human intervention (e.g. tapes located at an offsite storage site).

[0088] The secondary storage devices 108 can include any suitable type of storage device such as, without limitation, one or more tape libraries, disk drives or other magnetic, non-tape storage devices, optical media storage devices, solid state storage devices, NAS devices, combinations of the same, and the like. In some cases, the secondary storage devices 108 are provided in a cloud (e.g. a private cloud or one operated by a third-party vendor).

[0089] The secondary storage device(s) 108 in some cases comprises a disk array or a portion thereof. In some cases, a single storage device (e.g., a disk array) is used for storing both primary data 112 and at least some secondary copies 116. In one example, a disk array capable of performing hardware snapshots stores primary data 112 and creates and stores hardware snapshots of the primary data 112 as secondary copies 116.

The Use of Intermediary Devices For Creating Secondary Copies

[0090] Creating secondary copies can be a challenging task. For instance, there can be hundreds or thousands of client computing devices 102 continually generating large volumes of primary data 112 to be protected. Also, there can be significant overhead involved in the creation of secondary copies 116. Moreover, secondary storage devices 108 may be special purpose components, and interacting with them can require specialized intelligence.

[0091] In some cases, the client computing devices 102 interact directly with the secondary storage device 108 to create the secondary copies 116. However, in view of the factors described above, this approach can negatively impact the ability of the client computing devices 102 to serve the applications 110 and produce primary data 112. Further, the client computing devices 102 may not be optimized for interaction with the secondary storage devices 108.

[0092] Thus, in some embodiments, the information management system 100 includes one or more software and/or hardware components which generally act as intermediaries between the client computing devices 102 and the secondary storage devices 108. In addition to off-loading certain responsibilities from the client computing devices 102, these intermediary components can provide other benefits. For instance, as discussed further below with respect to FIG. 1D, distributing some of the work involved in creating secondary copies 116 can enhance scalability.

[0093] The intermediary components can include one or more secondary storage computing devices 106 as shown in FIG. 1A and/or one or more media agents, which can be software modules residing on corresponding secondary storage computing devices 106 (or other appropriate devices). Media agents are discussed below (e.g., with respect to FIGS. 1C-1E).

[0094] The secondary storage computing device(s) 106 can comprise any appropriate type of computing device and can include, without limitation, any of the types of fixed and portable computing devices described above with respect to the client computing devices 102. In some cases, the secondary storage computing device(s) 106 include specialized hardware and/or software componentry for interacting with the secondary storage devices 108.

[0095] To create a secondary copy 116, the client computing device 102 communicates the primary data 112 to be copied (or a processed version thereof) to the designated secondary storage computing device 106, via the communication pathway 114. The secondary storage computing device 106 in turn conveys the received data (or a processed version thereof) to the secondary storage device 108. In some such configurations, the communication pathway 114 between the client computing device 102 and the secondary storage computing device 106 comprises a portion of a LAN, WAN or SAN. In other cases, at least some client computing devices 102 communicate directly with the secondary storage devices 108 (e.g., via Fibre Channel or SCSI connections).

Exemplary Primary Data and an Exemplary Secondary Copy

[0096] FIG. 1B is a detailed view showing some specific examples of primary data stored on the primary storage device(s) 104 and secondary copy data stored on the secondary storage device(s) 108, with other components in the system removed for the purposes of illustration. Stored on the primary storage device(s) 104 are primary data objects including word processing documents 119A-B, spreadsheets 120, presentation documents 122, video files 124, image files 126, email mailboxes 128 (and corresponding email messages 129A-C), html/xml or other types of markup language files 130, databases 132 and corresponding tables 133A-133C).

[0097] Some or all primary data objects are associated with a primary copy of object metadata (e.g., “Meta1-11”), which may be file system metadata and/or application specific metadata. Stored on the secondary storage device(s) 108 are secondary copy objects 134A-C which may include copies of or otherwise represent corresponding primary data objects and metadata.

[0098] As shown, the secondary copy objects 134A-C can individually represent more than one primary data object. For example, secondary copy data object 134A represents three separate primary data objects 133C, 122 and 129C (represented as 133C′, 122′ and 129C′, respectively). Moreover, as indicated by the prime mark (′), a secondary copy object may store a representation of a primary data object or metadata differently than the original format, e.g., in a compressed, encrypted, deduplicated, or other modified format.

Exemplary Information Management System Architecture

[0099] The information management system 100 can incorporate a variety of different hardware and software components, which can in turn be organized with respect to one another in many different configurations, depending on the embodiment. There are critical design choices involved in specifying the functional responsibilities of the components and the role of each component in the information management system 100. For instance, as will be discussed, such design choices can impact performance as well as the adaptability of the information management system 100 to data growth or other changing circumstances.

[0100] FIG. 1C shows an information management system 100 designed according to these considerations and which includes: a central storage or information manager 140 configured to perform certain control functions, one or more data agents 142 executing on the client computing device(s) 102 configured to process primary data 112, and one or more media agents 144 executing on the one or more secondary storage computing devices 106 for performing tasks involving the secondary storage devices 108.

[0101] Storage Manager

[0102] As noted, the number of components in the information management system 100 and the amount of data under management can be quite large. Managing the components and data is therefore a significant task, and a task that can grow in an often unpredictable fashion as the quantity of components and data scale to meet the needs of the organization.

[0103] For these and other reasons, according to certain embodiments, responsibility for controlling the information management system 100, or at least a significant portion of that responsibility, is allocated to the storage manager 140.

[0104] By distributing control functionality in this manner, the storage manager 140 can be adapted independently according to changing circumstances. Moreover, a host computing device can be selected to best suit the functions of the storage manager 140. These and other advantages are described in further detail below with respect to FIG. 1D.

[0105] The storage manager 140 may be a software module or other application. The storage manager generally initiates, coordinates and/or controls storage and other information management operations performed by the information management system 100, e.g., to protect and control the primary data 112 and secondary copies 116 of data and metadata.

[0106] As shown by the dashed, arrowed lines, the storage manager 140 may communicate with and/or control some or all elements of the information management system 100, such as the data agents 142 and media agents 144. Thus, in certain embodiments, control information originates from the storage manager 140, whereas payload data and metadata is generally communicated between the data agents 142 and the media agents 144 (or otherwise between the client computing device(s) 102 and the secondary storage computing device(s) 106), e.g., at the direction of the storage manager 140. In other embodiments, some information management operations are controlled by other components in the information management system 100 (e.g., the media agent(s) 144 or data agent(s) 142), instead of or in combination with the storage manager 140.

[0107] According to certain embodiments, the storage manager provides one or more of the following functions:

- [0108] initiating execution of secondary copy operations;
- [0109] managing secondary storage devices 108 and inventory/capacity of the same;
- [0110] allocating secondary storage devices 108 for secondary storage operations;
- [0111] monitoring completion of and providing status reporting related to secondary storage operations;
- [0112] tracking age information relating to secondary copies 116, secondary storage devices 108, and comparing the age information against retention guidelines;
- [0113] tracking movement of data within the information management system 100;
- [0114] tracking logical associations between components in the information management system 100;
- [0115] protecting metadata associated with the information management system 100; and
- [0116] implementing operations management functionality.

[0117] The storage manager 140 may maintain a database 146 of management-related data and information management policies 148. The database 146 may include a management index 150 or other data structure that stores logical associations between components of the system, user preferences and/or profiles (e.g., preferences regarding encryption, compression, or deduplication of primary or secondary copy data, preferences regarding the scheduling, type, or other aspects of primary or secondary copy or other operations, mappings of particular information management users or user accounts to certain computing devices or other components, etc.), management tasks, media containerization, or other useful data. For example, the storage manager 140 may use the index 150 to track logical associations between media agents 144 and secondary storage devices 108 and/or movement of data from primary storage devices 104 to secondary storage devices 108.

[0118] Administrators and other employees may be able to manually configure and initiate certain information management operations on an individual basis. But while this may be acceptable for some recovery operations or other relatively less frequent tasks, it is often not workable for implementing on-going organization-wide data protection and management.

[0119] Thus, the information management system 100 may utilize information management policies 148 for specifying and executing information management operations (e.g., on an automated basis). Generally, an information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with storage or other information management operations.

[0120] The storage manager database 146 may maintain the information management policies 148 and associated data, although the information management policies 148 can be stored in any appropriate location. For instance, a storage policy may be stored as metadata in a media agent database 152 or in a secondary storage device 108 (e.g., as an archive copy) for use in restore operations or other information management operations, depending on the embodiment. Information management policies 148 are described further below.

[0121] According to certain embodiments, the storage manager database 146 comprises a relational database (e.g., an SQL database) for tracking metadata, such as metadata associated with secondary copy operations (e.g., what client computing devices 102 and corresponding data were protected). This and other metadata may additionally be stored in other locations, such as at the secondary storage computing devices 106 or on the secondary storage devices 108, allowing data recovery without the use of the storage manager 140.

[0122] As shown, the storage manager 140 may include a jobs agent 156, a user interface 158, and a management agent 154, all of which may be implemented as interconnected software modules or application programs.

[0123] The jobs agent 156 in some embodiments initiates, controls, and/or monitors the status of some or all storage or other information management operations previously performed, currently being performed, or scheduled to be performed by the information management system 100. For instance, the jobs agent 156 may access information management policies 148 to determine when and how to initiate and control secondary copy and other information management operations, as will be discussed further.

[0124] The user interface 158 may include information processing and display software, such as a graphical user interface (“GUI”), an application program interface (“API”), or other interactive interface through which users and system processes can retrieve information about the status of information management operations (e.g., storage operations) or issue instructions to the information management system 100 and its constituent components.

[0125] The storage manager 140 may also track information that permits it to select, designate, or otherwise identify content indices, deduplication databases, or similar databases or resources or data sets within its information management cell (or another cell) to be searched in response to certain queries. Such queries may be entered by the user via interaction with the user interface 158.

[0126] Via the user interface 158, users may optionally issue instructions to the components in the information management system 100 regarding performance of storage and recovery operations. For example, a user may modify a schedule concerning the number of pending secondary copy operations. As another example, a user may employ the GUI to view the status of pending storage operations or to monitor the status of certain components in the information management system 100 (e.g., the amount of capacity left in a storage device).

[0127] In general, the management agent 154 allows multiple information management systems 100 to communicate with one another. For example, the information management system 100 in some cases may be one information management subsystem or “cell” of a network of multiple cells adjacent to one another or otherwise logically related in a WAN or LAN. With this arrangement, the cells may be connected to one another through respective management agents 154.

[0128] For instance, the management agent 154 can provide the storage manager 140 with the ability to communicate with other components within the information management system 100 (and/or other cells within a larger information management system) via network protocols and application programming interfaces (“APIs”) including, e.g., HTTP, HTTPS, FTP, REST, virtualization software APIs, cloud service provider APIs, and hosted service provider APIs. Inter-cell communication and hierarchy is described in greater detail in U.S. Pat. No. 7,035,880, which is incorporated by reference herein.

[0129] Data Agents

[0130] As discussed, a variety of different types of applications 110 can reside on a given client computing device 102, including operating systems, database applications, e-mail applications, and virtual machines, just to name a few. And, as part of the as part of the process of creating and restoring secondary copies 116, the client computing devices 102 may be tasked with processing and preparing the primary data 112 from these various different applications 110. Moreover, the nature of the processing/preparation can differ across clients and application types, e.g., due to inherent structural and formatting differences between applications 110.

[0131] The one or more data agent(s) 142 are therefore advantageously configured in some embodiments to assist in the performance of information management operations based on the type of data that is being protected, at a client-specific and/or application-specific level.

[0132] The data agent 142 may be a software module or component that is generally responsible for managing, initiating, or otherwise assisting in the performance of information management operations. For instance, the data agent 142 may take part in performing data storage operations such as the copying, archiving, migrating, replicating of primary data 112 stored in the primary storage device(s) 104. The data agent 142 may receive control information from the storage manager 140, such as commands to transfer copies of data objects, metadata, and other payload data to the media agents 144.

[0133] In some embodiments, a data agent 142 may be distributed between the client computing device 102 and storage manager 140 (and any other intermediate components) or may be deployed from a remote location or its functions approximated by a remote process that performs some or all of the functions of data agent 142. In addition, a data agent 142 may perform some functions provided by a media agent 144, e.g., encryption and deduplication.

[0134] As indicated, each data agent 142 may be specialized for a particular application 110, and the system can employ multiple data agents 142, each of which may backup, migrate, and recover data associated with a different application 110. For instance, different individual data agents 142 may be designed to handle Microsoft Exchange data, Lotus Notes data, Microsoft Windows file system data, Microsoft Active Directory Objects data, SQL Server data, SharePoint data, Oracle database data, SAP database data, virtual machines and/or associated data, and other types of data.

[0135] A file system data agent, for example, may handle data files and/or other file system information. If a client computing device 102 has two or more types of data, one data agent 142 may be used for each data type to copy, archive, migrate, and restore the client computing device 102 data. For example, to backup, migrate, and restore all of the data on a Microsoft Exchange server, the client computing device 102 may use one Microsoft Exchange Mailbox data agent 142 to backup the Exchange mailboxes, one Microsoft Exchange Database data agent 142 to backup the Exchange databases, one Microsoft Exchange Public Folder data agent 142 to backup the Exchange Public Folders, and one Microsoft Windows File System data agent 142 to backup the file system of the client computing device 102. In such embodiments, these data agents 142 may be treated as four separate data agents 142 by even though they reside on the same client computing device 102.

[0136] 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.

[0137] Each data agent 142 may be configured to access data and/or metadata stored in the primary storage device(s) 104 associated with the data agent 142 and process the data as appropriate. For example, during a secondary copy operation, the data agent 142 may arrange or assemble the data and metadata into one or more files having a certain format (e.g., a particular backup or archive format) before transferring the file(s) to a media agent 144 or other component. The file(s) may include a list of files or other metadata. Each data agent 142 can also assist in restoring data or metadata to primary storage devices 104 from a secondary copy 116. For instance, the data agent 142 may operate in conjunction with the storage manager 140 and one or more of the media agents 144 to restore data from secondary storage device(s) 108.

[0138] Media Agents

[0139] As indicated above with respect to FIG. 1A, off-loading certain responsibilities from the client computing devices 102 to intermediary components such as the media agent(s) 144 can provide a number of benefits including improved client computing device 102 operation, faster secondary copy operation performance, and enhanced scalability. As one specific example which will be discussed below in further detail, the media agent 144 can act as a local cache of copied data and/or metadata that it has stored to the secondary storage device(s) 108, providing improved restore capabilities.

[0140] Generally speaking, a media agent 144 may be implemented as a software module that manages, coordinates, and facilitates the transmission of data, as directed by the storage manager 140, between a client computing device 102 and one or more secondary storage devices 108. Whereas the storage manager 140 controls the operation of the information management system 100, the media agent 144 generally provides a portal to secondary storage devices 108.

[0141] Media agents 144 can comprise logically and/or physically separate nodes in the information management system 100 (e.g., separate from the client computing devices 102, storage manager 140, and/or secondary storage devices 108). In addition, each media agent 144 may reside on a dedicated secondary storage computing device 106 in some cases, while in other embodiments a plurality of media agents 144 reside on the same secondary storage computing device 106.

[0142] A media agent 144 (and corresponding media agent database 152) may be considered to be “associated with” a particular secondary storage device 108 if that media agent 144 is capable of one or more of: routing and/or storing data to the particular secondary storage device 108, coordinating the routing and/or storing of data to the particular secondary storage device 108, retrieving data from the particular secondary storage device 108, and coordinating the retrieval of data from a particular secondary storage device 108.

[0143] While media agent(s) 144 are generally associated with one or more secondary storage devices 108, the media agents 144 in certain embodiments are physically separate from the secondary storage devices 108. For instance, the media agents 144 may reside on secondary storage computing devices 106 having different housings or packages than the secondary storage devices 108. In one example, a media agent 144 resides on a first server computer and is in communication with a secondary storage device(s) 108 residing in a separate, rack-mounted RAID-based system.

[0144] In operation, a media agent 144 associated with a particular secondary storage device 108 may instruct the secondary storage device 108 (e.g., a tape library) to use a robotic arm or other retrieval means to load or eject a certain storage media, and to subsequently archive, migrate, or retrieve data to or from that media, e.g., for the purpose of restoring the data to a client computing device 102. The media agent 144 may communicate with a secondary storage device 108 via a suitable communications link, such as a SCSI or Fiber Channel link.

[0145] As shown, each media agent 144 may maintain an associated media agent database 152. The media agent database 152 may be stored in a disk or other storage device (not shown) that is local to the secondary storage computing device 106 on which the media agent 144 resides. In other cases, the media agent database 152 is stored remotely from the secondary storage computing device 106.

[0146] The media agent database 152 can include, among other things, an index 153 including data generated during secondary copy operations and other storage or information management operations. The index 153 provides a media agent 144 or other component with a fast and efficient mechanism for locating secondary copies 116 or other data stored in the secondary storage devices 108. In one configuration, a storage manager index 150 or other data structure may store data associating a client computing device 102 with a particular media agent 144 and/or secondary storage device 108, as specified in a storage policy. A media agent index 153 or other data structure associated with the particular media agent 144 may in turn include information about the stored data.

[0147] For instance, for each secondary copy 116, the index 153 may include metadata such as a list of the data objects (e.g., files/subdirectories, database objects, mailbox objects, etc.), a path to the secondary copy 116 on the corresponding secondary storage device 108, location information indicating where the data objects are stored in the secondary storage device 108, when the data objects were created or modified, etc. Thus, the index 153 includes metadata associated with the secondary copies 116 that is readily available for use in storage operations and other activities without having to be first retrieved from the secondary storage device 108. In yet further embodiments, some or all of the data in the index 153 may instead or additionally be stored along with the data in a secondary storage device 108, e.g., with a copy of the index 153.

[0148] Because the index 153 maintained in the database 152 may operate as a cache, it can also be referred to as an index cache. In such cases, information stored in the index cache 153 typically comprises data that reflects certain particulars about storage operations that have occurred relatively recently. After some triggering event, such as after a certain period of time elapses, or the index cache 153 reaches a particular size, the index cache 153 may be copied or migrated to a secondary storage device(s) 108. This information may need to be retrieved and uploaded back into the index cache 153 or otherwise restored to a media agent 144 to facilitate retrieval of data from the secondary storage device(s) 108. In some embodiments, the cached information may include format or containerization information related to archives or other files stored on the storage device(s) 108. In this manner, the index cache 153 allows for accelerated restores.

[0149] In some alternative embodiments the media agent 144 generally acts as a coordinator or facilitator of storage operations between client computing devices 102 and corresponding secondary storage devices 108, but does not actually write the data to the secondary storage device 108. For instance, the storage manager 140 (or the media agent 144) may instruct a client computing device 102 and secondary storage device 108 to communicate with one another directly. In such a case the client computing device 102 transmits the data directly to the secondary storage device 108 according to the received instructions, and vice versa. In some such cases, the media agent 144 may still receive, process, and/or maintain metadata related to the storage operations. Moreover, in these embodiments, the payload data can flow through the media agent 144 for the purposes of populating the index cache 153 maintained in the media agent database 152, but not for writing to the secondary storage device 108.

[0150] The media agent 144 and/or other components such as the storage manager 140 may in some cases incorporate additional functionality, such as data classification, content indexing, deduplication, encryption, compression, and the like. Further details regarding these and other functions are described below.

[0151] Distributed, Scalable Architecture

[0152] As described, certain functions of the information management system 100 can be distributed amongst various physical and/or logical components in the system. For instance, one or more of the storage manager 140, data agents 142, and media agents 144 may reside on computing devices that are physically separate from one another. This architecture can provide a number of benefits.

[0153] For instance, hardware and software design choices for each distributed component can be targeted to suit its particular function. The secondary computing devices 106 on which the media agents 144 reside can be tailored for interaction with associated secondary storage devices 108 and provide fast index cache operation, among other specific tasks. Similarly, the client computing device(s) 102 can be selected to effectively service the applications 110 residing thereon, in order to efficiently produce and store primary data 112.

[0154] Moreover, in some cases, one or more of the individual components in the information management system 100 can be distributed to multiple, separate computing devices. As one example, for large file systems where the amount of data stored in the storage management database 146 is relatively large, the management database 146 may be migrated to or otherwise reside on a specialized database server (e.g., an SQL server) separate from a server that implements the other functions of the storage manager 140. This configuration can provide added protection because the database 146 can be protected with standard database utilities (e.g., SQL log shipping or database replication) independent from other functions of the storage manager 140. The database 146 can be efficiently replicated to a remote site for use in the event of a disaster or other data loss incident at the primary site. Or the database 146 can be replicated to another computing device within the same site, such as to a higher performance machine in the event that a storage manager host device can no longer service the needs of a growing information management system 100.

[0155] The distributed architecture also provides both scalability and efficient component utilization. FIG. 1D shows an embodiment of the information management system 100 including a plurality of client computing devices 102 and associated data agents 142 as well as a plurality of secondary storage computing devices 106 and associated media agents 144.

[0156] Additional components can be added or subtracted based on the evolving needs of the information management system 100. For instance, depending on where bottlenecks are identified, administrators can add additional client computing devices 102, secondary storage devices 106 (and corresponding media agents 144), and/or secondary storage devices 108.

[0157] Moreover, each client computing device 102 in some embodiments can communicate with any of the media agents 144, e.g., as directed by the storage manager 140. And each media agent 144 may be able to communicate with any of the secondary storage devices 108, e.g., as directed by the storage manager 140. Thus, operations can be routed to the secondary storage devices 108 in a dynamic and highly flexible manner. Further examples of scalable systems capable of dynamic storage operations are provided in U.S. Pat. No. 7,246,207, which is incorporated by reference herein.

[0158] In alternative configurations, certain components are not distributed and may instead reside and execute on the same computing device. For example, in some embodiments one or more data agents 142 and the storage manager 140 reside on the same client computing device 102. In another embodiment, one or more data agents 142 and one or more media agents 144 reside on a single computing device.

Exemplary Types of Information Management Operations

[0159] In order to protect and leverage stored data, the information management system 100 can be configured to perform a variety of information management operations. As will be described, these operations can generally include secondary copy and other data movement operations, processing and data manipulation operations, and management operations.

[0160] Data Movement Operations

[0161] Data movement operations according to certain embodiments are generally operations that involve the copying or migration of data (e.g., payload data) between different locations in the information management system 100. For example, data movement operations can include operations in which stored data is copied, migrated, or otherwise transferred from primary storage device(s) 104 to secondary storage device(s) 108, from secondary storage device(s) 108 to different secondary storage device(s) 108, or from primary storage device(s) 104 to different primary storage device(s) 104.

[0162] Data movement operations can include by way of example, backup operations, archive operations, information lifecycle management operations such as hierarchical storage management operations, replication operations (e.g., continuous data replication operations), snapshot operations, deduplication operations, single-instancing operations, auxiliary copy operations, and the like. As will be discussed, some of these operations involve the copying, migration or other movement of data, without actually creating multiple, distinct copies. Nonetheless, some or all of these operations are referred to as “copy” operations for simplicity.

[0163] Backup Operations

[0164] A backup operation creates a copy of primary data 112 at a particular point in time. Each subsequent backup copy may be maintained independently of the first. Further, a backup copy in some embodiments is stored in a backup format. This can be in contrast to the version in primary data 112 from which the backup copy is derived, and which may instead be stored in a native format of the source application(s) 110. In various cases, backup copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format. For example, a backup copy may be stored in a backup format that facilitates compression and/or efficient long-term storage.

[0165] Backup copies can have relatively long retention periods as compared to primary data 112, and may be stored on media with slower retrieval times than primary data 112 and certain other types of secondary copies 116. On the other hand, backups may have relatively shorter retention periods than some other types of secondary copies 116, such as archive copies (described below). Backups may sometimes be stored at on offsite location.

[0166] Backup operations can include full, synthetic or incremental backups. A full backup in some embodiments is generally a complete image of the data to be protected. However, because full backup copies can consume a relatively large amount of storage, it can be useful to use a full backup copy as a baseline and only store changes relative to the full backup copy for subsequent backup copies.

[0167] For instance, a differential backup operation (or cumulative incremental backup operation) tracks and stores changes that have occurred since the last full backup. Differential backups can grow quickly in size, but can provide relatively efficient restore times because a restore can be completed in some cases using only the full backup copy and the latest differential copy.

[0168] An incremental backup operation generally tracks and stores changes since the most recent backup copy of any type, which can greatly reduce storage utilization. In some cases, however, restore times can be relatively long in comparison to full or differential backups because completing a restore operation may involve accessing a full backup in addition to multiple incremental backups.

[0169] Any of the above types of backup operations can be at the file-level, e.g., where the information management system 100 generally tracks changes to files at the file-level, and includes copies of files in the backup copy. In other cases, block-level backups are employed, where files are broken into constituent blocks, and changes are tracked at the block-level. Upon restore, the information management system 100 reassembles the blocks into files in a transparent fashion.

[0170] Far less data may actually be transferred and copied to the secondary storage devices 108 during a block-level copy than during a file-level copy, resulting in faster execution times. However, when restoring a block-level copy, the process of locating constituent blocks can sometimes result in longer restore times as compared to file-level backups. Similar to backup operations, the other types of secondary copy operations described herein can also be implemented at either the file-level or the block-level.

[0171] Archive Operations

[0172] Because backup operations generally involve maintaining a version of the copied data in primary data 112 and also maintaining backup copies in secondary storage device(s) 108, they can consume significant storage capacity. To help reduce storage consumption, an archive operation according to certain embodiments creates a secondary copy 116 by both copying and removing source data. Or, seen another way, archive operations can involve moving some or all of the source data to the archive destination. Thus, data satisfying criteria for removal (e.g., data of a threshold age or size) from the source copy may be removed from source storage. Archive copies are sometimes stored in an archive format or other non-native application format. The source data may be primary data 112 or a secondary copy 116, depending on the situation. As with backup copies, archive copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format.

[0173] In addition, archive copies may be retained for relatively long periods of time (e.g., years) and, in some cases, are never deleted. Archive copies are generally retained for longer periods of time than backup copies, for example. In certain embodiments, archive copies may be made and kept for extended periods in order to meet compliance regulations.

[0174] Moreover, when primary data 112 is archived, in some cases the archived primary data 112 or a portion thereof is deleted when creating the archive copy. Thus, archiving can serve the purpose of freeing up space in the primary storage device(s) 104. Similarly, when a secondary copy 116 is archived, the secondary copy 116 may be deleted, and an archive copy can therefore serve the purpose of freeing up space in secondary storage device(s) 108. In contrast, source copies often remain intact when creating backup copies.

[0175] Snapshot Operations

[0176] Snapshot operations can provide a relatively lightweight, efficient mechanism for protecting data. From an end-user viewpoint, a snapshot may be thought of as an “instant” image of the primary data 112 at a given point in time. In one embodiment, a snapshot may generally capture the directory structure of an object in primary data 112 such as a file or volume or other data set at a particular moment in time and may also preserve file attributes and contents. A snapshot in some cases is created relatively quickly, e.g., substantially instantly, using a minimum amount of file space, but may still function as a conventional file system backup.

[0177] 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.

[0178] Some types of snapshots do not actually create another physical copy of all the data as it existed at the particular point in time, but may simply create pointers that are able to map files and directories to specific memory locations (e.g., disk blocks) where the data resides, as it existed at the particular point in time. For example, a snapshot copy may include a set of pointers derived from the file system or an application. Each pointer points to a respective stored data block, so collectively, the set of pointers reflect the storage location and state of the data object (e.g., file(s) or volume(s) or data set(s)) at a particular point in time when the snapshot copy was created.

[0179] In some embodiments, once a snapshot has been taken, subsequent changes to the file system typically do not overwrite the blocks in use at the time of the snapshot. Therefore, the initial snapshot may use only a small amount of disk space needed to record a mapping or other data structure representing or otherwise tracking the blocks that correspond to the current state of the file system. Additional disk space is usually required only when files and directories are actually modified later. Furthermore, when files are modified, typically only the pointers which map to blocks are copied, not the blocks themselves. In some embodiments, for example in the case of “copy-on-write” snapshots, when a block changes in primary storage, the block is copied to secondary storage or cached in primary storage before the block is overwritten in primary storage. The snapshot mapping of file system data is also updated to reflect the changed block(s) at that particular point in time. In some other cases, a snapshot includes a full physical copy of all or substantially all of the data represented by the snapshot. Further examples of snapshot operations are provided in U.S. Pat. No. 7,529,782, which is incorporated by reference herein.

[0180] Replication Operations

[0181] Another type of secondary copy operation is a replication operation. Some types of secondary copies 116 are used to periodically capture images of primary data 112 at particular points in time (e.g., backups, archives, and snapshots). However, it can also be useful for recovery purposes to protect primary data 112 in a more continuous fashion, by replicating the primary data 112 substantially as changes occur. In some cases a replication copy can be a mirror copy, for instance, where changes made to primary data 112 are mirrored to another location (e.g., to secondary storage device(s) 108). By copying each write operation to the replication copy, two storage systems are kept synchronized or substantially synchronized so that they are virtually identical at approximately the same time. Where entire disk volumes are mirrored, however, mirroring can require significant amount of storage space and utilizes a large amount of processing resources.

[0182] According to some embodiments storage operations are performed on replicated data that represents a recoverable state, or “known good state” of a particular application running on the source system. For instance, in certain embodiments, known good replication copies may be viewed as copies of primary data 112. This feature allows the system to directly access, copy, restore, backup or otherwise manipulate the replication copies as if the data was the “live”, primary data 112. This can reduce access time, storage utilization, and impact on source applications 110, among other benefits.

[0183] Based on known good state information, the information management system 100 can replicate sections of application data that represent a recoverable state rather than rote copying of blocks of data. Examples of compatible replication operations (e.g., continuous data replication) are provided in U.S. Pat. No. 7,617,262, which is incorporated by reference herein.

[0184] Deduplication/Single-Instancing Operations

[0185] Another type of data movement operation is deduplication, which is useful to reduce the amount of data within the system. For instance, some or all of the above-described secondary storage operations can involve deduplication in some fashion. New data is read, broken down into blocks (e.g., sub-file level blocks) of a selected granularity, compared with blocks that are already stored, and only the new blocks are stored. Blocks that already exist are represented as pointers to the already stored data.

[0186] In order to stream-line the comparison process, the information management system 100 may calculate and/or store signatures (e.g., hashes) corresponding to the individual data blocks and compare the hashes instead of comparing entire data blocks. In some cases, only a single instance of each element is stored, and deduplication operations may therefore be referred to interchangeably as “single-instancing” operations. Depending on the implementation, however, deduplication or single-instancing operations can store more than one instance of certain data blocks, but nonetheless significantly reduce data redundancy. Moreover, single-instancing in some cases is distinguished from deduplication as a process of analyzing and reducing data at the file level, rather than the sub-file level.

[0187] Depending on the embodiment, deduplication blocks can be of fixed or variable length. Using variable length blocks can provide enhanced deduplication by responding to changes in the data stream, but can involve complex processing. In some cases, the information management system 100 utilizes a technique for dynamically aligning deduplication blocks (e.g., fixed-length blocks) based on changing content in the data stream, as described in U.S. Pat. Pub. No. 2012/0084268, which is incorporated by reference herein.

[0188] The information management system 100 can perform deduplication in a variety of manners at a variety of locations in the information management system 100. For instance, in some embodiments, the information management system 100 implements “target-side” deduplication by deduplicating data (e.g., secondary copies 116) stored in the secondary storage devices 108. In some such cases, the media agents 144 are generally configured to manage the deduplication process. For instance, one or more of the media agents 144 maintain a corresponding deduplication database that stores deduplication information (e.g., datablock signatures). Examples of such a configuration are provided in U.S. Pat. Pub. No. 2012/0150826, which is incorporated by reference herein. Deduplication can also be performed on the “source-side” (or “client-side”), e.g., to reduce the amount of traffic between the media agents 144 and the client computing device(s) 102 and/or reduce redundant data stored in the primary storage devices 104. Examples of such deduplication techniques are provided in U.S. Pat. Pub. No. 2012/0150818, which is incorporated by reference herein.

[0189] Information Lifecycle Management and Hierarchical Storage Management Operations

[0190] 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.

[0191] One type of ILM operation is a hierarchical storage management (HSM) operation. A HSM operation is generally an operation for automatically moving data between classes of storage devices, such as between high-cost and low-cost storage devices. For instance, an HSM operation may involve movement of data from primary storage devices 104 to secondary storage devices 108, or between tiers of secondary storage devices 108. With each tier, the storage devices may be progressively relatively cheaper, have relatively slower access/restore times, etc. For example, movement of data between tiers may occur as data becomes less important over time.

[0192] In some embodiments, an HSM operation is similar to an archive operation in that creating an HSM copy may (though not always) involve deleting some of the source data. For example, an HSM copy may include data from primary data 112 or a secondary copy 116 that is larger than a given size threshold or older than a given age threshold and that is stored in a backup format.

[0193] Often, and unlike some types of archive copies, HSM data that is removed or aged from the source copy is replaced by a logical reference pointer or stub. The reference pointer or stub can be stored in the primary storage device 104 to replace the deleted data in primary data 112 (or other source copy) and to point to or otherwise indicate the new location in a secondary storage device 108.

[0194] According to one example, files are generally moved between higher and lower cost storage depending on how often the files are accessed. When a user requests access to the HSM data that has been removed or migrated, the information management system 100 uses the stub to locate the data and often make recovery of the data appear transparent, even though the HSM data may be stored at a location different from the remaining source data. The stub may also include some metadata associated with the corresponding data, so that a file system and/or application can provide some information about the data object and/or a limited-functionality version (e.g., a preview) of the data object.

[0195] An HSM copy may be stored in a format other than the native application format (e.g., where the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format). In some cases, copies which involve the removal of data from source storage and the maintenance of stub or other logical reference information on source storage may be referred to generally as “on-line archive copies”. On the other hand, copies which involve the removal of data from source storage without the maintenance of stub or other logical reference information on source storage may be referred to as “off-line archive copies”.

[0196] Auxiliary Copy and Disaster Recovery Operations

[0197] An auxiliary copy is generally a copy operation in which a copy is created of an existing secondary copy 116. For instance, an initial or “primary” secondary copy 116 may be generated using or otherwise be derived from primary data 112, whereas an auxiliary copy is generated from the initial secondary copy 116. Auxiliary copies can be used to create additional standby copies of data and may reside on different secondary storage devices 108 than initial secondary copies 116. Thus, auxiliary copies can be used for recovery purposes if initial secondary copies 116 become unavailable. Exemplary compatible auxiliary copy techniques are described in further detail in U.S. Pat. No. 8,230,195, which is incorporated by reference herein.

[0198] The information management system 100 may also perform disaster recovery operations that make or retain disaster recovery copies, often as secondary, high-availability disk copies. The information management system 100 may create secondary disk copies and store the copies at disaster recovery locations using auxiliary copy or replication operations, such as continuous data replication technologies. Depending on the particular data protection goals, disaster recovery locations can be remote from the client computing devices 102 and primary storage devices 104, remote from some or all of the secondary storage devices 108, or both.

[0199] Data Processing and Manipulation Operations

[0200] As indicated, the information management system 100 can also be configured to implement certain data manipulation operations, which according to certain embodiments are generally operations involving the processing or modification of stored data. Some data manipulation operations include content indexing operations and classification operations can be useful in leveraging the data under management to provide enhanced search and other features. Other data manipulation operations such as compression and encryption can provide data reduction and security benefits, respectively.

[0201] Data manipulation operations can be different than data movement operations in that they do not necessarily involve the copying, migration or other transfer of data (e.g., primary data 112 or secondary copies 116) between different locations in the system. For instance, data manipulation operations may involve processing (e.g., offline processing) or modification of already stored primary data 112 and/or secondary copies 116. However, in some embodiments data manipulation operations are performed in conjunction with data movement operations. As one example, the information management system 100 may encrypt data while performing an archive operation.

[0202] Content Indexing

[0203] In some embodiments, the information management system 100 “content indexes” data stored within the primary data 112 and/or secondary copies 116, providing enhanced search capabilities for data discovery and other purposes. The content indexing can be used to identify files or other data objects having pre-defined content (e.g., user-defined keywords or phrases), metadata (e.g., email metadata such as “to”, “from”, “cc”, “bcc”, attachment name, received time, etc.).

[0204] The information management system 100 generally organizes and catalogues the results in a content index, which may be stored within the media agent database 152, for example. The content index can also include the storage locations of (or pointer references to) the indexed data in the primary data 112 or secondary copies 116, as appropriate. The results may also be stored, in the form of a content index database or otherwise, elsewhere in the information management system 100 (e.g., in the primary storage devices 104, or in the secondary storage device 108). Such index data provides the storage manager 140 or another component with an efficient mechanism for locating primary data 112 and/or secondary copies 116 of data objects that match particular criteria.

[0205] For instance, search criteria can be specified by a user through user interface 158 of the storage manager 140. In some cases, the information management system 100 analyzes data and/or metadata in secondary copies 116 to create an “off-line” content index, without significantly impacting the performance of the client computing devices 102. Depending on the embodiment, the system can also implement “on-line” content indexing, e.g., of primary data 112. Examples of compatible content indexing techniques are provided in U.S. Pat. No. 8,170,995, which is incorporated by reference herein.

[0206] Classification Operations—Metabase

[0207] In order to help leverage the data stored in the information management system 100, one or more components can be configured to scan data and/or associated metadata for classification purposes to populate a metabase of information. Such scanned, classified data and/or metadata may be included in a separate database and/or on a separate storage device from primary data 112 (and/or secondary copies 116), such that metabase related operations do not significantly impact performance on other components in the information management system 100.

[0208] In other cases, the metabase(s) may be stored along with primary data 112 and/or secondary copies 116. Files or other data objects can be associated with user-specified identifiers (e.g., tag entries) in the media agent 144 (or other indices) to facilitate searches of stored data objects. Among a number of other benefits, the metabase can also allow efficient, automatic identification of files or other data objects to associate with secondary copy or other information management operations (e.g., in lieu of scanning an entire file system). Examples of compatible metabases and data classification operations are provided in U.S. Pat. Nos. 8,229,954 and 7,747,579, which are incorporated by reference herein.

[0209] Encryption Operations

[0210] The information management system 100 in some cases is configured to process data (e.g., files or other data objects, secondary copies 116, etc.), according to an appropriate encryption algorithm (e.g., Blowfish, Advanced Encryption Standard [AES], Triple Data Encryption Standard [3-DES], etc.) to limit access and provide data security in the information management system 100.

[0211] The information management system 100 in some cases encrypts the data at the client level, such that the client computing devices 102 (e.g., the data agents 142) encrypt the data prior to forwarding the data to other components, e.g., before sending the data media agents 144 during a secondary copy operation. In such cases, the client computing device 102 may maintain or have access to an encryption key or passphrase for decrypting the data upon restore. Encryption can also occur when creating copies of secondary copies, e.g., when creating auxiliary copies. In yet further embodiments, the secondary storage devices 108 can implement built-in, high performance hardware encryption.

[0212] Management Operations

[0213] Certain embodiments leverage the integrated, ubiquitous nature of the information management system 100 to provide useful system-wide management functions. As two non-limiting examples, the information management system 100 can be configured to implement operations management and e-discovery functions.

[0214] Operations management can generally include monitoring and managing the health and performance of information management system 100 by, without limitation, performing error tracking, generating granular storage/performance metrics (e.g., job success/failure information, deduplication efficiency, etc.), generating storage modeling and costing information, and the like.

[0215] Such information can be provided to users via the user interface 158 in a single, integrated view. For instance, the integrated user interface 158 can include an option to show a “virtual view” of the system that graphically depicts the various components in the system using appropriate icons. The operations management functionality can facilitate planning and decision-making. For example, in some embodiments, a user may view the status of some or all jobs as well as the status of each component of the information management system 100. Users may then plan and make decisions based on this data. For instance, a user may view high-level information regarding storage operations for the information management system 100, such as job status, component status, resource status (e.g., network pathways, etc.), and other information. The user may also drill down or use other means to obtain more detailed information regarding a particular component, job, or the like.

[0216] In some cases the information management system 100 alerts a user such as a system administrator when a particular resource is unavailable or congested. For example, a particular primary storage device 104 or secondary storage device 108 might be full or require additional capacity. Or a component may be unavailable due to hardware failure, software problems, or other reasons. In response, the information management system 100 may suggest solutions to such problems when they occur (or provide a warning prior to occurrence). For example, the storage manager 140 may alert the user that a secondary storage device 108 is full or otherwise congested. The storage manager 140 may then suggest, based on job and data storage information contained in its database 146, an alternate secondary storage device 108.

[0217] Other types of corrective actions may include suggesting an alternate data path to a particular primary or secondary storage device 104, 108, or dividing data to be stored among various available primary or secondary storage devices 104, 108 as a load balancing measure or to otherwise optimize storage or retrieval time. Such suggestions or corrective actions may be performed automatically, if desired. Further examples of some compatible operations management techniques and of interfaces providing an integrated view of an information management system are provided in U.S. Pat. No. 7,343,453, which is incorporated by reference herein. In some embodiments, the storage manager 140 implements the operations management functions described herein.

[0218] The information management system 100 can also be configured to perform system-wide e-discovery operations in some embodiments. In general, e-discovery operations provide a unified collection and search capability for data in the system, such as data stored in the secondary storage devices 108 (e.g., backups, archives, or other secondary copies 116). For example, the information management system 100 may construct and maintain a virtual repository for data stored in the information management system 100 that is integrated across source applications 110, different storage device types, etc. According to some embodiments, e-discovery utilizes other techniques described herein, such as data classification and/or content indexing.

Information Management Policies

[0219] As indicated previously, an information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with secondary copy or other information management operations.

[0220] One type of information management policy 148 is a storage policy. According to certain embodiments, a storage policy generally comprises a logical container that defines (or includes information sufficient to determine) one or more of the following items: (1) what data will be associated with the storage policy; (2) a destination to which the data will be stored; (3) datapath information specifying how the data will be communicated to the destination; (4) the type of storage operation to be performed; and (5) retention information specifying how long the data will be retained at the destination.

[0221] Data associated with a storage policy can be logically organized into groups, which can be referred to as “sub-clients”. A sub-client may represent static or dynamic associations of portions of a data volume. Sub-clients may represent mutually exclusive portions. Thus, in certain embodiments, a portion of data may be given a label and the association is stored as a static entity in an index, database or other storage location.

[0222] Sub-clients may also be used as an effective administrative scheme of organizing data according to data type, department within the enterprise, storage preferences, or the like. Depending on the configuration, sub-clients can correspond to files, folders, virtual machines, databases, etc. In one exemplary scenario, an administrator may find it preferable to separate e-mail data from financial data using two different sub-clients.

[0223] A storage policy can define where data is stored by specifying a target or destination storage device (or group of storage devices). For instance, where the secondary storage device 108 includes a group of disk libraries, the storage policy may specify a particular disk library for storing the sub-clients associated with the policy. As another example, where the secondary storage devices 108 include one or more tape libraries, the storage policy may specify a particular tape library for storing the sub-clients associated with the storage policy, and may also specify a drive pool and a tape pool defining a group of tape drives and a group of tapes, respectively, for use in storing the sub-client data.

[0224] Datapath information can also be included in the storage policy. For instance, the storage policy may specify network pathways and components to utilize when moving the data to the destination storage device(s). In some embodiments, the storage policy specifies one or more media agents 144 for conveying data (e.g., one or more sub-clients) associated with the storage policy between the source (e.g., one or more host client computing devices 102) and destination (e.g., a particular target secondary storage device 108).

[0225] A storage policy can also specify the type(s) of operations associated with the storage policy, such as a backup, archive, snapshot, auxiliary copy, or the like. Retention information can specify how long the data will be kept, depending on organizational needs (e.g., a number of days, months, years, etc.)

[0226] The information management policies 148 may also include one or more scheduling policies specifying when and how often to perform operations. Scheduling information may specify with what frequency (e.g., hourly, weekly, daily, event-based, etc.) or under what triggering conditions secondary copy or other information management operations will take place. Scheduling policies in some cases are associated with particular components, such as particular sub-clients, client computing device 102, and the like. In one configuration, a separate scheduling policy is maintained for particular sub-clients on a client computing device 102. The scheduling policy specifies that those sub-clients are to be moved to secondary storage devices 108 every hour according to storage policies associated with the respective sub-clients.

[0227] When adding a new client computing device 102, administrators can manually configure information management policies 148 and/or other settings, e.g., via the user interface 158. However, this can be an involved process resulting in delays, and it may be desirable to begin data protecting operations quickly.

[0228] Thus, in some embodiments, the information management system 100 automatically applies a default configuration to client computing device 102. As one example, when a data agent(s) 142 is installed on a client computing devices 102, the installation script may register the client computing device 102 with the storage manager 140, which in turn applies the default configuration to the new client computing device 102. In this manner, data protection operations can begin substantially immediately. The default configuration can include a default storage policy, for example, and can specify any appropriate information sufficient to begin data protection operations. This can include a type of data protection operation, scheduling information, a target secondary storage device 108, data path information (e.g., a particular media agent 144), and the like.

[0229] Other types of information management policies 148 are possible. For instance, the information management policies 148 can also include one or more audit or security policies. An audit policy is a set of preferences, rules and/or criteria that protect sensitive data in the information management system 100. For example, an audit policy may define “sensitive objects” as files or objects that contain particular keywords (e.g. “confidential,” or “privileged”) and/or are associated with particular keywords (e.g., in metadata) or particular flags (e.g., in metadata identifying a document or email as personal, confidential, etc.).

[0230] An audit policy may further specify rules for handling sensitive objects. As an example, an audit policy may require that a reviewer approve the transfer of any sensitive objects to a cloud storage site, and that if approval is denied for a particular sensitive object, the sensitive object should be transferred to a local storage device 104 instead. To facilitate this approval, the audit policy may further specify how a secondary storage computing device 106 or other system component should notify a reviewer that a sensitive object is slated for transfer.

[0231] In some implementations, the information management policies 148 may include one or more provisioning policies. A provisioning policy can include a set of preferences, priorities, rules, and/or criteria that specify how clients 102 (or groups thereof) may utilize system resources, such as available storage on cloud storage and/or network bandwidth. A provisioning policy specifies, for example, data quotas for particular client computing devices 102 (e.g. a number of gigabytes that can be stored monthly, quarterly or annually). The storage manager 140 or other components may enforce the provisioning policy. For instance, the media agents 144 may enforce the policy when transferring data to secondary storage devices 108. If a client computing device 102 exceeds a quota, a budget for the client computing device 102 (or associated department) is adjusted accordingly or an alert may trigger.

[0232] While the above types of information management policies 148 have been described as separate policies, one or more of these can be generally combined into a single information management policy 148. For instance, a storage policy may also include or otherwise be associated with one or more scheduling, audit, or provisioning policies. Moreover, while storage policies are typically associated with moving and storing data, other policies may be associated with other types of information management operations. The following is a non-exhaustive list of items the information management policies 148 may specify:

- [0233] schedules or other timing information, e.g., specifying when and/or how often to perform information management operations;
- [0234] the type of secondary copy 116 and/or secondary copy format (e.g., snapshot, backup, archive, HSM, etc.);
- [0235] a location or a class or quality of storage for storing secondary copies 116 (e.g., one or more particular secondary storage devices 108);
- [0236] preferences regarding whether and how to encrypt, compress, deduplicate, or otherwise modify or transform secondary copies 116;
- [0237] which system components and/or network pathways (e.g., preferred media agents 144) should be used to perform secondary storage operations;
- [0238] resource allocation between different computing devices or other system components used in performing information management operations (e.g., bandwidth allocation, available storage capacity, etc.);
- [0239] whether and how to synchronize or otherwise distribute files or other data objects across multiple computing devices or hosted services; and
- [0240] retention information specifying the length of time primary data 112 and/or secondary copies 116 should be retained, e.g., in a particular class or tier of storage devices, or within the information management system 100.

[0241] Policies can additionally specify or depend on a variety of historical or current criteria that may be used to determine which rules to apply to a particular data object, system component, or information management operation, such as:

- [0242] frequency with which primary data 112 or a secondary copy 116 of a data object or metadata has been or is predicted to be used, accessed, or modified;
- [0243] time-related factors (e.g., aging information such as time since the creation or modification of a data object);
- [0244] deduplication information (e.g., hashes, data blocks, deduplication block size, deduplication efficiency or other metrics);
- [0245] an estimated or historic usage or cost associated with different components (e.g., with secondary storage devices 108);
- [0246] the identity of users, applications 110, client computing devices 102 and/or other computing devices that created, accessed, modified, or otherwise utilized primary data 112 or secondary copies 116;
- [0247] a relative sensitivity (e.g., confidentiality) of a data object, e.g., as determined by its content and/or metadata;
- [0248] the current or historical storage capacity of various storage devices;
- [0249] the current or historical network capacity of network pathways connecting various components within the storage operation cell;
- [0250] access control lists or other security information; and
- [0251] the content of a particular data object (e.g., its textual content) or of metadata associated with the data object.
  Exemplary Storage Policy and Secondary Storage Operations

[0252] FIG. 1E shows a data flow data diagram depicting performance of storage operations by an embodiment of an information management system 100, according to an exemplary data storage policy 148A. The information management system 100 includes a storage manger 140, a client computing device 102 having a file system data agent 142A and an email data agent 142B residing thereon, a primary storage device 104, two media agents 144A, 144B, and two secondary storage devices 108A, 108B: a disk library 108A and a tape library 108B. As shown, the primary storage device 104 includes primary data 112A, 1128 associated with a file system sub-client and an email sub-client, respectively.

[0253] As indicated by the dashed box, the second media agent 144B and the tape library 1088 are “off-site”, and may therefore be remotely located from the other components in the information management system 100 (e.g., in a different city, office building, etc.). In this manner, information stored on the tape library 108B may provide protection in the event of a disaster or other failure.

[0254] The file system sub-client and its associated primary data 112A in certain embodiments generally comprise information generated by the file system and/or operating system of the client computing device 102, and can include, for example, file system data (e.g., regular files, file tables, mount points, etc.), operating system data (e.g., registries, event logs, etc.), and the like. The e-mail sub-client, on the other hand, and its associated primary data 112B, include data generated by an e-mail client application operating on the client computing device 102, and can include mailbox information, folder information, emails, attachments, associated database information, and the like. As described above, the sub-clients can be logical containers, and the data included in the corresponding primary data 112A, 1128 may or may not be stored contiguously.

[0255] The exemplary storage policy 148A includes a backup copy rule set 160, a disaster recovery copy rule set 162, and a compliance copy rule set 164. The backup copy rule set 160 specifies that it is associated with a file system sub-client 166 and an email sub-client 168. Each of these sub-clients 166, 168 are associated with the particular client computing device 102. The backup copy rule set 160 further specifies that the backup operation will be written to the disk library 108A, and designates a particular media agent 144A to convey the data to the disk library 108A. Finally, the backup copy rule set 160 specifies that backup copies created according to the rule set 160 are scheduled to be generated on an hourly basis and to be retained for 30 days. In some other embodiments, scheduling information is not included in the storage policy 148A, and is instead specified by a separate scheduling policy.

[0256] The disaster recovery copy rule set 162 is associated with the same two sub-clients 166, 168. However, the disaster recovery copy rule set 162 is associated with the tape library 108B, unlike the backup copy rule set 160. Moreover, the disaster recovery copy rule set 162 specifies that a different media agent 144B than the media agent 144A associated with the backup copy rule set 160 will be used to convey the data to the tape library 108B. As indicated, disaster recovery copies created according to the rule set 162 will be retained for 60 days, and will be generated on a daily basis. Disaster recovery copies generated according to the disaster recovery copy rule set 162 can provide protection in the event of a disaster or other data-loss event that would affect the backup copy 116A maintained on the disk library 108A.

[0257] The compliance copy rule set 164 is only associated with the email sub-client 166, and not the file system sub-client 168. Compliance copies generated according to the compliance copy rule set 164 will therefore not include primary data 112A from the file system sub-client 166. For instance, the organization may be under an obligation to store maintain copies of email data for a particular period of time (e.g., 10 years) to comply with state or federal regulations, while similar regulations do not apply to the file system data. The compliance copy rule set 164 is associated with the same tape library 108B and media agent 144B as the disaster recovery copy rule set 162, although a different storage device or media agent could be used in other embodiments. Finally, the compliance copy rule set 164 specifies that copies generated under the compliance copy rule set 164 will be retained for 10 years, and will be generated on a quarterly basis.

[0258] At step 1, the storage manager 140 initiates a backup operation according to the backup copy rule set 160. For instance, a scheduling service running on the storage manager 140 accesses scheduling information from the backup copy rule set 160 or a separate scheduling policy associated with the client computing device 102, and initiates a backup copy operation on an hourly basis. Thus, at the scheduled time slot the storage manager 140 sends instructions to the client computing device 102 to begin the backup operation.

[0259] At step 2, the file system data agent 142A and the email data agent 142B residing on the client computing device 102 respond to the instructions received from the storage manager 140 by accessing and processing the primary data 112A, 112B involved in the copy operation from the primary storage device 104. Because the operation is a backup copy operation, the data agent(s) 142A, 142B may format the data into a backup format or otherwise process the data.

[0260] At step 3, the client computing device 102 communicates the retrieved, processed data to the first media agent 144A, as directed by the storage manager 140, according to the backup copy rule set 160. In some other embodiments, the information management system 100 may implement a load-balancing, availability-based, or other appropriate algorithm to select from the available set of media agents 144A, 144B. Regardless of the manner the media agent 144A is selected, the storage manager 140 may further keep a record in the storage manager database 140 of the association between the selected media agent 144A and the client computing device 102 and/or between the selected media agent 144A and the backup copy 116A.

[0261] The target media agent 144A receives the data from the client computing device 102, and at step 4 conveys the data to the disk library 108A to create the backup copy 116A, again at the direction of the storage manager 140 and according to the backup copy rule set 160. The secondary storage device 108A can be selected in other ways. For instance, the media agent 144A may have a dedicated association with a particular secondary storage device(s), or the storage manager 140 or media agent 144A may select from a plurality of secondary storage devices, e.g., according to availability, using one of the techniques described in U.S. Pat. No. 7,246,207, which is incorporated by reference herein.

[0262] The media agent 144A can also update its index 153 to include data and/or metadata related to the backup copy 116A, such as information indicating where the backup copy 116A resides on the disk library 108A, data and metadata for cache retrieval, etc. After the 30 day retention period expires, the storage manager 140 instructs the media agent 144A to delete the backup copy 116A from the disk library 108A.

[0263] At step 5, the storage manager 140 initiates the creation of a disaster recovery copy 116B according to the disaster recovery copy rule set 162. For instance, at step 6, based on instructions received from the storage manager 140 at step 5, the specified media agent 144B retrieves the most recent backup copy 116A from the disk library 108A.

[0264] At step 7, again at the direction of the storage manager 140 and as specified in the disaster recovery copy rule set 162, the media agent 144B uses the retrieved data to create a disaster recovery copy 116B on the tape library 108B. In some cases, the disaster recovery copy 116B is a direct, mirror copy of the backup copy 116A, and remains in the backup format. In other embodiments, the disaster recovery copy 116C may be generated in some other manner, such as by using the primary data 112A, 1128 from the storage device 104 as source data. The disaster recovery copy operation is initiated once a day and the disaster recovery copies 116A are deleted after 60 days.

[0265] At step 8, the storage manager 140 initiates the creation of a compliance copy 116C, according to the compliance copy rule set 164. For instance, the storage manager 140 instructs the media agent 144B to create the compliance copy 116C on the tape library 108B at step 9, as specified in the compliance copy rule set 164. In the example, the compliance copy 116C is generated using the disaster recovery copy 116B. In other embodiments, the compliance copy 116C is instead generated using either the primary data 112B corresponding to the email sub-client or using the backup copy 116A from the disk library 108A as source data. As specified, compliance copies 116C are created quarterly, and are deleted after ten years.

[0266] While not shown in FIG. 1E, at some later point in time, a restore operation can be initiated involving one or more of the secondary copies 116A, 116B, 116C. As one example, a user may manually initiate a restore of the backup copy 116A by interacting with the user interface 158 of the storage manager 140. The storage manager 140 then accesses data in its index 150 (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 116A.

[0267] In other cases, a media agent may be selected for use in the restore operation based on a load balancing algorithm, an availability based algorithm, or other criteria. The selected media agent 144A retrieves the data from the disk library 108A. For instance, the media agent 144A may access its index 153 to identify a location of the backup copy 116A on the disk library 108A, or may access location information residing on the disk 108A itself.

[0268] When the backup copy 116A was recently created or accessed, the media agent 144A accesses a cached version of the backup copy 116A residing in the media agent index 153, without having to access the disk library 108A for some or all of the data. Once it has retrieved the backup copy 116A, the media agent 144A communicates the data to the source client computing device 102. Upon receipt, the file system data agent 142A and the email data agent 142B may unpackage (e.g., restore from a backup format to the native application format) the data in the backup copy 116A and restore the unpackaged data to the primary storage device 104.

Exemplary Secondary Copy Formatting

[0269] The formatting and structure of secondary copies 116 can vary, depending on the embodiment. In some cases, secondary copies 116 are formatted as a series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4 GB, or 8 GB chunks). This can facilitate efficient communication and writing to secondary storage devices 108, e.g., according to resource availability. For example, a single secondary copy 116 may be written on a chunk-by-chunk basis to a single secondary storage device 108 or across multiple secondary storage devices 108. In some cases, users can select different chunk sizes, e.g., to improve throughput to tape storage devices.

[0270] Generally, each chunk can include a header and a payload. The payload can include files (or other data units) or subsets thereof included in the chunk, whereas the chunk header generally includes metadata relating to the chunk, some or all of which may be derived from the payload. For example, during a secondary copy operation, the media agent 144, storage manager 140, or other component may divide the associated files into chunks and generate headers for each chunk by processing the constituent files.

[0271] The headers can include a variety of information such as file identifier(s), volume(s), offset(s), or other information associated with the payload data items, a chunk sequence number, etc. Importantly, in addition to being stored with the secondary copy 116 on the secondary storage device 108, the chunk headers can also be stored to the index 153 of the associated media agent(s) 144 and/or the storage manager index 150. This is useful in some cases for providing faster processing of secondary copies 116 during restores or other operations. In some cases, once a chunk is successfully transferred to a secondary storage device 108, the secondary storage device 108 returns an indication of receipt, e.g., to the media agent 144 and/or storage manager 140, which may update their respective indexes 150, 153 accordingly.

[0272] During restore, chunks may be processed (e.g., by the media agent 144) according to the information in the chunk header to reassemble the files. Additional information relating to chunks can be found in U.S. Pat. No. 8,156,086, which is incorporated by reference herein.

System Overview

[0273] The systems and methods described with respect to FIGS. 1A-1E can be used for archiving and restoring virtual machines and their associated data. In some embodiments, a virtual machine archiving module is a software module that forms a part of or resides on the storage manager 140 or, alternatively, the media agents 144. The virtual machine archiving module can additionally be a software module executing on one or more of the client computers 102. In some embodiments, the virtual machine archiving module may be implemented as a part of the data agent 142. Virtual machine archiving and seamless virtual machine recall will be discussed in more detail with respect to FIGS. 2-5.

An Exemplary Data Storage System for Implementing Virtual Machine Archiving and Virtual Machine Seamless Restore

[0274] FIG. 2 is a data flow diagram illustrative of the interaction between the various components of an exemplary storage system 200 configured to archive virtual machines according to certain embodiments. As illustrated, the exemplary data storage system 200 includes a storage manager 210, one or more clients 220, one or more information stores 230, a virtual machine (VM) archiving module 250, one or more media agents 270, and one or more secondary storage devices 280. A client 220 may include a hypervisor 227 and one or more virtual machines (VMs) 225. The system 200 and corresponding components of FIG. 2 may be similar to or the same as the system 100 and similarly named components of FIG. 1D. Moreover, depending on the embodiment, the system 200 of FIG. 2 may additionally include any of the other components shown in FIG. 1D that are not specifically shown in FIG. 2 (e.g., one or more data agents, one or more applications, etc.). The system 200 may include one or more of each component. All components of the system 200 can be in direct communication with each other or communicate indirectly via the client 220, the storage manager 210, the media agent 270, or the like. In certain embodiments, some of the components in FIG. 2 shown as separate components can reside on a single computing device, or vice versa. For example, the virtual machine archiving module 250 can be on the storage manager 210 or on a separate computing device.

[0275] The term virtualization in the computing arts can refer to the creation of a virtual instance of an entity (e.g., a hardware platform, operating system, storage device or network resource, etc.) that behaves like a physical instance. For instance, a virtual machine can be a software representation of a physical machine. Enterprises may use virtualization for a variety of purposes, such as to reduce the number of physical servers or other computers by instantiating multiple virtual machines on a single physical host computer. In this manner, virtualization can be used to centralize administrative tasks while improving scalability and workloads, and can be an important tool for maximizing hardware utilization.

[0276] Using virtualization techniques, many (e.g., hundreds or thousands) of virtual machines can be instantiated on a single host device. The host device can contain significant amounts of memory and computing power in order to execute the virtual machines, which can be referred to as “clients” or “guests.” Although each virtual client can be logically viewed as a stand-alone device, in actuality the virtual client machines share underlying hardware with the other virtual machines residing on the host.

[0277] With further reference to FIG. 2, the interaction between the various components of the exemplary data storage system will now be described in greater detail with respect to data flow steps indicated by the numbered arrows.

[0278] At data flow step 1, the virtual machine archiving module 250 determines whether a virtual machine 225 is low usage. The VM archiving module 250 may be a part of the storage manager 210 or may be on a separate computing device. One or more virtual machines 225 may run on one or more client computers 227. For instance, multiple virtual machines 225 can execute on one client computer 220, as shown in FIG. 2. In some embodiments, one virtual machine 225 can execute on multiple client computers 220. Each client 220 may include a hypervisor 227 that controls and manages the one or more virtual machines 225 on the client 220. The information store 230 associated with the client 220 may store information and/or data related to the virtual machine(s) 225 on the client 220. In some embodiments, a virtual center manages and collects information from the hypervisors 227 on different clients 220.

[0279] The VM archiving module 250 may monitor the usage of the virtual machines 225 executing on one or more client computers 220. The VM archiving module 250 can obtain the usage data or information from the hypervisor 227 on each client 220. In some embodiments, the VM archiving module 250 communicates with the virtual center that manages and collects information from the hypervisors 227 in order to obtain the usage information. The usage information may include storage usage (e.g., disk usage), CPU usage, memory usage, network usage, etc. The usage information may also include various events. Such events may include a set of events defined by a virtual machine software or application.

[0280] In some embodiments, monitoring the usage of the virtual machines 225 may be implemented as storage policies. For example, one or more storage policies can be defined for determining what constitutes low usage for VMs 225. The same storage policy(ies) may apply to all of the VMs 225, or to a subset of the VMs 225. For instance, VMs 225 may be associated with particular categories, and the same storage policy(ies) may be applied to a subset of VMs 225 associated with the same category. Such categories may provide information about usage pattern, characteristics, and/or level of VMs 225 belonging to the categories. A storage policy may also be defined for an individual VM 225. A separate storage policy for each VM 225 can specify what constitutes low usage for that particular VM 225. For example, the storage policy can define a threshold value at which the VM 225 should be archived. The storage policy may be defined based on a variety of factors, such as category of VM 225, period of peak usage, workloads handled by the VM 225, etc.

[0281] The VM archiving module 250 may monitor the usage of the virtual machines 225 according to a schedule. For example, the VM archiving module 250 may repeatedly check the usage of the VMs 225 after the passage of a pre-determined amount of time, such as on a regular basis (e.g., after a particular time interval, such as a certain number of hours or days), or on an intermittent basis. The monitoring may also be event-based and may be triggered by certain events. For example, usage information may be obtained as a part of a backup operation, and the VM archiving module 250 may collect usage data as a scheduled (e.g., daily, weekly, etc.) backup is occurring or after a scheduled backup has completed. As explained above, the monitoring of VMs 225 may be implemented as storage policies. Such policies may be run according to a schedule, on an event basis, etc. as explained above. The storage manager 210 may manage and store storage policies.

[0282] The VM archiving module 250 can determine whether a particular VM 225 is low usage based on the obtained usage information. The VM archiving module 250 can determine the usage of the VM 225 based on a variety of factors, including, but not limited to: storage usage (e.g., disk usage), CPU usage, memory usage, network usage, events, etc. For example, the usage may be determined based on a percentage of usage for the resources allocated to a particular VM 225. Even if a VM 225 is not being used, the VM 225 may have some level of activity (e.g., Windows services updating, virus scan running, etc.). Therefore, the VM archiving module 250 may determine whether the activity level of a VM 225 is above or at a certain level, in order to decide whether to archive the VM 225. In some embodiments, the VM archiving module 250 determines whether the usage of a VM 225 is equal to or above a threshold value. If the usage of the VM 225 is equal to or above the threshold value, the VM archiving module 250 determines that the VM 225 is not low usage. On the other hand, if the usage of the VM 225 is below the threshold value, the VM archiving module 250 determines that the VM 225 is low usage. A VM 225 that is determined to have low utilization may be archived, as explained with respect to data flow step 2. In some embodiments, instead of archiving the low usage VM 225, the resources allocated for the VM 225 may be reduced, as explained with respect to data flow step 2a.

[0283] At data flow step 2, the virtual machine archiving module 250 archives the virtual machines 225 that are determined to have low usage. In archiving, the source of the data may be pruned from primary storage after the data is copied to secondary storage. If the VM archiving module 250 is on a different computing device from the storage manager 210, the VM archiving module 250 may send a request to the storage manager 250 to archive the VM 225. The storage manager 210 can instruct one or more media agents 270 to archive the VM 225. The data associated with the VM 225 (e.g., residing in the information store 230 for the corresponding client 220) may be archived along with the VM 225. The media agents 270 can copy the VM 225 and the associated data to one or more secondary storage devices 280.

[0284] The virtual machines 225 may be copied to secondary storage, for example, during a scheduled backup. If a VM 225 has not been in use since the last backup, and a previous backup copy of the VM 225 and its data exists in the storage devices 280, the VM archiving module 250 may decide not to copy the VM 225 and the data again. After the VM and its associated data are copied to the storage devices 280, the VM archiving module 250 can delete or prune the VM 225 and the associated data from the client 220 and the information store 230. For instance, the VM archiving module 250 can delete a VM 225 through a command provided by the virtual machine application. Since the source data is pruned in archiving, the VM archiving module 250 can make sure that a backup copy of the VM 225 exists in secondary storage before removing the VM 225 and its data from primary storage. By deleting the VM 225 itself and the VM data, the system 200 can free up unutilized and/or underutilized resources in the primary storage and make them available for other uses.

[0285] At data flow step 2a, the virtual machine archiving module 250 reduces the resource allocation for virtual machines 225 that are determined to have low usage. As explained above, in some embodiments, the VM archiving module 250 reduces the resource allocation for the low usage VM 225, instead of archiving the VM 225. Each VM 225 may be allocated a certain amount of one or more of the following resources: storage space (e.g., disk space), CPU, memory, network resources, etc. The network resources may refer to network bandwidth, throughput, etc. The VM archiving module 250 may reduce the amount of resources currently allocated to the VM 225. For example, the VM archiving module 250 can reduce the CPU time for the VM 225 and/or reduce the storage space allocated to the VM 225. The VM archiving module 250 may also reduce the amount of resources by moving or migrating the VM 225 from high cost storage to low cost storage. For instance, the VM 225 and/or its associated data are stored on solid state drive (SSD), and if the VM 225 has low utilization, the VM 225 and/or its associated data are migrated to hard disk drive. The VM archiving module 250 can also move the VM 225 from fast storage to slower storage. In this manner, the cost of storage for virtual machines 225 can be decreased by reducing the amount of resources allocated to low usage VMs 225 and/or by migrating the low usage VMs 225 from high cost storage to low cost storage (or fast storage to slow storage).

[0286] The VM archiving module 250 may decide to reduce the amount of resources allocated to a low usage VM 225, instead of archiving the VM 225, until a certain level of low usage is reached. For example, the VM archiving module 250 can determine a threshold value for archiving VMs 225, and if the usage of a VM 225 does not fall below the threshold value, the VM archiving module 250 reduces the amount of resources allocated to the VMs 225. The VM archiving module 250 can reduce the resource allocation for the VMs 225 in various ways. For example, the VM archiving module 250 may determine the amount of resources to reduce based on the level of usage. For example, if storage usage is greater than 25 percent and less than or equal to 30 percent, the VM archiving module 250 reduces the storage space by half. If storage usage is greater than 20 percent and less than or equal to 25 percent, the VM archiving module 250 reduces the storage space by 75 percent. The amount of resources may also be reduced in increments based on the level of usage. For example, if CPU usage is greater than 15 percent and less than or equal to 20 percent, the VM archiving module 250 reduces the CPU time by 30%. If CPU usage is greater than 10 percent and less than or equal to 15 percent, the VMA 250 reduces the CPU time by another 30%. The amount of resources to be reduced can include any combination of different types of resources that can be allocated to a VM 225.

[0287] At data flow step 3, the virtual machine archiving module 250 creates a virtual machine placeholder for each archived virtual machine 225. A VM placeholder may be a minimal version of the VM 225 that acts as if it is the VM 225. The VM placeholder may have a reduced set or amount of resources compared to the VM 225. For example, the VM placeholder may have a minimum amount of CPU and memory allocated for it to run. The VM placeholder may replace the VM 225 and appear to be the VM 225. The VM placeholder can interact with one or more operating systems on the one or more client computers 220 like it is the VM 225. To the operating systems, the archived VM 225 may appear to be active. For instance, the operating systems can display the VM 225 in the list of available VMs 225, and when a user selects the VM 225, the VM placeholder can act like it is the VM 225. When a user accesses the VM placeholder, at least a portion of the VM 225 and its associated data may be restored to reactivate the VM 225. The VM placeholder may include information about restoring the archived VM 225. For example, the information may include a reference to the archived VM 225, such as the location of the archived VM 225 and its associated data in secondary storage.

[0288] In this way, a VM 225 may be archived, but still appear to be active and selectable by the user through the use of VM placeholders. Infrequently used VMs 225 can be moved to low cost storage without appearing to be unavailable and can be restored in a seamless manner. A VM placeholder can be allocated a very limited amount of resources (e.g., memory and disk space). Accordingly, the system 200 can reduce the amount of idle resources that are allocated to VMs 225, but rarely utilized.

[0289] FIG. 3 is a data flow diagram illustrative of the interaction between the various components of an exemplary storage system 300 configured to restore archived virtual machines according to certain embodiments. As illustrated, the exemplary data storage system 300 includes a storage manager 310, a client 320, an information store 330, a virtual machine (VM) archiving module 350, one or more media agents 370, and one or more secondary storage devices 380. A client 320 may include a hypervisor 327 and one or more virtual machines (VMs) 325. The system 300 and corresponding components of FIG. 3 may be similar to or the same as the system 100, 200 and similarly named components of FIGS. 1D and 2. Moreover, depending on the embodiment, the system 300 of FIG. 3 may additionally include any of the other components shown in FIGS. 1D and 2 that are not specifically shown in FIG. 3 (e.g., one or more data agents, one or more applications, etc.). The system 300 may include one or more of each component. All components of the system 300 can be in direct communication with each other or communicate indirectly via the client 320, the storage manager 310, the media agent 370, or the like. In certain embodiments, some of the components in FIG. 3 shown as separate components can reside on a single computing device, or vice versa. For example, the virtual machine archiving module 350 can be on the storage manager 310 or on a separate computing device.

[0290] With further reference to FIG. 3, the interaction between the various components of the exemplary data storage system will now be described in greater detail with respect to data flow steps indicated by the numbered arrows.

[0291] At data flow step 1, a user accesses an archived virtual machine 325 or a virtual machine placeholder, e.g., at a client computer 320. The VM 325 that has been archived may appear to be active. For instance, the user may see the VM 325 in a list of available VMs 325 and select the VM. When the user selects the VM, the user may be selecting the VM placeholder.

[0292] As explained above, a VM placeholder may be a minimal version of the VM 325 that replaces the archived VM 325. The VM placeholder may have a reduced set or amount of resources compared to the VM 325. For example, the VM placeholder may have a minimum amount of CPU and memory allocated for it to run. The VM placeholder may include information about restoring the archived VM 325. Such information may include a reference to the archived VM 325 (e.g., the location of the archived VM 325 and its associated data in secondary storage).

[0293] In some embodiments, the VM placeholder may act like it is the VM 325. The VM placeholder may interact with operating systems and/or applications on the one or more client computers 320 as if it is the actual VM 325. For example, the VM placeholder can interact with a virtualization software (e.g., VMware, etc.) in a similar manner as the VM 325. The VM placeholder may respond to commands from the virtualization software and communicate with the virtualization software (e.g., for notification, reporting, etc.). In one example, the virtualization software may request a VM 325 to power on. If the VM 325 has been archived, the VM placeholder can power on, report to the virtualization software that the VM 325 is powered on, and retrieve the archived VM 325 from secondary storage.

[0294] If a user attempts to access the VM 325 or the VM placeholder, at least a portion of the VM 325 and/or the associated data may be restored from secondary storage to primary storage. From the user interface perspective, there may be no differences between interacting with a VM 325 in primary storage and interacting with a VM placeholder for an archived VM 325.

[0295] At data flow step 2, the client 320 sends a request to restore the archived virtual machine 325 that has been accessed by the user to the VM archiving module 350. If the VM archiving module 350 is on a different computing device from the storage manager 310, the VM archiving module 350 may send the restore request to the storage manager 310. As explained above, the VM placeholder can include information for restoring the VM 325, such as a reference to the archived VM 325. In one embodiment, the reference is the address of the secondary storage location where the archived VM 325 and its associated data are stored. The VM archiving module 350 can restore the VM 325 using the reference. In this manner, the VM archiving module 350 may be able to quickly access and restore the archived VM 325 from secondary storage. In some embodiments, the storage manager 310 can determine which storage devices 380 have the backup copy of the VM 350 and its associated data.

[0296] At data flow step 3, the storage manager 310 instructs one or more media agents 370 to restore the archived virtual machine 325. The storage manager 310 can determine which media agent(s) 370 to instruct based on the storage devices 380 that store the backup copy of the VM 325 and the VM data. The entire backup copy of the VM 325 and the VM data may be restored to the primary storage (e.g., to the client 320 and/or the information store 330). In some embodiments, only a portion of the VM 325 and the VM data are restored.

[0297] The VM archiving module 350 may allocate resources for the restored VM 325. For example, the VM archiving module 350 may allocate a certain amount of one or more the following resources: storage space (e.g., disk space), CPU, memory, network resources, etc. The network resources may refer to network bandwidth, throughput, etc. The VM placeholder may already have a minimum set of resources allocated to it. In such embodiments, the VM archiving module 350 may assign the resources allocated to the VM placeholder to the restored VM 325. When assigning the VM placeholder resources to the restored VM 325, the VM archiving module 350 may also increase the amount of resources currently allocated to the VM placeholder and/or allocate new types resources, as appropriate.

[0298] After the archived VM 325 is restored, the VM placeholder can be deleted. In some cases, the system 300 may not delete the VM placeholder. For instance, if only a portion of the archived VM 325 and its data is restored, the system 300 may want to keep the VM placeholder in order to restore the remaining data. In such cases, the VM placeholder may continue to interact with the operating systems and/or the applications, at least partially, on behalf of the VM 325.

[0299] In addition, the system 300 may not remove the VM placeholder so that it does not have to create the placeholder again the next time the VM 325 is archived. Archived VMs 325 are generally those with low usage, and it may be likely that such VMs 325 are archived again at some time in the future after being restored. The VM placeholder can remain, and the system 300 may update any information as appropriate the next time the VM 325 is archived (e.g., update the information for restoring the VM 325).

[0300] Because a VM 325 can remain available to the user when it is archived and while it is being restored (e.g., through the VM placeholder), the restore of the VM 325 may appear to be “seamless” to the user. For example, the user may not be aware that the VM selected by the user is in secondary storage and is being restored from secondary storage. Such user experience may be possible because the VM 325 can be restored quickly. “Seamless virtual machine recall” may refer to the continuous availability of archived VMs 325 while they are in secondary storage and while they are being restored.

[0301] FIG. 4 is a flow diagram illustrative of one embodiment of a routine 400 implemented by a data storage system for archiving virtual machines. The routine 400 is described with respect to the system 200 of FIG. 2. However, one or more of the steps of routine 400 may be implemented by other data storage systems, such as those described in greater detail above with reference to FIG. 1D. The routine 400 can be implemented by any one, or a combination of, a client, a storage manager, a data agent, a virtual machine archiving module, a media agent, and the like. Moreover, further details regarding certain aspects of at least some of steps of the routine 400 are described in greater detail above with reference to FIG. 2. Although described in relation to backup operations for the purposes of illustration, the process of FIG. 4 can be compatible with other types of storage operations, such as, for example, migration, snapshots, replication operations, and the like.

[0302] At block 401, the virtual machine archiving module 250 receives or determines virtual machine utilization information. For example, the VM archiving module 250 may monitor the usage of VMs 225 in the system 200. The VM archiving module 250 may monitor the VMs 225, for example, according to a schedule, based on certain events, at a system administrator's request, etc. The VM archiving module 250 may also obtain the usage information from a virtual center that collects information relating to various VMs 225 in the system 200.

[0303] At block 402, if the utilization of a virtual machine 225 is low, the VM archiving module 250 sends instructions to archive the virtual machine 225 at block 403. The determination of utilization level may be based on a number of factors (e.g., usage level of various types of resources associated with the VM 225). If the VM archiving module 250 is not on the storage manager 210, the VM archiving module 250 may forward the instructions to the storage manager 210. The storage manager 210 can instruct the media agents 270 to archive the VM 225. After the backup of the VM 225 and/or the associated data is complete, the VM 225 and the data are deleted from primary storage.

[0304] At block 404, the VM archiving module 250 creates a VM placeholder for the archived VM 225. The VM placeholder may appear to be the VM 225 and can interact with the operating systems on the clients 220 in a way similar to the VM 225. In this manner, the VM 225 can appear to be available and selectable by the user after it has been archived.

[0305] The routine 400 can include fewer, more, or different blocks than those illustrated in FIG. 4 without departing from the spirit and scope of the description. Moreover, it will be appreciated by those skilled in the art and others that some or all of the functions described in this disclosure may be embodied in software executed by one or more processors of the disclosed components and mobile communication devices. The software may be persistently stored in any type of non-volatile storage.

[0306] FIG. 5 is a flow diagram illustrative of one embodiment of a routine 500 implemented by a data storage system for restoring archived virtual machines. The routine 500 is described with respect to the system 300 of FIG. 3. However, one or more of the steps of routine 500 may be implemented by other data storage systems, such as those described in greater detail above with reference to FIGS. 1D and 2. The routine 500 can be implemented by any one, or a combination of, a client, a storage manager, a data agent, a virtual machine archiving module, a media agent, and the like. Moreover, further details regarding certain aspects of at least some of steps of the routine 500 are described in greater detail above with reference to FIG. 3. Although described in relation to backup operations for the purposes of illustration, the process of FIG. 5 can be compatible with other types of storage operations, such as, for example, migration, snapshots, replication operations, and the like.

[0307] At block 501, the virtual machine archiving module 350 receives a request to restore a virtual machine 325. Such request may be received when a user accesses an archived VM 325 or a VM placeholder, e.g., at a client 320. The request may be for the entire VM 325 and its associated data, or may be for only a portion of the VM 325 and the VM data.

[0308] At block 502, the VM archiving module 350 sends instructions to restore the virtual machine 325. If the VM archiving module 350 is not on the storage manager 310, the VM archiving module 350 may forward the instructions to the storage manager 310. The storage manager 310 can instruct one or more media agents 380 to restore the requested VM 325. The media agents 380 can retrieve the backup copy of the VM 325 and the VM data from the corresponding secondary storage devices 380.

[0309] At block 503, the VM archiving module 350 replaces the VM placeholder with the restored VM 325. If all of the VM 350 and the associated data are restored, the VM archiving module 350 may replace the VM placeholder with the restored VM 325. The VM placeholder can then be removed from primary storage.

[0310] At block 504, the client 320 executes the restored VM 325. In general, a VM 325 can appear to be available to a user, regardless of whether the VM 325 is archived or not. However, once the VM 325 is restored to primary storage, the user can have access to the actual VM 325.

[0311] The routine 500 can include fewer, more, or different blocks than those illustrated in FIG. 5 without departing from the spirit and scope of the description. Moreover, it will be appreciated by those skilled in the art and others that some or all of the functions described in this disclosure may be embodied in software executed by one or more processors of the disclosed components and mobile communication devices. The software may be persistently stored in any type of non-volatile storage.

Terminology

[0312] 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.

[0313] Depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out all together (e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.

[0314] Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described herein. Software and other modules may reside on servers, workstations, personal computers, computerized tablets, PDAs, and other devices suitable for the purposes described herein. Software and other modules may be accessible via local memory, via a network, via a browser, or via other means suitable for the purposes described herein. Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes or methods, or any combinations thereof, suitable for the purposes described herein. User interface elements described herein may comprise elements from graphical user interfaces, command line interfaces, and other suitable interfaces.

[0315] Further, the processing of the various components of the illustrated systems can be distributed across multiple machines, networks, and other computing resources. In addition, two or more components of a system can be combined into fewer components. Various components of the illustrated systems can be implemented in one or more virtual machines, rather than in dedicated computer hardware systems. Likewise, the data repositories shown can represent physical and/or logical data storage, including, for example, storage area networks or other distributed storage systems. Moreover, in some embodiments the connections between the components shown represent possible paths of data flow, rather than actual connections between hardware. While some examples of possible connections are shown, any of the subset of the components shown can communicate with any other subset of components in various implementations.

[0316] Embodiments are also described above with reference to flow chart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products. Each block of the flow chart illustrations and/or block diagrams, and combinations of blocks in the flow chart illustrations and/or block diagrams, may be implemented by computer program instructions. Such instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the acts specified in the flow chart and/or block diagram block or blocks.

[0317] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the acts specified in the flow chart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the acts specified in the flow chart and/or block diagram block or blocks.

[0318] While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the disclosure. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the described methods and systems may be made without departing from the spirit of the disclosure. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the disclosure.

Claims

What is claimed is:

1. A method of creating virtual machine placeholders in a data storage system comprising:

receiving data about one or more virtual machines existing on one or more primary storage devices from a virtual machine hypervisor, the one or more primary storage devices comprising computer hardware;

migrating a first virtual machine from the one or more virtual machines to one or more secondary storage devices during one or more backups;

creating on the one or more primary storage devices a virtual machine placeholder for the first virtual machine that has been migrated to the one or more secondary storage devices,

the virtual machine placeholder comprises fewer assigned resources than the first virtual machine,

the virtual machine placeholder is created at least in part during the one or more backups that migrated the first virtual machine from the one or more primary storage devices to one or more secondary storage devices,

the virtual machine placeholder is recognized as the first virtual machine by one or more virtualization applications, and

wherein the virtual machine placeholder comprises a reference to the location of first virtual machine in the one or more secondary storage devices; and

using the reference in the virtual machine placeholder to restore the first virtual machine from the one or more secondary storage devices to the one or more primary storage devices.

2. The method of claim 1 wherein the first virtual machine is selectable by a user using the virtual machine placeholder.

3. The method of claim 1 wherein the virtual machine placeholder interacts with one or more virtualization applications as if the virtual machine placeholder were the first virtual machine.

4. The method of claim 1 wherein the reference identifies a storage location in the one or more secondary storage devices of copy data associated with the first virtual machine.

5. The method of claim 1 further comprising automatically using the reference to restore the first virtual machine in response to a request received by the virtual machine placeholder.

6. The method of claim 1 further comprising automatically using the reference to restore the first virtual machine in order to perform load balancing among multiple virtual machines.

7. The method of claim 1 wherein the reference identifies a storage location in the one or more secondary storage devices of copy data associated with the first virtual machine.

8. The method of claim 1 wherein the virtual machine placeholder is created when usage of the first virtual machine is less than a threshold defined in a storage policy.

9. The method of claim 1 further comprising monitoring usage of the one or more virtual machines occurs during the one or more backups.

10. The method of claim 1 wherein the virtual machine placeholder interacts with an operating system or the one or more virtualization applications as if the first virtual machine had not been deleted.

11. A data storage system that creates virtual machine placeholders comprising:

a storage manager executing on computer hardware comprising one or more computing devices,

the storage manager receives data about of one or more virtual machines existing on one or more primary storage devices from a virtual machine hypervisor, the storage manager comprising computer hardware;

the storage manager directs migration of a first virtual machine from the one or more virtual machines to one or more secondary storage devices during one or more backups;

the storage manager directs creation on the one or more primary storage devices of a virtual machine placeholder for the first virtual machine that has been migrated to the one or more secondary storage devices,

the virtual machine placeholder comprises fewer assigned resources than the first virtual machine,

the virtual machine placeholder is created at least in part during one or more backups that migrated the first virtual machine from the one or more primary storage devices to one or more secondary storage devices,

the virtual machine placeholder is recognized as the first virtual machine by one or more virtualization applications, and

the virtual machine placeholder comprises a reference to the location of the first virtual machine stored in the one or more secondary storage devices; and

the storage manager uses the reference in the virtual machine placeholder to restore the first virtual machine from the one or more secondary storage devices to the one or more primary storage devices.

12. The data storage system of claim 11 wherein the first virtual machine is selectable by a user using the virtual machine placeholder.

13. The data storage system of claim 11 wherein the virtual machine placeholder interacts with an operating system or the one or more virtualization applications as if it were the first virtual machine.

14. The data storage system of claim 11 wherein the reference identifies a storage location in the one or more secondary storage devices of copy data associated with the first virtual machine.

15. The data storage system of claim 14 wherein the first virtual machines is automatically restored in response to a request received by the virtual machine placeholder.

16. The data storage system of claim 11 wherein the storage manager automatically uses the reference to restore the first virtual machine in order to perform load balancing among multiple virtual machines.

17. The data storage system of claim 11 wherein the virtual machine placeholder comprises a reduced amount of resources in comparison to the first virtual machine.

18. The data storage system of claim 11 wherein the virtual machine placeholder is created when the usage of the first virtual machine is less than a threshold defined in a storage policy.

19. The data storage system of claim 11 wherein monitoring the usage of the one or more virtual machines occurs at least in part during the one or more backups.

20. The data storage system of claim 11 wherein the virtual machine placeholder interacts with an operating system or the one or more virtualization applications as if the first virtual machine had not been deleted.

Patent Citations (360)

Patent	Date	Inventor	Cited By
US4417321(A)	1983-11-01	Chang et al.	Applicant
US4641274(A)	1987-02-01	Swank	Applicant
US4654819(A)	1987-03-01	Stiffler et al.	Applicant
US4686620(A)	1987-08-01	Ng	Applicant
US4995035(A)	1991-02-01	Cole et al.	Applicant
US5005122(A)	1991-04-01	Griffin et al.	Applicant
US5093912(A)	1992-03-01	Dong et al.	Applicant
US5133065(A)	1992-07-01	Cheffetz et al.	Applicant
US5193154(A)	1993-03-01	Kitajima et al.	Applicant
US5212772(A)	1993-05-01	Masters	Applicant
US5226157(A)	1993-07-01	Nakano et al.	Applicant
US5239647(A)	1993-08-01	Anglin et al.	Applicant
US5241668(A)	1993-08-01	Eastridge et al.	Applicant
US5241670(A)	1993-08-01	Eastridge et al.	Applicant
US5276860(A)	1994-01-01	Fortier et al.	Applicant
US5276867(A)	1994-01-01	Kenley et al.	Applicant
US5287500(A)	1994-02-01	Stoppani, Jr.	Applicant
US5301286(A)	1994-04-01	Rajani	Applicant
US5321816(A)	1994-06-01	Rogan et al.	Applicant
US5333315(A)	1994-07-01	Saether et al.	Applicant
US5347653(A)	1994-09-01	Flynn et al.	Applicant
US5410700(A)	1995-04-01	Fecteau et al.	Applicant
US5420996(A)	1995-05-01	Aoyagi	Applicant
US5448724(A)	1995-09-01	Hayashi	Applicant
US5454099(A)	1995-09-01	Myers et al.	Applicant
US5491810(A)	1996-02-01	Allen	Applicant
US5495607(A)	1996-02-01	Pisello et al.	Applicant
US5504873(A)	1996-04-01	Martin et al.	Applicant
US5544345(A)	1996-08-01	Carpenter et al.	Applicant
US5544347(A)	1996-08-01	Yanai et al.	Applicant
US5559957(A)	1996-09-01	Balk	Applicant
US5559991(A)	1996-09-01	Kanfi	Applicant
US5619644(A)	1997-04-01	Crockett et al.	Applicant
US5638509(A)	1997-06-01	Dunphy et al.	Applicant
US5642496(A)	1997-06-01	Kanfi	Applicant
US5664204(A)	1997-09-01	Wang	Applicant
US5673381(A)	1997-09-01	Huai et al.	Applicant
US5699361(A)	1997-12-01	Ding et al.	Applicant
US5729743(A)	1998-03-01	Squibb	Applicant
US5751997(A)	1998-05-01	Kullick et al.	Applicant
US5758359(A)	1998-05-01	Saxon	Applicant
US5761677(A)	1998-06-01	Senator et al.	Applicant
US5764972(A)	1998-06-01	Crouse et al.	Applicant
US5778395(A)	1998-07-01	Whiting et al.	Applicant
US5812398(A)	1998-09-01	Nielsen	Applicant
US5813009(A)	1998-09-01	Johnson et al.	Applicant
US5813017(A)	1998-09-01	Morris	Applicant
US5875478(A)	1999-02-01	Blumenau	Applicant
US5887134(A)	1999-03-01	Ebrahim	Applicant
US5901327(A)	1999-05-01	Ofek	Applicant
US5924102(A)	1999-07-01	Perks	Applicant
US5950205(A)	1999-09-01	Aviani, Jr.	Applicant
US5974563(A)	1999-10-01	Beeler, Jr.	Applicant
US6021415(A)	2000-02-01	Cannon et al.	Applicant
US6026414(A)	2000-02-01	Anglin	Applicant
US6052735(A)	2000-04-01	Ulrich et al.	Applicant
US6076148(A)	2000-06-01	Kedem	Applicant
US6094416(A)	2000-07-01	Ying	Applicant
US6131095(A)	2000-10-01	Low et al.	Applicant
US6131190(A)	2000-10-01	Sidwell	Applicant
US6148412(A)	2000-11-01	Cannon et al.	Applicant
US6154787(A)	2000-11-01	Urevig et al.	Applicant
US6161111(A)	2000-12-01	Mutalik et al.	Applicant
US6167402(A)	2000-12-01	Yeager	Applicant
US6212512(B1)	2001-04-01	Barney et al.	Applicant
US6260069(B1)	2001-07-01	Anglin	Applicant
US6269431(B1)	2001-07-01	Dunham	Applicant
US6275953(B1)	2001-08-01	Vahalia et al.	Applicant
US6301592(B1)	2001-10-01	Aoyama et al.	Applicant
US6324581(B1)	2001-11-01	Xu et al.	Applicant
US6328766(B1)	2001-12-01	Long	Applicant
US6330570(B1)	2001-12-01	Crighton	Applicant
US6330642(B1)	2001-12-01	Carteau	Applicant
US6343324(B1)	2002-01-01	Hubis et al.	Applicant
USRE37601(E)	2002-03-01	Eastridge et al.	Applicant
US6356801(B1)	2002-03-01	Goodman et al.	Applicant
US6389432(B1)	2002-05-01	Pothapragada et al.	Applicant
US6418478(B1)	2002-07-01	Ignatius et al.	Applicant
US6421711(B1)	2002-07-01	Blumenau et al.	Applicant
US6487561(B1)	2002-11-01	Ofek et al.	Applicant
US6519679(B2)	2003-02-01	Devireddy et al.	Applicant
US6538669(B1)	2003-03-01	Lagueux, Jr.	Applicant
US6542972(B2)	2003-04-01	Ignatius et al.	Applicant
US6564228(B1)	2003-05-01	O'Connor	Applicant
US6581076(B1)	2003-06-01	Ching et al.	Applicant
US6658436(B2)	2003-12-01	Oshinsky et al.	Applicant
US6658526(B2)	2003-12-01	Nguyen et al.	Applicant
US6721767(B2)	2004-04-01	De Meno et al.	Applicant
US6760723(B2)	2004-07-01	Oshinsky et al.	Applicant
US7003641(B2)	2006-02-01	Prahlad et al.	Applicant
US7035880(B1)	2006-04-01	Crescenti et al.	Applicant
US7076270(B2)	2006-07-01	Jaggers et al.	Applicant
US7107298(B2)	2006-09-01	Prahlad et al.	Applicant
US7130970(B2)	2006-10-01	Devassy et al.	Applicant
US7162496(B2)	2007-01-01	Amarendran et al.	Applicant
US7174433(B2)	2007-02-01	Kottomtharayil et al.	Applicant
US7219162(B2)	2007-05-01	Donker et al.	Applicant
US7246207(B2)	2007-07-01	Kottomtharayil et al.	Applicant
US7315923(B2)	2008-01-01	Retnamma et al.	Applicant
US7324543(B2)	2008-01-01	Wassew et al.	Applicant
US7343356(B2)	2008-03-01	Prahlad et al.	Applicant
US7343453(B2)	2008-03-01	Prahlad et al.	Applicant
US7346751(B2)	2008-03-01	Prahlad et al.	Applicant
US7386744(B2)	2008-06-01	Barr et al.	Applicant
US7389311(B1)	2008-06-01	Crescenti et al.	Applicant
US7395282(B1)	2008-07-01	Crescenti	Applicant
US7440982(B2)	2008-10-01	Lu et al.	Applicant
US7448079(B2)	2008-11-01	Tremain	Applicant
US7454569(B2)	2008-11-01	Kavuri et al.	Applicant
US7475282(B2)	2009-01-01	Tormasov et al.	Applicant
US7490207(B2)	2009-02-01	Amarendran et al.	Applicant
US7500053(B1)	2009-03-01	Kavuri et al.	Applicant
US7502820(B2)	2009-03-01	Manders et al.	Applicant
US7529782(B2)	2009-05-01	Prahlad et al.	Applicant
US7536291(B1)	2009-05-01	Vijayan Retnamma et al.	Applicant
US7543125(B2)	2009-06-01	Gokhale	Applicant
US7546324(B2)	2009-06-01	Prahlad et al.	Applicant
US7603386(B2)	2009-10-01	Amarendran et al.	Applicant
US7606844(B2)	2009-10-01	Kottomtharayil	Applicant
US7613752(B2)	2009-11-01	Prahlad et al.	Applicant
US7617253(B2)	2009-11-01	Prahlad et al.	Applicant
US7617262(B2)	2009-11-01	Prahlad et al.	Applicant
US7620710(B2)	2009-11-01	Kottomtharayil et al.	Applicant
US7631351(B2)	2009-12-01	Erofeev	Applicant
US7636743(B2)	2009-12-01	Erofeev	Applicant
US7640406(B1)	2009-12-01	Hagerstrom et al.	Applicant
US7651593(B2)	2010-01-01	Prahlad et al.	Applicant
US7657550(B2)	2010-02-01	Prahlad et al.	Applicant
US7660807(B2)	2010-02-01	Prahlad et al.	Applicant
US7661028(B2)	2010-02-01	Erofeev	Applicant
US7668884(B2)	2010-02-01	Prahlad et al.	Applicant
US7685177(B1)	2010-03-01	Hagerstrom et al.	Applicant
US7694070(B2)	2010-04-01	Mogi et al.	Applicant
US7721138(B1)	2010-05-01	Lyadvinsky et al.	Applicant
US7730035(B2)	2010-06-01	Berger et al.	Applicant
US7747579(B2)	2010-06-01	Prahlad et al.	Applicant
US7756835(B2)	2010-07-01	Pugh	Applicant
US7756964(B2)	2010-07-01	Madison, Jr. et al.	Applicant
US7765167(B2)	2010-07-01	Prahlad et al.	Applicant
US7778984(B2)	2010-08-01	Zhang et al.	Applicant
US7792789(B2)	2010-09-01	Prahlad et al.	Applicant
US7801864(B2)	2010-09-01	Prahlad et al.	Applicant
US7809914(B2)	2010-10-01	Kottomtharayil et al.	Applicant
US7822967(B2)	2010-10-01	Fung	Applicant
US7840537(B2)	2010-11-01	Gokhale	Applicant
US7882077(B2)	2011-02-01	Gokhale et al.	Applicant
US7899788(B2)	2011-03-01	Chandhok et al.	Applicant
US7937421(B2)	2011-05-01	Mikesell et al.	Applicant
US8001277(B2)	2011-08-01	Mega et al.	Applicant
US8037028(B2)	2011-10-01	Prahlad et al.	Applicant
US8037032(B2)	2011-10-01	Pershin et al.	Applicant
US8046550(B2)	2011-10-01	Feathergill	Applicant
US8060476(B1)	2011-11-01	Afonso et al.	Applicant
US8069271(B2)	2011-11-01	Brunet et al.	Applicant
US8117492(B1)	2012-02-01	Searls et al.	Applicant
US8135930(B1)	2012-03-01	Mattox et al.	Applicant
US8140786(B2)	2012-03-01	Bunte	Applicant
US8170995(B2)	2012-05-01	Prahlad et al.	Applicant
US8185893(B2)	2012-05-01	Hyser et al.	Applicant
US8200637(B1)	2012-06-01	Stringham	Applicant
US8219524(B2)	2012-07-01	Gokhale	Applicant
US8219769(B1)	2012-07-01	Wilk	Applicant
US8229954(B2)	2012-07-01	Kottomtharayil et al.	Applicant
US8285681(B2)	2012-10-01	Prahlad et al.	Applicant
US8307177(B2)	2012-11-01	Prahlad et al.	Applicant
US8307187(B2)	2012-11-01	Chawla et al.	Applicant
US8315992(B1)	2012-11-01	Gipp et al.	Applicant
US8364652(B2)	2013-01-01	Vijayan et al.	Applicant
US8370542(B2)	2013-02-01	Lu et al.	Applicant
US8396838(B2)	2013-03-01	Brockway	Applicant
US8407190(B2)	2013-03-01	Prahlad	Applicant
US8433679(B2)	2013-04-01	Crescenti	Applicant
US8434131(B2)	2013-04-01	Varadharajan	Applicant
US8453145(B1)	2013-05-01	Naik	Applicant
US8473594(B2)	2013-06-01	Astete et al.	Applicant
US8489676(B1)	2013-07-01	Chaplin et al.	Applicant
US8560788(B1)	2013-10-01	Sreedharan et al.	Applicant
US8578120(B2)	2013-11-01	Attarde et al.	Applicant
US8620870(B2)	2013-12-01	Dwarampudi et al.	Applicant
US8667171(B2)	2014-03-01	Guo et al.	Applicant
US8799431(B2)	2014-08-01	Pabari	Applicant
US8831202(B1)	2014-09-01	Abidogun et al.	Applicant
US8850146(B1)	2014-09-01	Majumdar	Applicant
US8904081(B1)	2014-12-01	Kulkarni	Applicant
US8930543(B2)	2015-01-01	Ashok et al.	Applicant
US8938481(B2)	2015-01-01	Kumarasamy et al.	Applicant
US9026498(B2)	2015-05-01	Kumarasamy	Applicant
US9124633(B1)	2015-09-01	Eizadi et al.	Applicant
US9223597(B2)	2015-12-01	Deshpande et al.	Applicant
US9286086(B2)	2016-03-01	Deshpande et al.	Applicant
US9286110(B2)	2016-03-01	Mitkar et al.	Applicant
US9311121(B2)	2016-04-01	Deshpande et al.	Applicant
US9397944(B1)	2016-07-01	Hobbs et al.	Applicant
US9417968(B2)	2016-08-01	Dornemann et al.	Applicant
US9436555(B2)	2016-09-01	Dornemann et al.	Applicant
US9451023(B2)	2016-09-01	Sancheti	Applicant
US9461881(B2)	2016-10-01	Kumarasamy	Applicant
US9489244(B2)	2016-11-01	Mitkar et al.	Applicant
US9495404(B2)	2016-11-01	Kumarasamy et al.	Applicant
US2002/0069369(A1)	2002-06-01	Tremain	Applicant
US2002/0095609(A1)	2002-07-01	Tokunaga	Applicant
US2002/0194511(A1)	2002-12-01	Swoboda	Applicant
US2003/0126494(A1)	2003-07-01	Strasser	Applicant
US2003/0204597(A1)	2003-10-01	Arakawa et al.	Applicant
US2005/0060356(A1)	2005-03-01	Saika	Applicant
US2005/0198303(A1)	2005-09-01	Knauerhase	Examiner
US2005/0216788(A1)	2005-09-01	Mani-Meitav et al.	Applicant
US2006/0058994(A1)	2006-03-01	Ravi et al.	Applicant
US2006/0184935(A1)	2006-08-01	Abels et al.	Applicant
US2006/0195715(A1)	2006-08-01	Herington	Examiner
US2006/0224846(A1)	2006-10-01	Amarendran	Applicant
US2006/0225065(A1)	2006-10-01	Chandhok et al.	Applicant
US2006/0230136(A1)	2006-10-01	Ma	Applicant
US2007/0198802(A1)	2007-08-01	Kavuri	Applicant
US2007/0203938(A1)	2007-08-01	Prahlad et al.	Applicant
US2007/0208918(A1)	2007-09-01	Harbin et al.	Applicant
US2007/0220319(A1)	2007-09-01	Desai et al.	Applicant
US2007/0234302(A1)	2007-10-01	Suzuki et al.	Applicant
US2007/0239804(A1)	2007-10-01	Armstrong et al.	Applicant
US2007/0266056(A1)	2007-11-01	Stacey et al.	Applicant
US2008/0059704(A1)	2008-03-01	Kavuri	Applicant
US2008/0091655(A1)	2008-04-01	Gokhale	Applicant
US2008/0195639(A1)	2008-08-01	Freeman et al.	Applicant
US2008/0228771(A1)	2008-09-01	Prahlad et al.	Applicant
US2008/0229037(A1)	2008-09-01	Bunte	Applicant
US2008/0243855(A1)	2008-10-01	Prahlad	Applicant
US2008/0243947(A1)	2008-10-01	Kaneda	Applicant
US2008/0250407(A1)	2008-10-01	Dadhia et al.	Applicant
US2008/0270564(A1)	2008-10-01	Rangegowda et al.	Applicant
US2008/0282253(A1)	2008-11-01	Huizenga	Applicant
US2008/0320319(A1)	2008-12-01	Muller	Applicant
US2009/0006733(A1)	2009-01-01	Gold et al.	Applicant
US2009/0144416(A1)	2009-06-01	Chatley et al.	Applicant
US2009/0210427(A1)	2009-08-01	Eidler et al.	Applicant
US2009/0228669(A1)	2009-09-01	Slesarev et al.	Applicant
US2009/0240904(A1)	2009-09-01	Austruy et al.	Applicant
US2009/0287665(A1)	2009-11-01	Prahlad	Applicant
US2009/0300057(A1)	2009-12-01	Friedman	Applicant
US2009/0307166(A1)	2009-12-01	Routray et al.	Applicant
US2009/0313260(A1)	2009-12-01	Mimatsu	Applicant
US2009/0319534(A1)	2009-12-01	Gokhale	Applicant
US2009/0319585(A1)	2009-12-01	Gokhale	Applicant
US2009/0320029(A1)	2009-12-01	Kottomtharayil	Applicant
US2010/0011178(A1)	2010-01-01	Feathergill	Applicant
US2010/0030984(A1)	2010-02-01	Erickson	Applicant
US2010/0049929(A1)	2010-02-01	Nagarkar et al.	Applicant
US2010/0070466(A1)	2010-03-01	Prahlad et al.	Applicant
US2010/0070474(A1)	2010-03-01	Lad	Applicant
US2010/0070725(A1)	2010-03-01	Prahlad	Examiner
US2010/0082672(A1)	2010-04-01	Kottomtharayil et al.	Applicant
US2010/0107172(A1)	2010-04-01	Calinescu et al.	Applicant
US2010/0186014(A1)	2010-07-01	Vaghani et al.	Applicant
US2010/0242096(A1)	2010-09-01	Varadharajan et al.	Applicant
US2010/0257523(A1)	2010-10-01	Frank	Applicant
US2010/0262586(A1)	2010-10-01	Rosikiewicz et al.	Applicant
US2010/0262794(A1)	2010-10-01	De Beer et al.	Applicant
US2010/0299309(A1)	2010-11-01	Maki et al.	Applicant
US2010/0306173(A1)	2010-12-01	Frank	Applicant
US2010/0306486(A1)	2010-12-01	Balasubramanian et al.	Applicant
US2010/0325727(A1)	2010-12-01	Neystadt et al.	Applicant
US2010/0332401(A1)	2010-12-01	Prahlad	Applicant
US2010/0332454(A1)	2010-12-01	Prahlad et al.	Applicant
US2010/0332456(A1)	2010-12-01	Prahlad et al.	Applicant
US2010/0332479(A1)	2010-12-01	Prahlad	Applicant
US2010/0332629(A1)	2010-12-01	Cotugno et al.	Applicant
US2010/0332818(A1)	2010-12-01	Prahlad	Applicant
US2010/0333100(A1)	2010-12-01	Miyazaki et al.	Applicant
US2010/0333116(A1)	2010-12-01	Prahlad	Applicant
US2011/0010515(A1)	2011-01-01	Ranade	Applicant
US2011/0016467(A1)	2011-01-01	Kane	Applicant
US2011/0022811(A1)	2011-01-01	Kirihata et al.	Applicant
US2011/0047541(A1)	2011-02-01	Yamaguchi et al.	Applicant
US2011/0061045(A1)	2011-03-01	Phillips	Applicant
US2011/0087632(A1)	2011-04-01	Subramanian et al.	Applicant
US2011/0161299(A1)	2011-06-01	Prahlad	Applicant
US2011/0191559(A1)	2011-08-01	Li et al.	Applicant
US2011/0202734(A1)	2011-08-01	Dhakras et al.	Applicant
US2011/0213754(A1)	2011-09-01	Bindal	Applicant
US2011/0239013(A1)	2011-09-01	Muller	Applicant
US2011/0252208(A1)	2011-10-01	Ali et al.	Applicant
US2012/0017043(A1)	2012-01-01	Aizman et al.	Applicant
US2012/0017114(A1)	2012-01-01	Timashev et al.	Applicant
US2012/0072685(A1)	2012-03-01	Otani	Applicant
US2012/0079221(A1)	2012-03-01	Sivasubramanian et al.	Applicant
US2012/0084262(A1)	2012-04-01	Dwarampudi et al.	Applicant
US2012/0110328(A1)	2012-05-01	Pate et al.	Applicant
US2012/0131295(A1)	2012-05-01	Nakajima	Applicant
US2012/0131578(A1)	2012-05-01	Ciano et al.	Applicant
US2012/0150818(A1)	2012-06-01	Vijayan Retnamma et al.	Applicant
US2012/0150826(A1)	2012-06-01	Vijayan Retnamma et al.	Applicant
US2012/0151084(A1)	2012-06-01	Stathopoulos et al.	Applicant
US2012/0167083(A1)	2012-06-01	Suit	Applicant
US2012/0254364(A1)	2012-10-01	Vijayan	Applicant
US2012/0278799(A1)	2012-11-01	Starks et al.	Applicant
US2012/0324183(A1)	2012-12-01	Chiruvolu et al.	Applicant
US2012/0331248(A1)	2012-12-01	Kono et al.	Applicant
US2013/0024722(A1)	2013-01-01	Kotagiri	Applicant
US2013/0042234(A1)	2013-02-01	Deluca et al.	Applicant
US2013/0061014(A1)	2013-03-01	Prahlad et al.	Applicant
US2013/0080841(A1)	2013-03-01	Reddy et al.	Applicant
US2013/0117744(A1)	2013-05-01	Klein et al.	Applicant
US2013/0173771(A1)	2013-07-01	Ditto et al.	Applicant
US2013/0227558(A1)	2013-08-01	Du et al.	Applicant
US2013/0232215(A1)	2013-09-01	Gupta et al.	Applicant
US2013/0262390(A1)	2013-10-01	Kumarasamy et al.	Applicant
US2013/0262638(A1)	2013-10-01	Kumarasamy et al.	Applicant
US2013/0262801(A1)	2013-10-01	Sancheti et al.	Applicant
US2013/0268931(A1)	2013-10-01	O'Hare et al.	Applicant
US2013/0290267(A1)	2013-10-01	Dwarampudi et al.	Applicant
US2013/0326260(A1)	2013-12-01	Wei et al.	Applicant
US2014/0007097(A1)	2014-01-01	Chin et al.	Applicant
US2014/0007181(A1)	2014-01-01	Sarin et al.	Applicant
US2014/0095816(A1)	2014-04-01	Hsu et al.	Applicant
US2014/0136803(A1)	2014-05-01	Qin	Applicant
US2014/0181038(A1)	2014-06-01	Pawar et al.	Applicant
US2014/0181044(A1)	2014-06-01	Pawar et al.	Applicant
US2014/0181045(A1)	2014-06-01	Pawar et al.	Applicant
US2014/0181046(A1)	2014-06-01	Pawar et al.	Applicant
US2014/0188803(A1)	2014-07-01	James et al.	Applicant
US2014/0196038(A1)	2014-07-01	Kottomtharayil et al.	Applicant
US2014/0196039(A1)	2014-07-01	Kottomtharayil et al.	Applicant
US2014/0196056(A1)	2014-07-01	Kottomtharayil et al.	Applicant
US2014/0201151(A1)	2014-07-01	Kumarasamy et al.	Applicant
US2014/0201157(A1)	2014-07-01	Pawar et al.	Applicant
US2014/0201162(A1)	2014-07-01	Kumarasamy et al.	Applicant
US2014/0237537(A1)	2014-08-01	Manmohan et al.	Applicant
US2014/0278530(A1)	2014-09-01	Bruce et al.	Applicant
US2014/0282514(A1)	2014-09-01	Carson et al.	Applicant
US2014/0330874(A1)	2014-11-01	Novak et al.	Applicant
US2014/0337295(A1)	2014-11-01	Haselton et al.	Applicant
US2014/0372384(A1)	2014-12-01	Long et al.	Applicant
US2015/0074060(A1)	2015-03-01	Varadharajan et al.	Applicant
US2015/0074536(A1)	2015-03-01	Varadharajan et al.	Applicant
US2015/0120928(A1)	2015-04-01	Gummaraju et al.	Applicant
US2015/0134607(A1)	2015-05-01	Magdon-Ismail et al.	Applicant
US2015/0161015(A1)	2015-06-01	Kumarasamy et al.	Applicant
US2015/0317216(A1)	2015-11-01	Hsu et al.	Applicant
US2015/0370652(A1)	2015-12-01	He et al.	Applicant
US2015/0378833(A1)	2015-12-01	Misra et al.	Applicant
US2015/0378849(A1)	2015-12-01	Liu et al.	Applicant
US2016/0019317(A1)	2016-01-01	Pawar et al.	Applicant
US2016/0147607(A1)	2016-05-01	Dornemann et al.	Applicant
US2016/0196160(A1)	2016-07-01	Deshpande et al.	Applicant
US2016/0306558(A1)	2016-10-01	Varadharajan et al.	Applicant
US2016/0306587(A1)	2016-10-01	Dornemann et al.	Applicant
US2016/0306642(A1)	2016-10-01	Kottomtharayil et al.	Applicant
US2016/0306715(A1)	2016-10-01	Kumarasamy et al.	Applicant
US2017/0031707(A1)	2017-02-01	Mitkar et al.	Applicant
EP259912(A1)	1988-03-01		Applicant
EP405926(A2)	1991-01-01		Applicant
EP467546(A2)	1992-01-01		Applicant
EP541281(A2)	1993-05-01		Applicant
EP774715(A1)	1997-05-01		Applicant
EP809184(A1)	1997-11-01		Applicant
EP817040(A2)	1998-01-01		Applicant
EP899662(A1)	1999-03-01		Applicant
EP981090(A1)	2000-02-01		Applicant
WO95/13580	1995-05-01		Applicant
WO99/12098	1999-03-01		Applicant
WO2006/052872	2006-05-01		Applicant

Non-Patent Literature (37)

International Search Report and Written Opinion for PCT/US2011/054374, dated May 2, 2012, 7 pages.Applicant
International Preliminary Report on Patentability and Written Opinion for PCT/US2011/054374, dated Apr. 2, 2013, 9 pages.Applicant
Armstead et al., “Implementation of a Campus-wide Distributed Mass Storage Service: The Dream vs. Reality,” IEEE, Sep. 11-14, 1995, pp. 190-199.Applicant
Arneson, “Mass Storage Archiving in Network Environments,” Digest of Papers, Ninth IEEE Symposium on Mass Storage Systems, Oct. 31, 1988-Nov. 3, 1988, pp. 45-50, Monterey, CA.Applicant
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.Applicant
Celesti, et al., “Improving Virtual Machine Migration in Federated Cloud Environments”, 2010, pp. 61-67.Applicant
Chiappetta, Marco, “ESA Enthusiast System Architecture,” <http://hothardware.com/Articles/NVIDIA—ESA—Enthusiast—System—Architecture/>, Nov. 5, 2007, 2 pages.Applicant
Cully, et al., “Remus: High Availability via Asynchronous Virtual Machine Replication”, 2008, pp. 161-174.Applicant
Deng, et al., “Fast Saving and Restoring Virtual Machines with Page Compression”, 2011, pp. 150-157.Applicant
Eitel, “Backup and Storage Management in Distributed Heterogeneous Environments,” IEEE, Jun. 12-16, 1994, pp. 124-126.Applicant
Gait, “The Optical File Cabinet: A Random-Access File System for Write-Once Optical Disks,” IEEE Computer, vol. 21, No. 6, pp. 11-22 (Jun. 1988) (see in particular figure 5 in p. 15 and recitation in claim 5).Applicant
Granger, et al., “Survivable Storage Systems”, 2001, pp. 184-195.Applicant
Gupta, et al., “GPFS-SNC: An enterprise storage framework for virtual-machine clouds”, 2011, pp. 1-10.Applicant
Haselhorst, et al., “Efficient Storage Synchronization for Live Migration in Cloud Infrastructures”, 2011, pp. 511-518.Applicant
Hirofuchi, et al., “Enabling Instantaneous Relocation of Virtual Machines with a Lightweight VMM Extension”, 2010, pp. 73-83.Applicant
Hu, et al., “Virtual Machine based Hot-spare Fault-tolerant System”, 2009, pp. 429-432.Applicant
Huff, KL, “Data Set Usage Sequence Number,” IBM Technical Disclosure Bulletin, vol. 24, No. 5, Oct. 1981 New York, US, pp. 2404-2406.Applicant
Jander, M., “Launching Storage-Area Net,” Data Communications, US, McGraw Hill, NY, vol. 27, No. 4 (Mar. 21, 1998), pp. 64-72.Applicant
Jo, Changyeon, et al., “Efficient Live Migration of Virtual Machines Using Shared Storage”, 2013, pp. 1-10.Applicant
Kuo, et al., “A Hybrid Cloud Storage Architecture for Service Operational High Availability”, 2013, pp. 487-492.Applicant
Liang, et al., “A virtual disk environment for providing file system recovery”, 2006, pp. 589-599.Applicant
Mao, et al., “Read-Performance Optimization for Deduplication-Based Storage Systems in the Cloud”, 2014, pp. 1-22.Applicant
Migrate a Virtual Machine with Storage vMotion in the vSphere Client. http://pubs.vmware.com/vsphere-51/advanced/print/jsp?topic=/com.vmware.vsphere.vcent . . . Retrieved Aug. 12, 2014; 2 pages.Applicant
Nance et al., “Virtual Machine Introspection: Observation or Interference?”, 2008 IEEE.Applicant
Reingold, B. et al., “Cloud Computing: The Intersection of Massive Scalability, Data Security and Privacy (Part I),” LegalWorks, a Thomson Business, Jun. 2009, 5 pages.Applicant
Reingold, B. et al., “Cloud Computing: Industry and Government Developments (Part II),” LegalWorks, Sep. 2009, 5 pages.Applicant
Reingold, B. et al., “Cloud Computing: Whose Law Governs the Cloud? (Part III),” LegalWorks, Jan.-Feb. 2010, 6 pages.Applicant
Rosenblum et al., “The Design and Implementation of a Log-Structured File System,” Operating Systems Review SIGOPS, vol. 25, No. 5, New York, US, pp. 1-15 (May 1991).Applicant
Tran, et al, “Efficient Cooperative Backup with Decentralized Trust Management”, 2012, pp. 1-25.Applicant
Travostino, et al., “Seamless live migration of virtual machines over the MAN/WAN”, 2006, pp. 901-907.Applicant
Vaghani, “Virtual Machine File System”, 2010, pp. 57-70.Applicant
VMware Storage VMotion—Non-Disruptive Live Migration for Virtual Machine Storage Disk Files. Copyright 2009 VMware, Inc.; 2 pages.Applicant
Vrable, et al., “Cumulus: Filesystem Backup to the Cloud”, 2009, pp. 1-28.Applicant
vSphere Storage vMotion: Storage Management & Virtual Machine Migration. http://www.vmware.com/products /vsphere/features/storage-vmotion Retrieved Aug. 12, 2014; 6 pages.Applicant
Wikipedia, “Cloud computing,” <http://en.wikipedia.org/wiki/Cloud—computing>, 2009, 11 pages.Applicant
Wood, et al., “Disaster Recovery as a Cloud Service: Economic Benefits & Deployment Challenges”, 2010, pp. 1-7.Applicant
Zhao, et al., “Adaptive Distributed Load Balancing Algorithm based on Live Migration of Virtual Machines in Cloud”, 2009, pp. 170-175.Applicant

Abstract

Description

Related Applications

Background

Summary

Description of the Drawings

[0016] FIG. 1A is a block diagram illustrating an exemplary information management system.

[0017] FIG. 1B is a detailed view of a primary storage device, a secondary storage device, and some examples of primary data and secondary copy data.

[0018] FIG. 1C is a block diagram of an exemplary information management system including a storage manager, one or more data agents, and one or more media agents.

[0019] FIG. 1D is a block diagram illustrating a scalable information management system.

[0020] FIG. 1E illustrates certain secondary copy operations according to an exemplary storage policy.

[0023] FIG. 4 is a flow diagram illustrative of one embodiment of a routine for archiving virtual machines according to certain embodiments.

[0024] FIG. 5 is a flow diagram illustrative of one embodiment of a routine for restoring archived virtual machines according to certain embodiments.

Detailed Description

Information Management System Overview

- [0031] U.S. Pat. Pub. No. 2010-0332456, entitled “DATA OBJECT STORE AND SERVER FOR A CLOUD STORAGE ENVIRONMENT, INCLUDING DATA DEDUPLICATION AND DATA MANAGEMENT ACROSS MULTIPLE CLOUD STORAGE SITES”;
- [0032] U.S. Pat. No. 7,035,880, entitled “MODULAR BACKUP AND RETRIEVAL SYSTEM USED IN CONJUNCTION WITH A STORAGE AREA NETWORK”;
- [0033] U.S. Pat. No. 7,343,453, entitled “HIERARCHICAL SYSTEMS AND METHODS FOR PROVIDING A UNIFIED VIEW OF STORAGE INFORMATION”;
- [0034] U.S. Pat. No. 7,395,282, entitled “HIERARCHICAL BACKUP AND RETRIEVAL SYSTEM”;
- [0035] U.S. Pat. No. 7,246,207, entitled “SYSTEM AND METHOD FOR DYNAMICALLY PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK”;
- [0036] U.S. Pat. No. 7,747,579, entitled “METABASE FOR FACILITATING DATA CLASSIFICATION”;
- [0037] U.S. Pat. No. 8,229,954, entitled “MANAGING COPIES OF DATA”;
- [0038] U.S. Pat. No. 7,617,262, entitled “SYSTEM AND METHODS FOR MONITORING APPLICATION DATA IN A DATA REPLICATION SYSTEM”;
- [0039] U.S. Pat. No. 7,529,782, entitled “SYSTEM AND METHODS FOR PERFORMING A SNAPSHOT AND FOR RESTORING DATA”;
- [0040] U.S. Pat. No. 8,230,195, entitled “SYSTEM AND METHOD FOR PERFORMING AUXILIARY STORAGE OPERATIONS”;
- [0041] U.S. Pat. Pub. No. 2012/0084268, entitled “CONTENT-ALIGNED, BLOCK-BASED DEDUPLICATION”;
- [0042] U.S. Pat. Pub. No. 2006/0224846, entitled “SYSTEM AND METHOD TO SUPPORT SINGLE INSTANCE STORAGE OPERATIONS”;
- [0043] U.S. Pat. Pub. No. 2009/0329534, entitled “APPLICATION-AWARE AND REMOTE SINGLE INSTANCE DATA MANAGEMENT”;
- [0044] U.S. Pat. Pub. No. 2012/0150826, entitled “DISTRIBUTED DEDUPLICATED STORAGE SYSTEM”;
- [0045] U.S. Pat. Pub. No. 2012/0150818, entitled “CLIENT-SIDE REPOSITORY IN A NETWORKED DEDUPLICATED STORAGE SYSTEM”;
- [0046] U.S. Pat. No. 8,170,995, entitled “METHOD AND SYSTEM FOR OFFLINE INDEXING OF CONTENT AND CLASSIFYING STORED DATA”; and
- [0047] U.S. Pat. No. 8,156,086, entitled “SYSTEMS AND METHODS FOR STORED DATA VERIFICATION”.

Client Computing Devices

[0055] In some cases, each client computing device 102 is associated with one or more users and/or corresponding user accounts, of employees or other individuals.

Primary Data and Exemplary Primary Storage Devices

Secondary Copies and Exemplary Secondary Storage Devices

The Use of Intermediary Devices For Creating Secondary Copies

Exemplary Primary Data and an Exemplary Secondary Copy

Exemplary Information Management System Architecture

[0101] Storage Manager

[0107] According to certain embodiments, the storage manager provides one or more of the following functions:

- [0108] initiating execution of secondary copy operations;
- [0109] managing secondary storage devices 108 and inventory/capacity of the same;
- [0110] allocating secondary storage devices 108 for secondary storage operations;
- [0111] monitoring completion of and providing status reporting related to secondary storage operations;
- [0112] tracking age information relating to secondary copies 116, secondary storage devices 108, and comparing the age information against retention guidelines;
- [0113] tracking movement of data within the information management system 100;
- [0114] tracking logical associations between components in the information management system 100;
- [0115] protecting metadata associated with the information management system 100; and
- [0116] implementing operations management functionality.

[0129] Data Agents

[0138] Media Agents

[0151] Distributed, Scalable Architecture

Exemplary Types of Information Management Operations

[0160] Data Movement Operations

[0163] Backup Operations

[0171] Archive Operations

[0175] Snapshot Operations

[0180] Replication Operations

[0184] Deduplication/Single-Instancing Operations

[0189] Information Lifecycle Management and Hierarchical Storage Management Operations

[0196] Auxiliary Copy and Disaster Recovery Operations

[0199] Data Processing and Manipulation Operations

[0202] Content Indexing

[0206] Classification Operations—Metabase

[0209] Encryption Operations

[0212] Management Operations

Information Management Policies

- [0233] schedules or other timing information, e.g., specifying when and/or how often to perform information management operations;
- [0234] the type of secondary copy 116 and/or secondary copy format (e.g., snapshot, backup, archive, HSM, etc.);
- [0235] a location or a class or quality of storage for storing secondary copies 116 (e.g., one or more particular secondary storage devices 108);
- [0236] preferences regarding whether and how to encrypt, compress, deduplicate, or otherwise modify or transform secondary copies 116;
- [0237] which system components and/or network pathways (e.g., preferred media agents 144) should be used to perform secondary storage operations;
- [0238] resource allocation between different computing devices or other system components used in performing information management operations (e.g., bandwidth allocation, available storage capacity, etc.);
- [0239] whether and how to synchronize or otherwise distribute files or other data objects across multiple computing devices or hosted services; and
- [0240] retention information specifying the length of time primary data 112 and/or secondary copies 116 should be retained, e.g., in a particular class or tier of storage devices, or within the information management system 100.

- [0242] frequency with which primary data 112 or a secondary copy 116 of a data object or metadata has been or is predicted to be used, accessed, or modified;
- [0243] time-related factors (e.g., aging information such as time since the creation or modification of a data object);
- [0244] deduplication information (e.g., hashes, data blocks, deduplication block size, deduplication efficiency or other metrics);
- [0245] an estimated or historic usage or cost associated with different components (e.g., with secondary storage devices 108);
- [0246] the identity of users, applications 110, client computing devices 102 and/or other computing devices that created, accessed, modified, or otherwise utilized primary data 112 or secondary copies 116;
- [0247] a relative sensitivity (e.g., confidentiality) of a data object, e.g., as determined by its content and/or metadata;
- [0248] the current or historical storage capacity of various storage devices;
- [0249] the current or historical network capacity of network pathways connecting various components within the storage operation cell;
- [0250] access control lists or other security information; and
- [0251] the content of a particular data object (e.g., its textual content) or of metadata associated with the data object.
  Exemplary Storage Policy and Secondary Storage Operations