Abstract: Example implementations described herein are directed to systems and methods for facilitating remote copy pair volume with data consistency. For a command received for one of a first volume and a second volume during execution of a pair synchronization process between the first volume and the second volume, example implementations can involve determining whether an address range of one of the first volume and the second volume configured to be provided to a host computer is to be locked based on the command; locking the address range of the one of the first volume and the second volume for the determination indicative of the address range of one of the first volume and the second volume is to be locked; and executing the command on the first volume and the second volume while the address range configured to be provided to the host computer is locked.

Abstract: Example implementation described herein are directed to a mechanism to provision data volume which requires remote data copy between separated clusters, especially for the container platform. For a request to create a volume made to the clusters, example implementations can involve creating a first volume in a first cluster; obtaining volume information of a corresponding second volume from a second cluster; configuring the first volume and the corresponding second volume in the second cluster to have a remote copy relationship based on the obtained volume information; and setting access from the container to the first volume and the corresponding second volume based on the remote copy relationship.

Abstract: Example implementations described herein facilitate a drive unit to share physical mediums (e.g. solid state drives) among multiple storage controllers or storage nodes in a distributed storage system, while keeping them physically independent in a redundancy group to avoid single point of failure, by providing an interface to notify redundancy group to the drive unit.

Abstract: A storage system is connected to a backup storage system over a Storage Area Network (SAN). The backup storage system is managed by a backup server. The storage system includes a primary volume, a secondary volume configured to be mounted to a backup volume in the backup storage system and configured to be paired with the primary volume, and a processor configured to, for receipt of a backup operation request from the backup server, copy the primary volume to the secondary volume through a pair operation based on an Input/Output (I/O) between the storage system and a host computer managing the storage system, mount the secondary volume to the backup volume, and based on the I/O, copy the secondary volume to the backup volume through the SAN.

Abstract: A storage-based migration is performed in a VVOL environment. A migration processing unit generates a migration group in which a virtual volume to be migrated, a protocol endpoint related to the virtual volume, and a storage container that cuts out the virtual volume are grouped, and migrates the migration group to a storage node; and a configuration changing unit configures, based on information of the migration group transmitted from the storage node, a protocol endpoint, a virtual volume, and a storage container on a storage node which are the same as the protocol endpoint, the virtual volume, and the storage container configured on the storage node.

Abstract: Example implementations described herein are directed to backup and restore of a public cloud and data center for disaster recovery. In a backup process of the disaster recovery, the VM root device information (a public cloud) and storage system volume information (a data center) in a main site are transferred to the disaster recovery tool. In a restoration process, the DR Tool specifies the storage system volume for backup to attach the VM in a backup site with the above information.

Abstract: A storage system and storage control method are provided in which a plurality of volumes to be processed by a storage control unit are distributed and evacuated in a normal storage control unit without recovering redundancy of the storage control unit having decreased redundancy, and the storage control unit itself having the decreased redundancy is deleted after the evacuating is completed, and thus reservation information processing resources for guaranteeing recoverability of the redundancy become unnecessary.

Abstract: Example implementations described herein are directed to automated failover and assuring RTO (Recovery Time Objective) assurance, and RPO (Recovery Point Objective) on asynchronous remote copy feature of storage. By using markers that are cyclically stored to the journal volume, the storage device can thereby determine an accurate communication loss period.

Abstract: With omission of a duplication process of compressed data, a cache access frequency is reduced to improve throughput. A storage system includes first and second control units and a storage drive. Upon receiving a data write command, the first control unit stores data to be subjected to the write command in a first cache area of the first control unit, and stores the data in a second cache area of the second control unit to perform duplication, and upon completion of the duplication, the first control unit transmits a response indicating an end of write, performs a predetermined process on the data to be subjected to the write command, stores the data in a buffer area, reads the data stored in the buffer area, and transmits the read data to the storage drive.

Abstract: Saving a capacity of an on-premises storage apparatus, a high access performance of the on-premises storage apparatus, and resuming an operation quickly and accurately by using data on a cloud when a resource in the on-premises fails are achieved. A processor provides a first volume which is a virtual volume, and configures a copy pair of the first volume and a second volume provided from another storage system. Write data to the first volume is transferred to the second volume via a network, based on the copy pair. The processor writes to the memory a part of data written to the second volume, and writes to the storage device the data written to the memory.

Abstract: In a storage system having a controller constructing a provision volume provided to a server system and an addition volume in which data to be stored in the provision volume is added and stored, when a provision volume copying instruction is received, the controller inserts a start marker indicating start time point of copying into address change history information and copies address conversion information of a provision volume while receiving update data to a provision volume from the server system, as address conversion information of a copy-destination volume. On the basis of a start marker of address change history information and history information, a change from start to completion of copying of the address conversion information of a copy-destination volume is reset to a state at the start time point of copying.

Abstract: The accuracy of predicting the remaining life of a non-volatile memory in which WA occurs is enhanced. A storage controller predicts the remaining lives of SSDs on the basis of the data storage rates of the respective SSDs. When the storage controller determines that a life expectation result on one SSD does not satisfy a target operation period while a life expectation result on another SSD satisfies the target operation period, the storage controller executes extent migration processing of migrating data in any data stored extent to an extent in which data has not been stored, thereby decreasing the data storage rate of the one SSD to extend the life of the one SSD.

Abstract: A storage system includes a storage controller, plural volumes each configured by the storage controller, and a pool allocating physical storage areas to logical storage areas of the volumes. The storage controller configures a first group including, among the volumes, a first primary volume to which a first target protection period is set, and a first history information volume storing history information about updating to the first primary volume, and a second group including, thereamong, a second primary volume to which a second target protection period is set, and a second history information volume storing history information about updating to the second primary volume. The volumes included in the first and second groups utilize the same physical storage area of the pool. When increasing a free capacity thereof, history information to be purged is determined from the first and second protectable periods such that their protectable periods become the same.

Abstract: Example implementations described herein involve providing an interface configured to receive input to generate a project request for a project; determining an allocation of resources for the project for execution; determining a schedule for the project based on the project request based on the allocation of resources; for the first service platform being available to allocate the resources to execute the project according to the schedule, allocating the resources for executing the project on the first service platform according to the schedule; for the first service platform being unavailable to execute the project according to the schedule, determining whether a second service platform is available to allocate the resources to execute the project according to the schedule, and for the second service platform being available to execute the project according to the schedule, allocating the resources for executing the project on the second service platform according to the schedule.

Abstract: In a storage system, attributes of nodes are specified as first attribute nodes and second attribute nodes, the I/O processing in the nodes is executed as a plurality of processes including front-end I/O processing executed by any of the first attribute nodes and back-end I/O processing executed by the first and second attribute nodes having a storage device that stores data relating to the I/O processing.

Abstract: Example implementations described herein facilitate a drive unit to share physical mediums (e.g. solid state drives) among multiple storage controllers or storage nodes in a distributed storage system, while keeping them physically independent in a redundancy group to avoid single point of failure, by providing an interface to notify redundancy group to the drive unit.

Abstract: An object of the present invention is to provide a redundant information processing system that can continue its operation without stopping as much as possible. To achieve this, the information processing system includes multiple storage nodes including processors, memories, and storage devices, as well as a network for connecting the storage nodes. The processor of at least one storage node performs the steps of: obtaining the configuration information of the information processing system; obtaining first failure information related to a first failure occurred in the information processing system; calculating the availability level of the information processing system when a second failure further occurs, based on the configuration information and the first failure information; and controlling the operation of the system based on the availability level. Then, the processor outputs a notification.

Abstract: Example implementations are directed to a local area network (LAN)-free and application-consistent backup with data copy offload from backup server to primary storage. Primary storage mounts the secondary storage volume and directly transfers the differential data that updated after the last backup. The example implementations reduce the LAN network load and the load on the backup server and speeding up the backup process.

Abstract: Saving a capacity of an on-premises storage apparatus, a high access performance of the on-premises storage apparatus, and resuming an operation quickly and accurately by using data on a cloud when a resource in the on-premises fails are achieved. A processor provides a first volume which is a virtual volume, and configures a copy pair of the first volume and a second volume provided from another storage system. Write data to the first volume is transferred to the second volume via a network, based on the copy pair. The processor writes to the memory a part of data written to the second volume, and writes to the storage device the data written to the memory.

Abstract: Example implementations described herein are directed to automated failover and assuring RTO (Recovery Time Objective) assurance, and RPO (Recovery Point Objective) on asynchronous remote copy feature of storage. By using markers that are cyclically stored to the journal volume, the storage device can thereby determine an accurate communication loss period.