In some examples, a system may include a processing resource and a memory resource. The memory resource may store machine-readable instructions to cause the processing resource to create a migration plan, defining characteristics of a migration of an application from a native computing data center to a computing cloud of a plurality of distinct candidate computing clouds, based on: a first migration constraint for the application determined from an analysis of historical behavior of the application executed on the native computing data center; a second migration constraint for the application determined from an analysis of administrator cloud migration preferences for the application; and a cloud computing characteristic of each of the plurality of distinct candidate computing clouds.

In some examples, a system may include a processing resource and a memory resource. The memory resource may store machine-readable instructions to cause the processing resource to create a migration plan, defining characteristics of a migration of an application from a native computing data center to a computing cloud of a plurality of distinct candidate computing clouds, based on: a first migration constraint for the application determined from an analysis of historical behavior of the application executed on the native computing data center; a second migration constraint for the application determined from an analysis of administrator cloud migration preferences for the application; and a cloud computing characteristic of each of the plurality of distinct candidate computing clouds.

In general, embodiments of the invention relate to storing data and managing the stored data in linked nodes. More specifically, embodiments of the invention relate to nodes linked together in a daisy chain configuration such as, but not limited to, a single-chain configuration and a dual-chain configuration, which use data protection domain (DPD) information to determine where and/or how to store the data.

A cloud-based content object management system responds to download requests from user devices to provide access to synchronization code. Using the synchronization code, a user device requests, receives, and stores a user-device-local copy of a subject content object. The cloud-based content object management system determines that at least one security-related parameter pertaining to the subject content object has undergone a change and reaches a determination that the user-device-local copy of the subject content object is to be either deleted or quarantined. Upon such determination, the cloud-based content object management system forms eviction instructions and sends them to the user device, which in turn causes deletion or quarantining of the remote content object copy at the user device, while still retaining directory structure metadata that refers to the now evicted subject content object. The subject content object stored at the cloud-based content object management system is synchronized with other user devices.

A cloud-based content object management system responds to download requests from user devices to provide access to synchronization code. Using the synchronization code, a user device requests, receives, and stores a user-device-local copy of a subject content object. The cloud-based content object management system determines that at least one security-related parameter pertaining to the subject content object has undergone a change and reaches a determination that the user-device-local copy of the subject content object is to be either deleted or quarantined. Upon such determination, the cloud-based content object management system forms eviction instructions and sends them to the user device, which in turn causes deletion or quarantining of the remote content object copy at the user device, while still retaining directory structure metadata that refers to the now evicted subject content object. The subject content object stored at the cloud-based content object management system is synchronized with other user devices.

Cascading payload replication to target compute nodes is disclosed. Cascading payload replication can be accomplished using a two-stage operation for a replication operation. In the first stage, a plan is generated and distributed for the replication operation. The plan includes an assignment of compute nodes to tree nodes in a tree hierarchy. In the second phase, the payload is distributed according to the plan. The plan is different for at least two replication operations. Thus, the cascading payload replication is adaptable to changing target compute nodes and provides for load balancing.

Cascading payload replication to target compute nodes is disclosed. Cascading payload replication can be accomplished using a two-stage operation for a replication operation. In the first stage, a plan is generated and distributed for the replication operation. The plan includes an assignment of compute nodes to tree nodes in a tree hierarchy. In the second phase, the payload is distributed according to the plan. The plan is different for at least two replication operations. Thus, the cascading payload replication is adaptable to changing target compute nodes and provides for load balancing.

Various embodiments of apparatuses and methods for transaction processing at edge servers in a content distribution network (“CDN”) are described. In some embodiments, an edge server receives an initial request from a client for content associated with a particular origin, and then provides the content to the client. The edge server can then receive another request from the client that might include an indicator for transaction processing. The edge server determines that transaction processing is indicated for handling this new request, in some embodiments. The edge server can then send a transaction notification to the origin, receive a transaction continuation response from the origin, and then execute a data transaction with transaction entities that are distinct from the content distribution network and the origin, in some embodiments. If the transaction is successful, the edge server can notify the client and the origin of the successful transaction, in some embodiments.

In some examples, a system comprises a memory device for storing instructions and a processor which executes instructions causing the system to perform operations comprising receiving an instruction to transfer a state of a first device to a second device, and packaging information relating to the state of the first device in a file. The packaging of the information relating to the state of the first device includes recording each application executing on the first device in a list maintained in the file, and transferring the file containing information relating to the state of the first device to the second device, either directly or indirectly based on an availability of connections between the first device and the second device. The file, when processed by the second device, causes the second device to reproduce the state of the first device. In some example, reproducing the state of the first device includes the second device downloading, from one or more of the locations, one or more of the applications.

An illustrative storage management appliance is interposed between client computing devices and one or more cloud storage resources. The appliance uses cloud storage resources in conjunction with a network attached storage device configured within the appliance to provide to the client computing devices seemingly unlimited network attached storage on respective network shares. The storage management appliance monitors data objects on the network shares and when a data object meets one or more criteria for archiving, the storage management appliance archives the data object to a cloud storage resource and replaces it with a stub and preview image on the network share. When access to the stub and/or preview image is detected, the storage management appliance restores the data object from the cloud storage resource. The criteria for archiving flexibly allow individual data objects to be archived to cloud storage without archiving frequently-accessed “neighboring” data objects on the same network share.