Abstract: An illustrative approach accelerates live browse operations for block-level backup copies in a data storage management system. A cache storage area is maintained for locally storing and serving key data blocks, thus relying less on retrieving data on demand from backup copies. Live browse operations are used for populating the cache storage area for speedier retrieval during subsequent live browsing and/or file indexing of the same backup copy, and vice versa. The key data blocks cached while file indexing and/or live browsing an earlier backup copy help to pre-fetch corresponding data blocks of later backup copies, thus producing a beneficial learning cycle. The approach is especially beneficial for cloud and tape backup media, and is available for a variety of data sources and backup copies, including block-level backup copies of virtual machines (VMs) and block-level backup copies of file systems, including UNIX-based and Windows-based operating systems and corresponding file systems.

Abstract: Automatically managing database applications, including identifying, by a management extension, an SQL server host connected to a storage system, wherein the SQL server host comprises an SQL server managing an SQL database supported by the storage system; identifying, by the management extension, the SQL database supported by the storage system based on the identified SQL server host; and scheduling, by the management extension, a backup of the SQL database.

Abstract: In some embodiments, a method is provided that includes (1) prompting a user to identify news content to be filtered; (2) generating filter rules based on the content to be filtered identified by the user; (3) populating a rules database based on the filter rules; (4) retrieving news content from a news server over the internet; (5) filtering the news content based on the filter rules within the rules database; and (6) providing the filtered news content to the user on a mobile device of the user. Numerous other embodiments are provided.

Abstract: A method for performing hash code calculations may include calculating, during a write operation for a data block, a hash code for an occupied portion of the data block, inserting, during the write operation, a marker into the data block, calculating, during a read operation for the data block, a hash code for the occupied portion of the data block, searching, during the read operation, for the marker in the data block, and terminating the hash code calculation in response to finding the marker. A system may include a first interface configured to receive data blocks, a second interface configured to transmit data blocks, and hash logic coupled between the first and second interfaces, wherein the hash logic is configured to calculate a hash code for the occupied portion of a data block received through the first interface, and insert a marker in an unoccupied portion of the data block.

Abstract: A system for analyzing screenshots can include a computing device including a processor coupled to a memory and a display screen configured to display content. The system can include an application stored on the memory and executable by the processor. The application can include a screenshot receiver configured to access, from storage to which a screenshot of the content displayed on the display screen captured using a screenshot function of the computing device is stored, the screenshot including an image and a predetermined marker. The application can include a marker detector configured to detect the predetermined marker included in the screenshot. The application can include a link identifier configured to identify, using the predetermined marker, a link to a resource mapped to the image included in the screenshot, the resource accessible by the computing device via the link.

Abstract: An apparatus includes a processing device configured to identify a snapshot policy for creating a snapshot lineage comprising snapshots of a storage volume comprising data stored on a storage system, the snapshot lineage comprising (i) a local snapshot lineage stored on the storage system and (ii) at least one cloud snapshot lineage stored on cloud storage. The processing device is also configured to generate snapshots of the storage volume in accordance with the snapshot policy, to store the snapshots in the local snapshot lineage, and to copy snapshots from the local snapshot lineage to the at least one cloud snapshot lineage in accordance with the at least one snapshot policy. The processing device is further configured to provide an interface for managing the snapshot lineage by accessing, from the storage system, snapshots of the storage volume in the local snapshot lineage and the at least one cloud snapshot lineage.

Abstract: A system for providing backup services for limited-access user data includes persistent storage for storing a user data visualization enhanced user data backup and a manager. The manager identifies a backup generation event for limited-access user data based on a protection policy; in response to identifying the backup generation event, obtains fragmented user data from an application that gates access to the limited-access user data; obtains organizational metadata associated with the fragmented user data from the application; makes a determination that the fragmented user data is associated with a user data visualization; in response to making the determination, obtains user data visualization metadata associated with the fragmented user data from the application; and generates the user data enhanced user data backup using the organizational metadata, the user data visualization metadata, and the fragmented user data.

Abstract: Techniques are provided for utilizing snapshot longevity information to manage snapshots in a snapshot-enabled storage system. A snapshot management system generates a snapshot volume tree which comprises snapshots associated with a given storage volume. The snapshot management system obtains a snapshot policy associated with the given storage volume, which comprises a snapshot creation and retention schedule that specifies retention lifespans of the snapshots. The snapshot policy is evaluated to automatically determine and assign respective longevity ranking values for the snapshots within the snapshot volume tree, wherein the longevity ranking value of a given snapshot represents a retention lifespan of the given snapshot as compared to retention lifespans of other snapshots as represented by their respective longevity ranking values.

Abstract: A backup manager for providing backup services includes persistent storage and a backup orchestrator. The persistent storage includes protection policies. The backup orchestrator identifies a last backup generation time for a client in response to a protection policy of the protection policies triggering a backup generation for the client; obtains system metadata for the client; identifies a portion of client data that has been modified since the last backup generation time using the system metadata; generates an incremental backup based on the identified portion of the client data; and stores the incremental backup in backup storage.

Abstract: A method, a device and a computer program product for managing data backup are provided. The method comprises: obtaining a first set of performance parameters of a backup client prior to performing a data backup, the backup client being configured to transmit data to a backup server for backup and record information about the data in a cache to avoid duplicate data being transmitted to the backup server; determining, from a plurality of sets of historical performance parameters collected during multiple historical data backups performed by the backup client, at least one set of historical performance parameters similar to the first set of performance parameters; determining, from the at least one set of historical performance parameters, a set of historical performance parameters indicating the best performance; and adjusting, based on the set of historical performance parameters, an available capacity of the cache to be used in the data backup.

Abstract: By obtaining metadata for transactions submitted by a service to a log-first distributed database of a provider network, a metrics manager may determine database replica performance for those transactions and notify clients of potential performance issues. When an instance of the service submits a write transaction to the log-first distributed database, the transaction may include a host name and a timestamp for the submission of the transaction. At a later point in time, a write applier may obtain the transaction and apply it to a local database replica, along with an additional timestamp for the application of the transaction to the replica. A metrics manager may obtain the transaction timestamps from the replica and calculate a latency metric for the propagation of the transaction from the particular service instance/instance host to the replica. The latency metric may be stored or transmitted to an endpoint (e.g., a client or administrator).

Abstract: A database management system stores an entry in a journal. The journal, upon storage of the entry, comprises an ordered plurality of leaf nodes and a hierarchy of interior nodes based upon the leaf nodes. A node in the ordered plurality of nodes comprises a hash value computed based on the hash of a corresponding entry and a hash of a prior leaf node. A cryptographic proof of the entry comprises successive application of a hash operator to one or more hashes of the leaf nodes.

Abstract: Cascading payload replication to target compute nodes is disclosed. Cascading payload replication can be accomplished using a two-stage operation for a replication operation. In the first stage, a plan is generated and distributed for the replication operation. The plan includes an assignment of compute nodes to tree nodes in a tree hierarchy. In the second phase, the payload is distributed according to the plan. The plan is different for at least two replication operations. Thus, the cascading payload replication is adaptable to changing target compute nodes and provides for load balancing.

Abstract: A system, method and apparatus in which a client computer initiates and communicates a distributed ledger transaction either to an individual node in a network of distributed ledger nodes or to the network itself, which transaction is labeled with a nanosecond scale timestamp, encrypted using quantum event generated random binary data and then securely transmitted to other ledger nodes in the network at substantially the same time. Networks may consist of traditional wireline and wireless networks, cloud networks and 5G wireless networks in any combination and configuration. Using the invention, distributed ledger networks may take the forms of blockchains, transactionally integrated multiple distributed ledgers, decentralized exchanges, or immutable distributed databases. After the transaction is transmitted, additional messages necessary to the completion of the transaction are communicated between ledger nodes in the network using the same or similar system, method and apparatus.

Abstract: A method and a system for interfacing a database system with a consensus system are provided. The method comprises at least the steps of creating a shadow table of a table of the database system; and for each row of the shadow table: serialization of data, stored in a current row of the shadow table; generating a data item verification fingerprint of the data; and providing the data item verification fingerprint to the consensus system.

Abstract: Systems and methods are described for providing contextual search results. The system may receive a search query during presentation of a video. If the query is ambiguous, the system accesses some of the frames of the video. The frames are analyzed to identify a performed action depicted in the frames. The system retrieves a keyword related to the identified action. The ambiguous query is augmented with the keyword. The augmented search query is used to search for and output relevant search results.

Abstract: A backup manager for providing backup services includes storage and a backup orchestrator. The persistent storage stores prediction models. The backup orchestrator obtains a computing resource availability for a client; generates a prediction model of the prediction models using the computing resource availability for the client; predicts, using the prediction model and live data, a future computing resource availability for the client; and initiates generation of a backup for the client at an unscheduled time that is based, at least in part, on the future computing resource availability.

Abstract: Mechanisms for multidimensional data modeling and operations and related procedures are described. Resource structures for multidimensional data can be used. This can allow lumped operations such as RESTful operations and procedures on the multidimensional data. A new attribute “SamplingPeriodCovered” can be used to indicate the time interval when the related time series data (or any multi-dimension data streams) are stored. This can reduce the total size of the data stored.

Abstract: In one embodiment, an attribute application associates content with a road segment. In operation, the attribute application generates a spatial reference identifier based on coordinates associated with the attribute. The attribute application then generates an attribute based on the content and the spatial reference identifier. Finally, the attribute application transmits the road segment attribute to a navigation system that performs at least one navigation operation based on a road database and the attribute. Because the attribute is specified based on spatial referencing, the attribute application requires fewer resources to generate attributes than conventional approaches that generate different attributes for different versions and formats of road databases.

Abstract: A computer system and a fault tolerance processing method thereof of image file are provided. In the method, whether to segment the image file is determined. The image file is segmented into multiple image segmented files sequentially, and a segmenting process is recorded in response to determining to segment the image file. The segmenting process relates to a number of a last segmented file. Each time the image file is segmented once, the number of the last segmented file is accumulated. Segmenting the image file is continued according to the segmenting process in response to a segmenting exception situation. On the other hand, the deployment for the image file is performed in conjunction with a record of the current progress during the deployment, so that the deployment also can be continued in response to an interruption of the deployment. Accordingly, efficiency and successful rate can be improved.