Abstract: A request to restore a database to a particular point in time is received. It is determined that a closest preceding backup to the particular point in time is an incremental backup. One or more transaction log file segments needed to restore the database to the particular point in time are determined. An updated incremental backup is generated by applying the one or more determined transaction log file segments to the incremental backup. The updated incremental backup is restored to a primary system.

Abstract: The invention relates to data recovery technology. An archive connection driver creates a virtual storage medium that is readable by an operating system, with the operating system running antivirus scanning algorithms on the connected virtual storage medium. Corrupted data and malware are deleted and the relevant data blocks repaired in a connected backup. Corrupted data and infected files are restored in marked invalid data in the backup.

Abstract: A method that includes providing a database for storing meta-data that describes steps in a workflow and an order of the steps in the workflow. The meta-data includes, for each of the steps: a reference to an input data file for the step; a description of a transaction performed at the step; and a reference to an output data file generated by the step based at least in part on applying the transaction to the input data file. Data that includes meta-data for a step in the workflow is received and the data is stored in the database. A trace of the workflow is generated based at least in part on contents of the database. The generating is based on receiving a request from a requestor for the trace of the workflow. At least a subset of the trace is output to the requestor.

Abstract: In some embodiments, a method receives data for a block in a blockchain during a recovery process in which a recovering replica is recovering the block for a first instance of the blockchain being maintained by the recovering replica. The block is received from a second instance of the blockchain being maintained by a source replica. The method splits the data for the block into a plurality of chunks. Each chunk includes a portion of the data for the block; It is determined whether the recovering replica can recover a chunk in the plurality of chunks using a representation of the chunk. In response to determining that the recovering replica can recover the chunk, sending the representation of the chunk to the recovering replica. In response to determining that the recovering replica cannot recover the chunk, sending the data for the chunk to the recovering replica.

Abstract: Source database precommitted transactions are resolved in a target database of a database replication system when selected source database precommitted transactions are subsequently aborted in the source database.

Abstract: Embodiments of the present disclosure relate to a method for storage management, an electronic device, and a computer program product. According to an exemplary implementation of the present disclosure, a method for storage management includes: generating, at a client, a first backup block for recovering first target data, the client backing up the first target data to a first server and backing up metadata of the first target data to a second server, and the client together with at least one other client and the second server maintaining the same backup chain which includes at least one backup block; adding the first backup block to the backup chain maintained by the client; and distributing the first backup block to the at least one other client and the second server to add the first backup block to the backup chain maintained by the at least one other client and the second server. Therefore, the storage security can be improved.

Abstract: In an approach for improving performance of a batch job running on database servers in an active-active architecture. A processor, responsive to a batch job being ready to be executed on a source database server, sends a first communication to a target database server with a synchronization start point. While executing the batch job, a processor utilizes a pre-lock function, pre-load function, and lock avoidance function to prevent lock conflicts. A processor, responsive to either the source database server or the target database server encountering a commit statement, suspends the respective database server and sends a second communication to ask if the other respective database server is ready to complete the commit statement. A processor, responsive to the other respective database server confirming its ready to complete the commit statement, completes the commit statement on both the source database server and the target database server.

Abstract: Technologies are described for performing replication of data within a database environment having a source node and a replica node. The source node executes a database operation on at least one database table stored by the source node. The source node asynchronously sends the database operation to the replica node. A prepare commit request is synchronously sent from the source node to the replica node. The source node receives a synchronous precommit acknowledgement from the replica node. The precommit acknowledgement indicates that the database operation was executed at the replica node. The source node commits a transaction associated with the database operation.

Abstract: Target database constraint violations are potentially resolved in a database replication system by replacing, converting, or removing deferred database changes.

Abstract: Techniques for intelligently scheduling resynchronization jobs in a distributed object-based storage system are provided. In one set of embodiments, a storage node of the system can create a resynchronization job for a component of an object maintained by the system, where the resynchronization job defines one or more input/output (I/O) operations to be carried out with respect to the component. If a number of currently running resynchronization jobs on the storage node has reached a threshold, the storage node can further determine a priority level associated with the object; add the resynchronization job to an object queue for the object; and if the added resynchronization job is a first job in the object queue, add the object queue as a new queue entry to a global priority queue corresponding to the priority level associated with the object.

Abstract: A system that manages backups of filesystems. The system analyzes and presents changes in a file system. The system generates user interfaces that present changes to files in the filesystem. The user interfaces allow users to traverse the filesystem to view changes in the filesystem. The changes include file operations that took place during a time interval. As such, users can ascertain a filesystem behavior such as which files were added, modified, or deleted during a time period; how many files under a folder were added, modified, or deleted; or which user has issued most operations in a time interval.

Abstract: An extractor and an applier of a database replication system are configured to perform the functions of resolving target database constraint violations for replicated database transactions. The extractor replicates changes made at the source database to the target database. An applier immediately applies the changes to the target database that do not cause a constraint violation. The applier also performs the remaining functions, including detecting database changes that cause constraint violations, subsequent processing of these detected database changes, and performing a commit for the database transaction when the constraint violations are resolved.

Abstract: Technologies are described for performing replication of data within a database environment having a source node and a replica node. The source node executes a database operation on at least one database table stored by the source node. The source node asynchronously sends the database operation to the replica node. A prepare commit request is synchronously sent from the source node to the replica node. The source node receives a synchronous precommit acknowledgement from the replica node. The precommit acknowledgement indicates that the database operation was executed at the replica node. The source node commits a transaction associated with the database operation.

Abstract: Distributed storage systems frequently use a centralized metadata repository that stores metadata in an eventually consistent distributed database. However, a metadata repository cannot be relied upon for determining which erasure coded fragments are lost because of a storage node(s) failures. Instead, when recovering a failed storage node, a list of missing fragments is generated based on fragments stored in storage devices of available storage nodes. A storage node performing the recovery sends a request to one or more of the available storage nodes for a fragment list. The fragment list is generated, not based on a metadata database, but on scanning storage devices for fragments related to the failed storage node. The storage node performing the recovery merges retrieved lists to create a master list indicating fragments that should be regenerated for recovery of the failed storage node(s).

Abstract: Techniques are described for maintaining coherency of a portion of a database object mirrored in a particular node of a database. The techniques involve maintaining invalidation logs which identify transactions that have committed to a database. Based on the invalidation logs, the particular node generates invalid-row ID metadata which identifies, for each system change number, one or more rows that are not transactionally consistent with data stored in the database object as of said system change number.

Abstract: A system and method enable the modification of software data queries for the purpose of overcoming the problem of large, cumbersome data queries. The method and system presented includes a client device, which may split a software data query into segments representing a fraction of the original query size, and submit the divided data query to a remote server. The division of the initial query may continue until the query size is usable by the remote server. The remote server may receive the segmented query, and transmit database records associated with the fields in the divided query to the client device. Further segments of the divided query may be transmitted until the full query has been transmitted to the remote server. The divided queries may include date time stamp bounds to determine the desired database records. A computing device created specifically for the above-listed tasks may be utilized.

Abstract: An extractor and an applier of a database replication system are configured to perform the functions of resolving constraint violations for replicated database transactions. The extractor replicates changes made at the source database to the target database. An applier immediately applies the changes to the target database that do not cause a constraint violation. The applier also performs the remaining functions, including detecting database changes that cause constraint violations, subsequent processing of these detected database changes, and performing a commit for the database transaction when the constraint violations are resolved.

Abstract: Systems, methods, and computer program products to perform an operation comprising identifying a first access to a first subset of a first database table on a first storage node, of a plurality of storage nodes, identifying a second access to a second subset of the first database table on a second storage node, of the plurality of storage nodes, and performing a predefined operation to restrict access to the first database table on the plurality of storage nodes based on the first and second accesses.

Abstract: Disclosed herein are system, method, and computer program product embodiments for synchronizing lost change between a source table and a replica table. An embodiment operates by detecting a restart at a source node or a replica node. Row-ID values of replication log entries are then compared to row-ID column values of rows at a replica table of the replica node. Replication errors at a source table or the replica table are then determined based on the row-ID comparison. The rows of the source table and the replica table are then updated based on the determination.

Abstract: A computer-implemented method for virtual machine boot disk restoration may include (1) identifying a hypervisor that hosts at least one virtual machine, where a replication system is configured to replicate virtual machine data stored by the virtual machine, including a virtual machine boot disk used by the virtual machine, to a data repository that is separate from the hypervisor, (2) determining that the replication system is to restore the replicated virtual machine data back to the hypervisor for the virtual machine, including boot disk data replicated from the virtual machine boot disk, (3) attaching, at the hypervisor, the virtual machine boot disk to a storage proxy virtual machine hosted by the hypervisor, and (4) restoring, from the replication system and via the storage proxy virtual machine, the boot disk data back to the virtual machine boot disk. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Various systems and methods for determining whether a distributed storage cluster is operating with a last failure domain are disclosed. The last failure domain is the only node with access to a latest copy of configuration data and an up-to-date copy of application data. In response to a determination that the distributed storage cluster is operating with the last failure domain, the method causes the last failure domain to copy one or more changed blocks of the up-to-date copy of the application data from one or more mirrored volumes to a recovery server for storage.

Abstract: Features are disclosed for modifying identifying data including, but not limited to, demographic information, user identifiers, and device identifiers, according to user-definable preferences prior to transmitting content requests to content servers. The information may be modified to protect a user's privacy. In addition, the modified information may allow the content provider to serve a customized or targeted version of content that is more relevant to the user than a version that may otherwise be generated without the aid of identifying data. Users may elect to share some, all, or none of their identifying data with content providers, or users may elect to generalize their specific identifying data. Additional features include providing generalized or customized identifying data to cooperating content providers. Custom headers and other data fields may be provided to content providers, and content providers may choose to use information in the custom data fields or ignore it.

Abstract: Example apparatus and methods create and maintain a functional mirror of file system metadata for an active file system. The functional mirror may be implemented as a set of database tables that allow a journal functionality for information received from the active file system. Example apparatus and methods also restore the file system metadata from the functional mirror. Mirror creation and maintenance can operate in parallel. Mirror maintenance and metadata restore can also operate in parallel. The functional mirror may be created primarily using a systematic, system-wide, multi-threaded crawler approach whose results are updated using an event-driven approach that accounts for changes that may make obsolete information acquired during the crawler approach. The metadata may be restored using a systematic, system-wide, multi-threaded crawler approach acting together with an event-driven approach that restores certain files out of order as they are needed.

Abstract: A computer-implemented method for detecting malware may include 1) identifying a file represented within a file system by a file name, 2) identifying a creation of a hard link to the file that uses an additional file name, 3) updating a database with an association between the file name and the additional file name, 4) identifying a file-closing operation within the file system and determining that the target file name of the file-closing operation was removed from the file system after the file-closing operation, 5) querying the database with the target file name and identifying an existing file name representing the file based on the association, and 6) scanning the existing file name for malware in response to the file-closing operation instead of scanning the target file name because the target file name was removed from the file system. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: A method of managing backup data. The method includes accessing, via a backup manager, index data of an initial snapshot and accessing, via the backup manager, index data of a subsequent snapshot. The method further includes determining, via the backup manager, whether the index data of the subsequent snapshot is different from the index data of the initial snapshot. Responsive to a determination that the index data of the subsequent snapshot is different from the index data of the initial snapshot, creating an updated index data and creating an updated snapshot with the updated index data.

Abstract: Systems and methods for restoring files and metadata records associated with files are provided herein. Some of the methods include identifying a version of the file, evaluating one or more reverse incremental delta increments, and restoring an arbitrary version of the file based on an arbitrary time reference by assembling the arbitrary version of the file based on the one or more reverse incremental delta increments.

Abstract: A corrupted database is returned to a correct state by rolling forward or backward through a change queue and applying changes to the database in a selective manner. Changes that did not cause the corruption are applied without modification when rolling forward or are skipped when rolling backward. Changes that caused corruption are addressed when rolling forward, such as by being ignored or modified and then applied. Changes that caused corruption are corrected when rolling backward.

Abstract: Systems and methods for restoring files and metadata records associated with files are provided herein. Some of the methods include identifying a version of the file, evaluating one or more reverse incremental delta increments, and restoring an arbitrary version of the file based on an arbitrary time reference by assembling the arbitrary version of the file based on the one or more reverse incremental delta increments.

Abstract: The present description refers to a computer implemented method, computer program product, and computer system for receiving a start time, selecting one or more database objects for which a database recovery progress report is to be provided, determining, based on an object recovery table generated by the database recovery utility, which of the selected database objects have been recovered since the start time, and outputting a database recovery progress report that identifies at least a number or percentage of the selected database objects that have been recovered by the database recovery utility since the start time.

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 interface receives an indication to revert data stored in the data storage system to a state of data at a snapshot time stored in the deduplicating system. The processor is configured to determine a subset of the data stored in the data storage system that has changed between the data stored in the data storage system and the state of data at the snapshot time stored in the deduplicating system using a first list of fingerprints associated with the data stored on the data storage system and a second list of fingerprints associated with the state of data at the snapshot time stored in the deduplicating system.

Abstract: A system and method for restoring data including a workflow from an archived copy of a database file. The method includes receiving a request to restore a workflow from an archived copy. The workflow comprises attributes describing a sequence of conditions and actions corresponding to an item and comprises a history log. The item may comprise an electronic document and associated context information describing the document in an intranet portal application environment. The associated context information includes an identifier corresponding to the workflow. The method includes retrieving records comprising the workflow attributes from the archived copy. The method further includes generating from the retrieved records a workflow metadata file comprising tagged elements corresponding to the workflow attributes and history log. Then the method stores the workflow metadata file in a file system. The method further includes restoring the workflow to the intranet portal application via the file system.

Abstract: Systems and methods are disclosed for recovering data following a directory service malfunction, such as a forest-wide disaster in Microsoft® Active Directory. In certain examples, a single management console can be used for remotely recovering selected domain controllers in the forest without necessitating direct operator intervention. Multiple domain controllers can be concurrently restored from one or more backup files. Configurations of the system can advantageously eliminate manual intervention with each domain controller, thereby saving significant amounts of recovery time and effort. Also, certain systems and methods can be used to automatically and remotely quarantine corrupt domain controllers so that those individual domain controllers do not replicate with the newly restored environment, while allowing the domain controllers to remain online and in communication with the attached network.

Abstract: Provided are a computer program product, system, and method for restoring objects in a client-server environment. An entry is added to an index for each chunk identifier. Each index entry includes one of the chunk identifiers and a reference to the chunk of data in the target storage from which the chunk identifier was calculated. A request is transmitted to a server recovery agent to recover an object from the storage server. Chunk identifiers of chunks of data in the requested object to recover are received from the server recovery agent. A determination is made from the index of whether the received chunk identifiers for the requested object matches the chunk identifiers indicated in the index. A request is made of the chunks from the server recovery agent for the received chunk identifiers not matching chunk identifiers in the index entries.

Abstract: Techniques for providing a differential backup from a storage image are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for providing a differential backup from a storage image comprising identifying one or more dirty blocks in a storage image, creating a differential backup data structure, and transmitting the one or more dirty blocks to a data management process utilizing the differential backup data structure to provide a differential backup.

Abstract: An information handling system detects that a first electronic mail message has been permanently deleted from a local memory of a first information handling system, generates a second electronic mail message to request a recovery of the first electronic mail message, attaches a file to the second electronic mail message, and sends the second electronic mail message to a plurality of second information handling systems.

Abstract: Various embodiments of a system and method for restoring a plurality of files previously deleted from a volume are described. For each respective file of the plurality of deleted files, the method may operate to determine a time at which the respective file was last modified and a time at which the respective file was deleted. These times define a respective recovery time window for the respective file. The method may further comprise determining a particular point in time that is within the recovery time windows for two or more of the plurality of deleted files. A temporary version of the volume as it existed at the particular point in time may be created, and each file of the two or more files may be restored to the volume from the temporary version of the volume.

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 computer-based system includes a backup server, a production server, a recovery agent that executes on the production server, a database on the production server, a backup database on the backup server, and a meta data file on the backup server. The meta data file includes file names, a file directory, and file attributes. The system is configured to copy the metadata file from the backup server to a production server. When the copying of the metadata file from the backup server to the production server is complete, and before or during a time period in which backup data is copied from the backup server to the production server, the system is configured to receive a request from the production server to restore a file from the backup server with a higher priority than other files on the backup server.

Abstract: A method begins with a computing device of a dispersed storage network (DSN) determining that an encoded data slice of a set of encoded data slices requires rebuilding and sending partial rebuild requests to storage units of the DSN. The method continues with one of the storage units generating a partial rebuilt slice based one or more encoded data slices of the set of encoded data slices stored by the one of the storage units and securing the partial rebuilt slice using a shared secret scheme that is shared among the storage units to produce a secured partial rebuilt slice. The method continues with the computing device receiving a set of secured partial rebuilt slices from the storage units, recovering a set of partial rebuilt slices from the set of secured partial rebuilt slices, and rebuilding the encoded data slice from the set of partial rebuilt slices.

Abstract: Recovering from a failure of a soon-to-fail database system among a plurality of database systems in a multi-database system in processing a request submitted to the multi-database system through a multi-database system session is accomplished. A query band is created for the request. The query band is defined to be an identifier that uniquely identifies the session and the request among the plurality of sessions and plurality of requests being processed by the multi-database system at the time that the request was submitted. The query band is attached to a transaction issued by the multi-database system to the soon-to-fail database system to execute the query. The status concerning execution of the transaction is reported by the soon-to-fail database system. The status includes the query band. The status is logged. The failure of the soon-to-fail database system is detected.

Abstract: A cluster network environment may comprise a plurality of nodes configured to perform various tasks, such as data I/O, storage, backup, etc. It may be advantageous to improve disaster recovery and reliability by creating backups that may be used to restore the cluster network environment and/or nodes therein. Accordingly, one or more techniques and/or systems are disclosed for restoring a cluster network environment and/or nodes therein. In particular, cluster configuration data, which may be stored in a healthy node or at a remote source, may be used to restore a node affected by an integrity loss. If the integrity loss affects the cluster network environment (e.g., a majority of healthy nodes are lost), then a new cluster network environment may be created from a healthy node or a restored healthy node. The creation of the new cluster network environment may be based at least in part on cluster configuration data.

Abstract: A method and apparatus for recovery a cluster database is provided. Database recovery is divided among a plurality of surviving database server instances in the cluster. A surviving instance is responsible for recovering data blocks to which the surviving instance is assigned. One form of block-to-instance assignment may be based on mastership of the blocks. If a data block is locked by a surviving instance at the time of failure, then no recovery of that data block may be necessary. Else, if a copy of a data block that is to be recovered is stored on a surviving node in the cluster, then one or more redo records are applied to that copy (if necessary). A redo record that corresponds to that data block might not need to be applied to the copy if the redo record reflects changes (to the data block) that are already reflected in the copy.

Abstract: A system for storing encrypted data comprises a processor and a memory. The processor is configured to receive an encrypted segment. The encrypted segment is determined by breaking a data stream, a data block, or a data file into one or more segments and encrypting each of the one or more segments. The processor is further configured to determine whether the encrypted segment has been previously stored, and in the event that the encrypted segment has not been previously stored, store the encrypted segment. The memory is coupled to the processor and configured to provide the processor with instructions.

Abstract: System and method for distributing volume status information in a storage system. According to one embodiment, a system may include a plurality of volumes configured to store data, where the volumes are configured as mirrors of one another, and a plurality of hosts configured to access the plurality of volumes. A first one of the plurality of hosts may be configured to execute a mirror recovery process and to maintain a progress indication of the mirror recovery process, and the first host may be further configured to distribute the progress indication to another one or more of the plurality of hosts.

Abstract: An embodiment of a method of restoring data begins with a step of restoring point-in-time data from a local copy. The method concludes with a step of restoring at least a portion of an incremental difference between the point-in-time data and a desired state of the data from a remote mirror.

Abstract: Embodiments of the invention detect inadvertent or malicious data corruption and for recovering data including receiving a query specifying corrupted application data; analyzing transaction logs to find update operations related to the data; determining where the data are stored, by mapping the table data to locations within the file system and mapping the file system locations to volume logical blocks; and analyzing snapshot volume bitmaps to determine if the bitmaps show changes to the table data stored in the volume logical blocks. Changes which are reflected in the bitmaps for the data, but which do not have corresponding entries in the transaction logs are flagged as unauthorized changes. Snapshots of the data, from a time prior to the time at which a flagged snapshot was taken, are identified for use in restoring data to its status prior to the unauthorized change.

Abstract: A method of recovering a value in a data storage system includes maintaining a list of entries corresponding to values that have been inserted into the data storage system, determining whether the values are at an At Maximum Redundancy (AMR) state, and if not, the converging the values to the AMR state.

Abstract: Provided are a method, system, and computer program product for creating a buffer point-in-time copy relationship for a point-in-time copy function executed to create a point-in-time copy relationship. A point-in-time copy function is initiated to create a new point-in-time copy relationship from a source volume comprising a first volume to a target volume comprising a second volume. Detection is made that the target volume of the new point-in-time copy relationship is a source volume of a first pre-existing point-in-time copy relationship having as a target volume a third volume. Detection is also made that the target volume of the first pre-existing point-in-time copy relationship is a source volume of a second pre-existing point-in-time copy relationship having as a target volume a fourth volume.

Abstract: Systems and methods are disclosed for recovering data following a directory service malfunction, such as a forest-wide disaster in Microsoft® Active Directory. In certain examples, a single management console can be used for remotely recovering selected domain controllers in the forest without necessitating direct operator intervention. Multiple domain controllers can be concurrently restored from one or more backup files. Configurations of the system can advantageously eliminate manual intervention with each domain controller, thereby saving significant amounts of recovery time and effort. Also, certain systems and methods can be used to automatically and remotely quarantine corrupt domain controllers so that those individual domain controllers do not replicate with the newly restored environment, while allowing the domain controllers to remain online and in communication with the attached network.

Abstract: A method and system for detecting the transmission of preidentified content, such as copyrighted material, over an Internet Service Provider (ISP) network. A set of rules is provided to identify one or more traffic flow profiles of data streams transmitting preidentified content. Preferably the rules are adaptively created through analysis of actual ISP data in conjunction with data suggesting an initial set of profile characteristics. The rules are applied to data streams being transmitted in the ISP network, so that data streams fitting one or more of the profiles are identified. A database contains, e.g., as digital signatures or fingerprints, one or more items of content whose transmission is sought to be detected. Data streams identified as matching a profile are analyzed to determine if their content matches an item of content in the database, and if so, an action is taken which may include interrupting the transmission, suspending an ISP account, or reporting the transmission.