US20140201140A1 - Data synchronization management - Google Patents

Data synchronization management Download PDF

Info

Publication number
US20140201140A1
US20140201140A1 US13/968,120 US201313968120A US2014201140A1 US 20140201140 A1 US20140201140 A1 US 20140201140A1 US 201313968120 A US201313968120 A US 201313968120A US 2014201140 A1 US2014201140 A1 US 2014201140A1
Authority
US
United States
Prior art keywords
data
file
client computing
files
storage device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/968,120
Inventor
Anand Vibhor
Bhavyan Bharatkumar Mehta
Amey Vijaykumar Karandikar
Parag Gokhale
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Commvault Systems Inc
Original Assignee
Commvault Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Commvault Systems Inc filed Critical Commvault Systems Inc
Priority to US13/968,120 priority Critical patent/US20140201140A1/en
Assigned to COMMVAULT SYSTEMS, INC. reassignment COMMVAULT SYSTEMS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MEHTA, BHAVYAN BHARATKUMAR, VIBHOR, ANAND, GOKHALE, PARAG, KARANDIKAR, AMEY VIJAYKUMAR
Assigned to BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT reassignment BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT SECURITY INTEREST Assignors: COMMVAULT SYSTEMS, INC.
Publication of US20140201140A1 publication Critical patent/US20140201140A1/en
Assigned to COMMVAULT SYSTEMS, INC. reassignment COMMVAULT SYSTEMS, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: BANK OF AMERICA, N.A.
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H04L29/0854
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/17Details of further file system functions
    • G06F16/178Techniques for file synchronisation in file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1448Management of the data involved in backup or backup restore
    • G06F11/1451Management of the data involved in backup or backup restore by selection of backup contents
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1464Management of the backup or restore process for networked environments
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/275Synchronous replication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/52Network services specially adapted for the location of the user terminal

Definitions

  • a company might back up critical computing systems such as databases, file servers, web servers, and so on as part of a daily, weekly, or monthly maintenance schedule.
  • the company may similarly protect computing systems used by each of its employees, such as those used by an accounting department, marketing department, engineering department, and so forth.
  • aspects of the present disclosure are directed to a data synchronization management system that may synchronize files (and/or other data) among two or more client computing devices, in addition to backing up the files.
  • a user of the data synchronization management system may specify one or more file synchronization policies.
  • a file synchronization policy may specify the files that are to be synchronized, as well as the devices and locations to which those files are to be synchronized. For example, a user may create file synchronization policy and specify that all the files in a particular directory on their laptop are to be synchronized. Further, the user may specify that those files are to be synchronized to their desktop computer.
  • the user may also optionally specify a synchronization schedule, and/or a one-way or two-way file synchronization.
  • the data synchronization management system may work in conjunction with data backup policies.
  • a file synchronization proceeds as follows. Specified files are backed up or otherwise copied from the source client computing device to a secondary backup storage. The files to be synchronized are identified based both on the synchronization policy, and whether or not they have changed since the last backup. Thus, if a file backed up (and to be synchronized) is unchanged as compared to the previously backed up copy, that file is not synchronized. Any files identified for synchronization are synchronized to the one or more destination client computing devices, which are specified according to the synchronization policy of the user.
  • a user may specify the files to be synchronized.
  • Files to be synchronized may be directly selected or otherwise identified, or criteria may be specified to indirectly identify the files to be synchronized. For instance, without limitation, files may be identified by detecting the existence of specified content within the file (such as the existence of one or more specified terms within a document), and/or by matching metadata associated with the file with one or more specified metadata parameters (such as filename, file owner, directory, creation date, modification date, size, type, location, Global Positioning System (GPS) coordinates, among others).
  • GPS Global Positioning System
  • the criteria used to identify files to be synchronized can vary. For example, files to be synchronized may be identified as the files in a certain directory that were created after a certain date.
  • the data synchronization management system may add location information to files that are backed up.
  • a file to be synchronized may be identified according to the geographic location at which it was created and/or modified.
  • Location information may include, for example, GPS coordinates gathered by the client computing device including, for example, a GPS receiver.
  • a user of the data synchronization management system may access synchronized files through a cloud and/or remote file access interface. For example, the user may access their files through a web browser after their identity is authenticated.
  • a file list may initially be accessible by the user. Thereafter, a user may request access to a particular file. At this point the requested file data may be transferred from a secondary storage (backup) to the user's computer so that the user may access the file.
  • a computer-implemented method of synchronizing files between multiple client computers using secondary copy data comprising: accessing, by a synchronization module executing in computer hardware comprising one or more computer processors, user-defined synchronization criteria for identifying files to synchronize between a first primary storage device associated with a first client computing device and a second primary storage device associated with a second client computing device; initiating a secondary copy operation in which one or more files stored in the first primary storage device are copied to one or more secondary storage devices to create a secondary copy including the one or more files; after the initiation of the secondary copy operation, and based on the user-defined synchronization criteria, identifying, by the synchronization module, at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device; and communicating the at least one file to the second client computing device for storage in the second primary storage device to synchronize the at least one file between the first primary storage device and the second primary storage device.
  • said communicating comprises communicating a copy of the at least one file that is accessed from the one or more secondary storage devices.
  • said identifying is in response to the secondary copy operation.
  • the electronic data store is associated with a storage manager module executing in the computer hardware comprising the one or more computer processors.
  • At least one of said initiating, said identifying, or said communicating is performed by the storage manager module.
  • the method further comprises: receiving the user-defined synchronization criteria at the synchronization module; and storing the received user-defined synchronization criteria in an electronic data store accessible by the synchronization module.
  • the user-defined synchronization criteria are received from a user of at least one of the first client computing device or the second client computing device.
  • the at least one file communicated to the second client computing device replaces a previous version of the at least one file stored in the second primary storage device.
  • the user-defined synchronization criteria include at least one of: file data, file contents, file metadata, file name, file location, or location information.
  • identifying at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device comprises, for each particular file of the one or more files being copied to the one or more secondary storage devices: determining whether the particular file is different from a previous version of the particular file stored in the one or more secondary storage devices; and in response to determining that the particular files is different from the previous version of the particular file, identifying the particular file as a file to be synchronized.
  • a system for synchronizing files between multiple client computers using secondary copy data comprising: a data store; and a synchronization module executing in computer hardware comprising one or more computer processors and configured to: access user-defined synchronization criteria from the data store, the user-defined synchronization criteria for identifying files to synchronize between a first primary storage device associated with a first client computing device and a second primary storage device associated with a second client computing device; after the initiation of a secondary copy operation in which one or more files stored in the first primary storage device are copied to one or more secondary storage devices to create a secondary copy including the one or more files, and based on the user-defined synchronization criteria, identify at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device; wherein a copy of the at least one file is communicated to the second client computing device for storage in the second primary storage device to synchronize the at least one file between the first primary storage device and the second primary storage device.
  • the copy of the at least one file that is communicated to the second client computing device is accessed from the one or more secondary storage devices.
  • the identification of the at least one file is performed in response to the secondary copy operation.
  • the secondary copy operation comprises a backup operation or an archive operation.
  • communicating the accessed at least one file to the second client computing device comprises a restore operation.
  • the at least one file communicated to the second client computing device replaces a previous version of the at least one file stored in the second primary storage device.
  • the user-defined synchronization criteria include at least one of: file data, file contents, file metadata, file name, file location, or location information.
  • a networked data storage system comprising: a first client computing device; a second client computing device; at least one first primary storage device associated with the first client computing device; at least one second primary storage device associated with the second client computing device; one or more secondary storage devices; and computer hardware comprising one or more computer processors and having a synchronization module executing thereon, the synchronization module configured to: access user-defined synchronization criteria, the user-defined synchronization criteria for identifying files to synchronize between the first primary storage device and the second primary storage device; after the initiation of a secondary copy in which one or more files stored in the first primary storage device are copied to the one or more secondary storage devices to create a secondary copy including the one or more files, and based on the user-defined synchronization criteria, identify at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device; wherein a copy of the at least one file is communicated to the second client computing device for storage in the second primary storage device to synchron
  • the copy of the at least one file that is communicated to the second client computing device is accessed from the one or more secondary storage devices.
  • the identification of the at least one file is performed is in response to the secondary copy operation.
  • FIG. 1A is a block diagram illustrating an exemplary information management system.
  • FIG. 1B is a detailed view of a primary storage device, a secondary storage device, and some examples of primary data and secondary copy data.
  • FIG. 1C is a block diagram of an exemplary information management system including a storage manager, one or more data agents, and one or more media agents.
  • FIG. 1D is a block diagram illustrating a scalable information management system.
  • FIG. 1E illustrates certain secondary copy operations according to an exemplary storage policy.
  • FIG. 2 is a block diagram illustrating an exemplary information management system configured to implement synchronization management, according to an embodiment of the present disclosure.
  • FIG. 3 illustrates an example data synchronization management process, according to an embodiment of the present disclosure.
  • FIG. 4 illustrates an example data synchronization management process including designation of particular files, according to an embodiment of the present disclosure.
  • FIG. 5 illustrates an example data synchronization management process including location metadata, according to an embodiment of the present disclosure.
  • FIG. 6 illustrates an example remote file access process, according to an embodiment of the present disclosure.
  • FIGS. 7A-G illustrate exemplary screenshots of pages of a user interface of a data synchronization management system, according to various embodiments of the present disclosure.
  • Systems and methods are described herein for synchronizing files or other data. For instance, techniques are described for synchronizing files between multiple client computing devices in a data storage system. The synchronization can be in response to, or otherwise in conjunction with, backup or other secondary copy operations.
  • the data synchronization components and techniques may be incorporated within, implemented by, or otherwise compatible with information management systems such as those that will now be described with respect to FIGS. 1A-1E . Data synchronization is described in further detail with respect to FIGS. 2-7G .
  • FIG. 1A shows one such information management system 100 , which generally includes combinations of hardware and software configured to protect and manage data and metadata generated and used by the various computing devices in the information management system 100 .
  • the organization which employs the information management system 100 may be a corporation or other business entity, non-profit organization, educational institution, household, governmental agency, or the like.
  • systems and associated components described herein may be compatible with and/or provide some or all of the functionality of the systems and corresponding components described in one or more of the following U.S. patents and patent application publications assigned to CommVault Systems, Inc., each of which is hereby incorporated in its entirety by reference herein:
  • the illustrated information management system 100 includes one or more client computing device 102 having at least one application 110 executing thereon, and one or more primary storage devices 104 storing primary data 112 .
  • the client computing device(s) 102 and the primary storage devices 104 may generally be referred to in some cases as a primary storage subsystem 117 .
  • 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.
  • information management system 100 generally refers to a combination of specialized components used to protect, move, manage, manipulate and/or process data and metadata generated by the client computing devices 102 .
  • the term may generally not refer to the underlying components that generate and/or store the primary data 112 , such as the client computing devices 102 themselves, the applications 110 and operating system residing on the client computing devices 102 , and the primary storage devices 104 .
  • 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.
  • the data generation sources include the one or more client computing devices 102 .
  • the client computing devices 102 may include, without limitation, one or more: workstations, personal computers, desktop computers, or other types of generally fixed computing systems such as mainframe computers and minicomputers.
  • the client computing devices 102 can also include mobile or portable computing devices, such as one or more laptops, tablet computers, personal data assistants, mobile phones (such as smartphones), and other mobile or portable computing devices such as embedded computers, set top boxes, vehicle-mounted devices, wearable computers, etc.
  • 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.
  • each client computing device 102 is associated with one or more users and/or corresponding user accounts, of employees or other individuals.
  • client computing device is used herein because the information management system 100 generally “serves” the data management and protection needs for the data generated by the client computing devices 102 .
  • the use of this term does not imply that the client computing devices 102 cannot be “servers” in other respects.
  • a particular client computing device 102 may act as a server with respect to other devices, such as other client computing devices 102 .
  • the client computing devices 102 can include mail servers, file servers, database servers, and web servers.
  • the client computing devices 102 may additionally include virtualized and/or cloud computing resources. For instance, one or more virtual machines may be provided to the organization by a third-party cloud service vendor. Or, in some embodiments, the client computing devices 102 include one or more virtual machine(s) running on a virtual machine host computing device operated by the organization. As one example, the organization may use one virtual machine as a database server and another virtual machine as a mail server. A virtual machine manager (VMM) (e.g., a Hypervisor) may manage the virtual machines, and reside and execute on the virtual machine host computing device.
  • VMM virtual machine manager
  • Each client computing device 102 may have one or more applications 110 (e.g., software applications) executing thereon which generate and manipulate the data that is to be protected from loss.
  • applications 110 e.g., software applications
  • the applications 110 generally facilitate the operations of an organization (or multiple affiliated organizations), and can include, without limitation, mail server applications (e.g., Microsoft Exchange Server), file server applications, mail client applications (e.g., Microsoft Exchange Client), database applications (e.g., SQL, Oracle, SAP, Lotus Notes Database), word processing applications (e.g., Microsoft Word), spreadsheet applications, financial applications, presentation applications, browser applications, mobile applications, entertainment applications, and so on.
  • mail server applications e.g., Microsoft Exchange Server
  • file server applications e.g., Microsoft Exchange Client
  • 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 e.g., financial applications, presentation applications, browser applications, mobile applications, entertainment applications, and so on.
  • the applications 110 can include at least one operating system (e.g., Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-based operating systems, etc.), which may support one or more file systems and host the other applications 110 .
  • operating system e.g., Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-based operating systems, etc.
  • the client computing devices 102 and other components in the information management system 100 can be connected to one another via one or more communication pathways 114 .
  • the communication pathways 114 can include one or more networks or other connection types including as any of following, without limitation: the Internet, a wide area network (WAN), a local area network (LAN), a Storage Area Network (SAN), a Fibre Channel connection, a Small Computer System Interface (SCSI) connection, a virtual private network (VPN), a token ring or TCP/IP based network, an intranet network, a point-to-point link, a cellular network, a wireless data transmission system, a two-way cable system, an interactive kiosk network, a satellite network, a broadband network, a baseband network, other appropriate wired, wireless, or partially wired/wireless computer or telecommunications networks, combinations of the same or the like.
  • the communication pathways 114 in some cases may also include application programming interfaces (APIs) including, e.g., cloud service provider APIs, virtual machine management APIs,
  • Primary data 112 is production data or other “live” data generated by the operating system and other applications 110 residing on a client computing device 102 .
  • the primary data 112 is stored on the primary storage device(s) 104 and is organized via a file system supported by the client computing device 102 .
  • the client computing device(s) 102 and corresponding applications 110 may create, access, modify, write, delete, and otherwise use primary data 112 .
  • Primary data 112 is generally in the native format of the source application 110 . According to certain aspects, primary data 112 is an initial or first (e.g., created before any other copies or before at least one other copy) stored copy of data generated by the source application 110 . Primary data 112 in some cases is created substantially directly from data generated by the corresponding source applications 110 .
  • the primary data 112 may sometimes be referred to as a “primary copy” in the sense that it is a discrete set of data. However, the use of this term does not necessarily imply that the “primary copy” is a copy in the sense that it was copied or otherwise derived from another stored version.
  • the primary storage devices 104 storing the primary data 112 may be relatively fast and/or expensive (e.g., a disk drive, a hard-disk array, solid state memory, etc.). In addition, primary data 112 may be intended for relatively short term retention (e.g., several hours, days, or weeks).
  • the client computing device 102 can access primary data 112 from the primary storage device 104 by making conventional file system calls via the operating system.
  • Primary data 112 representing files may include structured data (e.g., database files), unstructured data (e.g., documents), and/or semi-structured data. Some specific examples are described below with respect to FIG. 1B .
  • primary data 112 can include files, directories, file system volumes, data blocks, extents, or any other types or granularities of data objects.
  • 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.
  • 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
  • some of the applications 110 maintain indices of metadata for data objects, e.g., metadata associated with individual email messages. Thus, each data object may be associated with corresponding metadata.
  • metadata e.g., metadata associated with individual email messages.
  • each data object may be associated with corresponding metadata.
  • Each of the client computing devices 102 are associated with and/or in communication with one or more of the primary storage devices 104 storing corresponding primary data 112 .
  • a client computing device 102 may be considered to be “associated with” or “in communication with” a primary storage device 104 if it is capable of one or more of: storing data to the primary storage device 104 , retrieving data from the primary storage device 104 , and modifying data retrieved from a primary storage device 104 .
  • the primary storage devices 104 can include, without limitation, disk drives, hard-disk arrays, semiconductor memory (e.g., solid state drives), and network attached storage (NAS) devices. In some cases, the primary storage devices 104 form part of a distributed file system. The primary storage devices 104 may have relatively fast I/O times and/or are relatively expensive in comparison to the secondary storage devices 108 . For example, the information management system 100 may generally regularly access data and metadata stored on primary storage devices 104 , whereas data and metadata stored on the secondary storage devices 108 is accessed relatively less frequently.
  • each primary storage device 104 is dedicated to an associated client computing devices 102 .
  • a primary storage device 104 in one embodiment is a local disk drive of a corresponding client computing device 102 .
  • one or more primary storage devices 104 can be shared by multiple client computing devices 102 .
  • a primary storage device 104 can be a disk array shared by a group of client computing devices 102 , such as one of the following types of disk arrays: EMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV, NetApp FAS, HP EVA, and HP 3PAR.
  • the information management system 100 may also include hosted services (not shown), which may be hosted in some cases by an entity other than the organization that employs the other components of the information management system 100 .
  • hosted services may be provided by various online service providers to the organization.
  • 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.
  • SaaS software-as-a-service
  • PaaS platform-as-a-service
  • ASPS application service providers
  • cloud services or other mechanisms for delivering functionality via a network.
  • each hosted service may generate additional data and metadata under management of the information management system 100 , e.g., as primary data 112 .
  • the hosted services may be accessed using one of the applications 110 .
  • a hosted mail service may be accessed via browser running on a client computing device 102 .
  • the primary data 112 stored on the primary storage devices 104 may be compromised in some cases, such as when an employee deliberately or accidentally deletes or overwrites primary data 112 during their normal course of work. Or the primary storage devices 104 can be damaged or otherwise corrupted.
  • the information management system 100 includes one or more secondary storage computing devices 106 and one or more secondary storage devices 108 configured to create and store one or more secondary copies 116 of the primary data 112 and associated metadata.
  • the secondary storage computing devices 106 and the secondary storage devices 108 may be referred to in some cases as a secondary storage subsystem 118 .
  • Creation of secondary copies 116 can help meet information management goals, such as: restoring data and/or metadata if an original version (e.g., of primary data 112 ) is lost (e.g., by deletion, corruption, or disaster); allowing point-in-time recovery; complying with regulatory data retention and electronic discovery (e-discovery) requirements; reducing utilized storage capacity; facilitating organization and search of data; improving user access to data files across multiple computing devices and/or hosted services; and implementing data retention policies.
  • an original version e.g., of primary data 112
  • e-discovery electronic discovery
  • Types of secondary copy operations can include, without limitation, backup operations, archive operations, snapshot operations, replication operations (e.g., continuous data replication [CDR]), data retention policies such as information lifecycle management and hierarchical storage management operations, and the like. These specific types operations are discussed in greater detail below.
  • backup operations e.g., archive operations, snapshot operations, replication operations (e.g., continuous data replication [CDR]), data retention policies such as information lifecycle management and hierarchical storage management operations, and the like.
  • CDR continuous data replication
  • the client computing devices 102 access or receive primary data 112 and communicate the data, e.g., over the communication pathways 114 , for storage in the secondary storage device(s) 108 .
  • a secondary copy 116 can comprise a separate stored copy of application data that is derived from one or more earlier created, stored copies (e.g., derived from primary data 112 or another secondary copy 116 ). Secondary copies 116 can include point-in-time data, and may be intended for relatively long-term retention (e.g., weeks, months or years), before some or all of the data is moved to other storage or is discarded.
  • a secondary copy 116 is a copy of application data created and stored subsequent to at least one other stored instance (e.g., subsequent to corresponding primary data 112 or to another secondary copy 116 ), in a different storage device than at least one previous stored copy, and/or remotely from at least one previous stored copy. Secondary copies 116 may be stored in relatively slow and/or low cost storage (e.g., magnetic tape). A secondary copy 116 may be stored in a backup or archive format, or in some other format different than the native source application format or other primary data format.
  • secondary copies 116 are indexed so users can browse and restore at another point in time.
  • a pointer or other location indicia e.g., a stub
  • the information management system 100 may create and manage multiple secondary copies 116 of a particular data object or metadata, each representing the state of the data object in primary data 112 at a particular point in time. Moreover, since an instance of a data object in primary data 112 may eventually be deleted from the primary storage device 104 and the file system, the information management system 100 may continue to manage point-in-time representations of that data object, even though the instance in primary data 112 no longer exists.
  • the operating system and other applications 110 of the client computing device(s) 102 may execute within or under the management of virtualization software (e.g., a VMM), and the primary storage device(s) 104 may comprise a virtual disk created on a physical storage device.
  • the information management system 100 may create secondary copies 116 of the files or other data objects in a virtual disk file and/or secondary copies 116 of the entire virtual disk file itself (e.g., of an entire .vmdk file).
  • Secondary copies 116 may be distinguished from corresponding primary data 112 in a variety of ways, some of which will now be described. First, as discussed, secondary copies 116 can be stored in a different format (e.g., backup, archive, or other non-native format) than primary data 112 . For this or other reasons, secondary copies 116 may not be directly useable by the applications 110 of the client computing device 102 , e.g., via standard system calls or otherwise without modification, processing, or other intervention by the information management system 100 .
  • a different format e.g., backup, archive, or other non-native format
  • Secondary copies 116 are also often stored on a secondary storage device 108 that is inaccessible to the applications 110 running on the client computing devices 102 (and/or hosted services). Some secondary copies 116 may be “offline copies,” in that they are not readily available (e.g. not mounted to tape or disk). Offline copies can include copies of data that the information management system 100 can access without human intervention (e.g. tapes within an automated tape library, but not yet mounted in a drive), and copies that the information management system 100 can access only with at least some human intervention (e.g. tapes located at an offsite storage site).
  • the secondary storage devices 108 can include any suitable type of storage device such as, without limitation, one or more tape libraries, disk drives or other magnetic, non-tape storage devices, optical media storage devices, solid state storage devices, NAS devices, combinations of the same, and the like.
  • the secondary storage devices 108 are provided in a cloud (e.g. a private cloud or one operated by a third-party vendor).
  • the secondary storage device(s) 108 in some cases comprises a disk array or a portion thereof.
  • a single storage device e.g., a disk array
  • a disk array capable of performing hardware snapshots stores primary data 112 and creates and stores hardware snapshots of the primary data 112 as secondary copies 116 .
  • Secondary copies can be a challenging task. For instance, there can be hundreds or thousands of client computing devices 102 continually generating large volumes of primary data 112 to be protected. Also, there can be significant overhead involved in the creation of secondary copies 116 . Moreover, secondary storage devices 108 may be special purpose components, and interacting with them can require specialized intelligence.
  • the client computing devices 102 interact directly with the secondary storage device 108 to create the secondary copies 116 .
  • this approach can negatively impact the ability of the client computing devices 102 to serve the applications 110 and produce primary data 112 .
  • the client computing devices 102 may not be optimized for interaction with the secondary storage devices 108 .
  • the information management system 100 includes one or more software and/or hardware components which generally act as intermediaries between the client computing devices 102 and the secondary storage devices 108 .
  • these intermediary components can provide other benefits. For instance, as discussed further below with respect to FIG. 1D , distributing some of the work involved in creating secondary copies 116 can enhance scalability.
  • the intermediary components can include one or more secondary storage computing devices 106 as shown in FIG. 1A and/or one or more media agents, which can be software modules residing on corresponding secondary storage computing devices 106 (or other appropriate devices). Media agents are discussed below (e.g., with respect to FIGS. 1C-1E ).
  • the secondary storage computing device(s) 106 can comprise any appropriate type of computing device and can include, without limitation, any of the types of fixed and portable computing devices described above with respect to the client computing devices 102 . In some cases, the secondary storage computing device(s) 106 include specialized hardware and/or software componentry for interacting with the secondary storage devices 108 .
  • the client computing device 102 communicates the primary data 112 to be copied (or a processed version thereof) to the designated secondary storage computing device 106 , via the communication pathway 114 .
  • the secondary storage computing device 106 in turn conveys the received data (or a processed version thereof) to the secondary storage device 108 .
  • the communication pathway 114 between the client computing device 102 and the secondary storage computing device 106 comprises a portion of a LAN, WAN or SAN.
  • at least some client computing devices 102 communicate directly with the secondary storage devices 108 (e.g., via Fibre Channel or SCSI connections).
  • FIG. 1B is a detailed view showing some specific examples of primary data stored on the primary storage device(s) 104 and secondary copy data stored on the secondary storage device(s) 108 , with other components in the system removed for the purposes of illustration.
  • Stored on the primary storage device(s) 104 are primary data objects including word processing documents 119 A-B, spreadsheets 120 , presentation documents 122 , video files 124 , image files 126 , email mailboxes 128 (and corresponding email messages 129 A-C), html/xml or other types of markup language files 130 , databases 132 and corresponding tables 133 A- 133 C).
  • 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.
  • object metadata e.g., “Meta1-11”
  • metadata Stored on the secondary storage device(s) 108 are secondary copy objects 134 A-C which may include copies of or otherwise represent corresponding primary data objects and metadata.
  • the secondary copy objects 134 A-C can individually represent more than one primary data object.
  • secondary copy data object 134 A represents three separate primary data objects 133 C, 122 and 129 C (represented as 133 C′, 122 ′ and 129 C′, respectively).
  • 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.
  • the information management system 100 can incorporate a variety of different hardware and software components, which can in turn be organized with respect to one another in many different configurations, depending on the embodiment. There are critical design choices involved in specifying the functional responsibilities of the components and the role of each component in the information management system 100 . For instance, as will be discussed, such design choices can impact performance as well as the adaptability of the information management system 100 to data growth or other changing circumstances.
  • FIG. 10 shows an information management system 100 designed according to these considerations and which includes: a central storage or information manager 140 configured to perform certain control functions, one or more data agents 142 executing on the client computing device(s) 102 configured to process primary data 112 , and one or more media agents 144 executing on the one or more secondary storage computing devices 106 for performing tasks involving the secondary storage devices 108 .
  • a central storage or information manager 140 configured to perform certain control functions
  • one or more data agents 142 executing on the client computing device(s) 102 configured to process primary data 112
  • media agents 144 executing on the one or more secondary storage computing devices 106 for performing tasks involving the secondary storage devices 108 .
  • the number of components in the information management system 100 and the amount of data under management can be quite large. Managing the components and data is therefore a significant task, and a task that can grow in an often unpredictable fashion as the quantity of components and data scale to meet the needs of the organization.
  • responsibility for controlling the information management system 100 is allocated to the storage manager 140 .
  • the storage manager 140 can be adapted independently according to changing circumstances. Moreover, a host computing device can be selected to best suit the functions of the storage manager 140 .
  • the storage manager 140 may be a software module or other application.
  • the storage manager generally initiates, coordinates and/or controls storage and other information management operations performed by the information management system 100 , e.g., to protect and control the primary data 112 and secondary copies 116 of data and metadata.
  • the storage manager 140 may communicate with and/or control some or all elements of the information management system 100 , such as the data agents 142 and media agents 144 .
  • control information originates from the storage manager 140
  • payload data and metadata is generally communicated between the data agents 142 and the media agents 144 (or otherwise between the client computing device(s) 102 and the secondary storage computing device(s) 106 ), e.g., at the direction of the storage manager 140 .
  • some information management operations are controlled by other components in the information management system 100 (e.g., the media agent(s) 144 or data agent(s) 142 ), instead of or in combination with the storage manager 140 .
  • the storage manager provides one or more of the following functions:
  • the storage manager 140 may maintain a database 146 of management-related data and information management policies 148 .
  • the database 146 may include a management index 150 or other data structure that stores logical associations between components of the system, user preferences and/or profiles (e.g., preferences regarding encryption, compression, or deduplication of primary or secondary copy data, preferences regarding the scheduling, type, or other aspects of primary or secondary copy or other operations, mappings of particular information management users or user accounts to certain computing devices or other components, etc.), management tasks, media containerization, or other useful data.
  • the storage manager 140 may use the index 150 to track logical associations between media agents 144 and secondary storage devices 108 and/or movement of data from primary storage devices 104 to secondary storage devices 108 .
  • Administrators and other employees may be able to manually configure and initiate certain information management operations on an individual basis. But while this may be acceptable for some recovery operations or other relatively less frequent tasks, it is often not workable for implementing on-going organization-wide data protection and management.
  • an information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with storage or other information management operations.
  • the storage manager database 146 may maintain the information management policies 148 and associated data, although the information management policies 148 can be stored in any appropriate location.
  • a storage policy may be stored as metadata in a media agent database 152 or in a secondary storage device 108 (e.g., as an archive copy) for use in restore operations or other information management operations, depending on the embodiment.
  • Information management policies 148 are described further below.
  • the storage manager database 146 comprises a relational database (e.g., an SQL database) for tracking metadata, such as metadata associated with secondary copy operations (e.g., what client computing devices 102 and corresponding data were protected). This and other metadata may additionally be stored in other locations, such as at the secondary storage computing devices 106 or on the secondary storage devices 108 , allowing data recovery without the use of the storage manager 140 .
  • a relational database e.g., an SQL database
  • metadata such as metadata associated with secondary copy operations (e.g., what client computing devices 102 and corresponding data were protected).
  • This and other metadata may additionally be stored in other locations, such as at the secondary storage computing devices 106 or on the secondary storage devices 108 , allowing data recovery without the use of the storage manager 140 .
  • the storage manager 140 may include a jobs agent 156 , a user interface 158 , and a management agent 154 , all of which may be implemented as interconnected software modules or application programs.
  • the jobs agent 156 in some embodiments initiates, controls, and/or monitors the status of some or all storage or other information management operations previously performed, currently being performed, or scheduled to be performed by the information management system 100 .
  • the jobs agent 156 may access information management policies 148 to determine when and how to initiate and control secondary copy and other information management operations, as will be discussed further.
  • the user interface 158 may include information processing and display software, such as a graphical user interface (“GUI”), an application program interface (“API”), or other interactive interface through which users and system processes can retrieve information about the status of information management operations (e.g., storage operations) or issue instructions to the information management system 100 and its constituent components.
  • GUI graphical user interface
  • API application program interface
  • the storage manager 140 may also track information that permits it to select, designate, or otherwise identify content indices, deduplication databases, or similar databases or resources or data sets within its information management cell (or another cell) to be searched in response to certain queries. Such queries may be entered by the user via interaction with the user interface 158 .
  • users may optionally issue instructions to the components in the information management system 100 regarding performance of storage and recovery operations. For example, a user may modify a schedule concerning the number of pending secondary copy operations. As another example, a user may employ the GUI to view the status of pending storage operations or to monitor the status of certain components in the information management system 100 (e.g., the amount of capacity left in a storage device).
  • the management agent 154 allows multiple information management systems 100 to communicate with one another.
  • the information management system 100 in some cases may be one information management subsystem or “cell” of a network of multiple cells adjacent to one another or otherwise logically related in a WAN or LAN. With this arrangement, the cells may be connected to one another through respective management agents 154 .
  • the management agent 154 can provide the storage manager 140 with the ability to communicate with other components within the information management system 100 (and/or other cells within a larger information management system) via network protocols and application programming interfaces (“APIs”) including, e.g., HTTP, HTTPS, FTP, REST, virtualization software APIs, cloud service provider APIs, and hosted service provider APIs.
  • APIs application programming interfaces
  • Inter-cell communication and hierarchy is described in greater detail in U.S. Pat. No. 7,035,880, which is incorporated by reference herein.
  • a variety of different types of applications 110 can reside on a given client computing device 102 , including operating systems, database applications, e-mail applications, and virtual machines, just to name a few. And, as part of the as part of the process of creating and restoring secondary copies 116 , the client computing devices 102 may be tasked with processing and preparing the primary data 112 from these various different applications 110 . Moreover, the nature of the processing/preparation can differ across clients and application types, e.g., due to inherent structural and formatting differences between applications 110 .
  • the one or more data agent(s) 142 are therefore advantageously configured in some embodiments to assist in the performance of information management operations based on the type of data that is being protected, at a client-specific and/or application-specific level.
  • the data agent 142 may be a software module or component that is generally responsible for managing, initiating, or otherwise assisting in the performance of information management operations. For instance, the data agent 142 may take part in performing data storage operations such as the copying, archiving, migrating, replicating of primary data 112 stored in the primary storage device(s) 104 . The data agent 142 may receive control information from the storage manager 140 , such as commands to transfer copies of data objects, metadata, and other payload data to the media agents 144 .
  • a data agent 142 may be distributed between the client computing device 102 and storage manager 140 (and any other intermediate components) or may be deployed from a remote location or its functions approximated by a remote process that performs some or all of the functions of data agent 142 .
  • a data agent 142 may perform some functions provided by a media agent 144 , e.g., encryption and deduplication.
  • each data agent 142 may be specialized for a particular application 110 , and the system can employ multiple data agents 142 , each of which may backup, migrate, and recover data associated with a different application 110 .
  • different individual data agents 142 may be designed to handle Microsoft Exchange data, Lotus Notes data, Microsoft Windows file system data, Microsoft Active Directory Objects data, SQL Server data, SharePoint data, Oracle database data, SAP database data, virtual machines and/or associated data, and other types of data.
  • a file system data agent may handle data files and/or other file system information.
  • one data agent 142 may be used for each data type to copy, archive, migrate, and restore the client computing device 102 data.
  • the client computing device 102 may use one Microsoft Exchange Mailbox data agent 142 to backup the Exchange mailboxes, one Microsoft Exchange Database data agent 142 to backup the Exchange databases, one Microsoft Exchange Public Folder data agent 142 to backup the Exchange Public Folders, and one Microsoft Windows File System data agent 142 to backup the file system of the client computing device 102 .
  • these data agents 142 may be treated as four separate data agents 142 even though they reside on the same client computing device 102 .
  • FIG. 1 may depict one or more generic data agents 142 that can handle and process data from two or more different applications 110 , or that can handle and process multiple data types, instead of or in addition to using specialized data agents 142 .
  • one generic data agent 142 may be used to back up, migrate and restore Microsoft Exchange Mailbox data and Microsoft Exchange Database data while another generic data agent may handle Microsoft Exchange Public Folder data and Microsoft Windows File System data.
  • Each data agent 142 may be configured to access data and/or metadata stored in the primary storage device(s) 104 associated with the data agent 142 and process the data as appropriate. For example, during a secondary copy operation, the data agent 142 may arrange or assemble the data and metadata into one or more files having a certain format (e.g., a particular backup or archive format) before transferring the file(s) to a media agent 144 or other component. The file(s) may include a list of files or other metadata. Each data agent 142 can also assist in restoring data or metadata to primary storage devices 104 from a secondary copy 116 . For instance, the data agent 142 may operate in conjunction with the storage manager 140 and one or more of the media agents 144 to restore data from secondary storage device(s) 108 .
  • a certain format e.g., a particular backup or archive format
  • off-loading certain responsibilities from the client computing devices 102 to intermediary components such as the media agent(s) 144 can provide a number of benefits including improved client computing device 102 operation, faster secondary copy operation performance, and enhanced scalability.
  • the media agent 144 can act as a local cache of copied data and/or metadata that it has stored to the secondary storage device(s) 108 , providing improved restore capabilities.
  • a media agent 144 may be implemented as a software module that manages, coordinates, and facilitates the transmission of data, as directed by the storage manager 140 , between a client computing device 102 and one or more secondary storage devices 108 . Whereas the storage manager 140 controls the operation of the information management system 100 , the media agent 144 generally provides a portal to secondary storage devices 108 .
  • Media agents 144 can comprise logically and/or physically separate nodes in the information management system 100 (e.g., separate from the client computing devices 102 , storage manager 140 , and/or secondary storage devices 108 ).
  • each media agent 144 may reside on a dedicated secondary storage computing device 106 in some cases, while in other embodiments a plurality of media agents 144 reside on the same secondary storage computing device 106 .
  • a media agent 144 (and corresponding media agent database 152 ) may be considered to be “associated with” a particular secondary storage device 108 if that media agent 144 is capable of one or more of: routing and/or storing data to the particular secondary storage device 108 , coordinating the routing and/or storing of data to the particular secondary storage device 108 , retrieving data from the particular secondary storage device 108 , and coordinating the retrieval of data from a particular secondary storage device 108 .
  • media agent(s) 144 are generally associated with one or more secondary storage devices 108
  • the media agents 144 in certain embodiments are physically separate from the secondary storage devices 108 .
  • the media agents 144 may reside on secondary storage computing devices 106 having different housings or packages than the secondary storage devices 108 .
  • a media agent 144 resides on a first server computer and is in communication with a secondary storage device(s) 108 residing in a separate, rack-mounted RAID-based system.
  • a media agent 144 associated with a particular secondary storage device 108 may instruct the secondary storage device 108 (e.g., a tape library) to use a robotic arm or other retrieval means to load or eject a certain storage media, and to subsequently archive, migrate, or retrieve data to or from that media, e.g., for the purpose of restoring the data to a client computing device 102 .
  • the media agent 144 may communicate with a secondary storage device 108 via a suitable communications link, such as a SCSI or Fiber Channel link.
  • each media agent 144 may maintain an associated media agent database 152 .
  • the media agent database 152 may be stored in a disk or other storage device (not shown) that is local to the secondary storage computing device 106 on which the media agent 144 resides. In other cases, the media agent database 152 is stored remotely from the secondary storage computing device 106 .
  • the media agent database 152 can include, among other things, an index 153 including data generated during secondary copy operations and other storage or information management operations.
  • the index 153 provides a media agent 144 or other component with a fast and efficient mechanism for locating secondary copies 116 or other data stored in the secondary storage devices 108 .
  • a storage manager index 150 or other data structure may store data associating a client computing device 102 with a particular media agent 144 and/or secondary storage device 108 , as specified in a storage policy.
  • a media agent index 153 or other data structure associated with the particular media agent 144 may in turn include information about the stored data.
  • the index 153 may include metadata such as a list of the data objects (e.g., files/subdirectories, database objects, mailbox objects, etc.), a path to the secondary copy 116 on the corresponding secondary storage device 108 , location information indicating where the data objects are stored in the secondary storage device 108 , when the data objects were created or modified, etc.
  • the index 153 includes metadata associated with the secondary copies 116 that is readily available for use in storage operations and other activities without having to be first retrieved from the secondary storage device 108 .
  • some or all of the data in the index 153 may instead or additionally be stored along with the data in a secondary storage device 108 , e.g., with a copy of the index 153 .
  • the index 153 maintained in the database 152 may operate as a cache, it can also be referred to as an index cache.
  • information stored in the index cache 153 typically comprises data that reflects certain particulars about storage operations that have occurred relatively recently. After some triggering event, such as after a certain period of time elapses, or the index cache 153 reaches a particular size, the index cache 153 may be copied or migrated to a secondary storage device(s) 108 . This information may need to be retrieved and uploaded back into the index cache 153 or otherwise restored to a media agent 144 to facilitate retrieval of data from the secondary storage device(s) 108 .
  • the cached information may include format or containerization information related to archives or other files stored on the storage device(s) 108 . In this manner, the index cache 153 allows for accelerated restores.
  • the media agent 144 generally acts as a coordinator or facilitator of storage operations between client computing devices 102 and corresponding secondary storage devices 108 , but does not actually write the data to the secondary storage device 108 .
  • the storage manager 140 (or the media agent 144 ) may instruct a client computing device 102 and secondary storage device 108 to communicate with one another directly.
  • the client computing device 102 transmits the data directly to the secondary storage device 108 according to the received instructions, and vice versa.
  • the media agent 144 may still receive, process, and/or maintain metadata related to the storage operations.
  • the payload data can flow through the media agent 144 for the purposes of populating the index cache 153 maintained in the media agent database 152 , but not for writing to the secondary storage device 108 .
  • the media agent 144 and/or other components such as the storage manager 140 may in some cases incorporate additional functionality, such as data classification, content indexing, deduplication, encryption, compression, and the like. Further details regarding these and other functions are described below.
  • certain functions of the information management system 100 can be distributed amongst various physical and/or logical components in the system.
  • one or more of the storage manager 140 , data agents 142 , and media agents 144 may reside on computing devices that are physically separate from one another. This architecture can provide a number of benefits.
  • the secondary computing devices 106 on which the media agents 144 reside can be tailored for interaction with associated secondary storage devices 108 and provide fast index cache operation, among other specific tasks.
  • the client computing device(s) 102 can be selected to effectively service the applications 110 residing thereon, in order to efficiently produce and store primary data 112 .
  • one or more of the individual components in the information management system 100 can be distributed to multiple, separate computing devices.
  • the management database 146 may be migrated to or otherwise reside on a specialized database server (e.g., an SQL server) separate from a server that implements the other functions of the storage manager 140 .
  • This configuration can provide added protection because the database 146 can be protected with standard database utilities (e.g., SQL log shipping or database replication) independent from other functions of the storage manager 140 .
  • the database 146 can be efficiently replicated to a remote site for use in the event of a disaster or other data loss incident at the primary site. Or the database 146 can be replicated to another computing device within the same site, such as to a higher performance machine in the event that a storage manager host device can no longer service the needs of a growing information management system 100 .
  • FIG. 1D shows an embodiment of the information management system 100 including a plurality of client computing devices 102 and associated data agents 142 as well as a plurality of secondary storage computing devices 106 and associated media agents 144 .
  • Additional components can be added or subtracted based on the evolving needs of the information management system 100 . For instance, depending on where bottlenecks are identified, administrators can add additional client computing devices 102 , secondary storage devices 106 (and corresponding media agents 144 ), and/or secondary storage devices 108 .
  • each client computing device 102 in some embodiments can communicate with any of the media agents 144 , e.g., as directed by the storage manager 140 .
  • each media agent 144 may be able to communicate with any of the secondary storage devices 108 , e.g., as directed by the storage manager 140 .
  • operations can be routed to the secondary storage devices 108 in a dynamic and highly flexible manner.
  • Further examples of scalable systems capable of dynamic storage operations are provided in U.S. Pat. No. 7,246,207, which is incorporated by reference herein.
  • certain components are not distributed and may instead reside and execute on the same computing device.
  • one or more data agents 142 and the storage manager 140 reside on the same client computing device 102 .
  • one or more data agents 142 and one or more media agents 144 reside on a single computing device.
  • the information management system 100 can be configured to perform a variety of information management operations. As will be described, these operations can generally include secondary copy and other data movement operations, processing and data manipulation operations, and management operations.
  • Data movement operations are generally operations that involve the copying or migration of data (e.g., payload data) between different locations in the information management system 100 .
  • data movement operations can include operations in which stored data is copied, migrated, or otherwise transferred from primary storage device(s) 104 to secondary storage device(s) 108 , from secondary storage device(s) 108 to different secondary storage device(s) 108 , or from primary storage device(s) 104 to different primary storage device(s) 104 .
  • Data movement operations can include by way of example, backup operations, archive operations, information lifecycle management operations such as hierarchical storage management operations, replication operations (e.g., continuous data replication operations), snapshot operations, deduplication operations, single-instancing operations, auxiliary copy operations, and the like. As will be discussed, some of these operations involve the copying, migration or other movement of data, without actually creating multiple, distinct copies. Nonetheless, some or all of these operations are referred to as “copy” operations for simplicity.
  • a backup operation creates a copy of primary data 112 at a particular point in time. Each subsequent backup copy may be maintained independently of the first. Further, a backup copy in some embodiments is stored in a backup format. This can be in contrast to the version in primary data 112 from which the backup copy is derived, and which may instead be stored in a native format of the source application(s) 110 . In various cases, backup copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format. For example, a backup copy may be stored in a backup format that facilitates compression and/or efficient long-term storage.
  • Backup copies can have relatively long retention periods as compared to primary data 112 , and may be stored on media with slower retrieval times than primary data 112 and certain other types of secondary copies 116 .
  • backups may have relatively shorter retention periods than some other types of secondary copies 116 , such as archive copies (described below). Backups may sometimes be stored at on offsite location.
  • Backup operations can include full, synthetic or incremental backups.
  • a full backup in some embodiments is generally a complete image of the data to be protected. However, because full backup copies can consume a relatively large amount of storage, it can be useful to use a full backup copy as a baseline and only store changes relative to the full backup copy for subsequent backup copies.
  • a differential backup operation (or cumulative incremental backup operation) tracks and stores changes that have occurred since the last full backup.
  • Differential backups can grow quickly in size, but can provide relatively efficient restore times because a restore can be completed in some cases using only the full backup copy and the latest differential copy.
  • An incremental backup operation generally tracks and stores changes since the most recent backup copy of any type, which can greatly reduce storage utilization. In some cases, however, restore times can be relatively long in comparison to full or differential backups because completing a restore operation may involve accessing a full backup in addition to multiple incremental backups.
  • Any of the above types of backup operations can be at the file-level, e.g., where the information management system 100 generally tracks changes to files at the file-level, and includes copies of files in the backup copy.
  • block-level backups are employed, where files are broken into constituent blocks, and changes are tracked at the block-level.
  • the information management system 100 reassembles the blocks into files in a transparent fashion.
  • backup operations generally involve maintaining a version of the copied data in primary data 112 and also maintaining backup copies in secondary storage device(s) 108 , they can consume significant storage capacity.
  • an archive operation creates a secondary copy 116 by both copying and removing source data. Or, seen another way, archive operations can involve moving some or all of the source data to the archive destination. Thus, data satisfying criteria for removal (e.g., data of a threshold age or size) from the source copy may be removed from source storage.
  • Archive copies are sometimes stored in an archive format or other non-native application format.
  • the source data may be primary data 112 or a secondary copy 116 , depending on the situation.
  • 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.
  • 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.
  • primary data 112 when primary data 112 is archived, in some cases the archived primary data 112 or a portion thereof is deleted when creating the archive copy. Thus, archiving can serve the purpose of freeing up space in the primary storage device(s) 104 . Similarly, when a secondary copy 116 is archived, the secondary copy 116 may be deleted, and an archive copy can therefore serve the purpose of freeing up space in secondary storage device(s) 108 . In contrast, source copies often remain intact when creating backup copies.
  • Snapshot operations can provide a relatively lightweight, efficient mechanism for protecting data.
  • a snapshot may be thought of as an “instant” image of the primary data 112 at a given point in time.
  • a snapshot may generally capture the directory structure of an object in primary data 112 such as a file or volume or other data set at a particular moment in time and may also preserve file attributes and contents.
  • a snapshot in some cases is created relatively quickly, e.g., substantially instantly, using a minimum amount of file space, but may still function as a conventional file system backup.
  • a snapshot copy in many cases can be made quickly and without significantly impacting primary computing resources because large amounts of data need not be copied or moved.
  • a snapshot may exist as a virtual file system, parallel to the actual file system. Users in some cases gain read-only access to the record of files and directories of the snapshot. By electing to restore primary data 112 from a snapshot taken at a given point in time, users may also return the current file system to the state of the file system that existed when the snapshot was taken.
  • 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.
  • 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.
  • 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.
  • 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.
  • Another type of secondary copy operation is a replication operation.
  • Some types of secondary copies 116 are used to periodically capture images of primary data 112 at particular points in time (e.g., backups, archives, and snapshots). However, it can also be useful for recovery purposes to protect primary data 112 in a more continuous fashion, by replicating the primary data 112 substantially as changes occur.
  • a replication copy can be a mirror copy, for instance, where changes made to primary data 112 are mirrored to another location (e.g., to secondary storage device(s) 108 ).
  • 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.
  • 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.
  • known good replication copies may be viewed as copies of primary data 112 . This feature allows the system to directly access, copy, restore, backup or otherwise manipulate the replication copies as if the data was the “live”, primary data 112 . This can reduce access time, storage utilization, and impact on source applications 110 , among other benefits.
  • the information management system 100 can replicate sections of application data that represent a recoverable state rather than rote copying of blocks of data. Examples of compatible replication operations (e.g., continuous data replication) are provided in U.S. Pat. No. 7,617,262, which is incorporated by reference herein.
  • deduplication Another type of data movement operation is deduplication, which is useful to reduce the amount of data within the system.
  • 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.
  • the information management system 100 may calculate and/or store signatures (e.g., hashes) corresponding to the individual data blocks and compare the hashes instead of comparing entire data blocks.
  • signatures e.g., hashes
  • deduplication operations may therefore be referred to interchangeably as “single-instancing” operations.
  • deduplication or single-instancing operations can store more than one instance of certain data blocks, but nonetheless significantly reduce data redundancy.
  • 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.
  • 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.
  • the information management system 100 utilizes a technique for dynamically aligning deduplication blocks (e.g., fixed-length blocks) based on changing content in the data stream, as described in U.S. Pat. Pub. No. 2012/0084269, which is incorporated by reference herein.
  • the information management system 100 can perform deduplication in a variety of manners at a variety of locations in the information management system 100 .
  • the information management system 100 implements “target-side” deduplication by deduplicating data (e.g., secondary copies 116 ) stored in the secondary storage devices 108 .
  • the media agents 144 are generally configured to manage the deduplication process.
  • one or more of the media agents 144 maintain a corresponding deduplication database that stores deduplication information (e.g., datablock signatures). Examples of such a configuration are provided in U.S. Pat. Pub. No. 2012/0150826, which is incorporated by reference herein.
  • Deduplication can also be performed on the “source-side” (or “client-side”), e.g., to reduce the amount of traffic between the media agents 144 and the client computing device(s) 102 and/or reduce redundant data stored in the primary storage devices 104 . Examples of such deduplication techniques are provided in U.S. Pat. Pub. No. 2012/0150818, which is incorporated by reference herein.
  • 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.
  • ILM information lifecycle management
  • 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.
  • HSM operation may involve movement of data from primary storage devices 104 to secondary storage devices 108 , or between tiers of secondary storage devices 108 . With each tier, the storage devices may be progressively relatively cheaper, have relatively slower access/restore times, etc. For example, movement of data between tiers may occur as data becomes less important over time.
  • 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.
  • an HSM copy may include data from primary data 112 or a secondary copy 116 that is larger than a given size threshold or older than a given age threshold and that is stored in a backup format.
  • HSM data that is removed or aged from the source copy is replaced by a logical reference pointer or stub.
  • the reference pointer or stub can be stored in the primary storage device 104 to replace the deleted data in primary data 112 (or other source copy) and to point to or otherwise indicate the new location in a secondary storage device 108 .
  • files are generally moved between higher and lower cost storage depending on how often the files are accessed.
  • the information management system 100 uses the stub to locate the data and often make recovery of the data appear transparent, even though the HSM data may be stored at a location different from the remaining source data.
  • the stub may also include some metadata associated with the corresponding data, so that a file system and/or application can provide some information about the data object and/or a limited-functionality version (e.g., a preview) of the data object.
  • An HSM copy may be stored in a format other than the native application format (e.g., where the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format).
  • 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”.
  • 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”.
  • An auxiliary copy is generally a copy operation in which a copy is created of an existing secondary copy 116 .
  • an initial or “primary” secondary copy 116 may be generated using or otherwise be derived from primary data 112
  • an auxiliary copy is generated from the initial secondary copy 116 .
  • Auxiliary copies can be used to create additional standby copies of data and may reside on different secondary storage devices 108 than initial secondary copies 116 .
  • auxiliary copies can be used for recovery purposes if initial secondary copies 116 become unavailable.
  • Exemplary compatible auxiliary copy techniques are described in further detail in U.S. Pat. No. 8,230,195, which is incorporated by reference herein.
  • the information management system 100 may also perform disaster recovery operations that make or retain disaster recovery copies, often as secondary, high-availability disk copies.
  • the information management system 100 may create secondary disk copies and store the copies at disaster recovery locations using auxiliary copy or replication operations, such as continuous data replication technologies.
  • disaster recovery locations can be remote from the client computing devices 102 and primary storage devices 104 , remote from some or all of the secondary storage devices 108 , or both.
  • the information management system 100 can also be configured to implement certain data manipulation operations, which according to certain embodiments are generally operations involving the processing or modification of stored data. Some data manipulation operations include content indexing operations and classification operations can be useful in leveraging the data under management to provide enhanced search and other features. Other data manipulation operations such as compression and encryption can provide data reduction and security benefits, respectively.
  • Data manipulation operations can be different than data movement operations in that they do not necessarily involve the copying, migration or other transfer of data (e.g., primary data 112 or secondary copies 116 ) between different locations in the system.
  • data manipulation operations may involve processing (e.g., offline processing) or modification of already stored primary data 112 and/or secondary copies 116 .
  • data manipulation operations are performed in conjunction with data movement operations.
  • the information management system 100 may encrypt data while performing an archive operation.
  • the information management system 100 “content indexes” data stored within the primary data 112 and/or secondary copies 116 , providing enhanced search capabilities for data discovery and other purposes.
  • the content indexing can be used to identify files or other data objects having pre-defined content (e.g., user-defined keywords or phrases), metadata (e.g., email metadata such as “to”, “from”, “cc”, “bcc”, attachment name, received time, etc.).
  • the information management system 100 generally organizes and catalogues the results in a content index, which may be stored within the media agent database 152 , for example.
  • the content index can also include the storage locations of (or pointer references to) the indexed data in the primary data 112 or secondary copies 116 , as appropriate.
  • the results may also be stored, in the form of a content index database or otherwise, elsewhere in the information management system 100 (e.g., in the primary storage devices 104 , or in the secondary storage device 108 ).
  • Such index data provides the storage manager 140 or another component with an efficient mechanism for locating primary data 112 and/or secondary copies 116 of data objects that match particular criteria.
  • search criteria can be specified by a user through user interface 158 of the storage manager 140 .
  • the information management system 100 analyzes data and/or metadata in secondary copies 116 to create an “off-line” content index, without significantly impacting the performance of the client computing devices 102 .
  • the system can also implement “on-line” content indexing, e.g., of primary data 112 . Examples of compatible content indexing techniques are provided in U.S. Pat. No. 8,170,995, which is incorporated by reference herein.
  • one or more components can be configured to scan data and/or associated metadata for classification purposes to populate a metabase of information.
  • Such scanned, classified data and/or metadata may be included in a separate database and/or on a separate storage device from primary data 112 (and/or secondary copies 116 ), such that metabase related operations do not significantly impact performance on other components in the information management system 100 .
  • the metabase(s) may be stored along with primary data 112 and/or secondary copies 116 .
  • Files or other data objects can be associated with user-specified identifiers (e.g., tag entries) in the media agent 144 (or other indices) to facilitate searches of stored data objects.
  • 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.
  • the information management system 100 in some cases is configured to process data (e.g., files or other data objects, secondary copies 116 , etc.), according to an appropriate encryption algorithm (e.g., Blowfish, Advanced Encryption Standard [AES], Triple Data Encryption Standard [3-DES], etc.) to limit access and provide data security in the information management system 100 .
  • an appropriate encryption algorithm e.g., Blowfish, Advanced Encryption Standard [AES], Triple Data Encryption Standard [3-DES], etc.
  • the information management system 100 in some cases encrypts the data at the client level, such that the client computing devices 102 (e.g., the data agents 142 ) encrypt the data prior to forwarding the data to other components, e.g., before sending the data media agents 144 during a secondary copy operation.
  • the client computing device 102 may maintain or have access to an encryption key or passphrase for decrypting the data upon restore. Encryption can also occur when creating copies of secondary copies, e.g., when creating auxiliary copies.
  • the secondary storage devices 108 can implement built-in, high performance hardware encryption.
  • Certain embodiments leverage the integrated, ubiquitous nature of the information management system 100 to provide useful system-wide management functions.
  • the information management system 100 can be configured to implement operations management and e-discovery functions.
  • Operations management can generally include monitoring and managing the health and performance of information management system 100 by, without limitation, performing error tracking, generating granular storage/performance metrics (e.g., job success/failure information, deduplication efficiency, etc.), generating storage modeling and costing information, and the like.
  • granular storage/performance metrics e.g., job success/failure information, deduplication efficiency, etc.
  • Such information can be provided to users via the user interface 158 in a single, integrated view.
  • the integrated user interface 158 can include an option to show a “virtual view” of the system that graphically depicts the various components in the system using appropriate icons.
  • the operations management functionality can facilitate planning and decision-making. For example, in some embodiments, a user may view the status of some or all jobs as well as the status of each component of the information management system 100 . Users may then plan and make decisions based on this data. For instance, a user may view high-level information regarding storage operations for the information management system 100 , such as job status, component status, resource status (e.g., network pathways, etc.), and other information. The user may also drill down or use other means to obtain more detailed information regarding a particular component, job, or the like.
  • the information management system 100 alerts a user such as a system administrator when a particular resource is unavailable or congested. For example, a particular primary storage device 104 or secondary storage device 108 might be full or require additional capacity. Or a component may be unavailable due to hardware failure, software problems, or other reasons.
  • the information management system 100 may suggest solutions to such problems when they occur (or provide a warning prior to occurrence).
  • the storage manager 140 may alert the user that a secondary storage device 108 is full or otherwise congested. The storage manager 140 may then suggest, based on job and data storage information contained in its database 146 , an alternate secondary storage device 108 .
  • corrective actions may include suggesting an alternate data path to a particular primary or secondary storage device 104 , 108 , or dividing data to be stored among various available primary or secondary storage devices 104 , 108 as a load balancing measure or to otherwise optimize storage or retrieval time. Such suggestions or corrective actions may be performed automatically, if desired. Further examples of some compatible operations management techniques and of interfaces providing an integrated view of an information management system are provided in U.S. Pat. No. 7,343,453, which is incorporated by reference herein. In some embodiments, the storage manager 140 implements the operations management functions described herein.
  • the information management system 100 can also be configured to perform system-wide e-discovery operations in some embodiments.
  • e-discovery operations provide a unified collection and search capability for data in the system, such as data stored in the secondary storage devices 108 (e.g., backups, archives, or other secondary copies 116 ).
  • the information management system 100 may construct and maintain a virtual repository for data stored in the information management system 100 that is integrated across source applications 110 , different storage device types, etc.
  • e-discovery utilizes other techniques described herein, such as data classification and/or content indexing.
  • an information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with secondary copy or other information management operations.
  • 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.
  • a portion of data may be given a label and the association is stored as a static entity in an index, database or other storage location.
  • Sub-clients may also be used as an effective administrative scheme of organizing data according to data type, department within the enterprise, storage preferences, or the like. Depending on the configuration, sub-clients can correspond to files, folders, virtual machines, databases, etc. In one exemplary scenario, an administrator may find it preferable to separate e-mail data from financial data using two different sub-clients.
  • a storage policy can define where data is stored by specifying a target or destination storage device (or group of storage devices). For instance, where the secondary storage device 108 includes a group of disk libraries, the storage policy may specify a particular disk library for storing the sub-clients associated with the policy. As another example, where the secondary storage devices 108 include one or more tape libraries, the storage policy may specify a particular tape library for storing the sub-clients associated with the storage policy, and may also specify a drive pool and a tape pool defining a group of tape drives and a group of tapes, respectively, for use in storing the sub-client data.
  • Datapath information can also be included in the storage policy.
  • the storage policy may specify network pathways and components to utilize when moving the data to the destination storage device(s).
  • the storage policy specifies one or more media agents 144 for conveying data (e.g., one or more sub-clients) associated with the storage policy between the source (e.g., one or more host client computing devices 102 ) and destination (e.g., a particular target secondary storage device 108 ).
  • a storage policy can also specify the type(s) of operations associated with the storage policy, such as a backup, archive, snapshot, auxiliary copy, or the like.
  • Retention information can specify how long the data will be kept, depending on organizational needs (e.g., a number of days, months, years, etc.)
  • the information management policies 148 may also include one or more scheduling policies specifying when and how often to perform operations. Scheduling information may specify with what frequency (e.g., hourly, weekly, daily, event-based, etc.) or under what triggering conditions secondary copy or other information management operations will take place. Scheduling policies in some cases are associated with particular components, such as particular sub-clients, client computing device 102 , and the like. In one configuration, a separate scheduling policy is maintained for particular sub-clients on a client computing device 102 . The scheduling policy specifies that those sub-clients are to be moved to secondary storage devices 108 every hour according to storage policies associated with the respective sub-clients.
  • administrators can manually configure information management policies 148 and/or other settings, e.g., via the user interface 158 .
  • this can be an involved process resulting in delays, and it may be desirable to begin data protecting operations quickly.
  • the information management system 100 automatically applies a default configuration to client computing device 102 .
  • the installation script may register the client computing device 102 with the storage manager 140 , which in turn applies the default configuration to the new client computing device 102 .
  • the default configuration can include a default storage policy, for example, and can specify any appropriate information sufficient to begin data protection operations. This can include a type of data protection operation, scheduling information, a target secondary storage device 108 , data path information (e.g., a particular media agent 144 ), and the like.
  • an audit policy is a set of preferences, rules and/or criteria that protect sensitive data in the information management system 100 .
  • 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.
  • an audit policy may require that a reviewer approve the transfer of any sensitive objects to a cloud storage site, and that if approval is denied for a particular sensitive object, the sensitive object should be transferred to a local storage device 104 instead.
  • the audit policy may further specify how a secondary storage computing device 106 or other system component should notify a reviewer that a sensitive object is slated for transfer.
  • the information management policies 148 may include one or more provisioning policies.
  • a provisioning policy can include a set of preferences, priorities, rules, and/or criteria that specify how clients 102 (or groups thereof) may utilize system resources, such as available storage on cloud storage and/or network bandwidth.
  • a provisioning policy specifies, for example, data quotas for particular client computing devices 102 (e.g. a number of gigabytes that can be stored monthly, quarterly or annually).
  • the storage manager 140 or other components may enforce the provisioning policy.
  • the media agents 144 may enforce the policy when transferring data to secondary storage devices 108 . If a client computing device 102 exceeds a quota, a budget for the client computing device 102 (or associated department) is adjusted accordingly or an alert may trigger.
  • information management policies 148 have been described as separate policies, one or more of these can be generally combined into a single information management policy 148 .
  • a storage policy may also include or otherwise be associated with one or more scheduling, audit, or provisioning policies.
  • storage policies are typically associated with moving and storing data, other policies may be associated with other types of information management operations. The following is a non-exhaustive list of items the information management policies 148 may specify:
  • Policies can additionally specify or depend on a variety of historical or current criteria that may be used to determine which rules to apply to a particular data object, system component, or information management operation, such as:
  • FIG. 1E shows a data flow data diagram depicting performance of storage operations by an embodiment of an information management system 100 , according to an exemplary data storage policy 148 A.
  • the information management system 100 includes a storage manger 140 , a client computing device 102 having a file system data agent 142 A and an email data agent 1428 residing thereon, a primary storage device 104 , two media agents 144 A, 144 B, and two secondary storage devices 108 A, 108 B: a disk library 108 A and a tape library 1088 .
  • the primary storage device 104 includes primary data 112 A, 112 B associated with a file system sub-client and an email sub-client, respectively.
  • the second media agent 1448 and the tape library 1088 are “off-site”, and may therefore be remotely located from the other components in the information management system 100 (e.g., in a different city, office building, etc.). In this manner, information stored on the tape library 1088 may provide protection in the event of a disaster or other failure.
  • the file system sub-client and its associated primary data 112 A in certain embodiments generally comprise information generated by the file system and/or operating system of the client computing device 102 , and can include, for example, file system data (e.g., regular files, file tables, mount points, etc.), operating system data (e.g., registries, event logs, etc.), and the like.
  • the e-mail sub-client, on the other hand, and its associated primary data 1128 include data generated by an e-mail client application operating on the client computing device 102 , and can include mailbox information, folder information, emails, attachments, associated database information, and the like.
  • the sub-clients can be logical containers, and the data included in the corresponding primary data 112 A, 1128 may or may not be stored contiguously.
  • the exemplary storage policy 148 A includes a backup copy rule set 160 , a disaster recovery copy rule set 162 , and a compliance copy rule set 164 .
  • the backup copy rule set 160 specifies that it is associated with a file system sub-client 166 and an email sub-client 168 . Each of these sub-clients 166 , 168 are associated with the particular client computing device 102 .
  • the backup copy rule set 160 further specifies that the backup operation will be written to the disk library 108 A, and designates a particular media agent 144 A to convey the data to the disk library 108 A.
  • the backup copy rule set 160 specifies that backup copies created according to the rule set 160 are scheduled to be generated on an hourly basis and to be retained for 30 days. In some other embodiments, scheduling information is not included in the storage policy 148 A, and is instead specified by a separate scheduling policy.
  • the disaster recovery copy rule set 162 is associated with the same two sub-clients 166 , 168 . However, the disaster recovery copy rule set 162 is associated with the tape library 108 B, unlike the backup copy rule set 160 . Moreover, the disaster recovery copy rule set 162 specifies that a different media agent 144 B than the media agent 144 A associated with the backup copy rule set 160 will be used to convey the data to the tape library 1088 . As indicated, disaster recovery copies created according to the rule set 162 will be retained for 60 days, and will be generated on a daily basis. Disaster recovery copies generated according to the disaster recovery copy rule set 162 can provide protection in the event of a disaster or other data-loss event that would affect the backup copy 116 A maintained on the disk library 108 A.
  • the compliance copy rule set 164 is only associated with the email sub-client 166 , and not the file system sub-client 168 . Compliance copies generated according to the compliance copy rule set 164 will therefore not include primary data 112 A from the file system sub-client 166 . For instance, the organization may be under an obligation to store maintain copies of email data for a particular period of time (e.g., 10 years) to comply with state or federal regulations, while similar regulations do not apply to the file system data.
  • the compliance copy rule set 164 is associated with the same tape library 108 B and media agent 144 B as the disaster recovery copy rule set 162 , although a different storage device or media agent could be used in other embodiments. Finally, the compliance copy rule set 164 specifies that copies generated under the compliance copy rule set 164 will be retained for 10 years, and will be generated on a quarterly basis.
  • the storage manager 140 initiates a backup operation according to the backup copy rule set 160 .
  • a scheduling service running on the storage manager 140 accesses scheduling information from the backup copy rule set 160 or a separate scheduling policy associated with the client computing device 102 , and initiates a backup copy operation on an hourly basis.
  • the storage manager 140 sends instructions to the client computing device 102 to begin the backup operation.
  • the file system data agent 142 A and the email data agent 142 B residing on the client computing device 102 respond to the instructions received from the storage manager 140 by accessing and processing the primary data 112 A, 112 B involved in the copy operation from the primary storage device 104 . Because the operation is a backup copy operation, the data agent(s) 142 A, 142 B may format the data into a backup format or otherwise process the data.
  • the client computing device 102 communicates the retrieved, processed data to the first media agent 144 A, as directed by the storage manager 140 , according to the backup copy rule set 160 .
  • the information management system 100 may implement a load-balancing, availability-based, or other appropriate algorithm to select from the available set of media agents 144 A, 144 B. Regardless of the manner the media agent 144 A is selected, the storage manager 140 may further keep a record in the storage manager database 140 of the association between the selected media agent 144 A and the client computing device 102 and/or between the selected media agent 144 A and the backup copy 116 A.
  • the target media agent 144 A receives the data from the client computing device 102 , and at step 4 conveys the data to the disk library 108 A to create the backup copy 116 A, again at the direction of the storage manager 140 and according to the backup copy rule set 160 .
  • the secondary storage device 108 A can be selected in other ways. For instance, the media agent 144 A may have a dedicated association with a particular secondary storage device(s), or the storage manager 140 or media agent 144 A may select from a plurality of secondary storage devices, e.g., according to availability, using one of the techniques described in U.S. Pat. No. 7,246,207, which is incorporated by reference herein.
  • the media agent 144 A can also update its index 153 to include data and/or metadata related to the backup copy 116 A, such as information indicating where the backup copy 116 A resides on the disk library 108 A, data and metadata for cache retrieval, etc. After the 30 day retention period expires, the storage manager 140 instructs the media agent 144 A to delete the backup copy 116 A from the disk library 108 A.
  • the storage manager 140 initiates the creation of a disaster recovery copy 1168 according to the disaster recovery copy rule set 162 . For instance, at step 6, based on instructions received from the storage manager 140 at step 5, the specified media agent 144 B retrieves the most recent backup copy 116 A from the disk library 108 A.
  • the media agent 144 B uses the retrieved data to create a disaster recovery copy 1168 on the tape library 1088 .
  • the disaster recovery copy 1168 is a direct, mirror copy of the backup copy 116 A, and remains in the backup format.
  • the disaster recovery copy 116 C may be generated in some other manner, such as by using the primary data 112 A, 1128 from the storage device 104 as source data. The disaster recovery copy operation is initiated once a day and the disaster recovery copies 116 A are deleted after 60 days.
  • the storage manager 140 initiates the creation of a compliance copy 116 C, according to the compliance copy rule set 164 .
  • the storage manager 140 instructs the media agent 144 B to create the compliance copy 116 C on the tape library 1088 at step 9, as specified in the compliance copy rule set 164 .
  • the compliance copy 116 C is generated using the disaster recovery copy 1168 .
  • the compliance copy 116 C is instead generated using either the primary data 1128 corresponding to the email sub-client or using the backup copy 116 A from the disk library 108 A as source data.
  • compliance copies 116 C are created quarterly, and are deleted after ten years.
  • a restore operation can be initiated involving one or more of the secondary copies 116 A, 1168 , 116 C.
  • a user may manually initiate a restore of the backup copy 116 A by interacting with the user interface 158 of the storage manager 140 .
  • the storage manager 140 then accesses data in its index 150 (and/or the respective storage policy 148 A) associated with the selected backup copy 116 A to identify the appropriate media agent 144 A and/or secondary storage device 116 A.
  • a media agent may be selected for use in the restore operation based on a load balancing algorithm, an availability based algorithm, or other criteria.
  • the selected media agent 144 A retrieves the data from the disk library 108 A. For instance, the media agent 144 A may access its index 153 to identify a location of the backup copy 116 A on the disk library 108 A, or may access location information residing on the disk 108 A itself.
  • the media agent 144 A accesses a cached version of the backup copy 116 A residing in the media agent index 153 , without having to access the disk library 108 A for some or all of the data. Once it has retrieved the backup copy 116 A, the media agent 144 A communicates the data to the source client computing device 102 . Upon receipt, the file system data agent 142 A and the email data agent 142 B may unpackage (e.g., restore from a backup format to the native application format) the data in the backup copy 116 A and restore the unpackaged data to the primary storage device 104 .
  • unpackage e.g., restore from a backup format to the native application format
  • secondary copies 116 can vary, depending on the embodiment.
  • secondary copies 116 are formatted as a series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4 GB, or 8 GB chunks). This can facilitate efficient communication and writing to secondary storage devices 108 , e.g., according to resource availability. For example, a single secondary copy 116 may be written on a chunk-by-chunk basis to a single secondary storage device 108 or across multiple secondary storage devices 108 . In some cases, users can select different chunk sizes, e.g., to improve throughput to tape storage devices.
  • 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.
  • the media agent 144 , storage manager 140 , or other component may divide the associated files into chunks and generate headers for each chunk by processing the constituent files.
  • the headers can include a variety of information such as file identifier(s), volume(s), offset(s), or other information associated with the payload data items, a chunk sequence number, etc.
  • the chunk headers 300 can also be stored to the index 153 of the associated media agent(s) 144 and/or the storage manager index 150 . This is useful in some cases for providing faster processing of secondary copies 116 during restores or other operations.
  • the secondary storage device 108 returns an indication of receipt, e.g., to the media agent 144 and/or storage manager 140 , which may update their respective indexes 150 , 153 accordingly.
  • chunks may be processed (e.g., by the media agent 144 ) according to the information in the chunk header to reassemble the files. Additional information relating to chunks can be found in U.S. Pat. No. 8,156,086, which is incorporated by reference herein.
  • FIG. 2 illustrates a data synchronization management system 200 according to an embodiment of the present disclosure.
  • the data synchronization management system 200 can incorporate a variety of different hardware and software components, which can in turn be organized with respect to one another in many different configurations, depending on the embodiment.
  • the data synchronization management system 200 of FIG. 2 includes the storage manager 140 , the secondary storage computing device(s) 106 , the secondary storage device(s) 108 , client computing devices 202 A-C, and primary storage devices 204 A-C.
  • the storage manager 140 includes the management database 146 and the management agent 154 .
  • the storage manager 140 includes a cloud interface 208 and a synchronization agent 210 .
  • the management database 146 includes information management policies 148 , synchronization policies 151 , and the management index 150 , as described above.
  • the secondary storage computing device(s) 106 include media agent(s) 144 and the media agent database 152 , the media agent database 152 also including the index 153 .
  • the client computing devices 202 A-C each may communicate with the respective primary storage devices 204 A-C. While three client computing devices 202 A-C and three primary storage devices 204 A-C are shown for illustrative purposes in FIG. 2 , additional (or fewer) client computing devices and primary storage devices may be present in the data synchronization management system 200 . Certain components in the system may communicate with one another via a network 206 . For instance, each of the client computing devices 202 A-C may communicate with the network 206 . Similarly, the storage manager 140 and the secondary storage computing device(s) 106 may communicate with the network 206 .
  • each of the client computing devices 202 A-C, the storage manager 140 , and the secondary storage computing device(s) 106 may communicate with one-another.
  • the network 206 may comprise any wired and/or wireless communications network suitable for data communications, and may include any of the networks, communications link, or communications pathways described herein.
  • the network 206 may comprise one or more of a LAN, WAN, cellular data network and/or the Internet, among others. Additionally, communication over the network 206 may be accomplished through any suitable communications protocol.
  • communication may be serial or parallel, through Universal Serial Bus (USB) (wired or wireless), Ethernet, Bluetooth, Near Field Communications (NFC), radio frequency (RF), infrared, and/or WiFi (such as any 802.1x interface), or combinations thereof, among others.
  • USB Universal Serial Bus
  • NFC Near Field Communications
  • RF radio frequency
  • infrared such as any 802.1x interface
  • WiFi such as any 802.1x interface
  • the storage manager 140 and the secondary storage computing device(s) 106 may also optionally communicate with one another directly, instead of or in addition to communicating with one another via the network 206 , also through any suitable communications network or protocol.
  • the storage manager 140 may include all of the functionality and components described above in reference to FIGS. 1A-E .
  • the storage manager 140 provides (among others) one or more of the following functions:
  • the storage manager 140 may maintain a database 146 of management-related data, such as information management and synchronization policies.
  • the database 146 may include the management index 150 or other data structure that stores logical associations between components of the system, user preferences, synchronization polices and/or synchronization (and/or user) profiles (e.g., preferences regarding what data is synchronized to which devices, preferences regarding the scheduling, type, or other aspects of data synchronization operations, etc.), management tasks, synchronization tasks, or other useful data.
  • the storage manager 140 may use the index 150 to track logical associations between media agents 144 and secondary storage devices 108 , movement of data from primary storage devices 204 A-C to secondary storage device(s) 108 , and/or synchronization states of data among the primary storage devices 204 A-C.
  • the data synchronization management system 200 may utilize information management policies 148 for specifying and executing information management operations, and synchronization policies 151 for specifying and executing synchronization operations (e.g., on an automated basis).
  • an information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with storage and/or other information management operations.
  • a synchronization policy 151 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with synchronization operations.
  • a synchronization policy 151 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 synchronization policy; (2) source information associated with the data to be synchronized, such as such as the identity of primary storage device(s) 204 and/or client computing device(s) 202 storing or otherwise associated with the data, information indicating where the data is stored (e.g., primary storage address information), and the like; (4) destination information associated with the data, such as the identify of secondary storage device(s), secondary storage devices 106 , and/or media agents to which the data will be synchronized; (5) datapath information specifying how the data will be communicated from sources to destinations; (6) the type of synchronization operation to be performed; and (7) the synchronization schedule.
  • a synchronization policy may be created by a user of the data synchronization management system 200 , in which the user specifies that files and/or data to be synchronized (by specifying for inclusion, for example, files belonging to a particular directory, files having particular content, and/or files having particular associated file metadata) and the devices to which the data will be synchronized (for example, a user may specify that data and/or files associated with client computing device 202 A are to be synchronized to the primary storage device 204 B associated with the client computing device 202 B).
  • a user may be identified by a user profile.
  • the user profile associated with a user may include, for example, information management policies 148 and/or synchronization policies 151 of the user, an identification of the user (for example, a username), and/or a means of authenticating the identity of the user (for example, a password), among other things.
  • Information management policies 148 and/or synchronization policies 151 may be associated with particular users of the data synchronization management system 200 , and more than one information management policy 148 and/or synchronization policy 151 may be associated with a particular user.
  • synchronization polices 151 in the data synchronization management system 200 are associated with a user profile.
  • the user profile may also include other information relevant to the data synchronization management system 200 , including for example, backup policies, among other things.
  • the management agent 154 may be implemented as interconnected software modules or application programs.
  • the synchronization agent 210 in some embodiments initiates, controls, and/or monitors the status of some or all synchronization or other information management operations previously performed, currently being performed, or scheduled to be performed by the data synchronization management system 200 .
  • the synchronization agent 210 may access information management policies 148 to determine when and how to initiate and control synchronization and other information management operations, as will be described further below.
  • embodiments of the data synchronization management system 200 generally also include the jobs agent 156 in the storage manager 140 , as described above with respect to the information management system 100 .
  • information management operations may be initiated, controlled, and/or monitored by the jobs agent 156 and/or the synchronization agent 210 .
  • the jobs agent 156 and the synchronization agent 210 may be a single unit.
  • the cloud interface 208 may include information processing and display software, such as a graphical user interface (“GUI”), an application program interface (“API”), or other interactive interface or portal through which users and system processes may retrieve information about the status of synchronization and/or other information management operations and data (e.g., storage operations and storage locations), retrieve data and/or files directly, view file lists, and/or issue instructions to the data synchronization management system 200 and its constituent components.
  • GUI graphical user interface
  • API application program interface
  • a user may access the cloud interface 208 via a browser or other application executing on one of the client computing devices 202 or another computing device.
  • users may optionally issue instructions to the components in the data synchronization management system 200 regarding performance of storage and recovery operations, performance of synchronization operations, and/or accessing of stored data.
  • a user may modify a synchronization schedule or may employ the GUI to view the status of pending storage and/or synchronization operations, or to monitor the status of certain components in the data synchronization management system 200 .
  • a user may identify and authenticate themselves (with, for example, a username and password), and view and access files and data (stored in, for example, the secondary storage device(s) 108 ) associated with the user.
  • Data from the cloud interface 208 may be transferred over the network 206 .
  • the cloud interface 208 may be accessed by a user over the Internet.
  • the cloud interface 208 may be located in a different part of the system (for example, in the secondary storage computing device(s) 106 ).
  • Data and/or files may be transferred from the client computing devices 202 A-C to the secondary storage device(s) via the media agent(s) 144 (and associated secondary storage computing device(s) 106 ).
  • files may be backed up or otherwise transferred from the primary storage device 204 A to the secondary storage device(s) 108 .
  • the media agent(s) 144 at the direction of the storage manager 140 , may communicate the files to be synchronized (e.g., through a restore operation) from the secondary storage device(s) 108 to the destination client computing device(s) 202 for storage in the associated primary storage devices 204 .
  • data and/or files transferred in the data synchronization management system 200 may be transferred directly from one client computing device to another. Such a transfer may be under the direction of the storage manager 140 .
  • storage manager 140 may direct client computing device 202 A to transfer files to be synchronized directly to computing device 202 B, e.g., without the use of the media agent(s) 144 .
  • the client computing devices 202 may include the components necessary to identify files to be synchronized, and to transfer those files to associated client computing devices directly.
  • the storage manager 140 may snoop on the files transferred from one client computing device to another so as to identify files to be copied to secondary storage.
  • the client computing devices 202 A-C include application(s) 110 and data agent(s) 142 (although they are not depicted in FIG. 2 ). These application(s) 110 and data agent(s) 142 generally function as described above. Additionally, it is to be understood that primary storage devices 204 A-C store primary data, as described above. Similarly, the secondary storage computing device(s) 106 (including the media agent 144 , media agent database 152 , and index 153 ) and the secondary storage device(s) 108 also generally function as described above in the information management system 100 .
  • data synchronization management system 200 information management, information processing, information transfer, data movement, secondary copy, and data backup, archive, and other operations in general are carried out in a manner similar to that described above.
  • description of the data synchronization management system 200 includes all of the functionality described above with respect to those and other operations, components, and characteristics (such as scalability).
  • FIG. 3 illustrates an example data synchronization management process, according to an embodiment of the present disclosure.
  • a data synchronization operation occurs as a result of or in response to a secondary copy operation (e.g., a data backup operation).
  • the data synchronization may occur subsequent to, simultaneously with, or may at least partially overlap with the secondary copy operation, depending on the embodiment.
  • data synchronization operations may be described herein as occurring in conjunction with backup operations for the purposes of illustration, data synchronization operations may be compatible with other types of secondary copy operations in addition to backup operations, e.g., archive operations, snapshot operations, replication operations, etc.
  • a secondary copy operation occurs in which a copy of primary data stored in one of the primary storage devices 204 A-C is created in the secondary storage device(s) 108 . Then, particular identified files are synchronized (e.g., through a restore operation) to the other primary storage devices 204 A-C from the secondary storage device(s) 108 . This process is described in detail in reference to blocks 302 , 304 , and 306 below.
  • a backup operation is initiated for a first client computing device.
  • an information management policy 148 may specify that a backup of certain data associated with client computing device 202 A is to occur. and the storage manager 140 may therefore initiate the backup.
  • a user of the client computing device 202 A may arbitrarily choose to manually initiate a backup, e.g., using the GUI of the storage manager 140 .
  • the data and/or file backup operation generally proceeds as detailed above (for example, as described in reference to FIG. 1E ).
  • the files selected for backup by the information management policy 148 may be copied from primary storage device 204 A to secondary storage device(s) 108 , as directed by the storage manager 140 .
  • files in the secondary copy are identified for synchronization.
  • Files and/or data to be synchronized are specified by the synchronization policy 151 , which can be any of those described above.
  • the storage manager 140 and/or the media agent(s) 144 compare the files backed up as part of the current backup operation to the previous versions of the files located in the secondary storage device(s) 108 .
  • Files that have not changed are determined to not require synchronization. Files that have changed in some way, however, are determined to require synchronization.
  • the user of the data synchronization management system 200 may specify that files contained within a particular directory are to be synchronized. Those files specified in the synchronization policy by the user will then be compared to previous versions of those files stored in the secondary storage device(s) 108 , and files requiring synchronization will be identified by, for example, the storage manager 140 and/or media agent(s) 144 .
  • the files to be synchronized may be identified before the backup is initiated, as the backup is initiated, as the backup is in progress, and/or after the backup is completed. Further details regarding the designation and identification of the files to be synchronized are described in reference to FIG. 4 below.
  • those files that are identified to be synchronized are restored to specific client computing devices.
  • the data and/or file restore operation proceeds as detailed above (for example, as described in reference to FIG. 1E ).
  • files may be transferred from the secondary storage device(s) 108 to one or more of the primary storage devices 204 A-C.
  • User created synchronization policies may specify the specific files to be synchronized, and/or the specific devices to which those files are to be synchronized.
  • the user may specify that files in a particular directory on the client computing device 202 A are to be synchronized with a particular directory on the client computing device 202 B.
  • the file synchronization among client computing devices may be accomplished through a combination of operations similar to the backup and restore operations described above.
  • identified files may not be restored/synchronized from the secondary storage device(s) 108 , but rather may be transferred from one client computing device to another directly.
  • the files to be synchronized may be backed up to the secondary storage device(s) 108 , and the backup operation may trigger the synchronization process, the synchronization is performed by transferring the files from the source client computing device to the target client computing device.
  • the bandwidth of the secondary storage computing device(s) 106 's connection to the network 206 may advantageously be preserved.
  • the user may specify multiple synchronization policies. For example, the user may specify that files located in directory “alpha” associated with client computing device 202 A are to be synchronized with a version of directory “alpha” associated with client computing device 202 B, while the files in directory “beta” associated with client computing device 202 B are to be synchronized with a version of directory “beta” associated with client computing device 202 C. Further, in certain embodiments, the user may specify different directories on the client computing devices to be synchronized. For example, the user may specify that files located in directory “alpha” associated with client computing device 202 A are to be synchronized with directory “gamma” associated with client computing device 202 B.
  • the user may synchronize files and/or data among more than two client computing devices.
  • the user may specify the particular client computing devices to which files are to be synchronized.
  • files may be synchronized to all client computing devices associated with the user of the data synchronization management system 200 .
  • Client computing devices associated with the user may be identified, in some embodiments, through the user profile. For example, a user may associate themselves with all the client computing devices they own and/or manage by including the identities of those client computing devices in the user's user profile.
  • FIG. 4 illustrates an example data synchronization management process including designation of particular files, according to an embodiment of the present disclosure.
  • the data synchronization management system 200 receives parameters indicating which files and/or data to synchronize.
  • the user indicates and/or identifies the files, and/or criteria for identifying the files, to be synchronized.
  • the files and/or data to be synchronized may be identified according to some policy, and/or a policy may be automatically created when a new user profile is created and/or a user profile is associated with a particular client computing device (for example, certain types of files, such as photos, may be automatically selected for synchronization when a user profile is created).
  • a user may specify the files to be synchronized.
  • Files to be synchronized may be directly selected or otherwise identified, or user-defined criteria may be specified to indirectly identify the files to be synchronized.
  • files may be identified by detecting the existence of specified content within the file (such as the existence of one or more specified terms within a document), and/or by matching metadata associated with the file with one or more specified metadata parameters (such as filename, file owner, directory, creation date, modification date, size, type, location, Global Positioning System (GPS) coordinates, among others).
  • GPS Global Positioning System
  • the criteria used to identify files to be synchronized may vary.
  • more than one criteria may be specified to identify files to be synchronized. For example, files to be synchronized may be identified as the files in a certain directory that were created after a certain date.
  • a backup operation is initiated for a first client computing device, similar to the operation of block 302 of FIG. 3 .
  • the files to be backed up may be specified by a backup policy, and may include files other than and/or in addition to those files selected for synchronization.
  • the files designated to be synchronized are automatically included in a backup policy.
  • the backup policy and the synchronization policy are separate, but may be related in some way.
  • the backup schedule set by the backup policy may or may not be linked to or associated with the synchronization schedule.
  • the synchronization policy is a subset of the backup policy.
  • multiple synchronization policies and backup policies may exist and/or be associated with a user profile.
  • files to be synchronized according to a synchronization policy are synchronized anytime any scheduled backup occurs (and/or is manually initiated).
  • the recently created backup copy is processed to identify files to be synchronized based on the received parameters discussed above in relation to block 402 .
  • the media agent 144 accesses the secondary copy from the secondary storage device(s) 108 and process the secondary copy to identify the files for synchronization. Similar to block 304 of FIG. 3 , in block 406 the files to be synchronized are thus identified.
  • the files in the secondary storage device(s) 108 that are in the designated directory “delta” (i.e., that satisfy the synchronization criteria specified by the policy) and are identified as having changed will be identified for synchronization.
  • those files that are identified to be synchronized are restored or otherwise transmitted to the target client computing devices, as described above in relation to the operation of block 306 of FIG. 3 .
  • identified files may not be restored/synchronized from the secondary storage device(s) 108 , but rather may be transferred from one client computing device to another directly.
  • the source client computing device may identify the files to be synchronized and communicate the files to the target client computing device(s).
  • FIG. 5 illustrates an example data synchronization management process including location metadata, according to an embodiment of the present disclosure.
  • the data synchronization management system 200 receives location information indicating which files and/or data to synchronize.
  • the user indicates and/or identifies the files to be synchronized based on the location information.
  • the files and/or data to be synchronized based on location information may be identified according to some policy, and/or may be automatically created when a new user profile is created and/or a user profile is associated with a particular client computing device (for example, certain files created in a particular location, such as documents created at home, may be automatically selected for synchronization when a user profile is created).
  • Location information may include, for example, geographical location, personal location (such as, for example, home or work), GPS location, city, and/or state, just to name a few.
  • a user may provide the location information in addition to other parameters as described above in reference to block 402 of FIG. 4 .
  • a backup operation is initiated for a first client computing device, similar to the operation of block 302 of FIGS. 3 , and 404 of FIG. 4 .
  • location metadata may be included and/or added to files in the secondary copy.
  • a component of the data synchronization management system 200 adds location information (such as, GPS coordinates) to the metadata associated with files on the client computing devices 202 A-C, in the primary copy.
  • location information such as, GPS coordinates
  • data agents on the client computing devices 202 A-C may add location metadata to files at the point the files are created, accessed, modified, and/or designated in some other way (such as, for example, designated through a backup and/or synchronization policy).
  • the storage manager 140 or other appropriate component may store location information related to client computing devices 202 A-C, and add location metadata to files backed up (or otherwise transferred to secondary storage).
  • the storage manager 140 may direct data agents on the client computing devices 202 A-C to add location metadata to files when a scheduled backup operation occurs.
  • Location information may include, for example, GPS coordinates, an Internet Protocol (IP) address, a street address, a geographic location (such as a city, state, etc.), a triangulated location based on mobile tracking with respect to telecommunications base stations, and/or computer-enabled location-based services, among others.
  • Location information may be provided by the client computing device. Location information may also be provided by a device attached to, embedded in, or otherwise in communication with the client computing device. For example, location information may be provided by a GPS receiver, a network adapter, or a cellular network radio, among others. Alternatively, location information may be provided manually by a user. For example, a user may specify location information for one or more files, and/or may designate location information associated with a particular client computing device. In an embodiment, any combination of the above described ways of providing location information may be used.
  • IP Internet Protocol
  • file location metadata is accessed in the secondary copy (in, for example, the secondary storage device(s) 108 ).
  • the accessed location metadata can then be used to identify files to be synchronized, according to the synchronization policy.
  • the user profile may include a synchronization policy that includes synchronization of all files that are created at the user's home GPS coordinates.
  • identified files in the secondary copy may include those with GPS metadata indicating a location associated with, at, or near the user's home.
  • those files that are identified to be synchronized are restored to the appropriate computing devices, as described above in relation to the operation of block 306 of FIG. 3 .
  • identified files may not be restored/synchronized from the secondary storage device(s) 108 , but rather may be transferred from one client computing device to another directly.
  • location metadata may be accessed on the client computing device to identify the files to be synchronized directly to other client computing devices.
  • FIG. 6 illustrates an example remote file access process, according to an embodiment of the present disclosure.
  • a user of the data synchronization management system 200 may request access to a file that may or may not presently be stored on the one of the client computing devices 202 A-C.
  • a file may not be present on one of the client computing devices 202 A-C in certain circumstances including circumstances in which, for example, the user is attempting to access the file through the cloud interface 208 and/or the file data has not yet been synchronized to the particular client computing device.
  • a user may utilize a client computing device to view, through the cloud interface 208 , a list of files designated for synchronization.
  • the list of files designated for synchronization may include files not presently synchronized to the client computing device. For example, a file that was recently created on another client computing device may not yet be synchronized to the user's client computing device. A user attempting to access files through the cloud interface 208 may thus attempt to access files that are not yet synchronized to the user's client computing device. Alternatively, an earlier version of the file desired by the user may be present on the user's client computing device, whereas an updated version has not yet synchronized from another client computing device where it was recently updated.
  • the data synchronization management system 200 may not synchronize all designated files to all client computing devices, but rather may synchronize a file list including, for example, file names and locations, but not the actual file data.
  • file data associated with a particular file may be synchronized to a client computing device at the time of a user's request for that file on that client computing device.
  • the data synchronization management system 200 may initially synchronize a file list, and subsequently synchronize the file data in the background.
  • the user may access a file list from any network 206 connected device, such as laptop computer with a web browser or the like. Thus, the user may be able to view a list of files, even though the actual file data may not be present on the network 206 connected device.
  • the example remote file access process begins at block 602 , at which point a file list is provided to, for example, a user.
  • the file list may be provided to the user in any of the examples and embodiments described above.
  • the file list may include limited file information, for example, file names, file locations, file modification dates, and/or file sizes, among other things.
  • a file access request is received from the user.
  • a user of the primary storage device 204 B or a web browser may view the file list, and see a file that they would like to access. The user may then request access to that file by, for example, clicking on or otherwise selecting the file.
  • the data synchronization management system 200 determines whether the file is locally synchronized. This may be accomplished, for example, by a local data agent and/or the storage manager 140 . In an embodiment in which the user is attempting to access the file through a web browser and the cloud interface 208 , it may be determined whether the requested file is stored in a local cache. In some embodiments, the file may be synchronizing in the background, and/or the locally synchronized file may be a version older than the most recent on all synchronized devices.
  • the current version of the requested file is locally synchronized, at block 608 the user is provided access to that local file.
  • the current version of the requested file is not locally synced, at block 610 the current version of the file is retrieved/synchronized from secondary storage.
  • the file may be retrieved directly from another client computing device, also as described above with respect to synchronization operations.
  • the user is provided access to that local copy of the file.
  • the user may optionally manually initiate synchronization of an accessed file.
  • the user may optionally manually initiate the transfer of the edited file back to the secondary storage device(s) 108 .
  • the edited file may then be synchronized to all related devices according to the synchronization policy.
  • the user profile may include synchronization policies specifying those files that are accessible through the remote file access process, as well as those that are not. For example, the user may specify that only particular files and/or data are to be available through the cloud interface 208 . The user may likely specify that all synchronized files, or no synchronized files are to be available through the cloud interface 208 .
  • file conflicts and/or inconsistencies arise.
  • the same file may be edited simultaneously in two of the client computing devices 202 A-C.
  • each file may be synchronized to the other client computing device, creating a conflict.
  • this conflict may be resolved in an automated fashion.
  • the differences may be merged according to any appropriate method.
  • one or more of the conflicting files may be renamed, and the user notified of the conflict for manual resolution. In general, even conflicted files will continue to be synchronized and backed up according to applicable policies.
  • one or more media agent(s) 144 may manage the synchronization of data and/or files among the client computing devices 202 A-C.
  • the media agent(s) 144 may determine whether changes have been made to backed up files that are designated for synchronization, and thus may determine whether or not a synchronization/restore operation occurs with respect to the other client computing device.
  • a synchronization policy may include the options for two-way synchronization and/or one-way synchronization.
  • files and/or data may be synchronized both to and from a destination.
  • a synchronization policy may indicate that files should be two-way synchronized between client computing device 202 A and client computing device 202 B. Thus, any changes on either of the devices would be synchronized to the other device.
  • a synchronization policy may indicate that files should be one-way synchronized.
  • one-way synchronization from client computing device 202 A to client computing device 202 B would cause any changes to synchronized files on client computing device 202 A to be synchronized to client computing device 202 B, but not the other way around.
  • a reverse one-way synchronization would cause any changes on client computing device 202 B to be synchronized to client computing device 202 A, but not the other way around.
  • the data synchronization management system 200 when a client computing device that is part of a synchronization policy is offline (for example, it is not connected to the network 206 , or it is powered down), the data synchronization management system 200 will wait until that client computing device comes back online to synchronize files and data to that client computing device. This may be accomplished, for example, through a polling process in which the storage manager 140 (or other component of the data synchronization management system 200 ) periodically polls the client computing devices 202 A-C to determine whether they are connected to the network 206 . Alternatively, the client computing devices 202 A-C may periodically send notification to the storage manager 140 (or other component of the data synchronization management system 200 ) when they are connected to the network 206 .
  • the connectedness of the client computing device is not determined until a scheduled or forced backup and/or synchronization occurs.
  • the client computing devices 202 A-C send notification to the storage manager 140 (or other component of the data synchronization management system 200 ) when they are initially connected to the network 206 .
  • all data transferred within the data synchronization management system 200 is encrypted.
  • the encrypted data may then be unencrypted when the user is identified and the identity of the user is authenticated.
  • the data associated with the data synchronization management system 200 does not leave the ecosystem of the data synchronization management system 200 .
  • the data synchronization management system 200 may comprise a local area network and/or enterprise network in which all communications are authenticated and encrypted. Thus, no unencrypted data is transferred out of the information management system to, for example, the open internet. Further, various data associated with various user profiles may be kept entirely separate (for example, encrypted separately).
  • data and files in the data synchronization management system 200 are deduplicated at the file and/or block level.
  • a file stored in secondary storage device(s) 108 is only stored once, even though it may be synchronized across multiple client computing devices, and although each of those client computing devices may have a separate backup policy involving that file.
  • the various embodiments of the data synchronization management system 200 described may include any or all of the various components of the information management system 100 described above, including, but not limited to, data movement operations, backup operations, archive operations, snapshot operations, replication operations, deduplication operations, data processing and manipulations operations, content indexing, metabase classification operations, encryption operations, and/or management operations.
  • FIGS. 7A-G illustrate exemplary screenshots of pages of the user interface of the data synchronization management system 200 , according to various embodiments of the present disclosure.
  • the term ‘cloud folder’ may be understood to refer to, without limitation, synchronization policies as described in the present disclosure.
  • Screenshot 700 of FIG. 7A shows an exemplary page of a user interface of the data synchronization management system 200 including a listing of backup information 702 , a current backup status display 704 , a listing of backup schedules 706 , a listing of content 707 , synchronization information 708 , and a last seen location window 709 .
  • user “backup1” has implemented a backup policy on a client computing device.
  • the listing of backup information 702 includes the date and time of the last backup, the last backup size, the total backup size, and the date and time this client computing device was last seen online.
  • the current backup status display 704 indicates that there is a current backup in process, and no backups are scheduled.
  • the backup schedules 706 button allows the user may schedule backups.
  • the listing of content 707 field indicates directories that the user has specified for back up.
  • the synchronization information 708 field allows the user to set synchronization policies by clicking the “Sync backup1 using Cloud Folders” link.
  • the last seen location window 709 shows the client computing devices last seen location.
  • the last seen location window 709 indicates that the client computing device associated with user interface of screenshot 700 includes a means of gathering location data that may be associated files to be backed up and/or synchronized.
  • the screenshot 710 of FIG. 7B shows an exemplary page of the user interface when a user chooses to create a synchronization policy, including a select folder path radio button 711 , an all backed-up data radio button 712 , a two-way sync radio button 714 , and one-way sync to cloud folder radio button 716 .
  • the user has specified a folder/synchronize policy name, “folder1.”
  • the select folder path radio button 711 the user may choose particular folders/directories to synchronize.
  • the all backed-up data radio button 712 the user may choose to synchronize all data that is already part of the backup policy.
  • the user may choose to synchronize file changes both ways (i.e., file changes on this client computing device are synchronized to other client computing devices, and likewise changes on other client computing devices are synchronized to this client computing device).
  • the user may use the one-way sync to cloud folder radio button 716 to synchronize files one way (i.e., file changes on this client computing device are synchronized to other client computing devices, but not the other way around).
  • Screenshot 720 of FIG. 7C shows another exemplary page of the user interface when a user chooses the select folder path radio button 711 of the page shown in FIG. 7B .
  • the page includes a listing 721 of backed up content.
  • the listing 721 includes a deselected folder 722 and a selected folder 724 .
  • the listing shows directories that will be synchronized under the present synchronization policy.
  • the deselected folder 722 is a folder/directory that is not selected for synchronization.
  • the selected folder 724 is a folder/directory that is selected for synchronization.
  • Screenshot 730 of FIG. 7D shows an exemplary page of the user interface after a synchronization policy/cloud folder “folder1” has been created, as indicated by field 732 .
  • Screenshot 740 of FIG. 7E shows another exemplary page of the user interface in which synchronization policies may be set.
  • the page includes a listing of cloud folders including folder1 information tab 741 , a listing of synchronization clients 742 , a listing of sync options including two-way sync mode 744 , only upload contents to cloud folder sync mode 746 , and only download contents to cloud folder sync mode 748 , and a default directory field 749 .
  • Folder1 information tab 741 indicates the current synchronization policy that is being set, as well as the directory path that is being synchronized.
  • the listing of synchronization clients 742 indicates the destinations to which the files of the current synchronization policy will be synchronized.
  • the user may select a synchronization mode from the listing of sync options.
  • the modes include: two-way sync mode 744 (synchronization both to and from the destination/client), only upload contents to cloud folder sync mode 746 (only synchronize to the destination/client), and only download contents to cloud folder sync mode 748 (only synchronize from the destination/client).
  • the user may set the path of the default download/upload path.
  • Screenshot 750 of FIG. 7F shows yet another exemplary page of user interface in which synchronization policies may be set.
  • the page includes two highlighted active cloud folders, indicated by the highlighted folder1 information tab 751 and folder2 information tab 752 .
  • the page also includes four inactive cloud folders, indicated by the greyed out folder information tabs 754 .
  • Active cloud folders may include those in which files are currently synchronizing, file synchronization is currently paused, and/or a synchronization schedule is set.
  • inactive cloud folders may include those in which files are not currently synchronizing, file synchronization is not currently paused, and/or a synchronization schedule is not set.
  • multiple synchronization policies may be set.
  • folder1 information tab 751 and folder2 information tab 752 indicate folders that are currently active
  • folder information tabs 754 indicate those that are currently inactive.
  • Screenshot 760 of FIG. 7G shows an exemplary page of the user interface in which synchronization policies may be set.
  • the page includes active cloud folders folder4 and folder 2, indicated by information tabs 761 and 762 .
  • the page also includes inactive cloud folders folder 3, folder5, and folder6 indicated by information tab 764 .
  • the page includes inactive cloud folder folder1 indicated by information tab 766 .
  • Folder4 (indicated by information tab 761 ) is active and currently synchronizing, while folder2 (indicated by information tab 762 ) is currently paused (not synchronizing).
  • folder1 is now inactive, as indicated by information tab 766 .
  • the data synchronization management system 200 advantageously enables synchronization of files and/or data among various client computing devices simultaneously with backups of files and/or data.
  • various synchronization policies may be set and adjusted by a user, specifying files to be synchronized based on parameters (file data, contents, and/or metadata) such as, for example, file location, file type, file size, file creation and/or modification, and/or location information.
  • synchronization policies may specify the devices to which various files should be synchronized.
  • the data synchronization management system 200 advantageously enables a user to access synchronized files through a cloud interface 208 from any location.
  • Conditional language such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
  • acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out all together (e.g., not all described acts or events are necessary for the practice of the algorithms).
  • acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
  • Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described herein.
  • Software and other modules may reside on servers, workstations, personal computers, computerized tablets, PDAs, and other devices suitable for the purposes described herein.
  • Software and other modules may be accessible via local memory, via a network, via a browser, or via other means suitable for the purposes described herein.
  • Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes or methods, or any combinations thereof, suitable for the purposes described herein.
  • User interface elements described herein may comprise elements from graphical user interfaces, command line interfaces, and other suitable interfaces.
  • processing of the various components of the illustrated systems can be distributed across multiple machines, networks, and other computing resources.
  • two or more components of a system can be combined into fewer components.
  • Various components of the illustrated systems can be implemented in one or more virtual machines, rather than in dedicated computer hardware systems.
  • the data repositories shown can represent physical and/or logical data storage, including, for example, storage area networks or other distributed storage systems.
  • the connections between the components shown represent possible paths of data flow, rather than actual connections between hardware. While some examples of possible connections are shown, any of the subset of the components shown can communicate with any other subset of components in various implementations.
  • Embodiments are also described above with reference to flow chart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products.
  • Each block of the flow chart illustrations and/or block diagrams, and combinations of blocks in the flow chart illustrations and/or block diagrams may be implemented by computer program instructions.
  • Such instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the acts specified in the flow chart and/or block diagram block or blocks.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the acts specified in the flow chart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the acts specified in the flow chart and/or block diagram block or blocks.

Abstract

In general, a data synchronization management system is disclosed in which files (and/or other data) are synchronized among two or more client computing devices in connection with a backup of those files. Synchronization polices specify files to be synchronized based on selected criteria including file data, metadata, and location information. In general, files are initially copied from a primary client computing device to secondary storage. Thereafter, files to be synchronized are identified from the secondary storage, and copied to other client computing devices. Additionally, synchronized files may be viewed and accessed through a cloud and/or remote file access interface.

Description

    INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS
  • Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 CFR 1.57.
  • The present application is being filed concurrently with U.S. application Ser. No. TBD, titled “CRITERIA-BASED DATA SYNCHRONIZATION MANAGEMENT,” U.S. application Ser. No. TBD, titled “LOCATION-BASED DATA SYNCHRONIZATION MANAGEMENT,” and U.S. application Ser. No. TBD, titled “REQUEST-BASED DATA SYNCHRONIZATION MANAGEMENT,” each of which is hereby incorporated herein by reference in its entirety.
  • BACKGROUND
  • Businesses worldwide recognize the commercial value of their data and seek reliable, cost-effective ways to protect the information stored on their computer networks while minimizing impact on productivity. Protecting information is often part of a routine process that is performed within an organization.
  • A company might back up critical computing systems such as databases, file servers, web servers, and so on as part of a daily, weekly, or monthly maintenance schedule. The company may similarly protect computing systems used by each of its employees, such as those used by an accounting department, marketing department, engineering department, and so forth.
  • Given the rapidly expanding volume of data under management, companies also continue to seek innovative techniques for managing data growth, in addition to protecting data. For instance, companies often implement migration techniques for moving data to lower cost storage over time and data reduction techniques for reducing redundant data, pruning lower priority data, etc.
  • Enterprises also increasingly view their stored data as a valuable asset. Along these lines, customers are looking for solutions that not only protect and manage, but also leverage their data. For instance, solutions providing data analysis capabilities, improved data presentation and access features, data synchronization, and the like, are in increasing demand.
  • SUMMARY
  • Generally described, aspects of the present disclosure are directed to a data synchronization management system that may synchronize files (and/or other data) among two or more client computing devices, in addition to backing up the files. In an embodiment, a user of the data synchronization management system may specify one or more file synchronization policies. A file synchronization policy may specify the files that are to be synchronized, as well as the devices and locations to which those files are to be synchronized. For example, a user may create file synchronization policy and specify that all the files in a particular directory on their laptop are to be synchronized. Further, the user may specify that those files are to be synchronized to their desktop computer. The user may also optionally specify a synchronization schedule, and/or a one-way or two-way file synchronization. The data synchronization management system may work in conjunction with data backup policies.
  • In an embodiment, a file synchronization proceeds as follows. Specified files are backed up or otherwise copied from the source client computing device to a secondary backup storage. The files to be synchronized are identified based both on the synchronization policy, and whether or not they have changed since the last backup. Thus, if a file backed up (and to be synchronized) is unchanged as compared to the previously backed up copy, that file is not synchronized. Any files identified for synchronization are synchronized to the one or more destination client computing devices, which are specified according to the synchronization policy of the user.
  • In an embodiment, a user may specify the files to be synchronized. Files to be synchronized may be directly selected or otherwise identified, or criteria may be specified to indirectly identify the files to be synchronized. For instance, without limitation, files may be identified by detecting the existence of specified content within the file (such as the existence of one or more specified terms within a document), and/or by matching metadata associated with the file with one or more specified metadata parameters (such as filename, file owner, directory, creation date, modification date, size, type, location, Global Positioning System (GPS) coordinates, among others). The criteria used to identify files to be synchronized can vary. For example, files to be synchronized may be identified as the files in a certain directory that were created after a certain date.
  • In an embodiment, the data synchronization management system may add location information to files that are backed up. Thus, a file to be synchronized may be identified according to the geographic location at which it was created and/or modified. Location information may include, for example, GPS coordinates gathered by the client computing device including, for example, a GPS receiver.
  • In an embodiment, a user of the data synchronization management system may access synchronized files through a cloud and/or remote file access interface. For example, the user may access their files through a web browser after their identity is authenticated. In this embodiment, a file list may initially be accessible by the user. Thereafter, a user may request access to a particular file. At this point the requested file data may be transferred from a secondary storage (backup) to the user's computer so that the user may access the file.
  • For purposes of summarizing the disclosure, certain aspects, advantages and novel features thereof have been described herein. Of course, it is to be understood that not necessarily all such aspects, advantages or features will be embodied in any particular embodiment of the invention.
  • According to an embodiment, a computer-implemented method of synchronizing files between multiple client computers using secondary copy data is disclosed, the computer-implemented method comprising: accessing, by a synchronization module executing in computer hardware comprising one or more computer processors, user-defined synchronization criteria for identifying files to synchronize between a first primary storage device associated with a first client computing device and a second primary storage device associated with a second client computing device; initiating a secondary copy operation in which one or more files stored in the first primary storage device are copied to one or more secondary storage devices to create a secondary copy including the one or more files; after the initiation of the secondary copy operation, and based on the user-defined synchronization criteria, identifying, by the synchronization module, at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device; and communicating the at least one file to the second client computing device for storage in the second primary storage device to synchronize the at least one file between the first primary storage device and the second primary storage device.
  • According to an aspect, said communicating comprises communicating a copy of the at least one file that is accessed from the one or more secondary storage devices.
  • According to an aspect, said identifying is in response to the secondary copy operation.
  • According to an aspect, the electronic data store is associated with a storage manager module executing in the computer hardware comprising the one or more computer processors.
  • According to an aspect, at least one of said initiating, said identifying, or said communicating is performed by the storage manager module.
  • According to an aspect, the method further comprises: receiving the user-defined synchronization criteria at the synchronization module; and storing the received user-defined synchronization criteria in an electronic data store accessible by the synchronization module.
  • According to an aspect, the user-defined synchronization criteria are received from a user of at least one of the first client computing device or the second client computing device.
  • According to an aspect, the at least one file communicated to the second client computing device replaces a previous version of the at least one file stored in the second primary storage device.
  • According to an aspect, the user-defined synchronization criteria include at least one of: file data, file contents, file metadata, file name, file location, or location information.
  • According to an aspect, identifying at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device comprises, for each particular file of the one or more files being copied to the one or more secondary storage devices: determining whether the particular file is different from a previous version of the particular file stored in the one or more secondary storage devices; and in response to determining that the particular files is different from the previous version of the particular file, identifying the particular file as a file to be synchronized.
  • According to another embodiment, a system for synchronizing files between multiple client computers using secondary copy data is disclosed, the system comprising: a data store; and a synchronization module executing in computer hardware comprising one or more computer processors and configured to: access user-defined synchronization criteria from the data store, the user-defined synchronization criteria for identifying files to synchronize between a first primary storage device associated with a first client computing device and a second primary storage device associated with a second client computing device; after the initiation of a secondary copy operation in which one or more files stored in the first primary storage device are copied to one or more secondary storage devices to create a secondary copy including the one or more files, and based on the user-defined synchronization criteria, identify at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device; wherein a copy of the at least one file is communicated to the second client computing device for storage in the second primary storage device to synchronize the at least one file between the first primary storage device and the second primary storage device.
  • According to an aspect, the copy of the at least one file that is communicated to the second client computing device is accessed from the one or more secondary storage devices.
  • According to an aspect, the identification of the at least one file is performed in response to the secondary copy operation.
  • According to an aspect, the secondary copy operation comprises a backup operation or an archive operation.
  • According to an aspect, communicating the accessed at least one file to the second client computing device comprises a restore operation.
  • According to an aspect, the at least one file communicated to the second client computing device replaces a previous version of the at least one file stored in the second primary storage device.
  • According to an aspect, the user-defined synchronization criteria include at least one of: file data, file contents, file metadata, file name, file location, or location information.
  • According to yet another embodiment, a networked data storage system is disclosed comprising: a first client computing device; a second client computing device; at least one first primary storage device associated with the first client computing device; at least one second primary storage device associated with the second client computing device; one or more secondary storage devices; and computer hardware comprising one or more computer processors and having a synchronization module executing thereon, the synchronization module configured to: access user-defined synchronization criteria, the user-defined synchronization criteria for identifying files to synchronize between the first primary storage device and the second primary storage device; after the initiation of a secondary copy in which one or more files stored in the first primary storage device are copied to the one or more secondary storage devices to create a secondary copy including the one or more files, and based on the user-defined synchronization criteria, identify at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device; wherein a copy of the at least one file is communicated to the second client computing device for storage in the second primary storage device to synchronize the at least one file between the first primary storage device and the second primary storage device.
  • According to an aspect, the copy of the at least one file that is communicated to the second client computing device is accessed from the one or more secondary storage devices.
  • According to an aspect, the identification of the at least one file is performed is in response to the secondary copy operation.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1A is a block diagram illustrating an exemplary information management system.
  • FIG. 1B is a detailed view of a primary storage device, a secondary storage device, and some examples of primary data and secondary copy data.
  • FIG. 1C is a block diagram of an exemplary information management system including a storage manager, one or more data agents, and one or more media agents.
  • FIG. 1D is a block diagram illustrating a scalable information management system.
  • FIG. 1E illustrates certain secondary copy operations according to an exemplary storage policy.
  • FIG. 2 is a block diagram illustrating an exemplary information management system configured to implement synchronization management, according to an embodiment of the present disclosure.
  • FIG. 3 illustrates an example data synchronization management process, according to an embodiment of the present disclosure.
  • FIG. 4 illustrates an example data synchronization management process including designation of particular files, according to an embodiment of the present disclosure.
  • FIG. 5 illustrates an example data synchronization management process including location metadata, according to an embodiment of the present disclosure.
  • FIG. 6 illustrates an example remote file access process, according to an embodiment of the present disclosure.
  • FIGS. 7A-G illustrate exemplary screenshots of pages of a user interface of a data synchronization management system, according to various embodiments of the present disclosure.
  • DETAILED DESCRIPTION
  • Systems and methods are described herein for synchronizing files or other data. For instance, techniques are described for synchronizing files between multiple client computing devices in a data storage system. The synchronization can be in response to, or otherwise in conjunction with, backup or other secondary copy operations. The data synchronization components and techniques may be incorporated within, implemented by, or otherwise compatible with information management systems such as those that will now be described with respect to FIGS. 1A-1E. Data synchronization is described in further detail with respect to FIGS. 2-7G.
  • 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. 1A shows one such information management system 100, which generally includes combinations of hardware and software configured to protect and manage data and metadata generated and used by the various computing devices in the information management system 100.
  • The organization which employs the information management system 100 may be a corporation or other business entity, non-profit organization, educational institution, household, governmental agency, or the like.
  • Generally, the systems and associated components described herein may be compatible with and/or provide some or all of the functionality of the systems and corresponding components described in one or more of the following U.S. patents and patent application publications assigned to CommVault Systems, Inc., each of which is hereby incorporated in its entirety by reference herein:
      • U.S. Pat. Pub. No. 2010-0332456, entitled “DATA OBJECT STORE AND SERVER FOR A CLOUD STORAGE ENVIRONMENT, INCLUDING DATA DEDUPLICATION AND DATA MANAGEMENT ACROSS MULTIPLE CLOUD STORAGE SITES”;
      • 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. Pub. No. 2012/0084269, 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/0329534, 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”; and
      • U.S. Pat. No. 8,156,086, entitled “SYSTEMS AND METHODS FOR STORED DATA VERIFICATION”.
  • The illustrated information management system 100 includes one or more client computing device 102 having at least one application 110 executing thereon, and one or more primary storage devices 104 storing primary data 112. The client computing device(s) 102 and the primary storage devices 104 may generally be referred to in some cases as a primary storage subsystem 117.
  • Depending on the context, the term “information management system” can refer to generally all of the illustrated hardware and software components. Or, in other instances, the term may refer to only a subset of the illustrated components.
  • For instance, in some cases information management system 100 generally refers to a combination of specialized components used to protect, move, manage, manipulate and/or process data and metadata generated by the client computing devices 102. However, the term may generally not refer to the underlying components that generate and/or store the primary data 112, such as the client computing devices 102 themselves, the applications 110 and operating system residing on the client computing devices 102, and the primary storage devices 104.
  • As an example, “information management system” may sometimes refer only to one or more of the following components and corresponding data structures: storage managers, data agents, and media agents. These components will be described in further detail below.
  • Client Computing Devices
  • There are typically a variety of sources in an organization that produce data to be protected and managed. As just one illustrative example, in a corporate environment such data sources can be employee workstations and company servers such as a mail server, a web server, or the like. In the information management system 100, the data generation sources include the one or more client computing devices 102.
  • The client computing devices 102 may include, without limitation, one or more: workstations, personal computers, desktop computers, or other types of generally fixed computing systems such as mainframe computers and minicomputers.
  • The client computing devices 102 can also include mobile or portable computing devices, such as one or more laptops, tablet computers, personal data assistants, mobile phones (such as smartphones), and other mobile or portable computing devices such as embedded computers, set top boxes, vehicle-mounted devices, wearable computers, etc.
  • In some cases, each client computing device 102 is associated with one or more users and/or corresponding user accounts, of employees or other individuals.
  • The term “client computing device” is used herein because the information management system 100 generally “serves” the data management and protection needs for the data generated by the client computing devices 102. However, the use of this term does not imply that the client computing devices 102 cannot be “servers” in other respects. For instance, a particular client computing device 102 may act as a server with respect to other devices, such as other client computing devices 102. As just a few examples, the client computing devices 102 can include mail servers, file servers, database servers, and web servers.
  • The client computing devices 102 may additionally include virtualized and/or cloud computing resources. For instance, one or more virtual machines may be provided to the organization by a third-party cloud service vendor. Or, in some embodiments, the client computing devices 102 include one or more virtual machine(s) running on a virtual machine host computing device operated by the organization. As one example, the organization may use one virtual machine as a database server and another virtual machine as a mail server. A virtual machine manager (VMM) (e.g., a Hypervisor) may manage the virtual machines, and reside and execute on the virtual machine host computing device.
  • Each client computing device 102 may have one or more applications 110 (e.g., software applications) executing thereon which generate and manipulate the data that is to be protected from loss.
  • The applications 110 generally facilitate the operations of an organization (or multiple affiliated organizations), and can include, without limitation, mail server applications (e.g., Microsoft Exchange Server), file server applications, mail client applications (e.g., Microsoft Exchange Client), database applications (e.g., SQL, Oracle, SAP, Lotus Notes Database), word processing applications (e.g., Microsoft Word), spreadsheet applications, financial applications, presentation applications, browser applications, mobile applications, entertainment applications, and so on.
  • The applications 110 can include at least one operating system (e.g., Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-based operating systems, etc.), which may support one or more file systems and host the other applications 110.
  • As shown, the client computing devices 102 and other components in the information management system 100 can be connected to one another via one or more communication pathways 114. The communication pathways 114 can include one or more networks or other connection types including as any of following, without limitation: the Internet, a wide area network (WAN), a local area network (LAN), a Storage Area Network (SAN), a Fibre Channel connection, a Small Computer System Interface (SCSI) connection, a virtual private network (VPN), a token ring or TCP/IP based network, an intranet network, a point-to-point link, a cellular network, a wireless data transmission system, a two-way cable system, an interactive kiosk network, a satellite network, a broadband network, a baseband network, other appropriate wired, wireless, or partially wired/wireless computer or telecommunications networks, combinations of the same or the like. The communication pathways 114 in some cases may also include application programming interfaces (APIs) including, e.g., cloud service provider APIs, virtual machine management APIs, and hosted service provider APIs.
  • Primary Data and Exemplary Primary Storage Devices
  • Primary data 112 according to some embodiments is production data or other “live” data generated by the operating system and other applications 110 residing on a client computing device 102. The primary data 112 is stored on the primary storage device(s) 104 and is organized via a file system supported by the client computing device 102. For instance, the client computing device(s) 102 and corresponding applications 110 may create, access, modify, write, delete, and otherwise use primary data 112.
  • Primary data 112 is generally in the native format of the source application 110. According to certain aspects, primary data 112 is an initial or first (e.g., created before any other copies or before at least one other copy) stored copy of data generated by the source application 110. Primary data 112 in some cases is created substantially directly from data generated by the corresponding source applications 110.
  • The primary data 112 may sometimes be referred to as a “primary copy” in the sense that it is a discrete set of data. However, the use of this term does not necessarily imply that the “primary copy” is a copy in the sense that it was copied or otherwise derived from another stored version.
  • The primary storage devices 104 storing the primary data 112 may be relatively fast and/or expensive (e.g., a disk drive, a hard-disk array, solid state memory, etc.). In addition, primary data 112 may be intended for relatively short term retention (e.g., several hours, days, or weeks).
  • According to some embodiments, the client computing device 102 can access primary data 112 from the primary storage device 104 by making conventional file system calls via the operating system. Primary data 112 representing files may include structured data (e.g., database files), unstructured data (e.g., documents), and/or semi-structured data. Some specific examples are described below with respect to FIG. 1B.
  • It can be useful in performing certain tasks to break the primary data 112 up into units of different granularities. In general, primary data 112 can include files, directories, file system volumes, data blocks, extents, or any other types or granularities of data objects. As used herein, a “data object” can refer to both (1) any file that is currently addressable by a file system or that was previously addressable by the file system (e.g., an archive file) and (2) a subset of such a file.
  • As will be described in further detail, it can also be useful in performing certain functions of the information management system 100 to access and modify metadata within the primary data 112. Metadata generally includes information about data objects or characteristics associated with the data objects.
  • Metadata can include, without limitation, one or more of the following: the data owner (e.g., the client or user that generates the data), the last modified time (e.g., the time of the most recent modification of the data object), a data object name (e.g., a file name), a data object size (e.g., a number of bytes of data), information about the content (e.g., an indication as to the existence of a particular search term), to/from information for email (e.g., an email sender, recipient, etc.), creation date, file type (e.g., format or application type), last accessed time, application type (e.g., type of application that generated the data object), location/network (e.g., a current, past or future location of the data object and network pathways to/from the data object), frequency of change (e.g., a period in which the data object is modified), business unit (e.g., a group or department that generates, manages or is otherwise associated with the data object), and aging information (e.g., a schedule, such as a time period, in which the data object is migrated to secondary or long term storage), boot sectors, partition layouts, file location within a file folder directory structure, user permissions, owners, groups, access control lists [ACLs]), system metadata (e.g., registry information), combinations of the same or the like.
  • In addition to metadata generated by or related to file systems and operating systems, some of the applications 110 maintain indices of metadata for data objects, e.g., metadata associated with individual email messages. Thus, each data object may be associated with corresponding metadata. The use of metadata to perform classification and other functions is described in greater detail below.
  • Each of the client computing devices 102 are associated with and/or in communication with one or more of the primary storage devices 104 storing corresponding primary data 112. A client computing device 102 may be considered to be “associated with” or “in communication with” a primary storage device 104 if it is capable of one or more of: storing data to the primary storage device 104, retrieving data from the primary storage device 104, and modifying data retrieved from a primary storage device 104.
  • The primary storage devices 104 can include, without limitation, disk drives, hard-disk arrays, semiconductor memory (e.g., solid state drives), and network attached storage (NAS) devices. In some cases, the primary storage devices 104 form part of a distributed file system. The primary storage devices 104 may have relatively fast I/O times and/or are relatively expensive in comparison to the secondary storage devices 108. For example, the information management system 100 may generally regularly access data and metadata stored on primary storage devices 104, whereas data and metadata stored on the secondary storage devices 108 is accessed relatively less frequently.
  • In some cases, each primary storage device 104 is dedicated to an associated client computing devices 102. For instance, a primary storage device 104 in one embodiment is a local disk drive of a corresponding client computing device 102. In other cases, one or more primary storage devices 104 can be shared by multiple client computing devices 102. As one example, a primary storage device 104 can be a disk array shared by a group of client computing devices 102, such as one of the following types of disk arrays: EMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV, NetApp FAS, HP EVA, and HP 3PAR.
  • The information management system 100 may also include hosted services (not shown), which may be hosted in some cases by an entity other than the organization that employs the other components of the information management system 100. For instance, the hosted services may be provided by various online service providers to the organization. Such service providers can provide services including social networking services, hosted email services, or hosted productivity applications or other hosted applications).
  • Hosted services may include software-as-a-service (SaaS), platform-as-a-service (PaaS), application service providers (ASPS), cloud services, or other mechanisms for delivering functionality via a network. As it provides services to users, each hosted service may generate additional data and metadata under management of the information management system 100, e.g., as primary data 112. In some cases, the hosted services may be accessed using one of the applications 110. As an example, a hosted mail service may be accessed via browser running on a client computing device 102.
  • Secondary Copies and Exemplary Secondary Storage Devices
  • The primary data 112 stored on the primary storage devices 104 may be compromised in some cases, such as when an employee deliberately or accidentally deletes or overwrites primary data 112 during their normal course of work. Or the primary storage devices 104 can be damaged or otherwise corrupted.
  • For recovery and/or regulatory compliance purposes, it is therefore useful to generate copies of the primary data 112. Accordingly, the information management system 100 includes one or more secondary storage computing devices 106 and one or more secondary storage devices 108 configured to create and store one or more secondary copies 116 of the primary data 112 and associated metadata. The secondary storage computing devices 106 and the secondary storage devices 108 may be referred to in some cases as a secondary storage subsystem 118.
  • Creation of secondary copies 116 can help meet information management goals, such as: restoring data and/or metadata if an original version (e.g., of primary data 112) is lost (e.g., by deletion, corruption, or disaster); allowing point-in-time recovery; complying with regulatory data retention and electronic discovery (e-discovery) requirements; reducing utilized storage capacity; facilitating organization and search of data; improving user access to data files across multiple computing devices and/or hosted services; and implementing data retention policies.
  • Types of secondary copy operations can include, without limitation, backup operations, archive operations, snapshot operations, replication operations (e.g., continuous data replication [CDR]), data retention policies such as information lifecycle management and hierarchical storage management operations, and the like. These specific types operations are discussed in greater detail below.
  • Regardless of the type of secondary copy operation, the client computing devices 102 access or receive primary data 112 and communicate the data, e.g., over the communication pathways 114, for storage in the secondary storage device(s) 108.
  • A secondary copy 116 can comprise a separate stored copy of application data that is derived from one or more earlier created, stored copies (e.g., derived from primary data 112 or another secondary copy 116). Secondary copies 116 can include point-in-time data, and may be intended for relatively long-term retention (e.g., weeks, months or years), before some or all of the data is moved to other storage or is discarded.
  • In some cases, a secondary copy 116 is a copy of application data created and stored subsequent to at least one other stored instance (e.g., subsequent to corresponding primary data 112 or to another secondary copy 116), in a different storage device than at least one previous stored copy, and/or remotely from at least one previous stored copy. Secondary copies 116 may be stored in relatively slow and/or low cost storage (e.g., magnetic tape). A secondary copy 116 may be stored in a backup or archive format, or in some other format different than the native source application format or other primary data format.
  • In some cases, secondary copies 116 are indexed so users can browse and restore at another point in time. After creation of a secondary copy 116 representative of certain primary data 112, a pointer or other location indicia (e.g., a stub) may be placed in primary data 112, or be otherwise associated with primary data 112 to indicate the current location on the secondary storage device(s) 108.
  • Since an instance a data object or metadata in primary data 112 may change over time as it is modified by an application 110 (or hosted service or the operating system), the information management system 100 may create and manage multiple secondary copies 116 of a particular data object or metadata, each representing the state of the data object in primary data 112 at a particular point in time. Moreover, since an instance of a data object in primary data 112 may eventually be deleted from the primary storage device 104 and the file system, the information management system 100 may continue to manage point-in-time representations of that data object, even though the instance in primary data 112 no longer exists.
  • For virtualized computing devices the operating system and other applications 110 of the client computing device(s) 102 may execute within or under the management of virtualization software (e.g., a VMM), and the primary storage device(s) 104 may comprise a virtual disk created on a physical storage device. The information management system 100 may create secondary copies 116 of the files or other data objects in a virtual disk file and/or secondary copies 116 of the entire virtual disk file itself (e.g., of an entire .vmdk file).
  • Secondary copies 116 may be distinguished from corresponding primary data 112 in a variety of ways, some of which will now be described. First, as discussed, secondary copies 116 can be stored in a different format (e.g., backup, archive, or other non-native format) than primary data 112. For this or other reasons, secondary copies 116 may not be directly useable by the applications 110 of the client computing device 102, e.g., via standard system calls or otherwise without modification, processing, or other intervention by the information management system 100.
  • Secondary copies 116 are also often stored on a secondary storage device 108 that is inaccessible to the applications 110 running on the client computing devices 102 (and/or hosted services). Some secondary copies 116 may be “offline copies,” in that they are not readily available (e.g. not mounted to tape or disk). Offline copies can include copies of data that the information management system 100 can access without human intervention (e.g. tapes within an automated tape library, but not yet mounted in a drive), and copies that the information management system 100 can access only with at least some human intervention (e.g. tapes located at an offsite storage site).
  • The secondary storage devices 108 can include any suitable type of storage device such as, without limitation, one or more tape libraries, disk drives or other magnetic, non-tape storage devices, optical media storage devices, solid state storage devices, NAS devices, combinations of the same, and the like. In some cases, the secondary storage devices 108 are provided in a cloud (e.g. a private cloud or one operated by a third-party vendor).
  • The secondary storage device(s) 108 in some cases comprises a disk array or a portion thereof. In some cases, a single storage device (e.g., a disk array) is used for storing both primary data 112 and at least some secondary copies 116. In one example, a disk array capable of performing hardware snapshots stores primary data 112 and creates and stores hardware snapshots of the primary data 112 as secondary copies 116.
  • The Use of Intermediary Devices for Creating Secondary Copies
  • Creating secondary copies can be a challenging task. For instance, there can be hundreds or thousands of client computing devices 102 continually generating large volumes of primary data 112 to be protected. Also, there can be significant overhead involved in the creation of secondary copies 116. Moreover, secondary storage devices 108 may be special purpose components, and interacting with them can require specialized intelligence.
  • In some cases, the client computing devices 102 interact directly with the secondary storage device 108 to create the secondary copies 116. However, in view of the factors described above, this approach can negatively impact the ability of the client computing devices 102 to serve the applications 110 and produce primary data 112. Further, the client computing devices 102 may not be optimized for interaction with the secondary storage devices 108.
  • Thus, in some embodiments, the information management system 100 includes one or more software and/or hardware components which generally act as intermediaries between the client computing devices 102 and the secondary storage devices 108. In addition to off-loading certain responsibilities from the client computing devices 102, these intermediary components can provide other benefits. For instance, as discussed further below with respect to FIG. 1D, distributing some of the work involved in creating secondary copies 116 can enhance scalability.
  • The intermediary components can include one or more secondary storage computing devices 106 as shown in FIG. 1A and/or one or more media agents, which can be software modules residing on corresponding secondary storage computing devices 106 (or other appropriate devices). Media agents are discussed below (e.g., with respect to FIGS. 1C-1E).
  • The secondary storage computing device(s) 106 can comprise any appropriate type of computing device and can include, without limitation, any of the types of fixed and portable computing devices described above with respect to the client computing devices 102. In some cases, the secondary storage computing device(s) 106 include specialized hardware and/or software componentry for interacting with the secondary storage devices 108.
  • To create a secondary copy 116, the client computing device 102 communicates the primary data 112 to be copied (or a processed version thereof) to the designated secondary storage computing device 106, via the communication pathway 114. The secondary storage computing device 106 in turn conveys the received data (or a processed version thereof) to the secondary storage device 108. In some such configurations, the communication pathway 114 between the client computing device 102 and the secondary storage computing device 106 comprises a portion of a LAN, WAN or SAN. In other cases, at least some client computing devices 102 communicate directly with the secondary storage devices 108 (e.g., via Fibre Channel or SCSI connections).
  • Exemplary Primary Data and an Exemplary Secondary Copy
  • FIG. 1B is a detailed view showing some specific examples of primary data stored on the primary storage device(s) 104 and secondary copy data stored on the secondary storage device(s) 108, with other components in the system removed for the purposes of illustration. Stored on the primary storage device(s) 104 are primary data objects including word processing documents 119A-B, spreadsheets 120, presentation documents 122, video files 124, image files 126, email mailboxes 128 (and corresponding email messages 129A-C), html/xml or other types of markup language files 130, databases 132 and corresponding tables 133A-133C).
  • Some or all primary data objects are associated with a primary copy of object metadata (e.g., “Meta1-11”), which may be file system metadata and/or application specific metadata. Stored on the secondary storage device(s) 108 are secondary copy objects 134A-C which may include copies of or otherwise represent corresponding primary data objects and metadata.
  • As shown, the secondary copy objects 134A-C can individually represent more than one primary data object. For example, secondary copy data object 134A represents three separate primary data objects 133C, 122 and 129C (represented as 133C′, 122′ and 129C′, respectively). Moreover, as indicated by the prime mark (′), a secondary copy object may store a representation of a primary data object or metadata differently than the original format, e.g., in a compressed, encrypted, deduplicated, or other modified format.
  • Exemplary Information Management System Architecture
  • The information management system 100 can incorporate a variety of different hardware and software components, which can in turn be organized with respect to one another in many different configurations, depending on the embodiment. There are critical design choices involved in specifying the functional responsibilities of the components and the role of each component in the information management system 100. For instance, as will be discussed, such design choices can impact performance as well as the adaptability of the information management system 100 to data growth or other changing circumstances.
  • FIG. 10 shows an information management system 100 designed according to these considerations and which includes: a central storage or information manager 140 configured to perform certain control functions, one or more data agents 142 executing on the client computing device(s) 102 configured to process primary data 112, and one or more media agents 144 executing on the one or more secondary storage computing devices 106 for performing tasks involving the secondary storage devices 108.
  • Storage Manager
  • As noted, the number of components in the information management system 100 and the amount of data under management can be quite large. Managing the components and data is therefore a significant task, and a task that can grow in an often unpredictable fashion as the quantity of components and data scale to meet the needs of the organization.
  • For these and other reasons, according to certain embodiments, responsibility for controlling the information management system 100, or at least a significant portion of that responsibility, is allocated to the storage manager 140.
  • By distributing control functionality in this manner, the storage manager 140 can be adapted independently according to changing circumstances. Moreover, a host computing device can be selected to best suit the functions of the storage manager 140. These and other advantages are described in further detail below with respect to FIG. 1D.
  • The storage manager 140 may be a software module or other application. The storage manager generally initiates, coordinates and/or controls storage and other information management operations performed by the information management system 100, e.g., to protect and control the primary data 112 and secondary copies 116 of data and metadata.
  • As shown by the dashed, arrowed lines, the storage manager 140 may communicate with and/or control some or all elements of the information management system 100, such as the data agents 142 and media agents 144. Thus, in certain embodiments, control information originates from the storage manager 140, whereas payload data and metadata is generally communicated between the data agents 142 and the media agents 144 (or otherwise between the client computing device(s) 102 and the secondary storage computing device(s) 106), e.g., at the direction of the storage manager 140. In other embodiments, some information management operations are controlled by other components in the information management system 100 (e.g., the media agent(s) 144 or data agent(s) 142), instead of or in combination with the storage manager 140.
  • According to certain embodiments, the storage manager provides one or more of the following functions:
      • initiating execution of secondary copy operations;
      • managing secondary storage devices 108 and inventory/capacity of the same;
      • allocating secondary storage devices 108 for secondary storage operations;
      • monitoring completion of and providing status reporting related to secondary storage operations;
      • tracking age information relating to secondary copies 116, secondary storage devices 108, and comparing the age information against retention guidelines;
      • tracking movement of data within the information management system 100;
      • tracking logical associations between components in the information management system 100;
      • protecting metadata associated with the information management system 100; and
      • implementing operations management functionality;
  • The storage manager 140 may maintain a database 146 of management-related data and information management policies 148. The database 146 may include a management index 150 or other data structure that stores logical associations between components of the system, user preferences and/or profiles (e.g., preferences regarding encryption, compression, or deduplication of primary or secondary copy data, preferences regarding the scheduling, type, or other aspects of primary or secondary copy or other operations, mappings of particular information management users or user accounts to certain computing devices or other components, etc.), management tasks, media containerization, or other useful data. For example, the storage manager 140 may use the index 150 to track logical associations between media agents 144 and secondary storage devices 108 and/or movement of data from primary storage devices 104 to secondary storage devices 108.
  • Administrators and other employees may be able to manually configure and initiate certain information management operations on an individual basis. But while this may be acceptable for some recovery operations or other relatively less frequent tasks, it is often not workable for implementing on-going organization-wide data protection and management.
  • Thus, the information management system 100 may utilize information management policies 148 for specifying and executing information management operations (e.g., on an automated basis). Generally, an information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with storage or other information management operations.
  • The storage manager database 146 may maintain the information management policies 148 and associated data, although the information management policies 148 can be stored in any appropriate location. For instance, a storage policy may be stored as metadata in a media agent database 152 or in a secondary storage device 108 (e.g., as an archive copy) for use in restore operations or other information management operations, depending on the embodiment. Information management policies 148 are described further below.
  • According to certain embodiments, the storage manager database 146 comprises a relational database (e.g., an SQL database) for tracking metadata, such as metadata associated with secondary copy operations (e.g., what client computing devices 102 and corresponding data were protected). This and other metadata may additionally be stored in other locations, such as at the secondary storage computing devices 106 or on the secondary storage devices 108, allowing data recovery without the use of the storage manager 140.
  • As shown, the storage manager 140 may include a jobs agent 156, a user interface 158, and a management agent 154, all of which may be implemented as interconnected software modules or application programs.
  • The jobs agent 156 in some embodiments initiates, controls, and/or monitors the status of some or all storage or other information management operations previously performed, currently being performed, or scheduled to be performed by the information management system 100. For instance, the jobs agent 156 may access information management policies 148 to determine when and how to initiate and control secondary copy and other information management operations, as will be discussed further.
  • The user interface 158 may include information processing and display software, such as a graphical user interface (“GUI”), an application program interface (“API”), or other interactive interface through which users and system processes can retrieve information about the status of information management operations (e.g., storage operations) or issue instructions to the information management system 100 and its constituent components.
  • The storage manager 140 may also track information that permits it to select, designate, or otherwise identify content indices, deduplication databases, or similar databases or resources or data sets within its information management cell (or another cell) to be searched in response to certain queries. Such queries may be entered by the user via interaction with the user interface 158.
  • Via the user interface 158, users may optionally issue instructions to the components in the information management system 100 regarding performance of storage and recovery operations. For example, a user may modify a schedule concerning the number of pending secondary copy operations. As another example, a user may employ the GUI to view the status of pending storage operations or to monitor the status of certain components in the information management system 100 (e.g., the amount of capacity left in a storage device).
  • In general, the management agent 154 allows multiple information management systems 100 to communicate with one another. For example, the information management system 100 in some cases may be one information management subsystem or “cell” of a network of multiple cells adjacent to one another or otherwise logically related in a WAN or LAN. With this arrangement, the cells may be connected to one another through respective management agents 154.
  • For instance, the management agent 154 can provide the storage manager 140 with the ability to communicate with other components within the information management system 100 (and/or other cells within a larger information management system) via network protocols and application programming interfaces (“APIs”) including, e.g., HTTP, HTTPS, FTP, REST, virtualization software APIs, cloud service provider APIs, and hosted service provider APIs. Inter-cell communication and hierarchy is described in greater detail in U.S. Pat. No. 7,035,880, which is incorporated by reference herein.
  • Data Agents
  • As discussed, a variety of different types of applications 110 can reside on a given client computing device 102, including operating systems, database applications, e-mail applications, and virtual machines, just to name a few. And, as part of the as part of the process of creating and restoring secondary copies 116, the client computing devices 102 may be tasked with processing and preparing the primary data 112 from these various different applications 110. Moreover, the nature of the processing/preparation can differ across clients and application types, e.g., due to inherent structural and formatting differences between applications 110.
  • The one or more data agent(s) 142 are therefore advantageously configured in some embodiments to assist in the performance of information management operations based on the type of data that is being protected, at a client-specific and/or application-specific level.
  • The data agent 142 may be a software module or component that is generally responsible for managing, initiating, or otherwise assisting in the performance of information management operations. For instance, the data agent 142 may take part in performing data storage operations such as the copying, archiving, migrating, replicating of primary data 112 stored in the primary storage device(s) 104. The data agent 142 may receive control information from the storage manager 140, such as commands to transfer copies of data objects, metadata, and other payload data to the media agents 144.
  • In some embodiments, a data agent 142 may be distributed between the client computing device 102 and storage manager 140 (and any other intermediate components) or may be deployed from a remote location or its functions approximated by a remote process that performs some or all of the functions of data agent 142. In addition, a data agent 142 may perform some functions provided by a media agent 144, e.g., encryption and deduplication.
  • As indicated, each data agent 142 may be specialized for a particular application 110, and the system can employ multiple data agents 142, each of which may backup, migrate, and recover data associated with a different application 110. For instance, different individual data agents 142 may be designed to handle Microsoft Exchange data, Lotus Notes data, Microsoft Windows file system data, Microsoft Active Directory Objects data, SQL Server data, SharePoint data, Oracle database data, SAP database data, virtual machines and/or associated data, and other types of data.
  • A file system data agent, for example, may handle data files and/or other file system information. If a client computing device 102 has two or more types of data, one data agent 142 may be used for each data type to copy, archive, migrate, and restore the client computing device 102 data. For example, to backup, migrate, and restore all of the data on a Microsoft Exchange server, the client computing device 102 may use one Microsoft Exchange Mailbox data agent 142 to backup the Exchange mailboxes, one Microsoft Exchange Database data agent 142 to backup the Exchange databases, one Microsoft Exchange Public Folder data agent 142 to backup the Exchange Public Folders, and one Microsoft Windows File System data agent 142 to backup the file system of the client computing device 102. In such embodiments, these data agents 142 may be treated as four separate data agents 142 even though they reside on the same client computing device 102.
  • Other embodiments may employ one or more generic data agents 142 that can handle and process data from two or more different applications 110, or that can handle and process multiple data types, instead of or in addition to using specialized data agents 142. For example, one generic data agent 142 may be used to back up, migrate and restore Microsoft Exchange Mailbox data and Microsoft Exchange Database data while another generic data agent may handle Microsoft Exchange Public Folder data and Microsoft Windows File System data.
  • Each data agent 142 may be configured to access data and/or metadata stored in the primary storage device(s) 104 associated with the data agent 142 and process the data as appropriate. For example, during a secondary copy operation, the data agent 142 may arrange or assemble the data and metadata into one or more files having a certain format (e.g., a particular backup or archive format) before transferring the file(s) to a media agent 144 or other component. The file(s) may include a list of files or other metadata. Each data agent 142 can also assist in restoring data or metadata to primary storage devices 104 from a secondary copy 116. For instance, the data agent 142 may operate in conjunction with the storage manager 140 and one or more of the media agents 144 to restore data from secondary storage device(s) 108.
  • Media Agents
  • As indicated above with respect to FIG. 1A, off-loading certain responsibilities from the client computing devices 102 to intermediary components such as the media agent(s) 144 can provide a number of benefits including improved client computing device 102 operation, faster secondary copy operation performance, and enhanced scalability. As one specific example which will be discussed below in further detail, the media agent 144 can act as a local cache of copied data and/or metadata that it has stored to the secondary storage device(s) 108, providing improved restore capabilities.
  • Generally speaking, a media agent 144 may be implemented as a software module that manages, coordinates, and facilitates the transmission of data, as directed by the storage manager 140, between a client computing device 102 and one or more secondary storage devices 108. Whereas the storage manager 140 controls the operation of the information management system 100, the media agent 144 generally provides a portal to secondary storage devices 108.
  • Media agents 144 can comprise logically and/or physically separate nodes in the information management system 100 (e.g., separate from the client computing devices 102, storage manager 140, and/or secondary storage devices 108). In addition, each media agent 144 may reside on a dedicated secondary storage computing device 106 in some cases, while in other embodiments a plurality of media agents 144 reside on the same secondary storage computing device 106.
  • A media agent 144 (and corresponding media agent database 152) may be considered to be “associated with” a particular secondary storage device 108 if that media agent 144 is capable of one or more of: routing and/or storing data to the particular secondary storage device 108, coordinating the routing and/or storing of data to the particular secondary storage device 108, retrieving data from the particular secondary storage device 108, and coordinating the retrieval of data from a particular secondary storage device 108.
  • While media agent(s) 144 are generally associated with one or more secondary storage devices 108, the media agents 144 in certain embodiments are physically separate from the secondary storage devices 108. For instance, the media agents 144 may reside on secondary storage computing devices 106 having different housings or packages than the secondary storage devices 108. In one example, a media agent 144 resides on a first server computer and is in communication with a secondary storage device(s) 108 residing in a separate, rack-mounted RAID-based system.
  • In operation, a media agent 144 associated with a particular secondary storage device 108 may instruct the secondary storage device 108 (e.g., a tape library) to use a robotic arm or other retrieval means to load or eject a certain storage media, and to subsequently archive, migrate, or retrieve data to or from that media, e.g., for the purpose of restoring the data to a client computing device 102. The media agent 144 may communicate with a secondary storage device 108 via a suitable communications link, such as a SCSI or Fiber Channel link.
  • As shown, each media agent 144 may maintain an associated media agent database 152. The media agent database 152 may be stored in a disk or other storage device (not shown) that is local to the secondary storage computing device 106 on which the media agent 144 resides. In other cases, the media agent database 152 is stored remotely from the secondary storage computing device 106.
  • The media agent database 152 can include, among other things, an index 153 including data generated during secondary copy operations and other storage or information management operations. The index 153 provides a media agent 144 or other component with a fast and efficient mechanism for locating secondary copies 116 or other data stored in the secondary storage devices 108. In one configuration, a storage manager index 150 or other data structure may store data associating a client computing device 102 with a particular media agent 144 and/or secondary storage device 108, as specified in a storage policy. A media agent index 153 or other data structure associated with the particular media agent 144 may in turn include information about the stored data.
  • For instance, for each secondary copy 116, the index 153 may include metadata such as a list of the data objects (e.g., files/subdirectories, database objects, mailbox objects, etc.), a path to the secondary copy 116 on the corresponding secondary storage device 108, location information indicating where the data objects are stored in the secondary storage device 108, when the data objects were created or modified, etc. Thus, the index 153 includes metadata associated with the secondary copies 116 that is readily available for use in storage operations and other activities without having to be first retrieved from the secondary storage device 108. In yet further embodiments, some or all of the data in the index 153 may instead or additionally be stored along with the data in a secondary storage device 108, e.g., with a copy of the index 153.
  • Because the index 153 maintained in the database 152 may operate as a cache, it can also be referred to as an index cache. In such cases, information stored in the index cache 153 typically comprises data that reflects certain particulars about storage operations that have occurred relatively recently. After some triggering event, such as after a certain period of time elapses, or the index cache 153 reaches a particular size, the index cache 153 may be copied or migrated to a secondary storage device(s) 108. This information may need to be retrieved and uploaded back into the index cache 153 or otherwise restored to a media agent 144 to facilitate retrieval of data from the secondary storage device(s) 108. In some embodiments, the cached information may include format or containerization information related to archives or other files stored on the storage device(s) 108. In this manner, the index cache 153 allows for accelerated restores.
  • In some alternative embodiments the media agent 144 generally acts as a coordinator or facilitator of storage operations between client computing devices 102 and corresponding secondary storage devices 108, but does not actually write the data to the secondary storage device 108. For instance, the storage manager 140 (or the media agent 144) may instruct a client computing device 102 and secondary storage device 108 to communicate with one another directly. In such a case the client computing device 102 transmits the data directly to the secondary storage device 108 according to the received instructions, and vice versa. In some such cases, the media agent 144 may still receive, process, and/or maintain metadata related to the storage operations. Moreover, in these embodiments, the payload data can flow through the media agent 144 for the purposes of populating the index cache 153 maintained in the media agent database 152, but not for writing to the secondary storage device 108.
  • The media agent 144 and/or other components such as the storage manager 140 may in some cases incorporate additional functionality, such as data classification, content indexing, deduplication, encryption, compression, and the like. Further details regarding these and other functions are described below.
  • Distributed, Scalable Architecture
  • As described, certain functions of the information management system 100 can be distributed amongst various physical and/or logical components in the system. For instance, one or more of the storage manager 140, data agents 142, and media agents 144 may reside on computing devices that are physically separate from one another. This architecture can provide a number of benefits.
  • For instance, hardware and software design choices for each distributed component can be targeted to suit its particular function. The secondary computing devices 106 on which the media agents 144 reside can be tailored for interaction with associated secondary storage devices 108 and provide fast index cache operation, among other specific tasks. Similarly, the client computing device(s) 102 can be selected to effectively service the applications 110 residing thereon, in order to efficiently produce and store primary data 112.
  • Moreover, in some cases, one or more of the individual components in the information management system 100 can be distributed to multiple, separate computing devices. As one example, for large file systems where the amount of data stored in the storage management database 146 is relatively large, the management database 146 may be migrated to or otherwise reside on a specialized database server (e.g., an SQL server) separate from a server that implements the other functions of the storage manager 140. This configuration can provide added protection because the database 146 can be protected with standard database utilities (e.g., SQL log shipping or database replication) independent from other functions of the storage manager 140. The database 146 can be efficiently replicated to a remote site for use in the event of a disaster or other data loss incident at the primary site. Or the database 146 can be replicated to another computing device within the same site, such as to a higher performance machine in the event that a storage manager host device can no longer service the needs of a growing information management system 100.
  • The distributed architecture also provides both scalability and efficient component utilization. FIG. 1D shows an embodiment of the information management system 100 including a plurality of client computing devices 102 and associated data agents 142 as well as a plurality of secondary storage computing devices 106 and associated media agents 144.
  • Additional components can be added or subtracted based on the evolving needs of the information management system 100. For instance, depending on where bottlenecks are identified, administrators can add additional client computing devices 102, secondary storage devices 106 (and corresponding media agents 144), and/or secondary storage devices 108.
  • Moreover, each client computing device 102 in some embodiments can communicate with any of the media agents 144, e.g., as directed by the storage manager 140. And each media agent 144 may be able to communicate with any of the secondary storage devices 108, e.g., as directed by the storage manager 140. Thus, operations can be routed to the secondary storage devices 108 in a dynamic and highly flexible manner. Further examples of scalable systems capable of dynamic storage operations are provided in U.S. Pat. No. 7,246,207, which is incorporated by reference herein.
  • In alternative configurations, certain components are not distributed and may instead reside and execute on the same computing device. For example, in some embodiments one or more data agents 142 and the storage manager 140 reside on the same client computing device 102. In another embodiment, one or more data agents 142 and one or more media agents 144 reside on a single computing device.
  • Exemplary Types of Information Management Operations
  • In order to protect and leverage stored data, the information management system 100 can be configured to perform a variety of information management operations. As will be described, these operations can generally include secondary copy and other data movement operations, processing and data manipulation operations, and management operations.
  • Data Movement Operations
  • Data movement operations according to certain embodiments are generally operations that involve the copying or migration of data (e.g., payload data) between different locations in the information management system 100. For example, data movement operations can include operations in which stored data is copied, migrated, or otherwise transferred from primary storage device(s) 104 to secondary storage device(s) 108, from secondary storage device(s) 108 to different secondary storage device(s) 108, or from primary storage device(s) 104 to different primary storage device(s) 104.
  • Data movement operations can include by way of example, backup operations, archive operations, information lifecycle management operations such as hierarchical storage management operations, replication operations (e.g., continuous data replication operations), snapshot operations, deduplication operations, single-instancing operations, auxiliary copy operations, and the like. As will be discussed, some of these operations involve the copying, migration or other movement of data, without actually creating multiple, distinct copies. Nonetheless, some or all of these operations are referred to as “copy” operations for simplicity.
  • Backup Operations
  • A backup operation creates a copy of primary data 112 at a particular point in time. Each subsequent backup copy may be maintained independently of the first. Further, a backup copy in some embodiments is stored in a backup format. This can be in contrast to the version in primary data 112 from which the backup copy is derived, and which may instead be stored in a native format of the source application(s) 110. In various cases, backup copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format. For example, a backup copy may be stored in a backup format that facilitates compression and/or efficient long-term storage.
  • Backup copies can have relatively long retention periods as compared to primary data 112, and may be stored on media with slower retrieval times than primary data 112 and certain other types of secondary copies 116. On the other hand, backups may have relatively shorter retention periods than some other types of secondary copies 116, such as archive copies (described below). Backups may sometimes be stored at on offsite location.
  • Backup operations can include full, synthetic or incremental backups. A full backup in some embodiments is generally a complete image of the data to be protected. However, because full backup copies can consume a relatively large amount of storage, it can be useful to use a full backup copy as a baseline and only store changes relative to the full backup copy for subsequent backup copies.
  • For instance, a differential backup operation (or cumulative incremental backup operation) tracks and stores changes that have occurred since the last full backup. Differential backups can grow quickly in size, but can provide relatively efficient restore times because a restore can be completed in some cases using only the full backup copy and the latest differential copy.
  • An incremental backup operation generally tracks and stores changes since the most recent backup copy of any type, which can greatly reduce storage utilization. In some cases, however, restore times can be relatively long in comparison to full or differential backups because completing a restore operation may involve accessing a full backup in addition to multiple incremental backups.
  • Any of the above types of backup operations can be at the file-level, e.g., where the information management system 100 generally tracks changes to files at the file-level, and includes copies of files in the backup copy. In other cases, block-level backups are employed, where files are broken into constituent blocks, and changes are tracked at the block-level. Upon restore, the information management system 100 reassembles the blocks into files in a transparent fashion.
  • Far less data may actually be transferred and copied to the secondary storage devices 108 during a block-level copy than during a file-level copy, resulting in faster execution times. However, when restoring a block-level copy, the process of locating constituent blocks can sometimes result in longer restore times as compared to file-level backups. Similar to backup operations, the other types of secondary copy operations described herein can also be implemented at either the file-level or the block-level.
  • Archive Operations
  • Because backup operations generally involve maintaining a version of the copied data in primary data 112 and also maintaining backup copies in secondary storage device(s) 108, they can consume significant storage capacity. To help reduce storage consumption, an archive operation according to certain embodiments creates a secondary copy 116 by both copying and removing source data. Or, seen another way, archive operations can involve moving some or all of the source data to the archive destination. Thus, data satisfying criteria for removal (e.g., data of a threshold age or size) from the source copy may be removed from source storage. Archive copies are sometimes stored in an archive format or other non-native application format. The source data may be primary data 112 or a secondary copy 116, depending on the situation. As with backup copies, archive copies can be stored in a format in which the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format.
  • In addition, archive copies may be retained for relatively long periods of time (e.g., years) and, in some cases, are never deleted. Archive copies are generally retained for longer periods of time than backup copies, for example. In certain embodiments, archive copies may be made and kept for extended periods in order to meet compliance regulations.
  • Moreover, when primary data 112 is archived, in some cases the archived primary data 112 or a portion thereof is deleted when creating the archive copy. Thus, archiving can serve the purpose of freeing up space in the primary storage device(s) 104. Similarly, when a secondary copy 116 is archived, the secondary copy 116 may be deleted, and an archive copy can therefore serve the purpose of freeing up space in secondary storage device(s) 108. In contrast, source copies often remain intact when creating backup copies.
  • Snapshot Operations
  • Snapshot operations can provide a relatively lightweight, efficient mechanism for protecting data. From an end-user viewpoint, a snapshot may be thought of as an “instant” image of the primary data 112 at a given point in time. In one embodiment, a snapshot may generally capture the directory structure of an object in primary data 112 such as a file or volume or other data set at a particular moment in time and may also preserve file attributes and contents. A snapshot in some cases is created relatively quickly, e.g., substantially instantly, using a minimum amount of file space, but may still function as a conventional file system backup.
  • A snapshot copy in many cases can be made quickly and without significantly impacting primary computing resources because large amounts of data need not be copied or moved. In some embodiments, a snapshot may exist as a virtual file system, parallel to the actual file system. Users in some cases gain read-only access to the record of files and directories of the snapshot. By electing to restore primary data 112 from a snapshot taken at a given point in time, users may also return the current file system to the state of the file system that existed when the snapshot was taken.
  • Some types of snapshots do not actually create another physical copy of all the data as it existed at the particular point in time, but may simply create pointers that are able to map files and directories to specific memory locations (e.g., disk blocks) where the data resides, as it existed at the particular point in time. For example, a snapshot copy may include a set of pointers derived from the file system or an application. Each pointer points to a respective stored data block, so collectively, the set of pointers reflect the storage location and state of the data object (e.g., file(s) or volume(s) or data set(s)) at a particular point in time when the snapshot copy was created.
  • In some embodiments, once a snapshot has been taken, subsequent changes to the file system typically do not overwrite the blocks in use at the time of the snapshot. Therefore, the initial snapshot may use only a small amount of disk space needed to record a mapping or other data structure representing or otherwise tracking the blocks that correspond to the current state of the file system. Additional disk space is usually required only when files and directories are actually modified later. Furthermore, when files are modified, typically only the pointers which map to blocks are copied, not the blocks themselves. In some embodiments, for example in the case of “copy-on-write” snapshots, when a block changes in primary storage, the block is copied to secondary storage or cached in primary storage before the block is overwritten in primary storage. The snapshot mapping of file system data is also updated to reflect the changed block(s) at that particular point in time. In some other cases, a snapshot includes a full physical copy of all or substantially all of the data represented by the snapshot. Further examples of snapshot operations are provided in U.S. Pat. No. 7,529,782, which is incorporated by reference herein.
  • Replication Operations
  • Another type of secondary copy operation is a replication operation. Some types of secondary copies 116 are used to periodically capture images of primary data 112 at particular points in time (e.g., backups, archives, and snapshots). However, it can also be useful for recovery purposes to protect primary data 112 in a more continuous fashion, by replicating the primary data 112 substantially as changes occur. In some cases a replication copy can be a mirror copy, for instance, where changes made to primary data 112 are mirrored to another location (e.g., to secondary storage device(s) 108). By copying each write operation to the replication copy, two storage systems are kept synchronized or substantially synchronized so that they are virtually identical at approximately the same time. Where entire disk volumes are mirrored, however, mirroring can require significant amount of storage space and utilizes a large amount of processing resources.
  • According to some embodiments storage operations are performed on replicated data that represents a recoverable state, or “known good state” of a particular application running on the source system. For instance, in certain embodiments, known good replication copies may be viewed as copies of primary data 112. This feature allows the system to directly access, copy, restore, backup or otherwise manipulate the replication copies as if the data was the “live”, primary data 112. This can reduce access time, storage utilization, and impact on source applications 110, among other benefits.
  • Based on known good state information, the information management system 100 can replicate sections of application data that represent a recoverable state rather than rote copying of blocks of data. Examples of compatible replication operations (e.g., continuous data replication) are provided in U.S. Pat. No. 7,617,262, which is incorporated by reference herein.
  • Deduplication/Single-Instancing Operations
  • Another type of data movement operation is deduplication, which is useful to reduce the amount of data within the system. For instance, some or all of the above-described secondary storage operations can involve deduplication in some fashion. New data is read, broken down into blocks (e.g., sub-file level blocks) of a selected granularity, compared with blocks that are already stored, and only the new blocks are stored. Blocks that already exist are represented as pointers to the already stored data.
  • In order to stream-line the comparison process, the information management system 100 may calculate and/or store signatures (e.g., hashes) corresponding to the individual data blocks and compare the hashes instead of comparing entire data blocks. In some cases, only a single instance of each element is stored, and deduplication operations may therefore be referred to interchangeably as “single-instancing” operations. Depending on the implementation, however, deduplication or single-instancing operations can store more than one instance of certain data blocks, but nonetheless significantly reduce data redundancy. Moreover, single-instancing in some cases is distinguished from deduplication as a process of analyzing and reducing data at the file level, rather than the sub-file level.
  • Depending on the embodiment, deduplication blocks can be of fixed or variable length. Using variable length blocks can provide enhanced deduplication by responding to changes in the data stream, but can involve complex processing. In some cases, the information management system 100 utilizes a technique for dynamically aligning deduplication blocks (e.g., fixed-length blocks) based on changing content in the data stream, as described in U.S. Pat. Pub. No. 2012/0084269, which is incorporated by reference herein.
  • The information management system 100 can perform deduplication in a variety of manners at a variety of locations in the information management system 100. For instance, in some embodiments, the information management system 100 implements “target-side” deduplication by deduplicating data (e.g., secondary copies 116) stored in the secondary storage devices 108. In some such cases, the media agents 144 are generally configured to manage the deduplication process. For instance, one or more of the media agents 144 maintain a corresponding deduplication database that stores deduplication information (e.g., datablock signatures). Examples of such a configuration are provided in U.S. Pat. Pub. No. 2012/0150826, which is incorporated by reference herein. Deduplication can also be performed on the “source-side” (or “client-side”), e.g., to reduce the amount of traffic between the media agents 144 and the client computing device(s) 102 and/or reduce redundant data stored in the primary storage devices 104. Examples of such deduplication techniques are provided in U.S. Pat. Pub. No. 2012/0150818, which is incorporated by reference herein.
  • Information Lifecycle Management and Hierarchical Storage Management Operations
  • In some embodiments, files and other data over their lifetime move from more expensive, quick access storage to less expensive, slower access storage. Operations associated with moving data through various tiers of storage are sometimes referred to as information lifecycle management (ILM) operations.
  • One type of ILM operation is a hierarchical storage management (HSM) operation. A HSM operation is generally an operation for automatically moving data between classes of storage devices, such as between high-cost and low-cost storage devices. For instance, an HSM operation may involve movement of data from primary storage devices 104 to secondary storage devices 108, or between tiers of secondary storage devices 108. With each tier, the storage devices may be progressively relatively cheaper, have relatively slower access/restore times, etc. For example, movement of data between tiers may occur as data becomes less important over time.
  • In some embodiments, an HSM operation is similar to an archive operation in that creating an HSM copy may (though not always) involve deleting some of the source data. For example, an HSM copy may include data from primary data 112 or a secondary copy 116 that is larger than a given size threshold or older than a given age threshold and that is stored in a backup format.
  • Often, and unlike some types of archive copies, HSM data that is removed or aged from the source copy is replaced by a logical reference pointer or stub. The reference pointer or stub can be stored in the primary storage device 104 to replace the deleted data in primary data 112 (or other source copy) and to point to or otherwise indicate the new location in a secondary storage device 108.
  • According to one example, files are generally moved between higher and lower cost storage depending on how often the files are accessed. When a user requests access to the HSM data that has been removed or migrated, the information management system 100 uses the stub to locate the data and often make recovery of the data appear transparent, even though the HSM data may be stored at a location different from the remaining source data. The stub may also include some metadata associated with the corresponding data, so that a file system and/or application can provide some information about the data object and/or a limited-functionality version (e.g., a preview) of the data object.
  • An HSM copy may be stored in a format other than the native application format (e.g., where the data is compressed, encrypted, deduplicated, and/or otherwise modified from the original application format). In some cases, copies which involve the removal of data from source storage and the maintenance of stub or other logical reference information on source storage may be referred to generally as “on-line archive copies”. On the other hand, copies which involve the removal of data from source storage without the maintenance of stub or other logical reference information on source storage may be referred to as “off-line archive copies”.
  • Auxiliary Copy and Disaster Recovery Operations
  • An auxiliary copy is generally a copy operation in which a copy is created of an existing secondary copy 116. For instance, an initial or “primary” secondary copy 116 may be generated using or otherwise be derived from primary data 112, whereas an auxiliary copy is generated from the initial secondary copy 116. Auxiliary copies can be used to create additional standby copies of data and may reside on different secondary storage devices 108 than initial secondary copies 116. Thus, auxiliary copies can be used for recovery purposes if initial secondary copies 116 become unavailable. Exemplary compatible auxiliary copy techniques are described in further detail in U.S. Pat. No. 8,230,195, which is incorporated by reference herein.
  • The information management system 100 may also perform disaster recovery operations that make or retain disaster recovery copies, often as secondary, high-availability disk copies. The information management system 100 may create secondary disk copies and store the copies at disaster recovery locations using auxiliary copy or replication operations, such as continuous data replication technologies. Depending on the particular data protection goals, disaster recovery locations can be remote from the client computing devices 102 and primary storage devices 104, remote from some or all of the secondary storage devices 108, or both.
  • Data Processing and Manipulation Operations
  • As indicated, the information management system 100 can also be configured to implement certain data manipulation operations, which according to certain embodiments are generally operations involving the processing or modification of stored data. Some data manipulation operations include content indexing operations and classification operations can be useful in leveraging the data under management to provide enhanced search and other features. Other data manipulation operations such as compression and encryption can provide data reduction and security benefits, respectively.
  • Data manipulation operations can be different than data movement operations in that they do not necessarily involve the copying, migration or other transfer of data (e.g., primary data 112 or secondary copies 116) between different locations in the system. For instance, data manipulation operations may involve processing (e.g., offline processing) or modification of already stored primary data 112 and/or secondary copies 116. However, in some embodiments data manipulation operations are performed in conjunction with data movement operations. As one example, the information management system 100 may encrypt data while performing an archive operation.
  • Content Indexing
  • In some embodiments, the information management system 100 “content indexes” data stored within the primary data 112 and/or secondary copies 116, providing enhanced search capabilities for data discovery and other purposes. The content indexing can be used to identify files or other data objects having pre-defined content (e.g., user-defined keywords or phrases), metadata (e.g., email metadata such as “to”, “from”, “cc”, “bcc”, attachment name, received time, etc.).
  • The information management system 100 generally organizes and catalogues the results in a content index, which may be stored within the media agent database 152, for example. The content index can also include the storage locations of (or pointer references to) the indexed data in the primary data 112 or secondary copies 116, as appropriate. The results may also be stored, in the form of a content index database or otherwise, elsewhere in the information management system 100 (e.g., in the primary storage devices 104, or in the secondary storage device 108). Such index data provides the storage manager 140 or another component with an efficient mechanism for locating primary data 112 and/or secondary copies 116 of data objects that match particular criteria.
  • For instance, search criteria can be specified by a user through user interface 158 of the storage manager 140. In some cases, the information management system 100 analyzes data and/or metadata in secondary copies 116 to create an “off-line” content index, without significantly impacting the performance of the client computing devices 102. Depending on the embodiment, the system can also implement “on-line” content indexing, e.g., of primary data 112. Examples of compatible content indexing techniques are provided in U.S. Pat. No. 8,170,995, which is incorporated by reference herein.
  • Classification Operations—Metabase
  • In order to help leverage the data stored in the information management system 100, one or more components can be configured to scan data and/or associated metadata for classification purposes to populate a metabase of information. Such scanned, classified data and/or metadata may be included in a separate database and/or on a separate storage device from primary data 112 (and/or secondary copies 116), such that metabase related operations do not significantly impact performance on other components in the information management system 100.
  • In other cases, the metabase(s) may be stored along with primary data 112 and/or secondary copies 116. Files or other data objects can be associated with user-specified identifiers (e.g., tag entries) in the media agent 144 (or other indices) to facilitate searches of stored data objects. Among a number of other benefits, the metabase can also allow efficient, automatic identification of files or other data objects to associate with secondary copy or other information management operations (e.g., in lieu of scanning an entire file system). Examples of compatible metabases and data classification operations are provided in U.S. Pat. Nos. 8,229,954 and 7,747,579, which are incorporated by reference herein.
  • Encryption Operations
  • The information management system 100 in some cases is configured to process data (e.g., files or other data objects, secondary copies 116, etc.), according to an appropriate encryption algorithm (e.g., Blowfish, Advanced Encryption Standard [AES], Triple Data Encryption Standard [3-DES], etc.) to limit access and provide data security in the information management system 100.
  • The information management system 100 in some cases encrypts the data at the client level, such that the client computing devices 102 (e.g., the data agents 142) encrypt the data prior to forwarding the data to other components, e.g., before sending the data media agents 144 during a secondary copy operation. In such cases, the client computing device 102 may maintain or have access to an encryption key or passphrase for decrypting the data upon restore. Encryption can also occur when creating copies of secondary copies, e.g., when creating auxiliary copies. In yet further embodiments, the secondary storage devices 108 can implement built-in, high performance hardware encryption.
  • Management Operations
  • Certain embodiments leverage the integrated, ubiquitous nature of the information management system 100 to provide useful system-wide management functions. As two non-limiting examples, the information management system 100 can be configured to implement operations management and e-discovery functions.
  • Operations management can generally include monitoring and managing the health and performance of information management system 100 by, without limitation, performing error tracking, generating granular storage/performance metrics (e.g., job success/failure information, deduplication efficiency, etc.), generating storage modeling and costing information, and the like.
  • Such information can be provided to users via the user interface 158 in a single, integrated view. For instance, the integrated user interface 158 can include an option to show a “virtual view” of the system that graphically depicts the various components in the system using appropriate icons. The operations management functionality can facilitate planning and decision-making. For example, in some embodiments, a user may view the status of some or all jobs as well as the status of each component of the information management system 100. Users may then plan and make decisions based on this data. For instance, a user may view high-level information regarding storage operations for the information management system 100, such as job status, component status, resource status (e.g., network pathways, etc.), and other information. The user may also drill down or use other means to obtain more detailed information regarding a particular component, job, or the like.
  • In some cases the information management system 100 alerts a user such as a system administrator when a particular resource is unavailable or congested. For example, a particular primary storage device 104 or secondary storage device 108 might be full or require additional capacity. Or a component may be unavailable due to hardware failure, software problems, or other reasons. In response, the information management system 100 may suggest solutions to such problems when they occur (or provide a warning prior to occurrence). For example, the storage manager 140 may alert the user that a secondary storage device 108 is full or otherwise congested. The storage manager 140 may then suggest, based on job and data storage information contained in its database 146, an alternate secondary storage device 108.
  • Other types of corrective actions may include suggesting an alternate data path to a particular primary or secondary storage device 104, 108, or dividing data to be stored among various available primary or secondary storage devices 104, 108 as a load balancing measure or to otherwise optimize storage or retrieval time. Such suggestions or corrective actions may be performed automatically, if desired. Further examples of some compatible operations management techniques and of interfaces providing an integrated view of an information management system are provided in U.S. Pat. No. 7,343,453, which is incorporated by reference herein. In some embodiments, the storage manager 140 implements the operations management functions described herein.
  • The information management system 100 can also be configured to perform system-wide e-discovery operations in some embodiments. In general, e-discovery operations provide a unified collection and search capability for data in the system, such as data stored in the secondary storage devices 108 (e.g., backups, archives, or other secondary copies 116). For example, the information management system 100 may construct and maintain a virtual repository for data stored in the information management system 100 that is integrated across source applications 110, different storage device types, etc. According to some embodiments, e-discovery utilizes other techniques described herein, such as data classification and/or content indexing.
  • Information Management Policies
  • As indicated previously, an information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with secondary copy or other information management operations.
  • One type of information management policy 148 is a storage policy. According to certain embodiments, a storage policy generally comprises a logical container that defines (or includes information sufficient to determine) one or more of the following items: (1) what data will be associated with the storage policy; (2) a destination to which the data will be stored; (3) datapath information specifying how the data will be communicated to the destination; (4) the type of storage operation to be performed; and (5) retention information specifying how long the data will be retained at the destination.
  • Data associated with a storage policy can be logically organized into groups, which can be referred to as “sub-clients”. A sub-client may represent static or dynamic associations of portions of a data volume. Sub-clients may represent mutually exclusive portions. Thus, in certain embodiments, a portion of data may be given a label and the association is stored as a static entity in an index, database or other storage location.
  • Sub-clients may also be used as an effective administrative scheme of organizing data according to data type, department within the enterprise, storage preferences, or the like. Depending on the configuration, sub-clients can correspond to files, folders, virtual machines, databases, etc. In one exemplary scenario, an administrator may find it preferable to separate e-mail data from financial data using two different sub-clients.
  • A storage policy can define where data is stored by specifying a target or destination storage device (or group of storage devices). For instance, where the secondary storage device 108 includes a group of disk libraries, the storage policy may specify a particular disk library for storing the sub-clients associated with the policy. As another example, where the secondary storage devices 108 include one or more tape libraries, the storage policy may specify a particular tape library for storing the sub-clients associated with the storage policy, and may also specify a drive pool and a tape pool defining a group of tape drives and a group of tapes, respectively, for use in storing the sub-client data.
  • Datapath information can also be included in the storage policy. For instance, the storage policy may specify network pathways and components to utilize when moving the data to the destination storage device(s). In some embodiments, the storage policy specifies one or more media agents 144 for conveying data (e.g., one or more sub-clients) associated with the storage policy between the source (e.g., one or more host client computing devices 102) and destination (e.g., a particular target secondary storage device 108).
  • A storage policy can also specify the type(s) of operations associated with the storage policy, such as a backup, archive, snapshot, auxiliary copy, or the like. Retention information can specify how long the data will be kept, depending on organizational needs (e.g., a number of days, months, years, etc.)
  • The information management policies 148 may also include one or more scheduling policies specifying when and how often to perform operations. Scheduling information may specify with what frequency (e.g., hourly, weekly, daily, event-based, etc.) or under what triggering conditions secondary copy or other information management operations will take place. Scheduling policies in some cases are associated with particular components, such as particular sub-clients, client computing device 102, and the like. In one configuration, a separate scheduling policy is maintained for particular sub-clients on a client computing device 102. The scheduling policy specifies that those sub-clients are to be moved to secondary storage devices 108 every hour according to storage policies associated with the respective sub-clients.
  • When adding a new client computing device 102, administrators can manually configure information management policies 148 and/or other settings, e.g., via the user interface 158. However, this can be an involved process resulting in delays, and it may be desirable to begin data protecting operations quickly.
  • Thus, in some embodiments, the information management system 100 automatically applies a default configuration to client computing device 102. As one example, when a data agent(s) 142 is installed on a client computing devices 102, the installation script may register the client computing device 102 with the storage manager 140, which in turn applies the default configuration to the new client computing device 102. In this manner, data protection operations can begin substantially immediately. The default configuration can include a default storage policy, for example, and can specify any appropriate information sufficient to begin data protection operations. This can include a type of data protection operation, scheduling information, a target secondary storage device 108, data path information (e.g., a particular media agent 144), and the like.
  • Other types of information management policies 148 are possible. For instance, the information management policies 148 can also include one or more audit or security policies. An audit policy is a set of preferences, rules and/or criteria that protect sensitive data in the information management system 100. For example, an audit policy may define “sensitive objects” as files or objects that contain particular keywords (e.g. “confidential,” or “privileged”) and/or are associated with particular keywords (e.g., in metadata) or particular flags (e.g., in metadata identifying a document or email as personal, confidential, etc.).
  • An audit policy may further specify rules for handling sensitive objects. As an example, an audit policy may require that a reviewer approve the transfer of any sensitive objects to a cloud storage site, and that if approval is denied for a particular sensitive object, the sensitive object should be transferred to a local storage device 104 instead. To facilitate this approval, the audit policy may further specify how a secondary storage computing device 106 or other system component should notify a reviewer that a sensitive object is slated for transfer.
  • In some implementations, the information management policies 148 may include one or more provisioning policies. A provisioning policy can include a set of preferences, priorities, rules, and/or criteria that specify how clients 102 (or groups thereof) may utilize system resources, such as available storage on cloud storage and/or network bandwidth. A provisioning policy specifies, for example, data quotas for particular client computing devices 102 (e.g. a number of gigabytes that can be stored monthly, quarterly or annually). The storage manager 140 or other components may enforce the provisioning policy. For instance, the media agents 144 may enforce the policy when transferring data to secondary storage devices 108. If a client computing device 102 exceeds a quota, a budget for the client computing device 102 (or associated department) is adjusted accordingly or an alert may trigger.
  • While the above types of information management policies 148 have been described as separate policies, one or more of these can be generally combined into a single information management policy 148. For instance, a storage policy may also include or otherwise be associated with one or more scheduling, audit, or provisioning policies. Moreover, while storage policies are typically associated with moving and storing data, other policies may be associated with other types of information management operations. The following is a non-exhaustive list of items the information management policies 148 may specify:
      • schedules or other timing information, e.g., specifying when and/or how often to perform information management operations;
      • the type of secondary copy 116 and/or secondary copy format (e.g., snapshot, backup, archive, HSM, etc.);
      • a location or a class or quality of storage for storing secondary copies 116 (e.g., one or more particular secondary storage devices 108);
      • preferences regarding whether and how to encrypt, compress, deduplicate, or otherwise modify or transform secondary copies 116;
      • which system components and/or network pathways (e.g., preferred media agents 144) 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; and
      • retention information specifying the length of time primary data 112 and/or secondary copies 116 should be retained, e.g., in a particular class or tier of storage devices, or within the information management system 100.
  • 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 data 112 or a secondary copy 116 of 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 devices 108);
      • the identity of users, applications 110, client computing devices 102 and/or other computing devices that created, accessed, modified, or otherwise utilized primary data 112 or secondary copies 116;
      • 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; and
      • the content of a particular data object (e.g., its textual content) or of metadata associated with the data object.
    Exemplary Storage Policy and Secondary Storage Operations
  • FIG. 1E shows a data flow data diagram depicting performance of storage operations by an embodiment of an information management system 100, according to an exemplary data storage policy 148A. The information management system 100 includes a storage manger 140, a client computing device 102 having a file system data agent 142A and an email data agent 1428 residing thereon, a primary storage device 104, two media agents 144A, 144B, and two secondary storage devices 108A, 108B: a disk library 108A and a tape library 1088. As shown, the primary storage device 104 includes primary data 112A, 112B associated with a file system sub-client and an email sub-client, respectively.
  • As indicated by the dashed box, the second media agent 1448 and the tape library 1088 are “off-site”, and may therefore be remotely located from the other components in the information management system 100 (e.g., in a different city, office building, etc.). In this manner, information stored on the tape library 1088 may provide protection in the event of a disaster or other failure.
  • The file system sub-client and its associated primary data 112A in certain embodiments generally comprise information generated by the file system and/or operating system of the client computing device 102, and can include, for example, file system data (e.g., regular files, file tables, mount points, etc.), operating system data (e.g., registries, event logs, etc.), and the like. The e-mail sub-client, on the other hand, and its associated primary data 1128, include data generated by an e-mail client application operating on the client computing device 102, and can include mailbox information, folder information, emails, attachments, associated database information, and the like. As described above, the sub-clients can be logical containers, and the data included in the corresponding primary data 112A, 1128 may or may not be stored contiguously.
  • The exemplary storage policy 148A includes a backup copy rule set 160, a disaster recovery copy rule set 162, and a compliance copy rule set 164. The backup copy rule set 160 specifies that it is associated with a file system sub-client 166 and an email sub-client 168. Each of these sub-clients 166, 168 are associated with the particular client computing device 102. The backup copy rule set 160 further specifies that the backup operation will be written to the disk library 108A, and designates a particular media agent 144A to convey the data to the disk library 108A. Finally, the backup copy rule set 160 specifies that backup copies created according to the rule set 160 are scheduled to be generated on an hourly basis and to be retained for 30 days. In some other embodiments, scheduling information is not included in the storage policy 148A, and is instead specified by a separate scheduling policy.
  • The disaster recovery copy rule set 162 is associated with the same two sub-clients 166, 168. However, the disaster recovery copy rule set 162 is associated with the tape library 108B, unlike the backup copy rule set 160. Moreover, the disaster recovery copy rule set 162 specifies that a different media agent 144B than the media agent 144A associated with the backup copy rule set 160 will be used to convey the data to the tape library 1088. As indicated, disaster recovery copies created according to the rule set 162 will be retained for 60 days, and will be generated on a daily basis. Disaster recovery copies generated according to the disaster recovery copy rule set 162 can provide protection in the event of a disaster or other data-loss event that would affect the backup copy 116A maintained on the disk library 108A.
  • The compliance copy rule set 164 is only associated with the email sub-client 166, and not the file system sub-client 168. Compliance copies generated according to the compliance copy rule set 164 will therefore not include primary data 112A from the file system sub-client 166. For instance, the organization may be under an obligation to store maintain copies of email data for a particular period of time (e.g., 10 years) to comply with state or federal regulations, while similar regulations do not apply to the file system data. The compliance copy rule set 164 is associated with the same tape library 108B and media agent 144B as the disaster recovery copy rule set 162, although a different storage device or media agent could be used in other embodiments. Finally, the compliance copy rule set 164 specifies that copies generated under the compliance copy rule set 164 will be retained for 10 years, and will be generated on a quarterly basis.
  • At step 1, the storage manager 140 initiates a backup operation according to the backup copy rule set 160. For instance, a scheduling service running on the storage manager 140 accesses scheduling information from the backup copy rule set 160 or a separate scheduling policy associated with the client computing device 102, and initiates a backup copy operation on an hourly basis. Thus, at the scheduled time slot the storage manager 140 sends instructions to the client computing device 102 to begin the backup operation.
  • At step 2, the file system data agent 142A and the email data agent 142B residing on the client computing device 102 respond to the instructions received from the storage manager 140 by accessing and processing the primary data 112A, 112B involved in the copy operation from the primary storage device 104. Because the operation is a backup copy operation, the data agent(s) 142A, 142B may format the data into a backup format or otherwise process the data.
  • At step 3, the client computing device 102 communicates the retrieved, processed data to the first media agent 144A, as directed by the storage manager 140, according to the backup copy rule set 160. In some other embodiments, the information management system 100 may implement a load-balancing, availability-based, or other appropriate algorithm to select from the available set of media agents 144A, 144B. Regardless of the manner the media agent 144A is selected, the storage manager 140 may further keep a record in the storage manager database 140 of the association between the selected media agent 144A and the client computing device 102 and/or between the selected media agent 144A and the backup copy 116A.
  • The target media agent 144A receives the data from the client computing device 102, and at step 4 conveys the data to the disk library 108A to create the backup copy 116A, again at the direction of the storage manager 140 and according to the backup copy rule set 160. The secondary storage device 108A can be selected in other ways. For instance, the media agent 144A may have a dedicated association with a particular secondary storage device(s), or the storage manager 140 or media agent 144A may select from a plurality of secondary storage devices, e.g., according to availability, using one of the techniques described in U.S. Pat. No. 7,246,207, which is incorporated by reference herein.
  • The media agent 144A can also update its index 153 to include data and/or metadata related to the backup copy 116A, such as information indicating where the backup copy 116A resides on the disk library 108A, data and metadata for cache retrieval, etc. After the 30 day retention period expires, the storage manager 140 instructs the media agent 144A to delete the backup copy 116A from the disk library 108A.
  • At step 5, the storage manager 140 initiates the creation of a disaster recovery copy 1168 according to the disaster recovery copy rule set 162. For instance, at step 6, based on instructions received from the storage manager 140 at step 5, the specified media agent 144B retrieves the most recent backup copy 116A from the disk library 108A.
  • At step 7, again at the direction of the storage manager 140 and as specified in the disaster recovery copy rule set 162, the media agent 144B uses the retrieved data to create a disaster recovery copy 1168 on the tape library 1088. In some cases, the disaster recovery copy 1168 is a direct, mirror copy of the backup copy 116A, and remains in the backup format. In other embodiments, the disaster recovery copy 116C may be generated in some other manner, such as by using the primary data 112A, 1128 from the storage device 104 as source data. The disaster recovery copy operation is initiated once a day and the disaster recovery copies 116A are deleted after 60 days.
  • At step 8, the storage manager 140 initiates the creation of a compliance copy 116C, according to the compliance copy rule set 164. For instance, the storage manager 140 instructs the media agent 144B to create the compliance copy 116C on the tape library 1088 at step 9, as specified in the compliance copy rule set 164. In the example, the compliance copy 116C is generated using the disaster recovery copy 1168. In other embodiments, the compliance copy 116C is instead generated using either the primary data 1128 corresponding to the email sub-client or using the backup copy 116A from the disk library 108A as source data. As specified, compliance copies 116C are created quarterly, and are deleted after ten years.
  • While not shown in FIG. 1E, at some later point in time, a restore operation can be initiated involving one or more of the secondary copies 116A, 1168, 116C. As one example, a user may manually initiate a restore of the backup copy 116A by interacting with the user interface 158 of the storage manager 140. The storage manager 140 then accesses data in its index 150 (and/or the respective storage policy 148A) associated with the selected backup copy 116A to identify the appropriate media agent 144A and/or secondary storage device 116A.
  • In other cases, a media agent may be selected for use in the restore operation based on a load balancing algorithm, an availability based algorithm, or other criteria. The selected media agent 144A retrieves the data from the disk library 108A. For instance, the media agent 144A may access its index 153 to identify a location of the backup copy 116A on the disk library 108A, or may access location information residing on the disk 108A itself.
  • When the backup copy 116A was recently created or accessed, the media agent 144A accesses a cached version of the backup copy 116A residing in the media agent index 153, without having to access the disk library 108A for some or all of the data. Once it has retrieved the backup copy 116A, the media agent 144A communicates the data to the source client computing device 102. Upon receipt, the file system data agent 142A and the email data agent 142B may unpackage (e.g., restore from a backup format to the native application format) the data in the backup copy 116A and restore the unpackaged data to the primary storage device 104.
  • Exemplary Secondary Copy Formatting
  • The formatting and structure of secondary copies 116 can vary, depending on the embodiment. In some cases, secondary copies 116 are formatted as a series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4 GB, or 8 GB chunks). This can facilitate efficient communication and writing to secondary storage devices 108, e.g., according to resource availability. For example, a single secondary copy 116 may be written on a chunk-by-chunk basis to a single secondary storage device 108 or across multiple secondary storage devices 108. In some cases, users can select different chunk sizes, e.g., to improve throughput to tape storage devices.
  • Generally, each chunk can include a header and a payload. The payload can include files (or other data units) or subsets thereof included in the chunk, whereas the chunk header generally includes metadata relating to the chunk, some or all of which may be derived from the payload. For example, during a secondary copy operation, the media agent 144, storage manager 140, or other component may divide the associated files into chunks and generate headers for each chunk by processing the constituent files.
  • The headers can include a variety of information such as file identifier(s), volume(s), offset(s), or other information associated with the payload data items, a chunk sequence number, etc. Importantly, in addition to being stored with the secondary copy 116 on the secondary storage device 108, the chunk headers 300 can also be stored to the index 153 of the associated media agent(s) 144 and/or the storage manager index 150. This is useful in some cases for providing faster processing of secondary copies 116 during restores or other operations. In some cases, once a chunk is successfully transferred to a secondary storage device 108, the secondary storage device 108 returns an indication of receipt, e.g., to the media agent 144 and/or storage manager 140, which may update their respective indexes 150, 153 accordingly.
  • During restore, chunks may be processed (e.g., by the media agent 144) according to the information in the chunk header to reassemble the files. Additional information relating to chunks can be found in U.S. Pat. No. 8,156,086, which is incorporated by reference herein.
  • Data Synchronization Management System
  • FIG. 2 illustrates a data synchronization management system 200 according to an embodiment of the present disclosure. The data synchronization management system 200 can incorporate a variety of different hardware and software components, which can in turn be organized with respect to one another in many different configurations, depending on the embodiment.
  • The data synchronization management system 200 of FIG. 2 includes the storage manager 140, the secondary storage computing device(s) 106, the secondary storage device(s) 108, client computing devices 202A-C, and primary storage devices 204A-C. As described above, the storage manager 140 includes the management database 146 and the management agent 154. Additionally, the storage manager 140 includes a cloud interface 208 and a synchronization agent 210. The management database 146 includes information management policies 148, synchronization policies 151, and the management index 150, as described above. The secondary storage computing device(s) 106 include media agent(s) 144 and the media agent database 152, the media agent database 152 also including the index 153.
  • The client computing devices 202A-C each may communicate with the respective primary storage devices 204A-C. While three client computing devices 202A-C and three primary storage devices 204A-C are shown for illustrative purposes in FIG. 2, additional (or fewer) client computing devices and primary storage devices may be present in the data synchronization management system 200. Certain components in the system may communicate with one another via a network 206. For instance, each of the client computing devices 202A-C may communicate with the network 206. Similarly, the storage manager 140 and the secondary storage computing device(s) 106 may communicate with the network 206. Thus, through the network 206 each of the client computing devices 202A-C, the storage manager 140, and the secondary storage computing device(s) 106 may communicate with one-another. The network 206 may comprise any wired and/or wireless communications network suitable for data communications, and may include any of the networks, communications link, or communications pathways described herein. For example, the network 206 may comprise one or more of a LAN, WAN, cellular data network and/or the Internet, among others. Additionally, communication over the network 206 may be accomplished through any suitable communications protocol. For example, communication may be serial or parallel, through Universal Serial Bus (USB) (wired or wireless), Ethernet, Bluetooth, Near Field Communications (NFC), radio frequency (RF), infrared, and/or WiFi (such as any 802.1x interface), or combinations thereof, among others. As shown by the dotted line in FIG. 2, the storage manager 140 and the secondary storage computing device(s) 106 may also optionally communicate with one another directly, instead of or in addition to communicating with one another via the network 206, also through any suitable communications network or protocol.
  • Storage Manager in the Data Synchronization Management System
  • In general, in the data synchronization management system 200 the storage manager 140 may include all of the functionality and components described above in reference to FIGS. 1A-E. In addition, according to certain embodiments of the data synchronization management system 200, the storage manager 140 provides (among others) one or more of the following functions:
      • tracking synchronization information related to primary copies of data on the primary storage devices 204A-C, and secondary copies of data on the secondary storage device(s) 108;
      • tracking and resolving conflicts between similar pieces of data located in the various storage devices;
      • managing user created data synchronization policies; and
      • providing direct access to data stored in secondary storage device(s) 108 through a cloud interface.
  • As described above, the storage manager 140 may maintain a database 146 of management-related data, such as information management and synchronization policies. The database 146 may include the management index 150 or other data structure that stores logical associations between components of the system, user preferences, synchronization polices and/or synchronization (and/or user) profiles (e.g., preferences regarding what data is synchronized to which devices, preferences regarding the scheduling, type, or other aspects of data synchronization operations, etc.), management tasks, synchronization tasks, or other useful data. For example, the storage manager 140 may use the index 150 to track logical associations between media agents 144 and secondary storage devices 108, movement of data from primary storage devices 204A-C to secondary storage device(s) 108, and/or synchronization states of data among the primary storage devices 204A-C.
  • Thus, the data synchronization management system 200 may utilize information management policies 148 for specifying and executing information management operations, and synchronization policies 151 for specifying and executing synchronization operations (e.g., on an automated basis). Generally, an information management policy 148 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with storage and/or other information management operations. Similarly, a synchronization policy 151 can include a data structure or other information source that specifies a set of parameters (e.g., criteria and rules) associated with synchronization operations.
  • According to certain embodiments, a synchronization policy 151 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 synchronization policy; (2) source information associated with the data to be synchronized, such as such as the identity of primary storage device(s) 204 and/or client computing device(s) 202 storing or otherwise associated with the data, information indicating where the data is stored (e.g., primary storage address information), and the like; (4) destination information associated with the data, such as the identify of secondary storage device(s), secondary storage devices 106, and/or media agents to which the data will be synchronized; (5) datapath information specifying how the data will be communicated from sources to destinations; (6) the type of synchronization operation to be performed; and (7) the synchronization schedule. For example, a synchronization policy may be created by a user of the data synchronization management system 200, in which the user specifies that files and/or data to be synchronized (by specifying for inclusion, for example, files belonging to a particular directory, files having particular content, and/or files having particular associated file metadata) and the devices to which the data will be synchronized (for example, a user may specify that data and/or files associated with client computing device 202A are to be synchronized to the primary storage device 204B associated with the client computing device 202B).
  • In general, in the data synchronization management system 200, a user may be identified by a user profile. The user profile associated with a user may include, for example, information management policies 148 and/or synchronization policies 151 of the user, an identification of the user (for example, a username), and/or a means of authenticating the identity of the user (for example, a password), among other things. Information management policies 148 and/or synchronization policies 151 may be associated with particular users of the data synchronization management system 200, and more than one information management policy 148 and/or synchronization policy 151 may be associated with a particular user. In general, synchronization polices 151 in the data synchronization management system 200 are associated with a user profile. The user profile may also include other information relevant to the data synchronization management system 200, including for example, backup policies, among other things.
  • In the storage manager 140, the management agent 154, synchronization agent 210, and cloud interface 208, may be implemented as interconnected software modules or application programs.
  • The synchronization agent 210 in some embodiments initiates, controls, and/or monitors the status of some or all synchronization or other information management operations previously performed, currently being performed, or scheduled to be performed by the data synchronization management system 200. For instance, the synchronization agent 210 may access information management policies 148 to determine when and how to initiate and control synchronization and other information management operations, as will be described further below. Although not depicted in FIG. 2, embodiments of the data synchronization management system 200 generally also include the jobs agent 156 in the storage manager 140, as described above with respect to the information management system 100. Thus, information management operations may be initiated, controlled, and/or monitored by the jobs agent 156 and/or the synchronization agent 210. In an embodiment, the jobs agent 156 and the synchronization agent 210 may be a single unit.
  • The cloud interface 208 may include information processing and display software, such as a graphical user interface (“GUI”), an application program interface (“API”), or other interactive interface or portal through which users and system processes may retrieve information about the status of synchronization and/or other information management operations and data (e.g., storage operations and storage locations), retrieve data and/or files directly, view file lists, and/or issue instructions to the data synchronization management system 200 and its constituent components. For instance, a user may access the cloud interface 208 via a browser or other application executing on one of the client computing devices 202 or another computing device.
  • Via the cloud interface 208, users may optionally issue instructions to the components in the data synchronization management system 200 regarding performance of storage and recovery operations, performance of synchronization operations, and/or accessing of stored data. For example, a user may modify a synchronization schedule or may employ the GUI to view the status of pending storage and/or synchronization operations, or to monitor the status of certain components in the data synchronization management system 200. As another example, a user may identify and authenticate themselves (with, for example, a username and password), and view and access files and data (stored in, for example, the secondary storage device(s) 108) associated with the user. Data from the cloud interface 208 may be transferred over the network 206. For example, the cloud interface 208 may be accessed by a user over the Internet. As with the other components of the data synchronization management system 200, in other embodiments the cloud interface 208 may be located in a different part of the system (for example, in the secondary storage computing device(s) 106).
  • Data and/or files may be transferred from the client computing devices 202A-C to the secondary storage device(s) via the media agent(s) 144 (and associated secondary storage computing device(s) 106). Thus, for example, during a secondary copy operation, files may be backed up or otherwise transferred from the primary storage device 204A to the secondary storage device(s) 108. During synchronization, the media agent(s) 144, at the direction of the storage manager 140, may communicate the files to be synchronized (e.g., through a restore operation) from the secondary storage device(s) 108 to the destination client computing device(s) 202 for storage in the associated primary storage devices 204.
  • In another embodiment, data and/or files transferred in the data synchronization management system 200 may be transferred directly from one client computing device to another. Such a transfer may be under the direction of the storage manager 140. For example, storage manager 140 may direct client computing device 202A to transfer files to be synchronized directly to computing device 202B, e.g., without the use of the media agent(s) 144. Alternatively, the client computing devices 202 may include the components necessary to identify files to be synchronized, and to transfer those files to associated client computing devices directly. In this alternative, the storage manager 140 may snoop on the files transferred from one client computing device to another so as to identify files to be copied to secondary storage.
  • Other Components in the Data Synchronization Management System
  • As described above with respect to the information management system 100, the client computing devices 202A-C include application(s) 110 and data agent(s) 142 (although they are not depicted in FIG. 2). These application(s) 110 and data agent(s) 142 generally function as described above. Additionally, it is to be understood that primary storage devices 204A-C store primary data, as described above. Similarly, the secondary storage computing device(s) 106 (including the media agent 144, media agent database 152, and index 153) and the secondary storage device(s) 108 also generally function as described above in the information management system 100.
  • In particular, in the data synchronization management system 200, information management, information processing, information transfer, data movement, secondary copy, and data backup, archive, and other operations in general are carried out in a manner similar to that described above. Thus, it is to be understood that the description of the data synchronization management system 200 includes all of the functionality described above with respect to those and other operations, components, and characteristics (such as scalability).
  • Exemplary Data Synchronization Management Operations and Processes
  • FIG. 3 illustrates an example data synchronization management process, according to an embodiment of the present disclosure. In general, according to certain embodiments, a data synchronization operation occurs as a result of or in response to a secondary copy operation (e.g., a data backup operation). The data synchronization may occur subsequent to, simultaneously with, or may at least partially overlap with the secondary copy operation, depending on the embodiment. While data synchronization operations may be described herein as occurring in conjunction with backup operations for the purposes of illustration, data synchronization operations may be compatible with other types of secondary copy operations in addition to backup operations, e.g., archive operations, snapshot operations, replication operations, etc.
  • In an embodiment, a secondary copy operation occurs in which a copy of primary data stored in one of the primary storage devices 204A-C is created in the secondary storage device(s) 108. Then, particular identified files are synchronized (e.g., through a restore operation) to the other primary storage devices 204A-C from the secondary storage device(s) 108. This process is described in detail in reference to blocks 302, 304, and 306 below.
  • At block 302, a backup operation is initiated for a first client computing device. For example, an information management policy 148 may specify that a backup of certain data associated with client computing device 202A is to occur. and the storage manager 140 may therefore initiate the backup. Alternatively, a user of the client computing device 202A may arbitrarily choose to manually initiate a backup, e.g., using the GUI of the storage manager 140. The data and/or file backup operation generally proceeds as detailed above (for example, as described in reference to FIG. 1E). For example, the files selected for backup by the information management policy 148 may be copied from primary storage device 204A to secondary storage device(s) 108, as directed by the storage manager 140.
  • At block 304, files in the secondary copy (for example, files backed up in the secondary storage device(s) 108) are identified for synchronization. Files and/or data to be synchronized are specified by the synchronization policy 151, which can be any of those described above. Additionally, the storage manager 140 and/or the media agent(s) 144 compare the files backed up as part of the current backup operation to the previous versions of the files located in the secondary storage device(s) 108.
  • Files that have not changed (e.g., no changes in file contents and/or metadata) are determined to not require synchronization. Files that have changed in some way, however, are determined to require synchronization. For example, the user of the data synchronization management system 200 may specify that files contained within a particular directory are to be synchronized. Those files specified in the synchronization policy by the user will then be compared to previous versions of those files stored in the secondary storage device(s) 108, and files requiring synchronization will be identified by, for example, the storage manager 140 and/or media agent(s) 144. In various embodiments, the files to be synchronized may be identified before the backup is initiated, as the backup is initiated, as the backup is in progress, and/or after the backup is completed. Further details regarding the designation and identification of the files to be synchronized are described in reference to FIG. 4 below.
  • At block 306, those files that are identified to be synchronized are restored to specific client computing devices. In general, the data and/or file restore operation proceeds as detailed above (for example, as described in reference to FIG. 1E). For example, files may be transferred from the secondary storage device(s) 108 to one or more of the primary storage devices 204A-C. User created synchronization policies may specify the specific files to be synchronized, and/or the specific devices to which those files are to be synchronized. For example, the user may specify that files in a particular directory on the client computing device 202A are to be synchronized with a particular directory on the client computing device 202B. Thus, in an embodiment, the file synchronization among client computing devices (such as client computing devices 202A-C) may be accomplished through a combination of operations similar to the backup and restore operations described above.
  • In an embodiment, identified files may not be restored/synchronized from the secondary storage device(s) 108, but rather may be transferred from one client computing device to another directly. Thus, although the files to be synchronized may be backed up to the secondary storage device(s) 108, and the backup operation may trigger the synchronization process, the synchronization is performed by transferring the files from the source client computing device to the target client computing device. Thus, the bandwidth of the secondary storage computing device(s) 106's connection to the network 206 may advantageously be preserved.
  • In certain embodiments, the user may specify multiple synchronization policies. For example, the user may specify that files located in directory “alpha” associated with client computing device 202A are to be synchronized with a version of directory “alpha” associated with client computing device 202B, while the files in directory “beta” associated with client computing device 202B are to be synchronized with a version of directory “beta” associated with client computing device 202C. Further, in certain embodiments, the user may specify different directories on the client computing devices to be synchronized. For example, the user may specify that files located in directory “alpha” associated with client computing device 202A are to be synchronized with directory “gamma” associated with client computing device 202B. Additionally, in certain embodiments, the user may synchronize files and/or data among more than two client computing devices. For example, the user may specify the particular client computing devices to which files are to be synchronized. Alternatively, files may be synchronized to all client computing devices associated with the user of the data synchronization management system 200. Client computing devices associated with the user may be identified, in some embodiments, through the user profile. For example, a user may associate themselves with all the client computing devices they own and/or manage by including the identities of those client computing devices in the user's user profile.
  • FIG. 4 illustrates an example data synchronization management process including designation of particular files, according to an embodiment of the present disclosure. At block 402, the data synchronization management system 200 receives parameters indicating which files and/or data to synchronize. In some embodiments, the user indicates and/or identifies the files, and/or criteria for identifying the files, to be synchronized. In some embodiments, the files and/or data to be synchronized may be identified according to some policy, and/or a policy may be automatically created when a new user profile is created and/or a user profile is associated with a particular client computing device (for example, certain types of files, such as photos, may be automatically selected for synchronization when a user profile is created).
  • A user may specify the files to be synchronized. Files to be synchronized may be directly selected or otherwise identified, or user-defined criteria may be specified to indirectly identify the files to be synchronized. For instance, without limitation, files may be identified by detecting the existence of specified content within the file (such as the existence of one or more specified terms within a document), and/or by matching metadata associated with the file with one or more specified metadata parameters (such as filename, file owner, directory, creation date, modification date, size, type, location, Global Positioning System (GPS) coordinates, among others). The criteria used to identify files to be synchronized may vary. In addition, more than one criteria may be specified to identify files to be synchronized. For example, files to be synchronized may be identified as the files in a certain directory that were created after a certain date.
  • At block 404, a backup operation is initiated for a first client computing device, similar to the operation of block 302 of FIG. 3. The files to be backed up may be specified by a backup policy, and may include files other than and/or in addition to those files selected for synchronization. In an embodiment, the files designated to be synchronized are automatically included in a backup policy. In another embodiment, the backup policy and the synchronization policy are separate, but may be related in some way. The backup schedule set by the backup policy may or may not be linked to or associated with the synchronization schedule. In an embodiment, the synchronization policy is a subset of the backup policy. In an embodiment, multiple synchronization policies and backup policies may exist and/or be associated with a user profile. In an embodiment, files to be synchronized according to a synchronization policy are synchronized anytime any scheduled backup occurs (and/or is manually initiated).
  • At block 406, the recently created backup copy is processed to identify files to be synchronized based on the received parameters discussed above in relation to block 402. For instance, the media agent 144 accesses the secondary copy from the secondary storage device(s) 108 and process the secondary copy to identify the files for synchronization. Similar to block 304 of FIG. 3, in block 406 the files to be synchronized are thus identified. Thus, for example, when the synchronization policy specifies files in directory “delta” are to be synchronized, at block 406 the files in the secondary storage device(s) 108 that are in the designated directory “delta” (i.e., that satisfy the synchronization criteria specified by the policy) and are identified as having changed will be identified for synchronization.
  • At block 408, those files that are identified to be synchronized are restored or otherwise transmitted to the target client computing devices, as described above in relation to the operation of block 306 of FIG. 3.
  • As described above, in an embodiment, identified files may not be restored/synchronized from the secondary storage device(s) 108, but rather may be transferred from one client computing device to another directly. In this embodiment the source client computing device may identify the files to be synchronized and communicate the files to the target client computing device(s).
  • FIG. 5 illustrates an example data synchronization management process including location metadata, according to an embodiment of the present disclosure. At block 502, the data synchronization management system 200 receives location information indicating which files and/or data to synchronize. In some embodiments, the user indicates and/or identifies the files to be synchronized based on the location information. In some embodiments, the files and/or data to be synchronized based on location information may be identified according to some policy, and/or may be automatically created when a new user profile is created and/or a user profile is associated with a particular client computing device (for example, certain files created in a particular location, such as documents created at home, may be automatically selected for synchronization when a user profile is created).
  • Location information may include, for example, geographical location, personal location (such as, for example, home or work), GPS location, city, and/or state, just to name a few. A user may provide the location information in addition to other parameters as described above in reference to block 402 of FIG. 4.
  • At block 504, a backup operation is initiated for a first client computing device, similar to the operation of block 302 of FIGS. 3, and 404 of FIG. 4.
  • At block 506, location metadata may be included and/or added to files in the secondary copy. In some embodiments, a component of the data synchronization management system 200 adds location information (such as, GPS coordinates) to the metadata associated with files on the client computing devices 202A-C, in the primary copy. For example, in an embodiment, data agents on the client computing devices 202A-C may add location metadata to files at the point the files are created, accessed, modified, and/or designated in some other way (such as, for example, designated through a backup and/or synchronization policy). In other embodiments, the storage manager 140 or other appropriate component may store location information related to client computing devices 202A-C, and add location metadata to files backed up (or otherwise transferred to secondary storage). For example, the storage manager 140 may direct data agents on the client computing devices 202A-C to add location metadata to files when a scheduled backup operation occurs.
  • Location information may include, for example, GPS coordinates, an Internet Protocol (IP) address, a street address, a geographic location (such as a city, state, etc.), a triangulated location based on mobile tracking with respect to telecommunications base stations, and/or computer-enabled location-based services, among others. Location information may be provided by the client computing device. Location information may also be provided by a device attached to, embedded in, or otherwise in communication with the client computing device. For example, location information may be provided by a GPS receiver, a network adapter, or a cellular network radio, among others. Alternatively, location information may be provided manually by a user. For example, a user may specify location information for one or more files, and/or may designate location information associated with a particular client computing device. In an embodiment, any combination of the above described ways of providing location information may be used.
  • At block 508, file location metadata is accessed in the secondary copy (in, for example, the secondary storage device(s) 108). The accessed location metadata can then be used to identify files to be synchronized, according to the synchronization policy. For example, the user profile may include a synchronization policy that includes synchronization of all files that are created at the user's home GPS coordinates. Thus, identified files in the secondary copy may include those with GPS metadata indicating a location associated with, at, or near the user's home.
  • At block 510, those files that are identified to be synchronized are restored to the appropriate computing devices, as described above in relation to the operation of block 306 of FIG. 3.
  • As described above, in an embodiment, identified files may not be restored/synchronized from the secondary storage device(s) 108, but rather may be transferred from one client computing device to another directly. In this embodiment, location metadata may be accessed on the client computing device to identify the files to be synchronized directly to other client computing devices.
  • Remote File Access Operations and Processes
  • FIG. 6 illustrates an example remote file access process, according to an embodiment of the present disclosure. In some instances, a user of the data synchronization management system 200, through one of the client computing devices 202A-C, may request access to a file that may or may not presently be stored on the one of the client computing devices 202A-C. A file may not be present on one of the client computing devices 202A-C in certain circumstances including circumstances in which, for example, the user is attempting to access the file through the cloud interface 208 and/or the file data has not yet been synchronized to the particular client computing device. For example, in certain embodiments a user may utilize a client computing device to view, through the cloud interface 208, a list of files designated for synchronization. The list of files designated for synchronization may include files not presently synchronized to the client computing device. For example, a file that was recently created on another client computing device may not yet be synchronized to the user's client computing device. A user attempting to access files through the cloud interface 208 may thus attempt to access files that are not yet synchronized to the user's client computing device. Alternatively, an earlier version of the file desired by the user may be present on the user's client computing device, whereas an updated version has not yet synchronized from another client computing device where it was recently updated.
  • In an embodiment, the data synchronization management system 200 may not synchronize all designated files to all client computing devices, but rather may synchronize a file list including, for example, file names and locations, but not the actual file data. In this embodiment, file data associated with a particular file may be synchronized to a client computing device at the time of a user's request for that file on that client computing device. In another embodiment, the data synchronization management system 200 may initially synchronize a file list, and subsequently synchronize the file data in the background. In an embodiment, the user may access a file list from any network 206 connected device, such as laptop computer with a web browser or the like. Thus, the user may be able to view a list of files, even though the actual file data may not be present on the network 206 connected device.
  • The example remote file access process begins at block 602, at which point a file list is provided to, for example, a user. The file list may be provided to the user in any of the examples and embodiments described above. The file list may include limited file information, for example, file names, file locations, file modification dates, and/or file sizes, among other things.
  • At block 604, a file access request is received from the user. For example, a user of the primary storage device 204B or a web browser may view the file list, and see a file that they would like to access. The user may then request access to that file by, for example, clicking on or otherwise selecting the file.
  • Once the file access request is received, at block 606 the data synchronization management system 200 determines whether the file is locally synchronized. This may be accomplished, for example, by a local data agent and/or the storage manager 140. In an embodiment in which the user is attempting to access the file through a web browser and the cloud interface 208, it may be determined whether the requested file is stored in a local cache. In some embodiments, the file may be synchronizing in the background, and/or the locally synchronized file may be a version older than the most recent on all synchronized devices.
  • In the event the current version of the requested file is locally synchronized, at block 608 the user is provided access to that local file. In the event the current version of the requested file is not locally synced, at block 610 the current version of the file is retrieved/synchronized from secondary storage. In another embodiment, the file may be retrieved directly from another client computing device, also as described above with respect to synchronization operations.
  • Once the requested file is transferred to the user's device, at block 612, the user is provided access to that local copy of the file.
  • In an embodiment, the user may optionally manually initiate synchronization of an accessed file. For example, when the user has edited the accessed file, the user may optionally manually initiate the transfer of the edited file back to the secondary storage device(s) 108. The edited file may then be synchronized to all related devices according to the synchronization policy.
  • The user profile may include synchronization policies specifying those files that are accessible through the remote file access process, as well as those that are not. For example, the user may specify that only particular files and/or data are to be available through the cloud interface 208. The user may likely specify that all synchronized files, or no synchronized files are to be available through the cloud interface 208.
  • File Conflicts
  • It may occur during the operation of the data synchronization management system 200 that file conflicts and/or inconsistencies arise. For example, the same file may be edited simultaneously in two of the client computing devices 202A-C. In this event, each file may be synchronized to the other client computing device, creating a conflict. In an embodiment, this conflict may be resolved in an automated fashion. For certain file types, the differences may be merged according to any appropriate method. In some instances, one or more of the conflicting files may be renamed, and the user notified of the conflict for manual resolution. In general, even conflicted files will continue to be synchronized and backed up according to applicable policies.
  • Other Embodiments
  • In an embodiment, one or more media agent(s) 144 may manage the synchronization of data and/or files among the client computing devices 202A-C. The media agent(s) 144 may determine whether changes have been made to backed up files that are designated for synchronization, and thus may determine whether or not a synchronization/restore operation occurs with respect to the other client computing device.
  • In various embodiments, a synchronization policy may include the options for two-way synchronization and/or one-way synchronization. In two-way synchronization, files and/or data may be synchronized both to and from a destination. For example, a synchronization policy may indicate that files should be two-way synchronized between client computing device 202A and client computing device 202B. Thus, any changes on either of the devices would be synchronized to the other device. Alternatively, a synchronization policy may indicate that files should be one-way synchronized. For example, one-way synchronization from client computing device 202A to client computing device 202B would cause any changes to synchronized files on client computing device 202A to be synchronized to client computing device 202B, but not the other way around. Alternatively, a reverse one-way synchronization would cause any changes on client computing device 202B to be synchronized to client computing device 202A, but not the other way around.
  • In an embodiment, when a client computing device that is part of a synchronization policy is offline (for example, it is not connected to the network 206, or it is powered down), the data synchronization management system 200 will wait until that client computing device comes back online to synchronize files and data to that client computing device. This may be accomplished, for example, through a polling process in which the storage manager 140 (or other component of the data synchronization management system 200) periodically polls the client computing devices 202A-C to determine whether they are connected to the network 206. Alternatively, the client computing devices 202A-C may periodically send notification to the storage manager 140 (or other component of the data synchronization management system 200) when they are connected to the network 206. In an embodiment, the connectedness of the client computing device is not determined until a scheduled or forced backup and/or synchronization occurs. In another embodiment, the client computing devices 202A-C send notification to the storage manager 140 (or other component of the data synchronization management system 200) when they are initially connected to the network 206.
  • In an embodiment, all data transferred within the data synchronization management system 200 is encrypted. The encrypted data may then be unencrypted when the user is identified and the identity of the user is authenticated. Additionally, in an embodiment, the data associated with the data synchronization management system 200 does not leave the ecosystem of the data synchronization management system 200. For example, the data synchronization management system 200 may comprise a local area network and/or enterprise network in which all communications are authenticated and encrypted. Thus, no unencrypted data is transferred out of the information management system to, for example, the open internet. Further, various data associated with various user profiles may be kept entirely separate (for example, encrypted separately).
  • In an embodiment, data and files in the data synchronization management system 200 are deduplicated at the file and/or block level. Thus, a file stored in secondary storage device(s) 108 is only stored once, even though it may be synchronized across multiple client computing devices, and although each of those client computing devices may have a separate backup policy involving that file.
  • It is to be understood that the various embodiments of the data synchronization management system 200 described may include any or all of the various components of the information management system 100 described above, including, but not limited to, data movement operations, backup operations, archive operations, snapshot operations, replication operations, deduplication operations, data processing and manipulations operations, content indexing, metabase classification operations, encryption operations, and/or management operations.
  • User Interface Screenshots
  • FIGS. 7A-G illustrate exemplary screenshots of pages of the user interface of the data synchronization management system 200, according to various embodiments of the present disclosure. In FIGS. 7A-G, the term ‘cloud folder’ may be understood to refer to, without limitation, synchronization policies as described in the present disclosure.
  • Screenshot 700 of FIG. 7A shows an exemplary page of a user interface of the data synchronization management system 200 including a listing of backup information 702, a current backup status display 704, a listing of backup schedules 706, a listing of content 707, synchronization information 708, and a last seen location window 709. In screenshot 700, user “backup1” has implemented a backup policy on a client computing device. The listing of backup information 702 includes the date and time of the last backup, the last backup size, the total backup size, and the date and time this client computing device was last seen online. The current backup status display 704 indicates that there is a current backup in process, and no backups are scheduled. The backup schedules 706 button allows the user may schedule backups. The listing of content 707 field indicates directories that the user has specified for back up. The synchronization information 708 field allows the user to set synchronization policies by clicking the “Sync backup1 using Cloud Folders” link. The last seen location window 709 shows the client computing devices last seen location. The last seen location window 709 indicates that the client computing device associated with user interface of screenshot 700 includes a means of gathering location data that may be associated files to be backed up and/or synchronized.
  • The screenshot 710 of FIG. 7B shows an exemplary page of the user interface when a user chooses to create a synchronization policy, including a select folder path radio button 711, an all backed-up data radio button 712, a two-way sync radio button 714, and one-way sync to cloud folder radio button 716. In screenshot 710, the user has specified a folder/synchronize policy name, “folder1.” Using the select folder path radio button 711, the user may choose particular folders/directories to synchronize. By selecting the all backed-up data radio button 712, the user may choose to synchronize all data that is already part of the backup policy. Using the two-way sync radio button 714, the user may choose to synchronize file changes both ways (i.e., file changes on this client computing device are synchronized to other client computing devices, and likewise changes on other client computing devices are synchronized to this client computing device). Alternatively, the user may use the one-way sync to cloud folder radio button 716 to synchronize files one way (i.e., file changes on this client computing device are synchronized to other client computing devices, but not the other way around).
  • Screenshot 720 of FIG. 7C shows another exemplary page of the user interface when a user chooses the select folder path radio button 711 of the page shown in FIG. 7B. The page includes a listing 721 of backed up content. The listing 721 includes a deselected folder 722 and a selected folder 724. The listing shows directories that will be synchronized under the present synchronization policy. The deselected folder 722 is a folder/directory that is not selected for synchronization. The selected folder 724 is a folder/directory that is selected for synchronization.
  • Screenshot 730 of FIG. 7D shows an exemplary page of the user interface after a synchronization policy/cloud folder “folder1” has been created, as indicated by field 732.
  • Screenshot 740 of FIG. 7E shows another exemplary page of the user interface in which synchronization policies may be set. The page includes a listing of cloud folders including folder1 information tab 741, a listing of synchronization clients 742, a listing of sync options including two-way sync mode 744, only upload contents to cloud folder sync mode 746, and only download contents to cloud folder sync mode 748, and a default directory field 749. Folder1 information tab 741 indicates the current synchronization policy that is being set, as well as the directory path that is being synchronized. The listing of synchronization clients 742 indicates the destinations to which the files of the current synchronization policy will be synchronized. For each of the four listed synchronization clients 742, the user may select a synchronization mode from the listing of sync options. The modes include: two-way sync mode 744 (synchronization both to and from the destination/client), only upload contents to cloud folder sync mode 746 (only synchronize to the destination/client), and only download contents to cloud folder sync mode 748 (only synchronize from the destination/client). At default directory 749 the user may set the path of the default download/upload path.
  • Screenshot 750 of FIG. 7F shows yet another exemplary page of user interface in which synchronization policies may be set. The page includes two highlighted active cloud folders, indicated by the highlighted folder1 information tab 751 and folder2 information tab 752. The page also includes four inactive cloud folders, indicated by the greyed out folder information tabs 754. Active cloud folders may include those in which files are currently synchronizing, file synchronization is currently paused, and/or a synchronization schedule is set. Conversely, inactive cloud folders may include those in which files are not currently synchronizing, file synchronization is not currently paused, and/or a synchronization schedule is not set. As shown, multiple synchronization policies (cloud folders) may be set. In screenshot 750, folder1 information tab 751 and folder2 information tab 752 indicate folders that are currently active, while folder information tabs 754 indicate those that are currently inactive.
  • Screenshot 760 of FIG. 7G shows an exemplary page of the user interface in which synchronization policies may be set. The page includes active cloud folders folder4 and folder 2, indicated by information tabs 761 and 762. The page also includes inactive cloud folders folder 3, folder5, and folder6 indicated by information tab 764. Further, the page includes inactive cloud folder folder1 indicated by information tab 766. Folder4 (indicated by information tab 761) is active and currently synchronizing, while folder2 (indicated by information tab 762) is currently paused (not synchronizing). Formerly active (as shown in the page of screenshot 750), folder1 is now inactive, as indicated by information tab 766.
  • Thus, the data synchronization management system 200 advantageously enables synchronization of files and/or data among various client computing devices simultaneously with backups of files and/or data. Advantageously, various synchronization policies may be set and adjusted by a user, specifying files to be synchronized based on parameters (file data, contents, and/or metadata) such as, for example, file location, file type, file size, file creation and/or modification, and/or location information. Additionally, synchronization policies may specify the devices to which various files should be synchronized. Further, the data synchronization management system 200 advantageously enables a user to access synchronized files through a cloud interface 208 from any location.
  • Terminology
  • Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
  • Depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out all together (e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
  • Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described herein. Software and other modules may reside on servers, workstations, personal computers, computerized tablets, PDAs, and other devices suitable for the purposes described herein. Software and other modules may be accessible via local memory, via a network, via a browser, or via other means suitable for the purposes described herein. Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes or methods, or any combinations thereof, suitable for the purposes described herein. User interface elements described herein may comprise elements from graphical user interfaces, command line interfaces, and other suitable interfaces.
  • Further, the processing of the various components of the illustrated systems can be distributed across multiple machines, networks, and other computing resources. In addition, two or more components of a system can be combined into fewer components. Various components of the illustrated systems can be implemented in one or more virtual machines, rather than in dedicated computer hardware systems. Likewise, the data repositories shown can represent physical and/or logical data storage, including, for example, storage area networks or other distributed storage systems. Moreover, in some embodiments the connections between the components shown represent possible paths of data flow, rather than actual connections between hardware. While some examples of possible connections are shown, any of the subset of the components shown can communicate with any other subset of components in various implementations.
  • Embodiments are also described above with reference to flow chart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products. Each block of the flow chart illustrations and/or block diagrams, and combinations of blocks in the flow chart illustrations and/or block diagrams, may be implemented by computer program instructions. Such instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the acts specified in the flow chart and/or block diagram block or blocks.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the acts specified in the flow chart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the acts specified in the flow chart and/or block diagram block or blocks.
  • While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the disclosure. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the described methods and systems may be made without departing from the spirit of the disclosure. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the disclosure.

Claims (20)

What is claimed is:
1. A computer-implemented method of synchronizing files between multiple client computers using secondary copy data, the computer-implemented method comprising:
accessing, by a synchronization module executing in computer hardware comprising one or more computer processors, user-defined synchronization criteria for identifying files to synchronize between a first primary storage device associated with a first client computing device and a second primary storage device associated with a second client computing device;
initiating a secondary copy operation in which one or more files stored in the first primary storage device are copied to one or more secondary storage devices to create a secondary copy including the one or more files;
after the initiation of the secondary copy operation, and based on the user-defined synchronization criteria, identifying, by the synchronization module, at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device; and
communicating the at least one file to the second client computing device for storage in the second primary storage device to synchronize the at least one file between the first primary storage device and the second primary storage device.
2. The computer implemented method of claim 1, wherein said communicating comprises communicating a copy of the at least one file that is accessed from the one or more secondary storage devices.
3. The computer implemented method of claim 1, wherein said identifying is in response to the secondary copy operation.
4. The computer-implemented method of claim 3, wherein the electronic data store is associated with a storage manager module executing in the computer hardware comprising the one or more computer processors.
5. The computer-implemented method of claim 4, wherein at least one of said initiating, said identifying, or said communicating is performed by the storage manager module.
6. The computer-implemented method of claim 1, further comprising:
receiving the user-defined synchronization criteria at the synchronization module; and
storing the received user-defined synchronization criteria in an electronic data store accessible by the synchronization module.
7. The computer-implemented method of claim 6, wherein the user-defined synchronization criteria are received from a user of at least one of the first client computing device or the second client computing device.
8. The computer-implemented method of claim 1, wherein the at least one file communicated to the second client computing device replaces a previous version of the at least one file stored in the second primary storage device.
9. The computer-implemented method of claim 1, wherein the user-defined synchronization criteria include at least one of: file data, file contents, file metadata, file name, file location, or location information.
10. The computer-implemented method of claim 1, wherein identifying at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device comprises, for each particular file of the one or more files being copied to the one or more secondary storage devices:
determining whether the particular file is different from a previous version of the particular file stored in the one or more secondary storage devices; and
in response to determining that the particular files is different from the previous version of the particular file, identifying the particular file as a file to be synchronized.
11. A system for synchronizing files between multiple client computers using secondary copy data, the system comprising:
a data store; and
a synchronization module executing in computer hardware comprising one or more computer processors and configured to:
access user-defined synchronization criteria from the data store, the user-defined synchronization criteria for identifying files to synchronize between a first primary storage device associated with a first client computing device and a second primary storage device associated with a second client computing device;
after the initiation of a secondary copy operation in which one or more files stored in the first primary storage device are copied to one or more secondary storage devices to create a secondary copy including the one or more files, and based on the user-defined synchronization criteria, identify at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device;
wherein a copy of the at least one file is communicated to the second client computing device for storage in the second primary storage device to synchronize the at least one file between the first primary storage device and the second primary storage device.
12. The system of claim 11, wherein the copy of the at least one file that is communicated to the second client computing device is accessed from the one or more secondary storage devices.
13. The system of claim 11, wherein the identification of the at least one file is performed in response to the secondary copy operation.
14. The system of claim 11, wherein the secondary copy operation comprises a backup operation or an archive operation.
15. The system of claim 11, wherein communicating the accessed at least one file to the second client computing device comprises a restore operation.
16. The system of claim 11, wherein the at least one file communicated to the second client computing device replaces a previous version of the at least one file stored in the second primary storage device.
17. The system of claim 11, wherein the user-defined synchronization criteria include at least one of: file data, file contents, file metadata, file name, file location, or location information.
18. A networked data storage system, comprising:
a first client computing device;
a second client computing device;
at least one first primary storage device associated with the first client computing device;
at least one second primary storage device associated with the second client computing device;
one or more secondary storage devices; and
computer hardware comprising one or more computer processors and having a synchronization module executing thereon, the synchronization module configured to:
access user-defined synchronization criteria, the user-defined synchronization criteria for identifying files to synchronize between the first primary storage device and the second primary storage device;
after the initiation of a secondary copy in which one or more files stored in the first primary storage device are copied to the one or more secondary storage devices to create a secondary copy including the one or more files, and based on the user-defined synchronization criteria, identify at least one file in the secondary copy to synchronize between the first primary storage device and the second primary storage device;
wherein a copy of the at least one file is communicated to the second client computing device for storage in the second primary storage device to synchronize the at least one file between the first primary storage device and the second primary storage device.
19. The networked data storage system of claim 18, wherein the copy of the at least one file that is communicated to the second client computing device is accessed from the one or more secondary storage devices.
20. The networked data storage system of claim 18, wherein the identification of the at least one file is performed is in response to the secondary copy operation.
US13/968,120 2013-01-11 2013-08-15 Data synchronization management Abandoned US20140201140A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/968,120 US20140201140A1 (en) 2013-01-11 2013-08-15 Data synchronization management

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201361751698P 2013-01-11 2013-01-11
US13/968,120 US20140201140A1 (en) 2013-01-11 2013-08-15 Data synchronization management

Publications (1)

Publication Number Publication Date
US20140201140A1 true US20140201140A1 (en) 2014-07-17

Family

ID=51165988

Family Applications (7)

Application Number Title Priority Date Filing Date
US13/968,120 Abandoned US20140201140A1 (en) 2013-01-11 2013-08-15 Data synchronization management
US13/968,023 Active 2033-12-29 US9336226B2 (en) 2013-01-11 2013-08-15 Criteria-based data synchronization management
US13/968,091 Active 2033-12-21 US9262435B2 (en) 2013-01-11 2013-08-15 Location-based data synchronization management
US13/968,133 Active 2034-07-08 US9430491B2 (en) 2013-01-11 2013-08-15 Request-based data synchronization management
US15/146,463 Active US9898481B2 (en) 2013-01-11 2016-05-04 Data synchronization management
US15/875,950 Active US10353871B2 (en) 2013-01-11 2018-01-19 Data synchronization management
US16/226,303 Active 2034-06-25 US11288236B2 (en) 2013-01-11 2018-12-19 Data synchronization management

Family Applications After (6)

Application Number Title Priority Date Filing Date
US13/968,023 Active 2033-12-29 US9336226B2 (en) 2013-01-11 2013-08-15 Criteria-based data synchronization management
US13/968,091 Active 2033-12-21 US9262435B2 (en) 2013-01-11 2013-08-15 Location-based data synchronization management
US13/968,133 Active 2034-07-08 US9430491B2 (en) 2013-01-11 2013-08-15 Request-based data synchronization management
US15/146,463 Active US9898481B2 (en) 2013-01-11 2016-05-04 Data synchronization management
US15/875,950 Active US10353871B2 (en) 2013-01-11 2018-01-19 Data synchronization management
US16/226,303 Active 2034-06-25 US11288236B2 (en) 2013-01-11 2018-12-19 Data synchronization management

Country Status (1)

Country Link
US (7) US20140201140A1 (en)

Cited By (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150142742A1 (en) * 2013-11-17 2015-05-21 Zhen-Chao HONG System and method for syncing local directories that enable file access across multiple devices
US9262435B2 (en) 2013-01-11 2016-02-16 Commvault Systems, Inc. Location-based data synchronization management
US20170134492A1 (en) * 2014-03-05 2017-05-11 Commvault Systems, Inc. Cross-system storage management for transferring data across autonomous information management systems
US20170192852A1 (en) * 2016-01-06 2017-07-06 International Business Machines Corporation Excluding content items from a backup operation
US9753816B2 (en) 2014-12-05 2017-09-05 Commvault Systems, Inc. Synchronization based on filtered browsing
US9823842B2 (en) 2014-05-12 2017-11-21 The Research Foundation For The State University Of New York Gang migration of virtual machines using cluster-wide deduplication
US9928005B2 (en) 2015-01-20 2018-03-27 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US9952934B2 (en) 2015-01-20 2018-04-24 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US20180113896A1 (en) * 2016-10-20 2018-04-26 International Business Machines Corporation Synchronizing data across multiple instances of an application in a cloud
US10168929B2 (en) 2015-07-22 2019-01-01 Commvault Systems, Inc. Browse and restore for block-level backups
US10310950B2 (en) 2014-05-09 2019-06-04 Commvault Systems, Inc. Load balancing across multiple data paths
US10691187B2 (en) 2016-05-24 2020-06-23 Commvault Systems, Inc. Persistent reservations for virtual disk using multiple targets
US10740300B1 (en) 2017-12-07 2020-08-11 Commvault Systems, Inc. Synchronization of metadata in a distributed storage system
US10776329B2 (en) 2017-03-28 2020-09-15 Commvault Systems, Inc. Migration of a database management system to cloud storage
US10789387B2 (en) 2018-03-13 2020-09-29 Commvault Systems, Inc. Graphical representation of an information management system
US10795927B2 (en) 2018-02-05 2020-10-06 Commvault Systems, Inc. On-demand metadata extraction of clinical image data
US10831778B2 (en) 2012-12-27 2020-11-10 Commvault Systems, Inc. Application of information management policies based on operation with a geographic entity
US10838821B2 (en) 2017-02-08 2020-11-17 Commvault Systems, Inc. Migrating content and metadata from a backup system
US10860401B2 (en) 2014-02-27 2020-12-08 Commvault Systems, Inc. Work flow management for an information management system
US10891069B2 (en) 2017-03-27 2021-01-12 Commvault Systems, Inc. Creating local copies of data stored in online data repositories
US11074140B2 (en) 2017-03-29 2021-07-27 Commvault Systems, Inc. Live browsing of granular mailbox data
US11093336B2 (en) 2013-03-11 2021-08-17 Commvault Systems, Inc. Browsing data stored in a backup format
US11218450B2 (en) 2019-09-11 2022-01-04 Commvault Systems, Inc. Data protection component scaling in a cloud-based data storage system
US11249858B2 (en) 2014-08-06 2022-02-15 Commvault Systems, Inc. Point-in-time backups of a production application made accessible over fibre channel and/or ISCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host
US11294768B2 (en) 2017-06-14 2022-04-05 Commvault Systems, Inc. Live browsing of backed up data residing on cloned disks
US11308034B2 (en) 2019-06-27 2022-04-19 Commvault Systems, Inc. Continuously run log backup with minimal configuration and resource usage from the source machine
US11314687B2 (en) 2020-09-24 2022-04-26 Commvault Systems, Inc. Container data mover for migrating data between distributed data storage systems integrated with application orchestrators
US11321181B2 (en) 2008-06-18 2022-05-03 Commvault Systems, Inc. Data protection scheduling, such as providing a flexible backup window in a data protection system
US11321195B2 (en) 2017-02-27 2022-05-03 Commvault Systems, Inc. Hypervisor-independent reference copies of virtual machine payload data based on block-level pseudo-mount
US11392542B2 (en) 2008-09-05 2022-07-19 Commvault Systems, Inc. Image level copy or restore, such as image level restore without knowledge of data object metadata
US11416341B2 (en) 2014-08-06 2022-08-16 Commvault Systems, Inc. Systems and methods to reduce application downtime during a restore operation using a pseudo-storage device
US11436038B2 (en) 2016-03-09 2022-09-06 Commvault Systems, Inc. Hypervisor-independent block-level live browse for access to backed up virtual machine (VM) data and hypervisor-free file-level recovery (block- level pseudo-mount)
US11513922B2 (en) 2019-08-14 2022-11-29 Commvault Systems, Inc. Systems and methods for change block tracking for backing up changed data
US11570243B2 (en) 2020-09-22 2023-01-31 Commvault Systems, Inc. Decommissioning, re-commissioning, and commissioning new metadata nodes in a working distributed data storage system
US11573866B2 (en) 2018-12-10 2023-02-07 Commvault Systems, Inc. Evaluation and reporting of recovery readiness in a data storage management system
US11789830B2 (en) 2020-09-22 2023-10-17 Commvault Systems, Inc. Anti-entropy-based metadata recovery in a strongly consistent distributed data storage system
US11934356B2 (en) 2022-03-30 2024-03-19 Commvault Systems, Inc. Synchronization of metadata in a distributed storage system

Families Citing this family (93)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9705730B1 (en) 2013-05-07 2017-07-11 Axcient, Inc. Cloud storage using Merkle trees
US10284437B2 (en) 2010-09-30 2019-05-07 Efolder, Inc. Cloud-based virtual machines and offices
US9553860B2 (en) 2012-04-27 2017-01-24 Intralinks, Inc. Email effectivity facility in a networked secure collaborative exchange environment
US9785647B1 (en) 2012-10-02 2017-10-10 Axcient, Inc. File system virtualization
US9852140B1 (en) 2012-11-07 2017-12-26 Axcient, Inc. Efficient file replication
US9934241B2 (en) * 2013-03-05 2018-04-03 Hightail, Inc. System and method for cloud-based read-only folder synchronization
US9397907B1 (en) * 2013-03-07 2016-07-19 Axcient, Inc. Protection status determinations for computing devices
US9858052B2 (en) * 2013-03-21 2018-01-02 Razer (Asia-Pacific) Pte. Ltd. Decentralized operating system
US10656800B2 (en) 2013-03-29 2020-05-19 Microsoft Technology Licensing, Llc Visual configuration and activation
US9854035B2 (en) 2013-05-28 2017-12-26 International Business Machines Corporation Maintaining state synchronization of an application between computing devices as well as maintaining state synchronization of common information between different applications without requiring periodic synchronization
US10044799B2 (en) * 2013-05-28 2018-08-07 International Business Machines Corporation Implementing synchronization of state information betweeen instances of an application as well as between different applications in an efficient, scalable manner
US9710248B2 (en) * 2013-05-29 2017-07-18 Microsoft Technology Licensing, Llc Application install and layout syncing
US10452222B2 (en) 2013-05-29 2019-10-22 Microsoft Technology Licensing, Llc Coordination of system readiness tasks
WO2014191925A1 (en) * 2013-05-31 2014-12-04 Koninklijke Philips N.V. System and method for automatically uploading, downloading, and updating data such as sleep study data
US20150026257A1 (en) * 2013-07-16 2015-01-22 Dropbox, Inc. Music box
CN104426955B (en) * 2013-08-28 2018-05-04 北大方正集团有限公司 The processing method and cloud storage service device of shared file
TWI514811B (en) * 2013-11-28 2015-12-21 Synology Inc Method for controlling operations of network system
US20150163206A1 (en) * 2013-12-11 2015-06-11 Intralinks, Inc. Customizable secure data exchange environment
US9336228B2 (en) * 2013-12-18 2016-05-10 Verizon Patent And Licensing Inc. Synchronization of program code between revision management applications utilizing different version-control architectures
US10223328B1 (en) * 2014-02-03 2019-03-05 Emc Corporation Unified system for connecting a content repository to a file sharing service
CN103873567B (en) * 2014-03-03 2018-09-04 北京智谷睿拓技术服务有限公司 The data transmission method and data transmission device of task based access control
US20150253946A1 (en) * 2014-03-10 2015-09-10 Verizon Patent And Licensing Inc. Method and apparatus for transferring files based on user interaction
WO2015164521A1 (en) 2014-04-23 2015-10-29 Intralinks, Inc. Systems and methods of secure data exchange
JP5783301B1 (en) 2014-06-11 2015-09-24 富士ゼロックス株式会社 Communication terminal, communication system, and program
US10344567B2 (en) 2014-06-23 2019-07-09 Rockwell Automation Asia Pacific Business Center Pte. Ltd. Systems and methods for cloud-based automatic configuration of remote terminal units
US9547563B2 (en) * 2014-06-30 2017-01-17 Vmware, Inc. Recovery system and method for performing site recovery using replicated recovery-specific metadata
US10284242B2 (en) * 2014-07-09 2019-05-07 Livio, Inc. Custom broadcast audio content station
KR101634571B1 (en) * 2014-07-31 2016-07-08 주식회사 파수닷컴 Method for document file synchronization, Computer program for the same, and Recording medium storing computer program thereof
JP6442915B2 (en) * 2014-08-15 2018-12-26 富士ゼロックス株式会社 Communication terminal, communication system, and program
EP3186701B1 (en) * 2014-08-26 2022-10-05 Ctera Networks, Ltd. A method and computing device for allowing synchronized access to cloud
US9646010B2 (en) * 2014-08-27 2017-05-09 Mokhtarzada Holdings, Llc Method and system for expanding storage capacity of a drive using cloud storage systems
US9684561B1 (en) * 2014-09-29 2017-06-20 EMC IP Holding Company LLC Smart assistant for backing up data
US20160142485A1 (en) 2014-11-19 2016-05-19 Commvault Systems, Inc. Migration to cloud storage from backup
US20160147788A1 (en) * 2014-11-20 2016-05-26 Ricoh Company, Ltd. Pre-synchronization analysis between local documents and an online document management system
US9674343B2 (en) 2014-11-20 2017-06-06 At&T Intellectual Property I, L.P. System and method for instantiation of services at a location based on a policy
WO2016081942A2 (en) * 2014-11-21 2016-05-26 Security First Corp. Gateway for cloud-based secure storage
CN104636480B (en) * 2015-02-13 2018-09-28 华为技术有限公司 Rebuild the method and its device of standby host database
US10013431B2 (en) 2015-04-29 2018-07-03 Box, Inc. Secure cloud-based shared content
US9842062B2 (en) * 2015-05-31 2017-12-12 Apple Inc. Backup accessible by subset of related devices
US9666223B2 (en) * 2015-10-02 2017-05-30 International Business Machines Corporation Enhanced tape library cataloging
US10230792B2 (en) * 2015-10-23 2019-03-12 International Business Machines Corporation Synchronizing proprietary data in an external cloud with data in a private storage system
US10296594B1 (en) 2015-12-28 2019-05-21 EMC IP Holding Company LLC Cloud-aware snapshot difference determination
US10620811B2 (en) * 2015-12-30 2020-04-14 Dropbox, Inc. Native application collaboration
US11023433B1 (en) * 2015-12-31 2021-06-01 Emc Corporation Systems and methods for bi-directional replication of cloud tiered data across incompatible clusters
US10360023B2 (en) * 2016-02-17 2019-07-23 International Business Machines Corporation Source code revision control with selectable file portion synchronization
US11010409B1 (en) * 2016-03-29 2021-05-18 EMC IP Holding Company LLC Multi-streaming with synthetic replication
CN105897330A (en) * 2016-04-01 2016-08-24 严炜 Signal synchronization method used for UWB high-precision positioning system
US10762054B2 (en) 2016-07-22 2020-09-01 Microsoft Technology Licensing, Llc Cloud content states determination logic
US10379893B2 (en) * 2016-08-10 2019-08-13 Rackware, Inc. Container synchronization
US10712951B2 (en) * 2016-09-06 2020-07-14 Acronis International Gmbh System and method for backing up social network data
US10650621B1 (en) 2016-09-13 2020-05-12 Iocurrents, Inc. Interfacing with a vehicular controller area network
US10616327B2 (en) * 2016-09-20 2020-04-07 Microsoft Technology Licensing, Llc Policy based hydration behavior in cloud storage synchronization
US11368528B2 (en) 2016-09-20 2022-06-21 Microsoft Technology Licensing, Llc Dynamic storage management in cloud storage synchronization
CN107872490B (en) * 2016-09-28 2020-11-03 北京京东尚科信息技术有限公司 Intelligent electric appliance and method for realizing business data consistency between intelligent electric appliance and cloud end
EP3318989A1 (en) * 2016-11-08 2018-05-09 Thomson Licensing Method for manipulating a collection of audiovisual files
US10409495B1 (en) * 2016-12-29 2019-09-10 EMC IP Holding Company LLC Data optimization decision control based on file system metadata
US11356396B2 (en) * 2016-12-30 2022-06-07 Dropbox, Inc. Content management system with integrated email service
CN106874403A (en) * 2017-01-18 2017-06-20 武汉天喻教育科技有限公司 The system and method for differential synchronization is carried out to compressed file
US10917469B2 (en) * 2017-03-22 2021-02-09 Western Digital Technologies, Inc. Read performance enhancement by enabling read from secondary in highly available cluster setup
US10949398B2 (en) 2017-03-29 2021-03-16 Commvault Systems, Inc. Synchronization operations for network-accessible folders
US11410754B2 (en) * 2017-03-31 2022-08-09 Konica Minolta Healthcare Americas, Inc. Cloud-to-local, local-to-cloud switching and synchronization of medical images and data
US10565168B2 (en) * 2017-05-02 2020-02-18 Oxygen Cloud, Inc. Independent synchronization with state transformation
US11470131B2 (en) 2017-07-07 2022-10-11 Box, Inc. User device processing of information from a network-accessible collaboration system
CN109426588B (en) * 2017-08-28 2023-03-14 中兴通讯股份有限公司 Method and system for realizing data protection and data distribution processing module
CN110019502B (en) 2017-08-29 2023-03-21 阿里巴巴集团控股有限公司 Synchronization method between primary database and backup database, database system and device
US10929351B2 (en) 2018-06-29 2021-02-23 Microsoft Technology Licensing, Llc Determining document libraries to sync to a local computing device
CN108848393B (en) * 2018-07-26 2020-10-27 广州酷狗计算机科技有限公司 Method, device and equipment for showing entrance and storage medium
US11126506B2 (en) * 2018-08-06 2021-09-21 Acronis International Gmbh Systems and methods for predictive data protection
US11023419B2 (en) 2018-08-13 2021-06-01 Sap Se Folder key management
US11449579B2 (en) * 2018-09-19 2022-09-20 Servicenow, Inc. File-based software application discovery
US11698727B2 (en) * 2018-12-14 2023-07-11 Commvault Systems, Inc. Performing secondary copy operations based on deduplication performance
US10768971B2 (en) 2019-01-30 2020-09-08 Commvault Systems, Inc. Cross-hypervisor live mount of backed up virtual machine data
US10922283B2 (en) 2019-02-22 2021-02-16 Rackware, Inc. File synchronization
US11269816B2 (en) * 2019-03-25 2022-03-08 Parallels International Gmbh Recent file synchronization and aggregation methods and systems
US11366723B2 (en) 2019-04-30 2022-06-21 Commvault Systems, Inc. Data storage management system for holistic protection and migration of serverless applications across multi-cloud computing environments
US11461184B2 (en) 2019-06-17 2022-10-04 Commvault Systems, Inc. Data storage management system for protecting cloud-based data including on-demand protection, recovery, and migration of databases-as-a-service and/or serverless database management systems
CN110287061B (en) * 2019-06-25 2023-05-16 重庆城市职业学院 Information maintenance system based on computer
US11157513B2 (en) 2019-08-09 2021-10-26 Adp, Llc Data synchronization in a micro services environment
US11445018B2 (en) * 2019-12-12 2022-09-13 Dropbox, Inc. Technologies for synchronizing content items across content management systems
US11467753B2 (en) 2020-02-14 2022-10-11 Commvault Systems, Inc. On-demand restore of virtual machine data
CN111372223A (en) * 2020-02-17 2020-07-03 深圳壹账通智能科技有限公司 Mobile terminal, data synchronization method of application program of mobile terminal and storage medium
US11442768B2 (en) 2020-03-12 2022-09-13 Commvault Systems, Inc. Cross-hypervisor live recovery of virtual machines
US11514075B2 (en) * 2020-04-29 2022-11-29 EMC IP Holding Company, LLC System and method for prioritizing replication copy activity
US11748143B2 (en) 2020-05-15 2023-09-05 Commvault Systems, Inc. Live mount of virtual machines in a public cloud computing environment
US11500566B2 (en) 2020-08-25 2022-11-15 Commvault Systems, Inc. Cloud-based distributed data storage system using block-level deduplication based on backup frequencies of incoming backup copies
CN112667742A (en) * 2020-09-24 2021-04-16 紫光云技术有限公司 Master-slave copy account synchronization optimization method
US11914731B1 (en) * 2020-09-29 2024-02-27 Amazon Technologies, Inc. Cross-boundary data backup background
US11604706B2 (en) 2021-02-02 2023-03-14 Commvault Systems, Inc. Back up and restore related data on different cloud storage tiers
CN113127436B (en) * 2021-04-28 2023-07-25 北京奇艺世纪科技有限公司 Data synchronization method, device, server and storage medium
US20230185768A1 (en) * 2021-12-11 2023-06-15 Dropbox, Inc. Classifying and organizing digital content items automatically utilizing content item classification models
CN114968055B (en) * 2022-05-20 2023-07-07 重庆科创职业学院 Electronic glove synchronization system, method, equipment and storage medium
US20230385236A1 (en) * 2022-05-31 2023-11-30 Microsoft Technology Licensing, Llc Maintaining Stale Files to Minimize Computing Costs
CN114996982B (en) * 2022-08-08 2022-10-25 西南交通大学 Real-time simulation system and method of train track model based on cloud computing

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050144195A1 (en) * 1999-12-02 2005-06-30 Lambertus Hesselink Managed peer-to-peer applications, systems and methods for distributed data access and storage
US7421411B2 (en) * 2001-07-06 2008-09-02 Nokia Corporation Digital rights management in a mobile communications environment
US20130238696A1 (en) * 2012-03-08 2013-09-12 Abel Cotelo System and method for presenting synchronized media in a digital content environment
US20140172793A1 (en) * 2012-12-13 2014-06-19 Microsoft Corporation Opportunistic, priority-based object synchronization

Family Cites Families (483)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4267568A (en) 1975-12-03 1981-05-12 System Development Corporation Information storage and retrieval system
US4084231A (en) 1975-12-18 1978-04-11 International Business Machines Corporation System for facilitating the copying back of data in disc and tape units of a memory hierarchial system
US4296465A (en) 1977-11-03 1981-10-20 Honeywell Information Systems Inc. Data mover
GB2035014B (en) 1978-11-06 1982-09-29 British Broadcasting Corp Cyclic redundancy data check encoding method and apparatus
US4417321A (en) 1981-05-18 1983-11-22 International Business Machines Corp. Qualifying and sorting file record data
US4641274A (en) 1982-12-03 1987-02-03 International Business Machines Corporation Method for communicating changes made to text form a text processor to a remote host
WO1984002409A1 (en) 1982-12-09 1984-06-21 Sequoia Systems Inc Memory backup system
US4686620A (en) 1984-07-26 1987-08-11 American Telephone And Telegraph Company, At&T Bell Laboratories Database backup method
GB8622010D0 (en) 1986-09-12 1986-10-22 Hewlett Packard Ltd File backup facility
US5193154A (en) 1987-07-10 1993-03-09 Hitachi, Ltd. Buffered peripheral system and method for backing up and retrieving data to and from backup memory device
US5005122A (en) 1987-09-08 1991-04-02 Digital Equipment Corporation Arrangement with cooperating management server node and network service node
JPH0743676B2 (en) 1988-03-11 1995-05-15 株式会社日立製作所 Back-up data dump control method and device
US5455926A (en) 1988-04-05 1995-10-03 Data/Ware Development, Inc. Virtual addressing of optical storage media as magnetic tape equivalents
US4912637A (en) 1988-04-26 1990-03-27 Tandem Computers Incorporated Version management tool
US4995035A (en) 1988-10-31 1991-02-19 International Business Machines Corporation Centralized management in a computer network
JPH07122868B2 (en) 1988-11-29 1995-12-25 日本電気株式会社 Information processing equipment
US5093912A (en) 1989-06-26 1992-03-03 International Business Machines Corporation Dynamic resource pool expansion and contraction in multiprocessing environments
DE69031443T2 (en) 1989-06-30 1998-04-23 Digital Equipment Corp Method and arrangement for controlling shadow memories
DE69029289T2 (en) 1989-06-30 1997-06-26 Digital Equipment Corp Method and arrangement for controlling shadow memories
US5454099A (en) 1989-07-25 1995-09-26 International Business Machines Corporation CPU implemented method for backing up modified data sets in non-volatile store for recovery in the event of CPU failure
US5133065A (en) 1989-07-27 1992-07-21 Personal Computer Peripherals Corporation Backup computer program for networks
US5321816A (en) 1989-10-10 1994-06-14 Unisys Corporation Local-remote apparatus with specialized image storage modules
US5504873A (en) 1989-11-01 1996-04-02 E-Systems, Inc. Mass data storage and retrieval system
US5276867A (en) 1989-12-19 1994-01-04 Epoch Systems, Inc. Digital data storage system with improved data migration
US5276860A (en) 1989-12-19 1994-01-04 Epoch Systems, Inc. Digital data processor with improved backup storage
US5677900A (en) 1990-04-17 1997-10-14 Sharp Kabushiki Kaisha Method and apparatus for replacing a selected file with another longer or shorter file with no portion of the selected file remaining
JPH0410041A (en) 1990-04-27 1992-01-14 Toshiba Corp Data saving system
GB2246218B (en) 1990-07-18 1994-02-09 Stc Plc Distributed data processing systems
US5239647A (en) 1990-09-07 1993-08-24 International Business Machines Corporation Data storage hierarchy with shared storage level
US5544347A (en) 1990-09-24 1996-08-06 Emc Corporation Data storage system controlled remote data mirroring with respectively maintained data indices
US5301286A (en) 1991-01-02 1994-04-05 At&T Bell Laboratories Memory archiving indexing arrangement
US5212772A (en) 1991-02-11 1993-05-18 Gigatrend Incorporated System for storing data in backup tape device
US5317731A (en) 1991-02-25 1994-05-31 International Business Machines Corporation Intelligent page store for concurrent and consistent access to a database by a transaction processor and a query processor
US5287500A (en) 1991-06-03 1994-02-15 Digital Equipment Corporation System for allocating storage spaces based upon required and optional service attributes having assigned piorities
US5369757A (en) 1991-06-18 1994-11-29 Digital Equipment Corporation Recovery logging in the presence of snapshot files by ordering of buffer pool flushing
US5333315A (en) 1991-06-27 1994-07-26 Digital Equipment Corporation System of device independent file directories using a tag between the directories and file descriptors that migrate with the files
US5347653A (en) 1991-06-28 1994-09-13 Digital Equipment Corporation System for reconstructing prior versions of indexes using records indicating changes between successive versions of the indexes
WO1993003549A1 (en) 1991-07-31 1993-02-18 Euphonix, Inc. Automated audio mixer
US5410700A (en) 1991-09-04 1995-04-25 International Business Machines Corporation Computer system which supports asynchronous commitment of data
EP0531599B1 (en) 1991-09-13 1998-07-22 International Business Machines Corporation Configurable gigabit/s switch adapter
EP0541281B1 (en) 1991-11-04 1998-04-29 Commvault Systems, Inc. Incremental-computer-file backup using signatures
CA2285096C (en) 1991-11-12 2000-05-09 Ibm Canada Limited-Ibm Canada Limitee Logical mapping of data objects using data spaces
JPH05189281A (en) 1992-01-10 1993-07-30 Hitachi Ltd File assigning system for storage device
US5555404A (en) 1992-03-17 1996-09-10 Telenor As Continuously available database server having multiple groups of nodes with minimum intersecting sets of database fragment replicas
US5263154A (en) 1992-04-20 1993-11-16 International Business Machines Corporation Method and system for incremental time zero backup copying of data
US5241670A (en) 1992-04-20 1993-08-31 International Business Machines Corporation Method and system for automated backup copy ordering in a time zero backup copy session
US5241668A (en) 1992-04-20 1993-08-31 International Business Machines Corporation Method and system for automated termination and resumption in a time zero backup copy process
US5448718A (en) 1992-04-20 1995-09-05 International Business Machines Corporation Method and system for time zero backup session security
US5265159A (en) 1992-06-23 1993-11-23 Hughes Aircraft Company Secure file erasure
US5603012A (en) 1992-06-30 1997-02-11 Discovision Associates Start code detector
US5403639A (en) 1992-09-02 1995-04-04 Storage Technology Corporation File server having snapshot application data groups
EP0680634B1 (en) 1993-01-21 1997-05-14 Apple Computer, Inc. Apparatus and method for backing up data from networked computer storage devices
DE69434311D1 (en) 1993-02-01 2005-04-28 Sun Microsystems Inc ARCHIVING FILES SYSTEM FOR DATA PROVIDERS IN A DISTRIBUTED NETWORK ENVIRONMENT
US5719786A (en) 1993-02-03 1998-02-17 Novell, Inc. Digital media data stream network management system
JP3265697B2 (en) 1993-03-17 2002-03-11 富士ゼロックス株式会社 Image processing device
CA2121852A1 (en) 1993-04-29 1994-10-30 Larry T. Jost Disk meshing and flexible storage mapping with enhanced flexible caching
US7174352B2 (en) 1993-06-03 2007-02-06 Network Appliance, Inc. File system image transfer
US6604118B2 (en) 1998-07-31 2003-08-05 Network Appliance, Inc. File system image transfer
US5963962A (en) 1995-05-31 1999-10-05 Network Appliance, Inc. Write anywhere file-system layout
US5689706A (en) 1993-06-18 1997-11-18 Lucent Technologies Inc. Distributed systems with replicated files
JPH0721135A (en) 1993-07-02 1995-01-24 Fujitsu Ltd Data processing system with duplex monitor function
US5642496A (en) 1993-09-23 1997-06-24 Kanfi; Arnon Method of making a backup copy of a memory over a plurality of copying sessions
US5544345A (en) 1993-11-08 1996-08-06 International Business Machines Corporation Coherence controls for store-multiple shared data coordinated by cache directory entries in a shared electronic storage
WO1995013580A1 (en) 1993-11-09 1995-05-18 Arcada Software Data backup and restore system for a computer network
US5495607A (en) 1993-11-15 1996-02-27 Conner Peripherals, Inc. Network management system having virtual catalog overview of files distributively stored across network domain
US5799325A (en) 1993-11-19 1998-08-25 Smartpatents, Inc. System, method, and computer program product for generating equivalent text files
US5491810A (en) 1994-03-01 1996-02-13 International Business Machines Corporation Method and system for automated data storage system space allocation utilizing prioritized data set parameters
US5673381A (en) 1994-05-27 1997-09-30 Cheyenne Software International Sales Corp. System and parallel streaming and data stripping to back-up a network
US5638509A (en) 1994-06-10 1997-06-10 Exabyte Corporation Data storage and protection system
US5487072A (en) 1994-06-30 1996-01-23 Bell Communications Research Inc. Error monitoring algorithm for broadband signaling
US5598546A (en) 1994-08-31 1997-01-28 Exponential Technology, Inc. Dual-architecture super-scalar pipeline
US5802281A (en) 1994-09-07 1998-09-01 Rsi Systems, Inc. Peripheral audio/video communication system that interfaces with a host computer and determines format of coded audio/video signals
US5574906A (en) 1994-10-24 1996-11-12 International Business Machines Corporation System and method for reducing storage requirement in backup subsystems utilizing segmented compression and differencing
US5826046A (en) 1994-12-30 1998-10-20 International Business Machines Corporation Method and apparatus for polling and selecting any paired device in any drawer
US5604862A (en) 1995-03-14 1997-02-18 Network Integrity, Inc. Continuously-snapshotted protection of computer files
US5682513A (en) 1995-03-31 1997-10-28 International Business Machines Corporation Cache queue entry linking for DASD record updates
US5615392A (en) 1995-05-05 1997-03-25 Apple Computer, Inc. Method and apparatus for consolidated buffer handling for computer device input/output
US5559957A (en) 1995-05-31 1996-09-24 Lucent Technologies Inc. File system for a data storage device having a power fail recovery mechanism for write/replace operations
US6049889A (en) 1995-06-07 2000-04-11 Digital Equipment Corporation High performance recoverable communication method and apparatus for write-only networks
JPH0916463A (en) 1995-06-30 1997-01-17 Hitachi Ltd Dynamic allocation management system for memory area
US5699361A (en) 1995-07-18 1997-12-16 Industrial Technology Research Institute Multimedia channel formulation mechanism
US5813009A (en) 1995-07-28 1998-09-22 Univirtual Corp. Computer based records management system method
US5860104A (en) 1995-08-31 1999-01-12 Advanced Micro Devices, Inc. Data cache which speculatively updates a predicted data cache storage location with store data and subsequently corrects mispredicted updates
US5619644A (en) 1995-09-18 1997-04-08 International Business Machines Corporation Software directed microcode state save for distributed storage controller
US5907672A (en) 1995-10-04 1999-05-25 Stac, Inc. System for backing up computer disk volumes with error remapping of flawed memory addresses
JP3856855B2 (en) 1995-10-06 2006-12-13 三菱電機株式会社 Differential backup method
US5970255A (en) 1995-10-16 1999-10-19 Altera Corporation System for coupling programmable logic device to external circuitry which selects a logic standard and uses buffers to modify output and input signals accordingly
US5819020A (en) 1995-10-16 1998-10-06 Network Specialists, Inc. Real time backup system
US5778395A (en) 1995-10-23 1998-07-07 Stac, Inc. System for backing up files from disk volumes on multiple nodes of a computer network
US5737747A (en) 1995-10-27 1998-04-07 Emc Corporation Prefetching to service multiple video streams from an integrated cached disk array
US5829046A (en) 1995-10-27 1998-10-27 Emc Corporation On-line tape backup using an integrated cached disk array
US5987478A (en) 1995-10-31 1999-11-16 Intel Corporation Virtual small block file manager for flash memory array
US6122668A (en) 1995-11-02 2000-09-19 Starlight Networks Synchronization of audio and video signals in a live multicast in a LAN
US5805920A (en) 1995-11-13 1998-09-08 Tandem Computers Incorporated Direct bulk data transfers
US5729743A (en) 1995-11-17 1998-03-17 Deltatech Research, Inc. Computer apparatus and method for merging system deltas
US5933104A (en) 1995-11-22 1999-08-03 Microsoft Corporation Method and system for compression and decompression using variable-sized offset and length fields
US5675511A (en) 1995-12-21 1997-10-07 Intel Corporation Apparatus and method for event tagging for multiple audio, video, and data streams
US5761677A (en) 1996-01-03 1998-06-02 Sun Microsystems, Inc. Computer system method and apparatus providing for various versions of a file without requiring data copy or log operations
US5765173A (en) 1996-01-11 1998-06-09 Connected Corporation High performance backup via selective file saving which can perform incremental backups and exclude files and uses a changed block signature list
US5970233A (en) 1996-05-03 1999-10-19 Intel Corporation Multiple codecs for video encoding format compatibility
US5995091A (en) 1996-05-10 1999-11-30 Learn2.Com, Inc. System and method for streaming multimedia data
KR970076238A (en) 1996-05-23 1997-12-12 포만 제프리 엘 Servers, methods and program products thereof for creating and managing multiple copies of client data files
US6044444A (en) 1996-05-28 2000-03-28 Emc Corporation Remote data mirroring having preselection of automatic recovery or intervention required when a disruption is detected
US5819299A (en) 1996-06-06 1998-10-06 Electric Communities Process for distributed garbage collection
US5812398A (en) 1996-06-10 1998-09-22 Sun Microsystems, Inc. Method and system for escrowed backup of hotelled world wide web sites
US6279078B1 (en) 1996-06-28 2001-08-21 Compaq Computer Corporation Apparatus and method for synchronizing a cache mode in a dual controller, dual cache memory system operating in a plurality of cache modes
US5761734A (en) 1996-08-13 1998-06-02 International Business Machines Corporation Token-based serialisation of instructions in a multiprocessor system
US5933601A (en) 1996-09-30 1999-08-03 Ncr Corporation Method for systems management of object-based computer networks
US5790114A (en) 1996-10-04 1998-08-04 Microtouch Systems, Inc. Electronic whiteboard with multi-functional user interface
US5758359A (en) 1996-10-24 1998-05-26 Digital Equipment Corporation Method and apparatus for performing retroactive backups in a computer system
US5907621A (en) 1996-11-15 1999-05-25 International Business Machines Corporation System and method for session management
US6148377A (en) 1996-11-22 2000-11-14 Mangosoft Corporation Shared memory computer networks
US6487644B1 (en) 1996-11-22 2002-11-26 Veritas Operating Corporation System and method for multiplexed data back-up to a storage tape and restore operations using client identification tags
US5926836A (en) 1996-12-03 1999-07-20 Emc Corporation Computer and associated method for restoring data backed up on archive media
US5875478A (en) 1996-12-03 1999-02-23 Emc Corporation Computer backup using a file system, network, disk, tape and remote archiving repository media system
US5878408A (en) 1996-12-06 1999-03-02 International Business Machines Corporation Data management system and process
US6131095A (en) 1996-12-11 2000-10-10 Hewlett-Packard Company Method of accessing a target entity over a communications network
US6009274A (en) 1996-12-13 1999-12-28 3Com Corporation Method and apparatus for automatically updating software components on end systems over a network
US6202135B1 (en) 1996-12-23 2001-03-13 Emc Corporation System and method for reconstructing data associated with protected storage volume stored in multiple modules of back-up mass data storage facility
AU5929398A (en) 1997-01-23 1998-08-18 Overland Data, Inc. Virtual media library
US5875481A (en) 1997-01-30 1999-02-23 International Business Machines Corporation Dynamic reconfiguration of data storage devices to balance recycle throughput
US6963923B1 (en) 1997-02-10 2005-11-08 International Business Machines Corporation Method for file transfer restarts using standard internet protocol
US6049892C1 (en) 1997-02-24 2002-06-04 Ethos Software Corp Process and apparatus for downloading data from a server computer to a client computer
US6658526B2 (en) 1997-03-12 2003-12-02 Storage Technology Corporation Network attached virtual data storage subsystem
US6012090A (en) 1997-03-14 2000-01-04 At&T Corp. Client-side parallel requests for network services using group name association
US6003089A (en) 1997-03-31 1999-12-14 Siemens Information And Communication Networks, Inc. Method for constructing adaptive packet lengths in a congested network
US5924102A (en) 1997-05-07 1999-07-13 International Business Machines Corporation System and method for managing critical files
WO1998051096A1 (en) 1997-05-09 1998-11-12 Dsc Telecom L.P. Communication system with rapid database synchronization
US6094416A (en) 1997-05-09 2000-07-25 I/O Control Corporation Multi-tier architecture for control network
US6112239A (en) 1997-06-18 2000-08-29 Intervu, Inc System and method for server-side optimization of data delivery on a distributed computer network
US5887134A (en) 1997-06-30 1999-03-23 Sun Microsystems System and method for preserving message order while employing both programmed I/O and DMA operations
US5958005A (en) 1997-07-17 1999-09-28 Bell Atlantic Network Services, Inc. Electronic mail security
US6366988B1 (en) 1997-07-18 2002-04-02 Storactive, Inc. Systems and methods for electronic data storage management
US6137864A (en) 1997-07-25 2000-10-24 Lucent Technologies Inc. Specifiable delete times for voice messaging
US5877766A (en) 1997-08-15 1999-03-02 International Business Machines Corporation Multi-node user interface component and method thereof for use in accessing a plurality of linked records
EP0899662A1 (en) 1997-08-29 1999-03-03 Hewlett-Packard Company Backup and restore system for a computer network
DE69802294T2 (en) 1997-08-29 2002-05-16 Hewlett Packard Co SYSTEMS FOR DATA BACKUP AND RECOVERY
US6467035B2 (en) 1997-09-08 2002-10-15 Agere Systems Guardian Corp. System and method for performing table look-ups using a multiple data fetch architecture
US6067541A (en) 1997-09-17 2000-05-23 Microsoft Corporation Monitoring document changes in a file system of documents with the document change information stored in a persistent log
JP3901806B2 (en) 1997-09-25 2007-04-04 富士通株式会社 Information management system and secondary server
US5950205A (en) 1997-09-25 1999-09-07 Cisco Technology, Inc. Data transmission over the internet using a cache memory file system
US6275953B1 (en) 1997-09-26 2001-08-14 Emc Corporation Recovery from failure of a data processor in a network server
JP4128641B2 (en) 1997-10-13 2008-07-30 株式会社東芝 Data backup method
US6052735A (en) 1997-10-24 2000-04-18 Microsoft Corporation Electronic mail object synchronization between a desktop computer and mobile device
US6021415A (en) 1997-10-29 2000-02-01 International Business Machines Corporation Storage management system with file aggregation and space reclamation within aggregated files
US6418478B1 (en) 1997-10-30 2002-07-09 Commvault Systems, Inc. Pipelined high speed data transfer mechanism
US7581077B2 (en) 1997-10-30 2009-08-25 Commvault Systems, Inc. Method and system for transferring data in a storage operation
US7209972B1 (en) 1997-10-30 2007-04-24 Commvault Systems, Inc. High speed data transfer mechanism
JP4363676B2 (en) 1997-10-31 2009-11-11 株式会社東芝 Computer system
US6061692A (en) 1997-11-04 2000-05-09 Microsoft Corporation System and method for administering a meta database as an integral component of an information server
JPH11143754A (en) 1997-11-05 1999-05-28 Hitachi Ltd Version information and constitution information display method and device therefor, and computer readable recording medium for recording version information and constitution information display program
US6304880B1 (en) 1997-12-12 2001-10-16 International Business Machines Corporation Automated reclamation scheduling override in a virtual tape server
US6131190A (en) 1997-12-18 2000-10-10 Sidwell; Leland P. System for modifying JCL parameters to optimize data storage allocations
US6023710A (en) 1997-12-23 2000-02-08 Microsoft Corporation System and method for long-term administration of archival storage
US6374336B1 (en) 1997-12-24 2002-04-16 Avid Technology, Inc. Computer system and process for transferring multiple high bandwidth streams of data between multiple storage units and multiple applications in a scalable and reliable manner
US6076148A (en) 1997-12-26 2000-06-13 Emc Corporation Mass storage subsystem and backup arrangement for digital data processing system which permits information to be backed up while host computer(s) continue(s) operating in connection with information stored on mass storage subsystem
US6262749B1 (en) 1997-12-31 2001-07-17 Acuson Corporation Ultrasonic system and method for data transfer, storage and/or processing
US6154787A (en) 1998-01-21 2000-11-28 Unisys Corporation Grouping shared resources into one or more pools and automatically re-assigning shared resources from where they are not currently needed to where they are needed
US6131148A (en) 1998-01-26 2000-10-10 International Business Machines Corporation Snapshot copy of a secondary volume of a PPRC pair
US6260069B1 (en) 1998-02-10 2001-07-10 International Business Machines Corporation Direct data retrieval in a distributed computing system
US6105129A (en) 1998-02-18 2000-08-15 Advanced Micro Devices, Inc. Converting register data from a first format type to a second format type if a second type instruction consumes data produced by a first type instruction
US6374363B1 (en) 1998-02-24 2002-04-16 Adaptec, Inc. Method for generating a footprint image file for an intelligent backup and restoring system
DE69816415T2 (en) 1998-03-02 2004-04-15 Hewlett-Packard Co. (N.D.Ges.D.Staates Delaware), Palo Alto Data Backup System
US6026414A (en) 1998-03-05 2000-02-15 International Business Machines Corporation System including a proxy client to backup files in a distributed computing environment
US6292783B1 (en) 1998-03-06 2001-09-18 Plexar & Associates Phone-assisted clinical document information computer system for use in home healthcare, post-acute clinical care, hospice and home infusion applications
US6631477B1 (en) 1998-03-13 2003-10-07 Emc Corporation Host system for mass storage business continuance volumes
US6161111A (en) 1998-03-31 2000-12-12 Emc Corporation System and method for performing file-handling operations in a digital data processing system using an operating system-independent file map
US6175829B1 (en) 1998-04-22 2001-01-16 Nec Usa, Inc. Method and apparatus for facilitating query reformulation
US6167402A (en) 1998-04-27 2000-12-26 Sun Microsystems, Inc. High performance message store
US6163856A (en) 1998-05-29 2000-12-19 Sun Microsystems, Inc. Method and apparatus for file system disaster recovery
US6154852A (en) 1998-06-10 2000-11-28 International Business Machines Corporation Method and apparatus for data backup and recovery
US6665687B1 (en) 1998-06-26 2003-12-16 Alexander James Burke Composite user interface and search system for internet and multimedia applications
US6421711B1 (en) 1998-06-29 2002-07-16 Emc Corporation Virtual ports for data transferring of a data storage system
US6542909B1 (en) 1998-06-30 2003-04-01 Emc Corporation System for determining mapping of logical objects in a computer system
US6366986B1 (en) 1998-06-30 2002-04-02 Emc Corporation Method and apparatus for differential backup in a computer storage system
US6094605A (en) 1998-07-06 2000-07-25 Storage Technology Corporation Virtual automated cartridge system
US6353878B1 (en) 1998-08-13 2002-03-05 Emc Corporation Remote control of backup media in a secondary storage subsystem through access to a primary storage subsystem
US6269431B1 (en) 1998-08-13 2001-07-31 Emc Corporation Virtual storage and block level direct access of secondary storage for recovery of backup data
GB2341249A (en) 1998-08-17 2000-03-08 Connected Place Limited A method of generating a difference file defining differences between an updated file and a base file
US6446077B2 (en) 1998-09-21 2002-09-03 Microsoft Corporation Inherited information propagator for objects
US6304914B1 (en) 1998-09-22 2001-10-16 Microsoft Corporation Method and apparatus for pre-compression packaging
US6195695B1 (en) 1998-10-27 2001-02-27 International Business Machines Corporation Data processing system and method for recovering from system crashes
US6487561B1 (en) 1998-12-31 2002-11-26 Emc Corporation Apparatus and methods for copying, backing up, and restoring data using a backup segment size larger than the storage block size
US7107395B1 (en) 1998-12-31 2006-09-12 Emc Corporation Apparatus and methods for operating a computer storage system
US6397308B1 (en) 1998-12-31 2002-05-28 Emc Corporation Apparatus and method for differential backup and restoration of data in a computer storage system
US6212512B1 (en) 1999-01-06 2001-04-03 Hewlett-Packard Company Integration of a database into file management software for protecting, tracking and retrieving data
US6324581B1 (en) 1999-03-03 2001-11-27 Emc Corporation File server system using file system storage, data movers, and an exchange of meta data among data movers for file locking and direct access to shared file systems
US6350199B1 (en) 1999-03-16 2002-02-26 International Game Technology Interactive gaming machine and method with customized game screen presentation
US6681230B1 (en) 1999-03-25 2004-01-20 Lucent Technologies Inc. Real-time event processing system with service authoring environment
JP3763992B2 (en) 1999-03-30 2006-04-05 富士通株式会社 Data processing apparatus and recording medium
US6389432B1 (en) 1999-04-05 2002-05-14 Auspex Systems, Inc. Intelligent virtual volume access
JP3726559B2 (en) 1999-06-01 2005-12-14 株式会社日立製作所 Direct backup method and storage system
US6519679B2 (en) 1999-06-11 2003-02-11 Dell Usa, L.P. Policy based storage configuration
US6539462B1 (en) 1999-07-12 2003-03-25 Hitachi Data Systems Corporation Remote data copy using a prospective suspend command
US7035880B1 (en) 1999-07-14 2006-04-25 Commvault Systems, Inc. Modular backup and retrieval system used in conjunction with a storage area network
US7395282B1 (en) 1999-07-15 2008-07-01 Commvault Systems, Inc. Hierarchical backup and retrieval system
US6538669B1 (en) 1999-07-15 2003-03-25 Dell Products L.P. Graphical user interface for configuration of a storage system
US7389311B1 (en) 1999-07-15 2008-06-17 Commvault Systems, Inc. Modular backup and retrieval system
US6490666B1 (en) 1999-08-20 2002-12-03 Microsoft Corporation Buffering data in a hierarchical data storage environment
US6343324B1 (en) 1999-09-13 2002-01-29 International Business Machines Corporation Method and system for controlling access share storage devices in a network environment by configuring host-to-volume mapping data structures in the controller memory for granting and denying access to the devices
US6363464B1 (en) 1999-10-08 2002-03-26 Lucent Technologies Inc. Redundant processor controlled system
TW454120B (en) 1999-11-11 2001-09-11 Miralink Corp Flexible remote data mirroring
US9191443B2 (en) 1999-12-02 2015-11-17 Western Digital Technologies, Inc. Managed peer-to-peer applications, systems and methods for distributed data access and storage
US6434681B1 (en) 1999-12-02 2002-08-13 Emc Corporation Snapshot copy facility for a data storage system permitting continued host read/write access
KR20020090206A (en) 1999-12-07 2002-11-30 데이타 파운데이션 인코퍼레이션 Scalable storage architecture
US6526418B1 (en) 1999-12-16 2003-02-25 Livevault Corporation Systems and methods for backing up data files
US6625623B1 (en) 1999-12-16 2003-09-23 Livevault Corporation Systems and methods for backing up data files
US6401178B1 (en) 1999-12-23 2002-06-04 Emc Corporatiion Data processing method and apparatus for enabling independent access to replicated data
US6564228B1 (en) 2000-01-14 2003-05-13 Sun Microsystems, Inc. Method of enabling heterogeneous platforms to utilize a universal file system in a storage area network
ATE435464T1 (en) 2000-01-14 2009-07-15 Thinkstream Inc DISTRIBUTED INFORMATION NETWORK WITH GLOBAL ACCESS
US7003473B2 (en) 2000-01-18 2006-02-21 Wisor Telecom Corporation Fully integrated service manager with automatic flow-through interconnection
US6658436B2 (en) 2000-01-31 2003-12-02 Commvault Systems, Inc. Logical view and access to data managed by a modular data and storage management system
US6542972B2 (en) 2000-01-31 2003-04-01 Commvault Systems, Inc. Logical view and access to physical storage in modular data and storage management system
US6721767B2 (en) 2000-01-31 2004-04-13 Commvault Systems, Inc. Application specific rollback in a computer system
US6760723B2 (en) 2000-01-31 2004-07-06 Commvault Systems Inc. Storage management across multiple time zones
US7003641B2 (en) 2000-01-31 2006-02-21 Commvault Systems, Inc. Logical view with granular access to exchange data managed by a modular data and storage management system
US7065538B2 (en) 2000-02-11 2006-06-20 Quest Software, Inc. System and method for reconciling transactions between a replication system and a recovered database
US6651075B1 (en) 2000-02-16 2003-11-18 Microsoft Corporation Support for multiple temporal snapshots of same volume
US6473775B1 (en) 2000-02-16 2002-10-29 Microsoft Corporation System and method for growing differential file on a base volume of a snapshot
US6647473B1 (en) 2000-02-16 2003-11-11 Microsoft Corporation Kernel-based crash-consistency coordinator
US6615223B1 (en) 2000-02-29 2003-09-02 Oracle International Corporation Method and system for data replication
US6487645B1 (en) 2000-03-06 2002-11-26 International Business Machines Corporation Data storage subsystem with fairness-driven update blocking
US6728733B2 (en) 2000-03-29 2004-04-27 Komatsu Wall System Development Co., Ltd. System, method, and program product for administrating document file in computerized network system
US20020049778A1 (en) 2000-03-31 2002-04-25 Bell Peter W. System and method of information outsourcing
WO2001075679A1 (en) 2000-04-04 2001-10-11 Metamatrix, Inc. A system and method for accessing data in disparate information sources
AU2001293359A1 (en) 2000-04-14 2001-10-30 Mathias Client Management Software Company Method and system for interfacing clients with relationship management (rm) accounts and for permissioning marketing
US6571310B1 (en) 2000-04-20 2003-05-27 International Business Machines Corporation Method and apparatus for managing a heterogeneous data storage system
US6356801B1 (en) 2000-05-19 2002-03-12 International Business Machines Corporation High availability work queuing in an automated data storage library
EP1158409B1 (en) 2000-05-25 2008-05-28 Hitachi, Ltd. Storage system making possible data synchronisation confirmation at time of asynchronous remote copy
US6665815B1 (en) 2000-06-22 2003-12-16 Hewlett-Packard Development Company, L.P. Physical incremental backup using snapshots
US6330642B1 (en) 2000-06-29 2001-12-11 Bull Hn Informatin Systems Inc. Three interconnected raid disk controller data processing system architecture
EP1174795A1 (en) 2000-07-19 2002-01-23 Hewlett-Packard Company, A Delaware Corporation Multiplexing computing apparatus
US20020049738A1 (en) 2000-08-03 2002-04-25 Epstein Bruce A. Information collaboration and reliability assessment
US6886020B1 (en) 2000-08-17 2005-04-26 Emc Corporation Method and apparatus for storage system metrics management and archive
US7082441B1 (en) 2000-08-17 2006-07-25 Emc Corporation Method and storage and manipulation of storage system metrics
US6751635B1 (en) 2000-08-18 2004-06-15 Network Appliance, Inc. File deletion and truncation using a zombie file space
GB2366014B (en) 2000-08-19 2004-10-13 Ibm Free space collection in information storage systems
US7278142B2 (en) 2000-08-24 2007-10-02 Veritas Operating Corporation Dynamic computing environment using remotely allocable resources
US6732125B1 (en) 2000-09-08 2004-05-04 Storage Technology Corporation Self archiving log structured volume with intrinsic data protection
EP1193616A1 (en) 2000-09-29 2002-04-03 Sony France S.A. Fixed-length sequence generation of items out of a database using descriptors
JP2002108662A (en) 2000-10-02 2002-04-12 Fujitsu Ltd Method for managing information
US6973553B1 (en) 2000-10-20 2005-12-06 International Business Machines Corporation Method and apparatus for using extended disk sector formatting to assist in backup and hierarchical storage management
US7225219B2 (en) 2000-11-29 2007-05-29 Broadspider Networks, Inc. Distributed caching architecture for computer networks
US6871271B2 (en) 2000-12-21 2005-03-22 Emc Corporation Incrementally restoring a mass storage device to a prior state
US6647396B2 (en) 2000-12-28 2003-11-11 Trilogy Development Group, Inc. Classification based content management system
US6799258B1 (en) 2001-01-10 2004-09-28 Datacore Software Corporation Methods and apparatus for point-in-time volumes
US6978265B2 (en) 2001-01-16 2005-12-20 Lakeside Software, Inc. System and method for managing information for a plurality of computer systems in a distributed network
US6847983B2 (en) 2001-02-28 2005-01-25 Kiran Somalwar Application independent write monitoring method for fast backup and synchronization of open files
US7734715B2 (en) 2001-03-01 2010-06-08 Ricoh Company, Ltd. System, computer program product and method for managing documents
US7194454B2 (en) 2001-03-12 2007-03-20 Lucent Technologies Method for organizing records of database search activity by topical relevance
US6836779B2 (en) 2001-03-13 2004-12-28 Christian D. Poulin Network transaction method
US6728736B2 (en) 2001-03-14 2004-04-27 Storage Technology Corporation System and method for synchronizing a data copy using an accumulation remote copy trio
JP3693958B2 (en) 2001-04-05 2005-09-14 松下電器産業株式会社 Distributed document search method and apparatus, distributed document search program, and recording medium recording the program
CA2347647A1 (en) 2001-05-15 2002-11-15 Ibm Canada Limited-Ibm Canada Limitee Storing and restoring snapshots of a computer process
US7111023B2 (en) 2001-05-24 2006-09-19 Oracle International Corporation Synchronous change data capture in a relational database
FI114417B (en) * 2001-06-15 2004-10-15 Nokia Corp Select data for synchronization
US6763351B1 (en) 2001-06-18 2004-07-13 Siebel Systems, Inc. Method, apparatus, and system for attaching search results
GB0116686D0 (en) 2001-07-07 2001-08-29 Hewlett Packard Co Data backup
US7062761B2 (en) 2001-07-10 2006-06-13 Micron Technology, Inc. Dynamic arrays and overlays with bounds policies
US20030018657A1 (en) 2001-07-18 2003-01-23 Imation Corp. Backup of data on a network
US6948038B2 (en) 2001-07-24 2005-09-20 Microsoft Corporation System and method for backing up and restoring data
US7685126B2 (en) 2001-08-03 2010-03-23 Isilon Systems, Inc. System and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system
US6662198B2 (en) 2001-08-30 2003-12-09 Zoteca Inc. Method and system for asynchronous transmission, backup, distribution of data and file sharing
JP4161557B2 (en) 2001-09-03 2008-10-08 株式会社日立製作所 Packet transfer method and apparatus
US20030061491A1 (en) 2001-09-21 2003-03-27 Sun Microsystems, Inc. System and method for the allocation of network storage
EP1442387A4 (en) 2001-09-28 2008-01-23 Commvault Systems Inc System and method for archiving objects in an information store
DE60232165D1 (en) 2001-09-28 2009-06-10 Commvault Systems Inc SYSTEM AND METHOD FOR PRODUCING AND MANAGING FAST RECOVERY VOLUME
US6925512B2 (en) 2001-10-15 2005-08-02 Intel Corporation Communication between two embedded processors
US7127477B2 (en) 2001-11-06 2006-10-24 Everyware Solutions Inc. Method and system for access to automatically synchronized remote files
AU2002365580A1 (en) 2001-11-23 2003-06-10 Commvault Systems, Inc. Selective data replication system and method
US7596586B2 (en) 2003-04-03 2009-09-29 Commvault Systems, Inc. System and method for extended media retention
US7296125B2 (en) 2001-11-29 2007-11-13 Emc Corporation Preserving a snapshot of selected data of a mass storage system
US6898688B2 (en) 2001-12-28 2005-05-24 Storage Technology Corporation Data management appliance
EP1324216A1 (en) 2001-12-28 2003-07-02 Deutsche Thomson-Brandt Gmbh Machine for classification of metadata
US6938180B1 (en) 2001-12-31 2005-08-30 Emc Corporation Logical restores of physically backed up data
US7139932B2 (en) 2002-01-03 2006-11-21 Hitachi, Ltd. Data synchronization of multiple remote storage after remote copy suspension
US6948089B2 (en) 2002-01-10 2005-09-20 Hitachi, Ltd. Apparatus and method for multiple generation remote backup and fast restore
US7237075B2 (en) 2002-01-22 2007-06-26 Columbia Data Products, Inc. Persistent snapshot methods
US20030220949A1 (en) 2002-01-22 2003-11-27 Columbia Data Products, Inc. Automatic deletion in data storage management
US6748504B2 (en) 2002-02-15 2004-06-08 International Business Machines Corporation Deferred copy-on-write of a snapshot
US7343365B2 (en) 2002-02-20 2008-03-11 Microsoft Corporation Computer system architecture for automatic context associations
JP2003248611A (en) 2002-02-26 2003-09-05 Hitachi Ltd Storage management integration system and its storage management control method
US7373364B1 (en) 2002-03-05 2008-05-13 Network Appliance, Inc. System and method for creating a point-in-time restoration of a database file
US6941393B2 (en) 2002-03-05 2005-09-06 Agilent Technologies, Inc. Pushback FIFO
US6880051B2 (en) 2002-03-14 2005-04-12 International Business Machines Corporation Method, system, and program for maintaining backup copies of files in a backup storage device
US20030177149A1 (en) 2002-03-18 2003-09-18 Coombs David Lawrence System and method for data backup
EP1349088B1 (en) 2002-03-19 2010-11-03 Network Appliance, Inc. System and method for determining and transmitting changes in snapshots
US6993539B2 (en) 2002-03-19 2006-01-31 Network Appliance, Inc. System and method for determining changes in two snapshots and for transmitting changes to destination snapshot
US7467167B2 (en) 2002-03-19 2008-12-16 Network Appliance, Inc. System and method for coalescing a plurality of snapshots
US7475098B2 (en) 2002-03-19 2009-01-06 Network Appliance, Inc. System and method for managing a plurality of snapshots
US7051050B2 (en) 2002-03-19 2006-05-23 Netwrok Appliance, Inc. System and method for restoring a single file from a snapshot
US7225204B2 (en) 2002-03-19 2007-05-29 Network Appliance, Inc. System and method for asynchronous mirroring of snapshots at a destination using a purgatory directory and inode mapping
US7032131B2 (en) 2002-03-26 2006-04-18 Hewlett-Packard Development Company, L.P. System and method for ensuring merge completion in a storage area network
US6983351B2 (en) 2002-04-11 2006-01-03 International Business Machines Corporation System and method to guarantee overwrite of expired data in a virtual tape server
US7532340B2 (en) 2002-04-19 2009-05-12 Toshiba Tec Kabushiki Kaisha Document management system rule-based automation
US6981177B2 (en) 2002-04-19 2005-12-27 Computer Associates Think, Inc. Method and system for disaster recovery
US7814053B1 (en) 2002-05-02 2010-10-12 Access Systems Americas, Inc. Synchronization of computer databases using caching agents
US6871163B2 (en) 2002-05-31 2005-03-22 Sap Aktiengesellschaft Behavior-based adaptation of computer systems
US7269612B2 (en) 2002-05-31 2007-09-11 International Business Machines Corporation Method, system, and program for a policy based storage manager
US6944796B2 (en) 2002-06-27 2005-09-13 Intel Corporation Method and system to implement a system event log for system manageability
US7085959B2 (en) 2002-07-03 2006-08-01 Hewlett-Packard Development Company, L.P. Method and apparatus for recovery from loss of lock step
US7844577B2 (en) 2002-07-15 2010-11-30 Symantec Corporation System and method for maintaining a backup storage system for a computer system
US7085787B2 (en) 2002-07-19 2006-08-01 International Business Machines Corporation Capturing data changes utilizing data-space tracking
US7096330B1 (en) 2002-07-29 2006-08-22 Veritas Operating Corporation Symmetrical data change tracking
US6952758B2 (en) 2002-07-31 2005-10-04 International Business Machines Corporation Method and system for providing consistent data modification information to clients in a storage system
US6792518B2 (en) 2002-08-06 2004-09-14 Emc Corporation Data storage system having mata bit maps for indicating whether data blocks are invalid in snapshot copies
US20040107199A1 (en) 2002-08-22 2004-06-03 Mdt Inc. Computer application backup method and system
US7103731B2 (en) 2002-08-29 2006-09-05 International Business Machines Corporation Method, system, and program for moving data among storage units
US7810067B2 (en) 2002-08-30 2010-10-05 Sap Aktiengesellschaft Development processes representation and management
US7130970B2 (en) 2002-09-09 2006-10-31 Commvault Systems, Inc. Dynamic storage device pooling in a computer system
US7246140B2 (en) 2002-09-10 2007-07-17 Exagrid Systems, Inc. Method and apparatus for storage system to provide distributed data storage and protection
US8370542B2 (en) 2002-09-16 2013-02-05 Commvault Systems, Inc. Combined stream auxiliary copy system and method
WO2004025423A2 (en) 2002-09-16 2004-03-25 Commvault Systems, Inc. System and method for blind media support
US7234115B1 (en) 2002-09-26 2007-06-19 Home Director, Inc. Home entertainment system and method
US7051053B2 (en) 2002-09-30 2006-05-23 Dinesh Sinha Method of lazily replicating files and monitoring log in backup file system
US6938135B1 (en) 2002-10-04 2005-08-30 Veritas Operating Corporation Incremental backup of a data volume
WO2004034197A2 (en) 2002-10-07 2004-04-22 Commvault Systems, Inc. System and method for managing stored data
US8121978B2 (en) 2002-11-15 2012-02-21 Sybase, Inc. Database system providing improved methods for data replication
WO2004047078A2 (en) 2002-11-20 2004-06-03 Filesx Ltd. Fast backup storage and fast recovery of data (fbsrd)
US7827283B2 (en) 2003-02-19 2010-11-02 International Business Machines Corporation System for managing and controlling storage access requirements
US20040193953A1 (en) 2003-02-21 2004-09-30 Sun Microsystems, Inc. Method, system, and program for maintaining application program configuration settings
US7231544B2 (en) 2003-02-27 2007-06-12 Hewlett-Packard Development Company, L.P. Restoring data from point-in-time representations of the data
US7174433B2 (en) 2003-04-03 2007-02-06 Commvault Systems, Inc. System and method for dynamically sharing media in a computer network
US7155465B2 (en) 2003-04-18 2006-12-26 Lee Howard F Method and apparatus for automatically archiving a file system
US8069218B1 (en) 2003-05-05 2011-11-29 Parallels Holdings, Ltd. System, method and computer program product for process migration with planned minimized down-time
JP2004334574A (en) 2003-05-08 2004-11-25 Hitachi Ltd Operation managing program and method of storage, and managing computer
US7853462B2 (en) 2003-05-12 2010-12-14 I2 Technologies Us, Inc. Optimizing an inventory of a supply chain
US7240219B2 (en) 2003-05-25 2007-07-03 Sandisk Il Ltd. Method and system for maintaining backup of portable storage devices
JP2004354752A (en) 2003-05-29 2004-12-16 Sumitomo Electric Ind Ltd Joint folder for single-core bidirectional optical module
US20040254919A1 (en) 2003-06-13 2004-12-16 Microsoft Corporation Log parser
US20040260678A1 (en) 2003-06-18 2004-12-23 Microsoft Corporation State based configuration failure detection using checkpoint comparison
US7567991B2 (en) 2003-06-25 2009-07-28 Emc Corporation Replication of snapshot using a file system copy differential
US7275177B2 (en) 2003-06-25 2007-09-25 Emc Corporation Data recovery with internet protocol replication with or without full resync
WO2005001646A2 (en) 2003-06-25 2005-01-06 Arkivio, Inc. Techniques for performing policy automated operations
US7454569B2 (en) 2003-06-25 2008-11-18 Commvault Systems, Inc. Hierarchical system and method for performing storage operations in a computer network
US7523276B1 (en) 2003-06-30 2009-04-21 Veritas Software Corporation Synchronization of selected data from snapshots stored on different storage volumes
US8095511B2 (en) 2003-06-30 2012-01-10 Microsoft Corporation Database data recovery system and method
JP4421230B2 (en) 2003-08-12 2010-02-24 株式会社日立製作所 Performance information analysis method
US7143117B2 (en) 2003-09-25 2006-11-28 International Business Machines Corporation Method, system, and program for data synchronization by determining whether a first identifier for a portion of data at a first source and a second identifier for a portion of corresponding data at a second source match
US7188292B2 (en) 2003-09-26 2007-03-06 Nortel Networks Limited Data mirroring system
US7225208B2 (en) 2003-09-30 2007-05-29 Iron Mountain Incorporated Systems and methods for backing up data files
US7496690B2 (en) 2003-10-09 2009-02-24 Intel Corporation Method, system, and program for managing memory for data transmission through a network
US8229888B1 (en) 2003-10-15 2012-07-24 Radix Holdings, Llc Cross-device playback with synchronization of consumption state
JP4267420B2 (en) 2003-10-20 2009-05-27 株式会社日立製作所 Storage apparatus and backup acquisition method
US7315923B2 (en) 2003-11-13 2008-01-01 Commvault Systems, Inc. System and method for combining data streams in pipelined storage operations in a storage network
WO2005050381A2 (en) 2003-11-13 2005-06-02 Commvault Systems, Inc. Systems and methods for performing storage operations using network attached storage
US7440982B2 (en) 2003-11-13 2008-10-21 Commvault Systems, Inc. System and method for stored data archive verification
WO2005048085A2 (en) 2003-11-13 2005-05-26 Commvault Systems, Inc. System and method for performing an image level snapshot and for restoring partial volume data
US7613748B2 (en) 2003-11-13 2009-11-03 Commvault Systems, Inc. Stored data reverification management system and method
US7412583B2 (en) 2003-11-14 2008-08-12 International Business Machines Corporation Virtual incremental storage method
US7225210B2 (en) 2003-11-20 2007-05-29 Overland Storage, Inc. Block level data snapshot system and method
EP1687745A2 (en) 2003-11-26 2006-08-09 Veritas Operating Corporation System and method for generating extensible file system metadata and file system content processing
US7272606B2 (en) 2003-11-26 2007-09-18 Veritas Operating Corporation System and method for detecting and storing file content access information within a file system
US7228456B2 (en) 2003-12-01 2007-06-05 Emc Corporation Data recovery for virtual ordered writes for multiple storage devices
CA2452251C (en) 2003-12-04 2010-02-09 Timothy R. Jewell Data backup system and method
US7155633B2 (en) 2003-12-08 2006-12-26 Solid Data Systems, Inc. Exchange server method and system
US7519726B2 (en) 2003-12-12 2009-04-14 International Business Machines Corporation Methods, apparatus and computer programs for enhanced access to resources within a network
US7720801B2 (en) 2003-12-19 2010-05-18 Netapp, Inc. System and method for supporting asynchronous data replication with very short update intervals
US7039661B1 (en) 2003-12-29 2006-05-02 Veritas Operating Corporation Coordinated dirty block tracking
US7293133B1 (en) 2003-12-31 2007-11-06 Veritas Operating Corporation Performing operations without requiring split mirrors in a multi-class file system
US7103740B1 (en) 2003-12-31 2006-09-05 Veritas Operating Corporation Backup mechanism for a multi-class file system
US7627617B2 (en) 2004-02-11 2009-12-01 Storage Technology Corporation Clustered hierarchical file services
JP2005235058A (en) 2004-02-23 2005-09-02 Hitachi Ltd Snapshot acquisition method, snapshot acquisition device, and computer program provided with snapshot acquisition function
JP4454342B2 (en) 2004-03-02 2010-04-21 株式会社日立製作所 Storage system and storage system control method
US7343356B2 (en) 2004-04-30 2008-03-11 Commvault Systems, Inc. Systems and methods for storage modeling and costing
US8055745B2 (en) 2004-06-01 2011-11-08 Inmage Systems, Inc. Methods and apparatus for accessing data from a primary data storage system for secondary storage
US20050278458A1 (en) 2004-06-09 2005-12-15 Microsoft Corporation Analysis services database synchronization
US7343518B2 (en) 2004-06-23 2008-03-11 Intel Corporation Method for data backup of computing platforms that are occasionally connected
US7383462B2 (en) 2004-07-02 2008-06-03 Hitachi, Ltd. Method and apparatus for encrypted remote copy for secure data backup and restoration
US20060020616A1 (en) 2004-07-22 2006-01-26 Geoffrey Hardy Indexing operational logs in a distributed processing system
US7467267B1 (en) 2004-07-23 2008-12-16 Sprint Communications Company L.P. Method and system for backing up or restoring data in remote devices over a communications network
US7661135B2 (en) 2004-08-10 2010-02-09 International Business Machines Corporation Apparatus, system, and method for gathering trace data indicative of resource activity
US7257689B1 (en) 2004-10-15 2007-08-14 Veritas Operating Corporation System and method for loosely coupled temporal storage management
JP4507249B2 (en) 2004-10-19 2010-07-21 株式会社日立製作所 System and method for controlling storage device updates
GB2435756B (en) 2004-11-05 2008-12-10 Commvault Systems Inc Method and system of pooling storage devices
WO2006053050A2 (en) 2004-11-08 2006-05-18 Commvault Systems, Inc. System and method for performing auxiliary storage operations
JP4349301B2 (en) 2004-11-12 2009-10-21 日本電気株式会社 Storage management system, method and program
US20060136685A1 (en) 2004-12-17 2006-06-22 Sanrad Ltd. Method and system to maintain data consistency over an internet small computer system interface (iSCSI) network
US7415488B1 (en) 2004-12-31 2008-08-19 Symantec Operating Corporation System and method for redundant storage consistency recovery
US7512601B2 (en) 2005-01-18 2009-03-31 Microsoft Corporation Systems and methods that enable search engines to present relevant snippets
JP2006285448A (en) 2005-03-31 2006-10-19 Oki Electric Ind Co Ltd Redundant system
JP2006302015A (en) 2005-04-21 2006-11-02 Hitachi Ltd Storage system and data management method
US7496589B1 (en) 2005-07-09 2009-02-24 Google Inc. Highly compressed randomly accessed storage of large tables with arbitrary columns
US7716171B2 (en) 2005-08-18 2010-05-11 Emc Corporation Snapshot indexing
US20070043956A1 (en) 2005-08-19 2007-02-22 Microsoft Corporation System and methods that facilitate third party code test development
US7617541B2 (en) 2005-09-09 2009-11-10 Netapp, Inc. Method and/or system to authorize access to stored data
JP4688617B2 (en) 2005-09-16 2011-05-25 株式会社日立製作所 Storage control system and method
JP4668763B2 (en) 2005-10-20 2011-04-13 株式会社日立製作所 Storage device restore method and storage device
WO2007053314A2 (en) 2005-10-28 2007-05-10 Goldengate Software, Inc. Apparatus and method for creating a real time database replica
US7840285B2 (en) 2005-10-28 2010-11-23 Invensys Systems, Inc. Sequence of events recorder facility for an industrial process control environment
US8595633B2 (en) 2005-10-31 2013-11-26 Yahoo! Inc. Method and system for displaying contextual rotating advertisements
US7529748B2 (en) 2005-11-15 2009-05-05 Ji-Rong Wen Information classification paradigm
WO2007062254A2 (en) 2005-11-28 2007-05-31 Commvault Systems, Inc. Systems and methods for data management
US7668879B2 (en) 2005-11-30 2010-02-23 Oracle International Corporation Database system configured for automatic failover with no data loss
US7627584B2 (en) 2005-11-30 2009-12-01 Oracle International Corporation Database system configured for automatic failover with no data loss
US7543125B2 (en) 2005-12-19 2009-06-02 Commvault Systems, Inc. System and method for performing time-flexible calendric storage operations
US7962709B2 (en) 2005-12-19 2011-06-14 Commvault Systems, Inc. Network redirector systems and methods for performing data replication
CA2632935C (en) 2005-12-19 2014-02-04 Commvault Systems, Inc. Systems and methods for performing data replication
US7651593B2 (en) 2005-12-19 2010-01-26 Commvault Systems, Inc. Systems and methods for performing data replication
US7636743B2 (en) 2005-12-19 2009-12-22 Commvault Systems, Inc. Pathname translation in a data replication system
US7620710B2 (en) 2005-12-19 2009-11-17 Commvault Systems, Inc. System and method for performing multi-path storage operations
US7617253B2 (en) 2005-12-19 2009-11-10 Commvault Systems, Inc. Destination systems and methods for performing data replication
US7606844B2 (en) * 2005-12-19 2009-10-20 Commvault Systems, Inc. System and method for performing replication copy storage operations
US7617262B2 (en) 2005-12-19 2009-11-10 Commvault Systems, Inc. Systems and methods for monitoring application data in a data replication system
US20070168721A1 (en) 2005-12-22 2007-07-19 Nokia Corporation Method, network entity, system, electronic device and computer program product for backup and restore provisioning
US7500150B2 (en) 2005-12-30 2009-03-03 Microsoft Corporation Determining the level of availability of a computing resource
US8533409B2 (en) 2006-01-26 2013-09-10 Infortrend Technology, Inc. Method of managing data snapshot images in a storage system
US8170985B2 (en) 2006-01-31 2012-05-01 Emc Corporation Primary stub file retention and secondary retention coordination in a hierarchical storage system
US7698318B2 (en) 2006-02-10 2010-04-13 Microsoft Corporation Automatically determining file replication mechanisms
US8548948B2 (en) 2006-04-11 2013-10-01 Oracle International Corporation Methods and apparatus for a fine grained file data storage system
US7613750B2 (en) 2006-05-29 2009-11-03 Microsoft Corporation Creating frequent application-consistent backups efficiently
US8190571B2 (en) 2006-06-07 2012-05-29 Microsoft Corporation Managing data with backup server indexing
US8495102B2 (en) 2006-09-01 2013-07-23 International Business Machines Corporation Method, system, and program product for organizing a database
US7882077B2 (en) 2006-10-17 2011-02-01 Commvault Systems, Inc. Method and system for offline indexing of content and classifying stored data
KR100791325B1 (en) 2006-10-27 2008-01-03 삼성전자주식회사 Apparatus and method for managing nonvolatile memory
EP2102750B1 (en) 2006-12-04 2014-11-05 Commvault Systems, Inc. System and method for creating copies of data, such as archive copies
US8677091B2 (en) 2006-12-18 2014-03-18 Commvault Systems, Inc. Writing data and storage system specific metadata to network attached storage device
US7840537B2 (en) 2006-12-22 2010-11-23 Commvault Systems, Inc. System and method for storing redundant information
US7734669B2 (en) 2006-12-22 2010-06-08 Commvault Systems, Inc. Managing copies of data
US8631088B2 (en) 2007-01-07 2014-01-14 Apple Inc. Prioritized data synchronization with host device
JP5207637B2 (en) 2007-02-23 2013-06-12 株式会社日立製作所 Backup control method for acquiring multiple backups in one or more secondary storage systems
WO2008121873A1 (en) * 2007-03-29 2008-10-09 Vmware, Inc. Synchronization and customization of a clone computer
US8239351B2 (en) 2007-06-07 2012-08-07 Apple Inc. Methods and systems for managing permissions data
US7827440B1 (en) 2007-11-01 2010-11-02 Apple Inc. Re-synchronizing corrupted data
US20090150462A1 (en) 2007-12-07 2009-06-11 Brocade Communications Systems, Inc. Data migration operations in a distributed file system
US8078957B2 (en) 2008-05-02 2011-12-13 Microsoft Corporation Document synchronization over stateless protocols
US8315978B2 (en) 2008-06-19 2012-11-20 Microsoft Corporation Synchronization adapter for synchronizing data to applications that do not directly support synchronization
US9098495B2 (en) 2008-06-24 2015-08-04 Commvault Systems, Inc. Application-aware and remote single instance data management
US8219524B2 (en) 2008-06-24 2012-07-10 Commvault Systems, Inc. Application-aware and remote single instance data management
US8166263B2 (en) 2008-07-03 2012-04-24 Commvault Systems, Inc. Continuous data protection over intermittent connections, such as continuous data backup for laptops or wireless devices
US8015343B2 (en) 2008-08-08 2011-09-06 Amazon Technologies, Inc. Providing executing programs with reliable access to non-local block data storage
US8307177B2 (en) 2008-09-05 2012-11-06 Commvault Systems, Inc. Systems and methods for management of virtualization data
US9367257B2 (en) 2008-09-11 2016-06-14 Microsoft Technology Licensing, Llc Techniques for resource location and migration across data centers
US8655840B2 (en) 2008-12-03 2014-02-18 Nokia Corporation Method, apparatus and computer program product for sub-file level synchronization
US9495382B2 (en) 2008-12-10 2016-11-15 Commvault Systems, Inc. Systems and methods for performing discrete data replication
US8204859B2 (en) 2008-12-10 2012-06-19 Commvault Systems, Inc. Systems and methods for managing replicated database data
JP4843687B2 (en) 2009-01-09 2011-12-21 富士通株式会社 Backup control device, storage system, backup control program, and backup control method
US8578120B2 (en) 2009-05-22 2013-11-05 Commvault Systems, Inc. Block-level single instancing
US8219526B2 (en) 2009-06-05 2012-07-10 Microsoft Corporation Synchronizing file partitions utilizing a server storage model
US20100333116A1 (en) 2009-06-30 2010-12-30 Anand Prahlad Cloud gateway system for managing data storage to cloud storage sites
US8645327B2 (en) 2009-09-30 2014-02-04 Apple Inc. Management of access to data distributed across multiple computing devices
CN101751473A (en) 2009-12-31 2010-06-23 中兴通讯股份有限公司 The searching of a kind of amendment record item, renewal and method for synchronous and data sync equipment
US20110196957A1 (en) 2010-02-05 2011-08-11 International Business Machines Corporation Real-Time Policy Visualization by Configuration Item to Demonstrate Real-Time and Historical Interaction of Policies
US8527549B2 (en) * 2010-02-22 2013-09-03 Sookasa Inc. Cloud based operating and virtual file system
US8504517B2 (en) 2010-03-29 2013-08-06 Commvault Systems, Inc. Systems and methods for selective data replication
US8504515B2 (en) 2010-03-30 2013-08-06 Commvault Systems, Inc. Stubbing systems and methods in a data replication environment
US8630980B2 (en) 2010-04-06 2014-01-14 Microsoft Corporation Synchronization framework that restores a node from backup
US8805968B2 (en) * 2010-05-03 2014-08-12 Panzura, Inc. Accessing cached data from a peer cloud controller in a distributed filesystem
US8452726B2 (en) 2010-06-04 2013-05-28 Salesforce.Com, Inc. Sharing information between tenants of a multi-tenant database
US8364652B2 (en) 2010-09-30 2013-01-29 Commvault Systems, Inc. Content aligned block-based deduplication
US20120131684A1 (en) 2010-11-19 2012-05-24 Mark Lynch Automatic backup license to avoid service interruptions in continuous service, high reliability systems
US8954446B2 (en) 2010-12-14 2015-02-10 Comm Vault Systems, Inc. Client-side repository in a networked deduplicated storage system
US9020900B2 (en) 2010-12-14 2015-04-28 Commvault Systems, Inc. Distributed deduplicated storage system
US8554951B2 (en) 2011-03-08 2013-10-08 Rackspace Us, Inc. Synchronization and ordering of multiple accessess in a distributed system
US8850516B1 (en) 2011-06-22 2014-09-30 Emc Corporation Virtual private cloud that provides enterprise grade functionality and compliance
US8793451B2 (en) 2012-03-29 2014-07-29 International Business Machines Corporation Snapshot content metadata for application consistent backups
US9483201B2 (en) 2012-07-31 2016-11-01 Commvault Systems, Inc. Administering a shared, on-line pool of data storage resources for performing data storage operations
US8984582B2 (en) 2012-08-14 2015-03-17 Confidela Ltd. System and method for secure synchronization of data across multiple computing devices
US10664354B2 (en) 2012-08-31 2020-05-26 Hewlett Packard Enterprise Development Lp Selecting a resource to be used in a data backup or restore operation
US9336094B1 (en) 2012-09-13 2016-05-10 Emc International Company Scaleout replication of an application
US20140143201A1 (en) 2012-11-20 2014-05-22 International Business Machines Corporation Dynamic content file synchronization
US9317223B2 (en) 2012-12-17 2016-04-19 International Business Machines Corporation Method and apparatus for automated migration of data among storage centers
US9633216B2 (en) 2012-12-27 2017-04-25 Commvault Systems, Inc. Application of information management policies based on operation with a geographic entity
US20140201140A1 (en) 2013-01-11 2014-07-17 Commvault Systems, Inc. Data synchronization management
US9483489B2 (en) 2013-01-14 2016-11-01 Commvault Systems, Inc. Partial sharing of secondary storage files in a data storage system
US9858052B2 (en) 2013-03-21 2018-01-02 Razer (Asia-Pacific) Pte. Ltd. Decentralized operating system
US9183268B2 (en) 2013-04-11 2015-11-10 Pivotal Software, Inc. Partition level backup and restore of a massively parallel processing database
US9747267B2 (en) 2013-08-12 2017-08-29 Adobe Systems Incorporated Document editing synchronization
US9633051B1 (en) 2013-09-20 2017-04-25 Amazon Technologies, Inc. Backup of partitioned database tables
US9495251B2 (en) 2014-01-24 2016-11-15 Commvault Systems, Inc. Snapshot readiness checking and reporting
US10015252B2 (en) 2014-06-24 2018-07-03 Google Llc Storing content items
US20160004721A1 (en) 2014-07-01 2016-01-07 Commvault Systems, Inc. Replicating local file systems as respective luns in a storage array, using block-level data transfers and enhanced storage managers, data agents, and media agents in an information management system
US20160019317A1 (en) 2014-07-16 2016-01-21 Commvault Systems, Inc. Volume or virtual machine level backup and generating placeholders for virtual machine files
US9436555B2 (en) 2014-09-22 2016-09-06 Commvault Systems, Inc. Efficient live-mount of a backed up virtual machine in a storage management system
US9876849B2 (en) 2014-11-05 2018-01-23 Google Llc Opening local applications from browsers
US9645891B2 (en) 2014-12-04 2017-05-09 Commvault Systems, Inc. Opportunistic execution of secondary copy operations
US9753816B2 (en) 2014-12-05 2017-09-05 Commvault Systems, Inc. Synchronization based on filtered browsing
US9588849B2 (en) 2015-01-20 2017-03-07 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US9952934B2 (en) 2015-01-20 2018-04-24 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US10831715B2 (en) 2015-01-30 2020-11-10 Dropbox, Inc. Selective downloading of shared content items in a constrained synchronization system
CA3128629A1 (en) 2015-06-05 2016-07-28 C3.Ai, Inc. Systems and methods for data processing and enterprise ai applications
US10831398B2 (en) 2016-09-19 2020-11-10 International Business Machines Corporation Storage device efficiency during data replication
US20180285201A1 (en) 2017-03-28 2018-10-04 Commvault Systems, Inc. Backup operations for large databases using live synchronization

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050144195A1 (en) * 1999-12-02 2005-06-30 Lambertus Hesselink Managed peer-to-peer applications, systems and methods for distributed data access and storage
US7421411B2 (en) * 2001-07-06 2008-09-02 Nokia Corporation Digital rights management in a mobile communications environment
US20130238696A1 (en) * 2012-03-08 2013-09-12 Abel Cotelo System and method for presenting synchronized media in a digital content environment
US20140172793A1 (en) * 2012-12-13 2014-06-19 Microsoft Corporation Opportunistic, priority-based object synchronization

Cited By (74)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11321181B2 (en) 2008-06-18 2022-05-03 Commvault Systems, Inc. Data protection scheduling, such as providing a flexible backup window in a data protection system
US11392542B2 (en) 2008-09-05 2022-07-19 Commvault Systems, Inc. Image level copy or restore, such as image level restore without knowledge of data object metadata
US10831778B2 (en) 2012-12-27 2020-11-10 Commvault Systems, Inc. Application of information management policies based on operation with a geographic entity
US11409765B2 (en) 2012-12-27 2022-08-09 Commvault Systems, Inc. Application of information management policies based on operation with a geographic entity
US11288236B2 (en) 2013-01-11 2022-03-29 Commvault Systems, Inc. Data synchronization management
US9262435B2 (en) 2013-01-11 2016-02-16 Commvault Systems, Inc. Location-based data synchronization management
US9336226B2 (en) 2013-01-11 2016-05-10 Commvault Systems, Inc. Criteria-based data synchronization management
US9430491B2 (en) 2013-01-11 2016-08-30 Commvault Systems, Inc. Request-based data synchronization management
US9898481B2 (en) 2013-01-11 2018-02-20 Commvault Systems, Inc. Data synchronization management
US10353871B2 (en) 2013-01-11 2019-07-16 Commvault Systems, Inc. Data synchronization management
US11093336B2 (en) 2013-03-11 2021-08-17 Commvault Systems, Inc. Browsing data stored in a backup format
US20150142742A1 (en) * 2013-11-17 2015-05-21 Zhen-Chao HONG System and method for syncing local directories that enable file access across multiple devices
US10860401B2 (en) 2014-02-27 2020-12-08 Commvault Systems, Inc. Work flow management for an information management system
US11316920B2 (en) 2014-03-05 2022-04-26 Commvault Systems, Inc. Cross-system storage management for transferring data across autonomous information management systems
US9769260B2 (en) * 2014-03-05 2017-09-19 Commvault Systems, Inc. Cross-system storage management for transferring data across autonomous information management systems
US10986181B2 (en) 2014-03-05 2021-04-20 Commvault Systems, Inc. Cross-system storage management for transferring data across autonomous information management systems
US20170134492A1 (en) * 2014-03-05 2017-05-11 Commvault Systems, Inc. Cross-system storage management for transferring data across autonomous information management systems
US10205780B2 (en) 2014-03-05 2019-02-12 Commvault Systems, Inc. Cross-system storage management for transferring data across autonomous information management systems
US10523752B2 (en) 2014-03-05 2019-12-31 Commvault Systems, Inc. Cross-system storage management for transferring data across autonomous information management systems
US11119868B2 (en) 2014-05-09 2021-09-14 Commvault Systems, Inc. Load balancing across multiple data paths
US11593227B2 (en) 2014-05-09 2023-02-28 Commvault Systems, Inc. Load balancing across multiple data paths
US10310950B2 (en) 2014-05-09 2019-06-04 Commvault Systems, Inc. Load balancing across multiple data paths
US10776219B2 (en) 2014-05-09 2020-09-15 Commvault Systems, Inc. Load balancing across multiple data paths
US9823842B2 (en) 2014-05-12 2017-11-21 The Research Foundation For The State University Of New York Gang migration of virtual machines using cluster-wide deduplication
US10156986B2 (en) 2014-05-12 2018-12-18 The Research Foundation For The State University Of New York Gang migration of virtual machines using cluster-wide deduplication
US11416341B2 (en) 2014-08-06 2022-08-16 Commvault Systems, Inc. Systems and methods to reduce application downtime during a restore operation using a pseudo-storage device
US11249858B2 (en) 2014-08-06 2022-02-15 Commvault Systems, Inc. Point-in-time backups of a production application made accessible over fibre channel and/or ISCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host
US9753816B2 (en) 2014-12-05 2017-09-05 Commvault Systems, Inc. Synchronization based on filtered browsing
US9928005B2 (en) 2015-01-20 2018-03-27 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US10817208B2 (en) 2015-01-20 2020-10-27 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US9952934B2 (en) 2015-01-20 2018-04-24 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US10126977B2 (en) 2015-01-20 2018-11-13 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US10713122B2 (en) 2015-01-20 2020-07-14 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US10884634B2 (en) 2015-07-22 2021-01-05 Commvault Systems, Inc. Browse and restore for block-level backups
US11314424B2 (en) 2015-07-22 2022-04-26 Commvault Systems, Inc. Restore for block-level backups
US10168929B2 (en) 2015-07-22 2019-01-01 Commvault Systems, Inc. Browse and restore for block-level backups
US11733877B2 (en) 2015-07-22 2023-08-22 Commvault Systems, Inc. Restore for block-level backups
US9952935B2 (en) * 2016-01-06 2018-04-24 International Business Machines Corporation Excluding content items from a backup operation
US20170192852A1 (en) * 2016-01-06 2017-07-06 International Business Machines Corporation Excluding content items from a backup operation
US11436038B2 (en) 2016-03-09 2022-09-06 Commvault Systems, Inc. Hypervisor-independent block-level live browse for access to backed up virtual machine (VM) data and hypervisor-free file-level recovery (block- level pseudo-mount)
US10691187B2 (en) 2016-05-24 2020-06-23 Commvault Systems, Inc. Persistent reservations for virtual disk using multiple targets
US11340672B2 (en) 2016-05-24 2022-05-24 Commvault Systems, Inc. Persistent reservations for virtual disk using multiple targets
US20180113896A1 (en) * 2016-10-20 2018-04-26 International Business Machines Corporation Synchronizing data across multiple instances of an application in a cloud
US11443026B2 (en) * 2016-10-20 2022-09-13 International Business Machines Corporation Synchronizing data across multiple instances of an application in a cloud
US10838821B2 (en) 2017-02-08 2020-11-17 Commvault Systems, Inc. Migrating content and metadata from a backup system
US11467914B2 (en) 2017-02-08 2022-10-11 Commvault Systems, Inc. Migrating content and metadata from a backup system
US11321195B2 (en) 2017-02-27 2022-05-03 Commvault Systems, Inc. Hypervisor-independent reference copies of virtual machine payload data based on block-level pseudo-mount
US11656784B2 (en) 2017-03-27 2023-05-23 Commvault Systems, Inc. Creating local copies of data stored in cloud-based data repositories
US10891069B2 (en) 2017-03-27 2021-01-12 Commvault Systems, Inc. Creating local copies of data stored in online data repositories
US10776329B2 (en) 2017-03-28 2020-09-15 Commvault Systems, Inc. Migration of a database management system to cloud storage
US11520755B2 (en) 2017-03-28 2022-12-06 Commvault Systems, Inc. Migration of a database management system to cloud storage
US11650885B2 (en) 2017-03-29 2023-05-16 Commvault Systems, Inc. Live browsing of granular mailbox data
US11074140B2 (en) 2017-03-29 2021-07-27 Commvault Systems, Inc. Live browsing of granular mailbox data
US11294768B2 (en) 2017-06-14 2022-04-05 Commvault Systems, Inc. Live browsing of backed up data residing on cloned disks
US11455280B2 (en) 2017-12-07 2022-09-27 Commvault Systems, Inc. Synchronization of metadata in a distributed storage system
US11468015B2 (en) 2017-12-07 2022-10-11 Commvault Systems, Inc. Storage and synchronization of metadata in a distributed storage system
US11500821B2 (en) 2017-12-07 2022-11-15 Commvault Systems, Inc. Synchronizing metadata in a data storage platform comprising multiple computer nodes
US10740300B1 (en) 2017-12-07 2020-08-11 Commvault Systems, Inc. Synchronization of metadata in a distributed storage system
US11567990B2 (en) 2018-02-05 2023-01-31 Commvault Systems, Inc. On-demand metadata extraction of clinical image data
US10795927B2 (en) 2018-02-05 2020-10-06 Commvault Systems, Inc. On-demand metadata extraction of clinical image data
US10789387B2 (en) 2018-03-13 2020-09-29 Commvault Systems, Inc. Graphical representation of an information management system
US11880487B2 (en) 2018-03-13 2024-01-23 Commvault Systems, Inc. Graphical representation of an information management system
US11573866B2 (en) 2018-12-10 2023-02-07 Commvault Systems, Inc. Evaluation and reporting of recovery readiness in a data storage management system
US11829331B2 (en) 2019-06-27 2023-11-28 Commvault Systems, Inc. Continuously run log backup with minimal configuration and resource usage from the source machine
US11308034B2 (en) 2019-06-27 2022-04-19 Commvault Systems, Inc. Continuously run log backup with minimal configuration and resource usage from the source machine
US11816005B2 (en) 2019-08-14 2023-11-14 Commvault Systems, Inc. Systems and methods for change block tracking for backing up changed data
US11513922B2 (en) 2019-08-14 2022-11-29 Commvault Systems, Inc. Systems and methods for change block tracking for backing up changed data
US11218450B2 (en) 2019-09-11 2022-01-04 Commvault Systems, Inc. Data protection component scaling in a cloud-based data storage system
US11792164B2 (en) 2019-09-11 2023-10-17 Commvault Systems, Inc. Data protection component scaling in a cloud-based data storage system
US11789830B2 (en) 2020-09-22 2023-10-17 Commvault Systems, Inc. Anti-entropy-based metadata recovery in a strongly consistent distributed data storage system
US11570243B2 (en) 2020-09-22 2023-01-31 Commvault Systems, Inc. Decommissioning, re-commissioning, and commissioning new metadata nodes in a working distributed data storage system
US11647075B2 (en) 2020-09-22 2023-05-09 Commvault Systems, Inc. Commissioning and decommissioning metadata nodes in a running distributed data storage system
US11314687B2 (en) 2020-09-24 2022-04-26 Commvault Systems, Inc. Container data mover for migrating data between distributed data storage systems integrated with application orchestrators
US11934356B2 (en) 2022-03-30 2024-03-19 Commvault Systems, Inc. Synchronization of metadata in a distributed storage system

Also Published As

Publication number Publication date
US20140201137A1 (en) 2014-07-17
US11288236B2 (en) 2022-03-29
US9336226B2 (en) 2016-05-10
US20140201141A1 (en) 2014-07-17
US20140201144A1 (en) 2014-07-17
US9898481B2 (en) 2018-02-20
US20160246815A1 (en) 2016-08-25
US9262435B2 (en) 2016-02-16
US9430491B2 (en) 2016-08-30
US10353871B2 (en) 2019-07-16
US20180181588A1 (en) 2018-06-28
US20190272253A1 (en) 2019-09-05

Similar Documents

Publication Publication Date Title
US11288236B2 (en) Data synchronization management
US11204710B2 (en) Filtered reference copy of secondary storage data in a data storage system
US20210263657A1 (en) Partial sharing of secondary storage files in a data storage system
US11461016B2 (en) Lightweight mounting of a secondary file system data
US20220164114A1 (en) Systems and methods to confirm replication data accuracy for data backup in data storage systems
US20200341945A1 (en) Systems and methods to identify unprotected virtual machines

Legal Events

Date Code Title Description
AS Assignment

Owner name: COMMVAULT SYSTEMS, INC., NEW JERSEY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VIBHOR, ANAND;MEHTA, BHAVYAN BHARATKUMAR;KARANDIKAR, AMEY VIJAYKUMAR;AND OTHERS;SIGNING DATES FROM 20130911 TO 20130916;REEL/FRAME:031260/0368

AS Assignment

Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, NORTH CAROLINA

Free format text: SECURITY INTEREST;ASSIGNOR:COMMVAULT SYSTEMS, INC.;REEL/FRAME:033266/0678

Effective date: 20140630

Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, NO

Free format text: SECURITY INTEREST;ASSIGNOR:COMMVAULT SYSTEMS, INC.;REEL/FRAME:033266/0678

Effective date: 20140630

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: COMMVAULT SYSTEMS, INC., NEW JERSEY

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:BANK OF AMERICA, N.A.;REEL/FRAME:054913/0905

Effective date: 20180209