Abstract: A method of processing files changes includes obtaining a change list of a designate folder, wherein the designate folder includes a plurality of sub-files changed in a time segment and the change list indicates filenames, pathnames and change times corresponding to the plurality of sub-files, determining whether a system time minus a last change time indicated by the change list is greater than a time threshold, and executing a process of determining file actions according to the change list to store a process result in a file action list when the system time minus the last change time indicated by the change list is greater than the time threshold.

Abstract: An embodiment of the invention provides relative bookmarks that are sharable between developers engaged in product development utilizing integrated design environment applications. The relative bookmarks are sharable in that they can be exported, imported, activated and deactivated. The relative bookmarks are relative in that they do not rely on the original code line and contain at least function and/or data flow information, facilitating quick identification of relevant lines of code that have been previously bookmarked. The relative bookmarks can also be utilized to insert breakpoints.

Abstract: An embodiment of the invention provides relative bookmarks that are sharable between developers engaged in product development utilizing integrated design environment applications. The relative bookmarks are sharable in that they can be exported, imported, activated and deactivated. The relative bookmarks are relative in that they do not rely on the original code line and contain at least function and/or data flow information, facilitating quick identification of relevant lines of code that have been previously bookmarked. The relative bookmarks can also be utilized to insert breakpoints.

Abstract: Arrangements are provided which improve the efficiency of the synchronization process. The same ensure that synchronizations of large quantities of content can be completed with a minimum of delay. One method prioritizes the various tasks that are to be performed prior to synchronization. Another method initiates dependent tasks while parsing a synchronization tasks list. Yet another method allows modification of an in-process synchronization operation to allow new synchronization tasks to be accomplished within the context of the same process, negating the need to restart synchronization.

Abstract: A new approach is proposed that contemplates systems and methods to support backing up only portions of data associated with a virtual machine that have been changed since the last backup of the data was performed. During a backup process, the proposed approach looks for a journal record of a file system located within one of the partitions on a virtual disk of the virtual machine, wherein the journal record reflects disk operations that have been performed to a storage device associated with a host device/machine running the virtual machine. Once portions of the storage device which data have been modified since the last data backup are identified based on the journal of the file system, only the modified portions of the storage device are submitted to the backup process to be backed up to a backup storage device.

Abstract: The disclosed technology can enable application data to be stored with an online content management system. In some embodiments, a user's application installed on a first computing device can send application data, such as current state information of the application, to be stored on the network service. If the user's application is also installed on at least a second computing, then the application data (e.g., current state information) stored with the content management system can be transmitted to at least the second computing device, thereby causing the application data for the user's application to be synced with respect to both the first device and the at least the second device. As such, data for the user's application can be synced among multiple, different platforms (e.g., computing devices running different operating systems). Moreover, the disclosed technology can provide approaches to managing conflicts among application data to be synced.

Abstract: A computer that is programmed with collaboration software receives a change to be made to an object that can be of any type among several predetermined types such as message, document, contact, discussion and meeting. The object is represented as an aggregate of identifiable parts shareable by users, including at least a content part, a lock part, and an access-control part. Each version of the object is represented by a set of identifiers of these parts. In response to receipt of information identifying the change, the computer automatically identifies a specific part to be changed from among multiple parts of the object. Thereafter, the computer automatically creates a new instance of the specific part which contains the change as per the received information. The computer automatically stores a new version of the object as a new set that includes a new identifier of the new instance of the specific part.

Abstract: A computer that is programmed with collaboration software receives a new value of an attribute (or property or characteristic) which is specific to a label (or tag or category) as applied to an object managed by the computer. The computer does not use the new value to overwrite a corresponding old value in existing metadata. Instead, the computer is programmed to hold the new value in an incremental label application for the object. The computer is further programmed to respond to a request for the object's label application, by retrieving the incremental label application, and a full application of said label to said object. The computer uses attribute values in the incremental label application to update corresponding attribute values in a copy of the full label application, in a time sequence based on the time of creation of incremental label applications, thereby to generate a current label application.

Abstract: Implementations of the present disclosure are directed to a method, system, and storage media for receiving an indication that an attempt to make a modified first version of a directory a current version of the directory in a file system using a consensus protocol did not succeed and, in response thereto, obtaining a most recent second version of the directory including second pointers and a second name associated with each of the second pointers, wherein each second pointer is a reference to an immutable data object in the file system; and identifying one or more of the second names, each identified second name being the same as one of the first names but being associated with a second pointer that is different than the first name's respective first pointer, and obtaining for each identified second name, the data object referenced by the respective second pointer from the file system.

Abstract: A method in one example implementation includes extracting a plurality of data elements from a record of a data file, tokenizing the data elements into tokens, and storing the tokens in a first tuple of a registration list. The method further includes selecting one of the tokens as a token key for the first tuple, where the token is selected because it occurs less frequently in the registration list than each of the other tokens in the first tuple. In specific embodiments, at least one data element is an expression element having a character pattern matching a predefined expression pattern that represents at least two words and a separator between the words. In other embodiments, at least one data element is a word defined by a character pattern of one or more consecutive essential characters. Other specific embodiments include determining an end of the record by recognizing a predefined delimiter.

Abstract: Embodiments relate to a method and computer program product for generating a composite simulated model. A method includes receiving a specification request for generating a set of target time-series data from a set of source time-series data and obtaining specification information relating to the set of source time-series data, obtaining specification information relating to the set of target time-series data, and obtaining the source time-series data. The method also includes comparing the source and target specification information to determine if the set of source time-series data are time-aligned with the set of target time-series data and converting the set of source time-series data to the set of target time-series data upon determination that time alignment is needed.

Abstract: Techniques are disclosed for race condition handling in a system which incrementally updates clients with what occurred in a cloud-enabled platform. In one embodiment, a method comprises, in response to an event received at a synchronization client which indicates a modification to an item, comparing a sequence identifier of the item in the event with a current sequence identifier of the item. The sequence identifier of the item can be numeric and can monotonically increase as a state of the item changes. The method further comprises, if the sequence identifier in the event is larger than the current sequence identifier of the item, determining a difference between the item's state as represented in the event and a current state of the item; and, based on the difference, generating at least one synchronization step to update the current state of the item to the item's state as represented in the event.

Abstract: A computer readable storage medium includes executable instructions to store load data in new rows of an append only table within a data warehouse, without updating or deleting existing rows in the append only table. The new rows are added in a database transaction that guarantees that the distributed reads and writes of all transactions are processed reliably and that the transactions obey snapshot isolation rules. Data changes associated with the load data are maintained in a separate update table. Data from the append only table is merged with data changes from the update table to supply read data.

Abstract: A file server is coupled to a plurality of user terminals and a remote file server. The file server, stores, in a storage device, data of files received from the plurality of user terminals, replicates the files to the remote file server, stubs the files stored in the storage device, and, upon receiving an access request from the user terminal, reads out data of the file from the storage device and transmits the data to the user terminal if a file related to the access request is not stubbed, and, recall data of the file from the remote file server and transmits data of the file to the user terminal if a file related to the access request is stubbed. The file server replicates, to the remote file server, data of a user who performs a session disconnection request to the file server within a certain time in preference to another user.

Abstract: Architecture for multi-level undo on a client in grid-based applications. The architecture is a control driven cascading changes system where change tracking works seamlessly in asynchronous (and synchronous) scenarios. A client application is associated with a grid object and, instantiates and configures the grid object. The application can initiate a change to data in the grid and/or the user can edit the data in the grid directly. A result of the change is a notification to the application, the notification including an order key. The application consumes the notification and can then append new changes based on synchronous or asynchronous computations by calling an update function using the order key. The application uses the key to attach further updates which are properly collected together for undo/redo.

Abstract: Methods and systems for synchronizing data files in a storage network between a first and a second storage device is provided. The method includes storing first data files associated with the first storage device to a storage medium, whereby the first data files include first data records. The storage medium may then be transferred to the second storage device. The first data files from the storage medium may be loaded onto the second storage device. The second data records from the first storage device may be received, and the first and second data records are compared. The first data files at the second storage device may be updated based on the comparison of the first and second data records.

Abstract: A transference control apparatus includes a communication controller, and a processor that executes a procedure, the procedure including processing a control that causes first processing, in which an update log representing the update content of updating performed for a first database is transmitted, by the communication controller, to a second database serving as a copy destination for the first database, to be performed with priority over second processing, in which transmission target data contained in the first database is transmitted to the second database, and restraining, in the case that updating of the transmission target data is allowed in the first database, the control that causes the first processing to be performed with priority.

Abstract: A synchronisation system and corresponding method for synchronising a set of records in a first database with a second database which comprises a copy of the set of records. The first database has a transaction log with entries indicating changes made to records in the first database. The second database stores a global version. The synchronisation system comprises at least one processor which is configured to process entries in the transaction log relating to the set of records to record changes from the first database in the second database; and associate the global version with any records written to the second database.

Abstract: A method begins by receiving at least a portion of a merchant master file. The method continues, for a merchant data file, by determining whether a corresponding merchant profile record exists within a merchant profile database. The method continues, when the corresponding merchant profile record exists in the merchant profile database, by comparing the merchant data file with the corresponding merchant profile record. The method continues, when an inconsistency exists between the corresponding merchant profile record and the merchant data file, by determining status of the merchant data file with respect to the at least a portion of the merchant master file. The method continues, when the status of the merchant data file is a first status level, by generating an inconsistency message that identifies the inconsistency.

Abstract: As changes are made to a document, each change may be assigned an extended identifier comprising a globally unique identifier (GUID) component and an integer component. Upon determining that the same GUID component is used in identifiers for multiple changes, the GUID component may be mapped to a range of indices. Each index of the range of indices may then be used to represent the same GUID component in each extended identifier.

Abstract: Systems and methods for managing data, such as metadata. In one exemplary method, metadata from files created by several different software applications are captured, and the captured metadata is searched. The type of information in metadata for one type of file differs from the type of information in metadata for another type of file. Other methods are described and data processing systems and machine readable media are also described.

Abstract: A communication apparatus for performing connection type communication includes a first memory configured to store pieces of communication endpoint information relating to communication endpoints of connection, and a moving device configured to move, among the pieces of communication endpoint information stored in the first memory, communication endpoint information of connection set in a disconnection wait state, from the first memory to a second memory.

Abstract: An information-processing apparatus includes a networking device that communicates with an external apparatus. The information-processing apparatus also includes a storage that stores an album of a plurality of content data and a transfer log indicating whether each of the content data has been transferred to the external apparatus. The information-processing apparatus additionally includes a processing unit that identifies certain content data from the content data of the album when the transfer log indicates that the certain content data has never been transferred to the external apparatus and controls a display of information about the album. Further, the processing unit starts a transfer of the certain content data to the external apparatus, when the album has been selected and the certain content data has never been transferred to the external apparatus, and updates the transfer log when the networking device transfers the certain content data to the external apparatus.

Abstract: Systems and/or methods for controlling access to a plurality of records and/or documentary materials to be persisted in an electronic archives system are provided. The plurality of records and/or documentary material and all preserved information may be stored and accessed on the basis of user and/or object attributes. The user attributes include group affiliation, ownership, and state (e.g., workflow step and time of day). The object attributes include group affiliation, business role, clearance or access level, and network address from which access is requested. Access to the plurality of records and/or documentary material can be obtained both from within a single security domain as well as across more than one security domain.

Abstract: Automatic detection and implementation of modifications to an application are described. A new base model of the application is generated using the edited version of the application. This base model is simulated to a selected state, resulting in a new presentation model that includes a tree of multiple objects described by the new base model at the selected state, and a pointer for each node of the tree that points back to the associated node in the new base model. The pointers of each node of the new presentation model are compared to the nodes of the previous presentation model of the application and then replaced with those corresponding nodes in the previous presentation model when the nodes are equivalent. Otherwise, the nodes of the new presentation model are maintained.

Abstract: Techniques for replicating data chunks in a storage system are described herein. In one embodiment, in response to a request for replicating data chunks of a source storage system having a first average chunk size to a target storage system having a second average chunk size, a new chunk size is determined based on metadata of the data chunks in view of an average chunk size of the target storage system. The data chunks are resized based on the new chunk size to generate resized data chunks. The resized data chunks are transmitted from the source storage system to the target storage system for replication.

Abstract: A synchronization system is described herein that synchronizes two environments by correctly matching identity objects in a source environment with related objects in a target environment. In addition to matching identities based on primitive attributes, the system matches identities across multiple heterogeneous environments based on their relative positions in an identity graph. The system builds the identity graph by first matching some identity objects based on primitive attribute value comparisons. The system fills in the remainder of the identity graph by comparing references to/from the matched identity objects. The combination of attribute value comparisons and comparing references enables identity-aware applications to complete a single identity graph, determine the equivalency of identities in this graph, and apply policy based on this new relationship.

Abstract: For efficiently storing and retrieving data and metadata in phases, in a first phase, metadata tokens, which are assigned to most active metadata-emitting entities, are used for storing the data and the metadata together in a single input/output operation while piggybacking the metadata of least active metadata-emitting entities onto one of the most active metadata-emitting entities having one of the metadata tokens. In a second phase, the metadata is re-written to a metadata delta journal for reclaiming the metadata tokens. In a third phase, the metadata journal is applied to a metadata structure containing the metadata of the storage system, the metadata delta journal is then cleared after successfully updating the main metadata structure with the metadata of the metadata journal. The metadata journal is swapped with an empty metadata journal for concurrently adding metadata while retaining the metadata journal until applying the metadata delta journal to the metadata structure.

Abstract: A system for case based, dynamic document layout in accordance with embodiments of the present invention includes a comparison system, a determination system, and a mutation system. The comparison system that compares one or more elements of at least a portion of an original document against the same elements in at least a portion each of a plurality of stored documents. The determination system identifies the stored document with the portion which is closest to the portion of the original document based on the comparing. The mutation system applies one or mutators to the portion of the original document which were used in the portion of the identified stored document.

Abstract: For efficiently storing and retrieving data and metadata in phases, in a first phase, metadata tokens, which are assigned to most active metadata-emitting entities, are used for storing the data and the metadata together in a single input/output operation while piggybacking the metadata of least active metadata-emitting entities onto one of the most active metadata-emitting entities having one of the metadata tokens. In a second phase, the metadata is re-written to a metadata delta journal for reclaiming the metadata tokens. In a third phase, the metadata journal is applied to a metadata structure containing the metadata of the storage system, the metadata delta journal is then cleared after successfully updating the main metadata structure with the metadata of the metadata journal. The metadata journal is swapped with an empty metadata journal for concurrently adding metadata while retaining the metadata journal until applying the metadata delta journal to the metadata structure.

Abstract: Various systems and methods can select an incremental modification detection technique to apply to a data object during generation of an incremental backup. For example, a method can involve accessing information indicating an access characteristic of a data object and then selecting an incremental modification detection technique (from a set of more than one different incremental modification detection techniques), in response to the information. The incremental modification detection technique is selected to be applied to the data object when generating an incremental backup. The set of incremental modification detection techniques can include change tracking and content differencing techniques.

Abstract: A method for synchronizing a file system (FS) and a remote file system (RFS) includes monitoring the FS for FS events, generating FS event records, receiving RFS event records of RFS events, generating file system operations (FSOs) based on the FS and RFS event records, and communicating the FSOs to the FS and RFS to synchronize them. A method for generating the FSOs includes accessing a plurality of FS and/or RFS event records, processing the accessed records to generate processed event records, generating the FSOs based on the processed event records, and outputting the FSOs to cause synchronization of the FS and RFS. Systems are also described. The invention facilitates event-based, steady-state synchronization of local and remote file systems.

Abstract: A data entry template can be associated with each of a plurality of data records that are distributed across a plurality of heterogeneous or homogeneous data sources which can optionally be data bases. The data entry template can be modified to reflect a change to a business process that was previously represented by the template. The change to the business process can be propagated to at least part of the plurality of data records associated with the template. Related systems, apparatus, methods, and/or articles are also described.

Abstract: A method and apparatus for creating a database replica comprising receiving database information from a source server to create a database replica on a target server. The target server subsequently receives at least one set of update data (e.g., a transaction log) from the source server. Lastly, the target server modifies the database replica in accordance to changes detailed in the at least one set of said update data.

Abstract: A device and method for providing a fault-tolerant file system. The fault-tolerant file system attempts to minimize the number of writes used when updating file system data structures. In one embodiment, file system data, including file system metadata, is stored in a fault-tolerant tree including a working state and a transacted state. In one embodiment, a change list is used to track blocks that have been updated, instead of cascading updates to leaf nodes up the tree, and a delta block is used to further minimize block updates when adding or removing nodes from the tree. In one embodiment, a Q-Block is used to prevent cycles when adding and removing free blocks from an allocation tree. Metadata values are stored in the tree in a way that allows certain metadata values to be inferred when not present in the tree, thus conserving space and lowering query time.

Abstract: A method of replicating a source file system on a storage system, the method including: utilising a changelog operable to store sequentially a data record corresponding to a modification of a source file system by a storage request; specifying a first data record of the changelog at a first time; initiating a scan of the directory inodes of the source file system at the first time; scanning the directory inodes; completing the scan at a second time later than the first time; specifying a second data record of the changelog at the second time; storing, in a database, information corresponding to the scanned directory inodes; updating the database with sequential data records from the first data record to the second data record of the changelog; and building, on a computer system, a replica target file system based on the database.

Abstract: Techniques for differencing binary installation packages are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for performing differencing binary installation packages. The method may comprise populating at least one data structure using information from different builds of a binary installation package, comparing information in the at least one data structure, and generating a result of the comparison.

Abstract: A method replicates data between instances of a distributed database. The method tracks changes to the distributed database at a first instance by storing deltas. Each delta includes a row identifier that identifies a row having a base value, and a sequence identifier that specifies an order in which the delta is applied to the base value to compute a current value for the row. The method identifies a set of deltas to send to a second instance based in part on an egress map at the first instance, wherein the egress map specifies which combinations of row identifier and sequence identifier have been acknowledged as received at the second instance. The method then transmits the identified set of deltas to the second instance. After receiving acknowledgement that the deltas in the identified set of deltas have been incorporated into the second instance, the egress map is updated accordingly.

Abstract: Systems, methods, and media for correlating objects according to relationships are provided herein. According to some embodiments, methods may include the steps of for each object in a database, determining a static weight, the static weight representing a number of relational connections between each object and one or more connected entities, setting a delta weight for each object, the delta weight being equal to the static weight, determining which object in the database comprises a highest delta weight, propagating the highest delta weight of the object to each of the connected entities, adding the highest delta weight to a static weight and a delta weight for each of the connected entities, setting the delta weight for the object to zero, wherein the method terminates upon determining that a highest delta weight for at least one object is below a threshold value.

Abstract: Synchronization of two or more items can be optimized through the use of parallel execution of synchronization tasks and adaptable processing that monitors and adjusts for system loading. Two or more synchronization tasks required to be performed for an item can, if not inherently serial in nature, be performed in parallel, optimizing synchronization of the item. Even if multiple synchronization tasks required for one item must be serially executed, e.g., download the item prior to translating the item, these synchronization tasks can be executed in parallel for different items, optimizing a download request involving two or more items. Moreover, multiple threads for one or more synchronization tasks can be concurrently executed when supportable by the current operating system resources. Rules can be established to ensure synchronization activity is not degraded by the overextension of system resources.

Abstract: In one embodiment, information content files, such as text files, image files, XML files and the like, that provide information related to an identifier bearing item, such as a consumer item with a barcode, are stored on a data storage device such as network server. Identifier data entries, such as UPC data, are associated with file data entries, such as file names, in a database. General file access information that is used in accessing the information content files is stored on a terminal. In operation an identifier is read by the terminal and is used to extract one of the file data entries from the database based on database communication information stored on the terminal. The file data entry in combination with the general file access information is used to establish communication with the data storage device and to extract one of the information content files.

Abstract: A synchronization system is described herein that synchronizes resource objects in an order based on their dependency relationships so that a referenced object is available by the time an object that references it is synchronized. Reference attributes present in resources define the dependency relationship among resources. Using these relationships, the system builds a dependency tree and orders synchronization operations for environment reconciliation by precedence so that referential integrity is preserved while still synchronizing reference attributes. The system can deterministically create a change list that guarantees referential integrity, and perform change list processing in parallel. The synchronization system attempts to order the synchronization based on references available to ensure that the system creates and updates dependent resources before their parent resources. Thus, the synchronization system provides a fast, reliable update mechanism for synchronizing two related data environments.

Abstract: Writes to a storage device of a protected computer system are tracked in a manner that accounts for those writes that may occur during a system reboot process when the file system is not available. During the shutdown process, write tracking data is maintained in system memory and is written into storage locations allocated to the tracking file after the file system has been dismounted so that any writes that may occur during the file system dismount can be captured. During the boot process, temporary write tracking data is maintained in system memory even before the file system is mounted so that any writes that may occur immediately after the file system mount can be captured. The temporary write tracking data is later merged with the tracking data contained in the tracking file and the merged tracking data is used to track further writes to the storage device.

Abstract: A file monitoring system tracks progress of data processing of a data file. Various applications and systems transmit status updates at one or more stages of processing to the file monitoring system. The file monitoring system monitors the status updates and generates reports displaying the status of the date file at the predetermined processing states. Reports include end to end status, files received and files delivered.

Abstract: Disclosed herein is a method of managing data in an asymmetric cluster file system. In this method, if an OPEN request for the opening of an absent file has been received, a metadata server assigns a file handle value and a file name and then generates a file in a data server. Thereafter, the metadata server copies a file stored in the data server or the generated file to one or more data servers based on a preset copying level. Thereafter, a client performs a file operation on the files stored in the data servers.

Abstract: Embodiments relate to systems and methods for generating iterated distributions of data in a hierarchical database. A data store can store data in a hierarchical format, for instance, in a tree. Higher-level data, such as yearly profit, may be desired to be spread from parent nodes to lower nodes, such as nodes representing quarters. A spreading tool can insert child nodes representing quarters, months, or other at insertion point(s) represented or encoded by a set of placeholder nodes, dividing quantities appropriately. In aspects, the spreading tool can access or host sequence logic including multiple sets of spreading rules which each ensure that data is spread in an order that takes dependencies, formatting, outputs, or other factors into account. In aspects, the spreading tool can receive or generate a prioritized ordering of the sets of spreading rules, to ensure that data distribution passes are iterated in a desired or error-free order.

Abstract: A method and apparatus for performing object modifications by using change-specific executable files comprises accessing at least one modification stub associated with an object file, wherein the modification stub comprises an instruction for modifying the object file, wherein the instruction identifies an element in the object file and defines instructions for modifying the identified element; applying a selected modification stub to the object file; and modifying the object file per the instruction contained in the modification stub.

Abstract: A device and method for providing a fault-tolerant file system. The fault-tolerant file system attempts to minimize the number of writes used when updating file system data structures. In one embodiment, file system data, including file system metadata, is stored in a fault-tolerant tree including a working state and a transacted state. In one embodiment, a change list is used to track blocks that have been updated, instead of cascading updates to leaf nodes up the tree, and a delta block is used to further minimize block updates when adding or removing nodes from the tree. In one embodiment, a Q-Block is used to prevent cycles when adding and removing free blocks from an allocation tree. Metadata values are stored in the tree in a way that allows certain metadata values to be inferred when not present in the tree, thus conserving space and lowering query time.

Abstract: A method is disclosed for reliably updating a data group in a read-before-write data replication environment. The method reliably updates the data group by receiving an updated data group sent from a first storage medium to a second storage medium, comparing the updated data group with a previous data group previously existing on the second storage medium and writing the updated data group to the second storage medium. The read-before-write and differencing method disclosed maintain reliability by storing multiple copies of changes made to the second storage medium during and after the write process.

Abstract: A universal data management interface (UDMI) system includes a processing system generates a visual interface through which a user can access, manage, and manipulate data on plural different types of remote databases. The UDMI connects to multiple standard database management systems and to allow multiple users to access, manage, and manipulate data within each of the multiple standard database management systems. The UDMI also allows multiple virtual databases that reside in a single database to be available as a network service.