| Entries |
| Document | Title | Date |
|---|
| 20110055155 | UNIVERSAL DELTA SET MANAGEMENT - The different advantageous embodiments provide a method for identifying changes in data sets. An ending version for a data set is received. A beginning version for the data set is identified. The ending version for the data set is compared with the beginning version for the data set. A number of differences is calculated between the ending version and the beginning version. A data structure is created that identifies the number of differences between the ending version and the beginning version. | 03-03-2011 |
| 20110066594 | METHODS AND SYSTEMS FOR FILE REPLICATION UTILIZING DIFFERENCES BETWEEN VERSIONS OF FILES - Methods and systems for efficient file replication are provided. In some embodiments, one or more coarse signatures for blocks in a base file are compared with those coarse signatures for blocks of a revised file, until a match is found. A fine signature is then generated for the matching block of the revised file and compared to a fine signature of the base file. Thus, fine signatures are not computed unless a coarse signature match has been found, thereby minimizing unneeded time-consuming fine signature calculations. Methods are also provided for determining whether to initiate a delta file generation algorithm, or whether to utilize a more efficient replication method, based upon system and/or file parameters. In accordance with additional embodiments, the lengths of valid data on physical blocks are obtained from physical block mappings for the files, and these lengths and mappings are utilized for delta file generation, to minimize unnecessary signature computations. | 03-17-2011 |
| 20110218963 | Partial Item Change Tracking and Synchronization - Embodiments herein change the way item syncing is handled and tracked between two devices. Changes to items are tracked in accordance with well defined property groups and each group is tracked independently of the other. For example, one group could contain large data items, e.g., attachments, while another group could include highly volatile properties like a follow-up flag. The present invention increases the sync rates between a client and a server by syncing only select portions of an item that have changed, without monitoring the change of each individual property within the item. Accordingly, if a change is made to a small data property (e.g., follow-up flag) on a relatively large email message, such change will not trigger a large download to a client running under a cached mode, nor will there be a requirement for high storage and processing for tracking each individual property. | 09-08-2011 |
| 20110289053 | ENABLING SYNCHRONIZATION WITH A DIFFERENCE UNAWARE DATA SOURCE - A system and a method are disclosed for updating a master data list with data from a difference unaware information repository and a difference aware information repository. A master synchronization engine may synchronize to the difference unaware information repository and the difference aware information repository via connectors coupled to each information repository. The difference unaware information repository exports all the data stored within the repository to its respective connector. The connecter determines the changes made to the data since the last synchronization and the changes are forwarded to the master synchronization engine. The difference aware information repository is capable of determining the changes made to the stored data since the last synchronization and forwards the changes to its connector. Each connector forwards the changes to the data in their respective information repositories to a database which updates the master data list. | 11-24-2011 |
| 20110295802 | SCALABLE POLICY-BASED DATABASE SYNCHRONIZATION OF SCOPES - Embodiments described herein are directed to synchronizing scopes between a source database and a target database without the target database specifying each scope that is to be synchronized and to determining scope changes based on service subscriptions. In one embodiment, a source database receives from a target database a synchronization scopes policy corresponding to scope criteria provided by the target database. The synchronization scopes policy includes both the scope criteria and a version identifier that together identify a point-in-time snapshot of the set of scopes meeting the scope criteria as of the latest synchronization. The source database resolves the set of scopes last synchronized from the source database to the target database based on the synchronization scopes policy's scope criteria and version identifier. The source database synchronizes to the target database the changes to data in the resolved set of scopes. | 12-01-2011 |
| 20110307444 | REPLICATING SERVER CONFIGURATION DATA IN DISTRIBUTED SERVER ENVIRONMENTS - Components of a distributed server system are configured through replicating configuration data from a central configuration store to server machines. Configuration data is placed in globally identifiable containers or batches. A master replication agent service and a file transfer agent service running in conjunction with a central data storage unit are responsible for replicating configuration data within the batches to other machines in the deployment. A replica replication agent service running on the individual machines updates its own state and posts its latest status back to the central replication services, which upon receiving the status from every machine pushes changes to synchronize the machines with the latest configuration in central store. | 12-15-2011 |
| 20120130947 | System and Method for Delta Change Synchronization - A system and method for delta change synchronization have been disclosed. The system performs delta change synchronization by transferring between two or multiple nodes an initial model and further rendering only the changed objects model-object architecture. The nodes are provided with delta change processing sub-system which mainly includes a delta recorder means for recording the changes in the objects of the main model and renders them to other nodes. | 05-24-2012 |
| 20120143818 | JOURNALING DATABASE CHANGES USING A BIT MAP FOR ZONES DEFINED IN EACH PAGE - The disclosure and claims herein are directed to efficient journaling for recovery of a database index by journaling zones of a page. A journal mechanism maintains a page zone bit map that includes a bit for a plurality of zones in each page to indicate which zones have had their unchanged image journaled before being changed since a last sync point update. The page zone bit map has a bit for each zone in each page so that the status of each zone can be tracked separately. Tracking the smaller zones of the pages makes the process more efficient both at run time and during recovery by reducing the period of time for memory deposits and reducing the amount of total redundant/recovery data sent to disk for larger pages. | 06-07-2012 |
| 20120209809 | CONTINUOUS DATA PROTECTION OVER INTERMITTENT CONNECTIONS, SUCH AS CONTINUOUS DATA BACKUP FOR LAPTOPS OR WIRELESS DEVICES - A portable data protection system is described for protecting, transferring or copying data using continuous data protection (CDP) over intermittent or occasional connections between a computer system or mobile device containing the data to be protected, transferred or copied, called a data source, and one or more computer systems that receive the data, called a data target. CDP can be broken down logically into two phases: 1) detecting changes to data on a data source and 2) replicating the changes to a data target. The portable data protection system uses a method that performs the first phase continuously or near continuously on the data source, and the second phase when a connection is available between the data source and the data target. | 08-16-2012 |
| 20120246114 | LOCALLY EDITING A REMOTELY STORED IMAGE - One or more techniques and/or systems are disclosed for editing a remotely stored image. A user can browse to a site comprising the image, and a preview (e.g., lightweight) version of the image can be loaded to a canvas component of the browser. One or more edits can be applied locally to the preview image, comprising one or more transformation. The one or more transformations can be recorded, and an edited version of the preview image, comprising the one or more image transformations, can be rendered in the canvas component. Once the user commits to one or more transformations, a request can be sent to a remote server comprising the image, to remotely edit the image, where the request comprises one or more delta changes that indicate the one or more committed image transformations, as opposed to requiring multiple bandwidth intensive transfers of the entire image. | 09-27-2012 |
| 20120271796 | METHODS AND SYSTEMS FOR MANAGING DATA - Systems and methods for managing data, such as metadata. In one exemplary method, metadata from files created by several different software applications are captured, and the captured metadata is searched. The type of information in metadata for one type of file differs from the type of information in metadata for another type of file. Other methods are described and data processing systems and machine readable media are also described. | 10-25-2012 |
| 20120278281 | STORING METADATA INSIDE FILE TO REFERENCE SHARED VERSION OF FILE - A link to a shared version of a local file is inserted into metadata of the local file. The local file may be a copy of a shared file and/or a local file that is designated to be shared. For example, when a local file is uploaded to a shared location for collaboration, a link to the shared location is automatically inserted into metadata of the local file. A local copy of a shared file may be created by downloading the shared file to a local data store. A link to the shared location is automatically inserted into the locally stored. When the local file is opened, the link within the metadata may be used to access the version of the local file at the shared location. Changes made to the local file and/or shared version of the file may also be synchronized. | 11-01-2012 |
| 20120296869 | Energy Information Exchange - Disclosed are various embodiments for facilitating data synchronization in a utility computing environment. A data synchronization application can monitor source systems in such an environment and generate periodic change sets that correspond to data that has changed in the various source systems. Destination systems can subscribe to change sets and receive the appropriate change sets by monitoring flags that the data synchronization application can set. Various classes of change sets that correspond to data within a particular change set can also be generated. | 11-22-2012 |
| 20120296870 | Method for Finding, Updating and Synchronizing Modified Record Item and Data Synchronizing Device - The present invention provides a method for searching a change log item, which includes: in a change log of a data synchronizing device, ordering change log items according to numerical values of entity identifiers contained in the items; in the data synchronizing device, when data updating occurs in an entity in a database of the data synchronizing device, using a search algorithm of elements in an ordered sequence to search out whether a change log item containing an entity identifier of the entity exists in the change log. The present invention also provides a data synchronizing device. | 11-22-2012 |
| 20130006930 | TRANSFERENCE CONTROL METHOD, TRANSFERENCE CONTROL APPARATUS AND RECORDING MEDIUM OF TRANSFERENCE CONTROL PROGRAM - A transference control apparatus includes a communication controller, and a processor that executes a procedure, the procedure including processing a control that causes first processing, in which an update log representing the update content of updating performed for a first database is transmitted, by the communication controller, to a second database serving as a copy destination for the first database, to be performed with priority over second processing, in which transmission target data contained in the first database is transmitted to the second database, and restraining, in the case that updating of the transmission target data is allowed in the first database, the control that causes the first processing to be performed with priority. | 01-03-2013 |
| 20130006931 | DATA QUALITY MONITORING - A computer implemented method, computer program product and system for data quality monitoring includes measuring a data quality of loaded data relative to a predefined data quality metric. The measuring the data quality includes identifying delta changes in at least one of the loaded data and the data quality rules relative to a previous measurement of the data quality of the loaded data. Logical calculus defined in the data quality rules is applied to the identified delta changes. | 01-03-2013 |
| 20130117226 | Method and A System for Synchronizing Data - The embodiments herein provide a system and a method for synchronizing a plurality of changes from a source to a destination. The method comprises the steps of starting with an initial polling time, checking for an elapse of a polling interval from a last polled time, polling a source for fetching a data after an elapse of a polling interval from a last polled time, selecting a plurality of changes from the source made by a user, processing the data fetched at the last polling time in a single thread, writing the processed data at a destination and reporting a status of a synchronization process. The initial polling time is a time from which a synchronization of changes in a data is initiated. The method uses both an even t based trigger and a scheduler based trigger | 05-09-2013 |
| 20130124472 | METHODS AND SYSTEMS FOR FILE REPLICATION UTILIZING DIFFERENCES BETWEEN VERSIONS OF FILES - Methods and systems for efficient file replication are provided. In some embodiments, one or more coarse signatures for blocks in a base file are compared with those coarse signatures for blocks of a revised file, until a match is found. A fine signature is then generated for the matching block, of the revised file and compared to a fine signature of the base file. Thus, fine signatures are not computed unless a coarse signature match has been found, thereby minimizing unneeded time-consuming fine signature calculations. Methods are also provided for determining whether to initiate a delta file generation algorithm, or whether to utilize a more efficient replication method, based upon system and/or file parameters. In accordance with additional embodiments, the lengths of valid data on physical blocks are obtained from physical block mappings for the files, and these lengths and mappings are utilized for delta file generation, to minimize unnecessary signature computations. | 05-16-2013 |
| 20130166507 | Declarative synchronization of shared data - Methods and apparatus, including computer systems and program products, related to declarative synchronization of shared data. One method includes receiving one or more changes to data maintained by one of multiple computer programs having respective local copies of the data, identifying an event characterizing synchronization of the data maintained by the computer program with the other computer programs (e.g., with a local copy managed by the other computer program), and initiating synchronization of the changes with one of the other programs having respective local copies (e.g., with the local copy managed by the other program) in response to the event occurring. The event can be characterized by an annotation. Identifying an event can include reading a property of a data object (e.g., in a data object graph of shared data). | 06-27-2013 |
| 20130173540 | GATHERING TRANSACTION DATA ASSOCIATED WITH LOCALLY STORED DATA FILES - Systems and methods are provided for enabling local storing of one or more portions of a data file and recording changes to contents of the data file. In some embodiments, a first data file may be sent to a client system, along with a script to manage the first data file. Changes to the data file may be stored locally, and may then be sent to a remote server upon network reconnection. | 07-04-2013 |
| 20130173541 | DATABASE VERSION MANAGEMENT SYSTEM - Systems and methods for managing versions of a database are described herein. The system includes a worklist module configured to receive a plurality of change requests and generate a first worklist based on them. The plurality of change requests include instructions for modifying one of a database structure and/or master data of the database. One or more change requests may be approved from the first worklist. The worklist module generates a second worklist comprising the approved change requests. One or more change requests included in the second worklist are executed to create a version of the database. A versioning module may maintain and track a plurality of versions within the database. A comparison module may allow comparison and synchronization of the plurality of versions of the database based on the results of comparison and needs in specific environment. | 07-04-2013 |
| 20130226869 | SELECTION OF ROWS AND VALUES FROM INDEXES WITH UPDATES - Methods and apparatus, including computer program products, for selection of rows and values from indexes with updates. In general, rows of an index may be associated with validity flags that indicate whether a row has been updated with an update inserted in a delta index; one scheme for value identifiers may be used for an index and another scheme for one or more delta indexes where all of the indexes are, to at least some extent, compressed according to dictionary-based compression; and multiple delta indexes may be used in alternation such that one delta index may accept updates while another is being updated. The delta indexes may also have validity flags and all updates, such as modifications of values, deletion of records, and inserting of new records may be handled as updates accepted by one or more delta indexes. | 08-29-2013 |
| 20130246355 | USING VIRTUAL MACHINE CLONING TO CREATE A BACKUP VIRTUAL MACHINE IN A FAULT TOLERANT SYSTEM - Techniques for creating a fault tolerant system in a virtual machine environment utilize a primary VM and a backup VM. To initialize the fault tolerant system, the backup VM and primary VM start from the same state. To achieve this in one embodiment, the primary VM is suspended and the state of the primary VM is copied to the backup VM. Once the backup VM has received all the primary VM's state, the primary VM is resumed. Subsequent state changes of the primary VM are buffered until the backup VM resumes, connects to the primary VM, and starts consuming the buffered content. Thereafter, synchronization is maintained by the primary VM's writing relevant state changes to a log and the backup VM's reading such relevant state changes from the log. | 09-19-2013 |
| 20130262380 | COMPUTER-READABLE NON-TRANSITORY MEDIUM STORING THEREIN A CONTROL PROGRAM, MANAGEMENT APPARATUS, AND INFORMATION PROCESSING SYSTEM - A computer-readable, non-transitory medium storing therein a control program that causes a management apparatus to execute an operation, the operation comprises specifying, from among a plurality of databases, a database with the highest frequency of update of target data to be integrated which is stored in the database, transmitting, in accordance with acquisition of update data from the specified database, to a database other than the specified database among the plurality of databases, a request to transmit information stored in the database other than the specified database to the management apparatus and updating the target data to be integrated on the basis of the information transmitted to the management apparatus by the database other than the specified database in accordance with the request. | 10-03-2013 |
| 20130268489 | METHODS AND SYSTEMS FOR REAL-TIME CONTINUOUS UPDATES - Embodiments of the present invention provide fine grain concurrency control for transactions in the presence of database updates. During operations, each transaction is assigned a snapshot version number or SVN. A SVN refers to a historical snapshot of the database that can be created periodically or on demand. Transactions are thus tied to a particular SVN, such as, when the transaction was created. Queries belonging to the transactions can access data that is consistent as of a point in time, for example, corresponding to the latest SVN when the transaction was created. At various times, data from the database stored in a memory can be updated using the snapshot data corresponding to a SVN. When a transaction is committed, a snapshot of the database with a new SVN is created based on the data modified by the transaction and the snapshot is synchronized to the memory. When a transaction query requires data from a version of the database corresponding to a SVN, the data in the memory may be synchronized with the snapshot data corresponding to that SVN. | 10-10-2013 |
| 20130282657 | SHARING AND SYNCHRONIZING ELECTRONICALLY STORED FILES - Aspects of the present disclosure are directed to architectures, methods and systems and structures that facilitate the sharing and synchronization of electronically stored files among and between cloud entities and a number of computers, systems, devices and/or users. One particular exemplary architectural aspect includes the concurrent determination of file system changes within a cloud file system and a client file system, the serial ordering of necessary file system operations in response to the determined file system changes, and the concurrent execution of file system operations such that the cloud file system and the client computer file system are synchronized. | 10-24-2013 |
| 20130332418 | METHOD OF MANAGING DATA IN ASYMMETRIC CLUSTER FILE SYSTEM - Disclosed herein is a method of managing data in an asymmetric cluster file system. In this method, if an OPEN request for the opening of an absent file has been received, a metadata server assigns a file handle value and a file name and then generates a file in a data server. Thereafter, the metadata server copies a file stored in the data server or the generated file to one or more data servers based on a preset copying level. Thereafter, a client performs a file operation on the files stored in the data servers. | 12-12-2013 |
| 20140012812 | Method and System for Efficiently Replicating Data in Non-Relational Databases - A method replicates data between instances of a distributed database. The method tracks changes to the distributed database at a first instance by storing deltas. Each delta includes a row identifier that identifies a row having a base value, and a sequence identifier that specifies an order in which the delta is applied to the base value to compute a current value for the row. The method identifies a set of deltas to send to a second instance based in part on an egress map at the first instance, wherein the egress map specifies which combinations of row identifier and sequence identifier have been acknowledged as received at the second instance. The method then transmits the identified set of deltas to the second instance. After receiving acknowledgement that the deltas in the identified set of deltas have been incorporated into the second instance, the egress map is updated accordingly. | 01-09-2014 |
| 20140019413 | METHOD OF, AND APPARATUS FOR, FILE SYSTEM REPLICATION - A method of replicating a source file system on a storage system, the method including: utilising a changelog operable to store sequentially a data record corresponding to a modification of a source file system by a storage request; specifying a first data record of the changelog at a first time; initiating a scan of the directory inodes of the source file system at the first time; scanning the directory inodes; completing the scan at a second time later than the first time; specifying a second data record of the changelog at the second time; storing, in a database, information corresponding to the scanned directory inodes; updating the database with sequential data records from the first data record to the second data record of the changelog; and building, on a computer system, a replica target file system based on the database. | 01-16-2014 |
| 20140025635 | METHOD AND APPARATUS FOR FAULT-TOLERANT MEMORY MANAGEMENT - A device and method for providing a fault-tolerant file system. The fault-tolerant file system attempts to minimize the number of writes used when updating file system data structures. In one embodiment, file system data, including file system metadata, is stored in a fault-tolerant tree including a working state and a transacted state. In one embodiment, a change list is used to track blocks that have been updated, instead of cascading updates to leaf nodes up the tree, and a delta block is used to further minimize block updates when adding or removing nodes from the tree. In one embodiment, a Q-Block is used to prevent cycles when adding and removing free blocks from an allocation tree. Metadata values are stored in the tree in a way that allows certain metadata values to be inferred when not present in the tree, thus conserving space and lowering query time. | 01-23-2014 |
| 20140040197 | System and Method for Event-Based Synchronization of Remote and Local File Systems - A method for synchronizing a file system (FS) and a remote file system (RFS) includes monitoring the FS for FS events, generating FS event records, receiving RFS event records of RFS events, generating file system operations (FSOs) based on the FS and RFS event records, and communicating the FSOs to the FS and RFS to synchronize them. A method for generating the FSOs includes accessing a plurality of FS and/or RFS event records, processing the accessed records to generate processed event records, generating the FSOs based on the processed event records, and outputting the FSOs to cause synchronization of the FS and RFS. Systems are also described. The invention facilitates event-based, steady-state synchronization of local and remote file systems. | 02-06-2014 |
| 20140040198 | MASS CHANGE OF MASTER DATA VIA TEMPLATES - A data entry template can be associated with each of a plurality of data records that are distributed across a plurality of heterogeneous or homogeneous data sources which can optionally be data bases. The data entry template can be modified to reflect a change to a business process that was previously represented by the template. The change to the business process can be propagated to at least part of the plurality of data records associated with the template. Related systems, apparatus, methods, and/or articles are also described. | 02-06-2014 |
| 20140052691 | EFFICIENTLY STORING AND RETRIEVING DATA AND METADATA - For efficiently storing and retrieving data and metadata in phases, in a first phase, metadata tokens, which are assigned to most active metadata-emitting entities, are used for storing the data and the metadata together in a single input/output operation while piggybacking the metadata of least active metadata-emitting entities onto one of the most active metadata-emitting entities having one of the metadata tokens. In a second phase, the metadata is re-written to a metadata delta journal for reclaiming the metadata tokens. In a third phase, the metadata journal is applied to a metadata structure containing the metadata of the storage system, the metadata delta journal is then cleared after successfully updating the main metadata structure with the metadata of the metadata journal. The metadata journal is swapped with an empty metadata journal for concurrently adding metadata while retaining the metadata journal until applying the metadata delta journal to the metadata structure. | 02-20-2014 |
| 20140059004 | EFFICIENTLY STORING AND RETRIEVING DATA AND METADATA - For efficiently storing and retrieving data and metadata in phases, in a first phase, metadata tokens, which are assigned to most active metadata-emitting entities, are used for storing the data and the metadata together in a single input/output operation while piggybacking the metadata of least active metadata-emitting entities onto one of the most active metadata-emitting entities having one of the metadata tokens. In a second phase, the metadata is re-written to a metadata delta journal for reclaiming the metadata tokens. In a third phase, the metadata journal is applied to a metadata structure containing the metadata of the storage system, the metadata delta journal is then cleared after successfully updating the main metadata structure with the metadata of the metadata journal. The metadata journal is swapped with an empty metadata journal for concurrently adding metadata while retaining the metadata journal until applying the metadata delta journal to the metadata structure. | 02-27-2014 |
| 20140156595 | SYNCHRONISATION SYSTEM AND METHOD - A synchronisation system and corresponding method for synchronising a set of records in a first database with a second database which comprises a copy of the set of records. The first database has a transaction log with entries indicating changes made to records in the first database. The second database stores a global version. The synchronisation system comprises at least one processor which is configured to process entries in the transaction log relating to the set of records to record changes from the first database in the second database; and associate the global version with any records written to the second database. | 06-05-2014 |
| 20140164327 | SYSTEMS AND METHODS FOR RESYNCHRONIZING INFORMATION - Methods and systems for synchronizing data files in a storage network between a first and a second storage device is provided. The method includes storing first data files associated with the first storage device to a storage medium, whereby the first data files include first data records. The storage medium may then be transferred to the second storage device. The first data files from the storage medium may be loaded onto the second storage device. The second data records from the first storage device may be received, and the first and second data records are compared. The first data files at the second storage device may be updated based on the comparison of the first and second data records. | 06-12-2014 |
| 20140172792 | FILE SERVER, INFORMATION SYSTEM, AND CONTROL METHOD THEREOF - A file server is coupled to a plurality of user terminals and a remote file server. The file server, stores, in a storage device, data of files received from the plurality of user terminals, replicates the files to the remote file server, stubs the files stored in the storage device, and, upon receiving an access request from the user terminal, reads out data of the file from the storage device and transmits the data to the user terminal if a file related to the access request is not stubbed, and, recall data of the file from the remote file server and transmits data of the file to the user terminal if a file related to the access request is stubbed. The file server replicates, to the remote file server, data of a user who performs a session disconnection request to the file server within a certain time in preference to another user. | 06-19-2014 |
| 20140188798 | RACE CONDITION HANDLING IN A SYSTEM WHICH INCREMENTALLY UPDATES CLIENTS WITH EVENTS THAT OCCURRED IN A CLOUD-BASED COLLABORATION PLATFORM - Techniques are disclosed for race condition handling in a system which incrementally updates clients with what occurred in a cloud-enabled platform. In one embodiment, a method comprises, in response to an event received at a synchronization client which indicates a modification to an item, comparing a sequence identifier of the item in the event with a current sequence identifier of the item. The sequence identifier of the item can be numeric and can monotonically increase as a state of the item changes. The method further comprises, if the sequence identifier in the event is larger than the current sequence identifier of the item, determining a difference between the item's state as represented in the event and a current state of the item; and, based on the difference, generating at least one synchronization step to update the current state of the item to the item's state as represented in the event. | 07-03-2014 |
| 20140214762 | SYNCHRONIZATION OF TIME BETWEEN DIFFERENT SIMULATION MODELS - Embodiments relate to a method and computer program product for generating a composite simulated model. A method includes receiving a specification request for generating a set of target time-series data from a set of source time-series data and obtaining specification information relating to the set of source time-series data, obtaining specification information relating to the set of target time-series data, and obtaining the source time-series data. The method also includes comparing the source and target specification information to determine if the set of source time-series data are time-aligned with the set of target time-series data and converting the set of source time-series data to the set of target time-series data upon determination that time alignment is needed. | 07-31-2014 |
| 20140236892 | SYSTEMS AND METHODS FOR VIRTUAL MACHINE BACKUP PROCESS BY EXAMINING FILE SYSTEM JOURNAL RECORDS - A new approach is proposed that contemplates systems and methods to support backing up only portions of data associated with a virtual machine that have been changed since the last backup of the data was performed. During a backup process, the proposed approach looks for a journal record of a file system located within one of the partitions on a virtual disk of the virtual machine, wherein the journal record reflects disk operations that have been performed to a storage device associated with a host device/machine running the virtual machine. Once portions of the storage device which data have been modified since the last data backup are identified based on the journal of the file system, only the modified portions of the storage device are submitted to the backup process to be backed up to a backup storage device. | 08-21-2014 |
| 20140244583 | Method of Processing File changes and Electronic Device Thereof - A method of processing files changes includes obtaining a change list of a designate folder, wherein the designate folder includes a plurality of sub-files changed in a time segment and the change list indicates filenames, pathnames and change times corresponding to the plurality of sub-files, determining whether a system time minus a last change time indicated by the change list is greater than a time threshold, and executing a process of determining file actions according to the change list to store a process result in a file action list when the system time minus the last change time indicated by the change list is greater than the time threshold. | 08-28-2014 |
| 20140258228 | PERFORMING PERSISTENT UNDO AND REDO OPERATION WITHIN COMPUTER SOFTWARE - A method and apparatus for managing persistent change operations on user data is disclosed. For each change, a record of the change is saved. An index tracks the current state of the user data. Changes can be undone or redone in a sequential manner if certain criteria are met. Variables pertaining to the changes are saved in a persistent storage, enabling an undo/redo history to be preserved if a program is exited and restarted. | 09-11-2014 |
| 20140279887 | VIRTUAL STORAGE GATE SYSTEM - An example embodiment includes a distributed file management system. The distributed file management system includes a central storage device that is communicatively coupled to data repositories configured to store one or more files. The central storage device includes a processor and a tangible computer-readable storage medium. The tangible computer-readable storage medium is communicatively coupled to the processor and has computer-executable instructions stored thereon that are executable by the processor to perform operations. The operations include receiving file access requests from the data repositories. The operations also include transmitting location information of files requested in the file access requests. The location information includes internet protocol (IP) addresses of the data repositories on which the files are stored. The operations also include receiving updated file indices from the data repositories indicating remote access to files and updating a central access log and a central file index to include the updated file indices. | 09-18-2014 |
| 20140279888 | METADATA-DRIVEN VERSION MANAGEMENT SERVICE IN PERVASIVE ENVIRONMENT - Metadata driven version management service determines one or more version operations to perform based on the properties of a device, computing environment and metadata associated with a file being versioned. The version management service allows different devices to perform different version operations based on different device properties. | 09-18-2014 |
| 20140297590 | INFORMATION PROCESSING SYSTEM, INFORMATION PROCESSING APPARATUS AND INFORMATION PROCESSING METHOD - A first information processing apparatus includes a unit to attach control information to update processing data containing update differential data per storage device and a unit to transfer the update processing data to a second information processing apparatus, and the second information processing apparatus includes a reflecting unit to reflect the update differential data in the transferred update processing data respectively to one or more storage devices, an exclusion setting unit to set exclusion of the storage device given in a list of the storage devices when the first reflecting unit of the reflecting unit reflects the top update differential data in the update processing data, and an exclusion cancelling unit to cancel the exclusion when the second reflecting unit reflects the last update differential data in the update processing data in the storage device. | 10-02-2014 |
| 20140330780 | UNIVERSAL DELTA DATA LOAD - Described herein is a technology for facilitating delta data load. In some implementations, history tables corresponding to physical tables in a data source are provided in a database layer. The database layer includes change list tables corresponding to the history tables and a physical data model based on one or more physical tables. Delta data is determined by analyzing the change list table to create delta data summary tables. Key lists are generated for summary tables corresponding to physical tables which physical data is based. The delta data is applied to the physical data model. | 11-06-2014 |
| 20150012492 | METHOD AND APPARATUS FOR REPLICATING DATA - In order to synchronize a file between transmitting and receiving nodes, when a file is changed, a hint provider of the transmitting node provides a change file and change information about the change file as a hint to a change log generator, the change log generator generates a change log with reference to the change file and the hint, and the generated change log is transmitted to the receiving node by a change log transmitter. | 01-08-2015 |
| 20150019486 | System and Method for Delta Change Synchronization of Data Changes across a Plurality of Nodes - A system and method for delta change synchronization of data changes across a plurality of nodes such as in a collaboration system have been disclosed. The system performs delta change synchronization by generating an initial model comprising objects corresponding to content, transferring initial model between two or multiple nodes and further by rendering only the changed objects of the model-to-model architecture. A tool is provided which is resident on all the nodes participating in a session. This tool comprises a delta change processing sub-system which mainly includes a delta change recorder for recording delta changes corresponding to the changes in the objects of the initial model and rendering the delta changes to other nodes in order to achieve synchronization. | 01-15-2015 |
| 20150032694 | Scalable Coordination Aware Static Partitioning For Database Replication - Parallel logical replication involves multiple apply threads running on a destination database server applying, in parallel, changes made by source transactions, where the changes of a single source transaction may be applied in parallel by multiple apply threads. An apply transaction for a source transaction may be committed by an apply thread independently of the commitment of any other apply transaction of the source transaction, that is, without coordinating the committing of another apply transaction executed by another apply thread for the source transaction. A configuration language is used to configure parallel logical replication. The language facilitates the configuration of various aspects of parallel logical replication, including the number of apply threads, partitioning schemes for the apply threads for partitioning change records between the apply threads, and various other aspects of parallel logical replication. | 01-29-2015 |
| 20150032695 | CLIENT AND SERVER INTEGRATION FOR REPLICATING DATA - Techniques are provided for client and server integration for scalable replication. A replication client transmits change records to a database server over a stream. The database server determines at least one batch comprising change records for at least one transaction. The database server generates dependency data for at least one change record in a batch based on at least one constraint identifier for at least one column. The database server determines an ordered grouping of the change records based on an operation type of each change record and the dependency data of each change record, wherein change records sharing operation types are grouped together unless a division based on the dependency data is determined. The database server generates a reordered transaction comprising a plurality of reordered operations based on the ordered grouping of the change records of the particular batch. | 01-29-2015 |
| 20150039559 | COMPRESSING A MULTI-VERSION DATABASE - Managing a multi-version database is provided. A logical record identifier to physical record row identifier indirection mapping table on a solid-state storage device is extended to include a plurality of delta blocks. A delta block within the plurality of delta blocks is maintained for each primary key in a plurality of primary keys associated with a data table on a magnetic hard disk storage device. | 02-05-2015 |
| 20150046396 | RECONCILIATION PROTOCOL AFTER ICR SWITCHOVER DURING BULK SYNC - According to one embodiment, a method for performing reconciliation sync includes a first network device configured as an active inter-chassis redundancy (ICR) device in response to detecting a switchover request while performing a bulk sync transitioning to serving as the standby ICR device and performing a reconciliation sync while serving as the standby ICR device, the reconciliation sync comprises starting a transmission of session records that failed to be transmitted during the bulk sync to the second network device. | 02-12-2015 |
| 20150058291 | LOG-STRUCTURED STORAGE DEVICE FORMAT - Embodiments of the disclosure provide techniques managing a log-structured solid state drive (SSD) format in a distributed storage system. SSDs in the distributed storage system maintains a journal of logical changes to storage objects to persist prepared and committed changes in the latency path. The journal includes metadata entries that describe changes and reference data pages. Dense data structures (such as a logical block addressing table) index the metadata entries. To reduce the amount of overhead in I/O operations, the distributed storage system maintains the dense data structures in memory rather than on disk. | 02-26-2015 |
| 20150066852 | DETECTING OUT-OF-BAND (OOB) CHANGES WHEN REPLICATING A SOURCE FILE SYSTEM USING AN IN-LINE SYSTEM - Examples described herein include a computer system, positioned in-line with respect to a plurality of clients that actively use a source file system, to replicate a source file system on a target memory in presence of out-of-band events which alter the source file system. | 03-05-2015 |
| 20150074050 | SYSTEM AND METHOD FOR INCREMENTAL REPLICATION - A method of incrementally replicating investigative analysis data is disclosed along with a system for performing the same. The method and system provide the ability to break a data replication job into multiple “replication chunks” which can be exported and imported separately. By doing so, the method and system can efficiently replicate large numbers of data object changes over an unreliable data network. | 03-12-2015 |
| 20150081632 | CHECKPOINT CAPTURE AND TRACKING IN A HIGH AVAILABILITY SYSTEM - The present disclosure includes a method for transferring checkpoint information of a primary virtual machine from a primary host to a secondary host that includes, by the primary host, capturing checkpoint information from the primary virtual machine to a primary holding buffer on the primary host, generating a first number of partition state records from the checkpoint information, transmitting the first number of partition state records to the secondary host, receiving acknowledgements from the secondary host for a second number of partition state records, and tracking the second number of partition state records acknowledged by the secondary host. | 03-19-2015 |
| 20150088822 | MULTI-VERSION CONCURRENCY CONTROL ON IN-MEMORY SNAPSHOT STORE OF ORACLE IN-MEMORY DATABASE - Techniques are provided for maintaining data persistently in one format, but making that data available to a database server in more than one format. For example, one of the formats in which the data is made available for query processing is based on the on-disk format, while another of the formats in which the data is made available for query processing is independent of the on-disk format. Data that is in the format that is independent of the disk format may be maintained exclusively in volatile memory to reduce the overhead associated with keeping the data in sync with the on-disk format copies of the data. | 03-26-2015 |
| 20150120659 | MULTI-INSTANCE REDO APPLY - A method, apparatus, and system for multi-instance redo apply is provided for standby databases. A multi-instance primary database generates a plurality of redo records, which are received and applied by a physical standby running a multi-instance standby database. Each standby instance runs a set of processes that utilize non-blocking, single-task threads for high parallelism. At each standby instance for the multi-instance redo, the plurality of redo records are merged into a stream from one or more redo strands in logical time order, distributed to standby instances according to determined apply slave processes using an intelligent workload distribution function, remerged after receiving updates from remote instances, and applied in logical time order by the apply slave processes. Redo apply progress is tracked at each instance locally and also globally, allowing a consistent query logical time to be maintained and published to service database read query requests concurrently with the redo apply. | 04-30-2015 |
| 20150324415 | GATHERING TRANSACTION DATA ASSOCIATED WITH LOCALLY STORED DATA FILES - Systems and methods are provided for enabling local storing of one or more portions of data file and recording changes to contents of the data file. In some embodiments, a first data file may be sent to a client system, along with a script to manage the first data file. Changes to the data file may be stored locally, and may then be sent to a remote server upon network reconnection. | 11-12-2015 |
| 20150339317 | AVOIDING FULL FILE REPLICATION USING SPARSE FILES - Examples disclosed herein provide systems, methods, and software for avoiding data replication using sparse files. In one example, a method of using a sparse file to manage modifications to read-only files includes identifying an open file request on a computing system for a read-only file, and generating the sparse file corresponding to the read-only file. The method further includes identifying a modification to the read-only file and, responsive to identifying the modification, initiate a write to the sparse file based on the modification and identifying the write in a region map. | 11-26-2015 |
| 20150339343 | MULTI-VERSION CONCURRENCY CONTROL ON IN-MEMORY SNAPSHOT STORE OF ORACLE IN-MEMORY DATABASE - Techniques are provided for maintaining data persistently in one format, but making that data available to a database server in more than one format. For example, one of the formats in which the data is made available for query processing is based on the on-disk format, while another of the formats in which the data is made available for query processing is independent of the on-disk format. Data that is in the format that is independent of the disk format may be maintained exclusively in volatile memory to reduce the overhead associated with keeping the data in sync with the on-disk format copies of the data. | 11-26-2015 |
| 20150347546 | SYNCHRONIZING A DISASTER-RECOVERY SYSTEM OF A DATABASE - A method and associated systems for synchronizing a disaster-recovery system of a database. A processor identifies transactions that affect data blocks of a database and records each change in a vector form. For each block, the processor determines a more efficient way to communicate changes made to the block by a subset of the identified transactions. If fewer resources are needed to communicate an updated image of the entire changed block than would be needed to instead communicate a related set of change vectors that identify changes made to the block by the subset of transactions, then the processor communicates the updated image to the disaster-recovery system. Otherwise, the processor instead communicates the related change vectors to the disaster-recovery system. The processor repeats these determinations and communications for each block of the database that was changed by an identified transaction. | 12-03-2015 |
| 20150356112 | METHOD AND ELECTRONIC DEVICE FOR PROCESSING DATA - An electronic device is provided. The electronic device includes a memory configured to store a file, a storage configured to support journaling of the file stored in the memory, and a data processing module configured to process a journaling method of the file in one mode of a writeback mode and an ordered mode in correspondence to at least one of a property of an application relating to the file and a property of the file. | 12-10-2015 |
| 20150363478 | Systems, Devices, and/or Methods for Managing Data - Certain exemplary embodiments can provide a system, machine, device, manufacture, circuit, and/or user interface adapted for, and/or a method and/or machine-readable medium comprising machine-implementable instructions for, activities that can comprise: via a hierarchy processor implemented via a predetermined information device: for each of a plurality of records of a data structure, displaying data corresponding to a hierarchically displayable field according to a hierarchy location field containing a corresponding hierarchy location identifier indicative of a display location of that data in a displayable hierarchical data structure. | 12-17-2015 |
| 20150379054 | Sparse Linear Algebra in Column-Oriented In-Memory Database - Embodiments relate to storing sparse matrices in an in-memory column-oriented database system. Specifically, recent hardware shifts of primary storage from disc into memory, allow execution of linear algebra queries directly in the database engine. Dynamic matrix manipulation operations (like online insertion or deletion of elements) are not covered by most linear algebra frameworks. Therefore a hybrid architecture comprises a read-optimized main structure, and a write-optimized delta structure. The resulting system layout derived from the Compressed Sparse Row (CSR) representation, integrates well with a columnar database design. Moreover, the resulting architecture is amenable to a wide range of non-numerical use cases when dictionary encoding is used. Performance in specific examples is evaluated for dynamic sparse matrix workloads, by applying work flows of nuclear science and network graphs. Embodiments allow performing linear algebra operations on large, sparse matrices commonly associated with scientific computations and analytical business applications. | 12-31-2015 |
| 20160004719 | USING DISTRIBUTED SOURCE CONTROL IN A CENTRALIZED SOURCE CONTROL ENVIRONMENT - A method is presented for using a distributed source control system with a centralized source control system. A first set of files is obtained from a source control repository and stored on a first electronic computing device. The first set of files comprises all or part of a code base in the centralized source control system. A request is received for at least part of the code base from a second electronic computing device in a distributed source control system. As a result of the request, at least a part of the first set of files is sent to the second electronic computing device. A change set for the first set of files is received from the second electronic computing device. The change set is processed to be in a format compatible with the source control repository. The change set is submitted to the source control repository. | 01-07-2016 |
| 20160019233 | SYSTEM AND METHOD FOR POLICY BASED SYNCHRONIZATION OF REMOTE AND LOCAL FILE SYSTEMS - A method for synchronizing a local file system (LFS) and a remote (cloud) file system (RFS) includes the step of storing events indicative of differences between the LFS and the RFS, where the events are associated with file system objects of the LFS and RFS. The method further includes the steps of prioritizing the events, generating file system operations for the events based at least in part on the prioritization of the events, and performing at least some of the file system operations to synchronize the LFS and RFS. Prioritizing the events includes defining a plurality of service classes (e.g., based on type of event, event attribute, etc.), assigning a priority to each of the service classes, and assigning each event to one of said service classes. Systems are also described. The invention allocates limited synchronization resources based on a predefined policy to synchronize important file system objects sooner. | 01-21-2016 |
| 20160019279 | HIGH THROUGHPUT DATA MODIFICATIONS USING BLIND UPDATE OPERATIONS - Update requests that specify updates to a logical page associated with a key-value store are obtained. Updates to the logical page are posted using the obtained plurality of update requests, without accessing the logical page via a read operation. | 01-21-2016 |
| 20160026654 | DATA MOVER DISCOVERY OF OBJECT EXTENT - Performing data backup for a client includes receiving, at a host other than the client, volume information including data indicating a physical data storage location of at least a part of a volume comprising one or more stored objects associated with the client; and determining at the host, based at least in part on the volume information, a stored object information for a stored object included in the volume, the stored object information including data associated with a physical data storage location of the stored object. | 01-28-2016 |
| 20160048569 | Method of integrating remote databases by automated client scoping of update requests prior to download via a communications network - A system and method enable the selection of a time range of database records for download from a source database source and for transfer to a recipient database. A specifically bounded time period is selected to limit the number of data records selected for download in a particular action to those records that are individually associated with date time stamp values falling within the specified time period. This limitation of records selected for inclusion in a download process to data records having associations with date time stamps falling within a limited time range reduces a likelihood of overload in transferring data and thereby reduces the incidence of time-outs in the communication of a source database, any intermediary server or software action, and the recipient database in an updating of the recipient database to reflect a current state of the source database. A plurality of threads may be employed to contemporaneously download records associated with date time stamps having values within a requested time range whereby data records may be downloaded in parallel. | 02-18-2016 |
| 20160055172 | DYNAMICALLY SYNCHING ELEMENTS IN FILE - An approach is provided for synchronizing elements in files across a technical environment. In one embodiment, a processor obtains a first change to a first file. The processor also obtains data identifying a second file. The processor determines if the change is supported by a data library in a pre-defined list of data sources. The processor analyzes the data library to determine a type of the change. The processor applies the type of the change to the second file. | 02-25-2016 |
| 20160092444 | DISTRIBUTED FILE SYSTEM BACKUP AND SYNCHRONIZATION - Systems and techniques for a distributed file system element collection are described herein. A node may identify a state of a file system element, which is identified in a file system element definition, from a local data store. The state corresponds to a distribution action. The file system element definition is one of a plurality of file system element definitions in a collection schema of a collection to which the node is a member. The node may, in response to identifying the state of the file system element, issue a communication to some members of the collection in furtherance of completion of the distribution action. A response may be received by the node from a participant node in the list of participant nodes. The node may complete the distribution action using content from the response. | 03-31-2016 |
| 20160110440 | APPARATUS, AND ASSOCIATED METHOD, FOR SYNCHRONIZING A GROUP OF DATA OBJECTS - An apparatus, and an associated method, facilitates synchronization of a group of data objects. Batches of data objects are iteratively processed. When a synchronization response indicates that the data of the request is unsynchronizable, data associated with the synchronization request is marked. A retry procedure is subsequently utilized to attempt synchronization of the marked data objects and to determine the individual data objects that cannot be synchronized. | 04-21-2016 |
| 20160117376 | SYNCHRONIZING OBJECT IN LOCAL OBJECT STORAGE NODE - A latest status record of an object in a local storage node is obtained as a local status record of the object. The status record includes a name of an operation changing the object, a timestamp of the operation changing the object, a first status flag, and a second status flag. The first status flag indicates whether a synchronization of the object from current object storage node to another object storage node is executed. The second status flag indicates whether a synchronization of the object from another object storage node to the current object storage node is executed. The latest status record of the object is obtained of the object in from a remote object storage node as a remote status record of the object. A synchronization of the object is executed based on the local status record and the remote status record. | 04-28-2016 |
| 20160124815 | EFFICIENT BACKUP OF VIRTUAL DATA - A method, article of manufacture, and apparatus for protecting data. In some embodiments, this includes taking a snapshot of a virtual machine, parsing the virtual machine to determine a header section and a file system, indexing the virtual machine based on the parsing, storing the index in a storage device, and storing the snapshot in a deduplicated data storage device. | 05-05-2016 |
| 20160132399 | IMPLEMENTING CHANGE DATA CAPTURE BY INTERPRETING PUBLISHED EVENTS AS A DATABASE RECOVERY LOG - A method for implementing a change capture system using an event publishing system as a database recovery log is provided. The method may include determining a set of data based on a description of events for which change capture is possible. The method may also include selecting at least one item of data from within the determined set of data, wherein the at least one item of data requires change capture to be performed. Additionally, the method may include identifying at least one published event, wherein the at least one published event is produced by the event publishing system. The method may include instructing the event publishing system to deliver the at least one identified published event to the change capture system. Furthermore, the method may include receiving the at least one identified published event. The method may also include processing the at least one published event. | 05-12-2016 |
| 20160132577 | Copy Procedure To Reduce Downtime For A Source System - A system, a method and a computer program product for performing a copy procedure are disclosed. A copy procedure that copies a table in a plurality of tables stored at a source system to a target system is initiated. At least one table in a plurality of tables stored at the source system is selected for copying from the source system to the target system. A trigger table containing at least one trigger is generated. The trigger indicates at least one change made to the at least one selected table. The trigger table is copied from the source system to the target system. The selected table is copied from the source system to the target system. Using the copied trigger table, changes are applied to the table copied to the target system. | 05-12-2016 |
| 20160132579 | DETERMINING COMMON TABLE DEFINITIONS IN DISTRIBUTED DATABASES - Determining common table definitions in distributed databases includes receiving a query at a node in a distributed database. The query targets a logical table. Upon determining the logical table is locally defined, one of the local definition and a network definition is selected to use. The network definition is independently established for shared logical table names. The selected definition is used and propagated with the query through the distributed database. Upon determining the logical table is not locally defined, an initial query is issued to other nodes in network to find the network definition for the logical table, the network definition is stored in memory, and the selected definition is propagated through the distributed database with the query. | 05-12-2016 |
| 20160147617 | Data Synchronization with Minimal Table Lock Duration in Asynchronous Table Replication - Disclosed herein are system, method, and computer program product embodiments for minimizing table lock duration during lost change resynchronization between a source table and a replica table. An embodiment operates by detecting a restart at a source node or a replica node. A source table at the source node is then locked based on the detection. A database transaction is then created for a lost change resynchronization operation and the source table is unlocked. The database transaction is then compared to another database transaction based on its timestamp. Based on the comparison, either the database transaction for the lost change resynchronization operation or the other database transaction is executed. | 05-26-2016 |
| 20160147618 | RowID-Based Data Synchronization for Asynchronous Table Replication - Disclosed herein are system, method, and computer program product embodiments for synchronizing lost change between a source table and a replica table. An embodiment operates by detecting a restart at a source node or a replica node. Row-ID values of replication log entries are then compared to row-ID column values of rows at a replica table of the replica node. Replication errors at a source table or the replica table are then determined based on the row-ID comparison. The rows of the source table and the replica table are then updated based on the determination. | 05-26-2016 |
| 20160147788 | PRE-SYNCHRONIZATION ANALYSIS BETWEEN LOCAL DOCUMENTS AND AN ONLINE DOCUMENT MANAGEMENT SYSTEM - Embodiments describe pre-synchronization analysis between a computing device and an online document management system. In one embodiment, the computing device identifies a mapping between a local folder and a remote folder at the system, identifies a local file in the local folder, and determines if a remote copy of the local file exists in the remote folder. When the remote copy does not exist, the computing device adds a pending upload entry in an analysis log. When the remote copy does exist, the computing device either adds a pending upload entry in the analysis log or skips an entry in the analysis log for the local file depending on whether the remote copy was modified after a previous synchronization, the local file was modified after the remote copy, and the local file and the remote copy have different file sizes. The computing device displays the analysis log to a user. | 05-26-2016 |
| 20160147802 | Synchronizing Different Representations of Content - Two different representations of content are maintained, at least one of which is a composite representation of the content. The composite representation is multiple different components, each component stored as a separate file and each component including some of the data of the content. The composite representation also includes a manifest that identifies the various components. Different devices can edit the content, and access to the content is coordinated via a synchronization system. The synchronization system manages generation of one or more representations of the content. The synchronization system also manages synchronization of the different representations of the content, allowing changes made on various different computing devices to be reflected in the different representations of the content, and managing situations in which different computing devices may attempt to change the content concurrently. | 05-26-2016 |
| 20160147860 | System and method for hierarchical synchronization of a dataset of image tiles - A system and method for hierarchical synchronization of tiles between a first dataset and a second dataset by computing and storing multiple composite cluster hash values for multiple clusters in the first and second dataset. For each of the composite cluster hash values, comparing a composite cluster hash value of a particular cluster in the first dataset with a composite cluster hash value of a corresponding cluster in the second dataset. When the composite cluster hash values of the corresponding clusters do not match, retrieving all tile hashes corresponding to all the tiles from the non-matching cluster in the first dataset, and retrieving all tile hashes corresponding to all the tiles from the non-matching cluster in the second dataset. Finally, determining the one or more changed tiles between the non-matching cluster in the first dataset and the non-matching cluster in the second dataset by comparing the corresponding tile hashes. | 05-26-2016 |
| 20160162534 | DATA ENVIRONMENT CHANGE NOTIFICATION - A method of and system for monitoring and providing notification of changes to a data environment. Parameters of interest for monitoring changes made to a metadata data store are stored. Instructions are stored related to notifying a recipient of a communication about the changes. The metadata is monitored for changes related to the parameters of interest, and a change notification communication is generated with transmission initiated to the recipient. The instructions related to notification of the changes may include the identity of a recipient, mechanism for notification, and format and content of notification. A computer readable memory system and a computer program product may be provided that is encoded with a data structure for notifying data consumers of changes to a data environment that includes metadata. | 06-09-2016 |
| 20160188627 | DETECTING OUT-OF-BAND (OOB) CHANGES WHEN REPLICATING A SOURCE FILE SYSTEM USING AN IN-LINE SYSTEM - Examples described herein include a computer system, positioned in-line with respect to a plurality of clients that actively use a source file system, to replicate a source file system on a target memory in presence of out-of-band events which after the source file system. | 06-30-2016 |
| 20160203050 | DATA REPLICATION IN A DATABASE MANAGEMENT SYSTEM | 07-14-2016 |
| 20160253401 | SYNCHRONIZATION ADAPTER FOR SYNCHRONIZING DATA TO APPLICATIONS THAT DO NOT DIRECTLY SUPPORT SYNCHRONIZATION | 09-01-2016 |
| 20160253404 | DATABASE-CONTROLLED INFORMATION LIFECYCLE MANAGEMENT | 09-01-2016 |
| 20170235758 | VIRTUALIZED FILE SERVER DISASTER RECOVERY | 08-17-2017 |
| 20170235781 | METHOD, SERVER AND COMPUTER PROGRAM STORED IN COMPUTER READABLE MEDIUM FOR MANAGING LOG DATA IN DATABASE | 08-17-2017 |
| 20170235808 | PREDICTIVE AND ADAPTIVE QUEUE FLUSHING FOR REAL-TIME DATA RECONCILIATION BETWEEN LOCAL AND REMOTE DATABASES | 08-17-2017 |
| 20180025023 | DYNAMICALLY SYNCHING ELEMENTS IN FILE | 01-25-2018 |
| 20180025042 | TITLE: AUTOMATIC DELTA QUERY SUPPORT FOR BACKEND DATABASES | 01-25-2018 |
| 20190149418 | CLUSTERED APPLICATION MANAGEMENT WITH A BLOCKCHAIN | 05-16-2019 |
