A method, system and program product for dynamically changing the size of a LUN in a replication based environment, the replication environment having a splitter, a production site and a replication site, the production site having a production LUN, the replication site having a journal and a replication LUN, comprising changing the LUN size on the production site based on a request to change the size of the LUN on the production site, determining on the replication site that the LUN on the production site has changed size, determining whether it is possible to change the size of the replication LUN, based on a negative determination and in response to a request for the replication LUN, pausing replication, and based on a positive determination, changing or faking the size of the replication LUN.

A method, system and program product for implementing the xcopy command in a replication environment, the replication environment having a production site, a splitter, and a replication site, wherein the replication site has a journal, comprising, determining if the source and target LUNs of the xcopy command are replicated, based on a determination that both source and target LUNs are replicated, determining if the production and replication LUNs are synchronized, based on a positive determination that the LUNs are synchronized, and performing the xcopy command on the replication.

Example embodiments of the present invention relate to a method, a system, and a computer program product for performing data replication and backup. The method comprises performing a first data replication of a production site storage to a replication site storage and performing a first backup of the production site storage to a production site backup storage. A second data replication then may be performed from the production site backup storage to a backup site backup storage.

Systems and methods are provided for persisting a data structure. One method may comprise, at a front-end node in a computing system: generating a data structure operation record for a data structure operation directed to a data structure persisted in a non-volatile memory (NVM) in a back-end node of the computing system, appending the data structure operation record in an operation log, generating a transaction record for a transaction that includes a plurality of memory operations that collectively accomplishing the data structure operation, appending the transaction record in a transaction log, flushing the transaction log to the back-end node after flushing the operation log; and at the back-end node of the computing system: persisting received operation log and received transaction log in the NVM, and accomplishing the data structure operation by performing the plurality of the memory operation records with the data structure operation record as a commit signal.

Examples of the present disclosure describe implementing bitmap-based data replication when a primary form of data replication between a source device and a target device cannot be used. According to one example, a temporal identifier may be received from the target device. If the source device determines that the primary replication method is unable to be used to replicate data associated with the temporal identifier, a secondary replication method may be initiated. The secondary replication method may utilize a recovery bitmap identifying data blocks that have changed on the source device since a previous event.

A method, computer program product, and computer system for receiving, at a computing device, a write request from a host, wherein a first portion of a process may receive the write request. A callback and context may be set in the write request by the first portion of the process. The write request may be passed to a second portion of the process. The first process may be provided with the context. The first process may use the context to replicate the write request data to a destination.

The present disclosure provides a system and method for online brand continuity. Online brand continuity can include a number of Internet or intranet access points via which one or more network addresses can be advertised. A client can be provided with availability of a business image application via at least one of the Internet or intranet access points.

One or more techniques and/or computing devices are provided for data synchronization. For example, an in-flight log may be maintained to track storage operations that are received by a first storage node, but have not been committed to both first storage of the first storage node and second storage of a second storage node that has a replication relationship, such as a disaster recovery relationship, with the first storage node. A dirty region log may be maintained to track regions within the first storage that have been modified by storage operations that have not been replicated to the second storage. Accordingly, a catchup synchronization phase (e.g., asynchronous replication by a resync scanner) may be performed to replicate storage operations (e.g., replicate data within dirty regions of the first storage that were modified by such storage operations) to the second storage until the first storage and the second storage are synchronized.

A method and system for performing incremental backup of a network attached storage (NAS) device are described. A storage capture instance associated with a first time instance is received from a network attached storage device. At least a portion of metadata of tracked network packets associated with the network attached storage device is also received. At least one changed content item of the network attached storage device that has changed since the first time instance is identified by analyzing the at least the portion of the metadata of the tracked network packets received. An incremental backup of the network attached storage device is performed at a second time instance based at least in part on the at least one changed content item identified.

Providing Quality of Service (QoS) for replicating datasets including: receiving, by a target data repository from a source data repository, a checkpoint describing one or more updates to one or more datasets stored in the source data repository and the target data repository; adding, by the target data repository, the checkpoint to a first queue for checkpoints directed to one or more volumes in the target data repository, wherein the first queue is included in a plurality of queues for the target data repository; selecting, by the target data repository, one or more queues from the plurality of queues; and servicing an operation from each of the selected one or more queues.