Patent application number | Description | Published |
20110276573 | JOURNAL EVENT CONSOLIDATION - Journal event consolidation extracts events occurring between two predetermined point in time on data volume, categorizes the events into categories of events, and consolidates the events in the categories of events. | 11-10-2011 |
20110282843 | METHOD AND SYSTEM FOR DATA BACKUP AND REPLICATION - A work flow is initiated and identified by a scenario identifier. A file system driver is notified to record operations on data associated with the work flow identified by the scenario identifier as raw journals without recording data content associated with the operations. The recorded operations are consolidated with previous operations as each operation is recorded in the raw journals. A system snapshot is initiated to be taken. The file system driver is notified of a point in time the system snapshot is taken. Data content associated with the consolidated recorded operations is retrieved from the system snapshot. A first packet is created from selected recorded operations and sent synchronously. A second packet including rest of the recorded operations along with associated data content are sent asynchronously with the point in time of the system snapshot. | 11-17-2011 |
20120136827 | PERIODIC DATA REPLICATION - 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. | 05-31-2012 |
20120197844 | BLOCK LEVEL DATA REPLICATION - Systems and methods for replicating data from a production server to a backup server include identifying one or more data blocks of a file that were modified after a first time instant and before a second time instant. The file may be associated with a protected directory of the production server. An representative data block (e.g., including a hash value) for at least one of the identified data blocks may be computed using a cryptography algorithm, e.g., MD | 08-02-2012 |
20130054529 | SHADOW COPY BOOKMARK GENERATION - 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. | 02-28-2013 |
20150213051 | SYSTEM AND METHOD FOR HIGH AVAILABILITY DATA REPLICATION - 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. In one embodiment, a data replication engine in the first replica file server replicates data stored in the first replica file server to a second replica file server in a location remote from the second replica file server, using a second network, for example a wide area network. | 07-30-2015 |
20150234712 | METHODS OF SYNCHRONIZING FILES INCLUDING SYNCHRONIZED HASH MAP LINKED LISTS AND RELATED DATA PROCESSING NODES - Synchronizing hard link files on master and replica servers includes providing master and replica server hard link file snapshots. The master server hard link file snapshot includes a listing of hard link file names from a root directory of the master server. The replica server hard link file snapshot includes a listing of hard link file names from a root directory of the replica server. The master server hard link file snapshot and the replica server hard link file snapshot are compared. A synchronized hash map linked list may be generated responsive to the comparison. The synchronized hash map linked list includes a listing of group identifications corresponding to physical data files at the master server. For each group identification in the synchronized hash map linked list, the synchronized hash map linked list includes at least a hard link file name from the root directory of the master server. | 08-20-2015 |
20150254080 | MODIFYING DISK IMAGES - 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. | 09-10-2015 |