One example method includes chunking a respective disk of each of a plurality of virtual machines (VM) to create a respective plurality of chunks associated with each of the VMs, creating, based on the chunking process, a cluster comprising one or more of the VMs, creating a VM template whose data and disk structure match respective data and disk structures of each of the VMs in the cluster, and in response to a file operation involving a first one of the VM disks, defragmenting the first VM disk so that a disk structure of the first VM disk is the same as a disk structure of the VM template.

Methods and systems of applying retroactive adjustments to financial data. An example method includes: receiving one or more adjustment records associated with a financial account; saving a snapshot of the financial account, the snapshot comprising a plurality of transaction records reflecting previously processed transactions associated with the financial account; merging the adjustment records and the transaction records to produce a plurality of adjusted transaction records; processing adjusted transaction records to produce an updated state of the financial account; comparing the saved snapshot to the updated state of the financial account to produce one or more adjustment events; and processing the adjustment events using one or more event processing rules.

The present disclosure provides a cleaning and recovery method and device for a heterogeneous executor in a mimic switch, and a mimic switch, the method includes: a mimic scheduler determining a designated heterogeneous executor that needs to be cleaned, marking the designated heterogeneous executor that needs to be cleaned as in a cleaning state, and sending a cleaning instruction to the designated heterogeneous executor; the designated heterogeneous executor sending a normal protocol negotiation message to the mimic scheduler to try to interact with the mimic scheduler; the mimic scheduler receiving the protocol negotiation message and detecting whether the designated heterogeneous executor is in the cleaning state; if in the cleaning state, the mimic scheduler; constructing a training message, and sending the training message to the designated heterogeneous executor for protocol training; repeating sending and processing the protocol negotiation message until the designated heterogeneous executor is in a normal state.

A secure element device that is configured to be cryptographically bound to a host device includes a secure element host key slot configured to store host key information that allows only the host device to control the secure element, a secure memory storing binding information, and limited functionality allowing the binding information to be read from the secure memory by the host device during a binding process. The binding information is cryptographically correlated with the host key information. The host key information is generated by the host device using the binding information read from the secure element and a secret key. The secure element device further includes general functionality only accessible to the host device using the host key information that is generated by the host device. The secure memory includes prevention measures impeding unauthorized entities from obtaining information from the secure memory.

A distributed database system, a data disaster backup exercise method and a non-transitory computer-readable storage medium are disclosed. The distributed database system may include a local computer room (110) and an offsite computer room (120), where the local computer room (110) includes a local management node (111) and a local database cluster (112), the offsite computer room (120) includes an offsite management node (121), an offsite exercise database cluster (123) and an offsite synchronization database cluster (122); where the local database cluster (112) and the offsite synchronization database cluster (122) are both connected with the local management node (111); the offsite exercise database cluster (123) is configured for: establishing a first connection with the offsite management node (121); and receiving a test service sent by a service layer.

Disclosed are techniques for coordinating distributed backup data protection sites for alternating recording of point in time copies. For a monitored volume, or pool of monitored volumes, periodic point in time copies are recorded upon data storage capabilities of rotating backup data storage sites as each period elapses. Upon recording a point in time copy at a given backup data storage site, the given site broadcasts to other sites metadata about the point in time copies recorded by each of the backup data storage sites for the monitored volume. As subsequent periods elapse, a rotation of sites are cycled through for selection to record point in time copies for the given period such that point in time copies of the monitored volume are recorded across multiple backup data storage sites, with each backup data storage site recording point in time copies of the monitored volume snapshotted to different times.

Replication of a filesystem or a mount point or share may replicate all data that it consists of irrespective of where the data is stored. Replication protects data irrespective of location. One method is to replicate the filesystem namespace as is while skipping the data outside of the appliance/machine so that replication cost and time are reasonable. The data outside of the machine, like cloud/tape data is protected differently. One example method includes a data protection operation configured to replication a namespace associated with multiple data tiers. During replication, data from one of the tiers is skipped while all of the namespace metadata is replicated. The recovery restores the namespace metadata and the data that was replicated from the other tier. This may be performed in connection with cyber security, for example when replicating multi-tier data to a vault.

The disclosed embodiments disclose techniques for journaling data received in a cloud-based distributed computing environment (CBDCE). Multiple services simultaneously execute on the CBDCE compute nodes, with each service comprising multiple service instances that simultaneously execute on multiple, distinct compute nodes of the CBDCE. The CBDCE includes a distributed database that enables coordination between the service instances of services that execute in the CBDCE; this distributed database also includes multiple distributed database instances that simultaneously executing on multiple different CBDCE compute nodes. During operation, a service instance executing on one of these compute nodes receives a client request. The service instance submits this client request to a distributed database instance and, in parallel, also submits the client request and its associated user data to a distributed journaling service.

An illustrative method includes accessing, by a controller operating within a global control plane, a recovery policy that specifies parameters for generating recovery data associated with one or more resources of a first cluster comprising a first one or more containers, wherein the first cluster comprises a first local control plane separate from the global control plane; determining, by the controller and based on the recovery policy, a second cluster comprising a second one or more containers, wherein the second cluster comprises a second local control plane separate from the global control plane; and generating, by the controller and with respect to the second cluster, the recovery data associated with the one or more resources of the first cluster.

Techniques described herein relate to systems and methods of data storage, and more particularly to providing layering of file system functionality on an object interface. In certain embodiments, file system functionality may be layered on cloud object interfaces to provide cloud-based storage while allowing for functionality expected from a legacy applications. For instance, POSIX interfaces and semantics may be layered on cloud-based storage, while providing access to data in a manner consistent with file-based access with data organization in name hierarchies. Various embodiments also may provide for memory mapping of data so that memory map changes are reflected in persistent storage while ensuring consistency between memory map changes and writes. For example, by transforming a ZFS file system disk-based storage into ZFS cloud-based storage, the ZFS file system gains the elastic nature of cloud storage.