Abstract: An archive of items, which are computing data accessed by a user, is created at a semantic object level. The object archiving may group seemingly disparate items as a composite object, which may then be stored to enable retrieval by the user at a later point in time. The composite object may include metadata from the various items to enable identifying the composite object and providing retrieval capabilities. In some aspects, an archiving process may extract item data from an item that is accessed by a computing device. Next, the item may be selected by a schema for inclusion in a composite object when the item data meets criteria specified in the schema. The composite object(s) may then be stored in an object store as an archive.

Abstract: A backup system that utilizes contextual and semantic concepts is described. The backup system provides for the ability to create a version changes log for listing and tracking all the changes in the different versions of the file. The version changes log creates a contextual description around the changes, deletions and additions. The semantic concept log is created from the version changes log to create a log of all of the semantic concepts associated with each change. A visualization builder then creates visualizations that can be used by the user to search for changes, deletions and additions whether in a text file or an image file.

Abstract: The claimed subject matter provides a system and/or a method that facilitates seamless integration of a data storage service within an operating system (OS). An online safe deposit box can store a portion of data, wherein the online safe deposit box is hosted by a data storage service provider. A local operating system associated with a device can leverage a graphic user interface (GUI) to interact with a portion of data associated with the device. A map component can create a mapped drive that integrates the online safe deposit box within the local operating system to enable seamless data interaction between the local operating system and the online safe deposit box, wherein the data interaction is at least one of a data upload from the local operating system to the online safe deposit box or a data download from the online safe deposit box to the local operating system.

Abstract: The claimed subject matter provides a system and/or a method that facilitates integration of a distributed backup environment and a online backup environment. A super peer device can be designated from a set of peer devices. The super peer can distribute backup data amongst the set of peer devices based upon availability and storage capacity of the peer devices. In addition, the super peer can transfer portions of backup data from the set of peers to an online backup service.

Abstract: Automated file distribution is described. A member of a peer-to-peer network receives from a file server, a file to be distributed. The file is then distributed via the peer-to-peer network to other members of the peer-to-peer network. Members of the peer-to-peer network can choose whether or not to receive a file from another member based on a trust level or reputation associated with the member. The trust level may be based, at least in part, on a number of degrees of separation between the members. Furthermore the file is verified, for example, by validating a digital signature associated with the file.

Abstract: The claimed subject matter provides a system and/or a method that facilitates employing a safe deposit box that allows perpetual archiving of data. An online safe deposit box can store a portion of data, wherein the online safe deposit box is hosted by a data storage service provider. An archival model component can implement the online safe deposit box for perpetual archival of the portion of data. The archival model component can ensure at least one of the following: the online safe deposit retains the portion of data for a pre-defined duration; the portion of data within the online safe deposit box is accessible solely by an authorized entity; or the integrity of the portion of data is maintained, wherein the integrity is modified solely by an authorized user.

Abstract: The claimed subject matter provides a system and/or a method that facilitates distributed backup and versioning techniques for network-based backup architectures. When data is committed to a backup system, a backup version can be created. The generated backup version can be a complete rendition of data or the generated backup version can be a differential between the data and backup information previously committed to the system. The generated backup version can be replicated across a distributed network of peers. Replication can be based upon a desire level of redundancy of versions, location of peers, network topology of peers, storage capacity of peers, health of peers, type of peer, and the like. In addition, versions can be retained based upon a configurable number of desired versions.

Abstract: The claimed subject matter relates to systems and/or methodologies that facilitate intelligent distribution of backup information across storage locations in network-based backup architectures. A virtual layering of backup information across storage locations in the backup architecture can be implemented. Statistical models are utilized to dynamically re-allocate backup information among storage locations and/or layers to ensure availability of data, minimum latency upon restore, and minimum bandwidth utilization upon restore. In addition, heuristics or machine learning techniques can be applied to proactively detect failures or other changes in storage locations such that backup information can be reallocated accordingly prior to a failure.

Abstract: The claimed subject matter relates to systems and/or methodologies that facilitate distributed storage of data. A distributed file system can be implemented on storage nodes such that the system places multiple copies of data (e.g., replicas) on a variety of disparate storage nodes to guarantee availability of the data and minimize loss of the data. Storage nodes are dynamically evaluated to identify respective characteristics. In one example, the characteristics can include availability of a storage node, capacity of a storage node, data storage cost associated with a storage node, data transfer costs associated with a storage node, locality of a storage node, network topology, or user preferences associated with a storage node. The characteristics can be employed to generate optimal placements decisions.

Abstract: Techniques are disclosed for identifying and stashing all or portions of application data to a network accessible storage device or location. Identifying and stashing are accomplished in a fashion that is transparent to a user such that a user is not burdened by the process of managing and stashing a full or partial set of application data. The system, the application, or a combination of system components and the application persist and manage data locally and stash portions of the local data to one or more network accessible storage devices or locations. One or more links are provided in place of the stashed portions of data. The application uses the links in a same or similar fashion as handling local data while providing little to no loss of functionality due to all or portions of the local data being stashed.

Abstract: Techniques are disclosed for identifying and stashing all or portions of application data to a network accessible storage device or location. Identifying and stashing are accomplished in a fashion that is transparent to a user such that a user is not burdened by the process of managing and stashing a full or partial set of application data. The system, the application, or a combination of system components and the application persist and manage data locally and stash portions of the local data to one or more network accessible storage devices or locations. One or more links are provided in place of the stashed portions of data. The application uses the links in a same or similar fashion as handling local data while providing little to no loss of functionality due to all or portions of the local data being stashed.

Abstract: Techniques are disclosed for identifying and stashing all or portions of application data to a network accessible storage device or location. Identifying and stashing are accomplished in a fashion that is transparent to a user such that a user is not burdened by the process of managing and stashing a full or partial set of application data. The system, the application, or a combination of system components and the application persist and manage data locally and stash portions of the local data to one or more network accessible storage devices or locations. One or more links are provided in place of the stashed portions of data. The application uses the links in a same or similar fashion as handling local data while providing little to no loss of functionality due to all or portions of the local data being stashed.

Abstract: Automated file distribution is described. A member of a peer-to-peer network receives from a file server, a file to be distributed. The file is then distributed via the peer-to-peer network to other members of the peer-to-peer network. Members of the peer-to-peer network can choose whether or not to receive a file from another member based on a trust level or reputation associated with the member. The trust level may be based, at least in part, on a number of degrees of separation between the members. Furthermore the file is verified, for example, by validating a digital signature associated with the file.

Abstract: Automated file distribution is described. A member of a peer-to-peer network receives from a file server, a file to be distributed. The file is then distributed via the peer-to-peer network to other members of the peer-to-peer network. Members of the peer-to-peer network can choose whether or not to receive a file from another member based on a trust level or reputation associated with the member. The trust level may be based, at least in part, on a number of degrees of separation between the members. Furthermore the file is verified, for example, by validating a digital signature associated with the file.

Abstract: A predictive failure model is used to generate a failure prediction associated with a node. A repair or backup action may also be determined to perform on the node based on the failure prediction.

Abstract: A method and system for determining the reputation of a sender for sending desirable communications is provided. The reputation system identifies senders of communications by keys sent along with the communications. The reputation system then may process a communication to determine whether it is a desirable communication. The reputation system then establishes a reputation for the sender of the communication based on the assessment of whether that communication and other communications sent by that sender are desirable. Once the reputation of a sender is established, the reputation system can discard communications from senders with undesired reputations, provide to the recipient communications from senders with desired reputations, and place in a suspect folder communications from senders with an unknown reputation.

Abstract: A backup system that utilizes contextual and semantic concepts is described. The backup system provides for the ability to create a version changes log for listing and tracking all the changes in the different versions of the file. The version changes log creates a contextual description around the changes, deletions and additions. The semantic concept log is created from the version changes log to create a log of all of the semantic concepts associated with each change. A visualization builder then creates visualizations that can be used by the user to search for changes, deletions and additions whether in a text file or an image file.

Abstract: Techniques are disclosed for identifying and stashing all or portions of application data to a network accessible storage device or location. Identifying and stashing are accomplished in a fashion that is transparent to a user such that a user is not burdened by the process of managing and stashing a full or partial set of application data. The system, the application, or a combination of system components and the application persist and manage data locally and stash portions of the local data to one or more network accessible storage devices or locations. One or more links are provided in place of the stashed portions of data. The application uses the links in a same or similar fashion as handling local data while providing little to no loss of functionality due to all or portions of the local data being stashed.

Abstract: The claimed subject matter provides a system and/or a method that facilitates generation of islands of data in distributed storage environments such as network-based backup architectures. A partition component can assign a policy to a portion of data within a distributed storage environment to generate an island of data that includes at least the portion of data. In addition, an enforcement component can manages the island of data in accordance with the policy. For instance, the enforcement component can control at least one of access to the island of the data, distribution of the island of data, or deletion of the island of data.

Abstract: The claimed subject matter provides a system and/or a method that facilitates differential transfer and storage of data for network-based backup architectures. A differential compression component can segment a portion of backup information into one or more blocks. In addition, signatures can be generated for each of the one or more blocks. The differential compression component can identify unique blocks from the one or more blocks based upon the generated signatures and signatures of chunks stored in a distributed chunk store. Moreover, a storage component can transfer the unique blocks of the portion of backup information to the distributed chunk store once identified.