Abstract: Systems and methods for replicating data from a production server to a backup server include recording at least one operation on one or more data items stored in a volume of a production server. The operation may be recorded as at least one journal event in a memory. A determination may then be made regarding whether a system malfunction incident has occurred in the production server and if so, a first set of journal events may be transferred from the memory to an auxiliary storage at a first time instant. At a second time instant, a second set of journal events recorded in the memory between the first and second time instants may be transferred to the auxiliary storage. At one journal event stored in the auxiliary storage unit may then be sent for replication to a backup server.

Abstract: Systems, methods, and software program products discussed herein can create a backup or replica of a master. A method can include receiving, at a backup server, a serialized stream of data representative of changes to a first file of a computer and sorting the received stream of data and storing the sorted data in a memory. The method can include sending an acknowledgment to the computer indicating that the stream of data was received, writing all the sorted data to a single second file, and merging, on the backup server, the written data with data representative of a backup of data on the computer in response to writing all the sorted data to the single second file.

Abstract: A method includes receiving a request for modification of computer readable program code associated with a scenario being executed at a production server. The production server is configured to provide a computing service. Writing to a storage medium associated with the production server with respect to data specified by the protection scenario is suspended during the modification responsive to the request, such that synchronization of the data specified by the scenario is maintained between the production server and a standby server during the modification. Related systems and computer program products are also discussed.

Abstract: During a synchronization phase of a replication process, a master server generates and saves a shadow copy of predefined files to one or more replica servers so as to synchronize the files on both servers. Thereafter, during a replication phase of the replication process, the master server supplements the shadow copy with copies of individual files that have been modified. Each replica server is associated with a filter that controls which of the modified individual files, if any, is sent from the master server to that replica server for storage.

Abstract: Systems and methods for replicating data from a production server to a backup server include recording at least one operation on one or more data items stored in a volume of a production server. The operation may be recorded as at least one journal event in a memory. A determination may then be made regarding whether a system malfunction incident has occurred in the production server and if so, a first set of journal events may be transferred from the memory to an auxiliary storage at a first time instant. At a second time instant, a second set of journal events recorded in the memory between the first and second time instants may be transferred to the auxiliary storage. At one journal event stored in the auxiliary storage unit may then be sent for replication to a backup server.

Abstract: Systems and methods for replicating data from a production server to a backup server include recording at least one operation on one or more data items stored in a volume of a production server. The operation may be recorded as at least one journal event in a memory. A determination may then be made regarding whether a system malfunction incident has occurred in the production server and if so, a first set of journal events may be transferred from the memory to an auxiliary storage at a first time instant. At a second time instant, a second set of journal events recorded in the memory between the first and second time instants may be transferred to the auxiliary storage. At one journal event stored in the auxiliary storage unit may then be sent for replication to a backup server.

Abstract: A method implemented by a node in a high availability system having a master node and a replica node, the method including monitoring another node to determine whether or not the node is responding via a network connection, when the node is found to be not responding, changing into a periodic replication mode of operation, serving user requests while in the replication mode of operation, determining that the other node is now responding via the network connection, negotiating to merge changes resulting from serving the user requests with the other node, and reverting to an online replication mode of operation.

Abstract: A resource management node is provided including a processor and a memory. The memory is coupled to the processor and comprises computer readable program code that when executed by the processor causes the processor to perform operations including creating a recovery virtual machine (VM) for a primary machine for each of a primary machines. The recovery VM is stored in a cache file in a kernel of an operating system. The data in the cache file is stored in a format readable by a virtual hypervisor. The processor is further caused to perform operations including providing the recovery VM from the cache file in the kernel of the operating system upon request when the primary machine fails without conversion of the data in the cache file.

Abstract: A data replication system and method is disclosed in which a master file server uses a first filter in a kernel space to intercept file I/O events, send the file I/O events over a first network, for example a local area network, to a second filter in a kernel space of a first replica file server, and submit the file I/O event to a file system program in user space of the master file server to be processed. The second filter records the file I/O event in a memory of the second file server and sends an acknowledge message to the first filter indicating the file I/O event received by the second filter has been recorded in the replica file server. The first filter notifies user land in the first file server that the file I/O event has been processed if the first filter has received the acknowledge message and the file system program has completed processing the file I/O event in the first file server.

Abstract: A method includes identifying a first boot configuration type for a disk image. The disk image includes a master boot record and a disk partition. The disk partition comprises a volume boot record. The master boot record comprises first instructions for loading an operating system, and the volume boot record comprises second instructions for loading the operating system. The method further includes receiving an input indicative of a second boot configuration type. The method also includes modifying the disk image to use the second boot configuration type to load the operating system by modifying the first instructions and the second instructions.

Abstract: A system, method, and computer-readable storage medium having a computer-readable instruction thereon to replicate transactions in a Zettabyte File System (ZFS). The method includes operations including determining, using a tracing module, a commitment of a current file transaction to a disk, obtaining when a probe function associated with the current file transaction is triggered, the current file transaction, recording a data change contained in the current file transaction, registering a callback function and a reference to the data change contained in the current file transaction after the commitment of the current file transaction, and sending the data change to a remote server.

Abstract: The system and method described herein may support multiple-layer data replication using a block input/output (“BIO”) structure that an operating system kernel employs to provide an intermediate mechanism between file systems and block devices. For example, the system and method described herein may capture events that occur when the kernel uses the BIO structure to encapsulate input/output requests that will change data on a master block device. As such, a replication mechanism may send the changes encapsulated within the BIO structure to a replay mechanism, which may then replicate the changes on a standby block device to ensure that the master block device and the standby block device have an identical state. Alternatively, a filter may be used to only replicate changes to certain partitions or file system objects on the master block device.

Abstract: Systems and methods for replicating input-output (I/O) events of a cluster shared volume (CSV) are presented. Such systems may include a cluster device or node (in a cluster of devices), a coordinator node, and a replica server. Replication techniques disclosed herein may include capturing, using a processor operatively associated with a cluster device, a direct I/O event generated at the cluster device (e.g., by a virtual machine). A legacy file system filter driver of the cluster device may be used and enabled to perform the capturing of the direct I/O event. The legacy file system filter driver may be different than a CSV filter driver associated with the CSV, and may be enabled after the CSV filter driver is enabled. The captured direct I/O event may then be transmitted to the replica server using, e.g., a replication filter, to maintain a backup copy of the event at the replica server.

Abstract: Systems and methods for replicating data from a master server to a replica or backup server include capturing a read event associated with a retrieved file at the master server. The retrieved file may be generated by updating a reference file with remotely stored data. Attributes associated with the retrieved file may be checked to determine if they include attributes associated with the reference file, and if they do not, at least a portion of data and one or more attributes of the retrieved file may be copied or replicated to the replica server. The captured read event may be generated when an application attempts to access or read the retrieved file. An event associated with generation of the reference file may also be captured at the master server, and copies to the replica server.

Abstract: A resource management node is provided including a processor and a memory. The memory is coupled to the processor and comprises computer readable program code that when executed by the processor causes the processor to perform operations including creating a recovery virtual machine (VM) for a primary machine for each of a primary machines. The recovery VM is stored in a cache file in a kernel of an operating system. The data in the cache file is stored in a format readable by a virtual hypervisor. The processor is further caused to perform operations including providing the recovery VM from the cache file in the kernel of the operating system upon request when the primary machine fails without conversion of the data in the cache file.

Abstract: A method includes identifying a first boot configuration type for a disk image. The disk image includes a master boot record and a disk partition. The disk partition comprises a volume boot record. The master boot record comprises first instructions for loading an operating system, and the volume boot record comprises second instructions for loading the operating system. The method further includes receiving an input indicative of a second boot configuration type. The method also includes modifying the disk image to use the second boot configuration type to load the operating system by modifying the first instructions and the second instructions.

Abstract: A data replication system and method is disclosed in which a master file server uses a first filter in a kernel space to intercept a file I/O events, send the file I/O events over a first network, for example a local area network, to a second filter in a kernel space of a first replica file server, and submit the file I/O event to a file system program in user space of the master file server to be processed. The second filter records the file I/O event in a memory of the second file server and sends an acknowledge message to the first filter indicating the file I/O event received by the second filter has been recorded in the replica file server. The first filter notifies user land in the first file server that the file I/O event has been processed if the first filter has received the acknowledge message and the file system program has completed processing the file I/O event in the first file server.

Abstract: Systems and methods for replicating input-output (I/O) events of a cluster shared volume (CSV) are presented. Such systems may include a cluster device or node (in a cluster of devices), a coordinator node, and a replica server. Replication techniques disclosed herein may include capturing, using a processor operatively associated with a cluster device, a direct I/O event generated at the cluster device (e.g., by a virtual machine). A legacy file system filter driver of the cluster device may be used and enabled to perform the capturing of the direct I/O event. The legacy file system filter driver may be different than a CSV filter driver associated with the CSV, and may be enabled after the CSV filter driver is enabled. The captured direct I/O event may then be transmitted to the replica server using, e.g., a replication filter, to maintain a backup copy of the event at the replica server.

Abstract: Systems and methods for generating a bookmark for a snapshot of one or more volumes of a production server include initiating a snapshot process to capture a shadow copy of a snapshot-volume set, which includes one or more volumes of the production server. The snapshot process (e.g., Volume Shadow Copy Service of Windows™ operating system) may include (a) temporarily freezing operations on a file system of the production server, and (b) releasing a freeze of operations on the file system of the production server. A bookmark for the shadow copy (representing a consistent state of the associated volumes) may be generated such that the bookmark corresponds to a completion of the temporarily freezing or releasing a freeze of the operations. The bookmark may include a point in time of the completion of the temporarily freezing or releasing the freeze of the operations.

Abstract: Systems and methods for replicating data from a master server to a replica or backup server include capturing a read event associated with a retrieved file at the master server. The retrieved file may be generated by updating a reference file with remotely stored data. Attributes associated with the retrieved file may be checked to determine if they include attributes associated with the reference file, and if they do not, at least a portion of data and one or more attributes of the retrieved file may be copied or replicated to the replica server. The captured read event may be generated when an application attempts to access or read the retrieved file. An event associated with generation of the reference file may also be captured at the master server, and copies to the replica server.