Abstract: Methods, systems and techniques for synchronizing content, such as a file, between one or more clients and one or more servers are provided. Example embodiments provide a Cross-File Differential Content Synchronization System (CDCSS) to synchronize files between remote systems in a nearly instantaneous manner without necessitating the transfer of the entire contents of a file. These components cooperate to transfer only the differences in data content wherever possible to a recipient system by providing a patch mechanism that instructs the recipient to build the modified or new data content based upon content it already has access to. In addition, in one embodiment the CDCSS synchronization solution provides a client-based index, rather than a server-based index, for tracking patches and files, which reduces the amount of computational and I/O overhead on the server and which does not require a negotiation between a client and a server to provide an update.

Abstract: A system and/or computer program product synchronizes data between a first computer and a second computer. An original first data in a first computer is changed into revised first data in the first computer by inserting a data change into the original first data. The data change in the revised first data is identified and transmitted to a second computer in a message. The message instructs the second computer to convert an original second data stored in the second computer into a revised second data by inserting the data change into the original second data, where the original second data and the revised second data are used and managed by a resident application software on the second computer. The message is executable without use of the resident application software on the second computer, thus allowing changes to be made across disparate platforms.

Abstract: Synchronization of folders shared among multiple clients over a network is provided. A first user of a first client instantiates a folder to be shared, and the folder and its contents are synchronized with a host system. As the user makes changes to the folder and its contents on the first client, those changes are propagated to the synchronized version on the host server. Other clients who will be sharing the synchronized folder register with the host system and obtain a current version of the synchronized folder and contents. As the contents of the synchronized folder are changed by any of the clients, the changes are propagated to the host system, which in turn delivers the changes to each of the clients registered as sharing that folder. In this way, each client participating in the share has a current version of the folder and its contents.

Abstract: Among other things, methods, systems and computer program products are disclosed for manipulating media. In one aspect, synchronization of media files involves identifying a change to an attribute associated with a media file associated with a first media file library located on the host system; accessing a client device list including device IDs for devices associated with the first media file library; identifying a first client device indicated by the device list; accessing a first synchronization order file stored on a server system; modifying the first synchronization order file to indicate the change to the attribute associated with the media file; and providing the modified first synchronization order file to the server system to enable the first client device to apply the indicated change to the attribute associated with the media file within a second media file library located on the first client device.

Abstract: Apparatus and methods are provided for performing a digital forensic investigation. Aspects of the apparatus and methods determine the location of forensically relevant data on a data source and copy this relevant data to a storage device in a forensically sound manner. Information related to the location of the relevant data may also be stored on the storage device.

Abstract: In a mirrored database system, mirror resynchronization of fixed length pages is optimized for quick repair and high availability by identifying those lost page changes that must be made for resynchronization and ignoring other duplicate changes. Essential pages are identified using log sequence numbers (LSNs) to locate the most current version of a changed page, and other lower valued LSNs of less current versions of that page are eliminated as having changes that are duplicated in the current version of the page. Page changes since the last database checkpoint before losing mirror synchronization and the current LSN of the transaction log are identified as possibly necessary changes to be made.

Abstract: The described implementations relate to updating views in a database system. One implementation can identify an active view that retrieves records from a database and determine one or more physical tables in the database that are referenced by the active view. The implementation can track one or more columns in the physical tables that are used by the active view and identify a change to the physical tables in a transaction log of the database. If the change does not affect the one or more columns, the change can be treated as an ignorable change for the active view.

Abstract: Systems for synchronizing data between a first-database and a second-database are presented including: a memory; and a client configured for determining whether a retrieval request requires a synchronization of the second-database before processing the received retrieval request, where the system partially synchronizes the second-database from the first-database with only that portion of the first-database associated with the retrieval request in response to determining whether synchronization is required and for processing the retrieval request from the second-database.

Abstract: Techniques to cross-synchronize data are described. An apparatus may comprise a cross-synchronization component to synchronize multiple data items for different application programs between multiple client devices synchronized using multiple synchronization circuits. The cross-synchronization component may determine whether changes to the multiple data items made at a first client device are propagated to a second client device using consistency information maintained by a consistency group item for a consistency group including the data items. Other embodiments are described and claimed.

Abstract: The technique introduced here involves using a block address and a corresponding generation number as a “fingerprint” to uniquely identify a sequence of data within a given storage domain. Each block address has an associated generation number which indicates the number of times that data at that block address has been modified. This technique can be employed, for example, to determine whether a given storage server already has the data, and to avoid sending the data to that storage server over a network if it already has the data. It can also be employed to maintain cache coherency among multiple storage nodes.

Abstract: Methods and systems for synchronizing network configuration state tables between an operating system kernel and an attached ASIC switch device are disclosed. An instruction to update a target network configuration state table in either an operating system kernel or an attached ASIC switch device is received. Data from the target network configuration state table and data from a corresponding network configuration state table are retrieved. Values of data in the two tables are compared and an instruction is sent to update the target network configuration state table with one or more values from the corresponding network configuration state table.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for deploying updates between environments of a multi-tenant on-demand database system. These mechanisms and methods for deploying updates between environments of a multi-tenant on-demand database system can enable embodiments to provide user-friendly, granular, and/or targeted updates between such environments.

Abstract: A method and system for backing up and restoring personal data are provided. The method includes communicating with a first communication device over a first communication connection when the first communication device detects changes to personal data stored in a first communication device; receiving the changed personal data over the first communication connection; performing a backup function by receiving the changed personal data from the first communication device; automatically communicating with a second communication device that is associated with a same user account as a user account associated with the first communication device, over a second communication connection upon performing the backup function; and automatically performing a restore function by transmitting the changed personal data to the second communication device over the second communication connection upon performing the backup function.

Abstract: A system for processing data comprises a deduplicating system, an interface, and a processor. The deduplicating system stores a copy of data stored in a data storage system by storing a set of segments that is able to reconstruct the data stored in the data storage system. The data storage system has a stored log file. The stored log file stores a data change and an associated time for the data change. The interface receives an indication to revert data stored in the data storage system to a state at a snapshot time. The processor is configured to determine a first subset of the data stored in the data storage system that has changed since a prior snapshot using the stored log file and to determine a second subset of the data stored in the data storage system that has changed between the prior snapshot and the snapshot time using a first list of fingerprints associated with the prior snapshot and a second list of fingerprints associated with the snapshot time.

Abstract: Techniques are disclosed for file system monitoring 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 which represents that a modification to an item has taken place on the cloud-based platform, identifying whether execution of the event is to violate any local file system rule. The method further comprises, if the execution of the event is to violate any local file system rule, buffering the event until a subsequent event arrives. The method further comprises identifying whether execution of an aggregate of the events is to violate any local file system rule.

Abstract: Systems and methods for replicating input-output (I/O) events of a cluster shared volume (CSV) are presented. Such systems may include a cluster device or node (in a cluster of devices), a coordinator node, and a replica server. Replication techniques disclosed herein may include capturing, using a processor operatively associated with a cluster device, a direct I/O event generated at the cluster device (e.g., by a virtual machine). A legacy file system filter driver of the cluster device may be used and enabled to perform the capturing of the direct I/O event. The legacy file system filter driver may be different than a CSV filter driver associated with the CSV, and may be enabled after the CSV filter driver is enabled. The captured direct I/O event may then be transmitted to the replica server using, e.g., a replication filter, to maintain a backup copy of the event at the replica server.

Abstract: [PROBLEM TO BE SOLVED] To reduce a server load when synchronizing data between a client and a server. [SOLUTION] A client 10 sends a synchronization request 41 containing an anchor point to a server 20. The server 20 sends synchronization information 42 to the client 10, which synchronization information including change profile information on data updated between the anchor point and a boundary point and change profile information on a change log after the anchor point. Based on the synchronization information 42, the client 10 sends a download request 43 to the server 20, and the server 20 sends download information 44 to the client 10 in response to the download request 43. The client 10 registers data contained in the download information 44 to a client database 11.

Abstract: According to one embodiment, a method for determining a transfer order of files includes acquiring the access count of a replicated file at a production site and at a remote site, these access counts being reflected in the order for asynchronous replication. In addition, the access count of backed up files at the remote site is also acquired and reflected in the order for asynchronous replication according to another embodiment. This allows for improved determination of the transmission order of files (according to priority based on usage) from a production site to a remote site in an asynchronous replication function.

Abstract: The disclosed technology can enable files to be stored with a networked environment. The files can be associated with information (e.g., properties) such as a file name, a file type, a date/time at which a respective file was last accessed, a number of times a respective file was accessed, data representing the contents of a respective file, and other information. Based at least in part on analyzing the information, the disclosed technology can select or identify a file and/or a file property (e.g., a file type) that the disclosed technology predicts to be most relevant to the user. The disclosed technology can then recommend applications based at least in part on the selected or identified file and/or file property (e.g., file type).

Abstract: Systems and methods for replicating a client data set on a computer includes replicating the client data set using an application software on the computer; generating a manifest of a target data set during replication containing state of target data reflecting post-update state; and determining differences between the local data and manifest to determine required backup operations.

Abstract: In one embodiment, a method receives a specification for aggregating data from processing of beacons. A beacon is associated with an event occurring at a client while a user is interacting with a web application and including unstructured data. The method then parses the specification to automatically generate an aggregation to aggregate structured data that has been converted from the unstructured data and stores dependency information for changes to the aggregation. State information is analyzed and the dependency information to determine when a change in the state information indicates that a change should be made to the aggregation. The method then dynamically changes the aggregation based on the analyzing to generate a new aggregation to aggregate different data based on changed information.

Abstract: According to one general aspect, a method may include replicating, to a software-as-a-service application, a plurality of pieces of master data from a physically remote master database. The method may also include converting the plurality of pieces of master data into one or more pieces of local data of the software-as-a-service application. The method may include changing one or more of either the pieces of master data or the pieces of local data. The method may further include synchronizing the changed pieces of either master data or local data between the remote master database and the software-as-a-service application.

Abstract: Systems and methods for replicating database data and generating read-only copies of the replicated data in a clean shutdown state. For example, systems can include a tracking module (e.g., a filter driver) that monitors transactions from a database application to a source storage device to generate log entries having at least one marker indicating a known good state of the application. The systems further include a computer coupled to a target storage device comprising a database and log files. The computer processes the transactions, based on the log entries, to replicate data to the target storage device; performs a first snapshot on data stored in the database and log files; replays into the database data stored in the log files; performs another snapshot on the database; and reverts the database back to a state in which the database existed at the time of the first snapshot.

Abstract: Systems and methods are described herein for creating, maintaining and applying a dataset that can be used to synchronize multiple instances of a data store. The dataset includes a sequentially-ordered sequence of change sets associated with the data store, wherein each change set includes zero or more entries that specify how the state of certain entities in the data store have changed since state changes represented by a previous change set in the sequence were applied to the data store. When a new change set is added to the dataset, any entries in any previously-added change sets dealing with the entities identified in the new change set are removed. Consequently, the dataset provides a concise and complete representation of all the state changes that have occurred to the data store since a known origin state.

Abstract: A multi-master cloud-based data replication service designed to support the needs of a broad class of web applications is disclosed. Generally, the replication service serves the purposes of facilitating sharing of web application data among personal computing devices and increasing the availability of that data. In one embodiment, the replication service includes a replica identifier reassignment features that allows a personal computing device to begin sharing application data changes with an existing group of personal computing devices that are already sharing application data changes between them even if the joining personal computing device has application data changes to share with the other personal computing devices of the group at the time the joining personal computing device requests to join the group.

Abstract: A technique includes, in response to the detecting movement of a virtual data container stored, performing a replication operation, including communicating data between the storage appliance and a storage device other than the storage appliance. The data identifies incremental differences between the first virtual data container and a second virtual data container that is stored on the storage device.

Abstract: Methods of synchronizing data between a first database and a second database each holding a portion of data included in the first database using an electronic computing device are presented including: causing the electronic computing device, in response to issuing a retrieval request to the second database, to extract, from the first database, differential data between a first data set in the first database and a second data set in the second database as a retrieval target of the retrieval request, where the retrieval request includes a current retrieval request and a future retrieval request, where the future retrieval request is configured for issuance after the current retrieval request; and updating the second data set by applying the differential data to the second database, where the updated second data set is the retrieval target of the retrieval request.

Abstract: Architecture that maintains the user experience as close as possible to the user experience when dealing with the usual/regular forms and data provided in an office application when dealing with hybrid forms and hybrid data. Synchronization of the hybrid data to single-master and multi-masters systems is accomplished when the associated hybrid client goes offline, changes are made to the hybrid data, and then the client comes back online. For example, where the single-master system is a line-of-business (LOB) server system and the multi-master system is an officer server that employs collaboration capability, the architecture allows office users to access, manipulate, and share LOB entity information using collaborative means, while at the same time, ensuring data and business process consistency for the LOB entity in the LOB system.

Abstract: An application program management method and apparatus using information are provided. The application program management method includes: in response to the state of an application program being changed in a first terminal, notifying a second terminal of the occurrence of an application program update in the first terminal; and in response to the second terminal recognizing the occurrence of an application program update in the first terminal, providing the second terminal with the state-changed application program or updated information relating to the state-changed application program.

Abstract: Embodiments provide information composition management features and functionality to manage composite information, but are not so limited. In an embodiment, a computing system can include functionality to provide a composition of informational data that can be used to identify and manage aspects of shared and other data that can be associated with distinct information sources. In one embodiment, a computing platform includes a client that can be configured to access and use information of a plurality of independent sources to create a data composition that includes aspects of shared and unshared data portions and manage data changes of the data composition including managing issues associated with one or more of the plurality of independent sources. Other embodiments are described and available.

Abstract: The invention provides an application technique of a backup data in which a backup data can be utilized by creating a backup data including no indeterminate data in a backup system. In a backup system including a primary system and a backup system, the method of creating the backup data includes: a data update record rerun step for rerunning a data update record to a backup data; and a backup data creation step for starting a read to a backup data B, stopping a read to a backup data A, copying the backup data to the backup data A, starting the read to the backup data A, stopping the read to the backup data B, and copying the backup data A to the backup data B.

Abstract: A method for historically synchronizing tag data related to a computer network is provided. A network management server compares a relations table of entities from a first database to a corresponding relations history table of entities from a second database. The network management server identifies from the comparison a pair of entities having a changed relationship. The network management server updates the relations history table of entities with the changed relationship in the second database. The network management server updates a path and level between a root of a tree of tags and each tag of the pair of tags in a historical configuration details table of tags in the second database based on updating the relations history table of entities.

Abstract: Methods and systems that permit file protocols and object protocols to co-exist using a file namespace and an object namespace in a unified storage system are disclosed. Data stored in the unified storage system are file-objects that preserve the behaviors expected by both file clients and object clients.

Abstract: A method performed by a video provisioning system may include receiving metadata associated with a video asset; storing the metadata in a catalog of video assets available through the video provisioning system; publishing information from the stored metadata to a first device associated with a video assets store front for set top boxes; and publishing information from the stored metadata to a second device associated with a video assets store front for devices other than set top boxes. A method may further include registering a user device with a user profile; identifying a media manager application for the user device that is configured to play video assets available via the video provisioning system on the user device; providing the media manager application to the user device; and synchronizing settings associated with the media manager application with settings associated with another user device registered with the user profile.

Abstract: A map update data delivery method includes: storing update unit data compiled in correspondence to each set of update data used to update map data in a specific version to map data in another version for a map element by incorporating update data for another map element that must also be updated in coordination with a change made for the map element; searching for base update data needed to update a map data for a map element designated as an update target in a map area specified at a terminal as a map data update target; searching for related update data with a relation to contents of update data included in the base update data searched; and transmitting the base update data and the related update data to the terminal.

Abstract: A first data structure stores indications of storage locations that need to be copied for forming a consistency group. A second data structure stores indications of new host writes, subsequent to starting a point in time copy operation to form the consistency group. Locations of the first data structure and the second data structure are exchanged, subsequent to the consistency group being formed successfully.

Abstract: The described embodiments include a computing device that enables the placement of data guards on data items (e.g., files, data in an application, etc.). The data guard is associated with a conflict priority that is used to determine users that are permitted to make changes to the data item. When the data guard has been placed, the data item is visually identified (e.g., when displayed on a display) as being guarded. In addition, the computing device includes various mechanisms for enabling synchronization of data items between computing devices.

Abstract: In a method of automated document replication in a distributed computing system, a document at a first node of a distributed computing system is analyzed. Based on the analysis, it is determined whether the document has a multi-node affinity. In response to determining that the document has a multi-node affinity, at least one document is automatically replicated between nodes of the distributed computing system. The indicated nodes are indicated based on context of the multi-node affinity of the analyzed document.

Abstract: A system and method for managing clinical research trials is disclosed. The system and method may include a centralized secure database with information on clinical research trial participants, clinical research trial events, investigator and administrator inputs, and communication of participants, investigators and administrators. In one embodiment, the system and method allows investigators to contact participants without disclosing confidential contact information of the participants to the investigators by storing health information and contact information in separate databases. In one embodiment, administrators may access clinical research trial information through a secure web portal.

Abstract: A multi-tiered replicated process database and corresponding method are disclosed for supporting replication between tiers. The multi-tiered replicated process database comprises a tier one (T1) database server computer including a process history database and a replication service. The replication service includes a set of accumulators. Each accumulator is adapted to render a summary T2 database tag data structure from a set of data values retrieved from the process history database for a specified T1 database tag. The replicated database system also includes a tier two (T2) database server computer comprising a consolidated database that includes process data replicated from a set of T1 database servers. At least a portion of the process data replicated from the set of T1 database servers is summary T2 database tag data rendered by the set of accumulators.

Abstract: Systems and methods are described herein for creating, maintaining and applying a dataset that can be used to synchronize multiple instances of a data store. The dataset includes a sequentially-ordered sequence of change sets associated with the data store, wherein each change set includes zero or more entries that specify how the state of certain entities in the data store have changed since state changes represented by a previous change set in the sequence were applied to the data store. When a new change set is added to the dataset, any entries in any previously-added change sets dealing with the entities identified in the new change set are removed. Consequently, the dataset provides a concise and complete representation of all the state changes that have occurred to the data store since a known origin state.

Abstract: The technology relates to synchronizing user metadata across devices. The system maintains a collection of incremental metadata changes for a collection of media items, for each media item represented in the collection, storing a media item identifier and a value, wherein the value is an incremental user metadata change for a respective media item. Next, the system receives, from a client device, a request for a metadata sync, the request comprising a last metadata version update number indicative of a last metadata sync received by the client device. The system then sends, to the client device, a metadata update associated with a version update number subsequent to the last metadata version update number indicative of the last metadata sync received by the client device.

Abstract: Systems and methods are provided for batch processing of data records in an on-demand system. A marker is stored that identifies a node in an on-demand system and identifies a most recent data record processed in a relational database management system by the node. The marker is used to query the database management system to identify a batch of records for the node to process. The batch of records is processed by the node to update a client of data changes reflected by the batch of records.

Abstract: Aspects of the present invention relate to data migration and/or disaster recovery. One embodiment enables merging of bitmaps to allow for automation of the process of switching to a different target volume on the same storage subsystem without major interruption of data recovery capability and limited interruption of host I/O to the source volumes during the migration.

Abstract: A method and system for propagating database records from staging database to a production database so that the production database reflects record changes made in the staging database. The system of the present disclosure propagates record changes from the staging database to the production database in a flexible, customizable, and reliable way. The system consolidates database record changes to cull out any unnecessary record changes that do not need to be propagated. The system may also track the status of the database record changes, and send alerts related to the propagation status.

Abstract: An apparatus for providing sub-file level synchronization may include a processor configured to receive an indication of a change to a portion of a file, generate a file identifier in response to the receipt of the indication, the file identifier including a sub-file identification indicative of the portion of the file, and enable synchronization of the portion of the file based on the sub-file identification. A corresponding method and computer program product are also provided.

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: An approach for replicating data is provided. A job that modifies data objects in a first system to generate a first set of changed data objects is determined to be a candidate for a job replication. Based on the job being a candidate for job replication, attributes of the job are retrieved, the retrieved attributes are sent to a second system, and an execution of the job by the second system is initiated as part of the job replication. The execution of the job causes data objects included in the second system to be modified to generate a second set of changed data objects as a replication of the first set of changed data objects.

Abstract: A data indexing system including a plurality of servers and a tracked resource set client is provided. Each of the servers include a plurality of resources that are part of a resource set. Each of the servers also include a tracked resource set corresponding to the resource set. The tracked resource set describes the plurality of resources located in the resource set. The server identifies the plurality of resources using rules of linked data. The tracked resource set client is in communication with the plurality of servers. The tracked resource set client has a data index. The data index is built and kept up to date using the tracked resource set of each of the plurality of servers.