| Class / Patent application number | Description | Number of patent applications / Date published |
|---|
| 707648000 | Transaction log backup (i.e, audit file, journal) | 71 |
| 20100082547 | Log Structured Content Addressable Deduplicating Storage - A log structured content addressable deduplicated data storage system may be used to store deduplicated data. Data to be stored is partitioned into data segments. Each unique data segment is associated with a label. The storage system maintains a transaction log. Mutating storage operations are initiated by storing transaction records in the transaction log. Additional transaction records are stored in the log when storage operations are completed. Upon restarting an embodiment of the data storage system, the transaction records from the transaction logs are replayed to recreate the state of the data storage system. The data storage system updates file system metadata with transaction information while a storage operation associated with the file is being processed. This transaction information serves as atomically updated transaction commit points, allowing fully internally consistent snapshots of deduplicated volumes to be taken at any time. | 04-01-2010 |
| 20100114831 | Building a Synchronized Target Database - One embodiment is a method that builds a target database with transaction logs from an online source database. The transaction logs include both existing data in the source database and updates that occur to the source database while the target database is being built. | 05-06-2010 |
| 20100191706 | Storing Information for Dynamically Enlisted Resources in a Transaction - A method, apparatus and program product dynamically enlist a plurality of resources to be committed by a transaction during execution of the transaction and store information about each enlisted resource in the plurality of resources with the transaction in a transaction log, including information about a state of each resource, to facilitate recovery of the transaction. Enlisting and storing may be performed during the execution of the transaction, and the resources to be committed by the transaction may be unknown prior to execution of the transaction. By doing so, a more complete record of all the resources that were enlisted during runtime may be maintained. | 07-29-2010 |
| 20100280995 | FILE SYSTEMS, PROCESSES, CIRCUITS, DEVICES AND ELECTRONIC SYSTEMS - A computer device ( | 11-04-2010 |
| 20110016090 | Hierarchical Scale Unit Values for Storing Instances of Data Among Nodes of a Distributed Store - Techniques are described herein for storing instances of data among nodes of a distributed store based on hierarchical scale unit values. Hierarchical scale unit values are assigned to the respective nodes of the distributed store. A first instance (e.g., a primary instance) of a data module is stored in a first node having a first hierarchical scale unit value. A primary instance of the data module with respect to a data operation is an instance of the data module at which the data operation with respect to the data module is initiated or initially directed. A second instance (e.g., a primary or secondary instance) of the data module is stored in a second node having a second hierarchical scale unit value based on a magnitude of a difference between the first hierarchical scale unit value and the second hierarchical scale unit value. A secondary instance is essentially a “back-up” instance. | 01-20-2011 |
| 20110029489 | Dynamic Information Hierarchies - A dynamic information hierarchy may be provided. Logging data comprising a captured user event and a component ID associated with a hierarchical node may be stored in a raw data table. The stored data may be aggregated across the nodes of the hierarchy, stored in an aggregation table, and provided to a user in a report. | 02-03-2011 |
| 20110113014 | Methodology of Applying Storage and Logistics Center Model to Achieve Business Data Exchange between Systems - A methodology of applying storage and logistics center model to achieve business data exchange between systems, is based on the storage logistics center model, establishes data storage management center, which receives and saves the data in each business system and sends data extraction request to the corresponding data; Conducts a detailed checking and verification action in the sending and receiving process of aforementioned data storage management center. Comparing with the existing technology and according to the empirical test, the data delivery stem that is based on fragmented data transportation of the logistics center model (the most typical system in the concurrent technology) shows that: performance is increased by 10%, resource consumption is reduced by 30%, system failure rate has dropped 20%, and each process can be controlled. | 05-12-2011 |
| 20110137864 | HIGH THROUGHPUT, RELIABLE REPLICATION OF TRANSFORMED DATA IN INFORMATION SYSTEMS - Provided are techniques for, in response to a source object being changed by a local transaction, generating log records, wherein each of the log records includes a sequence identifier, a source system entity modification timestamp, a target key, a target partition identifier, and values of source properties, wherein the source properties are identified using a target key indicator. The log records to process are selected based on a phase value of each log record, wherein the phase value is one of submitted, in-flight, and source system entity state change complete. One or more disjoint partitions are assigned to each of multiple processing instances. Under control of each of the multiple processing instances, it is determined whether to transmit a log record in the one or more disjoint partitions assigned to said processing instance and, in response to determining that the log record is to be transmitted, the log record is transmitted. | 06-09-2011 |
| 20110137865 | Method for managing storage service - A method for managing a storage service wherein checking and updating a result of a backup task are facilitated by analyzing a backup end log. In accordance with the method, the result of the backup task is determined by comparing the parameter of the backup end log with that of the backup script and is updated based on user input to obtain reliable statistics of the backup task. | 06-09-2011 |
| 20110137866 | Method for generating backup script - A method for generating a backup script is disclosed. In accordance with the present invention, since the backup script is generated using a backup script generating logic, errors in the backup script may be reduced, and the backup script may be easily modified or complemented even if administrative policies or users are changed. | 06-09-2011 |
| 20110145198 | Contextual and Semantic Differential Backup - A backup system that utilizes contextual and semantic concepts is described. The backup system provides for the ability to create a version changes log for listing and tracking all the changes in the different versions of the file. The version changes log creates a contextual description around the changes, deletions and additions. The semantic concept log is created from the version changes log to create a log of all of the semantic concepts associated with each change. A visualization builder then creates visualizations that can be used by the user to search for changes, deletions and additions whether in a text file or an image file. | 06-16-2011 |
| 20110153568 | HIGH VOLUME, HIGH SPEED ADAPTIVE DATA REPLICATION - System, method, computer program product embodiments and combinations and sub-combinations thereof for data replication in a database system environment are described. In an aspect, the data replication includes grouping, in-memory, a plurality of transactions to be replicated as a single transaction from a source database system to a target database system. A plurality of net row changes is compiled for the plurality of transactions, and data inconsistency detection and resolution within a command application order are performed. Further included is bulk application of the plurality of net row changes to the target database system. | 06-23-2011 |
| 20110153569 | SYSTEMS AND METHODS FOR PROVIDING NONLINEAR JOURNALING - In one embodiment, systems and methods are provided for nonlinear journaling. In one embodiment, groups of data designated for storage in a data storage unit are journaled into persistent storage. In one embodiment, the journal data is recorded nonlinearly. In one embodiment, a linked data structure records data and data descriptors in persistent storage. | 06-23-2011 |
| 20110167043 | GENERATING ANONYMOUS LOG ENTRIES - Assigning session identifications to log entries and generating anonymous log entries are provided. In order to balance users' privacy concerns with the need for analysis of the log entries to provide high quality search results, non-user-specific data fields, such as a user's location (e.g., city, state, and latitude/longitude) and connection speed, are inserted into the log entries, and user-specific data fields, such as the IP address and cookie identifications, are deleted from the log entries. In addition or alternatively, prior to anonymization of the log entries, session identifications are assigned to identified groups of log entries. The groups are identified based on factors such as the user's identification, the IP address, the time of search, and differences between the search terms used in the search queries. | 07-07-2011 |
| 20110307449 | CHECKPOINTS FOR A FILE SYSTEM - Aspects of the subject matter described herein relate to checkpoints for a file system. In aspects, updates to the file system are organized into checkpoint buckets. When a checkpoint is desired, subsequent updates are directed to another checkpoint bucket. After global tables have been updated for updates in the current checkpoint bucket, a logical copy of the global tables is created. This logical copy is stored as part of the checkpoint data. To assist in recovery, a checkpoint manager may wait until all updates of the current checkpoint bucket have been written to storage before writing final checkpoint data to storage. This final checkpoint data may refer to the logical copy of the global tables and include a validation code to verify that the checkpoint data is correct. | 12-15-2011 |
| 20120041926 | TECHNIQUES FOR INCREASING THE USEFULNESS OF TRANSACTION LOGS - Techniques for making light-weight checkpoints in logs of streams of transactions and for extending the logs from the checkpoints. The state saved in the light weight checkpoint need only include the state of all transactions that are active at a prior point in the log and are still active at the checkpoint. A log is extended from the checkpoint by processing new transactions in the transaction stream beginning at the prior point to produce the extending log. When the checkpoint is reached, the state saved at the checkpoint is used to continue to produce the extending log. Techniques are further disclosed for selecting points in the stream of transactions at which the checkpoints may be made and for determining the distance between checkpoints. As disclosed, the log in which the checkpoints are used is a logical log made from a physical log produced by a relational database system. The logical log may be used for replication and for data mining. | 02-16-2012 |
| 20120072395 | SYSTEM AND METHOD FOR VARIABLE BLOCK LOGGING WITH LOG-AHEAD BUFFERS - A system for logging database transactions comprises a memory (comprising a direct access storage device) operable to store a database, a database log, and a plurality of log buffers associated with the database log. Each log buffer is operable to store at least one log record associated with a database transaction. The system further comprises a processor operable to log a first record of a first database transaction using the database log and write the database log to the storage device. The processor is further operable to log a second record of a second database transaction in a first of the plurality of log buffers substantially concurrently to the database log being written to the storage device. | 03-22-2012 |
| 20120084260 | LOG-SHIPPING DATA REPLICATION WITH EARLY LOG RECORD FETCHING - Methods, systems and program products for log-shipping data replication from a primary system to a communicatively-coupled standby system. Embodiments of the invention may receive transactional log data at a standby system, from the primary system, and before the transactional log data is written to storage on the primary system. Embodiments may then receive a notification from the primary system indicating that the corresponding log data was written to storage on the primary system, and responsive to receiving the notification, may process the received transactional log data. | 04-05-2012 |
| 20120095966 | METHOD FOR USING AN OTP STORAGE DEVICE - The invention provides a method of managing data updates in DOS-based data storage device having an OTP memory die that includes a code region having a first memory capacity and a code region access resolution and a data region having a second memory capacity and a data region access resolution. The second memory capacity is larger than the first memory capacity and the code region access resolution is finer than the data region access resolution. The method includes chronologically writing a log entry in the code region indicating the change in FAT and root directory for each change in user data written in the data region. | 04-19-2012 |
| 20120109895 | VERSATILE IN-MEMORY DATABASE RECOVERY - The subject disclosure relates to a database recovery technique that implements various aspects of transaction logging to optimize database recovery performance. Transactions are logged logically with no reference to physical location, which enables logging to be performed via multiple independent log streams in parallel. A set of log streams can further be adjusted to conform to a local configuration of a mirror or secondary node in order to increase mirroring flexibility. Additionally, individual transactions or groups of transactions are recorded using a single log record, which contains timestamp information to enable database recovery without reference to physical checkpoint files. Further, techniques are provided herein for processing transactions without Write Ahead Logging or hardening of undo information. As further described herein, a transaction can be committed via a set of hierarchical stages, which in turn can facilitate integration of an in-memory database system with one or more external database systems. | 05-03-2012 |
| 20120143825 | FILE SYSTEM BACKUP USING CHANGE JOURNAL - Aspects of the subject matter described herein relate to backups and change journals. In aspects, a change journal is read to determine changes that have occurred to objects of a file system. From these changes a data structure is created to capture path information and collect changes for each object. Where the data structure is insufficient to identify a complete path, the live file system is consulted. After the data structure is complete, a data protection engine uses the data structure to update a catalog at least to provide the capability to view the namespace of the protected objects at one or more times covered by the catalog. | 06-07-2012 |
| 20120173490 | METHOD AND SYSTEM FOR IMPLEMENTING BUSINESS LOGIC - A method of recovering a database includes providing a computer having a processor and providing a backup database including a last change marker. The method also includes extracting, using the processor, the last change marker from the backup database and providing transaction logs. Each transaction of the transaction logs includes input data, processed data, and a change marker. The method further includes sorting, using the processor, the transactions of the transaction logs using the change markers, replaying, using the processor, one or more of the transactions of the transaction logs, and generating a recovered database. | 07-05-2012 |
| 20120254120 | LOGGING SYSTEM USING PERSISTENT MEMORY - A computer program product, including: a computer readable storage device to store a computer readable program, wherein the computer readable program, when executed by a processor within a computer, causes the computer to perform operations for logging. The operations include: receiving a transaction including data and a log record corresponding to the data; writing the data to a data storage device; and writing the log record to a log space on a persistent memory device coupled to the data storage device. | 10-04-2012 |
| 20120310891 | METHODS, SYSTEMS, AND PHYSICAL COMPUTER STORAGE MEDIA FOR BACKING UP A DATABASE - Methods, systems, and physical computer storage media are now provided that improve backing up data sets. The method includes registering each database transaction to a central repository prior to starting the database transaction, each database transaction comprising a plurality of writes to be executed for a database application on a database, receiving a first signal indicating a start of a backup application on the database, and quiescing all database transactions registered to the central repository to thereby wait for all ongoing writes of the database transactions registered to the central repository to complete and to release control of the database to the database application | 12-06-2012 |
| 20130006940 | METHODS AND APPARATUS RELATED TO COMPLETION OF LARGE OBJECTS WITHIN A DB2 DATABASE ENVIRONMENT - In one general aspect, an apparatus can include a completion identifier configured to identify, for completion processing, a large object (LOB) deleted from an auxiliary table within a DB2 database environment based on a space map record associated with the large object where the auxiliary table functions as an auxiliary space to a base table. The apparatus can also include a completion analyzer configured to identify a resource where an image of the large object is stored at a time before the deletion of the large object from the auxiliary table. | 01-03-2013 |
| 20130006941 | DEVICE AND METHOD FOR GENERATING COPY OF DATABASE - In a DBMS, in response to a request from application programs, a base table update function updates a base table and a recovery start point, and a log recording function records update logs for the base table. Then, at predetermined timing, a backup function outputs the content of the base table to a backup file and copies the recovery start point associated with the base table to a recovery start point. Subsequently, when a user has specified a quiesce point and the base table, a copy generation function generates a target table that is a copy of the base table at the quiesce point by updating the backup file of the specified base table with ones of the update logs from the recovery start point to the quiesce point. | 01-03-2013 |
| 20130085996 | SYSTEM AND METHOD FOR DATABASE PERSISTENCE OF TRANSACTION LOGS - A system and method for database persistence of transaction logs (TLOGs). Embodiments of the invention allow an administrator to configure their system to associate one or more Java Database Connectivity (JDBC) TLOG stores with a data source or database instead of a file system, for use in storing the primary TLOG. This provides an opportunity to exploit the high availability features of a database system; improve handling of disaster recovery scenarios, such as cross-site recovery using database replication; and alleviate the need for third-party distributed file system components, together with their cost and complexity. | 04-04-2013 |
| 20130117233 | Point-In-Time Database Recovery Using Log Holes - A first plurality of log segments are generated in a data storage application. The log segments are sequentially positioned within a log area and at least one of the log segments contains log hole information identifying a portion of log to skip during replay of the log. Thereafter, a portion of log segments are replayed up to a specified position while skipping at least one portion of the log prior to the specified position that is identified by the at least one log hole. Related apparatus, systems, techniques and articles are also described. | 05-09-2013 |
| 20130132347 | BACKUP METHOD FOR PORTABLE DEVICE - An embodiment of the invention provides a backup method for a portable device. The method comprises creating a first log file according to a first file that has to be stored in a backup device, connecting the portable device to the backup device. When the backup device is connected to the portable device, the backup device reads the first log file and stores the first file to the backup device. | 05-23-2013 |
| 20130132348 | MANAGING DISCONNECTED INVESTIGATIONS - A system and a method enable an information analyst to use a stand-alone computer-based investigation application to conduct a disconnected investigation on shared database data in a remote location where network access to a shared data repository of the system might be only periodically available, unreliable, or non-existent. In addition, the system and method enable the disconnected investigation to incrementally incorporate ongoing updates made to the shared repository of data, and to periodically publish interim or final results of the disconnected investigation to the shared data repository. A disconnected investigation can be conducted entirely at the disconnected investigation location without having any network connectivity to the shared repository of data. | 05-23-2013 |
| 20130151473 | METHODS, SYSTEMS, AND PHYSICAL COMPUTER STORAGE MEDIA FOR BACKING UP A DATABASE - Methods, systems, and physical computer storage media are now provided that improve backing up data sets. Each database transaction is registered to a central repository prior to starting the database transaction, each database transaction comprising a plurality of writes to be executed for a database application on a database, receiving a first signal indicating a start of a backup application on the database, and quiescing all database transactions registered to the central repository to thereby wait for all ongoing writes of the database transactions registered to the central repository to complete and to release control of the database to the database application | 06-13-2013 |
| 20130185262 | TRANSACTION LOG MANAGEMENT - Managing a log-full condition of a transaction log in a transaction processing system, where the transaction log has a plurality of log records each associated with a particular transaction. When a log-full condition is detected, the active transaction having the oldest log entry of all active transactions is identified and logging for all transactions except for the identified transaction is temporarily suspended. A dynamic transaction backout of the identified transaction is initiated, with the writing of a backout record for the identified transaction to the log being delayed. Confirmation that the backout has completed is awaited before trimming the log. Then the delayed backout record for the identified transaction is written to the log, and normal logging is resumed. | 07-18-2013 |
| 20130198138 | MODEL FOR CAPTURING AUDIT TRAIL DATA WITH REDUCED PROBABILITY OF LOSS OF CRITICAL DATA - An aspect of the present invention provides for capturing of audit trail data related to processing of requests. In an embodiment, the received requests are classified into a first category and a second category. For each request in the first category, the corresponding audit trail data is stored directly into non-volatile storage upon processing of the request. On the other hand, for each request in the second category, the audit trail data is first stored into a volatile memory upon processing of the request, and then later copied from the volatile memory to non-volatile storage. Thus, the audit trail data corresponding to both categories of requests is eventually available stored on non-volatile storage. | 08-01-2013 |
| 20130232118 | SHARED LOG-STRUCTURED MULTI-VERSION TRANSACTIONAL DATASTORE WITH METADATA TO ENABLE MELDING TREES - Architecture that includes an ordered and shared log of indexed transaction records represented as multi-version data structures of nodes and node pointers. The log is a sole monolithic source of datastore state and is used for enforcing concurrency control. The architecture also includes a transaction processing component that appends transaction records to the log from concurrent transactions executing on different processors. Each node of a record is assigned a log address. | 09-05-2013 |
| 20130246363 | IDLE POINT AUDITING FOR DATABASES - Idle points for a database, such as a database management system or a relational database management system (RDMS), may be marked in an audit log of a backup device coupled to the database. The backup device may receive an indication that the database has reached an idle point and verify the idle point through a data control system coupled to the database and the backup device. Once the idle point is verified, the idle point is logged in the audit log along with the date and time of the idle point. The idle point information may be used during recovery of the database from the backup device. | 09-19-2013 |
| 20130246364 | REMOVABLE STORAGE DEVICE WITH TRANSACTIONAL OPERATION SUPPORT AND SYSTEM INCLUDING SAME - A removable storage device operates in accordance with transactions defined by a connected host. The removable storage device includes an input unit receiving metadata update operation(s) and log file information, a log information storage storing the log file information, and a transaction manager controlling execution of the metadata update operation(s) and execution of a recovery operation for the transaction following a failure event interrupting the transaction in accordance with the stored log file information. | 09-19-2013 |
| 20130304703 | JOURNAL MANAGEMENT SYSTEM - A journal output device generates a journal describing a processing definition ID of a processing definition for which a processing is in progress and indicating a progress status of the processing in an application, and writes a journal generated, in a journal file. When a write destination journal file is to be changed among journals having a common processing definition ID, the journal output device describes a write destination change notice in a journal. A recovery device separates the processing definition ID of the journal describing the write destination change notice, from another processing definition ID as a write destination change notice, and concatenates two or more journal arrays having a common write destination change incidence ID, to guarantee the sequential order. In case of the write destination change incidence ID, the recovery device analyzes a journal array which has been sequential-order-guaranteed. Regarding other processing definition IDs, the recovery device analyzes the journal array without sequential order guarantee. | 11-14-2013 |
| 20140006353 | RECORDING BACKUP INFORMATION FOR BACKED-UP DATA ITEMS IN A DATA ITEM LIST | 01-02-2014 |
| 20140040208 | EARLY RELEASE OF TRANSACTION LOCKS BASED ON TAGS - A computing system is associated with a first transaction and a second transaction. The first transaction is associated with an update to data and a release of at least one lock on the data prior to the first transaction being durable. The at least one lock is associated with and/or replaced with at least one tag. The computing system is to identify that the second transaction is to acquire the at least one tag based on a read of the data, determine whether the first transaction is durable based on the at least one tag, and delay a transaction commit for the second transaction until the first transaction is durable. | 02-06-2014 |
| 20140040209 | FAILOVER SYSTEMS AND METHODS FOR PERFORMING BACKUP OPERATIONS - In certain embodiments, a tiered storage system is disclosed that provides for failover protection during data backup operations. The system can provide for an index, or catalog, for identifying and enabling restoration of backup data located on a storage device. The system further maintains a set of transaction logs generated by media agent modules that identify metadata with respect to individual data chunks of a backup file on the storage device. A copy of the catalog and transaction logs can be stored at a location accessible by each of the media agent modules. In this manner, in case of a failure of one media agent module during backup, the transaction logs and existing catalog can be used by a second media agent module to resume the backup operation without requiring a restart of the backup process. | 02-06-2014 |
| 20140089263 | FILE RECORDING APPARATUS, FILE SYSTEM MANAGEMENT METHOD, AND CHANGER DRIVE - A file recording apparatus handles a drive as a storage device, and the drive uses, as a removable recording medium, a cartridge on which a non-volatile memory is mounted and in which one of a disk-shaped recording medium and a tape-shaped recording medium is stored. In the file recording apparatus, when a change request is issued, a file system driver records journaling information of a file system recorded in the recording medium in the non-volatile memory. | 03-27-2014 |
| 20140101106 | LOG SERVER AND LOG FILE STORAGE METHOD - A log server is electronically connected to one or more hosts. The log server sends a scan command to all storage nodes connected to a host. The host obtains a log file from each storage node connected to the host, and transmits the log file and an identifier of the storage node to the log server. The log server then searches previously stored log files in relation to the storage node in a storage device according to the identifier, and determines if the received log file is an updated log file based on the search result. If the received log file is an updated log file, the log server stores the received log file into the storage device. Otherwise, if the received log file is not an updated log file, the log server abandons the received log file. | 04-10-2014 |
| 20140122436 | READ ACCESS LOGGING - Read access logging is performed by tracing data accesses in all domains. The logged data is traced on metadata level with some additions identifying the exposed data records. All data relevant for read access logging is stored at first in a temporary log, which is later processed, structured, and archived. | 05-01-2014 |
| 20140129523 | METHOD & APPARATUS FOR ENABLING AUDITING OF A POSITION BY CREATING A CHAIN OF ACTIVE & INACTIVE RECORDS - A computing apparatus and method of recalculating upon changes to data by saving changes to the data; receiving a request to recalculate a result according to the data; retrieving only active data from the data according to the saved changes to the data; and recalculating the result based upon the active data. | 05-08-2014 |
| 20140164331 | TECHNIQUES FOR BACKUP RESTORE AND RECOVERY OF A PLUGGABLE DATABASE - A container database stores redo records and logical timestamps for multiple pluggable databases. When it is detected that a first read-write instance of the pluggable database is opened and no other read-write instances of the pluggable database are open, offline range data associated with the pluggable database is updated. When it is detected that a second read-write instance of the pluggable database is closed, and the second read-write instance is the last open read-write instance, the offline range data associated with the pluggable database is updated. The pluggable database is restored to a logical timestamp associated with a restore request based on the offline range data. | 06-12-2014 |
| 20140181036 | LOG CONSOLIDATION - Consolidating a set of tenant log streams from separate user databases into a consolidated log stream. The method includes receiving a plurality of tenant log streams from separate user data bases. The method further includes recording the plurality of tenant log streams as a consolidated log stream. The method further includes maintaining metadata about the consolidated log stream to map log records from the plurality of tenant log streams to their location in the consolidated log stream. | 06-26-2014 |
| 20140181037 | SYSTEMS AND METHODS TO DETECT DELETED FILES - A data storage system protects data identified for deletion which has been created or modified between scheduled data backups. For instance, the system monitors data operations and when the data operation is a delete, the system determines whether the data identified for deletion has been protected by a backup operation. Data that has not been backed up, such as newly created data, is copied to temporary storage before deletion. When the data has been protected, the system determines whether the data has been modified after the backup operation. Data modified after the backup operation is copied to temporary storage before deletion. | 06-26-2014 |
| 20140279917 | Techniques To Parallelize CPU and IO Work of Log Writes - Techniques are provided for managing cached data objects in a mixed workload environment. In an embodiment, a system, log data is stored in one or more buffers. In response to receiving a request to perform a logical write, a first process writes a first portion of the log data to a log file in persistent storage. While the first portion of the log data is being written to the log file, a second process writes a second portion of the log data in the one or more buffers to the log file in persistent storage. In another embodiment, a request to perform a second logical write may be received before the first logical write completes. While the first log data is being written to the log file, one or more processes write second log data for the second logical write to the log file. | 09-18-2014 |
| 20140279918 | METHOD AND SYSTEM FOR DATA-TRIGGERED DYNAMIC LOG LEVEL CONTROL - Embodiments of the present teachings disclose method, system, and programs for data driven dynamic logging. Data is received by a logging system where the data is flagged for dynamic logging when one or more dynamic flagging level criteria are satisfied. Data is evaluated by a logging module wrapper, which determines whether to log the data using the default logging level or dynamic logging level, according to whether the data is flagged. A logging module logs information in a logging database according to the default logging level or dynamic logging level. Based on the logged information and detected abnormalities the dynamic flagging level and dynamic logging level are automatically or manually adjusted. | 09-18-2014 |
| 20140297595 | TRANSACTION PROCESSING FOR DATABASE IN PERSISTENT SYSTEM - Performing a transaction in the context of a computing system that has one or more persistent systems coupled to one or more processors over a bus. As an example, the persistent system may serve as at least part of the main memory of the computing system. The transaction might implement multi-versioning in which a record is not updated in place. Rather, each record is represented as a sequence of one or more record versions, each version having a valid interval during which the record version is considered to properly represent the record. As part of the transaction, post-commit processing information is generated to allow the computing system to recover in the event of a system failure. | 10-02-2014 |
| 20140351219 | SYSTEMS AND METHODS FOR RETRIEVING DATA IN A COMPUTER NETWORK - A data retrieval system comprising a first computing device communicatively coupled to a second computing device; the first computing device having a processor that supports operation of at least one software application that is used for retrieving data; the second computing device communicatively coupled to one or more storage media; the software application having a retrieval module for retrieving data from the one or more storage media; a storage and backup map that maps to the second computing device; and a data index stored on the second computing device that indicates to the retrieval module a particular location of the data that is to be retrieved by the retrieval module. | 11-27-2014 |
| 20140372380 | METHODS AND SYSTEMS FOR MANAGING AND QUERYING A JOURNALING-CAPABLE FILE SYSTEM - A method for managing a journaling-capable file system is implemented by a computing device including a processor and a memory coupled to the processor. The memory includes a set of meta commands, a set of standard journaling commands, and a journaling-capable file system that is responsive to the set of standard journaling commands. Each meta command corresponds to at least one of the standard journaling commands. The method includes receiving a first meta command wherein the first meta command corresponds to a first plurality of the standard journaling commands, converting the first meta command to the first plurality of standard journaling commands, and executing the first plurality of standard journaling commands to perform at least one operation on the journaling-capable file system. | 12-18-2014 |
| 20150088830 | MIRRORING, IN MEMORY, DATA FROM DISK TO IMPROVE QUERY PERFORMANCE - Techniques are provided for maintaining data persistently in one format, but making that data available to a database server in more than one format. For example, one of the formats in which the data is made available for query processing is based on the on-disk format, while another of the formats in which the data is made available for query processing is independent of the on-disk format. Data that is in the format that is independent of the disk format may be maintained exclusively in volatile memory to reduce the overhead associated with keeping the data in sync with the on-disk format copies of the data. | 03-26-2015 |
| 20150095286 | DATABASE AUDITING FOR BULK OPERATIONS - A method facilitates auditing of database transactions by maintaining logical consistency between a source database table and a shadow database table. A bulk command is received that specifies edits to a plurality of rows in the source database table. The bulk command is executed on the source database table. The shadow database table is queried to obtain an indication of the plurality of rows edited by the bulk command. The indication is stored as part of an audit trail for the source database table. | 04-02-2015 |
| 20150095287 | DATABASE AUDITING FOR BULK OPERATIONS - A method facilitates auditing of database transactions by maintaining logical consistency between a source database table and a shadow database table. A bulk command is received that specifies edits to a plurality of rows in the source database table. The bulk command is executed on the source database table. The shadow database table is queried to obtain an indication of the plurality of rows edited by the bulk command. The indication is stored as part of an audit trail for the source database table. | 04-02-2015 |
| 20150100551 | Database Virtualization - Aspects of the subject matter described herein relate database virtualization. In aspects, clusters of database servers may be located at various locations of the Internet. When a client seeks to access a logical database, the client may send a logical server and logical database name in a data structure. These names may be used to find a physical server(s) and database(s) that correspond to the logical database. Once the location is determined, a proxy component is used to intercept and/or forward communications between the client and the physical server(s) and database(s) corresponding to the logical database. Using this system, a client may access data from a logical database without knowing the physical address of the logical user database. | 04-09-2015 |
| 20150112940 | SYSTEM, INFORMATION PROCESSING APPARATUS, ACQUISITION METHOD, AND RECORDING MEDIUM - A system includes a plurality of nodes. Each of the plurality of nodes includes a processor that executes a process. The process includes: storing logs in a memory; requesting another node other than the node in which an abnormality has occurred to send information that indicates order the logs stored in the memory are created; receiving, from the other node, information that indicates order the logs stored in the other node are created; and acquiring, based on the order indicated by the received information and the order the logs stored in the memory are created, when the other node that stores therein a log that is created newer than the logs stored in the memory is present, the log created newer than the logs stored in the memory from the other node that stores therein the log created newer than the logs stored in the memory. | 04-23-2015 |
| 20150120668 | Method and System for Reducing Journaling Log Activity in Databases - Methods, devices and systems enable restoring a database system more efficiently. A server computing device may be configured to receive a database transaction request that includes information identifying a database operation, determine a priority value for the database operation, and add the database operation to a journaling log based on the determined priority value. After detecting a failure event, the server computing device may perform the database operations identified in the journaling log to restore the database system. | 04-30-2015 |
| 20150293966 | System and Method for Massively Parallel Processing Database - In one embodiment, a method of performing point-in-time recovery (PITR) in a massively parallel processing (MPP) database includes receiving, by a data node from a coordinator, a PITR recovery request and reading a log record of the MPP database. The method also includes determining a type of the log record and updating a transaction table when the type of the log record is an abort transaction or a commit transaction. | 10-15-2015 |
| 20150378830 | USE OF REPLICATED COPIES TO IMPROVE DATABASE BACKUP PERFORMANCE - A backup computing device detects an interruption while receiving a backup copy of a transaction log of a primary database and directs a secondary computing device to continue generation of the backup copy of the transaction log, based on the copy of the transaction log of the primary database. A primary computing device directs a secondary computing device to generate a backup copy of the data file and the primary computing device generates a backup copy of the transaction log, of a primary database. A primary computing device accesses a snapshot of a plurality of snapshots of a primary database, and generates a first portion of a backup copy of the database. The primary computing device directs a second computing device to generate a non-overlapping portion of the backup copy of the database based on a second snapshot of the plurality of snapshots. | 12-31-2015 |
| 20150378845 | ZERO DATA LOSS TRANSFER PROTOCOL - A method for reliable data synchronization within a network is disclosed. The producer system stories data in a persistent data store and produces one or more data updates. The producer system simultaneously transmits the data updates to a consumer system and initiating storage of the data updates at the producer system. When storage of the data updates at the producer system is complete, the producer system transmits a first acknowledgment to the consumer system. The producer system determines whether a second acknowledgment has been received from the consumer system, wherein the second acknowledgment indicates that the consumer system has successfully stored the data updates at the consumer system. In accordance with a determination that the second acknowledgment has been received from the consumer system, the producer system changes the temporary status of the data updates stored at the producer system to a permanent status. | 12-31-2015 |
| 20160012095 | INFORMATION PROCESSING METHOD, STORAGE MEDIUM, AND INFORMATION PROCESSING APPARATUS | 01-14-2016 |
| 20160048426 | METHOD AND DEVICE FOR BACKING UP DATA - The present disclosure relates to a method and a device for backing up data. The method includes: determining whether a new file of a predetermined type exists locally; calculating a checked value corresponding to the new file according to a predetermined algorithm if the new file of the predetermined type exists; sending a query request containing the checked value to a connected router, so as to query whether a file having the checked value is stored in the router; and backing up the new file to the router if determining that no file having the checked value is stored in the router according to a query result returned from the router. | 02-18-2016 |
| 20160078050 | Facilitating Handling Of Crashes In Concurrent Execution Environments Of Server Systems While Processing User Queries For Data Retrieval - A server system provided according to an aspect of the present disclosure forms physical queries to process a user query received from a client system. Each physical query is thereafter executed in a corresponding concurrent execution entity (e.g., thread) to retrieve a respective data portion from a corresponding data source. A response to the user query is formed based on the data portions. State information corresponding to each execution entity is logged into log storage. According to another aspect, when a query (either physical or user) causes an execution environment to crash, the identifier of such query is added to a prohibited list. When a new query is to be executed, the initiation of execution of the new query is prevented if the identifier of the new query is present in the prohibited list. | 03-17-2016 |
| 20160085639 | CONVERTING A SERIAL TRANSACTION SCHEDULE TO A PARALLEL TRANSACTION SCHEDULE - A method and system for transforming a serial schedule of transactions into a parallel schedule of transaction is disclosed. In one example, a computer system stores a list of data transactions in a transaction log. The computer system then reads a respective data transaction from the transaction log. The computer system determines whether the respective data transaction is dependent on any other currently pending data transaction. In accordance with a determination that the respective data transaction is not dependent on any other currently pending data transaction, the computer system applies the data changes to a reconstructed data set. In accordance with a determination that the respective data transaction is dependent on a currently pending second data transaction, the computer system delays commitment of the respective data transaction until the second data transaction has been applied to the reconstructed data set. | 03-24-2016 |
| 20160092464 | BUFFERING AND REPLICATING DATA WRITTEN TO A DISTRIBUTED STORAGE SYSTEM - Embodiments of the invention relate to small write performance enhancements for parallel file systems. One embodiment includes flushing a received write transaction from a first memory device to a second memory device on a node in a file system based on one or more byte-ranges within a file system block. It is determined to flush the received write transaction to a recovery log that is stored in a non-volatile storage layer of the file system. If it is determined to flush the received write transaction to the recovery log: appending data associated with the received write transaction in the recovery log of the file system, replicating the data associated with the received write transaction in another non-volatile storage layer of another node if required, and marking the one or more byte-ranges as committed. | 03-31-2016 |
| 20160147818 | METHOD AND SYSTEM TO REMOVE A SERVICE FROM A DISTRIBUTED DATABASE SYSTEM - A method, medium, and system to receive a request to remove a service of an instance of a distributed database system; redistribute data of the service to be removed to at least one remaining service of the distributed database system; save unsaved log segments of the service to be removed in a log backup; register removal of the service to be removed with the distributed database system; delete an entry of the service to be removed from a startup configuration of the distributed database system; halt operation of the service to be removed; and remove the halted service from internal topology information of the distributed database system. | 05-26-2016 |
| 20160179631 | TECHNIQUES FOR DATA BACKUP AND RESTORATION | 06-23-2016 |
| 20180024893 | INTELLIGENT BACKUP SYSTEM | 01-25-2018 |
| 20190147070 | USING PERSISTENT MEMORY TO ENABLE RESTARTABILITY OF BULK LOAD TRANSACTIONS IN CLOUD DATABASES | 05-16-2019 |
| 20220138056 | Non-Blocking Backup in a Log Replay Node for Tertiary Initialization - Disclosed herein are system, method, and computer program product embodiments for non-blocking backup for tertiary initialization in a log replay only node. An embodiment operates by performing a standard log replay on a secondary server and briefly suspending the standard log replay in response to tertiary initialization. Further, the secondary server may determine backup block information and perform a page-aligned backup process from the secondary server to a tertiary server. Additionally, the secondary server may determine log replay block information, and perform a modified log replay concurrently with the backup process based on the backup block information. | 05-05-2022 |
