International Business Machines Corporation

Other

Globalfoundries Inc.

Carol Santich Mellgren

Theresa Mary Brown

Gregory E McBride

Lokesh M Gupta

Nicolas Marc Clayton

Nedlaya Yazzie Francisco

Raul Eduardo Saba

Theodore Timothy Harris, Jr

Michael T Benhase

Matthew John Ward

Mark L Lipets

Joshua J Crawford

David Randall Blea

William J Rooney

Suguang Li

Warren Keith Stanley

Jared Michael Minch

Tabor R Powelson

Matthew J Kalos

Matthew G Borlick

Gail Andrea Spear

John Glenn Thompson

David C Reed

Alfred Emilio Sanchez

Matthew Sanchez

Scott Brady Compton

Matthew Richard Craig

Kenneth Wayne Todd

Michael Thomas Benhase, Jr

Dale Francis Riedy, Jr

Clint Alan Hardy

Kurt Allen Lovrien

Damian Trujillo

Kevin C Lin

Kevin J Ash

Brian D Hatfield

Ellen Joanne Grusy

Anthony J Ciaravella

Tri M Hoang

Michael S Gagner

Karl Allen Nielsen

Todd Charles Sorenson

Rivka Mayraz Matosevich

Matthew D Carson

Tariq Hanif

Edgar Xavier Somoza

Edwin K Scott

Aviad Zlotnick

Michael Edward Factor

Richard Anthony Ripberger

David Michael Shackelford

Brian Anthony Rinaldi

Shachar Fienblit

Thomas Charles Jarvis

Robert Francis Bartfai

Eyal Gordon

Olympia Gluck

David Frank Mannenbach

James Chien-Chiung Chen

Vernon John Legvold

Chung Man Fung

Minh-Ngoc Le Huynh

Alan George McClure

Stephen M Tee

Patricia Ching Lu

Eli Malul

David Brent Schreiber

Steven Robert Lowe

Angqin Bai

Alex Chen

David Fei

Eduard Aaron Diel

William Dennis Williams

Nicholas S Ham

Gary Steven Domrow

Chuong H Tran

Jeffrey Michael Barnes

Theodore T Harris

Nicholas M Clayton

A secondary storage controller determines one or more tracks of one or more volumes in which data loss has occurred in the secondary storage controller. The secondary storage controller suspends a peer to peer remote copy operation between the secondary storage controller and a primary storage controller. Information on the one or more tracks of the one or more volumes in which the data loss has occurred is transmitted to the primary storage controller.

Data loss recovery in a secondary storage controller from a primary storage controller

A computational device receives a command to activate a time lock for a data set. In response to receiving the command to activate the time lock for the data set, a point in time copy of the data set is generated to allow write operations to be performed even if the time lock is activated.

Point in time copy of time locked data in a storage controller

Withdrawal of a point-in-time snap copy relationship or a portion of such a relationship, is managed in a manner which can obviate disruption of consistency groups due to the withdrawal. If the withdrawal request is directed to a subrange of the original snap copy relationship, the snap copy relationship is split by creating one or more point-in-time snap copy relationships over one or more subranges of tracks of the snap copy source. A determination is made as to whether to delay execution of the withdrawal request to temporarily preserve data of the withdrawal range. Disruptions to completion of consistency groups may be avoided by selectively delaying the withdrawal of a snap copy relationship corresponding to the withdrawal subrange. In so far as the host is involved, a host may treat the withdrawal request as immediately granted without delay. Other aspects may be realized, depending upon the particular application.

Point-in-time snap copy withdrawal management

Remote copy operations are performed to copy data from a primary storage controller to a secondary storage controller, wherein input/output (I/O) requests are received at the primary storage controller from a host both via a bus interface and a network interface while the remote copy operations are in progress, and wherein consistency groups are formed during the remote copy operations to copy the data consistently. Quiescing of I/O operations performed via the bus interface are performed while a current consistency group is being replaced by a next consistency group during the remote copy operations.

Management of data written via a bus interface to a storage controller during consistent copying of data

Provided is a method for correcting untrusted data and avoiding logical device swapping for at least one logical subsystem of at least one computer system. A processor may monitor a primary storage for one or more errors that indicate untrusted data on the primary storage. An error indicating that a data set on the primary storage is an untrusted data set may be identified. In response to the error being identified, a corresponding uncompromised version of the data set may be read from a secondary storage. The corresponding uncompromised version of the data set may be written over the untrusted data set on the primary storage.

Automatic data healing by I/O

Provided are a method, system, and computer program product in which a computational device stores a data structure that includes identifications of a plurality of volumes and identifications of one or more time locks associated with each of the plurality of volumes. The data structure is indexed into, to determine whether an input/output (I/O) operation from a host with respect to a volume is to be permitted.

Performance efficient time locks on data in a storage controller

Provided are techniques for performing a recovery copy command to restore a safeguarded copy backup to a production volume. In response to receiving a recovery copy command, a production target data structure is created. A read operation is received for data for a storage location. In response to determining that the data for the storage location is in a cache of a host and a generation number is greater than a recovery generation number, the data is read from the cache. In response to determining at least one of that the data for the storage location is not in the cache and that the generation number is not greater than the recovery generation number, the data is read from one of the production volume and a backup volume based on a value of an indicator for the storage location in the production target data structure.

Performing a recovery copy command to restore a safeguarded copy backup to a production volume

Provided are a computer program product, system, and method for updating change information for current copy relationships when establishing a new copy relationship having overlapping data with the current copy relationships. A first copy relationship indicates changed first source data to copy to first target data. An establish request is processed to create a second copy relationship to copy second source data in to second target data. A second copy relationship is generated, in response to the establish request, indicating data in the second source data to copy to the second target data. A determination is made of overlapping data units in the first source data also in the second target data. Indication is made in the first copy relationship to copy the overlapping data units. The first source data indicated in the first copy relationship is copied to the first target data, including data for the overlapping data units.

Updating change information for current copy relationships when establishing a new copy relationship having overlapping data with the current copy relationships

Provided are a computer program product, system, and method for copying data from multiple point-in-time copies to a log storage to use to roll-back a source storage managing point-in-time copies of a source storage. A plurality of point-in-time copies of a source storage at different point-in-times are established. In response to receiving writes to the source storage after establishing each of the point-in-time copies, point-in-time data in the source storage is copied, before being updated by the received writes, to a log storage, wherein the log storage stores point-in-time data for multiple of the point-in-time copies. The log storage is used to roll-back the source storage to a selected point-in-time of one of the point-in-time copies.

Copying data from multiple point-in-time copies to a log storage to use to roll-back a source storage

Consistency groups are asynchronously copied to a remote computational device, from a local computational device, wherein point in time copy operations are performed at the local computational device while the consistency groups are being asynchronously copied to the remote computational device. Indicators are stored at the remote computational device to identify those point in time copy operations that are to be restored as part of a recovery operation performed at the remote computational device in response to a failure of the local computational device.

Restoration of data when point in time copy operations are performed during asynchronous copy

Provided are a computer program product, system, and method for determining whether to destage write data in cache to storage based on whether the write data has malicious data. Write data for a storage is cached in a cache. A determination is made as to whether the write data in the cache comprises random data according to a randomness criteria. The write data in the cache to the storage in response to determining that the write data does not comprise random data according to the randomness criteria. The write data is processed as malicious data after determining that the write data comprises random data according to the randomness criteria.

Determining whether to destage write data in cache to storage based on whether the write data has malicious data

One general aspect of device reservation state synchronization in accordance with the present description, device reservation management logic ensures synchronization of reservation states of primary and secondary volumes of a mirror relationship in the event of a change in the state of the mirroring relationship such as achieving full data synchronization between the volumes. Other features and aspects may be realized, depending upon the particular application.

Device reservation state synchronization in data mirroring

Provided are a computer program product, system, and method for offloading processing of writes to determine malicious data from a first storage system to a second storage system. Write data for a first storage is cached in a first cache in the first storage system and copied to a second cache in the second storage system. The second storage system determines whether the copy of the write data comprises random data according to a randomness criteria. The second storage system returns a message to the first storage system indicating that the write data comprises malicious data if random or not malicious data if not random. The first storage system destages the write data in the first cache if the message indicates not malicious data or processes the write data in the first cache as malicious data if the message indicates malicious data.

Offloading processing of writes to determine malicious data from a first storage system to a second storage system

Provided is a method for correcting pinned data in a primary storage. A primary storage controller may detect a pinned data set on a primary storage. In response to detecting the pinned data set, the primary storage controller may instruct a secondary storage controller to transmit a copy of the pinned data set to the primary storage controller. The copy of the pinned data set may be stored in a secondary storage that is communicatively coupled to the secondary storage controller. The secondary storage may include a synchronous copy of the primary storage. The primary storage controller may receive the copy of the pinned data set from the secondary storage controller. The primary storage controller may also write the copy of the pinned data set over the pinned data set on the primary storage.

Automatic data healing using a storage controller

Growing community of inventors

Tucson, AZ, United States of America

Carol Santich Mellgren