Abstract: Implementations are described of a computing device that migrates data and software applications from a first computing device to a second computing device, in order to preserve data and other application-related customizations.

Abstract: Implementations are described of a computing device that migrates data and software applications from a first computing device to a second computing device, in order to preserve data and other application-related customizations.

Abstract: Implementations are described of a computing device that migrates data and software applications from a first computing device to a second computing device, in order to preserve data and other application-related customizations.

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: Implementations are described of a computing device that migrates data and software applications from a first computing device to a second computing device, in order to preserve data and other application-related customizations.

Abstract: Implementations are described of a computing device that migrates data and software applications from a first computing device to a second computing device, in order to preserve data and other application-related customizations.

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: Implementations are described of a computing device that migrates data and software applications from a first computing device to a second computing device, in order to preserve data and other application-related customizations.

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, providing retrieval capabilities (e.g., search, etc.), and so forth. 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 (backup).

Abstract: Techniques for providing content management services are described. Managing content services includes determining a value of content and determining storage actions of the content based on the value. The value of the content is determined by weighting factors, such as access frequency, a rating, a size of the content, a type of the content, and a security level of the content. Based on the value of the content, one or more storage actions may be determined for the content to optimize storage. The storage actions may include identifying a version of the content to be saved, compressing the content, determining a back up of the content to store, identifying a location to store the content, performing erasure encoding of the content, and/or removing the content.