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

Patent metadata

Field	Value
Publication number	US-11829609-B2
Application number	US-202217959970-A
Country	US
Kind code	B2
Filing date	Oct 4, 2022
Priority date	Jun 3, 2016
Publication date	Nov 28, 2023
Grant date	Nov 28, 2023

Abstract

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.

First claim

What is claimed is:

1. A method comprising,
determining, by a secondary storage controller, one or more tracks of one or more volumes in which data loss has occurred in the secondary storage controller;
suspending, by the secondary storage controller, a peer to peer remote copy operation between the secondary storage controller and a primary storage controller; and
transmitting information on the one or more tracks of the one or more volumes in which the data loss has occurred to the primary storage controller, wherein a timer is queued to process a lost track volume list for a predetermined amount of time, and for each additional track that is lost the timer is requeued once again for the predetermined amount of time to dispatch a task to process the lost track volume list once no data loss has been observed for at least the predetermined amount of time.

2. The method of claim 1 , wherein in response to a process volume list task being dispatched once no data loss has been detected for the predetermined amount of time, cycling through a list and for volumes affected by data loss calling a copy service code component with a range of peer to peer remote copy secondary tracks.

3. The method of claim 1 , the method further comprising:
accumulating over a period of time, by the secondary storage controller, the information on the one or more tracks of the one or more volumes in which the data loss has occurred, prior to transmitting of any part of the information to the primary storage controller.

4. The method of claim 1 , wherein the one or more tracks comprise a first track and a second track of a volume, the method further comprising:
in response to an unsuspension of the peer to peer remote copy operation, receiving by the secondary storage controller, data stored in the primary storage controller to restore data in a range of tracks starting from the first track to the second track of the volume of the secondary storage controller to recover from the data loss.

5. The method of claim 1 , wherein a data structure is updated in the primary storage controller to indicate that data of the one or more tracks of the one or more volumes are to be transmitted on continuation of the peer to peer remote copy operation to the secondary storage controller.

6. The method of claim 1 , the method further comprising:
determining, by a tertiary storage controller, a set of tracks of a volume in which data loss has occurred in the tertiary storage controller;
suspending, by the tertiary storage controller, another peer to peer remote copy operation between the tertiary storage controller and the secondary storage controller; and
transmitting, by the tertiary storage controller, information on the set of tracks of the volume in which the data loss has occurred to the secondary storage controller.

7. A system comprising,
a memory; and
a processor coupled to the memory, wherein the processor performs operations, the operations comprising:
determining, by a secondary storage controller, one or more tracks of one or more volumes in which data loss has occurred in the secondary storage controller;
suspending, by the secondary storage controller, a peer to peer remote copy operation between the secondary storage controller and a primary storage controller; and
transmitting information on the one or more tracks of the one or more volumes in which the data loss has occurred to the primary storage controller, wherein a timer is queued to process a lost track volume list for a predetermined amount of time, and for each additional track that is lost the timer is requeued once again for the predetermined amount of time to dispatch a task to process the lost track volume list once no data loss has been observed for at least the predetermined amount of time.

8. The system of claim 7 , wherein in response to a process volume list task being dispatched once no data loss has been detected for the predetermined amount of time, cycling through a list and for volumes affected by data loss calling a copy service code component with a range of peer to peer remote copy secondary tracks.

9. The system of claim 7 , the operations further comprising:
accumulating over a period of time, by the secondary storage controller, the information on the one or more tracks of the one or more volumes in which the data loss has occurred, prior to transmitting of any part of the information to the primary storage controller.

10. The system of claim 7 , wherein the one or more tracks comprise a first track and a second track of a volume, the operations further comprising:
in response to an unsuspension of the peer to peer remote copy operation, receiving by the secondary storage controller, data stored in the primary storage controller to restore data in a range of tracks starting from the first track to the second track of the volume of the secondary storage controller to recover from the data loss.

11. The system of claim 7 , wherein a data structure is updated in the primary storage controller to indicate that data of the one or more tracks of the one or more volumes are to be transmitted on continuation of the peer to peer remote copy operation to the secondary storage controller.

12. The system of claim 7 , the operations further comprising:
determining, by a tertiary storage controller, a set of tracks of a volume in which data loss has occurred in the tertiary storage controller;
suspending, by the tertiary storage controller, another peer to peer remote copy operation between the tertiary storage controller and the secondary storage controller; and
transmitting, by the tertiary storage controller, information on the set of tracks of the volume in which the data loss has occurred to the secondary storage controller.

13. A computer program product, the computer program product comprising a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code configured to perform operations, the operations comprising:
determining, by a secondary storage controller, one or more tracks of one or more volumes in which data loss has occurred in the secondary storage controller;
suspending, by the secondary storage controller, a peer to peer remote copy operation between the secondary storage controller and a primary storage controller; and
transmitting information on the one or more tracks of the one or more volumes in which the data loss has occurred to the primary storage controller, wherein a timer is queued to process a lost track volume list for a predetermined amount of time, and for each additional track that is lost the timer is requeued once again for the predetermined amount of time to dispatch a task to process the lost track volume list once no data loss has been observed for at least the predetermined amount of time.

14. The computer program product of claim 13 , wherein in response to a process volume list task being dispatched once no data loss has been detected for the predetermined amount of time, cycling through a list and for volumes affected by data loss calling a copy service code component with a range of peer to peer remote copy secondary tracks.

15. The computer program product of claim 13 , the operations further comprising:
accumulating over a period of time, by the secondary storage controller, the information on the one or more tracks of the one or more volumes in which the data loss has occurred, prior to transmitting of any part of the information to the primary storage controller.

16. The computer program product of claim 13 , wherein the one

Assignees

• IBM

Inventors

• Carson Matthew D
• Mellgren Carol S
• Nielsen Karl A
• Sanchez Matthew
• Sorenson Todd C

Classifications

• G06F3/0619 Primary

  in relation to data integrity, e.g. data losses, bit errors · CPC title

• G06F3/065

  Replication mechanisms · CPC title

• G06F3/0689

  Disk arrays, e.g. RAID, JBOD · CPC title

• G06F11/14

  Error detection or correction of the data by redundancy in operations (error detection or correction of the data by redundancy in hardware G06F11/16) · CPC title

• G06F11/1662

  the resynchronized component or unit being a persistent storage device (re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008) · CPC title