Class / Patent application number | Description | Number of patent applications / Date published |
707611000 | Synchronous | 61 |
20100106685 | METHOD AND SYSTEM FOR DATA SYNCHRONIZATION - The present invention relates to data backup, and specifically to an apparatus, method, and computer readable medium to manage and automate the backup and synchronization of data on client machines and servers. For example, the system includes a user computer that contains local files and a data repository to which those local files are backed up and synchronized. A user is able to monitor and control the synchronization of the files. The files on the user computer are initially accessed. The files stored in the data repository can be utilized to update the local files, if necessary. | 04-29-2010 |
20100131464 | METHOD AND APPARATUS FOR ENABLING SIMULTANEOUS REPRODUCTION OF A FIRST MEDIA ITEM AND A SECOND MEDIA ITEM - First and second media items are synchronized (step | 05-27-2010 |
20100145909 | SYSTEMS AND METHODS FOR MANAGING REPLICATED DATABASE DATA - Systems and methods for replicating database data and generating read-only copies of the replicated data in a clean shutdown state. For example, systems can include a tracking module (e.g., a filter driver) that monitors transactions from a database application to a source storage device to generate log entries having at least one marker indicating a known good state of the application. The systems further include a computer coupled to a target storage device comprising a database and log files. The computer processes the transactions, based on the log entries, to replicate data to the target storage device; performs a first snapshot on data stored in the database and log files; replays into the database data stored in the log files; performs another snapshot on the database; and reverts the database back to a state in which the database existed at the time of the first snapshot. | 06-10-2010 |
20110153561 | MULTI-PHASE FILE SYSTEM RESTORE WITH SELECTIVE ON-DEMAND DATA AVAILABILITY - A selective restore technique for restoring file systems within computer systems provides on-demand access during the restore process, while preventing users from slowing the restore process by generating random accesses to files that have not yet been restored, early in the restore process. The restored files are grouped into multiple groups of files, which correspond to multiple phases of the restore process. On-demand requests may be locked out for some or all users during the first one or more phases of the restore, while they are permitted for the subsequent phases, ensuring that critical files needed by all users will be available before the backup process is interrupted by on-demand accesses. The groups are generally organized by elapsed time since last access or modification, and may be organized at restore time or during periodic back-up operations so that the files may be similarly organized in the backup media. | 06-23-2011 |
20110161288 | METHOD AND SYSTEM FOR DATA UPDATE SYNCHRONIZATION BY TWO-PHASE COMMIT - In an integrated management database system having a plurality of element databases holding the configuration information about an information system and an integrated database for integrally managing the element databases, an element database which cannot return a reply while maintaining a secure state in response to an update request is not informed of the update request in the first phase of a two-phase commit, thereby attaining synchronization when data is updated, and maintaining the consistency of the data in the system. | 06-30-2011 |
20110276536 | RANGING SCALABLE TIME STAMP DATA SYNCHRONIZATION - Embodiments of the present invention address deficiencies of the art in respect to time stamp based data synchronization and provide a method, system and computer program product for scalable, ranging time stamp based data synchronization. In an embodiment of the invention, a ranging time stamp synchronization method can include computing a time range for a specified time, and producing time stamp synchronization anchors using the time range for each of the anchors. Optionally, a drift value can be computed for the time range and the computing and producing steps can be repeated when the drift value exceeds a threshold. Finally, the anchors can be used to determine whether to update data items in a remote data source in the remote host computing platform with data items from a primary data source in the primary host computing platform. | 11-10-2011 |
20110282834 | CONTINUOUS REPLICATION IN A DISTRIBUTED COMPUTER SYSTEM ENVIRONMENT - A method for implementing continuous data replication in a distributed computer system. The method includes receiving a forwarded data object write I/O from a data server. The method further includes examining attribute information of the data object to determine a consistency group for the data object. A replication policy is examined in view of the consistency group of the data object to determine a destination redundancy server. The data object write I/O is forwarded to the destination redundancy server for storage. An acknowledgment is then sent to the data server upon storage of the data object in the destination redundancy server. | 11-17-2011 |
20110289049 | SCALEABLE FAULT-TOLERANT METADATA SERVICE - Metadata may be stored in, and retrieved from, a scalable, fault-tolerant metadata service. In one example, metadata is divided into partitions, and each partition is served by one or more nodes. For each partition, a first one of the nodes may handle read and write requests, and the other nodes may handle read requests in the event that the first node is down or is experiencing high load. When a request is made with respect to metadata, a metadata server may identify a node, in the partition to which the metadata is assigned, to which the request is to be made. The entity that is making the request then contacts that node, and requests the read or write on the metadata. In a partition, metadata may be replicated between the first node and the other nodes using a log-based replication protocol. | 11-24-2011 |
20110307442 | TRANSPARENT ACCESS MECHANISM FOR LOCAL AND REMOTE DATA - A unified data access mechanism can provide transparent access to data that is either stored locally or remotely. Application programs can direct data requests and data modifications to this singular component without foreknowledge of where the data is stored. The unified data access mechanism can work in concert with a synchronization mechanism that can maintain data synchronization between local data and remote data. Requested or modified data can be identified as stored locally or remotely based on the namespace of the data. If the data is stored remotely, the user credentials associated with the user's process space within which the application program is executing can be utilized to identify, and then provide, relevant authentication information to the remote data store, should it be required. | 12-15-2011 |
20120030168 | PERSISTENCE OF MASTER DATA IN A MULTI-TENANT SOFTWARE DELIVERY ARCHITECTURE - A first tenant-nonspecific database table on a repository accessible to an application server of a multi-tenant software delivery architecture can maintain a first record designating a first predefined generic field of a plurality of predefined generic fields. The first record can include an organization-specific master data field definition of the first predefined generic field maintained in a first tenant-specific definition field assigned to a first customer tenant of a plurality of customer tenants that are accessible via the application server. Each customer tenant of the plurality of customer tenants can provide a discrete organization-specific business configuration of a core software platform. A second tenant-nonspecific database table maintained on the repository can maintain a second record that can include a key value designating the first tenant, a record designator, and an organization-specific master data value corresponding to the first predefined generic field. A calculation or determination based on master data can be performed that is relevant to the discrete organization-specific business configuration provided by the first customer tenant using the organization-specific master data value. | 02-02-2012 |
20120089566 | METHOD FOR REORGANIZING OR MOVING A DATABASE TABLE - A computer system including instructions recorded on a non-transitory computer-readable storage medium and readable by at least one processor may include a table generator module, a table updater module, and a data replicator module. The table generator module may be configured to cause the at least one processor to generate a target table. The table updater module may be configured to cause the at least one processor to modify data in the target table synchronously with data being modified in a source table. The data replicator module may be configured to cause the at least one processor to replicate the data contained in the source table in the target table. | 04-12-2012 |
20120158650 | DISTRIBUTED DATA CACHE DATABASE ARCHITECTURE - System, method, computer program product embodiments and combinations and sub-combinations thereof for a distributed data cache database architecture are provided. An embodiment includes providing a scalable distribution of in-memory database (IMDB) system nodes organized as one or more data fabrics. Further included is providing a plurality of data granularity types for storing data within the one or more data fabrics. Database executions are managed via the one or more data fabrics for a plurality of applications compatible with at least one data granularity type. | 06-21-2012 |
20120271794 | METHOD FOR MANAGING TREATMENT OF A PATIENT HEALTH CONDITION WITH A PDA BASED SYSTEM - A method for managing treatment of a particular health condition afflicting a patient through the use of a PDA which includes a health management program stored in the PDA that prompts a user for entry of health condition data, including patient physiological data, subjective patient health condition data, and medication delivery data, compiles the health condition data into an accumulated data summary, and transmits the data summary from the PDA to a second processing unit through a communication port. A drop-down list related to subjective symptoms is provided, which includes stress and depression. A touch screen is provided for a graphical user interface. The health management program also provides prompts for the entry of diet data, and further displays drop-down lists related to daily activities and alerts for medication delivery. | 10-25-2012 |
20120296868 | Method and article of manufacture for ensuring fair access to information using propagation delays to determine when to release object locks - Locks placed on corresponding objects held in a plurality of databases located at different nodes in a network during replication are released in accordance with fairness criteria. Propagation delays are determined between a transaction initiating node and one or more other nodes in the network. An object is locked during a transaction being executed at the transaction initiating node. Corresponding objects are locked at one or more other nodes in the network that are manipulated as a result of the replication Upon determining that the object locks should be released, the propagation delays are used to determine when to release the object locks so that all of the object locks at the one or more other nodes are released in accordance with the fairness criteria. | 11-22-2012 |
20120303576 | SYNCHRONOUS REPLICATION IN A DISTRIBUTED STORAGE ENVIRONMENT - Embodiments of the present invention relate to synchronously replicating data in a distributed computing environment. To achieve synchronous replication both an eventual consistency approach and a strong consistency approach are contemplated. Received data may be written to a log of a primary data store for eventual committal. The data may then be annotated with a record, such as a unique identifier, which facilitates the replay of the data at a secondary data store. Upon receiving an acknowledgment that the secondary data store has written the data to a log, the primary data store may commit the data and communicate an acknowledgment of success back to the client. In a strong consistency approach, the primary data store may wait to send an acknowledgement of success to the client until it receives an acknowledgment that the secondary has not only written, but also committed, the data. | 11-29-2012 |
20120317074 | SYSTEMS AND METHODS FOR MANAGING REPLICATED DATABASE DATA - Systems and methods for replicating database data and generating read-only copies of the replicated data in a clean shutdown state. For example, systems can include a tracking module (e.g., a filter driver) that monitors transactions from a database application to a source storage device to generate log entries having at least one marker indicating a known good state of the application. The systems further include a computer coupled to a target storage device comprising a database and log files. The computer processes the transactions, based on the log entries, to replicate data to the target storage device; performs a first snapshot on data stored in the database and log files; replays into the database data stored in the log files; performs another snapshot on the database; and reverts the database back to a state in which the database existed at the time of the first snapshot. | 12-13-2012 |
20130151467 | Slave Consistency in a Synchronous Replication Environment - Approaches for replicating data in a distributed transactional system. At a first node of a cluster, a per-transaction write set, comprising a plurality of write operations, is committed against a first MySQL database. One or more per-transaction write sets are replicated from the first node to a second node. Upon receiving a read query, the second node parses the read query to identify a read set, calculates a write set conflict window for the read query, and upon determining that the read set conflicts with one or more write sets in the write set conflict window, waits to process the read query until all conflicting write sets are committed. However, upon determining that the read set does not conflict any write sets in the write set conflict window, the read query is processed without first committing any write transactions in the write set conflict window for the read query. | 06-13-2013 |
20130166505 | MONITORING REPLICATION LAG BETWEEN GEOGRAPHICALLY DISPERSED SITES - A method for detecting replication lag is described. In an embodiment, a local timestamp is generated at a first computer. The local timestamp is stored in an electronic folder. If a replication triggering event occurs, the electronic folder is replicated at one or more target computers. If an update triggering event occurs, the local timestamp in the electronic folder is updated. If a detection triggering event occurs, a request for at least a portion of the electronic folder representing the local timestamp is sent to at least one target computer of the one or more target computers. At least the portion of the electronic folder representing the local timestamp is received from the at least one target computer. If the time difference between one or more of the received timestamps and the local timestamp exceeds a threshold amount, a system event is generated. | 06-27-2013 |
20130166506 | DATA CHANGE MANAGEMENT THROUGH USE OF A CHANGE CONTROL MANAGER - The present description refers to a computer implemented method, computer program product, and computer system to store a node dependency network that includes a plurality of data nodes and one or more links between two or more data nodes, each link representing a data dependency between instances of the two or more data nodes, to forward a requested change to a first data node from a first change control component to a change control manager, identify, by the change control manager based upon the links within the node dependency network, one or more dependent data nodes that are dependent upon the first data node, and determine one or more dependent changes to be performed to one or more instances of the dependent data nodes to maintain consistency among instances of the data nodes. | 06-27-2013 |
20130173537 | MANAGING REMOTE DATA REPLICATION - Various systems, processes, and products may be used to manage remote data replication. In particular implementations, a system and process for managing remote data replication may include the ability to store versions of a disk at a first site, a second site, and a third site. The version of the disk at the first site may store input/output for a host system, the version at the second site may be a synchronous replication of the version at the first site, and the version at the third site may be an asynchronous replication of the version at the first site. The system and process may also include the ability to synchronize the version at the first site with the version at the third site if the second site is unavailable and synchronize the version at the second site with the version at the third site if the first site is unavailable. | 07-04-2013 |
20130173538 | MANAGING REMOTE DATA REPLICATION - Various systems, processes, and products may be used to manage remote data replication. In particular implementations, a system and process for managing remote data replication may include the ability to store versions of a disk at a first site, a second site, and a third site. The version of the disk at the first site may store input/output for a host system, the version at the second site may be a synchronous replication of the version at the first site, and the version at the third site may be an asynchronous replication of the version at the first site. The system and process may also include the ability to synchronize the version at the first site with the version at the third site if the second site is unavailable and synchronize the version at the second site with the version at the third site if the first site is unavailable. | 07-04-2013 |
20130198133 | PARALLEL PROCESSING APPARATUS AND METHOD IN DATABASE MANAGEMENT SYSTEM FOR SYNCHRONOUS REPLICATION - A parallel-processing apparatus and method provide for synchronous replication in a database management system (DBMS). During synchronous replication into the active node and the standby node in the DBMS, replications of transactions are parallelized in units of transactions, thereby improving a performance of the DBMS, guaranteeing atomicity and consistency of the transaction, and solving the deadlock state which may occur in parallel-processing. | 08-01-2013 |
20130204840 | SYSTEM, METHOD, AND INTERFACES FOR WORK PRODUCT MANAGEMENT - A method includes receiving an initial electronic file where the initial electronic file is associated with a work product. The method further includes resolving, automatically, an electronic file content type associated with the initial electronic file and executing, automatically, at least one subscription program associated with the electronic file content type of the initial electronic file. The method further includes retrieving an enhanced electronic file based on a matter security level. The enhanced electronic file is associated with an indication of completion of the at least one subscription program. Another embodiment includes extracting a set of metadata from the initial electronic file and storing the set of metadata from the initial electronic file in a memory. Yet another embodiment includes populating, automatically, at least one field within a field-oriented electronic file from the set of metadata. | 08-08-2013 |
20130262378 | AGGREGATION POINT FOR ENTERPRISE BUSINESS APPLICATION BINDING - Example apparatus and methods concern integrating external items (e.g., data, services) and an enterprise business application (EBA). Example apparatus and methods facilitate having an EBA describe an item for which external data or services are sought and then exposing the description. Example apparatus and methods also facilitate having a provider of external items register external items so that they can be discovered, evaluated, and bound to the EBA. Once an external item has been bound to an EBA item, then data may be automatically exchanged between the external item and the EBA under the control of a synchronization and transformation agent. Metadata-based descriptions of data items in two separate data models are collected in an aggregation point to break direct coupling of the two separate data models while facilitating flexible, extensible, re-definable indirect coupling through the aggregation point. | 10-03-2013 |
20130332413 | REDUCING DATA TRANSFERS WHILE ELIMINATING DATA LOSS FOR ASYNCHRONOUS REPLICATION OF DATABASES - A method for reducing data transfers while eliminating data loss during database replication includes receiving one or more database log write operations caused by an application making updates to a database. The method also includes writing the one or more database log write operations on a database log stored at a primary site and asynchronously mirroring the database log to a secondary storage device located at a secondary site. The method also includes synchronously storing the one or more database log write operations on a secure storage unit at the primary site and receiving an indication of a disaster event at the primary site. In response to the indication of the disaster event, transmitting only the one or more database log write operations stored to the secure storage unit during a time interval to the secondary storage device. | 12-12-2013 |
20130346366 | FRONT END AND BACKEND REPLICATED STORAGE - An existing primary data copy can be maintained on an existing primary front end server node. One or more existing secondary data copies can be maintained on one or more existing secondary front end server nodes to minor the existing primary data copy (such as by making synchronous changes to the secondary data copies). One or more existing backup data copies can be maintained on an existing backend server node to mirror the existing primary data copy (such as by making asynchronous changes to the one or more backup data copies). The existing backend server node can be accessible by one or more of the front end nodes. In response to detecting a failure of the existing primary data copy, one of the one or more secondary data copies can be designated as a new primary data copy in place of the existing primary data copy. | 12-26-2013 |
20140108339 | SYSTEM FOR LIVE-MIGRATION AND AUTOMATED RECOVERY OF APPLICATIONS IN A DISTRIBUTED SYSTEM - A method and apparatus for distribution of applications amongst a number of servers, ensuring that changes to application data on a master for that application are asynchronously replicated to a number of slaves for that application. Servers may be located in geographically diverse locations; the invention permits data replication over high-latency and lossy network connections and failure-tolerance under hardware and network failure conditions. Access to applications is mediated by a distributed protocol handler which allows any request for any application to be addressed to any server, and which, when working in tandem with the replication system, pauses connections momentarily to allow seamless, consistent live-migration of applications and their state between servers. Additionally, a system which controls the aforementioned live-migration based on dynamic measurement of load generated by each application and the topological preferences of each application, in order to automatically keep servers at an optimum utilisation level. | 04-17-2014 |
20140164323 | Synchronous/Asynchronous Storage System - A storage system with a duplicate network storage device may change to and from a synchronous to asynchronous write connection based on a service level agreement. Degradation of a network connection or device performance may cause synchronous writes to be changed to asynchronous network writes, and synchronous writes may be performed on a second device. During the asynchronous operation, a differencing set may be created on a local storage device and used to update the network storage device. When the network storage device becomes able to meet the service level agreement with synchronous writes, the system may include the network storage device for synchronous writes. | 06-12-2014 |
20140181014 | PRESERVING CONTENT ITEM COLLECTION DATA ACROSS INTERFACES - Systems, methods, and computer-readable storage media for preserving collection data across interfaces are disclosed. The system can generate, for a collection of content items stored in multiple user accounts in a synced online content management system, an index of the content items in the collection. The index can store, a content item identifier and a file location, for each content item. Upon detecting that a content item in the collection is moved to a new file location, the system can retrieve a collection identifier from metadata associated with the content item. The system can then locate the index for the collection associated with the collection identifier based on the collection identifier retrieved from the metadata associated with the content item. The system can then update the file location stored at the index for the content item to identify the new file location. | 06-26-2014 |
20140188793 | USING CONFIDENCE VALUES FOR SYNCHRONIZING FILE SYSTEMS - A system, computer implemented method, and computer program product for analyzing an installation to determine a file system promotion path during an online patching cycle. The method commences by identifying an initial file system and a shadow file system, the shadow file system being at least some duration older than the initial run file system, then analyzing a history of events that occurred in or on the installation during the duration to determine a degree of confidence. Based on the degree of confidence, then selecting the initial file system to be used on the online patching cycle when the confidence value is equal or above a threshold, or selecting the shadow file system to be used in the online patching cycle when the confidence value is below a threshold. The history of events is recorded in forms of a patch list, a log file, or a list of configuration events. | 07-03-2014 |
20140188794 | Split Brain Resistant Failover in High Availability Clusters - Method and high availability clusters that support synchronous state replication to provide for failover between nodes, and more precisely, between the master candidate machines at the corresponding nodes. There are at least two master candidates (m=2) in the high availability cluster and the election of the current master is performed by a quorum-based majority vote among quorum machines, whose number n is at least three and odd (n≧3 and n is odd). The current master is issued a current time-limited lease to be measured off by the current master's local clock. In setting the duration or period of the lease, a relative clock skew is used to bound the duration to an upper bound, thus ensuring resistance to split brain situations during failover events. | 07-03-2014 |
20140207735 | APPARATUS AND METHOD FOR DYNAMIC ALIGNMENT OF SOURCE SYNCHRONOUS BUS SIGNALS - An apparatus that compensates for misalignment on a synchronous data bus. The apparatus includes a replica distribution network, a bit lag control element, and a synchronous lag receiver. The replica distribution network receives a first signal, and generates a second signal, where the replica distribution network comprises replicated propagation characteristics of a radial distribution network for a strobe. The bit lag control element is configured to measure a propagation time beginning with assertion of the first signal and ending with assertion of the second signal, and is configured to generate a value on a lag bus that indicates the propagation time. The synchronous lag receiver is coupled to the bit lag control element, and is configured to receive a first one of a plurality of radially distributed strobes and a data bit, and is configured to delay registering of the data bit by the propagation time. | 07-24-2014 |
20140279878 | GENERAL, FLEXIBLE, RESILENT TICKETING INTERFACE BETWEEN A DEVICE MANAGEMENT SYSTEM AND TICKETING SYSTEMS - Systems and methods of the present disclosure facilitate synchronizing data between a device management system and ticketing systems. In some embodiments, the system includes an update module, a mapping module, and a service board selection module. The update module may be configured to update ticketing information about a ticketing ticket on the ticketing system to match device management information about a device management ticket on the device management system. The mapping module may be configured to select a ticket category for a device management ticket on the device management system responsive to the device management information about the device management ticket. The service board selection module may be configured to select a service board for a ticketing ticket on the ticketing system. | 09-18-2014 |
20140324774 | TECHNIQUES FOR MANAGING A DATA REPLICATION MODE - A technique for managing a data replication mode between a primary storage device and a secondary storage device includes in response to a data replication state between the primary storage device and the secondary storage device satisfying a first predetermined condition, selecting at least one candidate logical unit from a plurality of logical units implementing synchronous replication in the primary storage device at least according to priority information of the plurality of logical units. A data replication mode of the at least one candidate logical unit is then modified from synchronous replication to asynchronous replication. | 10-30-2014 |
20140351209 | PREDICTIVE SYNCHRONIZATION FOR CLUSTERED DEVICES - A method and system is provided for a scalable clustered system. The method and system may handle asynchronous traffic as well as session backup. In the method and system, a home cluster member having ownership of a local session predicts designation of a an other cluster member to receive a packet associated with the local session and sends appropriate state information or forwarding instruction to the other network member. | 11-27-2014 |
20140365433 | CROSS DOMAIN LOCKING IN A DISTRIBUTED ENVIRONMENT - In a distributed system, multiple nodes of a cluster update target data using a cross-domain lock. In the distributed system, data is separated into different domains, where some data elements are part of multiple domains. Multiple nodes each store a copy of the target data, which can be part of a single domain, or part of multiple domains. Where at least one element of the target data is part of two different domains, the nodes use cross-domain locks to lock both domains for at least a portion of the data update, and update the data while the lock is active. After updating the data, the nodes can release the cross-domain lock. | 12-11-2014 |
20140365434 | Data Collecting Method and Apparatus, and Mobile Terminal - A data collecting method and apparatus, and a mobile terminal are provided. The data collecting method may be applied in an apparatus including multiple data collecting units. The method includes collecting, by at least two data collecting units, initial data simultaneously at their respective collecting frequencies and at a collection starting moment and collecting, at a synchronous collecting frequency, the initial data collected by the at least two data collecting units so as to obtain synchronous data. The synchronous collecting frequency is a common divisor frequency of the respective collecting frequencies of the at least two data collecting units. | 12-11-2014 |
20140379643 | PRESERVING CONTENT ITEM COLLECTION DATA ACROSS INTERFACES - Systems, methods, and computer-readable storage media for preserving collection data across interfaces are disclosed. The system can generate, for a collection of content items stored in multiple user accounts in a synced online content management system, an index of the content items in the collection. The index can store, a content item identifier and a file location, for each content item. Upon detecting that a content item in the collection is moved to a new file location, the system can retrieve a collection identifier from metadata associated with the content item. The system can then locate the index for the collection associated with the collection identifier based on the collection identifier retrieved from the metadata associated with the content item. The system can then update the file location stored at the index for the content item to identify the new file location. | 12-25-2014 |
20150012488 | Structured Content Item Synchronization - A content management system defines a synchronization application programming interface (API) used by applications executing on client devices to synchronize content items after the content items are changed. Functions of the API specify changes to the content items in terms of semantically-meaningful locations within the content items, rather than physical file locations. The content management system can represent the state of a content item in terms of change descriptors that reference the semantic locations of the API. The content management system can then distribute the change descriptors to the client devices, which refer to the semantic locations of the change descriptors when determining how to reconcile changes made by other client devices. | 01-08-2015 |
20150012489 | SYSTEM AND METHOD FOR ENHANCED SYNCHRONIZATION OF RECORD ORGANIZED DATA BETWEEN DISPARATE APPLICATIONS - Among other things, embodiments of the present disclosure allow multiple accounting software applications to make concurrent edits to the same documents and database records, and provide an efficient, user-friendly interface for resolving conflicts that arise from such edits. | 01-08-2015 |
20150293935 | REDUCTION IN TIME REQUIRED TO WRITE FILE TO TAPE - Reducing time required to write a file to tape is provided. Synchronous processing is performed in a file system implementing a Linear Tape File System (LTFS) file format, wherein the synchronous processing includes writing, to a tape medium of a tape cartridge, index information and one or more files. A type of the synchronous processing is determined, wherein the type is either an index-MAM sync type or an index-only sync type. Updated information is stored to a media auxiliary memory of the tape cartridge in response to determining that the synchronous processing is of the index-MAM sync type. | 10-15-2015 |
20150310034 | FILESYSTEM HIERARCHICAL AGGREGATE METRICS - A software and hardware facility persistently maintains metrics on directories at different levels within a tree of a filesystem. The facility hierarchically aggregates attributes of files contained by directories and stores them as metric values in each directory within a tree. The stored values represent summed or otherwise aggregated data from the descendant directories and files. The metric values represent aggregated attributes such as total space consumed by a directory and all the descendant directories and files, total number of files within a directory, total data blocks used by a directory and its descendant directories and data files, etc. | 10-29-2015 |
20150331925 | Write Performance in Fault-Tolerant Clustered Storage Systems - Embodiments relate to supporting transaction data committed to a stable storage. Committed data in the cluster is stored in the persistent cache layer and replicated and stored in the cache layer of one or more secondary nodes. One copy is designated as a master copy and all other copies are designated as replica, with an exclusive write lock assigned to the master and a shared write lock extended to the replica. An acknowledgement of receiving the data is communicated following confirmation that the data has been replicated to each node designated to receive the replica. Managers and a director are provided to support management of the master copy and the replicas within the file system, including invalidation of replicas, fault tolerance associated with failure of a node holding a master copy, recovery from a failed node, recovered of the file system from a power failure, and transferring master and replica copies within the file system. | 11-19-2015 |
20150379107 | AUTOMATIC MODE SWITCHING IN A SYNCHRONOUS REPLICATION ENVIRONMENT - Disclosed in some examples is a method of database replication, the method including at a Relational Database Management System (RDMS), determining a first replication mode; identifying a triggering event; determining that the triggering event indicates a change in the first replication mode; responsive to determining that the triggering event indicates a change in the first replication mode, determining a second replication mode, the second replication mode being a different replication mode than the first replication mode; identifying a database change made by one or more database tasks; and replicating the database change to an external replication component according to the second replication mode. | 12-31-2015 |
20160044102 | METHOD AND APPARATUS FOR SYNCHRONIZING DATA INPUTS GENERATED AT A PLURALITY OF FREQUENCIES BY A PLURALITY OF DATA SOURCES - Methods and apparatuses are disclosed for synchronizing data inputs generated at a plurality of frequencies by a plurality of data sources. A device receives a first set of data points from a first data source of the plurality of data sources generated at a first frequency of the plurality of frequencies, receives a second set of data points from a second data source of the plurality of data sources generated at a second frequency of the plurality of frequencies, selects a time window corresponding to a period of time during which at least a subset of the first set of data points and at least a subset of the second set of data points were generated, and generates a vector representing a first reduced form of the subset of the first set of data points and a second reduced form of the subset of the second set of data points. | 02-11-2016 |
20160055226 | METHOD AND SYSTEM FOR SYNCING DATA STRUCTURES - The consistency of a data structure is maintained where changes in the form of atomic operations are requested by more than one user to an object graph containing a plurality of objects. Operational transformations specifying how one atomic operation is transformed against another one are accessed and the object graph is modified with the first and second set of changes by employing the operational transformations on the atomic operations and applying the resulting transformed operations to the object graph. The transformed operations are recorded in a history log. The atomic operations are object operations that create or delete an object of the object graph and/or property operations changing a property of an object. Each operation retains the identifier of the object it acts on and information on each change of the object resulting from the operation. Multi-operation conflicts are resolved by defined conflict resolution events. | 02-25-2016 |
20160078052 | Map-Reduce Ready Distributed File System - A map-reduce compatible distributed file system that consists of successive component layers that each provide the basis on which the next layer is built provides transactional read-write-update semantics with file chunk replication and huge file-create rates. Containers provide the fundamental basis for data replication, relocation, and transactional updates. A container location database allows containers to be found among all file servers, as well as defining precedence among replicas of containers to organize transactional updates of container contents. Volumes facilitate control of data placement, creation of snapshots and mirrors, and retention of a variety of control and policy information. Also addressed is the use of distributed transactions in a map-reduce system; the use of local and distributed snapshots; replication, including techniques for reconciling the divergence of replicated data after a crash; and mirroring. | 03-17-2016 |
20160092536 | HYBRID DATA REPLICATION - A system for accelerating database transaction processing by controlling data replication is provided. The system includes a first control unit configured to manage a first storage device and at least one second control unit configured to manage a second storage device. The first control unit writes first data to the first storage device and sends the first data to the second control unit in response to receiving from a host a first write command including the first data. The first control unit writes second data to the first storage device without sending the second data to the second control unit in response to receiving from the host a second write command. The second control unit writes the first data to the second storage device in response to receiving the first data. The second control unit writes the second data to the second storage device in response to receiving from the host a third write command. | 03-31-2016 |
20160092539 | HYBRID DATA REPLICATION - A system for accelerating database transaction processing by controlling data replication includes a first control unit configured to manage a first storage device and at least one second control unit configured to manage a second storage device. The first control unit writes first data to the first storage device and sends the first data to the second control unit responsive to receiving from a host a first write command including the first data. The first control unit writes second data to the first storage device without sending the second data to the second control unit responsive to receiving from the host a second write command. The second control unit writes the first data to the second storage device responsive to receiving the first data. The second control unit writes the second data to the second storage device responsive to receiving from the host a third write command. | 03-31-2016 |
20160110405 | SYSTEMS AND METHODS FOR UPDATING NATIVE CONTACT INFORMATION - Systems and methods for automatically updating contact information in a native contacts application of a device are provided. A contact synchronization engine executing on one or more processors can store a first plurality of contacts received from a first agent running on a first device, store a second plurality of contacts received from a second agent on a second device, receive a change to one or more contact fields of a contact of a user of the second device, determine that the contact of the user of the second device is in the first export, and transmit, responsive to the determination, the change to the first agent. | 04-21-2016 |
20160117378 | DATA STORAGE USING VECTORS OF VECTORS - The systems and methods described here can reduce the storage space required (memory and/or disk) to store certain types of data, provide efficient (fast) creation, modification and retrieval of such data, and support such data within the framework of a multi-version database. In some embodiments, the systems and methods can store each field of a set of records as a vector of values, e.g., a data vector. A set of records can be represented using a vector id vector, or “vid” vector, wherein each element of the vid vector contains a reference to the memory location of a data vector. A header table can store associations between labels and “vid” vectors that pertain to those labels. Identical data vectors can be re-used between different record sets or vid vectors needing that vector, thus saving space. | 04-28-2016 |
20160179871 | GENERAL, FLEXIBLE, RESILENT TICKETING INTERFACE BETWEEN A DEVICE MANAGEMENT SYSTEM AND TICKETING SYSTEMS | 06-23-2016 |
20160196322 | PROCESSING TRANSACTIONS IN A SYNCHRONIZED REPLICATION SYSTEM | 07-07-2016 |
20180025068 | AUTOMATIC MODE SWITCHING IN A SYNCHRONOUS REPLICATION ENVIRONMENT | 01-25-2018 |
707612000 | Multiway synchronization | 7 |
20100114817 | REPLICATION OF OPERATIONS ON OBJECTS DISTRIBUTED IN A STORAGE SYSTEM - One embodiment is a method that reads audit from an audit trail of a source database distributed across multiple storage systems with independent audit trails and then replicates the audit trail to a target database distributed across multiple storage systems with independent audit trails without manual coordination by a database administrator. | 05-06-2010 |
20100125549 | MAINTAINING CLIENT DATA INTEGRITY IN A DISTRIBUTED ENVIRONMENT USING ASYNCHRONOUS DATA SUBMISSION - Data processing architecture where submitters can write data and/or metadata changes to a destination through an asynchronous interface. The architecture includes a ticketing system that issues a ticket (a unique identifier) to the submitter in response to receiving a changelist from the submitter. When the changes are successfully completed at the destination, the cached destination data can be re-downloaded to the submitter, and the changes cached in the submitter, discarded. Absent this capability, a user has to manually manage the cached changes and cached data. The architecture can be distributed in that multiple submitters can submit changelists. The destination provides data integrity by managing submissions to assist in ensuring data integrity across multiple submissions. Automatic changelist cleanup is provided on the submitter so that changelists do not impact performance, memory, and storage. | 05-20-2010 |
20130159251 | Dedicating Disks to Reading or Writing - A method of increasing the speed of disk reading and writing operations in a database by using nodes of memory and processors where the memory stores programs to be executed by the processors. The data in the database is separated into one or more buckets and at least two replicas of each bucket of data are stored in different storage devices of the nodes. Determining a subset of storage devices that will be dedicated to writing, while keeping at least one replica of each bucket dedicated to reading and dedicating at least a substantial portion of the remaining storage devices to reading. | 06-20-2013 |
20140089259 | OPERATION METHOD AND APPARATUS FOR DATA STORAGE SYSTEM - An operation method and apparatus for a data storage system are provided, which relate to the field of data storage and enhance efficiency of a read operation on distributed stored data. The method includes: receiving, by a data node, a data operation message, where the data operation message carries a data operation type and a data object of an operation; querying a state parameter of the data object, where the state parameter is allocated to the data node by a management node, and is used to indicate an update state of the data object, and the update state includes a synchronous state, a semi-synchronous state and an asynchronous state; and if the state parameter is the synchronous state and the operation type is a read operation, reading the data object stored by the data node. Embodiments of the invention are used to operate data in a distributed data storage system. | 03-27-2014 |
20140279879 | SYSTEMS, METHODS AND MEDIA FOR DEFERRED SYNCHRONIZATION OF FILES IN CLOUD STORAGE CLIENT DEVICE - Systems, methods and media are provided for deferred synchronization of files in cloud storage systems. One method includes detecting changes to a data file. The method also includes monitoring I/O operations performed by a process associated with the changes. When the process is busy, the method also includes adding to an upload file list a name of a first file in response to a creation/modification of the first file. The method further includes adding to the list a new name of a second file and, when applicable, removing from the list an old name of the second file in response to renaming the second file. The method also includes removing from the list a name of a third file in response to a deletion of the third file and uploading files identifiable using file names in the list to the cloud storage server when the process is no longer busy. | 09-18-2014 |
20140289193 | SYNCHRONIZING FORWARDING DATABASES IN A NETWORK DEVICE BACKGROUND - Synchronizing forwarding databases in a network device. A first forwarding database may be maintained in a database engine portion of the network device. The forwarding database may include a plurality of entries, each of the entries comprises a synchronization field. The forwarding database may also include a global synchronization value used for the synchronization. A controller in the network device may receive a message indicating one or more changes to a first one or more entries in the forwarding database. The first one or more entries have a first global synchronization value in the synchronization field. Accordingly, the global synchronization value may be changed to a second value and a query may be performed using the first global synchronization value to return changes to the first entries. Changes to other entries in the forwarding database that occur after the global synchronization value is changed may not be part of the query results. | 09-25-2014 |
20150066844 | SYSTEM AND METHOD FOR PROVIDING A VIRTUALIZED REPLICATION AND HIGH AVAILABILITY ENVIRONMENT - The system and method described herein may provide a virtualized replication and high availability environment. In particular, a virtualized production server may run one or more virtual machines in one or more child partitions and have a replication and high availability engine installed in a parent partition. The replication and high availability engine may automatically discover the virtual machines running in the child partitions and automatically synchronize all files associated with the virtual machines to a virtualized replica server. Furthermore, the replication and high availability engine may continuously replicate subsequent changes to the files associated with the virtual machines running in the child partitions to the virtualized replica server, which may then create on-demand virtual machines from the synchronized and replicated files to handle switchover, failover, switchback, and failback events associated with the virtualized production server or the virtual machines running in the child partitions associated therewith. | 03-05-2015 |