Abstract: A data processing system archives local snapshots of a primary storage object to cloud storage by dividing an address space of the snapshots into sequential chunks, and organizing the cloud storage into archived snapshots including sets of cloud objects created from respective modified chunks of local snapshots. The archived snapshots are organized into families each having a full snapshot and incremental snapshots. A new family is started by creating a synthesized full snapshot from the archived snapshots of a preceding family, which includes (1) for chunks whose data is contained within one cloud object of the preceding family, logically incorporating the cloud object into the synthesized full snapshot, and (2) for chunks whose data is contained within multiple cloud objects of the preceding family, coalescing the data of the cloud objects into a new cloud object and logically incorporating the new cloud object into the synthesized full snapshot.

Abstract: Systems, methods, and computer readable storage mediums for discovering volumes which are good candidates for space reclamation. A storage subsystem identifies the file system storage capacity for a given volume from the file system metadata of the given volume. Then, the storage subsystem compares the file system capacity of the given volume to the allocated capacity on the storage subsystem. If the allocated capacity is greater than the file system capacity by a given threshold, the storage subsystem marks the given volume as a candidate for space reclamation and generates an alert to the user to reclaim the space of the given volume.

Abstract: A system for transmission of memory entries. The system includes a computing device that includes a memory module, a memory controller interfacing with the memory module via a memory bus, a snooping module interfacing with the memory bus, functionally in parallel to the memory module, and a high-speed interconnect, functionally connecting the snooping module to a receiving device. The memory controller is configured to write a memory entry to the memory module via the memory bus. The snooping module is configured to capture a copy of the memory entry being written to the memory module and to send the copy of the memory entry to the receiving device, via the high-speed interconnect.

Abstract: Embodiments of the present invention relate to a snapshot generating method, computer system, and apparatus, which can determine a plurality of virtual machines where an application runs and a deployment server where the plurality of virtual machines is deployed, and send a snapshot instruction to the deployment server of the plurality of virtual machines, so that the deployment server of the plurality of virtual machines can start snapshot operations on the plurality of virtual machines at consistent time points according to the snapshot instruction, so as to generate snapshot files of the plurality of virtual machines at the consistent time points, thereby implementing unified snapshots on the plurality of virtual machines where the application runs and ensuring consistency among backup data of the application.

Abstract: A method is disclosed for avoiding out-of-space conditions in an asynchronous data replication environment. In one embodiment, such a method creates a consistency group on a primary storage system of an asynchronous data replication environment. The method determines a number of additional extents that will be needed on a secondary storage system to accommodate the consistency group. The number of additional extents is compared to a number of free extents on the secondary storage system. In the event the number of additional extents does not exceed the number of free extents, the method transfers the data from the primary storage system to the secondary storage system. In the event the number of additional extents exceeds the number of free extents, the method automatically takes actions on the secondary storage system to provide the number of additional extents. A corresponding system and computer program product are also disclosed.

Abstract: A computer program product, system, and method for determining containers, within a secondary storage, to transform; determining users having access to the containers to transform; synchronizing storage configuration between the secondary storage and a primary storage; enumerating objects within the containers to transform; and adding object identifiers and object metadata for the enumerated objects to an object index within the primary storage.

Abstract: One example method includes identifying a data block as being in a corrupted state, and calculating a value of a identifier corresponding to the data block, where the value of the identifier is based on contents of the data block. The value of the identifier is then compared with a value of another identifier that is part of a stored access record for the data block. Based on results of the comparison, the virtual machine is either identified as the cause of corruption of the data block, or the virtual machine is eliminated as being the cause of the corruption of the data block.

Abstract: An objective of the present disclosure is to provide a method and apparatus for scheduling resources in a cloud system. The method according to the present disclosure comprises steps of: determining, according to stability of computing resources in the cloud system, respective resource priority levels of the respective computing resources; determining a scheduling algorithm corresponding to a current job when it is needed to schedule the resources; and allocating the resources based on the scheduling algorithm and resource priority levels of currently available respective computing resources. Compared with the prior art, the present disclosure has the following advantages: by differentiating the priorities of the computing resources and supporting a plurality of scheduling algorithms, resource scheduling is performed based on a variety of scheduling algorithms and resource priorities, which enhances the flexibility of resource scheduling and enhances the resource utilization and system throughput.

Abstract: Embodiments of the present disclosure provide a method, device and computer program product for validating a cache file. In an embodiment, a reference cache file associated with the backed up data is divided into a plurality of reference segments. Reference check information is generated for the respective reference segments of the plurality of reference segments, and the generated reference check information is stored. In response to the initiating of a backup job, the stored reference check information is used to validate the cache file.

Abstract: In one aspect, providing recovery during active/active replication includes: creating, at a first storage device, a local snapset; waiting for inflight (input/output) IO operations (IOs) from the first device to a second device at the time snapset creation to complete; creating a recovery snapset; and waiting for inflight IOs from the second device to the first device, at the time of snapset creation to complete. Upon determining a failure event, an aspect includes identifying a most recent local snapset (Sk) and a most recent recovery snapset (Sk?) on the first and second devices, respectively, identifying predecessor snapsets (Sk?1) and (Sk?1?) on the first and second devices, respectively, creating a new recovery snapset (Sk?) using (Sk?1?), sending the delta of (Sk) and (Sk?1) from the first device to the second device; updating (Sk?) with the delta; and performing async-to-sync recovery to transfer a difference between the first and second devices.

Abstract: Methods, storage facilities and computer software products implement embodiments of the present invention that include partitioning a software stack (140) into a first software component (141), a second software component (142) and a third software component (143) managed respectively by a primary host (26) at a primary site (22), by a secure storage unit (30) at or adjacent to the primary site, the secure storage unit including a protection storage unit (92) and a disaster-proof storage unit (94), and by a recovery system (34) at a secondary site (24). One or more files (90) are stored in the disaster-proof unit using the first and the second software components, and following a disaster occurring at the primary site, the files are recovered using the secure storage unit and the recovery system.

Abstract: Generating secondary virtual machine seed image storage is provided. An input is received to deploy a primary virtual machine and a secondary virtual machine based on a golden virtual machine image. In response, the primary virtual machine from the golden virtual machine image on a primary data processing site and the secondary virtual machine from the golden virtual machine image on a secondary data processing site are deployed. Execution of the secondary virtual machine is suspended on the secondary data processing site. Using the golden virtual machine image, a seed image corresponding to the secondary virtual machine is generated that is up-to-date at that point in time in storage at the secondary data processing site to form the secondary virtual machine seed image storage. The secondary virtual machine seed image storage is enabled to receive state data updates from the primary virtual machine on the primary data processing site.

Abstract: Cassandra SSTable data is transformed to provide data rows that are a consistent size such that data in each row has a length that is contained within a selected fixed sized kilobyte segment for deduplication. Tables of a Cassandra cluster node are translated in parallel to JSON format using Cassandra SSTableDump and the table rows are parsed to provide data rows corresponding to the data in each table row. Each row of data is padded with a predictable pattern of bits such that the data row has a length corresponding to the selected fixed segment size and has boundary locations that correspond to multiple of the selected segment size. Since each row of data starts on a segment boundary, duplicate rows of data will be identified wherever they move within a table.

Abstract: A storage system includes at least one drive chassis connected to at least one host computer via a first network, and a storage controller connected to the drive chassis, in which the storage controller instructs the drive chassis to create a logical volume, and the drive chassis creates a logical volume according to an instruction from the storage controller, provides a storage area of the storage system to the host computer, and receives an IO command from the host computer to the storage area of the storage system.

Abstract: Various examples are directed to systems and methods for backing up data. A tracking utility may receive a start request and then enter a holding mode until a first modifiable or writable snapshot is created. The tracking utility can track such a first snapshot and determine if any modifications such as writes have been made to the first snapshot. If the first snapshot has not been modified it can be backed up using a read only snapshot scheme. If the first snapshot has been modified, a record of the modifications thereto are used to update the frozen changes and the current changes. The resulting or finalized snapshot is generated and includes all of the modifications, modifications 1 to N made to the first snapshot. This process can be repeated for one or more or all of the modifiable or writable snapshots.

Abstract: Techniques are provided for handling misaligned holes and writes beyond end of files during a quick reconciliation process. During quick reconciliation, a read operation is performed to read data from a first storage object and is replicated to a second storage object. If the data read from the first storage object comprises misaligned holes, then a different range of data is read from the first storage object so that aligned holes are read and replicated to the second storage object. If the read operation targets a region beyond an end of the first storage object, then the second storage object is truncated to a size of the first storage object.

Abstract: A compliance audit log of a data storage is obtained. The compliance audit log is analyzed to identify one or more files associated with a mounted storage volume that have changed since a previous backup snapshot of the mounted storage volume associated with the data storage. An incremental backup snapshot of the mounted storage volume is caused to be performed based on a result of the analysis of the compliance audit log.

Abstract: Various systems and methods to efficiently store backups of partitions of a database are disclosed. An indication to take a current snapshot of a partition of the database is received. A log size and operation type statistics are determined for a portion of the change log for the partition. A snapshot type is determined for the partition based at least in part on the log size and the operation type statistics, where the snapshot type specifies a log-based snapshot or a full snapshot. The snapshot is stored as metadata indicating a point in the change log if the determined snapshot type is log-based snapshot or stored as complete data of the partition if the determined snapshot type is full snapshot.

Abstract: Virtual machine volumes may be migrated between software defined storage (SDS) systems by an orchestration engine configured to manage one or more virtual machines. The orchestration engine may identify one or more volumes associated with the one or more virtual machines and resident in a first SDS system to migrate to a second SDS system, and for each identified volume among the one or more identified volumes, the orchestration engine may create a replacement volume for the identified volume on the second SDS system, map the replacement volume to the associated virtual machine for the identified volume, cause the associated virtual machine to discover the replacement volume, mirror data from the identified volume to the replacement volume, unmap the identified volume from the associated virtual machine, and delete the identified volume from the first SDS system.

Abstract: A storage system comprises a plurality of storage devices and an associated storage controller. The plurality of storage devices are configured to store a plurality of logical units (LUNs) and snapshot data structures associated with the plurality of LUNs. The storage controller is configured to determine a mapping of a logical address associated with a pending read or write operation to a snapshot address associated with a given snapshot data structure of the storage system that comprises a plurality of nodes generated during point-in-time snapshots taken based on at least one of the LUNs, lock at least a portion of the given snapshot data structure during the read or write operation based on the determined mapping, and release the lock on the at least a portion of the given snapshot data structure in response to a completion of the read or write operation.

Abstract: Common data are maintained by a system including a plurality of node devices that each store a respective portion of a common data in a respective database, wherein a node device of the plurality of node devices stores a first portion of the common data, and receives a hash value of a second portion of the common data that is different from the first portion, in response to an update of the second portion of the common data.

Abstract: A distributed, deduplicated storage system according to certain embodiments is arranged in a parallel configuration including multiple deduplication nodes. Deduplicated data is distributed across the deduplication nodes. The deduplication nodes can be networked together and communicate with one another according using a light-weight, customized communication scheme (e.g., a scheme based on FTP or HTTP). In some cases, deduplication management information including deduplication signatures and/or other metadata is stored separately from the deduplicated data in deduplication management nodes, improving performance and scalability.

Abstract: Hypervisor-independent reference copies of virtual machine payload data based on block-level pseudo-mount infrastructure and techniques are generated and stored in an illustrative data storage management system. An illustrative hypervisor-independent reference copy comprises one or more virtual-machine payload data files that originated from a first virtual machine. The hypervisor-independent virtual-machine-payload reference copy is governed by a distinct reference copy policy that controls retention, storage, tiering, scheduling, etc. for the reference copy, independently of how the illustrative system treats other virtual machine payload data files originating from the same virtual machine.

Abstract: A method and system for securing user data, or data, possessed by a data owner, are disclosed. In one aspect data is concealed and encrypted to ensure data confidentiality, and may also be signed to ensure data integrity and authenticity. In another aspect accesses to data are controlled by the data owner through a distributed access control system. In another aspect the public keys of users are distributed automatically in a distributed manner, and are controlled by the users owning the corresponding public and private key pairs.

Abstract: An illustrative ISCSI server computing device provides user computing devices with “private writable snapshots” of a desired volume of data and/or further provides “private writable backup copies.” The ISCSI service is provided without invoking snapshot limits imposed by storage arrays and further without specialized backup software and pseudo-disk drivers installed on the user computing devices. A user can browse as well as edit personal versions of any number and/or versions of block-level backup copies—the “private writable backup copies.” Likewise, a user can browse and edit personal versions of any number of snapshots of one or more versions of one or more desired data volumes—the “private writable snapshots.” A user can have any number of co-existing private writable snapshots and private writable backup copies. Sparse files, extent-files, software snapshots, and/or media agents co-residing on the ISCSI server are used in the illustrative embodiments.

Abstract: Techniques for asynchronously indexing database tables are described herein. An update to data in a database table causes an update to an index table of the database. The update to the index table is made first to the index table and then to a replica of the index table. A first copy of the update is stored in a first replica of the index table and then a second copy of the update is provided to an asynchronous process that stores the second copy of the update in a second replica of the index table.

Abstract: Techniques are presented for implementing non-host-based migration in a manner that is not subject to certain types of data corruption. This may be accomplished by preventing any hosts from having write access to a target LUN until it can be confirmed that all applications that access a source LUN have been shut down. This arrangement prevents accidentally writing to the target LUN while the source LUN is still being accessed. As a further precaution, just in case the confirmations are incorrect, a target data storage system can direct a source data storage system to remove access to the source LUN from all of the hosts, which has a similar effect. The migration can then proceed.

Abstract: An illustrative ISCSI server computing device provides user computing devices with “private writable snapshots” of a desired volume of data and/or further provides “private writable backup copies.” The ISCSI service is provided without invoking snapshot limits imposed by storage arrays and further without specialized backup software and pseudo-disk drivers installed on the user computing devices. A user can browse as well as edit personal versions of any number and/or versions of block-level backup copies—the “private writable backup copies.” Likewise, a user can browse and edit personal versions of any number of snapshots of one or more versions of one or more desired data volumes—the “private writable snapshots.” A user can have any number of co-existing private writable snapshots and private writable backup copies. Sparse files, extent-files, software snapshots, and/or media agents co-residing on the ISCSI server are used in the illustrative embodiments.

Abstract: Each of a storage apparatus having a primary volume and a storage apparatus having a secondary volume, upon reception of a write command, changes a data attribute of a data area allocated to an address designated by the write command, to a first attribute if the data attribute is other than the first attribute. In an offloaded data copy processing sequence, each of the storage apparatus changes a data attribute of a data area allocated to a copy source address to a second attribute if the data attribute is other than the second attribute. When an allocation information copy process is to be performed to allocate the data area to a copy destination address according to an offloaded data copy command, each of the storage apparatus discontinues the offloaded data copy processing sequence if the data attribute of the data area is the first attribute.

Abstract: A sub-LUN ownership mapping for multiple storage controllers of a first storage array is generated. The sub-LUN ownership mapping indicates ownership of sub-LUNs by the multiple storage controllers of the first storage array. The sub-LUN ownership mapping is transmitted to a storage controller of a second storage array. A request to align sub-ownership is sent to the storage controller of the second storage array. Ownership is aligned for one or more sub-LUNS for multiple storage controllers of the second storage array.

Abstract: Examples described herein relate to apparatuses and methods for a Content Distribution Network (CDN) node of a CDN to facilitate communication among two or more clients, including but not limited to determining, by the CDN node, that the two or more clients are connected to the CDN node for accessing content data originating from an origin server, receiving, by the CDN node, a message from a first client of the two or more clients, the message is to be routed to at least one second client of the two or more clients, and sending, by the CDN node, the message to the at least one second client without routing the message to the origin server.

Abstract: Techniques are provided for overlapping write handling. Overlapping write managers are used to maintain the order that write operations are executed at a first computing environment and replicated to a second computing environment. Overlapping write managers are pre-allocated as available for managing overlapping write operations. A mapping is used to track what overlapping write managers are currently allocated for particular file handles of files. Thus, if an incoming write operation targets a file handle of an already allocated overlapping write manager, then that overlapping write manager is used to execute and replicate the incoming write operation so that the order of execution of overlapping writes by the second computing environment is the same as at the first computing environment. If there is no allocated overlapping write manager for the file handle, then a new overlapping write manager is allocated and utilized.

Abstract: A data storage method and an apparatus are provided in a distributed storage system including a computing node and a plurality of storage nodes. The computing node writes the N data slices and the M check slices into the R storage nodes in each storage node group to improve reliability and stability of data in a data center.

Abstract: A database access control method and apparatus are disclosed. The method is applied to a database system. The database system has at least two databases, and the at least two databases include a first database and a second database. One example method includes: receiving an access request from the application, determining that a target database to which the access request is sent is the second database; establishing a database connection between a connection agent and the second database, and sending the access request to the second database by using the connection agent.

Abstract: Disclosed herein are various systems and methods for performing block level incremental backup operations for QCOW2 virtual disks. A first snapshot of a virtual disk is taken and used by a virtual machine at a first point in time. The virtual disk is implemented as a QCOW2 image, and taking the first snapshot causes the first snapshot to be stored in the QCOW2 image. A second snapshot of the virtual disk is taken at a second point in time. Taking the second snapshot causes the second snapshot to be stored in the QCOW2 image. One or more blocks of the virtual disk that have been modified between the first point in time and the second point in time are identified using metadata stored in the QCOW2 image. An incremental backup operation is then performed on the virtual disk by copying one or more blocks from the second snapshot to backup storage.

Abstract: Profiling data includes accessing multiple collections of records to store quantitative information for each particular collection including, for at least one selected field of the records in the particular collection, a corresponding list of value count entries, each including a value appearing in the selected field and a count of the number of records in which the value appears. Processing the quantitative information of two or more collections includes: merging the value count entries of corresponding lists for at least one field from each of a first collection and a second collection to generate a combined list of value count entries, and aggregating value count entries of the combined list of value count entries to generate a list of distinct field value entries identifying a distinct value and including information quantifying a number of records in which the distinct value appears for each of the two or more collections.

Abstract: A first endpoint comprises a fabric attach point for attachment to a memory fabric, a first media controller, and a first non-volatile memory media. The memory fabric comprises a reliability zone comprising the first endpoint and at least a second endpoint. The first media controller is configured to receive, from at least one processor coupled to the first endpoint via the at least one fabric attach point, a memory fabric store command to store an object in the reliability zone. The first media controller is further configured to store the object in the first non-volatile memory media, to receive from the second endpoint a message indicating that the same object has been stored by the second endpoint, and to send to the at least one processor a single acknowledgement indicating that the at least one object has been stored in both the first and second endpoints of the reliability zone.

Abstract: An embodiment of the invention includes a database server system comprising a storage arrangement for storing at least one database and at least one processor operable for receiving a database request over a computer network and accessing the storage arrangement. The processor is further operable for carrying out a monitoring task. The monitoring task determines whether a monitoring description has been stored into the database by the database request. Furthermore, the monitoring task performs a monitoring operation which is specified in the monitoring description. The monitoring operation yields at least one result value. The monitoring task submits a monitoring result request in order to insert the at least one result value into the database. The invention also relates to a computer program product and to a method for performing a monitoring operation on a database server system.

Abstract: Examples include fault isolation in transaction logs. Some examples involve generation of a transaction log entry associated with a fault domain. The transaction log entry may comprise a transaction signature and a fault domain identifier. Based on the transaction signature, a domain sum may be computed. A determination may be made whether each transaction log entry associated with the fault domain is valid, and a valid domain sum may be computed for the fault domain based on the transaction signature of each valid transaction log entry associated with the fault domain. Based on a determination that the domain sum equals the valid domain sum, the fault domain may be recovered.

Abstract: In a reliable distributed computing system, techniques where user actions or events affecting real system devices (RSD's), or causing the system to make changes to metadata, require fewer accesses to RSD's. When a virtual system device (VSD) is mounted, substantially all the metadata, or at least that associated with data recovery, is read into memory. Changes to that metadata can be made substantially without any metadata accesses to RSD's. No metadata accesses to RSD's are made for read operations, as the RSD would remain unchanged. Metadata is flushed from memory upon write operations. Metadata about data locations can be maintained in memory, so as to be available if any RSD becomes corrupted or otherwise comes to lose data.

Abstract: A storage control device includes a processor configured to receive access information indicating a start position and an end position of an access area in a first volume. The processor is configured to determine, based on one or more pieces of the received access information, whether a number of blocks in a cache area is reduced as a whole by changing a position of data in the first volume. The blocks are used in response to an access to the access area and correspond to one or more unit areas in the first volume. The one or more unit areas include the access area. The processor is configured to change the position of the data in the first volume upon determining that the number of the blocks in the cache area is reduced as a whole by changing the position of the data in the first volume.

Abstract: A data disaster tolerance method, device and system is disclosed. Each node in a logic unit including a single master node and two or more slave nodes is monitored. If the master node is abnormal, the server acquires log information of the plurality of two or more slave nodes separately, the log information of the two or more slave nodes includes respective time points of data synchronization between the slave nodes and the master node A respective slave node of the two or more slave nodes having the time point of data synchronization closest to a current time is selected as a target node. A master-slave relationship in the logic unit is updated to change a role of the target node to that of the master node.

Abstract: An apparatus and method are provided for transferring data between address ranges in memory. The apparatus comprises a data transfer controller, that is responsive to a data transfer request received by the apparatus from a processing element, to perform a transfer operation to transfer data from at least one source address range in memory to at least one destination address range in the memory. A redirect controller is then arranged, whilst the transfer operation is being performed, to intercept an access request that specifies a target address within a target address range, and to perform a memory redirection operation so as to cause the access request to be processed without awaiting completion of the transfer operation.

Abstract: The present disclosure relates to a data backup method and device, and a method, device and computer program product for managing data backup. The method for data backup implemented at the computing device comprises: receiving a backup message indicating that data backup is to be performed, the backup message indicating at least one of the following: a virtual machine to be backed up, an operating computing device of the virtual machine to be backed up, and a virtual disk to be backed up; determining, based on the backup message, a block device for which data backup is to be performed, the block device corresponding to at least a part of the virtual disk to be backed up; and performing incremental backup on data in the block device.

Abstract: A redundancy method includes that a first disaster management function (DMF) device on a first site side receives a first request including identification information of a first virtual machine (VM) and a recovery point objective (RPO), allocates a maximum allowable delay time to each node that input/output (IO) data of the first VM passes through in a redundancy process, and sends a second request to a second DMF device on a second site side. The second request includes a maximum allowable delay time of a second replication gateway function (RGF) device on the second site side, and a maximum allowable delay time of an IO writer function (IOWF) device on the second site side and requests the second site side to perform redundancy on the first VM. Hence, the RPO requirements of the tenants can be satisfied in an entire redundancy process.

Abstract: In general, it is proposed to define techniques for managing a virtual storage volume in a cloud architecture comprising hosts which provide storage volume. The managing is achieved by checking the available virtual storage volume when a storage service request from a request interface is received. The virtual storage volume comprises at least one storage volume being assigned to the virtual storage volume. In case the storage service request can not be fulfilled by the available virtual storage volume, a request to the request interface is sent for requesting additional storage volume directly from at least one host. Upon receipt of an accept message that a storage volume fulfilling the storage service is exiting and available, the request interface initiates assigning of the additional storage volume to the virtual storage volume. As next the storage service request is executed on the virtual storage volume.

Abstract: A computing system includes a first storage unit at a first computing site. The first storage unit stores units of work data and data synchronously replicated from a first server cluster of a second computing site. The system further includes a second server cluster at the first computing site, the second server cluster is a proxy node of the first server cluster. The system further includes a second storage unit at the first computing site, the second storage unit stores the units of work data and data from the first storage unit asynchronously into the second storage unit. The system further includes a third server cluster at the first computing site, the third server cluster processes the units of work data asynchronously replicated into the second storage unit.

Abstract: A data replication method and a storage system are provided. The method is applied to a storage system including a first storage device and a second storage device. According to the method, after determining replication information, a first storage system determines a first replication sub-information and a second replication sub-information according to the replication information, where the replication information is used to indicate data that needs to be replicated by the first storage system to a second storage system in a current replication task. Then, the first storage device replicates data to the second storage system according to the second replication sub-information, and the second storage device replicates data to the second storage system according to the second replication sub-information. According to the data replication method, efficiency of replication performed between the first storage system and the second storage system can be improved.

Abstract: Provided are a computer program product, system, and method for managing point-in-time copies for extents of data. A point-in-time copy for at least one range of extents in at least one volume for a point-in-time copy identifier is established. Change recording information is generated indicating each of the at least one range of extents less than all of the extents in the at least one volume. An update to data in the at least one range of extents in the point-in-time copy is received and data in the source storage in the at least one range of extents to be updated is copied as changed data to the target storage. Indication is made in the change recording information of the data in the at least one range of extents that has been updated.

Abstract: The disclosed computer-implemented method for replicating information with information retention systems may include (1) queueing information communicated between a virtual machine and a source storage device, (2) initiating creating a clone of the virtual machine, (3) sending update information sets, (4) inserting a flush marker into a network queue, (5) stopping the queueing of the information communicated between the virtual machine and the source storage device, (6) sending, after sending the update information sets, the flush marker via a source replication gateway to the target server computing device, (7) pausing replication of the source storage device, (8) resuming replication of the source storage device responsive to completing creating the clone of the virtual machine, and (9) sending, to the target server computing device, additional information communicated between the virtual machine and the source storage device after stopping the queueing.