2112 results about "Storage pool" patented technology

A RAID system employs a storage controller, a primary storage array having a plurality of primary storage units, and a spare storage pool having one or more spare storage units. A method of operating the storage controller in managing the primary storage array and the spare storage pool involves a testing by the storage controller of at least one repair service threshold representative of one or more operational conditions indicative of a necessity to repair at least one of the primary storage array and the spare storage unit, and a selective initiation by the storage controller of a repair service action for repairing one of the primary storage array and the spare storage unit based on the testing of the at least one repair service threshold.

An apparatus for managing incremental storage includes a storage pool management module that allocates storage volumes to a virtual volume. Also included is an incremental log corresponding to the virtual volume, which maps virtual addresses to storage addresses. The apparatus may also include a replication module that sends replicated data to the virtual volume and a policy management module that determines allocation criteria for the storage pool management module. In one embodiment, the incremental log includes a lookup table that translates read and write requests to physical addresses on storage volumes within the virtual volume. The replicated data may include incremental snapshot data corresponding to one or more primary volumes. The various embodiments of the virtual incremental storage apparatus, method, and system facilitate dynamic adjustment of the storage capacity of the virtual volume to accommodate changing amounts of storage utilization.

Provided are a method, system, and program for managing data in storage units. Storage pool information indicates an assignment of a plurality of storage units to a plurality of storage pools, wherein each pool is assigned zero or more storage units, wherein data associated with one storage pool is stored in a storage unit assigned to the storage pool, wherein the storage pool information for each pool indicates a threshold and target storage pool, and wherein the target storage pool is capable of being different from the storage pool. One storage unit associated with a source storage pool is selected and a determination is made of the threshold from the storage pool information for the source storage pool. A determination is made of whether the selected storage unit satisfies the determined threshold and if the selected storage unit satisfies the determined threshold, then a target storage unit in the target storage pool is selected if the storage pool information for the source storage pool indicates a target storage pool different from the source storage pool. Data from the selected storage unit is copied to the selected target storage unit.

A virtual file system is described that is implemented in a virtualization platform as a stackable file system layer that intercepts file operations between a hypervisor and a physical file system. The virtual file system encrypts (at least in part) VM files to be stored, organizes the encrypted VM files into VM sets, and then maps and stores the encrypted VM sets into storage pools. Storage and access to files within the VM sets is controlled through the use of administrator-determined policies governing storage, security, access control, authentication, and auditing. The system and method described herein allow a seamless integration between a data center (e.g., a private cloud) and computing resources served across the internet and supported by cloud service providers (e.g., public clouds) while ensuring that the security needs of customers and cloud service providers are met.

A system for efficient backups using dynamically shared storage pools in peer-to-peer networks comprises one or more processors and memory coupled to the processors. The memory stores instructions executable by the processors to implement a backup manager configured to dynamically subdivide a storage pool into one or more portions of storage currently designated for local backup data and one or more portions of storage currently designated for peer-to-peer (P2P) backup data. In response to local backup data received from a backup client, the backup manager may store the local backup data in a portion of the storage pool that is currently designated for local backup data. The backup manager may then generate a P2P version of the local backup data, e.g., by encrypting and/or redundancy encoding the local backup data, and transmit parts of the P2P version to each of one or more peer devices in the P2P network.

The invention discloses a smart contract protection system based on a trusted environment, including a client, block chain nodes, a data provider, a trusted environment, a non-trusted environment, a smart contract information processing module (A), a block chain node information transmission module (B) (such as a node interaction interface in the Ethereum), an input data transmission module (C), a smart contract execution module (D), a local contract information storage pool (E) and a block chain smart contract storage pool (F). The client is in communication connection with the block chain nodes. The data provider is in communication connection with the block chain nodes. The block chain nodes are in communication connection with one another. The technical problem that the copyright of smart contracts cannot be protected and the rights and interests of smart contract users are damaged due to the fact that the information of smart contracts may easily leak in the existing smart contract system and the technical problem that data may be stolen due to data leakage are solved.

A map-reduce compatible distributed file system that consists of successive component layers that each provide the basis on which the next layer is built provides transactional read-write-update semantics with file chunk replication and huge file-create rates. A primitive storage layer (storage pools) knits together raw block stores and provides a storage mechanism for containers and transaction logs. Storage pools are manipulated by individual file servers. Containers provide the fundamental basis for data replication, relocation, and transactional updates. A container location database allows containers to be found among all file servers, as well as defining precedence among replicas of containers to organize transactional updates of container contents. Volumes facilitate control of data placement, creation of snapshots and mirrors, and retention of a variety of control and policy information. Key-value stores relate keys to data for such purposes as directories, container location maps, and offset maps in compressed files.

A method for performing a backup of a stub object located on a file system managed by a hierarchical storage manager configured to migrate data objects from the file system to a migration storage pool is provided. The stub object includes information for recalling a migrated data object. The method comprises determining whether a backup copy of the migrated data object is stored in a backup storage pool if the backup is performed in an incremental backup operation; directing the hierarchical storage manager to recall the migrated data object to the file system if the backup copy of the migrated data object is not stored in the backup storage pool or if the backup is performed in a selective backup operation; creating the backup copy of the migrated data object if the migrated data object is recalled; storing the backup copy of the migrated data object in the backup storage pool if the migrated data object is recalled; creating a backup copy of the stub object if the migrated data object is not recalled; storing the backup copy of the stub object from the file system in the backup storage pool if the migrated data object is not recalled; and logically grouping the backup copy of the migrated data object with the backup copy of the stub object in the backup storage pool such that the backup copy of the migrated data object cannot be deleted from the backup storage pool unless the backup copy of the stub object does not exist in the backup storage pool if the migrated data object is not recalled.

One aspect of the present invention includes enabling the efficient transfer of deduplicated data between storage pools in a storage management system without unnecessary reassembly and deduplication of data objects. In one embodiment, the storage management system tracks deduplication information for the data chunks of data objects within an index at the storage management system level, in addition to tracking storage information for each data object within another index at the storage management system level. The data chunk deduplication information is then accessible by any storage pool. Accordingly, transfers of the data objects and data chunks of the data object are easily facilitated, even between non-deduplicating and deduplicating storage pools.

A technique for implementing policy-aware backup and restore capability in a tiered storage system. If a data set's contents are backed up from the tiered storage system to a backup storage system, metadata for the data set may also be backed up. Prior to the data set being restored from the backup storage system to the tiered storage system, the backed up metadata is restored and processed to determine a tier among the tiered storage pools to which the data set will be restored.

A storage system which comprise includes a disk controller and a disk device having original volumes for backup and a storage pool for backup data. It incorporates a differential management program which checks whether the original volumes for backup are updated or not; a pool management program which allocates a disk area to the storage pool for backup data; a performance management program which manages the performance of each volume; and a backup control program which performs total backup control. A backup method by which recovery within a user-specified recovery object time is possible is selected according to the restore performance calculated by the performance management program and the total size of changed blocks after backup acquisition as counted by the differential management program.

One aspect of the present invention includes enabling data chunks to be shared among different storage pools within a storage management system, according the use of deduplication and storage information kept at the system level, and applied with policy-based rules that define the scope of deduplication. In one embodiment, the parameters of performing deduplication are defined within the policy, particularly which of the plurality of storage pools allow deduplication to which other pools. Accordingly, a data object may be linked to deduplicated data chunks existent within other storage pools, and the transfer of a data object may occur by simply creating references to existing data chunks in other pools provided the policy allows the pool to reference chunks in these other pools. Additionally, a group of storage pools may be defined within the policy to perform a common set of deduplication activities across all pools within the group.

A storage virtualization system that follows a four-layer hierarchy model, which facilitates the ability to create storage policies to automate complex storage management issues, is provided. The four-layers are a disk pool, Redundant Arrays of Independent Disks (RAID arrays), storage pools and a virtual pool of Virtual Disks (Vdisks). The storage virtualization system creates virtual storage arrays from the RAID arrays and assigns these arrays to storage pools in which all of the arrays have identical RAID levels and underlying chunk sizes representing in abstraction very large arrays. Virtual disks are then created from these pools wherein the abstraction of a storage pool makes it possible to create storage policies for the automatic expansion of virtual disks as they fill with user files.

A storage system stores objects and copies of objects on the storage system and other storage systems external to the storage system. The storage system stores the copies in storage pools of volumes, which are organized into one or more tiers. The configuration settings of each tier and each pool within the tier may be configured according to a user's preferences. In one example, the number of copies of data content and the number copies of metadata associated with the data content an individual pool stores may be specified. When objects are migrated between tiers, the objects are stored among the storage pools of the tiers. If the number of data content copies or metadata copies is increased, the data or metadata is copied from a determined copy source and if the number of copies decreases, the data is removed from the volumes in the pools.

One aspect of the present invention includes an optimized simultaneous storage operation for data objects onto a combination of deduplicated and non-deduplicated storage pools. In one embodiment, a data object is provided for storage onto destination storage pools in a storage management system, and placed into a source buffer. The data object is first divided into data chunks if the data object has not previously been chunked within the storage management system. The data object is then simultaneously copied from the source buffer to each destination storage pool (deduplicating and non-deduplicating) with the following operation. If the destination pool utilizes deduplication, then the individual data chunks are only transferred if copies of the individual data chunks do not already exist on the destination storage pool. If the destination pool does not utilize deduplication, then all chunks of the data object are transferred to the destination storage pool.

The storage of single or multiple references of the same data block in a storage pool is disclosed. Indexing of the data includes storing reference information in the storage pool as a mapping table. The mapping table indexes each data block in the storage pool. On any read or write request mapping information is used to retrieve the corresponding data block in storage pool.

An administrator provisions a virtual disk in a remote storage platform and defines policies for that virtual disk. A virtual machine writes to and reads from the storage platform using any storage protocol. Virtual disk data within a failed storage pool is migrated to different storage pools while still respecting the policies of each virtual disk. Snapshot and revert commands are given for a virtual disk at a particular point in time and overhead is minimal. A virtual disk is cloned utilizing snapshot information and no data need be copied. Any number of Zookeeper clusters are executing in a coordinated fashion within the storage platform, thus increasing overall throughput. A timestamp is generated that guarantees a monotonically increasing counter, even upon a crash of a virtual machine. Any virtual disk has a “hybrid cloud aware” policy in which one replica of the virtual disk is stored in a public cloud.

A method is used in managing data in a data storage system. A tiered storage pool is identified wherein the storage pool includes multiple tiers having multiple storage units. A wear indicator for each of the multiple storage units is monitored. A first storage unit having a wear indicator greater than a second storage unit is identified. High activity data on the first storage unit is also identified. The identified high activity data is migrated from the first storage unit to the second storage unit.