A method for automatically encrypting files is disclosed. In some cases, the method may be performed by computer hardware comprising one or more processors. The method can include detecting access to a first file, which may be stored in a primary storage system. Further, the method can include determining whether the access comprises a write access. In response to determining that the access comprises a write access, the method can include accessing file metadata associated with the first file and accessing a set of encryption rules. In addition, the method can include determining whether the file metadata satisfies the set of encryption rules. In response to determining that the file metadata satisfies the set of encryption rules, the method can include encrypting the first file to obtain a first encrypted file and modifying an extension of the first encrypted file to include an encryption extension.

DETAILED DESCRIPTION

Information Management System Overview

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

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

Certain embodiments described herein provide systems and methods capable of addressing these and other shortcomings of prior approaches by implementing unified, organization-wide information management.FIG. 1Ashows one such information management system100, 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 system100.

The organization which employs the information management system100may be a corporation or other business entity, non-profit organization, educational institution, household, governmental agency, or the like.

Generally, the systems and associated components described herein may be compatible with and/or provide some or all of the functionality of the systems and corresponding components described in one or more of the following U.S. patents and patent application publications assigned to CommVault Systems, Inc., each of which is hereby incorporated in its entirety by reference herein:U.S. Pat. No. 8,285,681, entitled “DATA OBJECT STORE AND SERVER FOR A CLOUD STORAGE ENVIRONMENT, INCLUDING DATA DEDUPLICATION AND DATA MANAGEMENT ACROSS MULTIPLE CLOUD STORAGE SITES”;U.S. Pat. No. 7,035,880, entitled “MODULAR BACKUP AND RETRIEVAL SYSTEM USED IN CONJUNCTION WITH A STORAGE AREA NETWORK”;U.S. Pat. No. 7,343,453, entitled “HIERARCHICAL SYSTEMS AND METHODS FOR PROVIDING A UNIFIED VIEW OF STORAGE INFORMATION”;U.S. Pat. No. 7,395,282, entitled “HIERARCHICAL BACKUP AND RETRIEVAL SYSTEM”;U.S. Pat. No. 7,246,207, entitled “SYSTEM AND METHOD FOR DYNAMICALLY PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK”;U.S. Pat. No. 7,747,579, entitled “METABASE FOR FACILITATING DATA CLASSIFICATION”;U.S. Pat. No. 8,229,954, entitled “MANAGING COPIES OF DATA”;U.S. Pat. No. 7,617,262, entitled “SYSTEM AND METHODS FOR MONITORING APPLICATION DATA IN A DATA REPLICATION SYSTEM”;U.S. Pat. No. 7,529,782, entitled “SYSTEM AND METHODS FOR PERFORMING A SNAPSHOT AND FOR RESTORING DATA”;U.S. Pat. No. 8,230,195, entitled “SYSTEM AND METHOD FOR PERFORMING AUXILIARY STORAGE OPERATIONS”;U.S. Pat. No. 8,364,652, entitled “CONTENT-ALIGNED, BLOCK-BASED DEDUPLICATION”;U.S. Pat. Pub. No. 2006/0224846, entitled “SYSTEM AND METHOD TO SUPPORT SINGLE INSTANCE STORAGE OPERATIONS”;U.S. Pat. Pub. No. 2009/0319534, entitled “APPLICATION-AWARE AND REMOTE SINGLE INSTANCE DATA MANAGEMENT”;U.S. Pat. Pub. No. 2012/0150826, entitled “DISTRIBUTED DEDUPLICATED STORAGE SYSTEM”;U.S. Pat. Pub. No. 2012/0150818, entitled “CLIENT-SIDE REPOSITORY IN A NETWORKED DEDUPLICATED STORAGE SYSTEM”;U.S. Pat. No. 8,170,995, entitled “METHOD AND SYSTEM FOR OFFLINE INDEXING OF CONTENT AND CLASSIFYING STORED DATA”; andU.S. Pat. No. 8,156,086, entitled “SYSTEMS AND METHODS FOR STORED DATA VERIFICATION”

The illustrated information management system100includes one or more client computing device102having at least one application110executing thereon, and one or more primary storage devices104storing primary data112. The client computing device(s)102and the primary storage devices104may generally be referred to in some cases as a primary storage subsystem117.

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

For instance, in some cases information management system100generally refers to a combination of specialized components used to protect, move, manage, manipulate and/or process data and metadata generated by the client computing devices102. However, the term may generally not refer to the underlying components that generate and/or store the primary data112, such as the client computing devices102themselves, the applications110and operating system residing on the client computing devices102, and the primary storage devices104.

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

Client Computing Devices

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

The client computing devices102may include, without limitation, one or more: workstations, personal computers, desktop computers, or other types of generally fixed computing systems such as mainframe computers and minicomputers.

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

In some cases, each client computing device102is associated with one or more users and/or corresponding user accounts, of employees or other individuals.

The term “client computing device” is used herein because the information management system100generally “serves” the data management and protection needs for the data generated by the client computing devices102. However, the use of this term does not imply that the client computing devices102cannot be “servers” in other respects. For instance, a particular client computing device102may act as a server with respect to other devices, such as other client computing devices102. As just a few examples, the client computing devices102can include mail servers, file servers, database servers, and web servers.

The client computing devices102may 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 devices102include one or more virtual machine(s) running on a virtual machine host computing device operated by the organization. As one example, the organization may use one virtual machine as a database server and another virtual machine as a mail server. A virtual machine manager (VMM) (e.g., a Hypervisor) may manage the virtual machines, and reside and execute on the virtual machine host computing device.

Each client computing device102may have one or more applications110(e.g., software applications) executing thereon which generate and manipulate the data that is to be protected from loss.

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

The applications110can 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 applications110.

As shown, the client computing devices102and other components in the information management system100can be connected to one another via one or more communication pathways114. The communication pathways114can 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 pathways114in some cases may also include application programming interfaces (APIs) including, e.g., cloud service provider APIs, virtual machine management APIs, and hosted service provider APIs.

Primary Data and Exemplary Primary Storage Devices

Primary data112according to some embodiments is production data or other “live” data generated by the operating system and other applications110residing on a client computing device102. The primary data112is stored on the primary storage device(s)104and is organized via a file system supported by the client computing device102. For instance, the client computing device(s)102and corresponding applications110may create, access, modify, write, delete, and otherwise use primary data112.

Primary data112is generally in the native format of the source application110. According to certain aspects, primary data112is 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 application110. Primary data112in some cases is created substantially directly from data generated by the corresponding source applications110.

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

The primary storage devices104storing the primary data112may be relatively fast and/or expensive (e.g., a disk drive, a hard-disk array, solid state memory, etc.). In addition, primary data112may be intended for relatively short term retention (e.g., several hours, days, or weeks).

According to some embodiments, the client computing device102can access primary data112from the primary storage device104by making conventional file system calls via the operating system. Primary data112representing 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 toFIG. 1B.

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

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

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

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

Each of the client computing devices102are associated with and/or in communication with one or more of the primary storage devices104storing corresponding primary data112. A client computing device102may be considered to be “associated with” or “in communication with” a primary storage device104if it is capable of one or more of: storing data to the primary storage device104, retrieving data from the primary storage device104, and modifying data retrieved from a primary storage device104.

The primary storage devices104can 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 devices104form part of a distributed file system. The primary storage devices104may have relatively fast I/O times and/or are relatively expensive in comparison to the secondary storage devices108. For example, the information management system100may generally regularly access data and metadata stored on primary storage devices104, whereas data and metadata stored on the secondary storage devices108is accessed relatively less frequently.

In some cases, each primary storage device104is dedicated to an associated client computing devices102. For instance, a primary storage device104in one embodiment is a local disk drive of a corresponding client computing device102. In other cases, one or more primary storage devices104can be shared by multiple client computing devices102. As one example, a primary storage device104can be a disk array shared by a group of client computing devices102, such as one of the following types of disk arrays: EMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV, NetApp FAS, HP EVA, and HP 3PAR.

The information management system100may 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 system100. For instance, the hosted services may be provided by various online service providers to the organization. Such service providers can provide services including social networking services, hosted email services, or hosted productivity applications or other hosted applications).

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

Secondary Copies and Exemplary Secondary Storage Devices

The primary data112stored on the primary storage devices104may be compromised in some cases, such as when an employee deliberately or accidentally deletes or overwrites primary data112during their normal course of work. Or the primary storage devices104can be damaged or otherwise corrupted.

For recovery and/or regulatory compliance purposes, it is therefore useful to generate copies of the primary data112. Accordingly, the information management system100includes one or more secondary storage computing devices106and one or more secondary storage devices108configured to create and store one or more secondary copies116of the primary data112and associated metadata. The secondary storage computing devices106and the secondary storage devices108may be referred to in some cases as a secondary storage subsystem118.

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

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

Regardless of the type of secondary copy operation, the client computing devices102access or receive primary data112and communicate the data, e.g., over the communication pathways114, for storage in the secondary storage device(s)108.

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

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

In some cases, secondary copies116are indexed so users can browse and restore at another point in time. After creation of a secondary copy116representative of certain primary data112, a pointer or other location indicia (e.g., a stub) may be placed in primary data112, or be otherwise associated with primary data112to indicate the current location on the secondary storage device(s)108.

Since an instance a data object or metadata in primary data112may change over time as it is modified by an application110(or hosted service or the operating system), the information management system100may create and manage multiple secondary copies116of a particular data object or metadata, each representing the state of the data object in primary data112at a particular point in time. Moreover, since an instance of a data object in primary data112may eventually be deleted from the primary storage device104and the file system, the information management system100may continue to manage point-in-time representations of that data object, even though the instance in primary data112no longer exists.

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

Secondary copies116may be distinguished from corresponding primary data112in a variety of ways, some of which will now be described. First, as discussed, secondary copies116can be stored in a different format (e.g., backup, archive, or other non-native format) than primary data112. For this or other reasons, secondary copies116may not be directly useable by the applications110of the client computing device102, e.g., via standard system calls or otherwise without modification, processing, or other intervention by the information management system100.

Secondary copies116are also often stored on a secondary storage device108that is inaccessible to the applications110running on the client computing devices102(and/or hosted services). Some secondary copies116may 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 system100can 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 system100can access only with at least some human intervention (e.g. tapes located at an offsite storage site).

The secondary storage devices108can 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 devices108are provided in a cloud (e.g. a private cloud or one operated by a third-party vendor).

The secondary storage device(s)108in 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 data112and at least some secondary copies116. In one example, a disk array capable of performing hardware snapshots stores primary data112and creates and stores hardware snapshots of the primary data112as secondary copies116.

The Use of Intermediary Devices For Creating Secondary Copies

Creating secondary copies can be a challenging task. For instance, there can be hundreds or thousands of client computing devices102continually generating large volumes of primary data112to be protected. Also, there can be significant overhead involved in the creation of secondary copies116. Moreover, secondary storage devices108may be special purpose components, and interacting with them can require specialized intelligence.

In some cases, the client computing devices102interact directly with the secondary storage device108to create the secondary copies116. However, in view of the factors described above, this approach can negatively impact the ability of the client computing devices102to serve the applications110and produce primary data112. Further, the client computing devices102may not be optimized for interaction with the secondary storage devices108.

Thus, in some embodiments, the information management system100includes one or more software and/or hardware components which generally act as intermediaries between the client computing devices102and the secondary storage devices108. In addition to off-loading certain responsibilities from the client computing devices102, these intermediary components can provide other benefits. For instance, as discussed further below with respect toFIG. 1D, distributing some of the work involved in creating secondary copies116can enhance scalability.

The intermediary components can include one or more secondary storage computing devices106as shown inFIG. 1Aand/or one or more media agents, which can be software modules residing on corresponding secondary storage computing devices106(or other appropriate devices). Media agents are discussed below (e.g., with respect toFIGS. 1C-1E).

The secondary storage computing device(s)106can 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 devices102. In some cases, the secondary storage computing device(s)106include specialized hardware and/or software componentry for interacting with the secondary storage devices108.

To create a secondary copy116, the client computing device102communicates the primary data112to be copied (or a processed version thereof) to the designated secondary storage computing device106, via the communication pathway114. The secondary storage computing device106in turn conveys the received data (or a processed version thereof) to the secondary storage device108. In some such configurations, the communication pathway114between the client computing device102and the secondary storage computing device106comprises a portion of a LAN, WAN or SAN. In other cases, at least some client computing devices102communicate directly with the secondary storage devices108(e.g., via Fibre Channel or SCSI connections).

Exemplary Primary Data and an Exemplary Secondary Copy

FIG. 1Bis a detailed view showing some specific examples of primary data stored on the primary storage device(s)104and 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)104are primary data objects including word processing documents119A-B, spreadsheets120, presentation documents122, video files124, image files126, email mailboxes128(and corresponding email messages129A-C), html/xml or other types of markup language files130, databases132and corresponding tables133A-133C).

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)108are secondary copy objects134A-C which may include copies of or otherwise represent corresponding primary data objects and metadata.

As shown, the secondary copy objects134A-C can individually represent more than one primary data object. For example, secondary copy data object134A represents three separate primary data objects133C,122and129C (represented as133C′,122′ and129C′, respectively). Moreover, as indicated by the prime mark (′), a secondary copy object may store a representation of a primary data object or metadata differently than the original format, e.g., in a compressed, encrypted, deduplicated, or other modified format.

Exemplary Information Management System Architecture

The information management system100can 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 system100. For instance, as will be discussed, such design choices can impact performance as well as the adaptability of the information management system100to data growth or other changing circumstances.

FIG. 1Cshows an information management system100designed according to these considerations and which includes: a central storage or information manager140configured to perform certain control functions, one or more data agents142executing on the client computing device(s)102configured to process primary data112, and one or more media agents144executing on the one or more secondary storage computing devices106for performing tasks involving the secondary storage devices108,

Storage Manager

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

For these and other reasons, according to certain embodiments, responsibility for controlling the information management system100, or at least a significant portion of that responsibility, is allocated to the storage manager140.

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

The storage manager140may 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 system100, e.g., to protect and control the primary data112and secondary copies116of data and metadata.

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

According to certain embodiments, the storage manager provides one or more of the following functions:initiating execution of secondary copy operations;managing secondary storage devices108and inventory/capacity of the same;allocating secondary storage devices108for secondary storage operations;monitoring completion of and providing status reporting related to secondary storage operations;tracking age information relating to secondary copies116, secondary storage devices108, and comparing the age information against retention guidelines;tracking movement of data within the information management system100;tracking logical associations between components in the information management system100;protecting metadata associated with the information management system100; andimplementing operations management functionality.

The storage manager140may maintain a database146of management-related data and information management policies148. The database146may include a management index150or 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 manager140may use the index150to track logical associations between media agents144and secondary storage devices108and/or movement of data from primary storage devices104to secondary storage devices108.

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

Thus, the information management system100may utilize information management policies148for specifying and executing information management operations (e.g., on an automated basis). Generally, an information management policy148can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with storage or other information management operations.

The storage manager database146may maintain the information management policies148and associated data, although the information management policies148can be stored in any appropriate location. For instance, a storage policy may be stored as metadata in a media agent database152or in a secondary storage device108(e.g., as an archive copy) for use in restore operations or other information management operations, depending on the embodiment. Information management policies148are described further below.

According to certain embodiments, the storage manager database146comprises a relational database (e.g., an SQL database) for tracking metadata, such as metadata associated with secondary copy operations (e.g., what client computing devices102and corresponding data were protected). This and other metadata may additionally be stored in other locations, such as at the secondary storage computing devices106or on the secondary storage devices108, allowing data recovery without the use of the storage manager140.

As shown, the storage manager140may include a jobs agent156, a user interface158, and a management agent154, all of which may be implemented as interconnected software modules or application programs.

The jobs agent156in 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 system100. For instance, the jobs agent156may access information management policies148to determine when and how to initiate and control secondary copy and other information management operations, as will be discussed further.

The user interface158may 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 system100and its constituent components.

The storage manager140may 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 interface158.

Via the user interface158, users may optionally issue instructions to the components in the information management system100regarding 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 system100(e.g., the amount of capacity left in a storage device).

In general, the management agent154allows multiple information management systems100to communicate with one another. For example, the information management system100in 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 agents154.

For instance, the management agent154can provide the storage manager140with the ability to communicate with other components within the information management system100(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. Nos. 7,747,579 and 7,343,453, which are incorporated by reference herein.

Data Agents

As discussed, a variety of different types of applications110can reside on a given client computing device102, 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 copies116, the client computing devices102may be tasked with processing and preparing the primary data112from these various different applications110. Moreover, the nature of the processing/preparation can differ across clients and application types, e.g., due to inherent structural and formatting differences between applications110.

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

The data agent142may 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 agent142may take part in performing data storage operations such as the copying, archiving, migrating, replicating of primary data112stored in the primary storage device(s)104. The data agent142may receive control information from the storage manager140, such as commands to transfer copies of data objects, metadata, and other payload data to the media agents144.

In some embodiments, a data agent142may be distributed between the client computing device102and storage manager140(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 agent142. In addition, a data agent142may perform some functions provided by a media agent144, e.g., encryption and deduplication.

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

A file system data agent, for example, may handle data files and/or other file system information. If a client computing device102has two or more types of data, one data agent142may be used for each data type to copy, archive, migrate, and restore the client computing device102data. For example, to backup, migrate, and restore all of the data on a Microsoft Exchange server, the client computing device102may use one Microsoft Exchange Mailbox data agent142to backup the Exchange mailboxes, one Microsoft Exchange Database data agent142to backup the Exchange databases, one Microsoft Exchange Public Folder data agent142to backup the Exchange Public Folders, and one Microsoft Windows File System data agent142to backup the file system of the client computing device102. In such embodiments, these data agents142may be treated as four separate data agents142by even though they reside on the same client computing device102.

Other embodiments may employ one or more generic data agents142that can handle and process data from two or more different applications110, or that can handle and process multiple data types, instead of or in addition to using specialized data agents142. For example, one generic data agent142may be used to back up, migrate and restore Microsoft Exchange Mailbox data and Microsoft Exchange Database data while another generic data agent may handle Microsoft Exchange Public Folder data and Microsoft Windows File System data.

Each data agent142may be configured to access data and/or metadata stored in the primary storage device(s)104associated with the data agent142and process the data as appropriate. For example, during a secondary copy operation, the data agent142may 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 agent144or other component. The file(s) may include a list of files or other metadata. Each data agent142can also assist in restoring data or metadata to primary storage devices104from a secondary copy116. For instance, the data agent142may operate in conjunction with the storage manager140and one or more of the media agents144to restore data from secondary storage device(s)108.

Media Agents

As indicated above with respect toFIG. 1A, off-loading certain responsibilities from the client computing devices102to intermediary components such as the media agent(s)144can provide a number of benefits including improved client computing device102operation, faster secondary copy operation performance, and enhanced scalability. As one specific example which will be discussed below in further detail, the media agent144can 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.

Generally speaking, a media agent144may be implemented as a software module that manages, coordinates, and facilitates the transmission of data, as directed by the storage manager140, between a client computing device102and one or more secondary storage devices108. Whereas the storage manager140controls the operation of the information management system100, the media agent144generally provides a portal to secondary storage devices108.

Media agents144can comprise logically and/or physically separate nodes in the information management system100(e.g., separate from the client computing devices102, storage manager140, and/or secondary storage devices108). In addition, each media agent144may reside on a dedicated secondary storage computing device106in some cases, while in other embodiments a plurality of media agents144reside on the same secondary storage computing device106.

A media agent144(and corresponding media agent database152) may be considered to be “associated with” a particular secondary storage device108if that media agent144is capable of one or more of: routing and/or storing data to the particular secondary storage device108, coordinating the routing and/or storing of data to the particular secondary storage device108, retrieving data from the particular secondary storage device108, and coordinating the retrieval of data from a particular secondary storage device108.

While media agent(s)144are generally associated with one or more secondary storage devices108, the media agents144in certain embodiments are physically separate from the secondary storage devices108. For instance, the media agents144may reside on secondary storage computing devices106having different housings or packages than the secondary storage devices108. In one example, a media agent144resides on a first server computer and is in communication with a secondary storage device(s)108residing in a separate, rack-mounted RAID-based system.

In operation, a media agent144associated with a particular secondary storage device108may instruct the secondary storage device108(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 device102. The media agent144may communicate with a secondary storage device108via a suitable communications link, such as a SCSI or Fiber Channel link.

As shown, each media agent144may maintain an associated media agent database152. The media agent database152may be stored in a disk or other storage device (not shown) that is local to the secondary storage computing device106on which the media agent144resides. In other cases, the media agent database152is stored remotely from the secondary storage computing device106.

The media agent database152can include, among other things, an index153including data generated during secondary copy operations and other storage or information management operations. The index153provides a media agent144or other component with a fast and efficient mechanism for locating secondary copies116or other data stored in the secondary storage devices108. In one configuration, a storage manager index150or other data structure may store data associating a client computing device102with a particular media agent144and/or secondary storage device108, as specified in a storage policy. A media agent index153or other data structure associated with the particular media agent144may in turn include information about the stored data.

For instance, for each secondary copy116, the index153may include metadata such as a list of the data objects (e.g., files/subdirectories, database objects, mailbox objects, etc.), a path to the secondary copy116on the corresponding secondary storage device108, location information indicating where the data objects are stored in the secondary storage device108, when the data objects were created or modified, etc. Thus, the index153includes metadata associated with the secondary copies116that is readily available for use in storage operations and other activities without having to be first retrieved from the secondary storage device108. In yet further embodiments, some or all of the data in the index153may instead or additionally be stored along with the data in a secondary storage device108, e.g., with a copy of the index153.

Because the index153maintained in the database152may operate as a cache, it can also be referred to as an index cache. In such cases, information stored in the index cache153typically 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 cache153reaches a particular size, the index cache153may be copied or migrated to a secondary storage device(s)108. This information may need to be retrieved and uploaded back into the index cache153or otherwise restored to a media agent144to 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 cache153allows for accelerated restores.

In some alternative embodiments the media agent144generally acts as a coordinator or facilitator of storage operations between client computing devices102and corresponding secondary storage devices108, but does not actually write the data to the secondary storage device108. For instance, the storage manager140(or the media agent144) may instruct a client computing device102and secondary storage device108to communicate with one another directly. In such a case the client computing device102transmits the data directly to the secondary storage device108according to the received instructions, and vice versa. In some such cases, the media agent144may still receive, process, and/or maintain metadata related to the storage operations. Moreover, in these embodiments, the payload data can flow through the media agent144for the purposes of populating the index cache153maintained in the media agent database152, but not for writing to the secondary storage device108.

The media agent144and/or other components such as the storage manager140may 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.

As described, certain functions of the information management system100can be distributed amongst various physical and/or logical components in the system. For instance, one or more of the storage manager140, data agents142, and media agents144may reside on computing devices that are physically separate from one another. This architecture can provide a number of benefits.

For instance, hardware and software design choices for each distributed component can be targeted to suit its particular function. The secondary computing devices106on which the media agents144reside can be tailored for interaction with associated secondary storage devices108and provide fast index cache operation, among other specific tasks. Similarly, the client computing device(s)102can be selected to effectively service the applications110residing thereon, in order to efficiently produce and store primary data112.

Moreover, in some cases, one or more of the individual components in the information management system100can be distributed to multiple, separate computing devices. As one example, for large file systems where the amount of data stored in the storage management database146is relatively large, the management database146may 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 manager140. This configuration can provide added protection because the database146can be protected with standard database utilities (e.g., SQL log shipping or database replication) independent from other functions of the storage manager140. The database146can 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 database146can 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 system100.

The distributed architecture also provides both scalability and efficient component utilization.FIG. 1Dshows an embodiment of the information management system100including a plurality of client computing devices102and associated data agents142as well as a plurality of secondary storage computing devices106and associated media agents144.

Additional components can be added or subtracted based on the evolving needs of the information management system100. For instance, depending on where bottlenecks are identified, administrators can add additional client computing devices102, secondary storage devices106(and corresponding media agents144), and/or secondary storage devices108.

Moreover, each client computing device102in some embodiments can communicate with any of the media agents144, e.g., as directed by the storage manager140. And each media agent144may be able to communicate with any of the secondary storage devices108, e.g., as directed by the storage manager140. Thus, operations can be routed to the secondary storage devices108in a dynamic and highly flexible manner. Further examples of scalable systems capable of dynamic storage operations are provided in U.S. Pat. No. 7,246,207, which is incorporated by reference herein.

In alternative configurations, certain components are not distributed and may instead reside and execute on the same computing device. For example, in some embodiments one or more data agents142and the storage manager140reside on the same client computing device102. In another embodiment, one or more data agents142and one or more media agents144reside on a single computing device.

Exemplary Types of Information Management Operations

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

Data Movement Operations

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

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

Backup Operations

A backup operation creates a copy of primary data112at 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 data112from which the backup copy is derived, and which may instead be stored in a native format of the source application(s)110. In various cases, backup copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format. For example, a backup copy may be stored in a backup format that facilitates compression and/or efficient long-term storage.

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

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

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

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

Any of the above types of backup operations can be at the file-level, e.g., where the information management system100generally 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 system100reassembles the blocks into files in a transparent fashion.

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

Archive Operations

Because backup operations generally involve maintaining a version of the copied data in primary data112and 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 copy116by 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 data112or a secondary copy116, depending on the situation. As with backup copies, archive copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format.

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

Moreover, when primary data112is archived, in some cases the archived primary data112or 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 copy116is archived, the secondary copy116may be deleted, and an archive copy can therefore serve the purpose of freeing up space in secondary storage device(s)108. In contrast, source copies often remain intact when creating backup copies.

Snapshot Operations

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

A snapshot copy in many cases can be made quickly and without significantly impacting primary computing resources because large amounts of data need not be copied or moved. In some embodiments, a snapshot may exist as a virtual file system, parallel to the actual file system. Users in some cases gain read-only access to the record of files and directories of the snapshot. By electing to restore primary data112from a snapshot taken at a given point in time, users may also return the current file system to the state of the file system that existed when the snapshot was taken.

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

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

Replication Operations

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

According to some embodiments storage operations are performed on replicated data that represents a recoverable state, or “known good state” of a particular application running on the source system. For instance, in certain embodiments, known good replication copies may be viewed as copies of primary data112. 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 data112. This can reduce access time, storage utilization, and impact on source applications110, among other benefits.

Based on known good state information, the information management system100can 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.

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

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

Depending on the embodiment, deduplication blocks can be of fixed or variable length. Using variable length blocks can provide enhanced deduplication by responding to changes in the data stream, but can involve complex processing. In some cases, the information management system100utilizes 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. No. 8,364,652, which is incorporated by reference herein.

The information management system100can perform deduplication in a variety of manners at a variety of locations in the information management system100. For instance, in some embodiments, the information management system100implements “target-side” deduplication by deduplicating data (e.g., secondary copies116) stored in the secondary storage devices108. In some such cases, the media agents144are generally configured to manage the deduplication process. For instance, one or more of the media agents144maintain 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 agents144and the client computing device(s)102and/or reduce redundant data stored in the primary storage devices104. Examples of such deduplication techniques are provided in U.S. Pat. Pub. No. 2012/0150818, which is incorporated by reference herein. Some other compatible deduplication/single instancing techniques are described in U.S. Pat. Pub. Nos. 2006/0224846 and 2009/0319534, which are incorporated by reference herein.

Information Lifecycle Management and Hierarchical Storage Management Operations

In some embodiments, files and other data over their lifetime move from more expensive, quick access storage to less expensive, slower access storage. Operations associated with moving data through various tiers of storage are sometimes referred to as information lifecycle management (ILM) operations.

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

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

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

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 system100uses the stub to locate the data and often make recovery of the data appear transparent, even though the HSM data may be stored at a location different from the remaining source data. The stub may also include some metadata associated with the corresponding data, so that a file system and/or application can provide some information about the data object and/or a limited-functionality version (e.g., a preview) of the data object.

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

Auxiliary Copy and Disaster Recovery Operations

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

The information management system100may also perform disaster recovery operations that make or retain disaster recovery copies, often as secondary, high-availability disk copies. The information management system100may 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 devices102and primary storage devices104, remote from some or all of the secondary storage devices108, or both.

Data Processing and Manipulation Operations

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

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

Content Indexing

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

The information management system100generally organizes and catalogues the results in a content index, which may be stored within the media agent database152, for example. The content index can also include the storage locations of (or pointer references to) the indexed data in the primary data112or secondary copies116, as appropriate. The results may also be stored, in the form of a content index database or otherwise, elsewhere in the information management system100(e.g., in the primary storage devices104, or in the secondary storage device108). Such index data provides the storage manager140or another component with an efficient mechanism for locating primary data112and/or secondary copies116of data objects that match particular criteria.

For instance, search criteria can be specified by a user through user interface158of the storage manager140. In some cases, the information management system100analyzes data and/or metadata in secondary copies116to create an “off-line” content index, without significantly impacting the performance of the client computing devices102. Depending on the embodiment, the system can also implement “on-line” content indexing, e.g., of primary data112. Examples of compatible content indexing techniques are provided in U.S. Pat. No. 8,170,995, which is incorporated by reference herein.

In order to help leverage the data stored in the information management system100, 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 data112(and/or secondary copies116), such that metabase related operations do not significantly impact performance on other components in the information management system100.

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

Encryption Operations

The information management system100in some cases is configured to process data (e.g., files or other data objects, secondary copies116, 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 system100.

The information management system100in some cases encrypts the data at the client level, such that the client computing devices102(e.g., the data agents142) encrypt the data prior to forwarding the data to other components, e.g., before sending the data media agents144during a secondary copy operation. In such cases, the client computing device102may 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 devices108can implement built-in, high performance hardware encryption.

Management Operations

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

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

Such information can be provided to users via the user interface158in a single, integrated view. For instance, the integrated user interface158can 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 system100. 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 system100, such as job status, component status, resource status (e.g., network pathways, etc.), and other information. The user may also drill down or use other means to obtain more detailed information regarding a particular component, job, or the like.

In some cases the information management system100alerts a user such as a system administrator when a particular resource is unavailable or congested. For example, a particular primary storage device104or secondary storage device108might 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 system100may suggest solutions to such problems when they occur (or provide a warning prior to occurrence). For example, the storage manager140may alert the user that a secondary storage device108is full or otherwise congested. The storage manager140may then suggest, based on job and data storage information contained in its database146, an alternate secondary storage device108.

Other types of corrective actions may include suggesting an alternate data path to a particular primary or secondary storage device104,108, or dividing data to be stored among various available primary or secondary storage devices104,108as 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 manager140implements the operations management functions described herein.

The information management system100can 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 devices108(e.g., backups, archives, or other secondary copies116). For example, the information management system100may construct and maintain a virtual repository for data stored in the information management system100that is integrated across source applications110, different storage device types, etc. According to some embodiments, e-discovery utilizes other techniques described herein, such as data classification and/or content indexing.

Information Management Policies

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

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

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

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

A storage policy can define where data is stored by specifying a target or destination storage device (or group of storage devices). For instance, where the secondary storage device108includes 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 devices108include one or more tape libraries, the storage policy may specify a particular tape library for storing the sub-clients associated with the storage policy, and may also specify a drive pool and a tape pool defining a group of tape drives and a group of tapes, respectively, for use in storing the sub-client data.

Datapath information can also be included in the storage policy. For instance, the storage policy may specify network pathways and components to utilize when moving the data to the destination storage device(s). In some embodiments, the storage policy specifies one or more media agents144for 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 devices102) and destination (e.g., a particular target secondary storage device108).

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

The information management policies148may 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 device102, and the like. In one configuration, a separate scheduling policy is maintained for particular sub-clients on a client computing device102. The scheduling policy specifies that those sub-clients are to be moved to secondary storage devices108every hour according to storage policies associated with the respective sub-clients.

When adding a new client computing device102, administrators can manually configure information management policies148and/or other settings, e.g., via the user interface158. However, this can be an involved process resulting in delays, and it may be desirable to begin data protecting operations quickly.

Thus, in some embodiments, the information management system100automatically applies a default configuration to client computing device102. As one example, when a data agent(s)142is installed on a client computing devices102, the installation script may register the client computing device102with the storage manager140, which in turn applies the default configuration to the new client computing device102. 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 device108, data path information (e.g., a particular media agent144), and the like.

Other types of information management policies148are possible. For instance, the information management policies148can 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 system100. For example, an audit policy may define “sensitive objects” as files or objects that contain particular keywords (e.g. “confidential,” or “privileged”) and/or are associated with particular keywords (e.g., in metadata) or particular flags (e.g., in metadata identifying a document or email as personal, confidential, etc.).

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

In some implementations, the information management policies148may include one or more provisioning policies. A provisioning policy can include a set of preferences, priorities, rules, and/or criteria that specify how clients102(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 devices102(e.g. a number of gigabytes that can be stored monthly, quarterly or annually). The storage manager140or other components may enforce the provisioning policy. For instance, the media agents144may enforce the policy when transferring data to secondary storage devices108. If a client computing device102exceeds a quota, a budget for the client computing device102(or associated department) is adjusted accordingly or an alert may trigger.

While the above types of information management policies148have been described as separate policies, one or more of these can be generally combined into a single information management policy148. 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 policies148may specify:schedules or other timing information, e.g., specifying when and/or how often to perform information management operations;the type of secondary copy116and/or secondary copy format (e.g., snapshot, backup, archive, HSM, etc.);a location or a class or quality of storage for storing secondary copies116(e.g., one or more particular secondary storage devices108);preferences regarding whether and how to encrypt, compress, deduplicate, or otherwise modify or transform secondary copies116;which system components and/or network pathways (e.g., preferred media agents144) should be used to perform secondary storage operations;resource allocation between different computing devices or other system components used in performing information management operations (e.g., bandwidth allocation, available storage capacity, etc.);whether and how to synchronize or otherwise distribute files or other data objects across multiple computing devices or hosted services; andretention information specifying the length of time primary data112and/or secondary copies116should be retained, e.g., in a particular class or tier of storage devices, or within the information management system100.

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:frequency with which primary data112or a secondary copy116of a data object or metadata has been or is predicted to be used, accessed, or modified;time-related factors (e.g., aging information such as time since the creation or modification of a data object);deduplication information (e.g., hashes, data blocks, deduplication block size, deduplication efficiency or other metrics);an estimated or historic usage or cost associated with different components (e.g., with secondary storage devices108);the identity of users, applications110, client computing devices102and/or other computing devices that created, accessed, modified, or otherwise utilized primary data112or secondary copies116;a relative sensitivity (e.g., confidentiality) of a data object, e.g., as determined by its content and/or metadata;the current or historical storage capacity of various storage devices;the current or historical network capacity of network pathways connecting various components within the storage operation cell;access control lists or other security information; andthe 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

FIG. 1Eshows a data flow data diagram depicting performance of storage operations by an embodiment of an information management system100, according to an exemplary data storage policy148A. The information management system100includes a storage manger140, a client computing device102having a file system data agent142A and an email data agent142B residing thereon, a primary storage device104, two media agents144A,144B, and two secondary storage devices108A,108B: a disk library108A and a tape library108B. As shown, the primary storage device104includes primary data112A,112B associated with a file system sub-client and an email sub-client, respectively.

As indicated by the dashed box, the second media agent144B and the tape library108B are “off-site”, and may therefore be remotely located from the other components in the information management system100(e.g., in a different city, office building, etc.). In this manner, information stored on the tape library108B may provide protection in the event of a disaster or other failure.

The file system sub-client and its associated primary data112A in certain embodiments generally comprise information generated by the file system and/or operating system of the client computing device102, 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 data112B, include data generated by an e-mail client application operating on the client computing device102, 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 data112A,112B may or may not be stored contiguously.

The exemplary storage policy148A includes a backup copy rule set160, a disaster recovery copy rule set162, and a compliance copy rule set164. The backup copy rule set160specifies that it is associated with a file system sub-client166and an email sub-client168. Each of these sub-clients166,168are associated with the particular client computing device102. The backup copy rule set160further specifies that the backup operation will be written to the disk library108A, and designates a particular media agent144A to convey the data to the disk library108A. Finally, the backup copy rule set160specifies that backup copies created according to the rule set160are 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 policy148A, and is instead specified by a separate scheduling policy.

The disaster recovery copy rule set162is associated with the same two sub-clients166,168. However, the disaster recovery copy rule set162is associated with the tape library108B, unlike the backup copy rule set160. Moreover, the disaster recovery copy rule set162specifies that a different media agent144B than the media agent144A associated with the backup copy rule set160will be used to convey the data to the tape library108B. As indicated, disaster recovery copies created according to the rule set162will be retained for 60 days, and will be generated on a daily basis. Disaster recovery copies generated according to the disaster recovery copy rule set162can provide protection in the event of a disaster or other data-loss event that would affect the backup copy116A maintained on the disk library108A.

The compliance copy rule set164is only associated with the email sub-client166, and not the file system sub-client168. Compliance copies generated according to the compliance copy rule set164will therefore not include primary data112A from the file system sub-client166. 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 set164is associated with the same tape library108B and media agent144B as the disaster recovery copy rule set162, although a different storage device or media agent could be used in other embodiments. Finally, the compliance copy rule set164specifies that copies generated under the compliance copy rule set164will be retained for 10 years, and will be generated on a quarterly basis.

At step 1, the storage manager140initiates a backup operation according to the backup copy rule set160. For instance, a scheduling service running on the storage manager140accesses scheduling information from the backup copy rule set160or a separate scheduling policy associated with the client computing device102, and initiates a backup copy operation on an hourly basis. Thus, at the scheduled time slot the storage manager140sends instructions to the client computing device102to begin the backup operation.

At step 2, the file system data agent142A and the email data agent142B residing on the client computing device102respond to the instructions received from the storage manager140by accessing and processing the primary data112A,112B involved in the copy operation from the primary storage device104. Because the operation is a backup copy operation, the data agent(s)142A,142B may format the data into a backup format or otherwise process the data.

At step 3, the client computing device102communicates the retrieved, processed data to the first media agent144A, as directed by the storage manager140, according to the backup copy rule set160. In some other embodiments, the information management system100may implement a load-balancing, availability-based, or other appropriate algorithm to select from the available set of media agents144A,144B. Regardless of the manner the media agent144A is selected, the storage manager140may further keep a record in the storage manager database140of the association between the selected media agent144A and the client computing device102and/or between the selected media agent144A and the backup copy116A.

The target media agent144A receives the data from the client computing device102, and at step 4 conveys the data to the disk library108A to create the backup copy116A, again at the direction of the storage manager140and according to the backup copy rule set160. The secondary storage device108A can be selected in other ways. For instance, the media agent144A may have a dedicated association with a particular secondary storage device(s), or the storage manager140or media agent144A may select from a plurality of secondary storage devices, e.g., according to availability, using one of the techniques described in U.S. Pat. No. 7,246,207, which is incorporated by reference herein.

The media agent144A can also update its index153to include data and/or metadata related to the backup copy116A, such as information indicating where the backup copy116A resides on the disk library108A, data and metadata for cache retrieval, etc. After the 30-day retention period expires, the storage manager140instructs the media agent144A to delete the backup copy116A from the disk library108A.

At step 5, the storage manager140initiates the creation of a disaster recovery copy116B according to the disaster recovery copy rule set162. For instance, at step 6, based on instructions received from the storage manager140at step 5, the specified media agent144B retrieves the most recent backup copy116A from the disk library108A.

At step 7, again at the direction of the storage manager140and as specified in the disaster recovery copy rule set162, the media agent144B uses the retrieved data to create a disaster recovery copy116B on the tape library108B. In some cases, the disaster recovery copy116B is a direct, mirror copy of the backup copy116A, and remains in the backup format. In other embodiments, the disaster recovery copy116C may be generated in some other manner, such as by using the primary data112A,112B from the storage device104as source data. The disaster recovery copy operation is initiated once a day and the disaster recovery copies116A are deleted after 60 days.

At step 8, the storage manager140initiates the creation of a compliance copy116C, according to the compliance copy rule set164. For instance, the storage manager140instructs the media agent144B to create the compliance copy116C on the tape library108B at step 9, as specified in the compliance copy rule set164. In the example, the compliance copy116C is generated using the disaster recovery copy116B. In other embodiments, the compliance copy116C is instead generated using either the primary data112B corresponding to the email sub-client or using the backup copy116A from the disk library108A as source data. As specified, compliance copies116C are created quarterly, and are deleted after ten years.

While not shown inFIG. 1E, at some later point in time, a restore operation can be initiated involving one or more of the secondary copies116A,116B,116C. As one example, a user may manually initiate a restore of the backup copy116A by interacting with the user interface158of the storage manager140. The storage manager140then accesses data in its index150(and/or the respective storage policy148A) associated with the selected backup copy116A to identify the appropriate media agent144A and/or secondary storage device116A.

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 agent144A retrieves the data from the disk library108A. For instance, the media agent144A may access its index153to identify a location of the backup copy116A on the disk library108A, or may access location information residing on the disk108A itself.

When the backup copy116A was recently created or accessed, the media agent144A accesses a cached version of the backup copy116A residing in the media agent index153, without having to access the disk library108A for some or all of the data. Once it has retrieved the backup copy116A, the media agent144A communicates the data to the source client computing device102. Upon receipt, the file system data agent142A and the email data agent142B may unpackage (e.g., restore from a backup format to the native application format) the data in the backup copy116A and restore the unpackaged data to the primary storage device104.

Exemplary Secondary Copy Formatting

The formatting and structure of secondary copies116can vary, depending on the embodiment. In some cases, secondary copies116are 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 devices108, e.g., according to resource availability. For example, a single secondary copy116may be written on a chunk-by-chunk basis to a single secondary storage device108or across multiple secondary storage devices108. In some cases, users can select different chunk sizes, e.g., to improve throughput to tape storage devices.

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

The headers can include a variety of information such as file identifier(s), volume(s), offset(s), or other information associated with the payload data items, a chunk sequence number, etc. Importantly, in addition to being stored with the secondary copy116on the secondary storage device108, the chunk headers can also be stored to the index153of the associated media agent(s)144and/or the storage manager index150. This is useful in some cases for providing faster processing of secondary copies116during restores or other operations. In some cases, once a chunk is successfully transferred to a secondary storage device108, the secondary storage device108returns an indication of receipt, e.g., to the media agent144and/or storage manager140, which may update their respective indexes150,153accordingly.

During restore, chunks may be processed (e.g., by the media agent144) 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.

Example Client Computing Environment

FIG. 2is a block diagram illustrating an example of a client computing environment200including a client computing device102and a primary storage device104. As previously described, for example with respect toFIG. 1C, the client computing device102may include one or more applications110and one or more data agents142. At least some of the data agents142may correspond to one or more of the applications110and, as previously described, may facilitate data operations with respect to the corresponding application(s). Further, one or more of the data agents142may facilitate managing and/or interacting with a file system202of the client computing device102. This file system202may include any type of file system that can be used by a client computing device102. For example, the file system202may include a Microsoft Windows file system (e.g., FAT, NTFS, etc.), a Linux based file system, a Unix based file system, an Apple Macintosh file system (e.g., HFS Plus), and the like. In some instances, the client computing device102may include multiple file systems202of the same type or of a different type.

In addition to the previously described systems, the client computing device102may include a filter driver204that can interact with data (e.g., production data) associated with the applications110. For instance, the filter driver204may comprise a file system filter driver, an operating system driver, a filtering program, a data trapping program, an application, a module of one or more of the applications110, an application programming interface (“API”), or other like software module or process that, among other things, monitors and/or intercepts particular application requests targeted at a file system, another file system filter driver, a network attached storage (“NAS”), a storage area network (“SAN”), mass storage and/or other memory or raw data. In some embodiments, the filter driver204may reside in the I/O stack of an application110and may intercept, analyze and/or copy certain data traveling to or from the application110from or to a file system.

In certain embodiments, the filter driver204may intercept data modification operations that include changes, updates and new information (e.g., data writes) with respect to the application(s)110of interest. For example, the filter driver204may locate, monitor and/or process one or more of the following with respect to a particular application110, application type, or group of applications: data management operations (e.g., data write operations, file attribute modifications), logs or journals (e.g., NTFS change journal), configuration files, file settings, control files, other files used by the application110, combinations of the same or the like. In certain embodiments, such data may also be gathered from files across multiple storage systems within the client computing device102. Furthermore, the filter driver204may be configured to monitor changes to particular files, such as files identified as being associated with data of the applications110.

In certain embodiments, multiple filter drivers204may be deployed on a computing system, each filter driver being dedicated to data of a particular application110. In such embodiments, not all information associated with the client computing system102may be captured by the filter drivers204and thus, the impact on system performance may be reduced. In other embodiments, the filter driver204may be suitable for use with multiple application types and/or may be adaptable or configurable for use with multiple applications110. For example, one or more instances of customized or particularizing filtering programs may be instantiated based on application specifics or other needs or preferences.

The filter driver204may include a number of modules or subsystems that can facilitate performing various operations with respect to the applications110and/or file system202. For example, the filter driver204may include a number of modules or subsystems to facilitate encrypting data and/or files. As a second example, the filter driver204may include modules or subsystems to facilitate presenting encrypted files to an authorized user. In certain embodiments, the modules or subsystems of the filter driver204can include one or more of the following: an interface agent220, an encryption module222, a secure file access module224, an encryption rules engine226, a decryption module228, and a file monitor230.

Using the file monitor230, the filter driver204can monitor a user's interaction with a file. This interaction can include accessing the file via the file system202, one or more applications110, one or more data agents142, or through any other method of accessing or interacting with a file. In some cases, the file monitor230may be configured to identify when a file is modified and/or created. Monitoring the creation of a file can include identifying a “new” file operation, a “save as” operation, a “copy” operation, or any other operation that can result in a new file or a new copy of an existing file.

The encryption rules engine226can include any system configured to determine whether a file is to be encrypted. Generally, the file monitor230is configured to trigger the encryption rules engine226determining whether a file is to be encrypted. For example, the encryption rules engine226may determine whether to encrypt a file in response to the file monitor230detecting a write access to the file, or a file creation operation (e.g., a “new” operation, a “save as” operation, etc.) that results in the creation of the file. Alternatively, the encryption rules engine226may determine whether a file is to be encrypted each time the file is accessed regardless of the type of file access. In other cases, the encryption rules engine226may determine whether a file should be encrypted in response to a command received from another system, such as a data agent142or the storage manager140.

Determining whether to encrypt a file can be based on a set of encryption rules. In some instances, these encryption rules may be included with the encryption rules engine226. Alternatively, or in addition, the encryption rules may be stored at an encryption rules repository208that is accessible by the filter driver204and/or the encryption rules engine226of the filter driver204. The encryption rules can include any rule for determining whether a file is to be encrypted. These encryption rules may be based on one or more users and/or pieces of metadata associated with the file.

For example, an encryption rule may be based on one or more of the following: the author of a file, the owner of a file, the editor of a file, the type of file, the location of the file, the name of the file, the age of the file, a tag associated with the file, whether the file and/or a version of the file was previously encrypted, keywords associated with the file name and/or the contents of the file, and the like. Unless stated otherwise, the phrase “a version of the file” as used herein generally refers to the file and/or a copy of the file that includes different content than the file currently being evaluated (e.g., an older copy of the file, a pre-edited version of a file, etc.).

In some cases, the characteristics of a file used to determine whether to encrypt a file may be weighted. For example, the type of the file may be weighted such that it has a greater affect in determining whether to encrypt a file than the author of the file.

Once the encryption rules engine226determines that a file should be encrypted, the encryption module222can encrypt the file using an encryption algorithm. In some cases, the encryption algorithm may be specified as part of an encryption rule. Once the file has been encrypted, the encryption module222may delete any unencrypted copies of the file located on the client computing device102and/or the primary storage device104. Further, in some cases, the encryption module222may cause a cached copy of the file to be locked or inaccessible to prevent access to unencrypted copies or fragments of a file that has been identified for encryption by the encryption rules engine226.

As stated above, the filter driver204may include an interface agent220. The interface agent220may be configured to control how files, or references to files (e.g., file names, file icons, etc.), are displayed to a user. In some cases, the interface agent220can control how files are displayed in a variety of display locations, such as in a window, in a listing of files, on a desktop display, in an application window or viewer, etc.

Further, in some cases, the interface agent220may be configured to present encrypted files as if the files were unencrypted. Further, the interface agent220may be configured to present files differently based on the user accessing the client computing device102as determined by a user identifier and/or authentication information obtained via an authentication system206. For example, an administrator may see the encryption status of a file via an annotation on an icon or a special file extension. However, the interface agent220may cause all files to appear as unencrypted files to a non-administrator user. Further, the interface agent220may cause at least some encrypted files to be hidden from view altogether for a user who does not have authorization to decrypt the hidden encrypted files.

When a user and/or application110attempts to access a file, the secure file access module224can determine whether the file is an encrypted file based on, for example, the file name. If the file is not encrypted, the file access operation is provided to the file system202for processing. If the file is encrypted, the secure file access module224can determine whether to decrypt the file based on, for example, authentication information associated with the user.

Generally, the secure file access module224can access the authentication information that the authentication system206obtained when the user logged in to the client computing device102. Advantageously, in certain embodiments, by using the authentication information provided at login, the request to access a file can be processed without the user being prompted with a request for authentication at the time the file is accessed. Thus, in some cases, the file access request may be processed without the user being made aware of the encryption status of the file.

In cases where the secure file access module224determines that a file is encrypted and that a user and/or application110is authorized to access the file, the secure file access module224can provide the encrypted file to a decryption module228. The decryption module228can decrypt the file and provide the file to the application110for use or presentation to a user. In some cases, as will be described in more detail below, the decryption module228can determine the type of encryption used to encrypt the file and select a corresponding decryption algorithm to decrypt the file. Further, in cases where an asymmetric key was used to encrypt the file, the decryption module228can identify a public key corresponding to the private key used to encrypt the file. The decryption module228can then use the public key to decrypt the file.

As indicated above, the primary storage device104can store the unencrypted files. Further, the primary storage device104can also store encrypted files, which may be encrypted by the encryption module222or otherwise. As illustrated inFIG. 2, the primary storage device104can include an unencrypted files repository210configured to store unencrypted files and an encrypted files repository212configured to store encrypted files.

Although encrypted files and unencrypted files may be stored in different repositories of the primary storage device104, the encrypted and unencrypted files may be presented to a user without differentiating between the encryption status of the files and the storage location of the file in the primary storage device104. Alternatively, the encrypted files may be presented to a user in a separate location of a file storage display and/or with an indication of the encryption status of the file. Further, in some cases, the primary storage device104may be divided into a fewer or greater number of repositories, which may or may not be divided based on the encryption status of files stored by the primary storage device104.

Generally, although not necessarily, a client computing device102includes an authentication system206. This authentication system206can be configured to authenticate a user attempting to use the client computing device102and/or attempting to access files stored on the primary storage device104. Further, in some cases, the authentication system206can provide authentication information to the secure file access module224to facilitate determining whether a user is authorized to access an encrypted file. In certain embodiments, the authentication system206may obtain additional authentication information from a user when the user attempts to access an encrypted file. This information can then be provided to the secure file access module224. In other embodiments, the authentication system206provides previously obtained authentication information to the secure access module224and does not prompt a user for additional information when the user attempts to access an encrypted file.

Example of an Encryption Determination Process

FIG. 3illustrates an example embodiment of an encryption determination process300. The process300can be implemented, at least in part, by any system that can detect when a file is created or modified and can determine whether to encrypt the file based on a set of encryption rules. For example, the process300, in whole or in part, can be implemented by the filter driver204, the file monitor230, the encryption rules engine226, and the encryption module222, to name a few. Although any number of systems, in whole or in part, can implement the process300, to simplify discussion, portions of the process300will be described with reference to particular systems.

The process300begins at block302where, for example, the file monitor230monitors file access operations to detect file write operations. Typically, the file monitor230is monitoring file access operations for files stored at the primary storage device104. However, in some cases, the file monitor230may monitor file access operations for files stored elsewhere, such as on a portable storage device (e.g., a USB key, an external disk drive, etc.). In some cases, the file write operations can include write commands, file create commands, file copy commands, or any commands or operations that can result in a file being modified or created, or that indicate that a file is being modified or created. For example, the file monitor230may detect a “New” command, a “Save” command, a “Save As” command, a “Copy” command, or any operations related to such commands. At decision block304, the file monitor230determines whether a file write, or file creation, operation is detected with respect to a file. If not, the file monitor230continues to monitor operations at the block302.

Generally, the operations monitored are commands received from the applications110and/or the data agents142. However, in some cases, the file monitor230can monitor commands or operations received from any source that can access a file. For example, in some cases, commands may be received from a processor or an application-specific processor (not shown) that is included as part of the client computing device110. As a second example, commands may be received from the storage manager140or a media agent144.

At block306, the encryption rules engine226accesses metadata, or file metadata, associated with the file. Alternatively, the file monitor230may access the metadata. In some cases, some of the metadata may be accessed and/or determined by the file monitor230and some of the metadata may be accessed and/or determined by the encryption rules engine226. The metadata can include any type of data associated with the file, including data associated with users associated with the file. Further, the metadata can include any type of data related to the file that can be the basis, at least in part, of an encryption rule for determining whether to encrypt the file.

For example, the metadata can include: the name of the file, the file type of the file (e.g., a word processing file, a spreadsheet, a PDF file, a CAD file, an audio file, a video file, etc.), an author of the file, users who have authorization to access the file, one or more applications capable of reading or accessing the file (e.g., Microsoft Word, Microsoft Excel, Adobe Acrobat, Corel WinDVD, etc.), the location of the file within a file organization structure, the time the file was created, the time the file was last modified and/or accessed, the size of the file, and the like. In some cases, the metadata can include a designation and/or tag associated with the file. For example, an encryption determination may be made based on whether a user or application designated a file or set of files for encryption, either through explicit designation or by inclusion in a location (e.g., directory) that has been designated for encryption. As a second example, files that are designated for backup or for backup to a particular location or media may be designated for encryption.

The encryption rules engine226accesses one or more encryption rules at block308for determining whether to encrypt the file associated with the file write detected at the decision block304. In some cases, the encryption rules are accessed from the encryption rules repository208. In other cases, the encryption rules are included as part of the filter driver204. Whether included with the filter driver, or stored at the encryption rules repository208, the encryption rules may be provided by the storage manager140, a user (e.g., an administrator), a provider of the filter driver204, or any other user or entity that can provide encryption rules.

As described above, the encryption rules can include any rule for determining whether a file is to be encrypted. Typically, the encryption rules are based on the metadata associated with the file that the encryption rules engine226is analyzing to make an encryption determination. However, in some cases, the encryption rules may be based on alternative or additional factors, such as a user associated with the client computing device102, the role of the client computing device102, a location of the client computing device102, and the like.

At decision block310, the encryption rules engine226determines whether the file metadata, or at least a subset of the metadata, satisfies one or more of the encryption rules. In some cases, decision block310includes determining whether the alternative or additional factors described above satisfy one or more of the encryption rules. If the file metadata does not satisfy any of the encryption rules, the file write, and/or file creation, operation is allowed to proceed at block312. In other words, the operation may be performed as if the filter driver204were not present or as if the blocks302-310were not performed. In some cases, the block312may include storing an unencrypted version of a previously encrypted file if the file previously satisfied an encryption rule, but no longer satisfies an encryption rule. In certain embodiments, the block312can include informing a user that an encryption rule is not satisfied and may present the user with an option to encrypt the file despite the file not satisfying one of the encryption rules.

If the encryption rules engine226determines that the file metadata does satisfy at least one of the encryption rules as the decision block310, the filter driver204locks one or more cache copies of the file at block314. Advantageously, in some embodiments, by locking cache copies of the file, users and/or applications are unable to access unencrypted versions or copies of the file. In some embodiments, the block314is optional.

At block316, the encryption module222encrypts the file. In some cases, the encryption module222uses the same encryption algorithm to encrypt the file regardless of the encryption rule satisfied by the metadata and/or the file to be encrypted. In other cases, the encryption module222selects an encryption algorithm based on the encryption rule satisfied and/or the file to be encrypted. If multiple encryption rules are satisfied, the encryption module222may select the encryption algorithm based on a preference, weighting, ranking, or other factor associated with the satisfied encryption rules. In some embodiments, the block316includes deleting or rendering inaccessible unencrypted versions or copies of the file.

In some cases, the block316can include modifying an extension of the file or appending an addition extension to the file to indicate the encryption status of the file. For example, the encryption module222may change a file extension to .CVX to indicate the file is encrypted. Thus, in some cases, an encrypted PDF file X may be renamed from X.pdf to X.cvx. Alternatively, the encryption module222may append an encryption extension (e.g., .CVX) indicating the encryption status of the file after the file's unencrypted extension. Thus, in some cases, an encrypted PDF file Y may be renamed from Y.pdf to Y.pdf.cvx. The encrypted file may be stored at the location indicated by the command detected at the decision block304. Alternatively, the encrypted file may be stored at an alternate location. This alternative location may be designated for encrypted files and/or may be designated by the encryption rule satisfied by the file.

The encryption module222stores metadata associated with the encryption status of the file at block318. The metadata may be stored with the encrypted file or at another location. For example, the metadata may be stored at the primary storage device104, with the file or in another location, and/or the metadata may be stored at the storage manager140. The metadata can include information related to the encryption of the file. For example, the metadata can include the encryption status of the file, an identification of the encryption rule satisfied, an identification of the encryption algorithm used to encrypt the file, and the like. In some embodiments, the block318is optional.

Example of an Encrypted File Display Process

FIG. 4illustrates an example embodiment of an encrypted file display process400. The process400can be implemented, at least in part, by any system that can cause a reference or link to a file to be presented to a user. Further, the process400can be implemented by any system that can cause the reference or link to the file to be presented as a reference or link to an unencrypted file regardless of the encryption status of the file. For example, the process400, in whole or in part, can be implemented by the filter driver204, the interface agent220, and the secure file access module224, to name a few. Although any number of systems, in whole or in part, can implement the process400, to simplify discussion, portions of the process400will be described with reference to particular systems.

The process400begins at block402where, for example, the interface agent220accesses an encrypted file. In some cases, the interface agent220may receive the encrypted file from the file system202, an application110, the primary storage device104, a cache (not shown), a processor (not shown), or any other source that can provide the encrypted file to the interface agent220. Alternatively, the interface agent220may scan a storage location (e.g., the primary storage device104) to identify encrypted files at the block402. In some embodiments, the process400may occur as part of an encryption process, such as the process300. In such embodiments, the process400, in whole or in part, may occur as part of the block316or subsequent to the block316.

At block404, the interface agent220identifies the file type of a pre-encrypted version or copy of the encrypted file. In other words, the interface agent220identifies the file type of the file (e.g., PDF file, spreadsheet file, word processing file, video file, audio file, image file, etc.) before the file was encrypted. The interface agent220may determine the file type based on a reference to the file. This reference generally refers to what is displayed to the user to identify the file or the existence of the file to the user. For example, the reference can include the name of the file, a file extension of the file, a link to the file, or an image or icon associated with the file, to name a few. Generally, but not necessarily, the file extension of the encrypted file differs from the file extension of the unencrypted file. Further, in some cases, the interface agent220may identify the file type based on metadata associated with the pre-encrypted file and/or the encrypted file.

The interface agent220identifies one or more application programs associated with the pre-encrypted version of the file at block406. By identifying the application programs associated with the pre-encrypted version of the file, the interface agent220can, in some cases, cause the encrypted file to be associated with the same application programs. Further, the interface agent220can, in some cases, cause a reference to the encrypted file to include an icon or other identifying information that informs the user that the encrypted file is associated with an application that typically can access the non-encrypted version of the file.

With many proprietary file formats or types, there may exist only a single application associated with the file. However, in some cases (e.g., PDF files), multiple applications may be capable of accessing a particular file type and thus multiple applications may be associated with the pre-encrypted version of the file. In some cases, there may not exist an application associated with the file. For example, the application that created the file may have been removed from the client computing device102, or the file may have been created on another computing device and then provided to the client computing device102. In such cases, the interface agent220may still determine an application capable of accessing the pre-encrypted file based on metadata associated with the file and/or based on information available on a network. In other cases, the interface agent220may identify the file as being associated with an unknown file type. In some embodiments, the block406is optional.

At block408, the interface agent220displays, or causes a display screen to display, a reference to the encrypted file that appears as if it were the reference to the unencrypted file. In other words, the reference to the encrypted file mimics, at least in part, a reference to the unencrypted file. Thus, in some cases, the reference to the encrypted file may have the same file name, file extension, icon or other file reference characteristic as a reference to the unencrypted file. Further, as described in more detail below, at least some of the metadata associated with the encrypted file may match at least some of the metadata associated with the unencrypted file thereby, in some cases, preventing a user and/or application from using the metadata to determine whether a file is encrypted.

Advantageously, in some embodiments, by displaying the reference to the encrypted file as if it were a reference to the unencrypted file, the file can be organized by the file system202and identified by a user with the same ease as if the file were not encrypted. In some cases, the user may not know whether the file is encrypted and can organize and access the file without knowing the encryption status of the file. Further, in some instances, the reference to the encrypted file may be based on a reference to the unencrypted file, but may or may not mimic the reference to the unencrypted file.

Moreover, the reference to the encrypted file may be similar, but not identical to a reference to the unencrypted file. For example, the reference to the encrypted file may include an annotation, such as a mark on the icon of the encrypted file that indicates the encryption status of the file. This annotation of the icon can inform the user that the file is an encrypted version of the unencrypted file. In other cases, the icon of the encrypted file may be identical to the icon of the unencrypted file, but the file extension may differ. Advantageously, in some embodiments, by non-identically mimicking the reference to the unencrypted file, encrypted and unencrypted files can be organized together, but still be distinguishable. Further, the file types of the encrypted files can be identified as easily as if the files were unencrypted files while maintaining the ability for the user to distinguish between encrypted and unencrypted files by, for example, glancing at a reference to the file (e.g., the file icon or file name).

As previously described, in some implementations, the file extension of the encrypted file may differ from the file extension of the unencrypted file. For example, a .CVX extension may be appended to an existing file extension. In some such cases, the added or modified extension of the encrypted file may be hidden from view by default thereby, in some cases, displaying the original file extension or no file extension to the user.

Example of an Encrypted File Access Process

FIG. 5illustrates an example embodiment of an encrypted file access process500. The process500can be implemented, at least in part, by any system that can provide a user and/or application with access to a file that has been encrypted using an encryption process, such as the process300. For example, the process500, in whole or in part, can be implemented by the filter driver204, the interface agent220, the secure file access module224, the decryption module228, and the authentication system206, to name a few. Although any number of systems, in whole or in part, can implement the process500, to simplify discussion, portions of the process500will be described with reference to particular systems.

The process500begins at block502where, for example, the authentication system206authenticates a user. The block502may be performed in response to the user attempting to access the client computing device102(e.g., at login), access an encrypted file, or in some cases, in response to both an attempt to access the client computing device102and an attempt to access an encrypted file. In certain embodiments, the block502is optional.

At block504, the secure file access module224receives a request to access a file stored in the primary storage device104. Generally, the request is sent by a user of the client computing device102or an application110to the file system202and is intercepted by the filter driver204, which provides the request to the secure access module224. However, in some cases, the request to access the file may be addressed to the filter driver204. In some embodiments, the request to access the file may be received from a remote system. For example, the request to access the file may be received from another client computing device, from a mobile device, from a server, or from any other computing device that can request file access on behalf of a user or application.

The secure file access module224determines the encryption status of the file at block506. Determining the encryption status of the file can include examining the file extension of the file, the icon associated with the file, metadata associated with the file, the storage location of the file, a table that identifies encrypted files and/or the encryption status of files, and any other data or source that can be used to determine the encryption status of the file. At decision block508, the secure file access module224determines whether the encryption status of the file indicates that the file is encrypted. If not, the secure file access module224at block510grants file access to the user, or application110, that provided the request to access the file at the block504. In some cases, granting access to the file involves the secure file access module224allowing the file access request to proceed. In other words, the file access request of the block504may be performed as if the filter driver204were not present.

In some embodiments, the block510may include additional operations. For example, the block510may include logging access to the file or notifying a user (e.g., an administrator) that the file was accessed.

If the secure file access module224determines that the file is encrypted at decision block508, the authentication system206authenticates the user at block512. Authenticating the user can include determining whether the user is authorized to access the encrypted file. In some embodiments, the secure file access module uses authentication information obtained at the block502to identify the user. The authentication information can then be used to determine whether the user is authorized to access the file without obtaining additional information from the user. Advantageously, in some cases, by using information obtained at the block502in place of requesting authentication information at the block512, a user can access a file without being aware of whether the file is encrypted.

In some cases, the secure file access module224can determine the files the user is authorized to access, encrypted or not, when the user is authenticated at the block502. In such cases, the block512is unnecessary. Thus, in some embodiments, the block512is optional. In other embodiments, the block502may be optional, and the secure file access module may determine whether the user is authorized to access a file by, in part, using the authentication system206to authenticate the user at the block512.

In certain embodiments, the secure file access module224may access metadata and/or access control information associated with a user to determine whether the user is authorized to access the encrypted file. This metadata and/or access control information may be stored at the primary storage device104, on a device on the network, in a secure storage location associated with the client computing device102, on a smartcard or other personal security device associated with the user, or at any other location that can be used to store authorization information associated with a user.

At block514, assuming that it is determined that the user is authorized to access the encrypted file, the decryption module228decrypts the encrypted file. Decrypting the file can include identifying the type of encryption used to encrypt the file and determining a corresponding decryption algorithm. The decryption module228can determine the type of encryption used based on a variety of factors including, for example, metadata associated with the file, metadata associated with the user, a source of the file, a type of the file, a header associated with the file, a storage location of the file, etc. In some cases, decrypting the file may include identifying a public key to decrypt the file when the file was encrypted with a corresponding private key.

If the user was not successfully authenticated, or was not authorized to access the file, the request to access the file is rejected. Rejecting access to the file can include logging the attempted file access and/or alerting another user (e.g., an administrator) regarding the attempted file access.

At block516, the secure file access module224provides the user and/or application110with access to the decrypted file. In some cases, providing access to the decrypted file can include sending the decrypted file over a network to a remote device. Assuming the file was not modified, the filter driver may delete the decrypted file upon detecting the user and/or application110has finished accessing the file (e.g., upon detection of a “file close” command). If the file is modified, the process300may in some cases be initiated.

Example of a File Backup Process

FIG. 6illustrates an example embodiment of a file backup process600. The process600can be implemented, at least in part, by any system that can backup a file to a secondary storage device108. For example, the process600, in whole or in part, can be implemented by the storage manager140, a data agent142, a secondary storage computing device106, and a media agent144, to name a few. Although any number of systems, in whole or in part, can implement the process600, to simplify discussion, portions of the process600will be described with reference to particular systems.

The process600begins at block602where, for example, a data agent142associated with an application110identifies a file accessible by the application110for backup on a secondary storage device108. In some cases, the data agent142performs the block602in accordance with a backup policy provided or established by the storage manager140. Alternatively, the storage manager140may perform the block602. In another alternative, the storage manager140may initiate the process600by providing a backup command to the data agent142, which may or may not identify the file for backup. In other cases, a user may identify the file for backup on the secondary storage device108. The process600may be initiated as part of a scheduled or automatic backup process, or may be initiated manually (e.g., in response to a user command).

At block604, the data agent142accesses the file identified at the block602from the primary storage104. The data agent142can provide the file to a secondary storage computing device106associated with a media agent144. Alternatively, the data agent142may provide the file to the storage manager140, which can then provide the file to the secondary storage computing device106. In some embodiments, the data agent142makes the file available to the secondary storage computing device106. The media agent144of the secondary storage computing device106can then access the client computing device102to obtain the file. Generally, regardless of how the file is provided, providing the file to the secondary storage computing device106involves providing a copy of the file to the secondary storage computing device106. Thus, the copy of the file may remain on the primary storage device104.

However, in some cases, providing the file to the secondary storage computing device106involves providing the file itself to the secondary storage computing device106. Thus, in some cases, a copy of the file may no longer exist on the primary storage device104after the backup process is complete. For example, during an archiving process, the file or a copy of the file may be provided to the secondary storage computing device106and may be removed from the primary storage device104. When the file is restored from secondary storage, the file may be decrypted and stored on the primary storage device104as described in more detail below. However, typically, at least a copy of the file will exist on both the primary storage device104and a secondary storage device108during performance of and/or subsequent to completion of the process600. In some cases, an archived copy of the file may remain on the primary storage device104.

The media agent144determines at decision block606whether the file is encrypted. This determination may be based on one or more factors including the file itself and/or metadata associated with the file. For example, the media agent144may examine the file name, the data stored in the file, a tag associated with the file, or any other information that can be used to determine the encryption status of a file. In some cases, the encryption status of the file is provided to the media agent144by another system (e.g., the data agent142or the storage manager140).

In addition to determining whether the file is encrypted, the media agent144, at decision block606, may in some cases identify the system that encrypted the file. For example, the media agent144may determine whether the file was encrypted by the client computing device102(e.g., by the encryption module222), by another computing device included within the information management system100, or by a computing system that is external to the information management system100. In some embodiments, the media agent144may treat files that were encrypted by particular computing systems, or files that were not encrypted by particular computer systems as unencrypted files with respect to the process600. In other words, in some cases, the media agent144may re-encrypt, or encrypt a second time, or cause files to be re-encrypted that are already encrypted based on the computing system that initially encrypted the file.

If the media agent144determines at the decision block606that the file is encrypted, the media agent144stores the file on a secondary storage device108without performing an encryption process at block608. If multiple secondary storage devices108exist, the media agent144may store the file on the secondary storage device108specified by the storage manager140. Alternatively, the media agent144selects the secondary storage device108to store the file based on one or more storage device selection rules. These rules may be based on the type of file, the source of the file, a user associated with the file, a data agent associated with the file, or any other information that can be used to determine the location or the device to backup a file.

After identifying the secondary storage device108to store the file, or secondary or backup copy of the file, the media agent144may identify the secondary storage device108to the storage manager140. The storage manager140may associate the identity of the secondary storage device108along with the identity of the file in a repository (e.g., the management database146). In addition, or alternatively, the media agent144may associate the identity of the secondary storage device108along with the identity of the file in a repository (e.g., the media agent database152. Further, one or more of the storage manager140and the media agent144may store at the repository information relating to the encryption algorithm used to encrypt the file. For example, one or both systems may store the identity of the algorithm used to encrypt the file, the identity of an algorithm capable of decrypting the file, the identity of the system that encrypted the file, and the like.

If the media agent144determines at the decision block606that the file is not encrypted or, in some cases, should be encrypted a second time, the media agent144encrypts the file, or causes the file to be encrypted, at block610. In some cases, the media agent144may use the same encryption algorithm regardless of the file to be encrypted. In other cases, the media agent144may select an encryption algorithm based on the file (e.g., the name of the file, the size of the file, the type of file, the owner of the file, etc.), the secondary storage device108where the file is to be stored, the client computing device102that provided the file, or any other factor that can be used to determine the encryption algorithm to use to encrypt the file. In yet other cases, the encryption algorithm may be selected by the storage manager140.

At block612, the media agent144stores the encrypted file on a secondary storage device108. In some embodiments, the block612can include one or more of the embodiments described above with respect to the block608. For example, in some cases, the media agent144may select the secondary storage device108based on one or more storage device selection rules. As a second example, the media agent144may store with the file the identity of the encryption algorithm used to encrypt the file. In addition, or alternatively, the media agent144may store the identity of the encryption algorithm used to encrypt the file along with the storage location of the file in a table at the media agent database152and/or at the storage manager140. In some cases, the storage location of the file may be stored at the client computing device102.

In some embodiments, a copy of the file may be stored at the secondary storage computing device106(e.g., as part of a cache) as part of the block608and/or the block612. The copy of the file may be stored for a specific period of time or until evicted, which, for example, may occur as part of a cache maintenance process or to make room in the cache for additional files.

Advantageously, in certain embodiments, the process600may be used to perform a selective encryption backup process. In some cases, encrypting only unencrypted files during a backup process, time and computing resources can be saved during the backup process. Alternatively, in some cases, the process600can be used to encrypt all files regardless of encryption status. By encrypting all files regardless of encryption status during a backup process, the process600can be used to ensure consistent encryption across files of a backup.

Example of a File Restoration Process

FIG. 7illustrates an example embodiment of a file restoration process700. The process700can be implemented, at least in part, by any system that can restore a file from a secondary storage device108to a recipient system (e.g., the client computing device102). For example, the process700, in whole or in part, can be implemented by the storage manager140, a secondary storage computing device106, and a media agent144, to name a few. Although any number of systems, in whole or in part, can implement the process700, to simplify discussion, portions of the process700will be described with reference to particular systems.

The process700begins at block702where, for example, a storage manager140identifies a file to be restored from a secondary storage device108by a media agent144. The file may be identified as part of a restore command received from the storage manager140at a secondary storage computing device106. In some cases, the restore command is sent to a particular secondary storage computing device106based on the file to be restored. The storage manager140can determine which secondary storage computing device106to send the restore command based on information stored at the storage manager140, such as a table of file locations. In some cases, the process700may be performed as part of a system or storage device restore process. In other cases, the process700may be initiated by a client computing device102. For example, the client computing device102may identify the file to be restored at the block702or may send the restore command to the secondary storage computing device106and/or media agent144.

At block704, the media agent144identifies a secondary storage device108that includes a copy of the file identified at the block702. The secondary storage device108may be identified based on the restore command that may be received as part of the block702. Alternatively, the secondary storage device108may be identified based on the file to be restored and/or based on a storage location table included as part of the media agent database152that identifies the location of stored files. The identified storage location may include the secondary storage device108from a set of secondary storage devices and, in some cases, may include the location within the identified secondary storage device108that has the copy of file. In some embodiments, the block704is optional. For example, in some cases, the media agent144has access to a single secondary storage device108.

At block706, the media agent144retrieves the file from the secondary storage device108. Further, the media agent144accesses metadata associated with the file at block708. The metadata may include the file name, the file extension, or additional information stored with the file or at a table with an entry for the file, such as a table at the media agent database152.

Based, at least in part, on the metadata accessed at the block708, the media agent144determines at decision block710whether the media agent144encrypted the file. In some embodiments, the media agent144determines whether any media agent included in a secondary storage device encrypted the file. Further, in some cases the decision block710can include determining whether any media agent associated with an information management system100of an organization encrypted the file. In other words, in some cases, the decision block710can include determining whether the file was encrypted as part of a storage operation associated with secondary storage or with primary storage, or whether the encryption occurred at a system external to the information management system100as may occur when a user or application receives an encrypted file from a third-party user or system.

If the media agent144determines that it encrypted the file at the decision block710, the media agent144at block712decrypts the file retrieved at the block706using a decryption algorithm associated with the media agent144. In cases where the media agent144may have used one of several encryption algorithms to encrypt the file, the media agent144may identify the decryption algorithm based on the metadata accessed at the block708. Alternatively, the decryption algorithm may be identified as part of the restore command or included with the identification of the file to restore at the block702.

As previously described, in some cases the file may have been encrypted by other systems within the secondary storage subsystem118, such as by other media agents144or secondary storage computing devices106. In such cases, the media agent144may determine the decryption algorithm based on the device that encrypted the file or by communicating with the device that encrypted the file, such as by accessing metadata stored at the device that encrypted the file.

Once the media agent144has decrypted the file, the secondary storage computing device106provides a recipient system with access to the unencrypted file at block714. The recipient system may be the system that requested the file (e.g., the client computing device102), a mobile device in communication with a computing system in the primary storage subsystem117of the information management system100(e.g., a client computing device102or a server (not shown)), the storage manager140, a system identified by the storage manager140, or any other system that may be authorized to access the decrypted file. Further, providing access to the decrypted file can include sending the decrypted file to the recipient system, sending the file to another system (e.g., the storage manager140) to provide to the recipient system, or enabling the recipient system to access the secondary storage computing device106to obtain the decrypted file. Moreover, in some cases, providing access to the decrypted file can include providing one or more data agents142at the recipient system with access to the decrypted file.

If the media agent144determines that it did not encrypt the file at the decision block710, the media agent144at block716identifies the encryption algorithm used by the encrypting system to encrypt the file. The media agent144may identify the encryption algorithm based on the file, metadata associated with the file, information provided by the storage manager140, information provided by the recipient system, information included in the restore command, or any other data that can be used to identify the encryption algorithm. In some cases, the encryption information may include a key, such as a public key, for decrypting the file.

At block718, the media agent144decrypts the file using a decryption algorithm associated with the encryption algorithm identified at the block716. In some cases, the media agent144may use a key provided and/or identified at the block716to decrypt the file. After the file is decrypted, the secondary storage computing device106provides a recipient system with access to the unencrypted file at block714as previously described.

In some embodiments, the blocks716,718, and714may be optional. For example, if the media agent144determines that it did not encrypt the file at the decision block710, it may send the encrypted file to the recipient system without decrypting the file. In such cases, the recipient system (e.g., client computing device102) may decrypt the file or provide the file to another system for decryption.

Second Example of a File Restoration Process

FIG. 8illustrates a second example embodiment of a file restoration process800. The process800can be implemented, at least in part, by any system that can restore a file from a secondary storage device108to a recipient system (e.g., the client computing device102). For example, the process800, in whole or in part, can be implemented by the storage manager140, a secondary storage computing device106, and a media agent144, to name a few. Although any number of systems, in whole or in part, can implement the process800, to simplify discussion, portions of the process800will be described with reference to particular systems.

The process800begins at block802where, for example, a storage manager140identifies a file to be restored from a secondary storage device108by a media agent144. The media agent144identifies at block804a secondary storage device108that includes a copy of the file to be restored. In some embodiments, the blocks802and804can include one or more of the embodiments described above with respect to the blocks702and704respectively.

At block806, the media agent144retrieves the file from the secondary storage device108identified at the block804. In some embodiments, the block806can include one or more of the embodiments described above with respect to the block706. Further, in some cases, the block806can include accessing metadata associated with the file. In such cases, the block806can include one or more of the embodiments described above with respect to the block708.

At decision block808, the media agent144determines whether the file is encrypted. The media agent144may make this determination based, at least in part, on metadata associated with the file. Alternatively, or in addition, the media agent144may determine whether the file is encrypted by analyzing the file itself. In some embodiments, the decision block808may be optional. For example, if every system capable of storing a file at a secondary storage device108is configured to encrypt each file before storing the file, then the decision block808may be optional. In some embodiments, the decision block808can include one or more of the embodiments described above with respect to the decision block710.

If the media agent144determines at the decision block808that the file is not encrypted, the secondary storage computing device106provides a recipient system with access to the file at block810. Once the recipient system has received the file, the recipient system can present it to a user or provide an application with access to the file via, for example, the interface agent220, the secure file access module224, or a data agent142. In some embodiments, the block810can include one or more of the embodiments described above with respect to the block714.

If the media agent144determines at the decision block808that the file is encrypted, the media agent144determines whether the file mimics an unencrypted file at decision block812. The determination of the decision block812is based on an unencrypted file of the same type as the decrypted version of the file retrieved at the block806. The media agent144may make the determination at the decision block812based, at least in part, on metadata associated with the file and/or the file itself. In some embodiments, the decision block812may be optional. For example, if every system capable of storing a file at a secondary storage device108is configured to configure each encrypted file to mimic an unencrypted file before storing the file, then the decision block812may be optional.

As previously described with respect to the block408, an encrypted file that mimics an unencrypted file can include a reference to the encrypted file that shares some or all of the display characteristics of a reference to an unencrypted file. For example, the reference to the encrypted file may include the same extension and/or the same icon as a reference to the unencrypted file. In some cases, at least some of the metadata associated with the encrypted file may be the same as the metadata associated with an unencrypted copy of the file. For example, the metadata associated with the encrypted file may identify one or more applications that can access the file as if it were unencrypted regardless of whether the one or more applications can access the file in its encrypted form. Thus, in some cases, a user accessing the metadata for the encrypted file may, in some cases, not be able to identify the file as an encrypted file. Further, in some instances, at least some applications may not be able to identify whether the file is encrypted based on the metadata associated with the file.

If at the decision block812the media agent144determines that the file does not mimic an unencrypted file, the media agent144modifies the encrypted file to mimic an unencrypted file at the block814. Generally, the modification of the block814does not include decrypting the file. Thus, the modified file remains an encrypted file. Modifying the encrypted file may include modifying one or more of the factors described above with respect to the decision block812in determining whether the file mimics an unencrypted file. For example, modifying the encrypted file can include changing the icon used to display a reference to the encrypted file to the user to match the icon used to display a reference to the unencrypted file to the user. As previously described, in some cases, the icon may be annotated. Further, as a second example, modifying the encrypted file can include changing a the file name and/or file extension of the encrypted file to match the file name and/or file extension of an unencrypted version of the file. In other cases, changing the file name may include hiding a portion of the file name and/or file extension so that it is not displayed to a user.

Once the encrypted file, or a reference to the encrypted file, has been modified at the block814, or if at the decision block812the media agent144determines that the file mimics an unencrypted file, the secondary storage computing device106provides a recipient system with access to the file at block810as previously described. The recipient system (e.g., the client computing device102) using, for example, the decryption module228can decrypt the file for presentation to a user or for provisioning to an application. In some cases, the decryption of the file may occur upon the recipient system obtaining access to the file. In other cases, the decryption of the file may occur at a later time. In either case, the file may be stored at the primary storage device104upon the recipient system receiving access to the file.

In some cases, as has been described, the process800is a multi-tier file restoration process. In such cases, a first portion of the restoration process is performed by one or more systems within the secondary storage subsystem118of the information management system100and a second portion of the file restoration process being performed by one or more systems within the primary storage subsystem117of the information management system100.

Further, in some embodiments, the recipient system may use the process500to provide a user and/or application with access to the file. As previously described, in some embodiments, the media agent144may decrypt the file at the block814and can provide the recipient system with access to the decrypted file.

Second Example Client Computing Environment

FIG. 9is a block diagram illustrating a second example of a client computing environment900including a client computing device950and a primary storage device960. The client computing device950and the primary storage device960can be included as part of the information management system100previously described above with respect toFIGS. 1A-1E. Further, the client computing device950and the primary storage device may be included in the primary storage subsystem117. Moreover, in certain embodiments, the client computing device950can include one or more of the embodiments described with respect to the client computing device102. Likewise, the primary storage device960can include one or more of the embodiments described with respect to the primary storage device104.

The client computing device950may include a number of systems and subsystems and be capable of executing a number of different types of software. For instance, the client computing device950may include one or more applications954, a file system902, one or more data agents952, an authentication system906, and an encryption rules repository908. Further, at least one of the data agents952may be a file system data agent904. Although a single file system902and a single file system data agent904are illustrated inFIG. 9, in some embodiments, the client computing device950may include multiple file systems and/or multiple file system data agents. The file system902can include any type of file system. For example, the file system902may include a Microsoft Windows based file system or a Linux based file system. Furthermore, in some embodiments, the file system902may include one or more of the embodiments previously described with respect to the file system202.

The applications954can include any type of application. Further, the applications954can include one or more embodiments previously described with respect to the applications110. Some or all of the applications may be associated with one or more data agents952. As previously described, a data agent may assist with the performance of information management operations based on the type of data that is being accessed and/or protected, at a client-specific and/or application-specific level. Further, at least some of the data agents952may include one or more of the embodiments previously described with respect to the data agents142.

As with the client computing device102, the client computing device950may include an authentication system906. The authentication system906may include any system configured to authenticate a user attempting to use the client computing device950and/or attempting to access files stored on the primary storage device960, or store elsewhere. Further, the authentication system906may include one or more of the embodiments previously described with respect to the authentication system206.

The file system data agent904can include a data agent that facilitates the file system902managing data processed or organized by the file system902. For example, as previously described, the file system data agent may be involved in handling data files and/or system files, and may facilitate backing up the file system902of the client computing device950. Backing up the file system902may include backing up files stored at the primary storage device960. In certain embodiments, the file system data agent904can perform one or more processes associated with the filter driver204. Thus, in some embodiments, the file system data agent904and/or its subsystems can include one or more of the embodiments described with respect to the filter driver204and/or it subsystems.

The primary storage device960can include any storage device for storing primary data. For example, the primary storage device960may be a hard drive, a solid state drive, memory, flash, etc. Although illustrated as a separate system, the primary storage device960may be included as part of the client computing device950. Further, the primary storage device960may include one or more of the embodiments described with respect to the primary storage device104. As previously described with respect toFIG. 2, the primary storage device may include a number of repositories to facilitate storing and/or organizing data stored by the primary storage device. For instance, the primary storage device960may include a repository910for storing unencrypted files and a repository912for storing encrypted files. In some embodiments, the primary storage device960may be organized into a lesser number or a greater number of repositories and/or partitions.

Each data agent may include a number of systems or subsystems that facilitate the data agent processing data for a corresponding application or system. For instance, the file system data agent904may include an interface agent920, an encryption module922, a secure file access module924, an encryption rules engine926, a decryption module928, and a file monitor930. In some embodiments, the file system data agent904may include fewer or additional subsystems. For instance, the encryption module922and the decryption module928may be part of a single subsystem. As a second example, the secure file access module924may be optional because, for example, a separate system may handle secure file access.

The interface agent920may be configured to control how files, or references to files (e.g., file names, file icons, etc.), are displayed to a user. Controlling how files are displayed can include controlling whether a file reference to an encrypted files is displayed as a file reference to an unencrypted file or as an annotated version of a reference to an unencrypted file. For instance, a file icon for an encrypted file may be the same as for an unencrypted file. Alternatively, the file icon may include an asterisk to indicate that it represents an encrypted file. In some embodiments, the interface agent920can include one or more of the embodiments described with respect to the interface agent220.

In some cases, the file system data agent904may use an encryption rules engine926, which can access encryption rules from the encryption rules repository908, to determine whether a file is to be encrypted. If the encryption rules engine926determines that a file should be encrypted, the encryption module922can perform encryption of the file and, in some cases, of the encryption key used to encrypt the file. The encryption module922can include any encryption engine that can encrypt a file using one or more encryption algorithms. Further, the encryption module922can be used to encrypt encryption keys. In some embodiments, the encryption rules engine926can include one or more of the embodiments described with respect to the encryption rules engine226. Similarly, in some cases, the encryption module922can include one or more of the embodiments previously described with respect to the encryption module222.

To decrypt files, the file system data agent904can use the decryption module928, which can include any decryption engine that can decrypt a file using one or more decryption algorithms. Further, the decryption module928can be used to decrypt encrypted keys. In some cases, the decryption module928can include one or more of the embodiments previously described with respect to the decryption module228.

The secure file access module924can determine the encryption status of a file and can manage the decryption and presentation of encrypted files to users who are authorized to access the file. Further, the secure file access module924can manage access by applications and/or computing systems attempting to access the file. In some embodiments, the file access module924can include one or more of the embodiments previously described with respect to the secure file access module224.

In some embodiments, the decision of whether to encrypt a file at the primary storage device may be based on whether the file has been modified. Further, the decision of whether to decrypt a file may be based on whether a file has been selected for backup to a secondary storage device106, or whether a user or application desires to access the file. The file monitor930can include any system that can monitor activity with respect to the file to facilitate determining whether the file needs encrypting or decrypting. This determination may be made based, at least in part, on rules stored at the encryption rules repository908and/or commands received from a user, application, and/or storage manager140. In some embodiments, the file monitor930can include one or more of the embodiments described with respect to the file monitor230.

Example User Key Encryption Process

FIG. 10Aillustrates an example embodiment of a user key encryption process1000. The process1000can be implemented, at least in part, by any system that can encrypt a private key from an asymmetric key pair (e.g., a private/public key pair). For example, the process1000, in whole or in part, can be implemented by the filter driver204, the file system data agent904, the authentication system906, the encryption rules engine926, and the encryption module922, to name a few. Although any number of systems, in whole or in part, can implement the process1000, to simplify discussion, portions of the process1000will be described with reference to particular systems.

In some embodiments, the process1000may be combined and/or integrated with a process for encrypting a file for storage on a primary storage device, such as the process1050, which is described below with respect toFIG. 10B. In some cases, the process1000may be performed at a time period that is earlier than a time period during which the process1050may be performed. In other cases, the process1000and the process1050may be performed together as part of a single process. In some cases, the process1000may be performed multiple times for a user. For example, a user or system may have different asymmetric key pairs for use with different sets of files.

Further, in some cases, the process1050may be performed a number of times as a file is encrypted and decrypted over the lifetime of the file, while the process1000may be performed once or some number of times fewer than the process1050. For instance, the process1000may be used to obtain an encrypted copy of a user private key. Once the encrypted user private key is obtained, it may be unnecessary to perform the process1000again for that user. However, the process1050may be performed multiple times as a file may be encrypted and decrypted a number of times.

The process1000begins at block1002where, for example, the encryption module922obtains access to an asymmetric key pair for each user who is authorized to access a set of files at, or stored on, a primary storage960. The set of files may include any number of files including a single file. Determining the users who are authorized to access the set of files may be based on metadata associated with the files and/or the user. Alternatively, or in addition, determining the users who are authorized to access the set of files may be based on identifying the users who are authorized to access the client computing device950or who have an account with the client computing device950. Thus, in some cases, the block1002may identify users who are authorized to access the client computing device950and/or the primary storage960instead of the users who are authorized to access the set of files.

In some cases, only a single user may be authorized to access the set of files (e.g., the file author or owner for each of the files, or for a directory including the files). In other cases, a number of users may be authorized to access the set of files. The asymmetric key pair for each user may include a public key and a private key and may be generated based on any type of asymmetric key algorithm. For example, the asymmetric key pair may be generated using RSA.

The asymmetric key pairs may be obtained by accessing a key repository and/or by accessing the encryption rules repository908. Alternatively, the asymmetric key pairs may be obtained from the storage manager140. As yet another alternative, the asymmetric key pairs may be generated by the encryption module922. An asymmetric key pair may be associated with a user regardless of the computing device or primary storage that the user accesses. In other cases, the asymmetric key pair may be specific to a user and a computing device and/or primary storage accessed by the user.

At block1004, the encryption module922obtains a passphrase for each of the users. The passphrase may be a password, such as the password used by the user to login or to access the client computing device950, or a password used to access a network used to communicate with systems of the primary storage subsystem117. In such cases, the passphrase may be obtained by the authentication system906. Often, the passphrase is unique to the user. However, in some cases, the passphrase may not be unique. In some embodiments, the passphrase of a user may be combined with information unique to a user to ensure that the passphrase obtained at the block1004is unique. For instance, the passphrase may include a combination of a user's password and a randomly, or pseudo-randomly, generated number assigned to the user that is unique to the user.

At block1006, the encryption module922hashes each passphrase. Hashing the passphrase may include performing a hashing algorithm multiple times (e.g., 512 times, a thousand times, a million times, etc.) with each subsequent performance of the hashing algorithm using the result of the prior performance of the hashing algorithm as the input to be hashed. In some cases, the hashing may be performed a threshold number of times. The threshold may be selected based on a security level of the set of files. Advantageously, in certain embodiments, by hashing the passphrase multiple times, the probability that a malicious user is able to determine the passphrase based on the hashed passphrase is reduced. The encryption module922may use any type of cryptographic hash function. For example, the hash function can be a SHA-512, MD6, or BLAKE-512 hash function. In some cases, the encryption module922may pad the passphrase with additional data to ensure the passphrase is of a particular length.

At block1008, the encryption module922encrypts, for each user, one of the keys from the asymmetric key pair (e.g., the private key) associated with the user using the hashed passphrase obtained at the block1006. In some embodiments, the blocks1002-1008are optional. For example, the data encryption key used to encrypt the file may be secured using only keys associated with the client computing device950, as described with respect to the blocks1010-1014.

At block1010, the encryption module922obtains access to an asymmetric key pair for the client computing device950. The asymmetric key pair may include a public key and a private key and, as with the asymmetric key pairs of the block1002, may be generated based on any type of asymmetric key algorithm. For example, the asymmetric keys may be generated using an RSA algorithm. Further, as with the user asymmetric key pairs, the asymmetric key pair of the client computing device950may be obtained by accessing a key repository and/or by accessing the encryption rules repository908. Alternatively, the asymmetric key pair may be obtained from the storage manager140. Further, in some cases, the asymmetric key pair may be generated by the encryption module922.

At block1012, the file system data agent904provides one of the keys from the asymmetric key pair (e.g., the private key) associated with the client computing device950obtained at the block1010to the storage manager140for encryption. In some embodiments, the block1012can include providing an identity of the client computing system950to the storage manager140.

Upon receiving the private key, the storage manager140can access a passphrase associated with the client computing device950. In some cases, the passphrase may be hashed, for example, by the storage manager140. Further, the passphrase and/or the hashed version of the passphrase may be used to encrypt a copy of the private key. Thus, in some cases, the storage manager140may perform similar operations on the private key, provided to the storage manager at block1012, as described above with respect to the blocks1006and1008.

In some cases, the passphrase may be accessed from a repository, which may be included with the storage manager140or may be separate, but accessible by the storage manager140over, for example, a network. Alternatively, or in addition, the storage manager140may generate the passphrase for the client computing device950. Moreover, in some cases, the passphrase is generated and used by computing systems without a user accessing the passphrase. Thus, in such embodiments, the passphrase may be automatically generated without user action. In some cases, the passphrase may include symbols and/or data that may be unreadable by a user or not alphanumeric. Further, in certain embodiments, the storage manager140may identify the client computing device950as available or accessible as opposed to lost or stolen. In some cases, marking the client computing device950as available, or not lost, may include marking the passphrase for the client computing device950as live or in-use.

At block1014, the file system data agent904receives an encrypted copy of the private key associated with the client computing device950from the storage manager140. In some embodiments, the blocks1010-1014may be optional. For example, in some cases, users may be associated with asymmetric key pairs for encrypting files at the primary storage960, but the client computing device950may, in some cases, not be associated with its own asymmetric key pair.

At block1016, the file system data agent904stores the encrypted user private keys (obtained at the block1008) and the encrypted private key associated with the client computing device960(obtained at the block1014). In cases where the block1008or the block1014is optional, the block1016may store the encrypted user private keys or the encrypted private key for the client computing device960respectively. Storing the encrypted private keys may include storing the encrypted private keys in one or more of the primary storage960, the file system data agent904, a registry of the client computing device950, the encryption rules repository908, a directory of the file system902, a special purpose memory device (not shown) of the client computing device950, a special purpose location within a memory device of the client computing device950, and the like. In some cases, the encrypted private key may be embedded with a file that is encrypted with a data encryption key, which is itself encrypted by a public key corresponding to the encrypted private key. The encrypted data encryption key may also be embedded with the file.

At block1018, the encryption module922discards the private key, the passphrase, and the hashed passphrase for each user. In addition, the block1018may include discarding the private key for the client computing device950. Discarding the private key for the users and the client computing device950may include discarding unencrypted private keys. Thus, in certain embodiments, a private key may exist in its unencrypted form during generation of the private key and during decryption of a data encryption key that was encrypted with a public key corresponding to the private key. In such instances, the private key may only exist in an encrypted form during time periods other than asymmetric key generation and decryption of a data encryption key.

Although the operations of the process1000have been described following a specific order, the process1000is not limited as such. For instance, in some cases, operations may be performed in a different order (e.g., the operations associated with the block1010may be performed prior to the operations associated with the block1002). Further, in some cases, operations may be performed serially or substantially in parallel. For instance, the blocks1002and1010may be performed substantially in parallel.

Example Primary Storage File Encryption Process

FIG. 10Billustrates an example embodiment of a primary storage encryption process1050. The process1050can be implemented, at least in part, by any system that can encrypt a file for storage on a primary storage device (e.g., the primary storage device104or the primary storage device960). Further, the process1050can be performed by any system that can encrypt the key used to encrypt the file with user and/or system specific keys, which may be embedded with the encrypted file. For example, the process1050, in whole or in part, can be implemented by the filter driver204, the file system data agent904, the authentication system906, the file monitor930, the encryption rules engine926, the interface agent920, and the encryption module922, to name a few. Although any number of systems, in whole or in part, can implement the process1050, to simplify discussion, portions of the process1050will be described with reference to particular systems.

The process1050begins at block1052where, for example, the encryption rules engine926determines that a file is to be encrypted for storage at a primary storage device960. The encryption rules engine926may determine that the file is to be encrypted based, at least in part, on metadata associated with the file (e.g., the file type, the file storage location). Further, the determination may be based, at least in part, on encryption rules, which may be stored at the encryption rules repository908and which may be associated with the file based on the file's metadata. For example, all word processing files with a particular extension may be associated with an encryption rule that states that word processing files should be encrypted at the primary storage device960each time the files are closed. Alternatively, the encryption rules engine926may determine that a file is to be encrypted in response to an action by a user or application. In some embodiments, the block1052may occur in response to a command from a user, application954, or system (e.g., the storage manager140). Alternatively, the block1052may occur as part of an existing process (e.g., during or at the end of a backup process to a secondary storage computing device106or a secondary storage device108).

At block1054, the encryption module922obtains a data encryption key. This data encryption key can include any type of symmetric key. For example, the symmetric key can be an Advanced Encryption Standard (AES) key. Further, the key may be based on a stream cipher (e.g., RC4, A5/1, etc.) or a block cipher (e.g., Blowfish, DES, etc.). In some cases, the data encryption key may be an asymmetric key. In some cases, the encryption module922may obtain the key by accessing a key repository and/or by accessing the encryption rules repository908. Alternatively, the encryption module922may obtain the key from the storage manager140. In some cases, the encryption module922may generate the data encryption key. Generally, the data encryption key is unique for a file. However, in some cases, the data encryption key may be shared among a set of files. For example, the data encryption key may be used for each file in a directory. In certain embodiments, the data encryption key may be based on the file. In other cases, the data encryption key may be generated independently of the file.

Using the data encryption key, the encryption module922encrypts the file at block1056. At block1058, the encryption module922accesses a public key for each user who is authorized to access the file. The encryption module922may determine the users who are authorized to access the file based on metadata associated with the file and/or based on users who are authorized to access the client computing device950and/or the primary storage960or a storage location thereon (e.g., a directory). Further, the encryption module922may access the public keys by accessing one or more of the storage locations previously described with respect to the block1016. Although the same types of storage locations may be used to store the public keys and the encrypted private keys, the storage used to store the public keys and the private keys may or may not be the same storage. For example, the encrypted private keys may be stored in a special encrypted key store, while the corresponding public keys may be stored in an unencrypted key manager (not shown) or a location of the primary storage960. As mentioned previously, a user may be associated with multiple asymmetric key pairs. In such cases, the block1058may include determining the public key of the user to access based on the file to be encrypted and/or the location of the file to be encrypted. Alternatively, or in addition, the public key may be selected based on a desired encryption level.

At block1060, the encryption module922encrypts, for each user who is authorized to access the file, a copy of the data encryption key using the public key associated with the user identified or accessed at the block1058. In some embodiments, the blocks1058and1060are optional. For example, the data encryption key used to encrypt the file may be secured using only keys associated with the client computing device950, as described with respect to the blocks1062-1064.

At block1062, the encryption module922accesses a public key associated with the client computing device950. As with the block1058, the encryption module922may access the public key associated with the client computing device950by accessing one or more of the storage locations previously described with respect to the block1016. Further, as with the user public keys, in some cases the client computing device950may be associated with multiple asymmetric key pairs. In such cases, the block1062may include determining the public key of the client computing device950to access at the block1062based on the file to be encrypted the location of the file to be encrypted and/or a desired encryption level.

At block1064, the encryption module922encrypts a copy of the data encryption key using the public key identified and/or accessed at the block1062. In some embodiments, the blocks1062and1064are optional. For example, the data encryption key used to encrypt the file may be secured using only keys associated with users, as described with respect to the blocks1058-1060.

At block1066, the encryption module922discards the data encryption key. Discarding the data encryption key may include discarding unencrypted copies of the data encryption key from the client computing device950.

The encryption module922embeds each encrypted data encryption key with the encrypted file at block1068. Embedding the encrypted data encryption keys with the file may include storing the encrypted data encryption keys with the encrypted file in a single file. In some cases, the block1068may include the encrypted data encryption keys with the file without embedding the keys with the file. For example, the encrypted data encryption keys may be stored with the encrypted file (e.g., in the same directory or an adjacent block of memory). In other cases, the encrypted data encryption keys may be stored in a separate location. In such cases, the encrypted data encryption keys may be associated with the encrypted file, for example, based on a relationship in a table or using any other mechanism to associate the encrypted data encryption keys with the encrypted file.

At block1070, the encryption module922embeds encrypted private keys for each user and the client computing device with the encrypted file. These encrypted private keys correspond to the public keys accessed at blocks1058and1062. Further, the private keys may be encrypted as previously described with respect to the process1000. In some embodiments, the block1070is optional and/or omitted. For example, the encrypted private keys may be stored at the storage manager140, at a secure store of the client computing device950, or in any other location as previously described with respect to the block1016.

Second Example File Backup Process

FIG. 11illustrates a second example embodiment of a file backup process1100. The process1100can be implemented, at least in part, by any system that can backup a file to a secondary storage device108. For example, the process1100, in whole or in part, can be implemented by the filter driver204, the file system data agent904, the secure file access module924, the decryption module928, the file monitor930, and the storage manager140, to name a few. Although any number of systems, in whole or in part, can implement the process1100, to simplify discussion, portions of the process1100will be described with reference to particular systems.

As described below, the process1100includes decrypting an encrypted file, which may be stored at a primary storage device960, and providing the decrypted file to a secondary storage device108, which may or may not re-encrypt the file before storing the file. In certain embodiments, the encrypted file is decrypted as part of the process1100to enable single instancing. In other words, in some cases, by decrypting the file before backing up the file, the secondary storage can keep one copy of a file or data to which multiple users or computing devices may share access. Further, decrypting the file before backing it up enables deduplication at the secondary storage. In some embodiments, the process1100may be performed transparently and/or automatically when a user grants a backup system permission to decrypt files using the user's private key. This permission may be granted at the time that the file is protected or encrypted. Alternatively, the permission may be granted at a later time. In some cases, when the user is granting a backup system permission to backup encrypted files, the user may provide the backup system with access to the user's private key. Alternatively, in some cases, the process1100may be performed without the user granting permission to use the user's private key. For example, the process1100may be performed using the private key associated with the client computing device950. In some such cases, the user may have previously indicated that a backup system is authorized to access one or more of the encrypted files.

The process1100begins at block1102where, for example, the file monitor930identifies a file for backup to a secondary storage device108. The file may be identified for backup in response to a user command or a command from a storage manager140. In other cases, the file may be identified for backup as part of a scheduled backup process that may occur once, or on a scheduled basis (e.g., nightly, weekly, monthly, etc.). Further, in some cases, the file may be identified for backup based on the storage location of the file in the primary storage device960. For example, files in a particular directory may be identified or scheduled for backup.

At decision block1104, the secure file access module924determines whether the file identified for backup is encrypted. If the secure file access module924determines that the file is not encrypted, the file system data agent904provides the file to the secondary storage device108at block1106. Providing the file to the secondary storage device108may include providing the file to a media agent144of a secondary storage computing device106, which can then process the file for backup storage at a secondary storage device108. Processing the file for backup can include the secondary storage computing device106encrypting the file.

If at decision block1104the secure file access module924determines that the file is encrypted, the decryption module928accesses an encrypted private key for the file that is associated with the client computing device950at block1108. Accessing the encrypted private key can include extracting the encrypted private key from the encrypted file. In other cases, the encrypted private key may be accessed from a secure storage area of the primary storage device960.

At block1110, the file system data agent904provides the encrypted private key to the storage manager140. In some embodiments, providing the encrypted private key to the storage manager140includes providing an identity of the client computing device950to the storage manager140. Further, in some cases, the block1110may include providing authentication information for a user who is accessing the client computing device950to the storage manager140.

The storage manager140can decrypt the encrypted private key using a passphrase associated with the client computing device950. The storage manager140may identity the passphrase based on the received encrypted private key and/or the identity information received from the client computing device950. The storage manager140may hash the passphrase associated with the client computing device950and use the hashed passphrase to decrypt the encrypted private key. In some cases, the passphrase may be stored in its hashed form thereby making it unnecessary to hash the passphrase at the time of decryption of the encrypted private key for the client computing device950.

In some embodiments, the storage manager140may determine whether the passphrase associated with the client computing device950is active. If the passphrase is active, the storage manager140can use the passphrase to decrypt the encrypted private key. However, if the passphrase is marked as inactive, lost, or stolen, then the storage manager140may reject the request to decrypt the encrypted private key. Advantageously, when a client computing device950has been compromised, lost, stolen, or is no longer trusted, a user (e.g., an administrator) may indicate to the storage manager140that requests from the client computing device950should no longer be accepted. In response, the storage manager140can mark passphrases associated with the client computing device950as inactive thereby preventing requests to access encrypted files from the client computing device950from being processed.

At block1112, assuming the passphrase associated with the client computing device950is active at the storage manager140, the file system data agent904receives the private key from the storage manager140. The private key received at the block1112may be the decrypted version of the encrypted private key provided to the storage manager140at the block1110.

The decryption module928extracts an encrypted data encryption key associated with the client computing device950from the file at block1114. In some cases, the encrypted data encryption key is accessed from a storage location at the client computing device950and/or the primary storage device960. The encrypted data encryption key may be identified by accessing a data structure, such as a table, the associates the encrypted data encryption keys with the corresponding files. Further the data structure may associate each of the encrypted data encryption keys for a file with corresponding systems and/or users.

At block1116, the decryption module928decrypts the encrypted data encryption key using the private key obtained at the block1112. The decryption module928then decrypts the file using the decrypted data encryption key at block1118. The decrypted file is provided to the secondary storage device108, or to the secondary storage computing device106, at block1120. In some embodiments, the block1120may also include deleting or discarding the decrypted data encryption key and/or private key. Further, the block1120may include deleting the decrypted file after it is provided to the secondary storage device108.

In some embodiments, the process1100may include using a private key associated with a user instead of the private key associated with the client computing device950. In such embodiments, block1108may include accessing an encrypted private key associated with a user who, for example, initiated the file backup process. Further, the blocks1110and1112may include accessing a passphrase from the user by, for example, requesting the user provide the passphrase and/or accessing the passphrase from the authentication system906, which may have obtained the passphrase during an authentication process of the user. The passphrase may then be hashed by the decryption module928and used to decrypt the user's encrypted private key. At block1114, the decryption module928can extract an encrypted data encryption associated with the user. This encrypted data encryption key may be decrypted at the block1116using the private key of the user.

The process1100, in some embodiments, may be used for accessing the file by a user, an application, or system other than the secondary storage device108. In such embodiments, the decrypted file is presented to the requestor of the file at the block1120. For instance, the file may be presented to a user who is authorized to access the file. The user's authorization may be determined based, at least in part, on whether a data encryption key that was encrypted with a key associated with the user exists.

Example Client Passphrase Replacement Process

FIG. 12illustrates an example embodiment of a client passphrase replacement process1200. The process1200can be implemented, at least in part, by any system that can access an encrypted private key associated with or assigned to a client computing device and can replace the passphrase used to encrypt the encrypted private key. For example, the process1200, in whole or in part, can be implemented by the filter driver204, the file system data agent904, the secure file access module924, the encryption module922, the decryption module928, the file monitor930, and the storage manager140, to name a few. Although any number of systems, in whole or in part, can implement the process1200, to simplify discussion, portions of the process1200will be described with reference to particular systems.

The process1200may be performed in response to a detected integrity breach with respect to a client computing device950or storage manager140. This integrity breach may include a detected unauthorized access or an attempted unauthorized access of the client computing device950or storage manager140. The unauthorized access may include an attempt, successful or otherwise, to access or decrypt a private key associated with the client computing device950. Alternatively, or in addition, the process1200may be performed at a scheduled time to update or replace system passphrases for one or more client computing devices950. Further, as will be described in more detail below, the process1200may be used to replace user passphrases.

The process1200begins at block1202where, for example, the file system data agent904accesses an encrypted private key associated with a client computing device950. This encrypted private key may be specific to a file or set of files stored at the primary storage device960or accessible by the client computing device950. Alternatively, the encrypted private key may be specific to the client computing device950and may be used for any file that the client computing device950can access.

At block1204, the file system data agent904provides the encrypted private key to the storage manager140. In some cases, the block1204includes providing an identity of the client computing device950to the storage manager140. The storage manager140can decrypt the encrypted private key using a passphrase or hashed passphrase associated with the client computing device950. The storage manager can then access a new passphrase, or can generate a new passphrase, for the client computing device950. This new passphrase can be hashed and used to encrypt the decrypted private key to obtain an updated encrypted private key that is encrypted based on the new passphrase for the client computing device950. The new passphrase may be assigned to the client computing device950and may be identified as active at the storage manager140. The previous passphrase that was assigned to the client computing device950can be identified as inactive thereby preventing decryption of versions of the private key that were encrypted using the previous passphrase of the client computing device950. In some embodiments, the block1204can include one or more embodiments described above with respect to the block1110.

The file system data agent904receives a new encrypted private key from the storage manager140at block1206. This new encrypted private key can be the updated encrypted private key created by the storage manager140and assigned to the client computing device950. Using the process1200, the passphrase of the client computing device950may be updated while maintaining the same asymmetric key pair for the client computing device950. An example of an embodiment for updating the asymmetric key pair for the client computing device950will be described below with respect toFIG. 13.

As previously mentioned, a modified version of the process1200may be used to update a passphrase for a user. In such embodiments, the file system data agent904accesses an encrypted key associated with a user at the block1202. In some cases, the file system data agent904may still provide the encrypted private key to the storage manager140, which may obtain the user's passphrase from the user and decrypt the encrypted private key. In such cases, the storage manager140may also obtain a new passphrase from the user, or generate a new passphrase for the user, and encrypt the private key with the new passphrase, or a hashed version thereof, and provide the new encrypted private key to the client computing device950.

However, in other embodiments, Instead of providing the encrypted private key to the storage manger140, the file system data agent904can obtain the user's passphrase. The user may be prompted for the passphrase or the passphrase may be obtain from the authentication system906, which may have obtained the passphrase when the user was authenticated by the authentication system906during, for example, a login process. The decryption module928may hash the passphrase and use the hashed passphrase to decrypt the encrypted private encryption key. The encryption module922can obtain a new passphrase for the user by, for example, prompting the user for a new passphrase. The encryption module922can then hash the new passphrase and use the hashed version of the new passphrase to encrypt the private key. Any unencrypted copies of the private key can be discarded. Further, the passphrase provided by the user may also be discarded.

In some embodiments, instead of decrypting an encrypted private key and using a new passphrase to re-encrypt the private key, a new asymmetric key pair may be generated for a user or a client computing device950. In such cases, the old private key may be used to obtain access to the data encryption key. The data encryption key can then be encrypted using the new private key. The encrypted copy of the data encryption key can then be embedded or stored with the one or more files for which the data encryption key corresponds. In some implementations, instead of using the old private key to obtain access to the data encryption key, another private key may be used. For example, if the passphrase is being replaced for a user, the private key of the client computing device950may be used to obtain access to the data encryption key.

In some embodiments, the data encryption key encrypted with the old public key corresponding to the old private key may be discarded. In other cases, it may be left with the file, or at its storage location.

Example of a Client Key Rotation Process

FIG. 13illustrates an example embodiment of a client key rotation and/or replacement process1300. The process1300can be implemented, at least in part, by any system that can access an encrypted private key associated with or assigned to a client computing device and can replace the private key with a new private key for the client computing device as part of a process for replacing an asymmetric key pair associated with the client computing device. For example, the process1300, in whole or in part, can be implemented by the filter driver204, the file system data agent904, the secure file access module924, the encryption module922, the decryption module928, the file monitor930, and the storage manager140, to name a few. Although any number of systems, in whole or in part, can implement the process1300, to simplify discussion, portions of the process1300will be described with reference to particular systems.

As with the process1200, the process1300may be performed in response to a detected integrity breach with respect to a client computing device950or storage manager140. This integrity breach may include a detected unauthorized access or an attempted unauthorized access of the client computing device950or storage manager140. The unauthorized access may include an attempt, successful or otherwise, to access or decrypt a private key associated with the client computing device950. Alternatively, or in addition, the process1300may be performed at a scheduled time to update or replace system passphrases for one or more client computing devices950. Further, as will be described in more detail below, the process1300may be used to replace asymmetric keys associated with a user. Moreover, in some cases, the process1300can be performed in combination with the process1200to replace both an asymmetric key pair and a passphrase for a client computing device950and/or a user.

The process1300begins at block1302where, for example, the file system data agent904accesses an encrypted private key associated with a client computing device950from a file. In some embodiments, the block1302may include one or more embodiments described above with respect to the block1202.

At block1304, the file system data agent904obtains a copy of the data encryption key for the file. Obtaining the copy of the data encryption key may include decrypting a copy of an encrypted private key associated with the client computing device950and using the decrypted private key to decrypt an encrypted copy of the data encryption key as was previously described with respect to the blocks1108-1116.

At block1306, the file system data agent904discards the encrypted private key associated with the client computing device950. Discarding the private key of the client computing device950can include discarding copies of the client computing device's950corresponding public key. In some embodiments, the block1306may be optional. For example, in some cases, the passphrase used to encrypt the private key may be classified as inactive at the storage manager140thereby causing the storage manager140to reject attempts to decrypt the encrypted private key.

The file system data agent904obtains a new asymmetric key pair for the client computing device950at the block1308. As previously mentioned, the asymmetric key pairs can be obtained using an RSA scheme, or any other type of asymmetric encryption scheme. Further, in some cases, the encryption module922can generate the asymmetric encryption keys.

At block1310, the encryption module922encrypts the copy of the data encryption key using one of the keys (e.g., a public key) from the new asymmetric key pair. The encryption module922, at block1312, stores the encrypted data encryption key with the file by, for example, embedding the encrypted data encryption key into the file or by storing the encrypted data encryption key in an adjacent memory block. Alternatively, the encrypted data encryption key may be stored in a designated storage area of the client computing device950for storing encryption keys, such as a hardware key manager or in a protected area of memory. As another alternative, the encrypted data encryption key may be stored in a designated area of the primary storage device960.

At block1314, the file system data agent904provides the second key (e.g., a private key) from the new asymmetric key pair to the storage manager140. The storage manager140can encrypt the private key using a passphrase or a hashed passphrase associated with the client computing device950. In some embodiments, the storage manager140may select a new passphrase for the client computing device950and use the new passphrase, or a hashed version thereof, to encrypt the private key. Thus, in some cases, the process1200may be performed in combination with the process1300. Further, in certain embodiments, the block1314can include one or more of the embodiments described above with respect to the block1204.

At block1316, the file system data agent904receives the new encrypted private key from the storage manager140. In some embodiments, the block1316can include one or more of the embodiments described above with respect to the block1206.

As previously mentioned, the process1300, or a modified version thereof, may be used to replace an asymmetric key pair for a user. In such embodiments, the encrypted private key obtained at the block1302is the encrypted private key for the user whose encryption keys are being replaced. Further, obtaining the copy of the data encryption key may include obtaining the user's passphrase by, for example, prompting the user for the passphrase or obtaining the passphrase from the authentication system906as previously described. The passphrase may then be hashed and the hashed passphrase can be used to decrypt the encrypted private key. The decrypted private key can then be used to decrypt the encrypted data encryption key associated with the user for the file to obtain the data encryption key. As with the process for replacing the asymmetric key pair of the client computing device950, the private key of the user may be discarded and a new asymmetric key pair for the user may be obtained. One of the asymmetric keys (e.g., the public key) can be used to encrypt the copy of the data encryption key at block1310. The encrypted data encryption key can be stored with the file at block1312. The second asymmetric key (e.g., the private key) can be encrypted using a passphrase, or hashed passphrase, associated with the user. This may by the same passphrase for the user obtained during the process of decrypting the copy of the data encryption key at the block1304. Alternatively, the file system data agent904may obtain a new passphrase for the user by, for example, prompting the user for a new passphrase.

In some embodiments, the process1300, or a modified version thereof, may be used to provide additional users or client computing devices with access to an encrypted file. In such embodiments, the block1302and1304may be performed to obtain access to a data encryption key. However, rather than discarding an encrypted private key or obtaining a new asymmetric key pair for the client computing device950or a user that is associated with an existing copy of an encrypted data encryption key for the file, an asymmetric key pair is obtained or generated for a new client computing device and/or user at the block1308. The blocks1310-1316may then be performed using the new asymmetric key pair for the new client computing device. Alternatively, the process described in the previous paragraph with respect to the blocks1310-1316may be used to encrypt a copy of the data encryption key and the private key for the new user.

To remove authorization to access a file for a client computing device and/or for a user, the file system data agent904can obtain or extract the encrypted copy of the data encryption key for the file corresponding to the client computing device or user whose authorization to access the file is being removed. This encryption copy of the data encryption key can then be deleted or discarded thereby preventing the client computing device or user from being able to obtain a decrypted version of the data encryption key for the file.

In certain embodiments, a new asymmetric key pair may be selected for the client computing device950using, for example, the process associated with the block1308. However, a data key for a file may not be encrypted with the new private key of the new asymmetric key pair until the file is accessed by a user, or a system in the performance of an operation, such as a backup process. For example, a new asymmetric key pair may be selected for the client computing device950at a time X. At some later time Y, a file may be accessed using an old private key of the client computing device950associated with an older asymmetric key pair. After the data encryption key is obtained for the file, it may be reencrypted using the new public key of the new asymmetric key pair. The new private key can then be provided to the storage manger140for encryption using the client computing device's passphrase or hashed passphrase.

It is possible to rotate the asymmetric keys at some time subsequent to the replacement of the asymmetric key pairs because, for example, the storage manager140can maintain the passphrase of the client computing device950, even if the passphrase has been updated. Thus, for example, if a new asymmetric key pair is assigned to the client computing device950and a new passphrase is generated for the client computing device950to encrypt or obfuscate the private key of the new asymmetric key pair, the old passphrase may still be used to access the old private key at the time that a file is first accessed subsequent to the client computing device950being associated with a new asymmetric key pair. Once the data encryption key is extracted using the old asymmetric key pair, it can by protected using the new asymmetric key pair. In some cases, if there are no other files with data encryption keys that were secured using the old asymmetric key pair, the old asymmetric key pair can then be discarded.

Alternatively, in some embodiments, the data encryption keys for a set of files may be reencrypted using the new asymmetric key pair for the client computing device950as part of a background and/or low-priority process. For instance, when the client computing device950is idle, or not being accessed by a user, files stored on the primary storage device960may be accessed to rotate the client computing device's950asymmetric key pair using, for example the process1300.

TERMINOLOGY

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.

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

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