Abstract: A computer-implemented method (and structure) includes receiving information. The received information is converted into a strictly hierarchical data format. A precision for a releasing the strictly hierarchical data is calculated based on privacy protection levels and a reward for different precision levels. The strictly hierarchical data is sequentially released at the calculated precision.

Abstract: A data storage apparatus includes a nonvolatile memory device, a random-access memory including an address mapping table configured to store mapping information between a logical address received from a host apparatus and a physical address for the nonvolatile memory device, and a processor configured to generate a modified write logical address by changing a value of a specific bit among bits of a write logical address when a write request is received from the host apparatus, and store the modified write logical address in the address mapping table.

Abstract: Example implementations relate to configuration item integrity. For example, a computing device may include a processor. The processor may receive a request for feedback specifying data integrity associated with a configuration item migrated from a first system to a second system. The configuration item is associated with a data source. The data integrity indicates quality and completeness of the configuration item. The processor may identify anomalies associated with the configuration item and unresolved conflicts between the configuration item and at least one other data source. The processor may generate a high availability and disaster recovery forecast associated with the configuration item and may calculate the data integrity based on the anomalies, the unresolved conflicts, and the high availability and disaster recovery forecast. The processor may provide the feedback specifying the data integrity.

Abstract: A system, method and computer program product for restoration of MICROSOFT Exchange Server mail. MICROSOFT Exchange Server mail is retrieved from a virtual copy of the MICROSOFT Exchange database. Virtualization is implemented by a system filter. Logs are applied to a virtualized DB in order to synchronize it with a real DB of the MICROSOFT Exchange. The data located in the remote archive does not need to be copied into the real folder, because the data is made available by virtualization means. After the logs are applied, the virtualized DB is opened (without being mounted) from files from the virtual folder. From this point on, the DB of MICROSOFT Exchange can be viewed and the data can be queried and retrieved from the virtualized DB. Thus, a single message or a mailbox can be retrieved very fast, as if it were being retrieved from a real MICROSOFT Exchange DB.

Abstract: Crash recovery of a computing system in the context in which the computing system includes a volatile memory which has contents lost due to the crash, an intermediate non-volatile memory that (together with the volatile memory) contributes to the active memory of the computing system, and non-volatile storage. The recovery occurs by identifying pages that were in the volatile memory at the time of the crash and that are in the intermediate non-volatile memory and recovers those pages into the volatile memory. In embodiments in which access speeds for the intermediate non-volatile memory may be much faster than for the storage, and in which much of the pages to be recovered are recovered from the intermediate non-volatile memory, the recovery time may be reduced.

Abstract: Altering a database structure based on software updates in a distributed computing system can include identifying a plurality of software updates that include alterations to structural elements in the database structure and identifying, for the plurality of software updates, a plurality of alterations corresponding to a first structural element of the structural elements. A combined alteration can be generated by combining the plurality of alterations. A database statement can be generated for altering the first structural element according to the combined alteration. The database structure can then be updated using the database statement. The structural elements can define logical relationships between data stored in the database structure. The alterations can be expressed using a markup language and the database statement can be expressed using a query language.

Abstract: A method for execution by one or more processing modules of one or more computing devices of a dispersed storage network (DSN), the method begins by, receiving a write data object request and writing and committing the data object as a set of encoded data slices into DSN memory. The method continues by writing and committing an index consistency write-intent to DSN memory. The method continues by writing metadata of the data object to DSN memory. The method continues by write and committing an index entry to DSN memory. The method continues, during a finalization of the index consistency write-intent, by executing the index consistency write-intent to ensure consistency between the metadata of the data object and metadata located in the index entry.

Abstract: According to embodiments of the present invention, a metadata file is transferred from the first system to the second system and a database on the second system is initialized based on the metadata file. An image, including information of the first system to be restored, is transferred from the first system to the second system, and restoration of the information to the second system based on the image is initiated. Prior to completion of the restoration, one or more log files indicating actions performed on the first system relating to the information to be restored is transferred from the first system to the initialized database on the second system. In response to completion of the restoration, the actions of the log files are performed to synchronize the restored data on the second system with the first system.

Abstract: A facility comprising methods and systems for analyzing and visualizing trends in the usage of data within a shared storage filesystem is disclosed. The facility analyzes the rate at which the filesystem or a portion thereof is used by periodically generating manifests of the usage of the filesystem and comparing one manifest to another manifest. Furthermore, the facility may store additional information relevant to the manifest, such as the time at which the manifest was taken; for each directory, the sum of all of the values determined for items in that directory (including any subdirectories); and so on. In this manner, the facility collects and stores information relevant to developing trend information for each item in the filesystem. The trends analysis and visualizations described herein provide quick insight into the changes deemed most interesting or significant between two times.

Abstract: Embodiments are provided for replicating a relational source database associated with a transaction log of the relational source database. In operation, embodiments may perform receiving a request for replicating data of the relational source database to a relational target database and identifying a first start position within the transaction log. Upon having identified the first start position, embodiments may further perform waiting at least a time period for ensuring that each transaction currently executing on the relational source database at a moment of receiving said request has terminated at an end of said time period. After having waited said time period, embodiments may perform an asynchronously creating of a copy of data of the relational source database to produce a created copy. In turn, embodiments may perform writing the created copy to the relational target database and identifying a repair start position within the transaction log.

Abstract: Some examples include backing up and restoring an application state across multiple devices. For example, an instance of a computer application may be executed at a first electronic device and a backup event that occurs in the first electronic device may be determined. The backup event may suggest a backup of application state data and the application state data may represent an application state of the computer application at the backup event. The application state data of the computer application is transmitted to a remote storage service in response to the backup event. A second electronic device can retrieve the application state data from the remote storage service and restore the application state.

Abstract: A cluster of nodes can receive a request to perform a logging operation of a distributed data storage application. The logging operation can include writing of data to a secondary storage of each of the nodes of the plurality of nodes. The request can include an indication of a durability mode to use for the logging operation. The logging operation can be initiated at each node of the plurality of nodes according to the indication of the durability mode, a completion callback can be run at each node of the plurality of nodes according to the indication of the durability mode, a global durability state and a global commit state can be determined for the cluster, and a reply can be returned to the request once the global durability state and global commit state are consistent with the indication of the durability mode to be used for the logging operation.

Abstract: A memory system for utilizing a deduplication process may include a controller, a storage media, and a non-volatile RAM including a metadata journal and a metadata cache, the metadata cache including an address table and a fingerprinting table, and the metadata journal including a plurality of transactions indicating whether a transaction is successfully written on the storage media.

Abstract: A journaled database system may comprise data nodes that maintain a collection of data structured in accordance with a schema. A change to the schema may be applied by a journal module while a journal consumer continues to operate using a prior version of the schema. A buffer may be formed and have stored therein records describing state change instructions according to the prior view of the schema. An index of correspondence between the records in the buffer and in the source journal may be maintained.

Abstract: A backup system and method for a large data store employs a new and enhanced summary change log data structure that records all file system changes comprises inode entry records augmented with additional fields to indicate inodes representing related child and parent file system objects. A single preprocessing pass through the summary change log augments all of the appropriate inode fields with the appropriate inode numbers of family members to create a graph structure that can be traversed in hierarchical order starting at a root inode to quickly identify all created and modified file system objects for inclusion in an incremental backup.

Abstract: For data backup and recovery based on linked file repositories with each of the linked file repositories representing an individual file system capable of storing at least one version of a file and being connected to at least one server system, each of the linked file repositories are placed in a certain position for storing a certain version of the file. Each position of each of the linked file repositories is continuously numbered. A number of the versions of the file are determined by the position of the one of the linked file repositories.

Abstract: A first compute node of a plurality of compute nodes of a database cluster may receive a request for a database transaction from a client application. The client application may be located within the first compute node. A first connection may be established, without regard to whether another compute node has a lighter workload than the first compute node, between the client application and a first database of the database cluster. The first connection may be a local connection, wherein the first database is located within the first compute node. The first compute node may detect that a failure associated with the first database has occurred. The first compute node may execute a failover operation to continue servicing the request for the data. The executing of a failover operation may include establishing a second connection between the client application and a second database of the database cluster.

Abstract: Described embodiments provide methods and systems for smoothly restarting a crashed storage cluster application associated with a storage cluster of a storage system. A survivor process associated with each storage cluster application is started. If a crash of at least one of the storage cluster applications is detected, the storage system performs a smooth restart of the at least one crashed storage cluster application. A smooth restart of the at least one crashed storage cluster application is performed according to a new storage cluster application that is configured to replace the crashed storage cluster application by managing open handles associated with the crashed storage cluster application.

Abstract: Technologies are generally described for systems and methods effective to provide a seamless backup and recovery of applications using metadata. In an example, metadata can be defined to map data associated with an application and provide the relationship of the data to the application. From the metadata, a backup system can create a capsule containing application data, and a payload containing application related data. The capsule can contain not just the application data, but also configuration information, and access parameters. The capsule and payload can be associated together and saved by the backup system. In another example, to recover an application, a capsule and a payload can be retrieved, and using the metadata, the capsule can be unpacked to reinstall the application to the same state it was in when backed up, and the application related data can be restored from the payload.

Abstract: A first compute node of a plurality of compute nodes of a database cluster may receive a request for a database transaction from a client application. The client application may be located within the first compute node. A first connection may be established, without regard to whether another compute node has a lighter workload than the first compute node, between the client application and a first database of the database cluster. The first connection may be a local connection, wherein the first database is located within the first compute node. The first compute node may detect that a failure associated with the first database has occurred. The first compute node may execute a failover operation to continue servicing the request for the data. The executing of a failover operation may include establishing a second connection between the client application and a second database of the database cluster.

Abstract: A controller-implemented method, according to one embodiment, includes: restoring a valid snapshot of a LPT from the non-volatile random access memory, examining each journal entry from at least one journal beginning with a most recent one of the journal entries in a most recent one of the at least one journal and working towards an oldest one of the journal entries in an oldest one of the at least one journal, the journal entries corresponding to updates made to one or more entries of the LPT, determining whether a current LPT entry which corresponds to a currently examined journal entry has already been updated, using the currently examined journal entry to update the current LPT entry in response to determining that the current LPT entry has not already been updated, and discarding the currently examined journal entry in response to determining that the current LPT entry has already been updated.

Abstract: The present invention provides a mechanism for generating an initial copy in replication initialization. A request is received to replicate a source volume from a source node to a target node so as to generate the initial copy of the source volume in the target node. With respect to a current source data block of at least one source data block contained in the source volume, a search in the target node is performed for a target data block corresponding to the current source data block. Responsive to identifying the target data block, the initial copy of the source volume in the target node is updated using the target data block with the information from the current source data block.

Abstract: A method of establishing communication links during a failure within a mobile communications network includes detecting disruptions in communications between a plurality of base stations and a plurality of mobile terminals. Survivability components are activated within the base station and the mobile terminal to operate in a survivability mode. The survivability mode enables communications and services to be provided by the surviving base stations to mobile terminals through activated survivability components. The alternate communication links may operate for as long as a disruption exists.

Abstract: A system includes reception of a command to recover a database to a point in time, determining a log backup which covers the point in time, determination of a sequence identifier associated with the log backup, collection of log backups which are older than the determined log backup and associated with the sequence identifier, and a data backup associated with the sequence identifier, and execution of a recovery of the database based on the determined log backup and the collected log backups and data backup.

Abstract: 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.

Abstract: In one example, a method for backing up data is performed in part by a manager server that receives a request for a deviceless backup session. The manager server authenticates the request and authorizes media database and index database operations. Next, the requested deviceless backup session is created and a backup session ID is transmitted that corresponds to the created deviceless backup session. The manager server then spawns an agent to handle communications with other devices. An update is then received concerning a backup performed with respect to a target device, and a confirmation sent that that the backup has been completed. Catalogue information concerning the completed backup is then received and stored, and the deviceless backup session and agent terminated.

Abstract: An information management system according certain aspects may be configured to generate a snapshot of data relating to a plurality of applications. The system may include first and second data agents associated with first and second applications, respectively. The system may also include a snapshot manager configured to: in response to receiving notifications from the first and second data agents that the first and second applications are in consistent states: obtain a snapshot of the logical volume including data generated by the first and second applications; generate mapping information between the first application and a portion of the snapshot relating to the first application based at least in part on metadata obtained by the first data agent; and generate mapping information between the second application and a portion of the snapshot relating to the second application based at least in part on metadata obtained by the second data agent.

Abstract: The systems and methods disclosed herein transparently provide an improved scalable cloud-based dynamically adjustable or configurable storage volume. In one aspect, a gateway provides a dynamically or configurably adjustable storage volume, including a local cache. The storage volume may be transparently adjusted for the amount of data that needs to be stored using available local or cloud-based storage. The gateway may use caching techniques and block clustering to provide gains in access latency compared to existing gateway systems, while providing scalable off-premises storage.

Abstract: Described herein are systems and methods to process efficiently, according to a certain order, a plurality of data sets arranged in data blocks. In one embodiment, a first compute element receives from another compute element a first set of instructions that determine an order in which a plurality of data sets are to be processed as part of a processing task. Relevant data sets are then streamed into a cache memory associated with the first compute element, but the order of streaming is not by order of storage but rather by the order conveyed in the first set of instructions.

Abstract: A method of creating a new layer for an information handling system is disclosed. A layering client mounts a new layer at a layer storage medium accessible to the information handling system. A layering file system filter driver redirects a request to create a new file at a target file path to the layer storage medium and updates the file metadata to associate the target file path with the path to file created on the layer storage medium.

Abstract: Described herein are systems and methods to redirect data read requests from the first tier to the second tier of a two-tier distributed memory. The first tier includes memory modules with data sets. Data interfaces associated with the first tier memory modules, receive from a second tier including compute elements and associated cache memories, requests to fetch data from the first tier. If a data set has not recently been fetched by the second tier, then the data interface will send the data set from the first tier to the cache memory associated with the requesting compute element. If a data set has recently been fetched by the second tier, the data interface will redirect the requesting compute element to fetch the data set from the cache memory in which the data set is currently located.

Abstract: Clients send telemetry data to a cloud server, where the telemetry data includes security-related information such as file creations, timestamps and malware detected at the clients. The cloud server analyzes the telemetry data to identify malware that is currently spreading among the clients. Based on the analysis of the telemetry data, the cloud server segments malware definitions in a cloud definition database into a set of local malware definitions and a set of cloud malware definitions. The cloud server provides the set of local malware definitions to the clients as a local malware definition update, and replies to cloud definition lookup requests from clients with an indication of whether a file identified in a request contains malware. If the file is malicious, the client remediates the malware using local malware definition update.

Abstract: A first compute node of a plurality of compute nodes of a database cluster may receive a request for a database transaction from a client application. The client application may be located within the first compute node. A first connection may be established, without regard to whether another compute node has a lighter workload than the first compute node, between the client application and a first database of the database cluster. The first connection may be a local connection, wherein the first database is located within the first compute node. The first compute node may detect that a failure associated with the first database has occurred. The first compute node may execute a failover operation to continue servicing the request for the data. The executing of a failover operation may include establishing a second connection between the client application and a second database of the database cluster.

Abstract: An embodiment includes a low-latency mechanism for performing a checkpoint on a distributed application. More specifically, an embodiment of the invention includes processing a first application on a compute node, which is included in a cluster, to produce first computed data and then storing the first computed data in volatile memory included locally in the compute node; halting the processing of the first application, based on an initiated checkpoint, and storing first state data corresponding to the halted first application in the volatile memory; storing the first state information and the first computed data in non-volatile memory included locally in the compute node; and resuming processing of the halted first application and then continuing the processing the first application to produce second computed data while simultaneously pulling the first state information and the first computed data from the non-volatile memory to an input/output (IO) node.

Abstract: A system includes reception of a transaction to change a columnar table, recordation of the transaction within a delta structure in a volatile memory, recordation of the transaction within a log of a persisted memory, reception of an instruction to merge the delta structure in the volatile memory with a first instantiation of the columnar table in the volatile memory, and in response to the instruction, merging of the delta structure in the volatile memory with the first instantiation of the columnar table in the volatile memory to create a merged columnar table in the volatile memory, and not storing the merged columnar table in the persisted memory.

Abstract: Provided are a computer program product, system, and method for recovering a volume table and data sets from a volume. Content from a backup volume table comprising a valid backup of a volume table from backup of the volume is processed to generate a recovery volume table for a recovery volume. The data sets in the volume are processed to determine whether they are valid. The valid data sets are moved to the recovery volume. A data recovery operation is initiated for the data sets determined not to be valid.

Abstract: In one embodiment, a data storage system includes a server system that includes a processor and a local buffer pool configured to store instances for use in catalog requests, and a direct access storage device (DASD) subsystem electrically coupled to the server system and to at least one DASD, where the at least one DASD includes an integrated catalog facility (ICF) configured to provide at least one catalog, and where the data storage system is configured to provide record level sharing (RLS) for the at least one catalog stored to the at least one DASD.

Abstract: Steady state data distribution is provided between a client application, a leader machine, and a plurality of replica machines. The distribution comprises the leader machine receiving an operation request from the client application, the leader machine sending the prepare message to each of the plurality of replica machines, the replica machines recording in their logs information on the operation, the replica machines sending acknowledgement messages to the leader machine, and the leader machine sending commit command messages to the replica machines. A new quorum of the replica machines is created by using log information. Replica machines that become part of the new quorum are updated in an efficient manner.

Abstract: A processing device detects a file system call that is associated with copying data to a destination file. The processing device identifies an application initiating the copying of the data to the destination file and determines one or more files that are opened by the application. The processing device identifies a source file from the one or more files opened by the application. The source file corresponds to the destination file. The processing device determines whether the source file includes data to be protected and allows or denies the copying of the data to the destination file based on whether the source file includes data to be protected.

Abstract: Utilizing an incremental backup in a decremental backup system. In one example embodiment, a method for utilizing an incremental backup in a decremental backup system includes creating a base backup that includes all original allocated blocks in a source storage at a first point in time. Next, an incremental backup is created that includes allocated blocks in the source storage that were newly allocated or were changed between the first point in time and a second point in time. The changed allocated blocks in the incremental backup are identified. During a third time period, a decremental backup is created and the incremental backup is ingested into the base backup by copying, into the decremental backup, original allocated blocks from the base backup that correspond to the changed allocated blocks in the incremental backup. Lastly, the newly-allocated blocks and the changed allocated blocks from the incremental backup are added to the base backup.

Abstract: Techniques are disclosed for facilitating the process of undoing and redoing modifications that are made to content using an online content management system (CMS). As a user makes changes to content, such as by editing a webpage using a web-based CMS, a history of the user's modifications is generated and stored locally on the client. When the user invokes an undo command, the modification history can be used to determine a previous state of the content and restore the content to that previous state. Similarly, when the user invokes a redo command, the modification history can be used to return to a state that had previously been undone. In some embodiments, the process of undoing or redoing the user's modifications is selectively performed on either a client side or a server side of the online system, depending on the type of content that is being manipulated.

Abstract: A restoration apparatus restores backup data without running an operating system (OS) until a time point until which the total amount of the data read out along with the start-up of the OS and a business system remains equal to or smaller than the total amount of the data that is restorable while running the OS and the business system, and subsequently restores the backup data in parallel with the start-up of the OS and the business system.

Abstract: A mechanism is provided for generating enumerated information in which a plurality of files is enumerated except entirely-invalidated files on a sequential medium. Management information for managing locations where the plurality of files on the sequential medium are recorded is acquired from the sequential medium. The enumerated information in which the plurality of files are enumerated is generated in an order according to the locations where the plurality of files are recorded on the basis of the acquired management information.

Abstract: According to one embodiment of the present invention, a system reduces re-reading of database logs by persisting long running transaction data. The system processes the database log records of the database transaction log; generates a snapshot of the database log records at periodic intervals, wherein each snapshot includes database log records for pending transactions; and in response to an interruption in processing of the database log records, utilizes a snapshot to restore database log records for the pending transactions and resume processing of the database transaction log from a position succeeding the database log records of the selected snapshot.

Abstract: A disaster recovery system, including a target datastore for replicating data written to source datastores, and a checkpoint engine (i) for transmitting, at multiple times, quiesce commands to a plurality of host computers, each quiesce command including a timeout period that is adjusted at each of the multiple times, (ii) for determining, at each of the multiple times, whether acknowledgements indicating that a host has successfully stopped writing enterprise data to the source datastores, have been received from each of the host computers within the timeout period, (iii) for marking, at each of the multiple times, a cross-host checkpoint in the target datastore and reducing the timeout period for the quiesce commands at the next time, if the determining is affirmative, and (iv) for increasing, at each of the multiple times, the timeout period for the quiesce commands transmitted at the next time, if the determining is not affirmative.

Abstract: Systems and methods for performing hierarchical storage operations on electronic data in a computer network are provided. In one embodiment, the present invention may store electronic data from a network device to a network attached storage (NAS) device pursuant to certain storage criteria. The data stored on the NAS may be migrated to a secondary storage and a stub file having a pointer pointing to the secondary storage may be put at the location the data was previously stored on the NAS. The stub file may redirect the network device to the secondary storage if a read request for the data is received from the network device.

Abstract: An approach to providing auto recovery of data sets in volumes. When an error condition results from an attempt to access an unintentionally deleted data set, an event is generated and sent to other systems with access to the volume in which the data set existed. The volume is also locked to prevent corruption during the recovery process. A system that has the unintentionally deleted data set open retrieves location information for the data set from control blocks in the system's memory. This location information is used to build a new entry for the data set in the VTOC for the volume. When the data set is thus recovered, the data set is validated, the lock removed, and the data set is made available to the systems sharing the volume.

Abstract: A system and method for automated database management are provided. Statistics relating to operation of a database may be collected, wherein the database comprises one or more database objects. Characteristics of the database objects may be determined, either automatically or by user intervention, using the collected statistics, one or more policies, and/or one or more definitions. The policies and definitions may be defaults or may be customized by a user. Actions to be performed on the database objects may be determined, either automatically or by user intervention, based on the characteristics of the database objects. A schedule for performing the actions on the database objects may be automatically determined. The actions may be performed on the database objects based on the schedule.

Abstract: A logging system includes an event receiver and a storage manager. The receiver receives log data, processes it, and outputs a data “chunk.” The manager receives data chunks and stores them so that they can be queried. The receiver includes buffers that store events and a metadata structure that stores metadata about the contents of the buffers. The metadata includes a unique identifier associated with the receiver, the number of events in the buffers, and, for each “field of interest,” a minimum value and a maximum value that reflect the range of values of that field over all of the events in the buffers. A chunk includes the metadata structure and a compressed version of the contents of the buffers. The metadata structure acts as a search index when querying event data. The logging system can be used in conjunction with a security information/event management (SIEM) system.

Abstract: According to one embodiment, recovering file systems by restoring partitions is described. In one example, a method includes discovering an error in a storage partition of a file storage system, the storage partition including identification metadata to identify itself to the file system, finding a backup storage partition containing data and identification metadata corresponding to that of the error storage partition, restoring the error storage partition using the backup storage partition, and using the restored identification metadata to identify the restored storage partition to the file system.