Abstract: The present disclosure relates to methods and systems for protecting cloud resources. The methods and systems may use a virtual gatekeeper resource to enforce secure access controls to cloud resources for a list of privileged operations. The cloud resources and the virtual gatekeeper resource may be in different security domains within a cloud computing system and the cloud resources may be linked to the virtual gatekeeper resource. A request may be sent to perform a privileged operation on the cloud resource. Access may be provided to the virtual gatekeeper resource in response to approval of the request and the access to the virtual gatekeeper resource may be used to perform the privileged operation on the cloud resource.

Abstract: The present disclosure relates to methods and systems for protecting cloud resources. The methods and systems may use a virtual gatekeeper resource to enforce secure access controls to cloud resources for a list of privileged operations. The cloud resources and the virtual gatekeeper resource may be in different security domains within a cloud computing system and the cloud resources may be linked to the virtual gatekeeper resource. A request may be sent to perform a privileged operation on the cloud resource. Access may be provided to the virtual gatekeeper resource in response to approval of the request and the access to the virtual gatekeeper resource may be used to perform the privileged operation on the cloud resource.

Abstract: Techniques for initializing a replication relationship between virtual machines are described herein. The techniques include performing one or more pre-requisite checks, determining, at least partly in response to performing the one or more pre-requisite checks, one or more first data blocks associated with a first virtual machine that differ from one or more second data blocks associated with a second virtual machine. The second virtual machine may be instructed to send the one or more second data blocks that differ from the one or more first data blocks to the first virtual machine.

Abstract: Data consistency between a primary virtual machine and a recovery virtual machine may employ a resync engine to detect differences in data blocks stored on both virtual machines. For example, the resync engine may calculate a signature (e.g., hash value) for a primary data block and a corresponding signature for a recovery data block, and compare the signature and the corresponding signature to identify a difference between the primary data block and the recovery data block. In some instances, by identifying a difference between the primary data block and the recovery data block, a data block (e.g., primary data block or recovery data block) may be identified to be transferred from a virtual machine to another virtual machine.

Abstract: Data consistency between a primary virtual machine and a recovery virtual machine may employ a resync engine to detect differences in data blocks stored on both virtual machines. For example, the resync engine may calculate a signature (e.g., hash value) for a primary data block and a corresponding signature for a recovery data block, and compare the signature and the corresponding signature to identify a difference between the primary data block and the recovery data block. In some instances, by identifying a difference between the primary data block and the recovery data block, a data block (e.g., primary data block or recovery data block) may be identified to be transferred from a virtual machine to another virtual machine.

Abstract: Techniques for initializing a replication relationship between virtual machines are described herein. The techniques include performing one or more pre-requisite checks, determining, at least partly in response to performing the one or more pre-requisite checks, one or more first data blocks associated with a first virtual machine that differ from one or more second data blocks associated with a second virtual machine. The second virtual machine may be instructed to send the one or more second data blocks that differ from the one or more first data blocks to the first virtual machine.

Abstract: A synchronization framework is provided for synchronizing data groups between a server and clients that may go off-line. The framework includes a client sync provider component that interfaces to client storage in a storage format independent way, a sync agent component that collects synchronization metadata maintained by the clients and uploads and/or downloads changes to the data groups to and/or from server storage and a server sync provider component that interfaces via sync adapters to server storage independently of storage format. The framework provides default building blocks for building off-line synchronizing applications that behave according to default application synchronization scenarios, and also enables custom building blocks for custom off-line application synchronization scenarios.

Abstract: A synchronization framework is provided for synchronizing data groups between a server and clients that may go off-line. The framework includes a client sync provider component that interfaces to client storage in a storage format independent way, a sync agent component that collects synchronization metadata maintained by the clients and uploads and/or downloads changes to the data groups to and/or from server storage and a server sync provider component that interfaces via sync adapters to server storage independently of storage format. The framework provides default building blocks for building off-line synchronizing applications that behave according to default application synchronization scenarios, and also enables custom building blocks for custom off-line application synchronization scenarios.