Example implementations disclosed herein can be used to build, maintain, and use a hash table distributed across the plurality multiple nodes in a multi-node computing system. The hash table can include data pages associated by corresponding pointers according to a tree data structure. The data pages include leaf data pages. Each leaf data page can be associated with a corresponding hash value and include a tag bitmap. When a transaction associated with a key is executed, a hash value and a tag value are generated based on the key. The leaf data pages can be searched using the hash value. A probability that a leaf data page includes the key can be determined based on a comparison tag value with the tag bitmap.

Described are methods, systems and computer readable media for data source refreshing.

An illustrative method for storing disaster recovery data includes receiving a plurality of copies of data stored by a first memory device. Each of the plurality of copies includes a plurality of blocks of data. The method also includes storing, in a second memory device, the plurality of copies in an object-oriented format, determining, using recovery time objectives, a number of the plurality of copies to be stored in a block-oriented format, and selecting a subset of the plurality of copies having the determined number of the plurality of copies. The method further includes assigning each of the other copies of the plurality of copies to one of a plurality of clusters. Each cluster of the plurality of clusters includes one of the subset of the plurality of copies. The method also includes determining, for each cluster, a copy having a highest number of blocks also present in the other copies of the cluster and storing, in the block-oriented format, the determined copy from each cluster in a third memory device.

A system includes reception of a first query at a first host, determination, at the first host, that the first query is associated with a first table, the first table including geographically-restricted data and a partitioning column storing identifiers of geographic restrictions, determination, at the first host and based on the partitioning column of the first table and on the first query, a first partition of the first table and a storage location of the first partition, and execution of the first query at the first host in conjunction with the storage location of the first partition.

Certain embodiments described herein relate to an improved block-level replication system. One or more components in an information management system may receive a request to perform a block-level replication between a source storage device and a destination storage device, and depending on the specific replication mode requested, (i) store block-level changes directly to the destination storage device or (ii) first to a recovery point store and then later to the destination storage device.

One example method includes chunking a respective disk of each of a plurality of virtual machines (VM) to create a respective plurality of chunks associated with each of the VMs, creating, based on the chunking process, a cluster comprising one or more of the VMs, creating a VM template whose data and disk structure match respective data and disk structures of each of the VMs in the cluster, and in response to a file operation involving a first one of the VM disks, defragmenting the first VM disk so that a disk structure of the first VM disk is the same as a disk structure of the VM template.

A data backup method of a storage device which includes a storage controller, a buffer memory, and a plurality of nonvolatile memory devices, the method including: detecting a power-off event of an external power provided to the storage device; deactivating a host interface of the storage controller in response to the detection of the power-off event: moving data stored in the buffer memory to a static random access memory (SRAM) in the storage controller; blocking or deactivating a power of the buffer memory; setting an interleaving mode of the plurality of nonvolatile memory devices to a minimum power mode; and programming the data moved to the SRAM to at least one of the plurality of nonvolatile memory devices.

A storage manager for an information management system determines whether one or more predetermined conditions have been met for transferring metadata of previously performed backup jobs stored in a first management database. A backup job may correspond to a backup operation of a primary storage device of a first client computing device. In response to a determination that one or more of the predetermined conditions have been met, the storage manager may transfer metadata for a second plurality of backup jobs to a second management database of a recovery manager. The recovery manager may receive a request to restore data to the primary storage device of the first client computing device based on the metadata of the second plurality of backup jobs. A media agent managed by the recovery manager may then restore the requested data to the primary storage device of the first client computing device.

A secure element device that is configured to be cryptographically bound to a host device includes a secure element host key slot configured to store host key information that allows only the host device to control the secure element, a secure memory storing binding information, and limited functionality allowing the binding information to be read from the secure memory by the host device during a binding process. The binding information is cryptographically correlated with the host key information. The host key information is generated by the host device using the binding information read from the secure element and a secret key. The secure element device further includes general functionality only accessible to the host device using the host key information that is generated by the host device. The secure memory includes prevention measures impeding unauthorized entities from obtaining information from the secure memory.

An information management system implements a method for determining whether to initiate a failover of a storage manager in the system. Nodes in the system may be assigned as monitoring nodes configured to communicate with a storage manager. Furthermore, each monitoring node may be configured to transmit a status inquiry message to each other monitoring node, and each monitoring node may receive a status inquiry message from each other monitoring node. Each monitoring node may also generate a session message comprising status information, and a plurality of failover nodes may receive the generated session messages. A failover node may then determine whether a failover condition has occurred by applying a plurality of failover rules to the status information of the transmitted session message. Where the failover node determines that a failover condition has occurred, the failover node may activate another storage manager to take place of the presently assigned storage manager.