Entries |
Document | Title | Date |
20100076930 | SYSTEM AND METHOD FOR PROVIDING HIGH AVAILABILITY DATA - A computer-implemented data processing system and method writes a first plurality of copies of a data set at a first plurality of hosts and reads a second plurality of copies of the data set at a second plurality of hosts. The first and second pluralities of copies may be overlapping and the first and second pluralities of hosts may be overlapping. A hashing function may be used to select the first and second pluralities of hosts. Version histories for each of the first copies of the data set may also written at the first plurality of hosts and read at the second plurality of hosts. The version histories for the second copies of the data set may be compared and causal between the second copies of the data set may be evaluated based on the version histories for the second copies of the data set. | 03-25-2010 |
20100076931 | Recording Information About an Item - Among other disclosed subject matter, a computer program product is tangibly embodied in a computer-readable storage medium and includes instructions that when executed by a processor perform a method for recording information about an item. The method includes assigning a unique identifier to an item in a repository, the item supporting versioning and being subject to a data model having no predefined schema for items. The method includes associating a first attribute with the unique identifier, the first attribute being part of the item and being configured for modification. The method includes associating the first attribute with a version number, wherein the versioning is supported without recording in the repository a time period when the first attribute is valid. | 03-25-2010 |
20100088278 | Network file update mechanism with integrity assurance - An approach is provided that receives a file request and maintains a set of file versions of the requested file on a network-accessible storage media. The file versions are retrieved from the network accessible storage media along with expected hash values corresponding to each of the file versions. The retrieved file versions are stored in a second nonvolatile storage media, such as a local nonvolatile storage. File versions are selected from newest to oldest. When a file version is selected, a hash value is computed for the file and this hash value is compared to the expected hash value that corresponds to the selected file version. The first (newest) file version with a hash value that matches the expected hash value is selected and returned to the requestor. | 04-08-2010 |
20100114825 | VERSION CONTROL ENVIRONMENT FOR VIRTUAL MACHINES - A method of maintaining update history of a virtual machine (VM) is disclosed. The VM includes a version number. The method includes continuously monitoring a state of the VM. The monitoring of the state including detecting updates in configurations and applications of the VM. The changes in a status of the applications and the configuration are captured and metadata of the VM is updated when a change in the configurations or in the applications is detected. The version number of the VM is then incremented. | 05-06-2010 |
20100114826 | CONFIGURATION MANAGEMENT IN DISTRIBUTED DATA SYSTEMS - Systems and methods for managing configurations of data nodes in a distributed environment A configuration manager is implemented as a set of distributed master nodes that may use quorum-based processing to enable reliable identification of master nodes storing current configuration information, even if some of the master nodes fail. If a quorum of master nodes cannot be achieved or some other event occurs that precludes identification of current configuration information, the configuration manager may be rebuilt by analyzing reports from read/write quorums of nodes associated with a configuration, allowing automatic recovery of data partitions. | 05-06-2010 |
20100114827 | SYSTEM AND METHOD FOR DOCUMENT MANAGEMENT - A system and method for document management in an industry where mass volumes of drawings are exchanged and worked upon is facilitated and streamlined. The system has a server in communication with a plurality of remote workstations. Each of the workstations includes a display and interface. The system standardizes the documents, and is operable to display the same document in each of the workstations. Thus, revisions by an authorized person may be made and seen by the other workstations. The system and method disclosed herein also ensures that drawings are delivered to the appropriate personnel as only authorized users may access the system, and eliminates the potential use of outdated drawings in planning as each drawing is automatically time and date stamped and placed in sequential order. | 05-06-2010 |
20100138389 | SYSTEMS AND METHODS FOR UPDATING A DATA STORE USING A TRANSACTION STORE - Embodiments include systems and methods for updating a data store in a distributed data store system. In one embodiment, a previous version of a data store is compared to an updated version of the data store in order to create a transaction store. The transaction store may include a cryptographic hash indicative of the previous version of the data store and a cryptographic hash indicative of the updated version of the data store. The transaction store further indicates data differences between the previous and updated versions of the data stores. The transaction store may then be used to update data stores at other locations. | 06-03-2010 |
20100145914 | DATABASE MANAGEMENT SERVER APPARATUS, DATABASE MANAGEMENT SYSTEM, DATABASE MANAGEMENT METHOD AND DATABASE MANAGEMENT PROGRAM - Provided is a database management server apparatus that can maintain the consistency of updates and prevent blocking other update requests in an update process. | 06-10-2010 |
20100153339 | Updating display system of display list and method thereof - An updating display system of a display list and the method thereof are provided. A first version information of the display list at a local end is checked against with a second version information on a server. If they are different, only a modification item file containing a data item to be modified is downloaded from the server. The display list is then modified according to a line number given in the modification item file. The data item in the display list are ordered according to the time tags in the modification item file. This can solve the problems of spending too much time in downloading the display list and an unclear play list. This helps to achieve efficient update and better display. | 06-17-2010 |
20100161556 | SYSTEMS AND METHODS FOR A SNAPSHOT OF DATA - In one embodiment, a user or client device is connected to a distributed file system comprised of one or more physical nodes. The data on each of the physical nodes store metadata about files and directories within the file system. Some of the embodiments permit a user to take a snapshot of data stored on the file system. The snapshot may include a single file, a single directory, a plurality of files within a directory, a plurality of directories, a path on the file system that includes nested files and subdirectories, or more than one path on the file system that each includes nested files and directories. In one embodiment, the metadata comprises mini-snapshots for directories representing a path from the root of the file system to the root of the snapshot. The mini-snapshots serve as stand-ins for portions of the file system which are not included in the snapshot, but which permit access to the snapshot data in an intuitive way. | 06-24-2010 |
20100161557 | SYSTEMS AND METHODS FOR A SNAPSHOT OF DATA - In one embodiment, a user or client device is connected to a distributed file system comprised of one or more physical nodes. The data on each of the physical nodes store metadata about files and directories within the file system. Some of the embodiments permit a user to take a snapshot of data stored on the file system. The snapshot may include a single file, a single directory, a plurality of files within a directory, a plurality of directories, a path on the file system that includes nested files and subdirectories, or more than one path on the file system that each includes nested files and directories. According to one embodiment, the system stores representations of the snapshots that govern a file or directory and its descendants within metadata associated with that file or directory. In one embodiment, before modifying a file or directory, the system updates the representations of the governing snapshots by traversing the metadata of ancestors of the file or directory. | 06-24-2010 |
20100198789 | DATABASE CONTRADICTION SOLUTION METHOD - Provided is a database operation method which modifies references among database records. A record is fetched ( | 08-05-2010 |
20100198790 | UPDATING ELEMENTS IN A DATA STORAGE FACILITY USING A PREDEFINED STATE MACHINE, WITH SERIAL ACTIVATION - A technique for updating elements in a data storage facility, including a single server or a multi-server system, such as by providing updated internal code packages to the elements. The update is performed using a fixed state machine, where the elements are updated in a coordinated manner within the constraints of the state machine. In a multi-server device, code packages are distributed to elements associated with the different servers in one traversal of the state machine, during distribute states of the state machine. The distributed code packages are activated in activate states of the state machine in multiple traversals of the state machine, so there is a serial activation. The code packages can be grouped in a flexible way by configuring an external update bundle used by the state machine. The distributing of the code is based on the grouping. | 08-05-2010 |
20100217749 | Method and system for optimizing the storage of different digital data on the basis of data history - The present invention relates to optimized storage of data in digital memories ( | 08-26-2010 |
20100250492 | NETWORK ATTACHED STORAGE DEVICE AND METHOD USING SAME - A network attached storage device comprising a first file system, a first file system driver, a redirection pseudo device driver, a second file system, and a second file system driver. A method using Applicant's network attached storage device to write information to an information storage medium comprising a plurality of storage blocks. | 09-30-2010 |
20100306171 | Timeline Experience for Restore User Interface - A backup restoration system may present two or more versions of a file in a graphical user interface. A user may examine the versions to identify a desired version, and the desired version may be restored. The system may identify changed versions of the file from many stored instances of the file in the backup system, and may present the changed versions within the user interface. In some embodiments, a timeline may be presented that displays when the file was changed. Some embodiments may also highlight the changes in the display. Some embodiments may present the versions of a file in a horizontal format, where two or more versions may be viewed side by side. | 12-02-2010 |
20100306172 | UNIFIED MODEL DESIGN FOR PENDING AND PRODUCTION INFORMATION AND VERSIONED INFORMATION - A change management model-based approach can be used for managing information, such as rows of data, presenting merged information from a pending and/or production datastore with rule-based redirection to an appropriate pending and/or production datastore. Such a model can support versioning, leveraging the pending data storage; can provide for direct or merged views of the appropriate datastore; and can provide a model logic for production data updates, version updates, and/or for change context updates. A unified presentation and update model for change management can merge pending data over the production information based on the context, and allow updates on top of production/date effective versioned information. Based on various rules, the data can be pushed to production or to a change order in the context of either datastore or to a fresh change order itself. | 12-02-2010 |
20110010344 | METHODS, SYSTEMS AND DEVICES FOR PERFORMING INCREMENTAL UPDATES OF PARTIAL DATABASES - Methods, systems and devices for performing incremental updates of a partial database stored on a client device from a computer system containing the database of which the partial database is a subset. A first database record which has been inserted into, deleted from or changed in the server database as a result of a database operation is identified in order to perform a corresponding operation on the client device. In addition, a second record that has not been inserted, deleted or changed, but that is related to the first record through a constraint, is identified. The second record is inserted into or deleted from the partial database through a database operation performed on the client device such that the constraint is fulfilled in the partial database. Identification of records is based on database logs and on the structured relationship between record types. | 01-13-2011 |
20110078114 | Independently Variably Scoped Content Rule Application in a Content Management System - A content management system (CMS) synchronization mechanism synchronizes content attributes, preferably in metadata, with content documents. For each of one or more content attributes (e.g. metadata fields), a respective content document context is associated. Each attribute is synchronized to content in the content document according to the associated context. Preferably, the content document contains multiple nested files, and context limits synchronization to a subset of files. Synchronization rules, enforced by a synchronization engine, define respective attributes and content to be synchronized, each rule having an associated context in the content document. Rules are preferably created in XML format, and parsed to produce a document object model upon which the synchronization engine operates. | 03-31-2011 |
20110145195 | SYSTEMS AND METHODS FOR ACCESSING AND UPDATING DISTRIBUTED DATA - Systems and methods are disclosed that provide an indexing data structure. In one embodiment, the indexing data structure is mirrored index tree where the copies of the nodes of the tree are stored across devices in a distributed system. In one embodiment, nodes that are stored on an offline device are restored, and an offline device that comes back online is merged into the distributed system and given access to the current indexing data structure. In one embodiment, the indexing data structure is traversed to locate and restore nodes that are stored on offline devices of the distributed system. | 06-16-2011 |
20110153566 | OPTIMISTIC SERIALIZABLE SNAPSHOT ISOLATION - The subject disclosure relates to a concurrency control technique that ensures isolation among concurrently execution transactions optimistically in a multiversion database by applying two optional tests at the end of a read-write transaction: validating the visibility of the read set of the read-write transaction(s) and phantom detection by re-scanning and confirming no new version have appeared in the view. Depending on desired level of isolation, both, one or none of the test are applied. Each version of a data record in an applicable database can be assigned two timestamps indicating the lifetime the version. The value of a version timestamp, though assigned, may be conditional on a transaction committing. | 06-23-2011 |
20110167042 | CONTINUOUS INTEGRATION OF BUSINESS INTELLIGENCE SOFTWARE - A method for providing automatic version control to a business intelligence system includes receiving business metric data from a business intelligence system, creating an initial version of a business intelligence artifact derived from the received business metric data, automatically storing the initial version of the business intelligence artifact with a source control system, detecting a request to the business intelligence system to modify the initial version of the business intelligence artifact, creating a subsequent version of the business intelligence artifact that includes the requested modification, and automatically storing the subsequent version of the business intelligence artifact with the source control system. | 07-07-2011 |
20110196839 | METHOD AND SYSTEM FOR PROCESSING RAW FINANCIAL DATA STREAMS TO PRODUCE AND DISTRIBUTE STRUCTURED AND VALIDATED PRODUCT OFFERING OBJECTS - A real time information manager which processes raw data from data providers, such as feeds of current information about financial product offerings, is provided. Raw data objects received from various data providers are analyzed, formatted, and a current version of each unique data object is stored in an object storage pool. Information about the state of each objects is transmitted on a particular output data channel in accordance with the type of object. A subscriber process can access one or more of the data channels and utilize the broadcast data. In one configuration, one or more client managers are provided which subscribe to particular data channels and serve as an intermediary between the real time information manager and sets of clients. | 08-11-2011 |
20110208700 | METHOD FOR CARRYING OUT DATABASE VERSION CONTROL - The method carries out version-control of a database in a database environment including a master server storing a database, which is to be developed, one or more local servers capable of storing a local copy of the database, and a local machine for the development of the database. When a developer makes a change to the local database on the local machine, a program resident on the local machine derives a script (e.g. an SQL script) based on the change, and checks the script into the master server. The program executes the script on the master database and stores the script in a metadatabase, which can be accessed by the local servers. When a developer wishes to update a local copy of a database to a particular version, he calls up the program on the local machine, which obtains from the metadatabase those scripts necessary to incrementally change the state of the local copy to the given state. Preferably, when the script is stored on the metadatabase, the program issues an ID for the script, and the ID is stored in a table on both the master server and the local server. Preferably also, the program derives the script by comparing the changed local copy of the database with a reference copy of the original database likewise situated on the local server, and forming the script from the determined changes. Scripts may also be exported, preferably as text files, and used to update test or production servers to a required version. | 08-25-2011 |
20110252000 | IN-MEMORY DATABASE SYSTEM - A computer system includes a memory and a processor coupled to the memory. The processor is configured to execute instructions that cause execution of an in-memory database system that includes one or more database tables. Each database table includes a plurality of rows, where data representing each row is stored in the memory. The in-memory database system also includes a plurality of indexes associated with the one or more database tables, where each index is implemented by a lock-free data structure. Update logic at the in-memory database system is configured to update a first version of a particular row to create a second version of the particular row. The in-memory database system includes a non-blocking garbage collector configured to identify data representing outdated versions of rows. | 10-13-2011 |
20110282838 | AGING FILE SYSTEM - A method, programmed medium and system are provided for a file system that provides for the aging of information and files stored thereon. Digital data stored on the aging file systems ages appropriately as would normal paper or photographs without the need for an external application. The aging file system uses a number of parameters depending on what type of digital data are stored. For example, parameters like ambient temperature, rate of aging, simulated type of paper or photo paper are selected and may be input to a filing system at configuration time. The aging file system also creates and stores digital authentication certificates to provide a unique certificate number based on the aged digital information. | 11-17-2011 |
20110289056 | METHOD, NODE AND SYSTEM FOR CONTROLLING VERSION IN DISTRIBUTED SYSTEM - A method, node and system for controlling version in a distributed system. Wherein, the method includes: a management node is selected from each domain of the distributed system; one is selected as the synchronization source of the distributed system from all the management nodes, and all the management nodes synchronize the time with that of the synchronization source; all the management nodes control the time synchronization of the nodes in their own domain according to the synchronized time; the nodes of the distributed system control the version of the duplicate copy of the storage data according to the synchronized time. According to the technical scheme, it can be realized that the rough time synchronization of the distributed system, the expansibility and the practicability are improved, and the defects of the distributed system in the prior art, such as the poor expansibility and practicability, are solved. | 11-24-2011 |
20120030173 | PEER-TO-PEER SYNCING IN A DECENTRALIZED ENVIRONMENT - An apparatus and method of synchronizing a datum between a plurality of stores uses version vectors associated with the datum in each store. Each version vector has one or more entries, and each entry has an identifier and a value. The identifier identifies a store that has modified the datum, and the value indicates a number of modifications to the datum made by the store. When synchronizing the datum between stores, the version vectors of the datum are compared to determine whether one version vector is subordinate to another version vector. The datum in the store having the subordinate version vector is then replaced with the datum having the dominant version vector. When compared, a conflict resolution by a user is required if the version vectors are not identical, if the version vectors do not have all the same identifiers, and if one version vector does not contain all of the identifiers with equal or greater values of those in the other version vector. | 02-02-2012 |
20120059796 | ACCESSING DATA ENTITIES - Data entities in a client-server system are accessed. The client-server system comprises a set of clients, a server system, and a repository for storing a plurality of data entities. The server system comprises an inter-transactional cache, the inter-transactional cache being accessible for each client of the set of clients. A first client of the set of clients comprises a first intra-transactional cache. If a copy of a first data entity is in the inter-transactional cache, a version identifier of the original first data entity is read from the repository. If the copy of the first data entity is to be accessed with an exclusive lock, a copy of the copy of the first data entity is added to the first intra-transactional cache. The copy of the copy of the first data entity in the first intra-transactional cache is accessed for further processing of the first data entity by the first client. | 03-08-2012 |
20120078842 | MECHANISMS TO SUPPORT OBJECT-ORIENTED VERSION CONTROL OPERATIONS - Mechanisms to support object-oriented version control operations are provided. A user manipulates and views a project from an object viewpoint and within an object module. The user performs version control operations using object handles. The object handles are resolved to specific file references and the specific file references are used to process legacy version control commands utilizing a legacy version control system in a manner that is transparent to the user. | 03-29-2012 |
20120084257 | MASTER DATA MANAGEMENT VERSIONING - A method, system, apparatus, and article of manufacture provide the ability to maintain multiple versions of structured views of data in a computer system. A relational database management system (RDBMS) is executed that stores master data in the computer system in master RDBMS tables. The master data is hierarchical in nature and hierarchy metadata for the master data is stored in the RDBMS tables. As part of a process and framework, a series of business rules and process workflows are maintained to manage the master data. Version tables are created in the RDBMS that correspond to each of the master RDBMS tables. Each of the version tables includes an attribute denoting version information. Versions of the master data are defined by replicating the master data and hierarchy metadata into the corresponding version tables. The version tables are used to graphically visualize, manage, and manipulate the versions of the master data. | 04-05-2012 |
20120095964 | SYSTEM AND A METHOD FOR HANDLING CO-OPERATION FILES - The invention relates to a method for handling co-operation files between customers and suppliers where a unique ID is attached to the co-operation file. The customer stores co-operation files on a central file handling database and the co-operation files of the supplier are stored on a supplier computer. When a user tries to access the co-operation file stored on the supplier's storage medium, the user is informed if a version of the co-operation file stored on the central file server differs from the version of the co-operation file stored on the supplier's storage medium. | 04-19-2012 |
20120117027 | METHODS AND SYSTEMS FOR HARDWARE ACCELERATION OF DATABASE OPERATIONS AND QUERIES FOR A VERSIONED DATABASE BASED ON MULTIPLE HARDWARE ACCELERATORS - Embodiments of the present invention provide a hardware accelerator that assists a host database system in processing its queries. The hardware accelerator comprises special purpose processing elements that are capable of receiving database query/operation tasks in the form of machine code database instructions, execute them in hardware without software, and return the query/operation result back to the host system. | 05-10-2012 |
20120130952 | APPARATUS AND METHOD FOR SYNCHRONIZING DATA IN CONNECTED DEVICES - A network-connectable terminal can synchronize data in connected devices. The network-connectable terminal includes a memory unit and a synchronization unit. The memory unit stores metadata updated according to update of data. The synchronization unit updates the metadata, creates version information indicating whether the metadata are updated, and exchanges version information with peripheral devices to determine a peripheral device and data requiring synchronization. | 05-24-2012 |
20120130953 | SYSTEM AND METHOD FOR SYNCHRONIZING DATA RECORDS BETWEEN MULTIPLE DATABASES - A communication device includes a database. The database is configured to store data records to be synchronized with a host device and to store, for each record, a corresponding device synchronization parameter (DSP) and a corresponding host synchronization parameter (HSP). The DSP indicates a version number assigned to a current version, of the respective data record, as stored in the database of the device. The HSP indicates a version number assigned to a current version, of the same record, as stored in the host device. | 05-24-2012 |
20120150803 | REPLICATION RESYNCHRONIZATION - System, method, computer program product embodiments and combinations and sub-combinations thereof for replication resynchronization are provided. An embodiment includes providing a mode of operation in a replication control system for repopulating a replicated version of a primary database that does not affect an ability to continue activity in the primary database. Further included is managing the repopulating of the replicated version with attention to at least a resynchronization marker. | 06-14-2012 |
20120158658 | AUTOMATIC WIRELESS DEVICE DATA MAINTENANCE - A computer-implemented method includes downloading data elements from a wireless device. The method includes determining whether a user account exists in storage and determining whether the user account currently has stored data elements of the same type as the downloaded data elements associated therewith. The method further includes comparing the downloaded data elements to the stored data elements. This method also includes storing any downloaded data elements not currently existing in the data elements associated with the user account and not in conflict with data elements associated with the user account. The method further includes resolving conflicts between downloaded data elements and currently existing data elements, to establish which of the conflicting elements is representative of a proper version of the element. Finally, the method includes storing the proper version of the element resulting from each conflict resolution. | 06-21-2012 |
20120179654 | RESOLVING CONFLICTS IN CONTENT MANAGEMENT SYSTEMS - A conflict resolution system is described for reducing false conflicts among entities synchronized within a content management system. A typical content management system maintains a version for an entity that is incremented each time an endpoint modifies the entity, including changes that affect the metadata rather than the content of the entity. The conflict resolution system adds a new content version that is updated when the content of the entity changes. By comparing content version information, endpoints can automatically resolve false conflicts that occur when an endpoint has modified the metadata of the entity. | 07-12-2012 |
20120185435 | ORGANIZING VERSIONING ACCORDING TO PERMISSIONS - Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for storing data according to permissions. In general, one aspect of the subject matter described in this specification can be embodied in methods that include the actions of identifying a version of a data item to be stored; determining permissions associated with the version of the data item; and storing the version of the data item at a storage location that is based on the determined permissions. | 07-19-2012 |
20120284231 | DISTRIBUTED, ASYNCHRONOUS AND FAULT-TOLERANT STORAGE SYSTEM - Methods and systems for reading from and writing to a distributed, asynchronous and fault-tolerant storage system. The storage system includes storage nodes communicating with clients. The method includes a first client writing an object to the storage system and a second client reading the object from the storage system. For the first client, previous transient metadata relating to a previously written version of the object is retrieved and a new version of the object together with new transient metadata is stored. For the second client, a set of transient metadata from a third set of nodes amongst storage nodes is retrieved, a specific version of the object as stored on the storage system is determined, and a specific version of the corresponding object from a fourth set of nodes amongst storage nodes is retrieved. Two sets of nodes amongst all sets have at least one node in common. | 11-08-2012 |
20120303582 | LOCAL DIFFERENTIAL COMPRESSION - The disclosure is related to systems and methods of local differential compression. Local differential compression can allow a computer to transfer data efficiently over a limited or restricted bandwidth network. For example, a first computer can be adapted to synchronize a data object between the first computer and a second computer by: determining a list of portions of a data object to synchronize and sending the list to the second computer. When the second computer has received the list, the second computer may build the data object based on the list, data retrieved corresponding to the list, and other data already existing at the second computer. | 11-29-2012 |
20120323851 | DISTRIBUTED, ASYNCHRONOUS AND FAULT-TOLERANT STORAGE SYSTEM - Methods and systems for reading from and writing to a distributed, asynchronous and fault-tolerant storage system. The storage system includes storage nodes communicating with clients. The method includes a first client writing an object to the storage system and a second client reading the object from the storage system. For the first client, previous transient metadata relating to a previously written version of the object is retrieved and a new version of the object together with new transient metadata is stored. For the second client, a set of transient metadata from a third set of nodes amongst storage nodes is retrieved, a specific version of the object as stored on the storage system is determined, and a specific version of the corresponding object from a fourth set of nodes amongst storage nodes is retrieved. Two sets of nodes amongst all sets have at least one node in common. | 12-20-2012 |
20130031055 | PEER-TO-PEER N-WAY SYNCING IN A DECENTRALIZED ENVIRONMENT - A technique for synchronizing a datum between a plurality of stores, wherein a version history is associated with the datum in each store. The version history has one or more entries, and each entry has an identifier and a value. The identifier identifies a store that has modified the datum, and indicates a number of modifications to the datum. When synchronizing the datum between stores, the version histories of the datum are compared to determine whether one version history is subordinate to another version history. The datum having the subordinate version history is then replaced with the datum having the dominant version history. Conflict resolution is required if the version histories are not identical, if the version histories do not have the same identifiers, and if one version history does not contain all of the identifiers with equal or greater values of those in the other version history. | 01-31-2013 |
20130031056 | 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. | 01-31-2013 |
20130054528 | COMPUTER SYSTEM AND DATA ACCESS CONTROL METHOD - Proposed is a convenient computer system and data access control method which, while protecting data in a snapshot, enable restoration in operational volume file units. | 02-28-2013 |
20130103644 | WRITABLE SNAPSHOTS - Embodiments of the invention include systems and methods for providing writable snapshot functionality for file systems. Pointer-based snapshots can be taken of an active version of the file system resulting in either (1) a read-only snapshot image and a new active version of the file system resulting from a read-only snapshot operation; or (2) a read-only snapshot image and two new active versions of the file system resulting from a writable snapshot operation. The two active file systems generated from writable snapshot operations are each independently and concurrently writable. Various techniques are also presented for handling multiple, concurrently active file systems. For example, novel techniques are described for allowing snapshot restore, compaction, and other functionality to operate in an environment having multiple read-only and writable versions of the file system. | 04-25-2013 |
20130110781 | SERVER REPLICATION AND TRANSACTION COMMITMENT | 05-02-2013 |
20130117230 | Enablement of Quasi Time Dependency in Organizational Hierarchies - Changes to a hierarchical organizational structure may be stored in different versions of a data structure depicting the hierarchical organizational structure. Each of these versions may include a validity period field representing a time period that the hierarchical organizational structure depicted in the version accurately reflects the organizational structure of the organization. Each of the versions may also be designated as active or inactive. In some instances, each of the versions may be designated as inactive except for a version that reflects the organizational structure of the organization at a particular time, which may change over time. Historical copies of versions may be stored and subsequently recalled to identify an organizational structure that was in effect at a particular time in the past. The recalled version may then be used to limit the results of a query to a selected node of the historical organizational structure. | 05-09-2013 |
20130124477 | SYSTEM AND A METHOD FOR HANDLING CO-OPERATION FILES - The invention relates to a method for handling co-operation files, where the content of the co-operation files is of the type that describes the co-operation basis in relation to a co-operation between document owners and document users and where a unique hash calculated ID is attached to and embedded into a co-operation file, where the document owner stores co-operation files on a central file handling database and where the co-operation files of the document users are stored on a the user's computer. The method includes checking if a co-operation file exists on the central database with an ID matching the ID of the co-operation file stored on the document user's storage medium where the checking is initiated by the supplier trying to access the co-operation file stored on the document user's storage medium, and informing the user if a version of the co-operation file stored on the central file server differs from the version of the co-operation file stored on the document user's storage medium. | 05-16-2013 |
20130138612 | PROVISIONING AND/OR SYNCHRONIZING USING COMMON METADATA - Techniques are described herein that are capable of provisioning and/or synchronizing a data store using common metadata. For instance, a common instance of metadata may be used in lieu of multiple instances of the metadata that correspond to respective items in the data store for indicating a time at which the data store was provisioned. Each time a change occurs with respect to an item in a data table of the data store after provisioning of the data store, a record may be added or updated in a corresponding tracking table. When a request is made for changes that have occurred with respect to the items in a data table, the common instance of the metadata may be used to generate a record in the corresponding tracking table for each item in the data table that did not change since the data store was provisioned. | 05-30-2013 |
20130166509 | Version Management for Application Execution Environment - Methods, systems, and apparatus, including medium-encoded computer program products, for managing an application execution environment on a computer. One or more aspects of the subject matter described in this specification can be embodied in one or more methods of managing an application execution environment, the one or more methods including: identifying which of multiple different versions of the application execution environment are installed on a computer; and managing the different versions of the application execution environment on the computer; wherein the identifying and the managing are performed using one or more of the different versions of the application execution environment. | 06-27-2013 |
20130173546 | SYSTEMS AND METHODS FOR MIGRATING DATABASE DATA - In one general aspect, a computer-implemented method for migrating data from a source database to a target database includes a computer-implemented method that includes executing, using at least one processor, instructions recorded on a non-transitory computer-readable storage medium. The method includes ensuring that the source database has correct version information, creating an image copy of the data in the source database, and collecting metadata describing the source database. The metadata may include information used to verify that the target database is compatible with the source database, to automatically translate object identifiers, and to avert the migration if no data has changed in the source and the target databases (e.g., table and index spaces) since a previous migration. The method may further include refreshing the data in the target database using the image copy after determining that the source database and the target database are compatible. | 07-04-2013 |
20130173547 | SYSTEMS AND METHODS FOR MIGRATING DATABASE DATA - In one aspect, a computer-implemented method for ensuring a source database (e.g., target space or index space) has correct version information before a migration includes executing, using at least one processor, instructions recorded on a computer-readable storage medium. The instructions include determining whether a table has been changed since a most recent alter of the table, performing an update on the table when it is determined that the table has not been changed since the most recent alter, and performing a rollback on the table after the update. The method may also include creating an image copy of the data in the source database and refreshing data in a target database with the image copy of the data in the source database. The method may also include automatically repairing the target database when the version information of the target does not correspond with the version information for the source. | 07-04-2013 |
20130173548 | METHOD AND SYSTEM FOR BACKUP AND RECOVERY - For data backup and recovery based on linked file repositories with each of the linked file repositories representing an individual file system capable of storing at least one version of a file and being connected to at least one server system, each of the linked file repositories are placed in a certain position for storing a certain version of the file. Each position of each of the linked file repositories is continuously numbered. A number of the versions of the file are determined by the position of the one of the linked file repositories. A version-movement process over each of the linked file repositories is implemented to perform a read operation of the at least one version of the file. | 07-04-2013 |
20130185258 | UNIFIED LOCAL STORAGE SUPPORTING FILE AND CLOUD OBJECT ACCESS - A method and system for providing unified local storage support for file and cloud access is disclosed. The method comprises writing a chunk on a storage server, and replicating the chunk to other selected storage servers when necessary. The method and system further comprise writing a version manifest on the storage server; replicating the version manifest to other selected storage servers when necessary. Object puts or appends are implemented by first chunking the object, determining if the chunks are new, transferring the chunks if required, followed by creation of a new version manifest referencing the chunks. Finally, the method and system include providing concurrent file-oriented read and write access consistent with the stored version manifests and chunks. | 07-18-2013 |
20130191339 | Recognizing Cloud Content - Recognizing cloud content techniques are described herein. A designated storage location for cloud content corresponding to a service is registered locally at a device. Files stored in association with the registered storage location may be recognized as cloud content of the corresponding service. The recognized cloud content may be handled in various ways to customize the user experience and tailor interaction with cloud content. For example, icons or other visual identifiers may be used within device, operating system and/or application user interfaces to represent an association of files with a particular service based on recognition of the files as cloud content. Additionally, a registered storage location for a device may be employed to obtain relative paths to files that may be used to roam file activity lists between different devices. | 07-25-2013 |
20130191340 | In Service Version Modification of a High-Availability System - In one embodiment, an operating system kernel and/or one or more processes of a high-availability system are modified while the system is operating and providing high-availability service. In accomplishing this, one embodiment uses a second virtual machine to operate a second operating system kernel including a second set of processes in the standby mode, which receive state information from corresponding process(es) in the active mode. Individually, the operating system kernel and processes within the second set of processes may be a same or different version of their counterpart in a first virtual machine and its processes which are being replaced. When the second set of processes have acquired sufficient state information to perform the standby role, the operation of the first virtual machine is typically ceased as the version modified second virtual machine is performing the version modified functionality of the first virtual machine. | 07-25-2013 |
20130198136 | DATABASE MIGRATION - A technique for converting a first version of a database to a second version is disclosed. The technique includes determining available translation steps, selecting a translation path from the first version of the database to the second version, and executing the selected translation steps in the translation path. The translation path includes selected translation steps from among the available translation steps. | 08-01-2013 |
20130204842 | METHOD AND SYSTEM FOR SYNCHRONIZATION OF DATA EDITED IN PARALLEL - Fundamental methods, memory systems and processors systems to synchronize replicas of data by exchanging editing plans to replicas are first explained in Section 1. Other sections show derived methods and systems. Major derived methods and systems are expressed as independent claims. Section 2 shows synchronization supported by server providing relay function. Updating of replica is performed, using editing plans arranged in a sequence determined by the server. Section 3 shows synchronization supported by server providing ordinal numbers. Updating of replica is performed, using editing plans arranged in a sequence of ordinal numbers provided by the server. Section shows synchronization keeping reference consistency. Section 5 shows synchronization of edited data and edited definition of data. Even if definition of data is edited, replicas can synchronize each other. Section 6 shows synchronization by version control, which removes editing plans with old version before updating of replicas. | 08-08-2013 |
20130218839 | METHOD AND SYSTEM USING REUSABLE STATE INFORMATION FOR SYNCHRONIZATION AND MAINTENANCE OF DATA - A system for synchronization whereby metadata repository maintains information regarding the history and status of data items in a data repository. Data items are associated with states and such states changes (e.g. increment) in response to changes to the data items. History statements associated with the same states describe the changes in a generic enough fashion that multiple data items may be associated with a single state (e.g. if multiple data items share a common history such as that they were all edited by a user on the same device). The history repository is synchronized with other history repositories so as to reflect the states of data items on multiple devices. The synchronized history stores are used during synchronization to identify and resolve data conflicts through ancestry of data item history. | 08-22-2013 |
20130226872 | ON-DEMAND FILE SYNCHRONIZATION - Techniques are described for managing access and synchronization of one or more files of a document management system stored locally at a client device. The techniques may include receiving, by a document management system executing on a server device, a file update notification message from a first client device to notify the document management system that a file was modified by the first client device. The file update notification message may include an indication of the modified file on the first client device without including the modified file. The document management system may receive a file editing request from a second client device to request the file. In response, the document management system may send a file upload request to the first client device, receive the modified file from the first client device, and send the modified file to the second client device. | 08-29-2013 |
20130232115 | Quorum Based Transactionally Consistent Membership Management in Distributed Storage - Systems and methods that restore a failed reconfiguration of nodes in a distributed environment. By analyzing reports from read/write quorums of nodes associated with a configuration, automatic recovery for data partitions can be facilitated. Moreover, a configuration manager component tracks current configurations for replication units and determines whether a reconfiguration is required (e.g., due to node failures, node recovery, replica additions/deletions, replica moves, or replica role changes, and the like.) Reconfigurations of data activated as being replicated from an old configuration to being replicated on a new configuration may be performed in a transactionally consistent manner based on dynamic quorums associated with the new configuration and the old configuration. | 09-05-2013 |
20130238558 | ON-DEMAND FILE SYNCHRONIZATION - Techniques are described for managing access and synchronization of one or more files of a document management system stored locally at a client device. The techniques may include receiving, by a document management system executing on a server device, a file update notification message from a first client device to notify the document management system that a file was modified by the first client device. The file update notification message may include an indication of the modified file on the first client device without including the modified file. The document management system may receive a file editing request from a second client device to request the file. In response, the document management system may send a file upload request to the first client device, receive the modified file from the first client device, and send the modified file to the second client device. | 09-12-2013 |
20130325805 | SYSTEM AND METHOD FOR TAGGING AND SECURELY ARCHIVING PATIENT RADIOLOGICAL INFORMATION - A system and method for tagging and securely archiving patient radiological data includes computing a unique token from at least one of a plurality of data set attribute values, creating a de-identified version of the data set, writing the unique token to the de-identified version of the data set, and transmitting the de-identified version of the data set to an archive for storage. The de-identified version of the data set may be retrieved from the archive by querying and retrieving the de-identified version of the data set having the unique token written thereto. | 12-05-2013 |
20130325806 | PRESERVING A STATE USING SNAPSHOTS WITH SELECTIVE TUPLE VERSIONING - Selective tuple versioning is used on a file system providing file system snapshots using selective tuple versioning for maintaining the state of the file system. | 12-05-2013 |
20130325807 | SHARED PLAYLIST SYNCHRONIZATION - Various embodiments relating to synchronizing changes to a shared list of items between different devices are provided. In one embodiment, a first set of change operations for a first version of a shared list may be received from a first device. The first set of change operations may be performed on the first version of the shared list to produce a second version of the shared list. A second set of change operations for the first version of the shared list may be received from a second device. The second set of change operations may be performed on the second version of the shared list to produce a third version of the shared list that maintains changes that are made by the first set of change operations but that are not made by the second set of change operations. | 12-05-2013 |
20140006352 | DETERMINING A PREFERRED MODIFIED VERSION FROM AMONG MULTIPLE MODIFIED VERSIONS FOR SYNCHRONIZED FILES | 01-02-2014 |
20140040204 | AUTOMATIC OFFLINE SYNCHRONIZATION OF BROWSER DOCUMENTS - In an embodiment, a method for synchronizing browser documents is described. The method may include losing a connection to a version control server at a client device having first and second instances of a document open in first and second browser windows of a browser. The method may also include storing a first branch corresponding to the first instance of the document in local storage associated with the first browser. The first branch may indicate whether the first instance of the document is open or abandoned and one or more first changes. The method may also include the second browser window automatically determining that the first instance of the document is abandoned. The method may also include the second browser window automatically merging the one or more first changes into the second instance of the document in response to determining that the first instance of the document is abandoned. | 02-06-2014 |
20140074786 | UPDATING LOCAL DATA UTILIZING A DISTRIBUTED STORAGE NETWORK - A method begins by a device of a distributed storage network (DSN) sending read-if-revised requests to storage units of the DSN with regards to data cached in local memory with one or more local memory revision numbers. The method continues with a storage unit determining whether a revision number of one portion of the data stored by the storage unit is a more recent revision number than the one or more local memory revision numbers. When the revision number is the more recent revision number, the method continues with the storage unit sending a read response that includes the portion of the data to the device. When the revision number is not the more recent revision number, the method continues with the storage unit sending a read response that includes an indication that the data cached in the local memory is a current revision level of the data. | 03-13-2014 |
20140081917 | SEARCHING FILES - Aspects of the subject matter described herein relate to searching files. In aspects, a search engine is able to search not only the current files but also is able to search for deleted and previous versions of files that satisfy queries. The search engine may maintain an index that facilitates searches. In addition, the search engine may also determine not only that a file satisfies a query but what version(s) of the file satisfies the query. | 03-20-2014 |
20140114921 | Methods and Systems for Cloning a Cloud Node - Systems and methods for cloning a cloud node are disclosed. For example, one disclosed method for cloning a cloud node comprises identifying changes during editing of content over a predetermined interval in an author node, compiling, via a replication agent of the author node, all changes of the content identified during the predetermined interval, all of the changes compiled in a replication queue maintained by the replication agent, and at the end of the predetermined interval, providing all of the changes of the content identified during the predetermined interval from the replication queue to both the publisher node and a clone of the published node. | 04-24-2014 |
20140143208 | MAINTAINING ACCESS CONTROL LISTS IN NON-IDENTITY-PRESERVING REPLICATED DATA REPOSITORIES - Managing access control lists (ACLs) across replicated data repositories can include selecting, from a first data processing system, a controlled object and an ACL object bound to the controlled object, wherein the first data processing system is associated with a first user identity space, and creating, using a processor, a replicated version of the controlled object within a second data processing system associated with a second user identity space, wherein the second user identity space is different from the first user identity space. Managing ACLs further includes, creating, using the processor, a replicated version of the ACL object within the second data processing system and substituting, within the replicated version of the ACL object, an identity from the first user identity space with a selected identity from the second user identity space. | 05-22-2014 |
20140172799 | METHOD AND APPARATUS FOR SYNCHRONIZATION OF ITEMS WITH READ-ONLY PERMISSIONS IN A CLOUD-BASED ENVIRONMENT - Techniques are disclosed for enabling synchronization of items (e.g., folders or files) with read-only permissions in a cloud-based environment. In one embodiment, a method comprises, upon receiving a request from a collaborator to synchronize an item stored in the workspace, determining whether the item is marked as read-only and verifying if the collaborator has permission for downloading the item. The method further comprises, if the item is marked as read-only and if the collaborator has permission for downloading the item, sending the item to the collaborator. The method further comprises synchronizing the item by automatically pushing an updated version of the item unilaterally from the cloud-based environment to the collaborator regardless of whether the collaborator has performed any modification to the sent item. Among other advantages, embodiments disclosed herein provide capabilities to synchronize read-only files/folder in cloud-based platforms, especially where items are often opened/edited among the collaborators. | 06-19-2014 |
20140172800 | Updating A File Using Differences and File Format Therefor - A method for updating and formatting a local file is described. An update file, having a newer version of the local file, is accessed from a server over a network and a list of new hash values corresponding to data blocks of the update file is retrieved. Divisions between the data blocks are located when a value of a rolling checksum reaches a particular value, the data blocks being of variable size. New hash values of the update file are compared with local hash values of the local file. For each of the new hash values not having a matching local hash value, the corresponding data block is downloaded from the server and written to a new file. For each of the new hash values having a matching local hash value, the corresponding block is copied from the local file to the new file. | 06-19-2014 |
20140188803 | SYSTEMS AND METHODS FOR AUTOMATIC SYNCHRONIZATION OF RECENTLY MODIFIED DATA - The present disclosure describes systems and methods for automatic synchronization of recently modified data between a plurality of devices. A device may identify newly utilized files stored on the device, and a synchronization engine may synchronize these files to one or more additional devices. The synchronization engine may record a storage location of the files on the first device, and may transmit the files for storage in a hidden directory on the other devices. After modification, a file may be synchronized back to the initial device. The synchronization engine on the initial device may retrieve the storage location of the modified file, and may replace the previous version of the file with the newly received modified file, in the original storage location. The user may view and edit recently utilized files on any device, while maintaining their original storage locations on each device and without having to manually manage files. | 07-03-2014 |
20140201148 | INFORMATION PROCESSING APPARATUS, METHOD AND MEDIUM - Provided is an information processing apparatus including: a setting unit that sets, for electronic documents, a document ID by which an older version or a newer version can be determined among a plurality of sequential electronic documents; a linking unit that links attachment information to an electronic document; a request accepting unit that accepts a request for an electronic document; an attachment information acquiring unit that, in response to acceptance of the request for the electronic document, acquires the attachment information linked to an electronic document of which version is older than the electronic document related to this request based on the document ID; and a response outputting unit that outputs the electronic document related to the request and the acquired attachment information. | 07-17-2014 |
20140222758 | Coherent File State Maintained Among Confederated Repositories By Distributed Workspace Apparatuses Backed Up By a File State Ledgerdemain Store - Each one of many networked user workstation apparatuses may commit a file into the variant controlled file system by storing a version tracking record for each change log and content point for each block of the file into its local file system view store, and transmitting a version tracking record to a network attached file state ledgerdemain store. Each user workstation displays a file system view of every variant of every file in the file system for selection. When required, the workstation applies change logs to content points according to first a local file system view store for a version tracking record, then requesting and comparing version tracking records from confederated repositories at other user workstation apparatuses, and if unsatisfied, obtains a version tracking record from a network attached file state ledgerdemain store. | 08-07-2014 |
20140250074 | FORGETTING ITEMS WITH KNOWLEDGE BASED SYNCHRONIZATION - Systems and methods that enable removal of data from an endpoint, while not propagating such removal to other endpoints when synchronizing data sources associated therewith. A designation component can indicate items as forgotten items, wherein such items are being known to an endpoint and deleted therefrom—yet, reintroduced therein and reappearing (e.g., as a create) upon re-synchronizing with the replica over again. Moreover, the forgotten items can employ additional metadata such as in from of an additional bit that indicates whether an item is a forgotten item. | 09-04-2014 |
20140258234 | SYNCHRONIZATION OF CMS DATA TO MOBILE DEVICE STORAGE - Aspects include systems and methods for synchronizing a remote datastore that includes files and data for use by an application on a remote device, which can be represented on the device in a device-specific format, while the remote data store can have a different data representation, such as a relational database or object graph data model. A server can maintain a unique row identifier for each row in all synchronized tables and an update log table that has rows with the unique row identifiers for changed rows (inserted, updated or deleted), for each insert, update, or delete operation and a current update version that reflects the last change to that row. An update request from a device can comprise identifiers for a (sub)set of the data. The update log table can be used to prepare an update package containing this data. | 09-11-2014 |
20140279903 | VERSION CONTROL SYSTEM USING COMMIT MANIFEST DATABASE TABLES - A centralized version control system stores and tracks commits as a set of database tables in a central repository that may be shared by others. A commit represents a version of a repository of files at a given point in time. The centralized version control system allows users to query for information relating to the history of the commits. The queries are implemented through operations performed on database tables using a database query language. The configuration of the database tables in this manner enables the system to process the queries more readily. | 09-18-2014 |
20140279904 | 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 |
20140289199 | EXTENSIBLE AND QUERYABLE STRONG TYPES - Data type configuration data is expressed and deployed to a database system to obtain a relational representation of the data types in addition to the compile code representation. Users or developers extend the data types by adding data to the relational representation, and the runtime environment operates off of the relational representation. Because the data types are extended (such as by creating new entities) using the data type tables in the relational representation, the extensions obtain the benefits of the type checking performed at compile time. | 09-25-2014 |
20140289200 | CONTROL METHOD, AND INFORMATION PROCESSING SYSTEM - A control method is used in an information processing system which has a plurality of computers. The control method includes receiving, by a first computer of the plurality of computers, an update request of data from a first client device, receiving, by a second computer of the plurality of computers, a read request of the data from a second client device. The control method also includes selecting, by the second computer, a computer as an query destination from the plurality of computers excluding the first computer and a third computer that is a terminal to receive the update request sent from the first computer, when the data is undergoing updating due to the update request; transmitting a verify request to inquire whether the data is undergoing updating, to the query destination; and transmitting the data to the second client device based on a reply from the query destination. | 09-25-2014 |
20140297592 | COMPUTER-READABLE MEDIUM STORING PROGRAM AND VERSION CONTROL METHOD - An information processing apparatus permits editing of information held by an existing node in a version control graph that contains a plurality of nodes, each of which is assigned an identifier corresponding to information held by the node. The information processing apparatus detects, upon merging a first branch and a second branch contained in the version control graph, a previous merged data set that is generated from a data set of a first version referred to by a node of the first branch and a data set of a second version referred to by a node of the second branch, on the basis of history information. The information processing apparatus generates a new merged data set by merging the first branch and the second branch, using the detected merged data set. | 10-02-2014 |
20140330783 | Method and System for Stateful Recovery and Self-Healing - The ability to perform non-destructive editing of files and models requires the generation and persistence of input deltas that capture changes that are made to a base starting point. Reconstitution of saved state may be achieved through the application of deltas. This capability is useful for failover remediation in client/server environments since the client has access to the deltas, such that in the event that a stateful service becomes unresponsive (and therefore, no longer available), the service may be taken offline and a new resource may be assigned as a replacement. In such an event, the service is directed to load the baseline data and any changes may be reapplied, restoring the service state. | 11-06-2014 |
20140358860 | Sync Framework Extensibility - Embodiments described herein may involve enabling applications to cooperate with a system-level sync framework. The sync framework may provide system synchronization of files between user devices and a cloud storage service. Arbitrary applications on a user computing device can communicate with the sync framework to temporarily suspend synchronization of a specified file by the sync framework. The application can register functions with the sync framework that the sync framework can invoke in relation to suspending synchronization, continuing to provide system-level access to the file for arbitrary applications, and resuming synchronization. | 12-04-2014 |
20140358861 | MANAGING A MULTI-VERSION DATABASE - Managing different versions of a data record is provided. A mapping is maintained between a version-independent logical record identifier and a version-dependent physical record row identifier that correspond to each data record within a plurality of data records of a data table using a logical record identifier to physical record row identifier indirection mapping table. Entries within leaf pages of an index associated with the data table are updated to point to the version-independent logical record identifier corresponding to a data record instead of pointing to the version-dependent physical record row identifier corresponding to the data record. The logical record identifier to physical record row identifier indirection mapping table is updated in response to performing an operation on the data record instead of updating the entries within the leaf pages of the index associated with the data table. | 12-04-2014 |
20140379656 | System and Method for Maintaining a Cluster Setup - Methods and systems are directed to a maintenance procedure in a production environment comprising a primary database and a secondary database. Production data may be stored in the primary database and failover data may be stored in the secondary database. Data from the primary database may be replicated to the secondary database. The maintenance procedure may provide for modification of the primary database and the secondary database to conform to one or more modified requirements of a modified version of the application. During the maintenance procedure, data in the databases may be duplicated, data structures may be modified, and modification of certain data elements may be prohibited. | 12-25-2014 |
20140379657 | Document Provenance Scoring Based On Changes Between Document Versions - A computer-implemented method, system and computer program product is provided for optimizing a document change or provenance scoring system by weighting sections of a document, scoring the changes for each section, and then combining the change scores for each section to generate an overall change score. An associated report may also be generated that catalogs all of the various scoring elements. The weighted score is stored in a document management system and provides a human document reviewer a level of detail to evaluate document changes. Accordingly, the weighted score reveals whether a document's changes require a brief or detailed review before the document's changes are approved for a next document version. | 12-25-2014 |
20150012494 | SYSTEM AND METHOD OF PERFORMING CONTINUOUS BACKUP OF A DATA FILE ON A COMPUTING DEVICE - The described embodiments relate to devices for performing continuous backup of a data file on a computing device. The computing device transmits, to a backup server, a first network backup version of the data file, when the backup server is constantly available to the computing device through an uninterrupted network connection. The computing device monitors the data file to detect when a modification has been made to the data file, and when a modification to the data file has been detected, the computing device refrains from transmitting backup data associated with the modification until a network time interval expires. During the network time interval, a delta file corresponding to the modification made to the data file is stored locally on the computing device. Upon expiry of the network time interval, the computing device then transmits a second network backup version of the data file to the backup server. | 01-08-2015 |
20150026131 | DATA AVAILABILITY DURING COLUMNAR TABLE MERGES - Improved availability of data in columnar tables can be provided via use of additional data structures, such as for example a second delta part, a shadow second delta part, and a second main part, that are employed during a merge operation of a first delta part into a main part. Related apparatus, systems, techniques and articles are also described. | 01-22-2015 |
20150032698 | HISTORICAL VIEW OF OPEN FILES - Managing versions of an electronic entity comprising many independently managed, but mutually-dependent, subcomponents can be challenging. File management functionality is provided for use with an integrated development environment to produce a visual indication of the relationships among the subcomponents. The approach described herein provides an improvement over source code control systems and backup systems in the ability to revert the state of one or more files as their content existed at an historical time point. The technique does not require a user to predict in advance at which time points the content state of one or more files will be interesting as historical time points for future use. | 01-29-2015 |
20150039561 | MERGING DATA VOLUMES AND DERIVATIVE VERSIONS OF THE DATA VOLUMES - Disclosed are systems, methods, and software for performing version control. In a particular embodiment, a non-transitory computer readable medium is provided having stored therein program instructions that, when executed by a computer system, direct the computer system to perform a method of version control. The method includes executing a plurality of virtual machines from a plurality of derivative versions of an ancestor data volume, wherein the ancestor data volume and the plurality of derivative versions each comprise a plurality of files. The method further includes tracking modifications to the plurality of files in each of the plurality of derivative versions and merging the plurality of derivative versions with the ancestor data volume based on the modifications. | 02-05-2015 |
20150046401 | FILE DELETION DETECTION IN KEY VALUE DATABASES FOR VIRTUAL BACKUPS - A method, article of manufacture, and apparatus for protecting data. In some embodiments, this includes receiving a changed block, reading a previous backup to get a file list in change block tracking, checking a file in a modified master file table list for a reference flag, wherein the modified master file table list is based on the changed block, and modifying a database entry based on the reference flag. | 02-12-2015 |
20150052107 | OBJECT DEPENDENCY MANAGEMENT - A method for object dependency management for historical access includes assigning versions to states of a structure for storing objects, and assigning the versions to dependency changes between the objects. The method further includes managing historical access to the objects based on an analysis of the versions and the dependency changes between the objects. | 02-19-2015 |
20150066855 | OUTCAST INDEX IN A DISTRIBUTED FILE SYSTEM - An outcast index in a distributed file system is described. A first server can receive an indication that a first replica stored on the first server is to be modified in view of a second replica stored on a second server. The first replica and the second replica are replicas of a same file. The first server updates metadata associated with the first replica to indicate an outcast state of the first replica. The first server receives an indication that the modification of the first replica is complete. The first server updates the metadata associated with the first replica to remove the outcast state of the first replica. | 03-05-2015 |
20150081635 | DOCUMENT MANAGEMENT SYSTEMS AND METHODS - A system for managing files over a network comprises a first computer hosting managed folders and files and one or more second computers. The first computer comprises database management software, server software such as server pipe software, and a first unique token. The second computer comprises a software module adapted and configured to be integrated into application software, client software such as client pipe software, and a second unique token. The computers communicate in part using the server and client software to establish a secure session for file access and transfer between the first and second computers. | 03-19-2015 |
20150100549 | EXTENDING A CONTENT REPOSITORY USING AN AUXILIARY DATA STORE - According to one embodiment of the present invention, a system extends a content repository by creating an auxiliary data store outside of the content repository and storing auxiliary data in the auxiliary data store, wherein the auxiliary data is associated with a collection of documents in the content repository. The system stores version information for the auxiliary data store and records of operations against the auxiliary data store in a log in the repository. In response to receiving a request for an operation against the auxiliary data store, the system determines that the auxiliary data store and repository are consistent based on the version information and applies the operation against the auxiliary data store. Embodiments of the present invention further include a method and computer program product for extending a content repository data model in substantially the same manners described above. | 04-09-2015 |
20150100550 | EXTENDING A CONTENT REPOSITORY USING AN AUXILIARY DATA STORE - According to one embodiment of the present invention, a system extends a content repository by creating an auxiliary data store outside of the content repository and storing auxiliary data in the auxiliary data store, wherein the auxiliary data is associated with a collection of documents in the content repository. The system stores version information for the auxiliary data store and records of operations against the auxiliary data store in a log in the repository. In response to receiving a request for an operation against the auxiliary data store, the system determines that the auxiliary data store and repository are consistent based on the version information and applies the operation against the auxiliary data store. Embodiments of the present invention further include a method and computer program product for extending a content repository data model in substantially the same manners described above. | 04-09-2015 |
20150106332 | TIME SERIES DATA PROCESSING DEVICE, TIME SERIES DATA PROCESSING METHOD AND TIME SERIES DATA PROCESSING PROGRAM STORAGE MEDIUM - Provided is a time series data device with which, when a process is changed, results of both a new and an old process are not outputted to the outside being mixed, and the results of the old process before and after the process is changed can be outputted to the outside. The device is equipped with: a first processing unit that executes a first process and outputs first results data; a second processing unit that executes a second process and outputs second results data; and a control unit that, when an instruction to change a process is received, determines whether the first process can be stopped, and generates first and second results data sets by appending identification information corresponding to process contents to the respective first and second results data. | 04-16-2015 |
20150106333 | APPLICATION UPDATE SYSTEM, METHOD AND COMPUTER PROGRAM PRODUCT - In accordance with embodiments, there are provided mechanisms and methods for storing documents that are being tracked in an on-demand service. These mechanisms and methods for storing documents in an on-demand service can enable embodiments to provide the sharing of documents and the storing of the documents in association with a tag. The ability of embodiments to provide the sharing of documents and the storing can enable an efficient searching for a shared document. In an embodiment, the shared document is categorized upon being stored. | 04-16-2015 |
20150120663 | METHOD OF DATA STORING AND DATA SYNCHRONIZATION IN A DISTRIBUTED DATA STORAGE SYSTEM - The present invention generally relates to distributed data storage systems, where different devices manipulate data shared by these devices. In particular, the technical field of the present invention is to related storing of data in a distributed data storage system and associated data synchronization for devices connecting to such a system. | 04-30-2015 |
20150120664 | SYNCHRONIZATION OF WEB SERVICE ENDPOINTS IN A MULTI-MASTER SYNCHRONIZATION ENVIRONMENT - A Web service synchronization protocol is provided that sets forth the metadata and messaging by which endpoints roam, share and synchronize common information with one another in a multi-master networked computing ecosystem. A general SOAP-based protocol is defined for synchronizing data between two endpoints where one or more of the endpoints supports a Web service. Defining messaging for knowledge-based transfers using XML Web services, the protocol allows devices, services and applications to synchronize through firewalls, allows for flexibility by allowing any common set or subset of information across endpoints and allows for extensibility by not prescribing the schema of the actual data being synchronized at the endpoints. | 04-30-2015 |
20150134614 | DETERMINING A PREFERRED MODIFIED VERSION FROM AMONG MULTIPLE MODIFIED VERSIONS FOR SYNCHRONIZED FILES - A server stores files and manages the synchronization of those files across client devices in accordance with user preferences that may be embodied in change management rules. A first version of a file has been designated to be synchronized across at least a first client and a second client. The first client accesses the first version of the file and creates a first modified version of the file, and the second client accesses the first version of the file and creates a second modified version of the file. When the first and second clients attempt to re-synchronize their respective modified versions of the file, the server determines a preferred version from among the available modified versions of the file according to change management rules. Then, the preferred version is stored by the server and is subsequently served for synchronization across the client devices. | 05-14-2015 |
20150347408 | MANAGING RECORDS IN A TRAVEL MANAGEMENT SYSTEM - Methods, apparatus, and computer program products for managing an extended record data structure in a content management system. A plurality of records are stored in an extended record data structure that include first data containers containing standard data elements and second data containers containing non-standard data elements. A record identifier is assigned to each record in the extended data structure for which one or more of the standard data elements and one or more of the non-standard data elements are related. For each record, an entry is created in an auxiliary data structure. The entry shares the record identifier of the record and comprises an auxiliary data container. The auxiliary data container includes a set of attributes related to the first and second data containers sharing the same record identifier in the record data structure. The extended record data structure is managed based on the auxiliary data structures. | 12-03-2015 |
20150347550 | WIRELESS CONTENT SYNCHRONIZATION - Mobile devices that perform synchronization operations are configured to reduce the amount of data that must be synced to perform a media content sync operation over a wireless connection. The sync operation is implemented as a two-phase arrangement, synchronizing first in a metadata sync operation and then in a media content sync operation. The source device transmits to the destination device a last known version number of the music database that was synced to the destination device and a current version number of the media database at the source device. In response to a failure of the network connection before completion of the metadata sync operation, upon establishment of a second network connection between the source device and destination device, the metadata sync is completed only for any version numbers that indicate a version subsequent to the last version number that was synchronized over the first network connection. | 12-03-2015 |
20150363452 | HYBRID DATABASE UPGRADE MIGRATION - According to some embodiments, it may be determined that a plurality of hybrid database version upgrade migrations are to be performed. Each upgrade migration may include, for example, a schema change portion and a data change portion. A first database migration tool instance may be automatically run to perform the upgrade migration schema change portions. Similarly, a second database migration tool instance may be automatically run to perform the upgrade migration data change portions, wherein the second instance is not run until the first instance is complete. | 12-17-2015 |
20150363458 | SYSTEMS AND METHODS FOR MIGRATING DATABASE DATA - In one aspect, a computer-implemented method for ensuring a source database (e.g., target space or index space) has correct version information before a migration includes executing, using at least one processor, instructions recorded on a computer-readable storage medium. The instructions include determining whether a table has been changed since a most recent alter of the table, performing an update on the table when it is determined that the table has not been changed since the most recent alter, and performing a rollback on the table after the update. The method may also include creating an image copy of the data in the source database and refreshing data in a target database with the image copy of the data in the source database. The method may also include automatically repairing the target database when the version information of the target does not correspond with the version information for the source. | 12-17-2015 |
20150379063 | SYSTEM FOR MANAGING IFC VERSION SYNCHRONIZED WITH BIM AND METHOD FOR MANAGING IFC VERSION THEREOF - The present invention relates to a system for managing IFC versions by comparing two or more IFC files produced with a time interval therebetween so as to trace the alteration history, and to a method for managing the IFC file version thereof. A system for managing the IFC versions includes: a comparison target processing unit for acquiring first IFC file attribute information concerning a first IFC file and second IFC file attribute information concerning at least one second IFC file; a GUID comparison engine for comparing a first IFC file GUID set containing first IFC GUIDs with a second IFC file GUID set containing second IFC GUIDs; and a spatial object comparison engine for comparing a first IFC file spatial object information set containing first IFC file spatial objects with a second IFC file spatial object information set containing second IFC file spatial objects. | 12-31-2015 |
20160012070 | METHODS FOR MANAGING A REQUEST TO LIST PREVIOUS VERSIONS OF AN OBJECT AND DEVICES THEREOF | 01-14-2016 |
20160048570 | PROCESSING MUTATIONS FOR A REMOTE DATABASE - Methods, systems, and apparatus are described for processing mutations for a remote database. In one aspect, a method includes receiving a log of database mutations from a client device, the log of database mutations indicating changes previously made to a client version of a database stored on the client device, and each database mutation specifying: an entity included in the database; an operation for the entity; and a client version number for the entity; identifying, in the log of database mutations, two or more database mutations that each specify a same client version number for a same entity; determining, based on a conflict resolution policy, that the two or more database mutations are eligible for collapsing; and collapsing the two or more database mutations into a single database mutation. | 02-18-2016 |
20160070717 | SYNCHRONIZATION AND STRATEGIC STORAGE OF MULTIPLE VERSIONS OF A FILE - Disclosed are some examples of systems, methods and storage media for synchronizing files between a user's computer and a remote system, and more specifically, to strategically storing updated versions of a file on the remote system. In some implementations, a system is capable of receiving a request including an updated version of a file. The system is additionally capable of identifying a version type of the updated version, identifying a current version of the file stored in one or more storage devices, and determining, based on the version type of the updated version, whether to store the updated version in the one or more storage devices as a new version or to replace the current version with the updated version. The system is further capable of storing the updated version in the one or more storage devices based on the determination. | 03-10-2016 |
20160085838 | METHOD AND SYSTEM FOR DOCUMENT SYNCHRONIZATION IN A DISTRIBUTED SERVER-CLIENT ENVIRONMENT - A method and system for synchronizing documents in a distributed server-client environment. The system includes a synchronization server, a distributor client, a user client, and/or a network connecting the server and the clients. The method includes the steps of wrapping synchronization information such as document ID and version number in a synchronized document, storing the synchronized document and the synchronization information in a synchronization server, and comparing the local version with the version stored in the sync server if a latest version is to open, and if the local version is not the latest version, accessing the latest version document by receiving the document from the synchronized server. | 03-24-2016 |
20160098423 | ASYNCHRONOUS MULTI-NODE FILESYSTEM COORDINATED REPLICATION - A system for replicating a filesystem running on multiple nodes comprising an originator system and a replica system. The originator system includes a plurality of nodes. The replica system includes a plurality of nodes and a processor. The plurality of nodes of the replica system are paired with the plurality of nodes of the originator system. The processor is configured to receive an indicator of a node of the plurality of nodes of the replica system finishing replication for a view of a filesystem at a point in time. The processor is further configured to indicate that replication for the view of the filesystem is complete in the event that all replica system nodes have received their indication for the view. | 04-07-2016 |
20160103829 | SUPPORTING TRANSIENT SNAPSHOT WITH COORDINATED/UNCOORDINATED COMMIT PROTOCOL - Methods and a system are provided. A method includes maintaining an in-page log for records in each of a plurality of data pages of a multi-version database. The method further includes adding record update information to the in-page log when a corresponding one of the records is deleted or updated. The method also includes consulting the in-page log for a recently updated one of the records or a recently deleted one of the records to determine a record status thereof. The method additionally includes spilling, by a processor-based overflow manager, to overflow pages when the in-page log is full. The data pages include any of row-oriented data pages and column-oriented data pages. | 04-14-2016 |
20160117375 | Online Schema and Data Transformations - Transforming a database while allowing the data in the database to be available to database users during the transformation of the database. A method includes creating a new version of metadata for an old copy of database items. The method further includes creating a copy of data items to be transformed in the old copy of database items while applying a transformation to the data while migrating data from the old copy of database items to the new copy of database according to the new version of metadata. The method further includes while migrating data from the old copy of database items to the new copy of database items, servicing user queries made against the old copy of database items to allow the database to remain online while transforming data items in the database. | 04-28-2016 |
20160125000 | HISTORY PRESERVING DATA PIPELINE - A history preserving data pipeline computer system and method. In one aspect, the history preserving data pipeline system provides immutable and versioned datasets. Because datasets are immutable and versioned, the system makes it possible to determine the data in a dataset at a point in time in the past, even if that data is no longer in the current version of the dataset. | 05-05-2016 |
20160134490 | MANAGING EVENT METRICS FOR SERVICE MANAGEMENT ANALYTICS - A method of managing event metrics for service management analytics. The method includes: determining, by a computer processor, whether a record associated with service level management needs to be versioned based on metric metadata; if so, capturing, by the computer processor, present state of the record; versioning, by the computer processor, the captured present state of the record; summarizing and aggregating, by the computer processor, the versioned record; generating, by the computer processor, snapshots of the summarized and aggregated records; and attaching, by the computer processor, reference attributes to the snapshots. | 05-12-2016 |
20160162560 | PROVIDING AN ELECTRONIC BOOK TO A USER EQUIPMENT - In a method executable on a server a version of an electronic book is provided to a user equipment, the electronic book comprising media content provided as sequentially arranged sections and including at least one tag, each of which is being representative of an associated annotation, where each annotation comprises additional media content. The method comprise: identifying, in a request received from a first user equipment, a first version of an electronic book, at least one additional version of the electronic book, a first end user and the first user equipment as a user equipment on which an end user requires presentation of the electronic book; synchronizing the media content of the first version of the electronic book and the at least one tag with associated content of said at least one additional version of the electronic book, and identifying and transmitting, sequentially, to the first user equipment, media content of the first version of the electronic book together with any identified associated tag, wherein, in response to identifying a request received from the first user equipment indicating a selection of one of said tags, the method further comprises identifying and transmitting, to a preferred user equipment, an annotation associated with the selected tag, such that the annotation can be presented to the end user on the preferred user equipment. A method is also provided for generating tags and associated annotation such that each generated tag/annotation is selectable upon presentation of associated media content on a user equipment. | 06-09-2016 |
20160196262 | METHOD AND SYSTEM FOR BACKUP AND RECOVERY | 07-07-2016 |
20160197996 | MASSIVELY SCALABLE OBJECT STORAGE SYSTEM | 07-07-2016 |
20160253352 | METHOD AND APPARATUS FOR FILE SYNCHRONIZATION AND SHARING WITH CLOUD STORAGE | 09-01-2016 |