Patent Grant
10318542
Increasingly, people generate data and metadata across multiple computing devices and multiple hosted services. For example, during the course of a single day, a person may use a laptop computer, desktop computer, tablet computer, and smartphone in order to view and edit files, e-mails, or other data objects. As another example, a person may use hosted solutions such as Facebook, Gmail, Google Docs, and salesforce.com to communicate with others and conduct work. A person may not be able to access the files and information they need readily from a single interface, since the files are scattered across multiple computing devices and hosted sites. Moreover, conventional information management systems are often focused on organizing, protecting, and recovering the data from fixed computing devices, such as servers or desktop computers. As a result, a person's hosted data and mobile data may be scattered outside of the purview of conventional information management systems and that data will therefore not be backed up or otherwise actively managed. Thus, in the event that a mobile device is lost or broken or a hosted service has a service disruption, there is a risk that a person's critical data may be lost, without any way to recover it.
The need exists for systems and methods that overcome the above problems, as well as systems and methods that provide additional benefits. Overall, the examples herein of some prior or related systems and methods and their associated limitations are intended to be illustrative and not exclusive. Other limitations of existing or prior systems and methods will become apparent to those of skill in the art upon reading the following detailed description.
The headings provided herein are for convenience only and do not necessarily affect the scope or meaning of the disclosure.
Overview
A software, firmware, and/or hardware system for comprehensive information management is disclosed. The system helps collect, manage and distribute, in a unified fashion, data and metadata from numerous sources, including data and metadata originating from hosted services and mobile devices. The system can help a user obtain a unified view of her data across numerous devices and also keep data synchronized across numerous computing devices associated with the user. The system permits users to define simple or complex data distribution policies to help drive data distribution and synchronization across the user's devices. The system allows a user on a mobile device to perform “live browsing” of the files on another computing device that is associated with the user. The system also permits a user of a mobile device or other limited-feature device to execute full-featured applications installed on a remote computing device (e.g., a desktop or laptop device) and to interact with the full-featured application via the input-output hardware of the limited-feature device.
The system offers numerous benefits. First, from a single interface, users can browse and search for files from practically any of their computing devices or hosted services and access those files. Second, the system provides a closed corporate collaboration environment where data objects are exchanged and synchronized across multiple devices, but using the resources of a private information management system, not an untrusted or untried third-party service. As a result, copies of an organization's data objects are not unnecessarily exposed to others because the copies do not need to be stored or controlled by third parties. Third, the system permits an organization to better comply with data retention regulations and other regulations by capturing and managing practically all of a user's data, not just the user's data that originates from fixed computing devices. Fourth, the system can permit an organization to better respond to unexpected data losses, such as the loss of a mobile device or a service outage by a hosted service, because the system is actively managing copies of mobile data and hosted data. Other benefits are of course possible.
Various examples of the invention will now be described. The following description provides specific details for a thorough understanding and enabling description of these examples. One skilled in the relevant art will understand, however, that the invention may be practiced without many of these details. Likewise, one skilled in the relevant art will also understand that the invention may include many other obvious features not described in detail herein. Additionally, some well-known structures or functions may not be shown or described in detail below, so as to avoid unnecessarily obscuring the relevant description.
The terminology used below is to be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain specific examples of the invention. Indeed, certain terms may even be emphasized below; however, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section.
Information Management Environment
Aspects of the technologies described herein may be practiced in an information management environment 100, which will now be described while referencing
The environment 100 may include virtualized computing resources, such as a virtual machine 120 provided to the organization by a third-party cloud service vendor or a virtual machine 125 running on a virtual machine host 130 operated by the organization. For example, the organization may use one virtual machine 125A as a database server and another virtual machine 125B as a mail server. The environment 100 may also include mobile or portable computing devices, such as laptops 135, tablet computers 140, personal data assistants 145, mobile phones 152 (such as smartphones), and other mobile or portable computing devices such as embedded computers, set top boxes, vehicle-mounted devices, wearable computers, etc.
Of course, other types of computing devices may form part of the environment 100. As part of their function, each of these computing devices creates, accesses, modifies, writes, and otherwise uses production copies of data and metadata that are typically stored in a persistent storage medium having fast I/O times. For example, each computing device may regularly access and modify data files and metadata stored on semiconductor memory, a local disk drive or a network-attached storage device. Each of these computing devices may access data and metadata via a file system supported by an operating system of the computing device.
The environment 100 may also include hosted services 122 that provide various online services to the organization or its constituent members (e.g., the organization's departments, employees, independent contractors, etc.) such as social networking services (e.g., Facebook, Twitter, Pinterest), hosted email services (e.g., Gmail, Yahoo Mail, Hotmail), or hosted productivity applications or other hosted applications (e.g., Microsoft Office 365, Google Docs, Salesforce.com). Hosted services may include software-as-a-service (SaaS), platform-as-a-service (PaaS), application service providers (ASPs), cloud services, and all manner of delivering computing or functionality via a network. As it provides services to users, each hosted service may generate additional “hosted data and metadata” that is associated with each user. For example, Facebook may generate and store photos, wall posts, notes, videos, and other content that are associated with a particular Facebook user's account.
The organization directly or indirectly employs an information management system 150 to protect and manage the data and metadata used by the various computing devices in the environment 100 and the data and metadata that is maintained by hosted services on behalf of users associated with the organization. One example of an information management system is the CommVault Simpana system, available from CommVault Systems, Inc. of Oceanport, N.J. The information management system creates and manages non-production copies of the data and metadata to meet information management goals, such as: permitting the organization to restore data, metadata or both data and metadata if an original copy of the data/metadata is lost (e.g., by deletion, corruption, or disaster, or because of a service interruption by a hosted service); allowing data to be recovered from a previous time; complying with regulatory data retention and electronic discovery (“e-discovery”) requirements; reducing the amount of data storage media used; facilitating data organization and search; improving user access to data files across multiple computing devices and/or hosted services; and implementing information lifecycle management (“ILM”) or other data retention policies for the organization. The information management system 150 may create the additional non-production copies of the data and metadata on any suitable non-production storage medium such as magnetic disks 155, magnetic tapes 160, other storage media 165 such as solid-state storage devices or optical disks, or on cloud data storage sites 170 (e.g. those operated by third-party vendors). Further details on the information management system may be found in the assignee's U.S. patent application Ser. No. 12/751,850, filed Mar. 31, 2010 entitled DATA OBJECT STORE AND SERVER FOR A CLOUD STORAGE ENVIRONMENT, INCLUDING DATA DEDUPLICATION AND DATA MANAGEMENT ACROSS MULTIPLE CLOUD STORAGE SITES, now U.S. Patent Publication Number 2010-0332456, which is hereby incorporated by reference herein in its entirety.
The information management system 150 accesses or receives copies of the various production copies of data objects and metadata, and via an information management operation (such as a backup operation, archive operation, or snapshot operation), creates non-production copies of these data objects and metadata, often stored in one or more non-production storage mediums 265 different than the production storage medium 218 where the production copies of the data objects and metadata reside. A non-production copy of a data object represents the production data object and its associated metadata at a particular point in time (non-production objects 260A-C). Since a production copy of a data object or metadata changes over time as it is modified by an application 215, hosted service 122, or the operating system 210, the information management system 150 may create and manage multiple non-production copies of a particular data object or metadata, each representing the state of the production data object or metadata at a particular point in time. Moreover, since a production copy of a data object may eventually be deleted from the production data storage medium and the file system from which it originated, the information management system may continue to manage point-in-time representations of that data object, even though a production copy of the data object itself no longer exists.
For virtualized computing devices, such as virtual machines, the operating system 210 and applications 215A-D may be running on top of virtualization software, and the production data storage medium 218 may be a virtual disk created on a physical medium such as a physical disk. The information management system may create non-production copies of the discrete data objects stored in a virtual disk file (e.g., documents, email mailboxes, and spreadsheets) and/or non-production copies of the entire virtual disk file itself (e.g., a non-production copy of an entire .vmdk file).
Each non-production object 260A-C may contain copies of or otherwise represent more than one production data object. For example, non-production object 260A represents three separate production data objects 255C, 230 and 245C (represented as 245C′, 230′ and 245′, respectively). Moreover, as indicated by the prime mark (′), a non-production object may store a representation of a production data object or metadata differently than the original format of the data object or metadata, e.g., in a compressed, encrypted, deduplicated, or otherwise optimized format. Although
Non-production copies include backup copies, archive copies, and snapshot copies. Backup copies are generally used for shorter-term data protection and restoration purposes and may be in a native application format or in a non-native format (e.g., compressed, encrypted, deduplicated, and/or otherwise modified from the original application format). Archive copies are generally used for long-term data storage purposes and may be compressed, encrypted, deduplicated and/or otherwise modified from the original application format. In some examples, when an archive copy of a data object is made, a logical reference or stub may be used to replace the production copy of the data object in the production storage medium 218. In such examples, the stub may point to or otherwise reference the archive copy of the data object stored in the non-production storage medium so that the information management system can retrieve the archive copy if needed. The stub may also include some metadata associated with the data object, 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. A snapshot copy represents a data object at a particular point in time. A snapshot copy can be made quickly and without significantly impacting production computing resources because large amounts of data need not be copied or moved. A snapshot copy may include a set of pointers derived from the file system or an application, where 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 at a particular point in time when the snapshot copy was created. In “copy-on-write”, if a block of data is to be deleted or changed, the snapshot process writes the block to a particular data storage location, and the pointer for that block is now directed to that particular location. The set of pointers and/or the set of blocks pointed to by a snapshot may be stored within the production data storage medium 218.
Non-production copies of a data object or metadata may be distinguished from a production copy of a data object or metadata in several ways. First, a non-production copy of a data object is created to meet the different information management goals described above and is not directly used or modified by applications 215A-D, hosted services 122, or the operating system 210. Second, a non-production copy of a data object is stored as one or more non-production objects 260 that may have a format different from the native application format of the production copy of the data object, and thus often cannot be directly used by the native application or a hosted service 122 without first being modified. Third, non-production objects are often stored on a non-production storage medium 265 that is inaccessible to the applications 215A-D running on computing devices and hosted services 122. Also, some non-production copies may be “offline copies,” in that they are not readily available (e.g. not mounted tape or disk.) Offline copies include copies of data that the information management system can access without any human intervention (e.g. tapes within an automated tape library, but not yet mounted in a drive), and copies that the information management system 150 can access only with at least some human intervention (e.g. tapes located at an offsite storage site).
The information management system 150 also generates information management data 275, such as indexing information, that permit the information management system to perform its various information management tasks. As shown in
Information Management System
Information Management Cell
The storage manager 402 may be a software module or other application that coordinates and controls information management operations performed by one or more information management cells 350 to protect and control copies of non-production data objects and metadata. As shown by the dashed lines 416 and 422, the storage manager may communicate with some or all elements of the information management cell 350, such as the media agents 410 and computing devices 205, to initiate and manage backup operations, snapshot operations, archive operations, data replication operations, data migrations, data distributions, data recovery, and other information management operations. The storage manager may control additional information management operations including ILM, deduplication, content indexing, data classification, data mining or searching, e-discovery management, collaborative searching, encryption, and compression. Alternatively or additionally, a storage manager may control the creation and management of disaster recovery copies, which are often created as secondary, high-availability disk copies, using auxiliary copy or replication technologies.
The storage manager 402 may include a jobs agent 455, a management agent 450, a network agent 445, and an interface agent 460, all of which may be implemented as interconnected software modules or application programs. The jobs agent 455 monitors the status of information management operations previously performed, currently being performed, or scheduled to be performed by the information management cell 350. The management agent 450 provides an interface that allows various management agents 450 in multiple information management cells 350 (or in a global storage manager 305) to communicate with one another. This allows each information management cell 350 to exchange status information, routing information, capacity and utilization information, and information management operation instructions or policies with other cells. In general, the network agent 445 provides the storage manager 402 with the ability to communicate with other components within the information management cell and the larger information management system, e.g., via proprietary or non-proprietary network protocols and application programming interfaces (“APIs”) (including HTTP, HTTPS, FTP, REST, virtualization software APIs, cloud service provider APIs, hosted service provider APIs). The interface agent 460 includes information processing and display software, such as a graphical user interface (“GUI”), an API, or other interactive interface through which users and system processes can retrieve information about the status of information management operations or issue instructions to the information management cell and its constituent components. The storage manager 402 may also track information that permits it to select, designate, or otherwise identify content indices, deduplication databases, or similar databases within its information management cell (or another cell) to be searched in response to certain queries.
The storage manager 402 may also maintain information management data, such as a database 465 of management data and policies. The database 465 may include a management index that stores logical associations between components of the system, user preferences, user profiles (that among other things, map particular information management users to computing devices or hosted services), management tasks, or other useful data. The database 465 may also include various “information management policies,” which are generally data structures or other information sources that each includes a set of criteria and rules associated with performing an information management operation. The criteria may be used to determine which rules apply to a particular data object, system component, or information management operation, an may include:
As noted above, each computing device 205 may include one or more data management agents 280. Each data management agent is a software module or component that helps govern communications with other system components. For example, the data management agent receives commands from the storage manager 402 and sends to and receives from media agents 410 copies of data objects, metadata, and other payload (as indicated by the heavy arrows). Each data management agent accesses data and/or metadata stored in a production data storage medium 218 and arranges or packs the data and metadata in a certain format (e.g., backup or archive format) before it is transferred to another component. Each data management agent can also restore a production copy of a data object or metadata in a production data storage medium 218 from a non-production copy. A data management agent may perform some functions provided by a media agent, which are described further herein, such as compression, encryption, or deduplication. Each data management agent may be specialized for a particular application (e.g. a specified data management agent customized to handle data generated or used by Exchange by Microsoft Corp.). Alternatively or additionally, a more generic data management agent may handle data generated or used by two or more applications.
Each computing device 205 may also include a data distribution and live browsing client module 405 (herein “distribution client module”). The distribution client module 405 is responsible for, inter alia, associating mobile devices and/or hosted service accounts with users of the information management system, setting information management policies for mobile and other computing devices, pushing data objects to a distribution module for distribution to other computing devices, providing unified access to a user's data via an interface, and providing live browsing features. The various functions of the distribution client module are described in greater detail herein.
A media agent 410, which may be implemented as a software module, conveys data, as directed by the storage manager 402, between a computing device 205 (or hosted service 122) and one or more non-production storage mediums 155-870. Each media agent 410 may control one or more intermediary storage devices 418, such as a cloud server or a tape or magnetic disk library management system, to read, write, or otherwise manipulate data stored in a non-production storage medium 155-870. Each media agent 410 may be considered to be “associated with” a storage device and its related non-production storage media if that media agent is capable of routing data to and storing data in the storage media managed by the particular storage device. A media agent may communicate with computing devices 205, hosted services 122, storage devices 418A-D, and the storage manager 402 via any suitable communications path, including SCSI, a Storage Area Network (“SAN”), a Fibre Channel communications link, or a wired, wireless, or partially wired/wireless computer or telecommunications network, including the Internet.
To perform its functions, the media agent 410 may include a media file system module 425, a data classification module 435, a content indexing module 420, a deduplication module 430, an encryption module 475, a compression module 485, a network module 415, a distribution module 490, and a media agent database 440. The media file system module 425 is responsible for reading, writing, archiving, copying, migrating, restoring, accessing, moving, sparsifying, deleting, sanitizing, destroying, or otherwise performing file system operations on various non-production storage devices of disparate types. The media file system module may also instruct the storage device to use a robotic arm or other retrieval means to load or eject certain storage media such as a tape.
The network module 415 permits the media agent to communicate with other components within the system and hosted services 122 via one or more proprietary and/or non-proprietary network protocols or APIs (including cloud service provider APIs, virtual machine management APIs, and hosted service provider APIs). The deduplication module 430 performs deduplication of data objects and/or data blocks to reduce data redundancy in the cell. The deduplication module may generate and store data structures to manage deduplicated data objects, such as deduplication tables, in the media agent database 440. The encryption module 475 performs encryption of data objects, data blocks, or non-production objects to ensure data security in the cell. The compression module 485 performs compression of data objects, data blocks, or non-production objects to reduce the data capacity needed in the cell.
The content indexing module 420 analyzes the contents of production copies or non-production copies of data objects and/or their associated metadata and catalogues the results of this analysis, along with the storage locations of (or references to) the production or non-production copies, in a content index stored within a media agent database 440. The results may also be stored elsewhere in the system, e.g., in the storage manager 402, along with a non-production copy of the data objects, and/or an index cache. Such index data provides the media agent 410 or another device with an efficient mechanism for locating production copies and/or non-production copies of data objects that match particular criteria. The index data or other analyses of data objects or metadata may also be used by the data classification module 435 to associate data objects with classification identifiers (such as classification tags) in the media agent database 440 (or other indices) to facilitate information management policies and searches of stored data objects.
The distribution module 490 may be a set of instructions that coordinates the distribution of data objects and indices of data objects. The distribution may occur from one computing device 205 to another computing device 205 and/or from hosted services 122 to computing devices 205. As a first example, the distribution module may collect and manage data and metadata from hosted services 122 or mobile devices 205. As another example, the distribution module may synchronize data files or other data objects that are modified on one computing device so that the same modified files or objects are available on another computing device. As yet another example, the distribution module may distribute indices of data objects that originated from multiple computing devices and/or hosted services, so a user can access all of their data objects through a unified user interface or a native application on their computing device. The distribution module may also initiate “live browse” sessions to permit communications between different computing devices so that the devices can interchange data and metadata or so the devices can provide computing resources, such as applications, to each other. The functions performed by the distribution module are described in greater detail herein.
Manacling Hosted Data
To provide comprehensive management of all of an organization's data, the information management system 150 (or IMS) may collect and manage hosted data associated with individual users of the IMS, such as individual employees or members of the organization that operate or utilize the IMS.
The interface 600 also includes several selection boxes 605 or similar elements to permit the user to identify the hosted accounts the user has. For illustrative purposes, the interface 600 shows only the hosted services Facebook, Flickr, LinkedIn, Twitter, Gmail, Dropbox, and Box.net. However, as indicated by the services selection field 630, the information management system may also support numerous other hosted services, including practically any hosted service that generates production data and metadata for a user and provides APIs or other interfaces that permit the distribution module to access the user's data and metadata. For each selected service, the interface 600 provides username and password fields, 610 and 615, where the user can enter hosted account authentication information or credentials to permit the IMS to access the user's data and metadata hosted on the service.
For each selected service, the interface also includes a policy selection dropdown menu 620 or similar selection means so that the user can associate the selected service with a particular information management policy for collecting and managing the service's hosted data and metadata. A policy may include any of the criteria and rules described above in connection with the discussion of information management policies generally. The selected policy may specify how frequently the distribution module should collect hosted data from the service, the type or other characteristics of hosted data that the distribution module should collect (e.g., all data versus photos versus documents, etc.), and/or the types of information management operations that the IMS should perform on collected hosted data (e.g., deduplication, content indexing, data classification, archiving, back up operations, etc.). The selected policy may also specify where or how non-production copies of the hosted data should be stored. The interface can include options for all of these criteria and rules, as well as other criteria and rules.
As shown with element 620a, to simplify the user experience, the interface 600 may provide a suggested default or mandatory policy (e.g., “FB default” policy) for each service (e.g., all data content is collected twice a day). For each selected service, the interface 600 may also include an alias field 635 where a user can provide a descriptive alias for the hosted account, to permit the user and the IMS to readily identify the hosted account as a data source for the user.
The interface 600 may be presented to a user via a web browser (e.g., as a web portal), or may be presented to a user via a mobile application or other application installed on the user's computing device, such as a mobile device. For example, the interface 600 may be provided by the same application used to produce the interface 770, which is described further herein. In examples where the interface 600 is presented via a mobile application, some or all of the entry fields may be auto-populated by the application. For example, the application producing interface 600 may detect other applications installed on the mobile device that are associated with hosted services or local data related to these other applications. For example, the application used to produce interface 600 may detect that a user's mobile device has a Facebook application installed and may therefore automatically select “Facebook.”
Although not shown in
Returning to the process 500 of
At block 515, the distribution module 490 sets or adjusts information management policies to govern the collection and management of the hosted data associated with the user. For example, in accordance with the user's policy preferences that were received at block 505 (and any administrator-defined policies), for each hosted service selected, the distribution module may set a policy specifying which of the user's hosted data should be collected from the service and the schedule for collecting the hosted data. Continuing the previous example, the distribution module may set a policy to collect all of the user jane65's data and metadata from her “Facebook Jane” account twice a day.
At block 520, the distribution module 490 collects hosted data and metadata in accordance with the applicable information management policies that were set at block 515. To do so, the distribution module may utilize general or service-specific APIs to request any new data or metadata associated with a user's hosted account on the prescribed schedule. As part of its request, the distribution module may provide the authentication or credential information (e.g., username/password or other credentials) that it received at block 505 in order to gain access to the user's hosted data and metadata.
The process 500 ends at block 525, where the distribution module 490 manages collected hosted data in accordance with applicable information management policies. For example, the distribution module may perform deduplication, content indexing, data classification, and/or archiving; create additional non-production copies (e.g., backup copies or archive copies); restore copies of the data and metadata to a production location; or perform information lifecycle management of the hosted data in accordance with the applicable information management policies set at block 515.
In some examples, the distribution module may restore or expose hosted data at a new location that is different from its original hosted location so that an organization can interact with the data in a different fashion. For example, the distribution module may restore IMAP data that was generated by a first hosted email service (e.g., Gmail) so that it is accessible via a second hosted email service (e.g., Hotmail) or a local email client (e.g., Outlook). As another example, the distribution module may restore hosted data to an organization's network attached storage filer. In such an example, data that was previously accessible only via a service-specific API of a hosted service would now be accessible to the organization via Network File System or Common Internet File System protocols.
Managing Mobile Device Data
To provide comprehensive management of all of an organization's data, the information management system 150 may also collect and manage data and metadata generated by the mobile devices owned or used by individual users of the IMS, such as individual employees or members of the organization that operates or utilizes the IMS. For example, the IMS may collect and manage all employees' data and metadata generated from smartphones, tablet computers, laptops and/or other mobile devices (which may be referred to herein simply as “mobile data”).
The process 700 begins at block 705, where the distribution client module 405 receives IMS authentication information and management policies for the mobile data from a mobile device.
The interface 770 includes several selection boxes 776 or similar elements to permit the user to identify what types of mobile data from the mobile device the user wants the IMS to collect and manage. For illustrative purposes, the interface 770 shows only the data types of pictures, documents, emails, applications and application data. However, as indicated by the selection field 776e, the information management system may also support the collection and management of numerous other types of mobile data. Moreover, in some examples, the interface 770 permits a user to define more granular criteria for the mobile data that should be collected and managed by the IMS. For example, the interface 770 might permit a user to define which particular applications and application data are collected and managed and/or might permit the user to define other selection criteria (such as file size, file extension, or particular source directory folders on a mobile device).
The interface 770 also includes policy selection menus 778 or similar selection means so that the user can associate each selected data type (or all data types) with a particular information management policy for collecting, managing or distributing the selected type of data. A selected policy may include any of the criteria and rules described above in connection with the discussion of information management policies generally. A selected policy may specify the frequency with which the distribution client module collects data from the mobile device, the type of network connectivity that can or cannot be used for data collection or distribution (e.g., a WiFi connection or a domestic cellular network), a specific “blacklist” of network access points or IP addresses that cannot be used for data collection or distribution, a specific “whitelist” of network access points or IP addresses that may be used for data collection or distribution, and operating conditions such as battery life that must be satisfied during data collection or distribution. The policy may also specify that certain data objects cannot be opened on the mobile device unless the mobile device is within a certain IP address range or connected via a specific network. The policy may specify particular directories on the mobile device file system for which data should be collected and managed. The policy selected may also specify the types of information management operations that should be performed on the mobile data after it is collected (e.g., deduplication, content indexing, data classification, archiving, etc.). The selected policy may also specify where or how non-production copies of the mobile data should be stored. As shown with element 778a, to simplify the user experience, the interface 770 may provide a suggested default or mandatory policy (e.g., a Default policy where data is collected once a day, and only when the mobile device has a WiFi connection). To illustrate the use of the interface 770, in the example shown in
Although not shown in
Returning to
At block 715, the distribution client module 405 sets or adjusts information management policies to govern the collection and management of the mobile data from the mobile device. For example, in accordance with the user's policy preferences that were received at block 705, for each data type selected, the distribution client module may set a policy specifying the schedule and other rules for sending mobile data to an information management system. Continuing the previous example, the distribution client module may set a policy to collect all of jane65's pictures, documents, applications and application data from the tablet named “Janes tablet” once a day when a WiFi connection is available. The distribution client module may also send the policies to other components, such as a storage manager 402 or the distribution module 490.
Next, at block 720, the distribution client module 405 sends mobile data from the mobile device to an IMS in accordance with the applicable information management policies. The mobile data may be sent opportunistically, e.g., when a high-speed or low cost network connection such as WiFi is available. The distribution client module may instruct data management agents installed 280 on the mobile device to send data both in (1) an initial operation so the IMS can collect existing data objects from the mobile device and (2) in subsequent scheduled operations so the IMS can collect new or modified data objects from the mobile device. Returning to the previous example, after the user preferences have been received at block 705, if a WiFi connection is available, the distribution client module may initially instruct various installed data management agents 280 to package up and send any of jane65's existing pictures, documents, applications and application data from the tablet named “Janes tablet” to a distribution module 490. From thereon, once a day, when a WiFi connection is available on the Janes Tablet device, the distribution client module may instruct various installed data management agents 280 to package up and send any changes to jane65's pictures, documents, applications and application data to the distribution module 490. After block 720 the process 700 ends.
Although the process 700 was described as being performed by a distribution client module 405 on the mobile device whose data is being sent, some or all of the process 700 may be performed by another computing device that acts as an intermediary. For example, a mobile device may tether (physically or wireless) to a laptop or desktop computer and a distribution client module on the laptop or desktop computer may perform some of the steps in the process 700.
Distributing User's Data
In addition to collecting and managing a user's data from hosted services and/or mobile devices, the information management system 150 may also distribute a user's data and/or indices of a user's data so that the user can obtain a unified view of all of her data, across different hosted services and different computing devices and access all of this data readily. For example, the information management system may permit a user to view all of her mobile data, hosted data, and other data in a manner similar to that shown in
Before data is distributed, the distribution module 490 may perform various management tasks to facilitate subsequent distribution.
As one example, as shown, the interface 930 may permit a user to specify a source location, a file type, and a modification date in order to define the set of data objects that should be distributed under the policy. A source location may be defined by an alias for a hosted account, an alias or hostname for a computing device (including mobile devices), and/or a directory path within a hosted account or computing device. Of course, other types of criteria may be used to define the set of data objects that should be distributed, including, without limitation file size, access control information, data classification tags, content information (e.g., keywords), and modification or creation dates.
The interface 930 also includes input fields 944, 946, and other types of menus 948 that permit a user to select one or more destination locations to where the defined set of data objects should be distributed. The destination locations may include specific computing devices, a class of computing devices (e.g., all computing devices associated with a particular user, all computing devices having certain characteristics such as having more than a threshold capacity of disk space or a particular application installed), and/or a directory within a specific computing device or within a class of computing devices. By permitting a user to define a destination directory, a user can merge data from multiple sources into a specific folder on a destination device. In some examples, a user can omit a source directory path and destination directory path from the criteria, so that all data from a source device (e.g., a smartphone) is synchronized with all of the data at a destination device (e.g., a tablet).
Although not shown, a distribution policy may also specify whether a preview version or a copy of a version of an implicated data object should be automatically pushed by the distribution module to the destination location, even if it doesn't receive an explicit request for it from a destination computing device. The policy may also specify triggers for pushing unsolicited previews or copies. For example, a distribution policy may specify that a preview version or copy of an implicated data object should be pushed immediately when the preview or copy becomes available (or at the first opportunity thereafter) so that the destination device has a cached version available.
A synchronization policy field 950 permits a user to select or define whether and how data should be synchronized across the source and destination computing devices and may include pre-defined synchronization policies and/or a menu option to build a custom synchronization policy. One example of a synchronization policy is a one-way synchronization policy (“push only”), where only changes made to a data object at a source location are pushed or propagated to a destination location but changes made at a destination location are not propagated back to the source location. Another example is full two-way synchronization, where all changes made to a data object at any location (any source or destination location) are pushed or propagated to all other locations where a copy of the data object is located. A synchronization policy may further specify how frequently to distribute or receive changes to a data object (or other conditions for distributing or receiving data changes). A synchronization policy may also specify whether to lock access to a data object at locations where it is distributed if a copy of the object is being edited at another location. In this way, a synchronization policy may ensure that only one copy of a data object is unlocked for editing at any given time, so that only one computing device can edit the data object. Alternatively, a synchronization policy may specify methods for resolving concurrent editing of the same data object by more than one computing device. Although not shown, the interface 930 may permit a user to define other characteristics of a distribution policy, such as conditions precedent for collecting changes to a data object, receiving changes to a data object, opening a data object or preview, or editing a data object. Examples of these conditions include the type of network connectivity that can or cannot be used for data collection or distribution (e.g., a WiFi connection or a domestic cellular network), a specific “blacklist” of network access points that cannot be used for data collection or distribution, a specific “whitelist” of network access points that may be used for data collection or distribution, and operating conditions such as battery life that must be satisfied during data collection or distribution. The policy may also specify that certain data objects or preview cannot be opened on a computing device unless the computing device is within a certain IP address range or connected via a specific network. Other polices are of course possible, including combinations of those disclosed herein.
It should be noted that the information management system 150 permits a single user to define different distribution policies for their different computing devices, which gives the users more flexibility to customize their experience on each device. As just one example, a user may specify that their photos are synchronized to all their devices but their videos are only synchronized across devices that have sufficient data storage space to accommodate numerous videos. This is in contrast to some conventional techniques for data synchronization, which do not permit different synchronization policies for different devices.
Also, although not shown in
Returning to the discussion of
At block 810, the distribution module 490 receives a user's data objects and metadata, e.g., by receiving data objects and metadata from computing devices 205 or hosted services 122. The distribution module may receive entirely new data objects implicated by a distribution policy or new versions of data objects that were already subject to a distribution policy. For example, in accordance with an applicable distribution policy created and implemented at block 805 (or in accordance with other information management policies, such as backup policies), the distribution module may receive data from a user's computing device 205. Alternatively, or additionally, the distribution module 490 may receive hosted data that is implicated by a distribution policy by pulling the data from a hosted service in accordance with information management policies, as described previously at block 520.
At block 810, the distribution module 490 may receive a new version of a data object, e.g., either by receiving a copy of the changed data object itself or by receiving a copy of any blocks that have changed since the last version of the data object was received by the distribution module. Additionally, at block 810, instead of receiving a copy of a particular data object or a constituent block of a data object, the distribution module may receive a hash or other substantially unique identifier for the data object or a constituent block, if source-side deduplication techniques are implemented, e.g., as described in assignee's U.S. patent application Ser. No. 12/982,087, filed Dec. 30, 2010, entitled Systems and Methods for Retaining and Using Data Block Signatures in Data Protection Operations, which is hereby incorporated by reference herein in its entirety, and commonly-assigned U.S. patent application Ser. No. 12/751,850, which was introduced and incorporated by reference above. In conjunction with receiving data at block 810, the distribution module may also receive metadata associated with the data object, such as a file name, file or data object type, source directory, access control information, creation time, file or object size, and modification time.
At block 815, the distribution module 490 analyzes and indexes the data and metadata received at block 810. For example, for each data object received, the distribution module may perform content indexing and data classification analyses of the data object, as described further in the assignee's U.S. Pat. Nos. 7,822,749 and 7,882,077, both of which are hereby incorporated herein by reference. The distribution module may store the results of the analyses and other information related to the data object in an object log index 1000, such as that shown in
Returning to the process 800 of
At block 825, the distribution module 490 determines where to distribute copies of the received data objects, index information related to the received data objects, and/or preview versions of the received data objects. For example, the distribution module may analyze the distribution policies received at block 805 and any other applicable information management policies to determine that it should distribute a received data object, its related index information, and/or a preview version of the object to a particular destination location, such as a particular destination computing device. In some examples, the distribution module 490 records the result of its determinations in a distribution index 1100, such as that shown in
The distribution index 1100 may also include one or more columns to track whether and when a data object, a related preview, or related index information about a data object has been distributed to a particular destination. For example, an index sent column 1110 indicates when a particular destination device (or portal) receives index information about the version of the data object, as described further herein. As another example, a preview sent timestamp column 1112 indicates when a particular destination device or portal receives a preview version of a data object. As yet another example, a copy sent column 1114 indicates when a particular destination device or portal receives a copy of a particular version of the data object. A copy locked column 1116 indicates whether a particular computing device or portal is actively editing an object and thus, under the applicable synchronization policy, other computing devices or portals should be blocked from simultaneously editing the object.
Of course, different types of index data structures could provide similar functionalities to those described in connection with the object log index 1000 and distribution index 1100. Additionally, in accordance with applicable storage policies, the distribution module may intermittently or on a prescribed schedule prune the indices 1000 and 1100 to remove all references to versions of data objects that meet predefined criteria (e.g., older versions that haven't been accessed during a prescribed period). Additionally, the distribution module may delete stored non-production copies and/or preview versions of these pruned data objects.
Returning to
A distribution client module 405 may perform actions that are complementary to the process 800 performed by a distribution module 940.
At block 860, the distribution client module 405 detects changes to a user's data objects that are implicated by a distribution policy, i.e., objects that match the criteria specified by a distribution policy. As a first example, the distribution module may determine that a user has created a new file implicated by a distribution policy. As a second example, the distribution module may determine that a user has opened and edited a file on a source device, and the file is implicated by a distribution policy that specifies one-way or two-way synchronization across devices. As a third example, the distribution client module may determine that a user has opened and edited a file at a source or destination location, and the file is implicated by a distribution policy that specifies two-way synchronization across devices.
At block 865, the distribution client module 405 sends a copy of the implicated data objects to the distribution module 490 in accordance with the distribution policies (i.e., resulting in block 810 of process 800). The timing of block 865 may be mandated by settings of the distribution policy and may be opportunistic (e.g., when a low-cost or high-speed network connection is available to the distribution client module). For example, the distribution policy may specify particular conditions for sending the data objects such as requiring that the device sending the copy is on a corporate network or corporate VPN, has WiFi or another type of network access, has a minimum level of battery power left, etc. After block 865, the process 800 ends. The data objects may be sent using continuous data replication techniques such those techniques described in assignee's U.S. patent application Ser. No. 12/167,933, entitled “Continuous Data Protection Over Intermittent Connections, Such as Continuous Data Backup For Laptops or Wireless Devices,” filed Jul. 3, 2008, now U.S. Patent Publication Number 2010-0005259 and/or source-side deduplication techniques such those techniques described in commonly-assigned U.S. patent application Ser. No. 12/982,087 (introduced earlier above) and assignee's U.S. patent application Ser. No. 12/751,850 (introduced and incorporated by reference earlier above), all of which are hereby incorporated by reference herein in their entirety.
Unified Views of a User's Data
As introduced above, the information management system 150 may distribute a user's data and/or indices of a user's data so that the user can obtain a unified view of all of her data that has been created and modified across different hosted services and different computing devices. The information management system permits the user to obtain this unified view and access her data on different computing devices or via a web portal.
The interface 1300 may also provide the user with multiple ways to access their data objects. For example, if a user selects an icon associated with a data object (e.g., icon 1305), the user may be presented with a menu 1310 of options, such as the options of
Additionally, the menu may include an option to perform a “live browse” of the local files of another computing device (e.g., of the device with alias “Janes Laptop”), as described further herein. For example, if a user doesn't see a file they wanted under the “Janes Laptop” branch because it wasn't subject to a distribution policy, they may use the “live browse” option to try and locate it on the other device. Alternatively, or additionally, in some examples when a user double-clicks a particular data object icon 1305 (or otherwise indicates they wish to “open” the data object), the interface may respond by taking one of these actions by default. The default action taken may be dictated by the capabilities of the computing device presenting the interface 1300, such as its installed applications, processing power, and memory. For example, on a mobile device, the default action may be opening a preview version using a limited-feature viewer application.
In addition to providing a navigable directory structure, the interface 1300 may provide search menus or fields 1315 to permit the user to enter search criteria and receive a list of search results (or a filtered directory structure) that includes the data objects that match the criteria. For example, if a user enters criteria into the search field 1315, the client distribution module may search received content indexing information, data classification tags, and/or metadata to find and present matching data objects. In this way, the user may be able to search across the content, tags, and metadata of data objects that originated from numerous hosted services and/or numerous computing devices.
Also, the interface 1300 may provide “drag-and-drop” features. For example, the interface may permit a user to indicate that they want to receive a local copy or preview version of an object, simply by dragging an icon into a local directory folder. As another example, the interface may permit a user to indicate that they want to push a copy or preview version of an object to another computing device (thereby effectively creating a new distribution policy), simply by dragging an icon for a data object into the displayed navigable folder structure. In other words, the user can use the drag-and-drop feature to create a distribution policy to indicate data from one folder or device is to be copied to another location, without having to determine and enter path names or other information.
The interface 1300 shown is intended to be illustrative, not exhaustive. The user may obtain a unified view of their data, such as a view of interface 1300, in numerous ways. As one example, a user may provide the user's IMS authentication credentials (e.g., IMS username and password or other IMS authentication information) to a dedicated data navigation application, such as a downloaded mobile application that comprises a distribution client module 804. Or the application may obtain credentials from an operating system or directory or security service, such as an Active Directory service. As another example, a user may provide the user's IMS authentication credentials (e.g., IMS username and password or other IMS authentication information) to a web portal associated with the IMS in order to view and access her data through a personalized web interface similar to interface 1300. As another example, a native application installed on a user's computing device may provide a unified view of the her data. Examples of native applications that may be used include Windows Explorer or similar file system navigators (including NFS/CIFS clients) provided by an operating system and email clients such as Outlook (or IMAP clients).
In such examples, a distribution client module 405 may be implemented as a plug-in to the native application so that data objects originating from hosted services or other computing devices are presented to the user within the native application's interface in a manner similar to other locally-stored files or data objects, such as locally-stored files and locally-stored emails. For example, if a user has created a distribution policy that implements cross-device synchronization, synchronized data objects might simply appear within Windows Explorer or a similar application at a directory location (e.g., /a/different/path) on the destination device specified by the distribution policy. As another example, a user may have a folder on their desktop called “Remote Data,” that provides access to an interface similar to 1300. As yet another example, Outlook may request and cache indexing information, previews and/or copies of synchronized data so that it can provide an interface such as that shown in
Prior to the process 1200, the installed distribution client module may receive or obtain IMS credentials or other information identifying the IMS user or users whose data is to be presented as noted herein. Steps in process 1200 may be performed opportunistically, e.g., when a low-cost or high-speed network connection is available to the distribution client module on the computing device.
The process 1200 begins at block 1205, where the distribution client module 405 requests and receives index information related to the user's data, such as information from the object log index 1000 and distribution index 1100 that is specific to the user and the device or portal from which the user is accessing the data. Typically the request is made to and fulfilled by the distribution module 490. To illustrate, the distribution client module may request index information related to data objects that have been slated for distribution to the particular computing device and are associated with the user, e.g., as indicated by the destination column 1104 and the user ID column 1102 of the distribution log 1100. The distribution client module will typically request and receive sufficient information to permit the distribution client module to display an organized graphical depiction of the user's data, such as that shown in
Next, at block 1210, the distribution client module 405 provides a navigable graphical display of the user's index information to the user. For example, the distribution client module 405 may interpret the received index information (and/or locally cached index information) in order to produce a graphical representation similar to interface 1300. Alternatively, the distribution client module 405 may interpret the received index information in order to instruct another application (e.g., Windows Explorer or Outlook) regarding how to provide a similar graphical representation.
At block 1215, the distribution client module 405 receives a request to provide a preview of a selected version of a selected object (e.g., via a menu 1310 or a double-click). In response, at block 1220, the distribution client module 405 requests a preview version of the selected data object from the distribution module 490 (e.g., by sending an object ID and version ID). When the distribution client module receives the requested preview version, it presents the preview version to the user using a limited-feature viewer application, such as a PDF viewer or web browser.
At block 1225, the distribution client module 405 receives a request for a copy of a selected version of a selected object (e.g., via a menu 1310 or a double-click). In response, at block 1230, the distribution client module 405 requests a copy of the selected version of the selected data object from the distribution module 490 (e.g., by providing an associated object ID and version ID). Once the copy is received, the distribution client module launches an application capable of opening the data object, typically a full-featured application associated with the file type of the data object. If a user edits a copy of a selected data object, the distribution client module may push a copy of the edited version back to its source computing device (via the distribution module), so that the source computing device has the latest version of the data object.
At block 1235, the distribution client module 405 receives a request for a live browse session. These requests are described in further detail herein with respect to
Although process 1200 has been described as being performed at a particular computing device, a similar process 1200 may be performed by a web server associated with the IMS that is configured to provide IMS users with a web portal to access their data. In such examples, the steps that were described above as being performed by a distribution client module may instead be performed by a web server.
A distribution module 490 may perform actions that are complementary to the process 1200 performed by a distribution client module 490.
At block 1410, the distribution module 490 receives a request to send a preview version of a data object to a distribution client module 405. The request may indicate an object identifier and/or version identifier associated with a single desired data object. Alternatively, the request may ask for preview versions of numerous data objects that match a provided set of criteria. For example, the request may ask for any new preview versions generated in the last 30 days, so that those recent previews can be cached by the client distribution module 405. In response to the received request, at block 1415, for each indicated version of a data object, the distribution module selects a preview version by using a received data object identifier and version identifier (or the received criteria) to look up an associated preview version from the preview column 1020 of the object log index 1000. When selecting the preview version, the distribution module may determine the capabilities of the device or portal that will be used to display the preview to the user. The distribution module may then select a preview version based on the determined capabilities. For example, the distribution module may determine the hard disk capacity, memory capacity, video or sound card specifications, network connection type or bandwidth, processing power, and installed applications of the computing device and select a preview version that is best suited to those characteristics. More information about selecting preview versions suitable for a particular computing device can be found in the commonly-assigned U.S. patent application No. 61/618,125 entitled “Smart Archiving and Data Previewing for Mobile Devices,” filed Mar. 30, 2012, which is hereby incorporated by reference herein in its entirety. If there is no existing preview version available from the object log index 1000 that is suitable for the capabilities of the computing device, the distribution module may generate a suitable preview version. The distribution module then sends the selected preview version(s) to the distribution client module, which may be performed using source-side deduplication techniques.
At block 1420, the distribution module 490 receives a request to send a copy of a selected version of a selected data object to a distribution client module 405. The request may indicate a data object identifier and/or version identifier associated with the desired data object (or may specify a set of criteria that identifies one or more versions of one or more data objects). In response to the received request, at block 1425, the distribution module locates a copy of the requested version of a data object by using a received data object identifier and version identifier (or other criteria) to look up an associated stored copy from the object lookup column 1010 of the object log index 1000. The distribution module then sends the located copy to the distribution client module, which may be performed using source-side deduplication techniques. When an applicable synchronization policy specifies locking, as described previously, before performing block 1420, the distribution module may verify that the object has not already been locked and after performing block 1420, the distribution module may add a “lock” on the data object to prevent other computing devices from simultaneously editing the data object, e.g., by adding a timestamp to column 1116.
At block 1430, the distribution module 490 receives a request from a requesting distribution client module 405 at a requesting computing device to facilitate a “live browse” session between the requesting distribution client module and a second, target computing device. There are two variants of a live browse session. A first variant of a live browse session presents a user at the requesting computing device with a browseable and searchable view of data objects on the target computing device, even if those data objects have not yet been pushed to the distribution module 490. In a second variant, the requesting distribution client module requests to open a data object in a “live browse” mode. The second variant permits the requesting distribution client module to utilize computing resources of the target computing device (e.g., processing power, installed applications, memory, hard disk) in order to view or manipulate files and other data objects.
At block 1435, the distribution module 490 responds to the request for a live browse session. When a request for the first variant of live browsing is received (i.e., a request to browse the files of a target computing device), the distribution module may first determine if the target computing device is online, i.e., has network connectivity to the distribution module. If the target computing device is not online, the distribution module may access backup copies of the data from the target computing device and/or indexing information that were created as part of a backup operation in order to create an index similar to that shown in the object log index 1000, which reflects the data contents and organization of the target computing device. Otherwise, if the target computing device is online, the distribution module may query a distribution client module 405 at the target computing device and ask it to provide an updated index of all of the file folders and data objects on the target computing device (or a subset of its folders and data objects). For example, the distribution module may request indexing information for each data object similar to the indexing information shown in the object log index 1000. The distribution module then provides the indexing information obtained from either the backup operations or from the target computer itself to the requesting distribution client module. The requesting distribution client module uses the indexing information to produce an interface with a graphical, navigable and searchable file folder structure of the folders and data objects on the target computing device, such as the interface shown in
The requests and responses at block 1435 may be iterative, so that the distribution module first obtains and provides only coarse indexing information (e.g., only the data objects and folders that appear in top-level file folders of the target device) and then later obtains and provides additional indexing information, e.g., in response to a user navigating to a specific folder in a displayed navigable file folder structure. For example, the distribution module may, upon such user navigation, obtain and provide more granular indexing information for specific folders on the target computing device. If a user indicates that she wishes to open a preview version or copy of the data object shown in the navigable folder structure (e.g., as described previously with respect to
In addition to providing index information related to the data objects available on a target computing device, the distribution module may also determine and provide information regarding the applications that are installed on the target computing device and are capable of being run in a “live browse” mode. In this way, the user can initiate applications on the target computing device from a requesting device such as a limited-feature mobile device.
The previous discussion described the distribution module as playing an intermediary role by collecting and distributing indexing information, preview versions, and copies of data objects. However, in some examples, instead the target distribution client module may communicate directly with the requesting distribution client module to exchange this information directly. Also, the requesting distribution client module may generate preview versions, as needed.
When a request for the second variant of live browsing is received, in response, at block 1435, the distribution module 490 identifies the target computing device and establishes a secure connection between a requesting distribution client module and a target distribution client module at the target computing device. Once the connection is established, the target distribution client module may initiate applications installed at the target computing device and provide an optimized view of the application to the requesting distribution client module. This second feature of a live browse session is described in greater detail herein, e.g., with respect to
The distribution module 490 and client distribution module 405 may perform variants of the processes 1400 and 1200 respectively. As one example, instead of providing a preview of a data object only in response to an explicit request for the preview, the distribution module 490 may instead provide a preview of a data object when a new version of the data object is received and indexed, in conjunction with indexing information at block 1405, and/or upon a prescribed schedule. As another example, instead of providing a copy of a data object in response to an explicit request for the copy, the distribution module may instead provide a copy of the data object when a new version of the data object is received and indexed and/or upon a prescribed schedule. In these variants, the methods may keep data objects that are being edited at different computing devices synchronized across those different computing devices. When all of the synchronized computing devices have network access, cross-device synchronization may occur nearly in real-time. In another variant, instead of providing a preview of a data object or a copy of a data object only in response to an explicit request for a preview or copy, the distribution module may proactively push a subset of the previews and data objects (e.g., in conjunction with indexing information) and the distribution client module may cache these so it can respond to user requests even when it has no network connectivity. For example, the distribution module may proactively push previews or copies of any objects that have been edited in the last 30 days.
Live Browsing
The second variant of a live browse session permits a user of a mobile device or other limited-feature device to execute full-featured applications installed on a remote computing device (e.g., a desktop or laptop device) and to interact with the full-featured application via the input-output hardware of the limited-feature device. As described above, when a user of a requesting computing device indicates that they want to open a data object in a “live browse” mode, a connection is established between a distribution client module 405 at the requesting computer (the “requesting distribution client module”) and a distribution client module 405 at the target computing device (the “target distribution client module.” The target distribution client module identifies a copy of the data object and if necessary, requests a copy of the data object, e.g., from a distribution module 490. The target distribution client module launches an instance of a full-featured native application using the processor and memory of the target computing device in order to open the data object in the native application.
As shown in
Other Features
In some examples, the functionality of the information management system may be provided to an organization on a subscription, or software-as-a-service or platform-as-a-service basis. In such examples, the operator of the information management system may charge an organization on a per-user basis and/or on the basis of other metrics of usage.
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 computing devices suitable for the purposes described herein. Modules described herein may be executed by a general-purpose computer, e.g., a server computer, wireless device, or personal computer. Those skilled in the relevant art will appreciate that aspects of the invention can be practiced with other communications, data processing, or computer system configurations, including: Internet appliances, hand-held devices (including personal digital assistants (PDAs)), wearable computers, all manner of cellular or mobile phones, multi-processor systems, microprocessor-based or programmable consumer electronics, set-top boxes, network PCs, mini-computers, mainframe computers, and the like. Furthermore, aspects of the invention can be embodied in a special purpose computer or data processor that is specifically programmed, configured, or constructed to perform one or more of the computer-executable instructions explained in detail herein.
Software and other modules may be accessible via local memory, a network, a browser, or other application in an ASP context, or via another means suitable for the purposes described herein. Examples of the technology can also be practiced in distributed computing environments where tasks or modules are performed by remote processing devices, which are linked through a communications network, such as a Local Area Network (LAN), Wide Area Network (WAN), or the Internet. In a distributed computing environment, program modules may be located in both local and remote memory storage devices. 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 interfaces suitable for the purposes described herein.
Examples of the technology may be stored or distributed on computer-readable media, including magnetically or optically readable computer disks, hard-wired or preprogrammed chips (e.g., EEPROM semiconductor chips), nanotechnology memory, or other data storage media. Indeed, computer-implemented instructions, data structures, screen displays, and other data under aspects of the invention may be distributed over the Internet or over other networks (including wireless networks), or they may be provided on any analog or digital network (packet switched, circuit switched, or other scheme).
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
The above Detailed Description is not intended to be exhaustive or to limit the invention to the precise form disclosed above. While specific examples for the invention are described above for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative implementations may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed or implemented in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.
The teachings of the invention provided herein can be applied to other systems, not necessarily the systems described herein. The elements and acts of the various examples described above can be combined to provide further implementations of the invention.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further implementations of the invention.
These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain examples of the invention, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.
While certain examples are presented below in certain forms, the applicant contemplates the various aspects of the invention in any number of claim forms. Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the invention.
The present application is a continuation of U.S. patent application Ser. No. 13/787,280, filed Mar. 6, 2013, now U.S. Pat. No. 9,529,871, which claims priority to and the benefit of U.S. Provisional Application No. 61/618,506, filed Mar. 30, 2012, each of which is hereby incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4686620 | Ng | Aug 1987 | A |
| 4995035 | Cole et al. | Feb 1991 | A |
| 5005122 | Griffin et al. | Apr 1991 | A |
| 5093912 | Dong et al. | Mar 1992 | A |
| 5133065 | Cheffetz et al. | Jul 1992 | A |
| 5193154 | Kitajima et al. | Mar 1993 | A |
| 5212772 | Masters | May 1993 | A |
| 5226157 | Nakano et al. | Jul 1993 | A |
| 5239647 | Anglin et al. | Aug 1993 | A |
| 5241164 | Pavlidis et al. | Aug 1993 | A |
| 5241668 | Eastridge et al. | Aug 1993 | A |
| 5241670 | Eastridge et al. | Aug 1993 | A |
| 5265159 | Kung | Nov 1993 | A |
| 5276860 | Fortier et al. | Jan 1994 | A |
| 5276867 | Kenley et al. | Jan 1994 | A |
| 5287500 | Stoppani, Jr. | Feb 1994 | A |
| 5321816 | Rogan et al. | Jun 1994 | A |
| 5333315 | Saether et al. | Jul 1994 | A |
| 5347653 | Flynn et al. | Sep 1994 | A |
| 5367698 | Webber et al. | Nov 1994 | A |
| 5410700 | Fecteau et al. | Apr 1995 | A |
| 5412668 | Dewey | May 1995 | A |
| 5448724 | Hayashi | Sep 1995 | A |
| 5455926 | Keele et al. | Oct 1995 | A |
| 5491810 | Allen | Feb 1996 | A |
| 5495457 | Takagi et al. | Feb 1996 | A |
| 5495607 | Pisello et al. | Feb 1996 | A |
| 5499364 | Klein et al. | Mar 1996 | A |
| 5504873 | Martin et al. | Apr 1996 | A |
| 5506986 | Healy | Apr 1996 | A |
| 5544345 | Carpenter et al. | Aug 1996 | A |
| 5544347 | Yanai et al. | Aug 1996 | A |
| 5548521 | Krayer et al. | Aug 1996 | A |
| 5559957 | Balk | Sep 1996 | A |
| 5608865 | Midgely et al. | Mar 1997 | A |
| 5619644 | Crockett et al. | Apr 1997 | A |
| 5638509 | Dunphy et al. | Jun 1997 | A |
| 5673381 | Huai et al. | Sep 1997 | A |
| 5677900 | Nishida et al. | Oct 1997 | A |
| 5699361 | Ding et al. | Dec 1997 | A |
| 5729743 | Squibb | Mar 1998 | A |
| 5751997 | Kullick et al. | May 1998 | A |
| 5758359 | Saxon | May 1998 | A |
| 5761677 | Senator et al. | Jun 1998 | A |
| 5764972 | Crouse et al. | Jun 1998 | A |
| 5778395 | Whiting et al. | Jul 1998 | A |
| 5812398 | Nielsen | Sep 1998 | A |
| 5813009 | Johnson et al. | Sep 1998 | A |
| 5813017 | Morris | Sep 1998 | A |
| 5815662 | Ong | Sep 1998 | A |
| 5832522 | Blickenstaff et al. | Nov 1998 | A |
| 5860068 | Cook | Jan 1999 | A |
| 5875478 | Blumenau | Feb 1999 | A |
| 5875481 | Ashton et al. | Feb 1999 | A |
| 5887134 | Ebrahim | Mar 1999 | A |
| 5893139 | Kamiyama et al. | Apr 1999 | A |
| 5898593 | Baca et al. | Apr 1999 | A |
| 5901327 | Ofek | May 1999 | A |
| 5924102 | Perks | Jul 1999 | A |
| 5950205 | Aviani, Jr. | Sep 1999 | A |
| 5958005 | Thorne et al. | Sep 1999 | A |
| 5974563 | Beeler, Jr. | Oct 1999 | A |
| 5978577 | Rierden et al. | Nov 1999 | A |
| 5983239 | Cannon | Nov 1999 | A |
| 6014695 | Yamashita et al. | Jan 2000 | A |
| 6021415 | Cannon et al. | Feb 2000 | A |
| 6023705 | Bellinger et al. | Feb 2000 | A |
| 6026398 | Brown et al. | Feb 2000 | A |
| 6026414 | Anglin | Feb 2000 | A |
| 6052735 | Ulrich et al. | Apr 2000 | A |
| 6076148 | Kedem | Jun 2000 | A |
| 6088694 | Burns et al. | Jul 2000 | A |
| 6094416 | Ying | Jul 2000 | A |
| 6131095 | Low et al. | Oct 2000 | A |
| 6131099 | Johnson et al. | Oct 2000 | A |
| 6131147 | Takagi | Oct 2000 | A |
| 6131190 | Sidwell | Oct 2000 | A |
| 6137864 | Yaker | Oct 2000 | A |
| 6148412 | Cannon et al. | Nov 2000 | A |
| 6149316 | Harari et al. | Nov 2000 | A |
| 6154738 | Call | Nov 2000 | A |
| 6154787 | Urevig et al. | Nov 2000 | A |
| 6161111 | Mutalik et al. | Dec 2000 | A |
| 6167402 | Yeager | Dec 2000 | A |
| 6195794 | Buxton | Feb 2001 | B1 |
| 6212512 | Barney et al. | Apr 2001 | B1 |
| 6223205 | Harchol-Balter et al. | Apr 2001 | B1 |
| 6246882 | Lachance | Jun 2001 | B1 |
| 6260069 | Anglin | Jul 2001 | B1 |
| 6266678 | McDevitt et al. | Jul 2001 | B1 |
| 6266784 | Hsiao et al. | Jul 2001 | B1 |
| 6269382 | Cabrera et al. | Jul 2001 | B1 |
| 6269431 | Dunham | Jul 2001 | B1 |
| 6275953 | Vahalia et al. | Aug 2001 | B1 |
| 6301592 | Aoyama et al. | Oct 2001 | B1 |
| 6304880 | Kishi | Oct 2001 | B1 |
| 6308245 | Johnson et al. | Oct 2001 | B1 |
| 6324581 | Xu et al. | Nov 2001 | B1 |
| 6328766 | Long | Dec 2001 | B1 |
| 6330570 | Crighton | Dec 2001 | B1 |
| 6330572 | Sitka | Dec 2001 | B1 |
| 6330642 | Carteau | Dec 2001 | B1 |
| 6338006 | Jesionowski et al. | Jan 2002 | B1 |
| 6343324 | Hubis et al. | Jan 2002 | B1 |
| RE37601 | Eastridge et al. | Mar 2002 | E |
| 6353878 | Dunham | Mar 2002 | B1 |
| 6356801 | Goodman et al. | Mar 2002 | B1 |
| 6356901 | MacLeod et al. | Mar 2002 | B1 |
| 6366900 | Hu | Apr 2002 | B1 |
| 6374336 | Peters et al. | Apr 2002 | B1 |
| 6389432 | Pothapragada et al. | May 2002 | B1 |
| 6418441 | Call | Jul 2002 | B1 |
| 6418478 | Ignatius et al. | Jul 2002 | B1 |
| 6421711 | Blumenau et al. | Jul 2002 | B1 |
| 6434682 | Ashton et al. | Aug 2002 | B1 |
| 6457017 | Watkins et al. | Sep 2002 | B2 |
| 6484166 | Maynard | Nov 2002 | B1 |
| 6487561 | Ofek et al. | Nov 2002 | B1 |
| 6490666 | Cabrera et al. | Dec 2002 | B1 |
| 6496744 | Cook | Dec 2002 | B1 |
| 6519679 | Devireddy et al. | Feb 2003 | B2 |
| 6538669 | Lagueux, Jr. et al. | Mar 2003 | B1 |
| 6542972 | Ignatius et al. | Apr 2003 | B2 |
| 6550057 | Bowman-Amuah | Apr 2003 | B1 |
| 6564228 | O'Connor | May 2003 | B1 |
| 6615349 | Hair | Sep 2003 | B1 |
| 6616047 | Catan | Sep 2003 | B2 |
| 6658436 | Oshinsky et al. | Dec 2003 | B2 |
| 6658526 | Nguyen et al. | Dec 2003 | B2 |
| 6662281 | Ballard et al. | Dec 2003 | B2 |
| 6669832 | Saito et al. | Dec 2003 | B1 |
| 6674924 | Wright et al. | Jan 2004 | B2 |
| 6704839 | Butterworth et al. | Mar 2004 | B2 |
| 6721334 | Ketcham | Apr 2004 | B1 |
| 6732293 | Schneider | May 2004 | B1 |
| 6757794 | Cabrera et al. | Jun 2004 | B2 |
| 6771595 | Gilbert et al. | Aug 2004 | B1 |
| 6785078 | Basham et al. | Aug 2004 | B2 |
| 6789161 | Blendermann et al. | Sep 2004 | B1 |
| 6802025 | Thomas et al. | Oct 2004 | B1 |
| 6820035 | Zahavi | Nov 2004 | B1 |
| 6851031 | Trimmer et al. | Feb 2005 | B2 |
| 6862622 | Jorgensen | Mar 2005 | B2 |
| 6909356 | Brown et al. | Jun 2005 | B2 |
| 6922687 | Vernon | Jul 2005 | B2 |
| 6934879 | Misra et al. | Aug 2005 | B2 |
| 6941370 | Boies et al. | Sep 2005 | B2 |
| 6950723 | Gallo et al. | Sep 2005 | B2 |
| 6968351 | Butterworth | Nov 2005 | B2 |
| 6968479 | Wyatt et al. | Nov 2005 | B2 |
| 6972918 | Kokami et al. | Dec 2005 | B2 |
| 6973369 | Trimmer et al. | Dec 2005 | B2 |
| 6973553 | Archibald, Jr. et al. | Dec 2005 | B1 |
| 6983351 | Gibble et al. | Jan 2006 | B2 |
| 7006435 | Davies et al. | Feb 2006 | B1 |
| 7010387 | Lantry et al. | Mar 2006 | B2 |
| 7012529 | Sajkowsky | Mar 2006 | B2 |
| 7034683 | Ghazarian | Apr 2006 | B2 |
| 7035880 | Crescenti et al. | Apr 2006 | B1 |
| 7058649 | Ough et al. | Jun 2006 | B2 |
| 7069466 | Trimmer et al. | Jun 2006 | B2 |
| 7082441 | Zahavi et al. | Jul 2006 | B1 |
| 7085786 | Carlson et al. | Aug 2006 | B2 |
| 7085904 | Mizuno et al. | Aug 2006 | B2 |
| 7093089 | de Brebisson | Aug 2006 | B2 |
| 7096269 | Yamagami | Aug 2006 | B2 |
| 7096315 | Takeda et al. | Aug 2006 | B2 |
| 7103619 | Rajpurkar et al. | Sep 2006 | B1 |
| 7103731 | Gibble et al. | Sep 2006 | B2 |
| 7103740 | Colgrove et al. | Sep 2006 | B1 |
| 7107298 | Prahlad et al. | Sep 2006 | B2 |
| 7107395 | Ofek et al. | Sep 2006 | B1 |
| 7118034 | Baldassari et al. | Oct 2006 | B2 |
| 7120823 | Foster et al. | Oct 2006 | B2 |
| 7130970 | Devassy et al. | Oct 2006 | B2 |
| 7136720 | Deckers | Nov 2006 | B2 |
| 7146377 | Nowicki et al. | Dec 2006 | B2 |
| 7155465 | Lee et al. | Dec 2006 | B2 |
| 7155486 | Aoshima et al. | Dec 2006 | B2 |
| 7162496 | Amarendran et al. | Jan 2007 | B2 |
| 7162604 | Nourmohamadian et al. | Jan 2007 | B1 |
| 7162693 | Yamanaka et al. | Jan 2007 | B2 |
| 7165059 | Shah et al. | Jan 2007 | B1 |
| 7191283 | Amemiya et al. | Mar 2007 | B2 |
| 7197490 | English | Mar 2007 | B1 |
| 7200621 | Beck et al. | Apr 2007 | B2 |
| 7203944 | van Rietschote et al. | Apr 2007 | B1 |
| 7209949 | Mousseau et al. | Apr 2007 | B2 |
| 7213118 | Goodman et al. | May 2007 | B2 |
| 7216244 | Amano | May 2007 | B2 |
| 7246140 | Therrien et al. | Jul 2007 | B2 |
| 7246207 | Kottomtharayil et al. | Jul 2007 | B2 |
| 7246258 | Chen et al. | Jul 2007 | B2 |
| 7251218 | Jorgensen | Jul 2007 | B2 |
| 7275063 | Horn | Sep 2007 | B2 |
| 7277246 | Barbian et al. | Oct 2007 | B2 |
| 7277953 | Wils et al. | Oct 2007 | B2 |
| 7281032 | Kodama | Oct 2007 | B2 |
| 7287047 | Kavuri | Oct 2007 | B2 |
| 7293133 | Colgrove et al. | Nov 2007 | B1 |
| 7302540 | Holdman et al. | Nov 2007 | B1 |
| 7315923 | Retnamma et al. | Jan 2008 | B2 |
| 7343356 | Prahlad et al. | Mar 2008 | B2 |
| 7343453 | Prahlad et al. | Mar 2008 | B2 |
| 7343459 | Prahlad et al. | Mar 2008 | B2 |
| 7346623 | Prahlad et al. | Mar 2008 | B2 |
| 7346751 | Prahlad et al. | Mar 2008 | B2 |
| 7379850 | Sprogis et al. | May 2008 | B2 |
| 7395282 | Crescenti et al. | Jul 2008 | B1 |
| 7395387 | Berkowitz et al. | Jul 2008 | B2 |
| 7395446 | Luke et al. | Jul 2008 | B2 |
| 7398524 | Shapiro | Jul 2008 | B2 |
| 7401728 | Markham et al. | Jul 2008 | B2 |
| 7412433 | Anglin et al. | Aug 2008 | B2 |
| 7418464 | Cannon et al. | Aug 2008 | B2 |
| 7421312 | Trossell | Sep 2008 | B2 |
| 7434090 | Hartung et al. | Oct 2008 | B2 |
| 7447907 | Hart, III et al. | Nov 2008 | B2 |
| 7451283 | Chen et al. | Nov 2008 | B2 |
| 7454569 | Kavuri et al. | Nov 2008 | B2 |
| 7467167 | Patterson | Dec 2008 | B2 |
| 7472238 | Gokhale et al. | Dec 2008 | B1 |
| 7500053 | Kavuri et al. | Mar 2009 | B1 |
| 7529782 | Prahlad et al. | May 2009 | B2 |
| 7536424 | Barzilai et al. | May 2009 | B2 |
| 7539702 | Deshmukh et al. | May 2009 | B2 |
| 7539783 | Kochunni et al. | May 2009 | B2 |
| 7565340 | Herlocker et al. | Jul 2009 | B2 |
| 7581011 | Teng | Aug 2009 | B2 |
| 7584227 | Gokhale et al. | Sep 2009 | B2 |
| 7584298 | Klinker et al. | Sep 2009 | B2 |
| 7587749 | Leser et al. | Sep 2009 | B2 |
| 7596586 | Gokhale et al. | Sep 2009 | B2 |
| 7603518 | Kottomtharayil | Oct 2009 | B2 |
| 7617262 | Prahlad et al. | Nov 2009 | B2 |
| 7617392 | Hair | Nov 2009 | B2 |
| 7627617 | Kavuri et al. | Dec 2009 | B2 |
| 7644245 | Prahlad et al. | Jan 2010 | B2 |
| 7653671 | Ikezawa et al. | Jan 2010 | B2 |
| 7657666 | Kottomtharayil et al. | Feb 2010 | B2 |
| 7659820 | Schnee et al. | Feb 2010 | B2 |
| 7660812 | Findlay et al. | Feb 2010 | B2 |
| 7680843 | Panchbudhe et al. | Mar 2010 | B1 |
| 7689510 | Lamkin et al. | Mar 2010 | B2 |
| 7693832 | Vargas et al. | Apr 2010 | B2 |
| 7702659 | Ban et al. | Apr 2010 | B2 |
| 7702831 | Ma et al. | Apr 2010 | B2 |
| 7707060 | Chainer et al. | Apr 2010 | B2 |
| 7712094 | Shapiro | May 2010 | B2 |
| 7720817 | Stager et al. | May 2010 | B2 |
| 7734669 | Kottomtharayil et al. | Jun 2010 | B2 |
| 7739450 | Kottomtharayil | Jun 2010 | B2 |
| 7747579 | Prahlad et al. | Jun 2010 | B2 |
| 7748610 | Bell et al. | Jul 2010 | B2 |
| 7751628 | Reisman | Jul 2010 | B1 |
| 7765167 | Prahlad et al. | Jul 2010 | B2 |
| 7765369 | Prahlad et al. | Jul 2010 | B1 |
| 7805416 | Compton et al. | Sep 2010 | B1 |
| 7809699 | Passmore et al. | Oct 2010 | B2 |
| 7809914 | Kottomtharayil et al. | Oct 2010 | B2 |
| 7818417 | Ginis et al. | Oct 2010 | B2 |
| 7822715 | Petruzzo | Oct 2010 | B2 |
| 7831566 | Kavuri et al. | Nov 2010 | B2 |
| 7840537 | Gokhale et al. | Nov 2010 | B2 |
| 7844573 | Amarendran et al. | Nov 2010 | B2 |
| 7849266 | Kavuri et al. | Dec 2010 | B2 |
| 7861011 | Kottomtharayil et al. | Dec 2010 | B2 |
| 7873802 | Gokhale et al. | Jan 2011 | B2 |
| 7877351 | Crescenti et al. | Jan 2011 | B2 |
| 7877362 | Gokhale et al. | Jan 2011 | B2 |
| 7889847 | Gainsboro | Feb 2011 | B2 |
| 7890796 | Pawar et al. | Feb 2011 | B2 |
| 7904350 | Ayala et al. | Mar 2011 | B2 |
| 7917473 | Kavuri et al. | Mar 2011 | B2 |
| 7917695 | Ulrich et al. | Mar 2011 | B2 |
| 7934071 | Abe et al. | Apr 2011 | B2 |
| 7937365 | Prahlad et al. | May 2011 | B2 |
| 7937393 | Prahlad et al. | May 2011 | B2 |
| 7945810 | Soran et al. | May 2011 | B2 |
| 7953802 | Mousseau et al. | May 2011 | B2 |
| 7966293 | Owara et al. | Jun 2011 | B1 |
| 7969306 | Ebert et al. | Jun 2011 | B2 |
| 7975061 | Gokhale et al. | Jul 2011 | B1 |
| 7987319 | Kottomtharayil | Jul 2011 | B2 |
| 8005913 | Carlander | Aug 2011 | B1 |
| 8006111 | Faibish et al. | Aug 2011 | B1 |
| 8032569 | Oshita et al. | Oct 2011 | B2 |
| 8040727 | Harari | Oct 2011 | B1 |
| 8051043 | Young | Nov 2011 | B2 |
| 8112605 | Kavuri | Feb 2012 | B2 |
| 8140786 | Bunte et al. | Mar 2012 | B2 |
| 8156086 | Lu et al. | Apr 2012 | B2 |
| 8161318 | D'Souza et al. | Apr 2012 | B2 |
| 8170995 | Prahlad et al. | May 2012 | B2 |
| 8195800 | Tameshige et al. | Jun 2012 | B2 |
| 8200638 | Zheng et al. | Jun 2012 | B1 |
| 8204862 | Paulzagade et al. | Jun 2012 | B1 |
| 8209293 | Gokhale et al. | Jun 2012 | B2 |
| 8219524 | Gokhale | Jul 2012 | B2 |
| 8229954 | Kottomtharayil et al. | Jul 2012 | B2 |
| 8230066 | Heil | Jul 2012 | B2 |
| 8230171 | Kottomtharayil | Jul 2012 | B2 |
| 8230195 | Amarendran et al. | Jul 2012 | B2 |
| 8234417 | Kottomtharayil et al. | Jul 2012 | B2 |
| 8234468 | Deshmukh et al. | Jul 2012 | B1 |
| 8244841 | Shaji et al. | Aug 2012 | B2 |
| 8266406 | Kavuri | Sep 2012 | B2 |
| 8266615 | Shapiro | Sep 2012 | B2 |
| 8285681 | Prahlad et al. | Oct 2012 | B2 |
| 8285898 | Amit et al. | Oct 2012 | B2 |
| 8306926 | Prahlad et al. | Nov 2012 | B2 |
| 8307177 | Prahlad et al. | Nov 2012 | B2 |
| 8327050 | Amit et al. | Dec 2012 | B2 |
| 8335789 | Hull et al. | Dec 2012 | B2 |
| 8341182 | Muller et al. | Dec 2012 | B2 |
| 8346733 | Gokhale et al. | Jan 2013 | B2 |
| 8346734 | Muller et al. | Jan 2013 | B2 |
| 8347088 | Moore et al. | Jan 2013 | B2 |
| 8352433 | Crescenti et al. | Jan 2013 | B2 |
| 8364652 | Vijayan et al. | Jan 2013 | B2 |
| 8402000 | Gokhale et al. | Mar 2013 | B2 |
| 8407190 | Prahlad et al. | Mar 2013 | B2 |
| 8412848 | Therrien et al. | Apr 2013 | B2 |
| 8417678 | Bone et al. | Apr 2013 | B2 |
| 8422733 | Reisman | Apr 2013 | B2 |
| 8433679 | Crescenti et al. | Apr 2013 | B2 |
| 8463753 | Gokhale et al. | Jun 2013 | B2 |
| 8463994 | Kottomtharayil | Jun 2013 | B2 |
| 8478876 | Paul et al. | Jul 2013 | B2 |
| 8484165 | Gokhale et al. | Jul 2013 | B2 |
| 8510573 | Muller et al. | Aug 2013 | B2 |
| 8527549 | Cidon | Sep 2013 | B2 |
| 8539118 | Kottomtharayil et al. | Sep 2013 | B2 |
| 8572330 | Kottomtharayil et al. | Oct 2013 | B2 |
| 8572706 | Lucovsky et al. | Oct 2013 | B2 |
| 8578120 | Attarde et al. | Nov 2013 | B2 |
| 8600998 | Chaudhary et al. | Dec 2013 | B1 |
| 8620286 | Stannard et al. | Dec 2013 | B2 |
| 8626128 | Limont et al. | Jan 2014 | B2 |
| 8635204 | Xie et al. | Jan 2014 | B1 |
| 8656068 | Kottomtharayil et al. | Feb 2014 | B2 |
| 8661216 | Kavuri et al. | Feb 2014 | B2 |
| 8671209 | Awano | Mar 2014 | B2 |
| 8688641 | Cook et al. | Apr 2014 | B1 |
| 8695058 | Batchu et al. | Apr 2014 | B2 |
| 8700578 | Varadan et al. | Apr 2014 | B1 |
| 8706976 | Kottomtharayil et al. | Apr 2014 | B2 |
| 8712959 | Lim et al. | Apr 2014 | B1 |
| 8756203 | Muller et al. | Jun 2014 | B2 |
| 8825591 | Lai et al. | Sep 2014 | B1 |
| 8832031 | Kavuri et al. | Sep 2014 | B2 |
| 8832044 | Gipp et al. | Sep 2014 | B1 |
| 8849761 | Prahlad et al. | Sep 2014 | B2 |
| 8849762 | Kumarasamy et al. | Sep 2014 | B2 |
| 8850140 | De Atley et al. | Sep 2014 | B2 |
| 8886853 | Kottomtharayil et al. | Nov 2014 | B2 |
| 8924428 | Muller et al. | Dec 2014 | B2 |
| 8931107 | Brandwine | Jan 2015 | B1 |
| 8938481 | Kumarasamy et al. | Jan 2015 | B2 |
| 8966017 | Wipfel et al. | Feb 2015 | B2 |
| 8996823 | Kottomtharayil et al. | Mar 2015 | B2 |
| 9027076 | Roach et al. | May 2015 | B2 |
| 9069799 | Vijayan et al. | Jun 2015 | B2 |
| 9244779 | Littlefield et al. | Jan 2016 | B2 |
| 9529871 | Vibhor et al. | Dec 2016 | B2 |
| 20020010661 | Waddington et al. | Jan 2002 | A1 |
| 20020032613 | Buettgenbach et al. | Mar 2002 | A1 |
| 20020049778 | Bell et al. | Apr 2002 | A1 |
| 20020069324 | Gerasimov et al. | Jun 2002 | A1 |
| 20020087950 | Brodeur et al. | Jul 2002 | A1 |
| 20030055671 | Nassar | Mar 2003 | A1 |
| 20030065759 | Britt et al. | Apr 2003 | A1 |
| 20030101155 | Gokhale et al. | May 2003 | A1 |
| 20030134619 | Phillips et al. | Jul 2003 | A1 |
| 20030177145 | Lohn | Sep 2003 | A1 |
| 20030220901 | Carr et al. | Nov 2003 | A1 |
| 20040054607 | Waddington et al. | Mar 2004 | A1 |
| 20040073677 | Honma et al. | Apr 2004 | A1 |
| 20040083202 | Mu et al. | Apr 2004 | A1 |
| 20040107199 | Dalrymple et al. | Jun 2004 | A1 |
| 20040186847 | Rappaport et al. | Sep 2004 | A1 |
| 20040192260 | Sugimoto et al. | Sep 2004 | A1 |
| 20040193953 | Callahan et al. | Sep 2004 | A1 |
| 20050008163 | Leser et al. | Jan 2005 | A1 |
| 20050021524 | Oliver | Jan 2005 | A1 |
| 20050033913 | Kottomtharayil et al. | Feb 2005 | A1 |
| 20050039069 | Prahlad et al. | Feb 2005 | A1 |
| 20050076264 | Rowan et al. | Apr 2005 | A1 |
| 20050102203 | Keong | May 2005 | A1 |
| 20050102328 | Ring | May 2005 | A1 |
| 20050125807 | Brady et al. | Jun 2005 | A1 |
| 20050174869 | Kottomtharayil et al. | Aug 2005 | A1 |
| 20050177828 | Graham et al. | Aug 2005 | A1 |
| 20050210304 | Hartung et al. | Sep 2005 | A1 |
| 20050246342 | Vernon | Nov 2005 | A1 |
| 20060004639 | O'Keefe | Jan 2006 | A1 |
| 20060004675 | Bennett et al. | Jan 2006 | A1 |
| 20060011720 | Call | Jan 2006 | A1 |
| 20060069886 | Tulyani | Mar 2006 | A1 |
| 20060075007 | Anderson et al. | Apr 2006 | A1 |
| 20060095385 | Atkinson et al. | May 2006 | A1 |
| 20060100912 | Kumar et al. | May 2006 | A1 |
| 20060106881 | Leung et al. | May 2006 | A1 |
| 20060161879 | Lubrecht et al. | Jul 2006 | A1 |
| 20060169769 | Boyarsky et al. | Aug 2006 | A1 |
| 20060224846 | Amarendran et al. | Oct 2006 | A1 |
| 20060248165 | Sridhar et al. | Nov 2006 | A1 |
| 20060282194 | Schaefer et al. | Dec 2006 | A1 |
| 20060288044 | Kashiwagi et al. | Dec 2006 | A1 |
| 20070130105 | Papatla | Jun 2007 | A1 |
| 20070185912 | Gupta et al. | Aug 2007 | A1 |
| 20080077622 | Keith | Mar 2008 | A1 |
| 20080147621 | Newman | Jun 2008 | A1 |
| 20080177806 | Cannon et al. | Jul 2008 | A1 |
| 20080243795 | Prahlad et al. | Oct 2008 | A1 |
| 20090319534 | Gokhale | Dec 2009 | A1 |
| 20100030528 | Smith et al. | Feb 2010 | A1 |
| 20100070466 | Prahlad et al. | Mar 2010 | A1 |
| 20100070474 | Lad | Mar 2010 | A1 |
| 20100070726 | Ngo et al. | Mar 2010 | A1 |
| 20100077453 | Mohanty | Mar 2010 | A1 |
| 20100082672 | Kottomtharayil et al. | Apr 2010 | A1 |
| 20100269164 | Sosnosky et al. | Oct 2010 | A1 |
| 20100318500 | Murphy et al. | Dec 2010 | A1 |
| 20100333116 | Prahlad et al. | Dec 2010 | A1 |
| 20110040736 | Kalaboukis et al. | Feb 2011 | A1 |
| 20110093672 | Gokhale et al. | Apr 2011 | A1 |
| 20110218964 | Hagan | Sep 2011 | A1 |
| 20110231852 | Gokhale et al. | Sep 2011 | A1 |
| 20110252071 | Cidon | Oct 2011 | A1 |
| 20110270833 | von Kaenel et al. | Nov 2011 | A1 |
| 20110306326 | Reed et al. | Dec 2011 | A1 |
| 20120150818 | Vijayan Retnamma et al. | Jun 2012 | A1 |
| 20120150826 | Vijayan Retnamma et al. | Jun 2012 | A1 |
| 20120185657 | Gokhale et al. | Jul 2012 | A1 |
| 20120191930 | Brown | Jul 2012 | A1 |
| 20120240183 | Sinha | Sep 2012 | A1 |
| 20120254119 | Kumarasamy et al. | Oct 2012 | A1 |
| 20130054533 | Hao et al. | Feb 2013 | A1 |
| 20130238572 | Prahlad et al. | Sep 2013 | A1 |
| 20130275380 | Gokhale et al. | Oct 2013 | A1 |
| 20130318207 | Dotter | Nov 2013 | A1 |
| 20140046904 | Kumarasamy | Feb 2014 | A1 |
| 20140122435 | Chavda et al. | May 2014 | A1 |
| 20150012495 | Prahlad et al. | Jan 2015 | A1 |
| 20150269035 | Vijayan | Sep 2015 | A1 |
| 20160100007 | Prahlad et al. | Apr 2016 | A1 |
| 20160147472 | Littlefield et al. | May 2016 | A1 |
| 20160292040 | Kumarasamy | Oct 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 0259912 | Mar 1988 | EP |
| 0405926 | Jan 1991 | EP |
| 0467546 | Jan 1992 | EP |
| 0620553 | Oct 1994 | EP |
| 0757317 | Feb 1997 | EP |
| 0774715 | May 1997 | EP |
| 0809184 | Nov 1997 | EP |
| 0899662 | Mar 1999 | EP |
| 0981090 | Feb 2000 | EP |
| 7254204 | Oct 1995 | JP |
| 9044381 | Feb 1997 | JP |
| 9081424 | Mar 1997 | JP |
| WO-9513580 | May 1995 | WO |
| WO-9912098 | Mar 1999 | WO |
| WO-2005024573 | Mar 2005 | WO |
| WO-2008154448 | Dec 2008 | WO |
| Entry |
|---|
| About Backupify [retrieved on Aug. 1, 2014], Retrieved from internet: http://web.archive.org/web/20120122064518/https://www.backupify.com/about; published on Jan. 22, 2012 as per Wayback Machine. |
| Allen, “Probability, Statistics and Queuing Theory,” (1978), p. 370, col. 19, Lines 3-33, 2 pages. |
| Armstead et al., “Implementation of a Campwide Distributed Mass Storage Service: The Dream vs. Reality,” IEEE, Sep. 11-14, 1995, pp. 190-199. |
| Arneson, “Mass Storage Archiving in Network Environments,” Digest of Papers, Ninth IEEE Symposium on Mass Storage Systems, Oct. 31, 1988-Nov. 3, 1988, pp. 45-50, Monterey, CA. |
| Ashton et al., “Two Decades of policy-based storage management for the IBM mainframe computer”, www.research.ibm.com, published Apr. 10, 2003, printed Jan. 3, 2009, 19 pages. |
| Backup your social media content with MyCube Vault [retrieved on Oct. 30, 2014] Retrieved from internet; http://web.archive.org/web/20110606160223/http://www.kullin.net/2010/11/backup-your-social-media-content-with-mycube-vault/; published on Jun. 6, 2011 as per Wayback Machine. |
| Cabrera et al., “ADSM: A Multi-Platform, Scalable, Backup and Archive Mass Storage System,” Digest of Papers, Compcon '95, Proceedings of the 40th IEEE Computer Society International Conference, Mar. 5, 1995-Mar. 9, 1995, pp. 420-427, San Francisco, CA. |
| Campbell, C.: “Linux and Windows NT 4.0: Basic Administration—Part III” Internet Publication, [Online] Oct. 5, 2000, Retrieved from the Internet: URL: <http://linux.omnipotent.net/article.php?article_id=10933> [retrieved on Aug. 22, 2006], 6 pages. |
| Carrington, D.: “Backups Using the ”at“ Command”, Internet Publication, [Online] May 4, 1999, Retrieved from the Internet: URL: <http://groups.google.de/group/microsoft.public.windowsnt.misc/browse_thread/thread/d1406a9a8391afea/48bac300a0adcc7a?Ink=st&q=&rnum=12&h1=de#48bac300a0adcc7a> [retrieved on Aug. 22, 2006], 1 page. |
| Cook, P.: “ntbackup: eject tape at end of backup?” Internet Publication, [Online] Oct. 18, 2000, Retrieved from the Internet: URL: <http://groups.google.de/group/microsoft.public.windowsnt.misc/browse_thread/thread/8f67f0cc96df42b7/0ab1d93a6f91b511?Ink=st&q=%22ntbackup+eject%22+at&rnum=1&h1=de#0ab1d93a6f91b511> [retrieved on Aug. 22, 2006], 1 page. |
| Eitel, “Backup and Storage Management in Distributed Heterogeneous Environments,” IEEE, Jun. 12-16, 1994, pp. 124-126. |
| Extended European Search Report in European Application No. 13767340.6, dated Aug. 19, 2015, 7 pages. |
| Gait, J., “The Optical File Cabinet: A Random-Access File System for Write-Once Optical Disks,” IEEE Computer, vol. 21, No. 6, pp. 11-22 (Jun. 1988). |
| Gonzalez-Seco, Jose, “A Genetic Algorithm as the Learning Procedure for Neural Networks,” International Joint Conference on Neural Networks, Jun. 1992, 356 pages. |
| International Search Report and Written Opinion for International Application No. PCT/US2013/029393; dated Jun. 27, 2013; 10 pages. |
| Jander, M., “Launching Storage-Area Net,” Data Communications, US, McGraw Hill, NY, vol. 27, No. 4 (Mar. 21, 1998), pp. 64-72. |
| MDM: “Automatically eject tape”, Internet Publication, [Online] Jun. 7, 1999, Retrieved from Internet: URL: <http://groups.google.de/group/microsoft.public.windowsnt.misc/browse_thread/thread/66537271a88cebda/2f8b1b96dfc5f102?Ink=st&q=&rnum=11&h1=de#2f8b1b96dfc5f102> [retrieved on Jun. 22, 2006], 1 page. |
| PageFreezer Website Archiving & Social Media Archiving [retrieved on Aug. 1, 2014], Retrieved from internet: http://webarchive.org/web/20120303012345/http://pagefreezer.com/blog; published on Mar. 3, 2012 as per Wayback Machine. |
| Recycle Bin (Windows), Aug. 2007, Wikipedia, pp. 1-3. |
| Rosenblum et al., “The Design and Implementation of a Log-Structured File System,” Operating Systems Review SIGOPS, vol. 25, No. 5, New York, US, pp. 1-15 (May 1991). |
| Savill, J., “Windows NT FAQ Single File Version—Section Backup's” Internet Publication, [Online] 2000, Retrieved from Internet: URL: <http://burks.bton.ac.uk/burks/pcinfo/osdocs/ntfaq/ntfaq_09.htm> [retrieved on Aug. 22, 2006], 8 pages. |
| Supplementary European Search Report in European Application No. 13767340.6, dated Sep. 4, 2015, 1 page. |
| U.S. Appl. No. 14/843,075 for Kochunni et al., filed Sep. 2, 2015. |
| Examination Report in European Patent Application No. 13767340.6, dated Mar. 23, 2018, 5 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170091294 A1 | Mar 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61618506 | Mar 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13787280 | Mar 2013 | US |
| Child | 15377299 | US |
