# US 2014/0195483 A1 · Copy of replication status for synchronization > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0195483 A1 - Document ID: US20140195483A1 - Status: Published application - Kind: A1 - Application number: 13/734,909 - Filed: 2013-01-04 - Published: 2014-07-10 - Earliest claimed: 2013-01-04 - Assignees: International Business Machines Corporation - Inventors: Nicolas M. Clayton - Web page: https://patentgrep.com/patent/US20140195483A1 ## CPC - G06F 16/275: {Synchronous replication} - G06F 11/1446: Point-in-time backing up or restoration of persistent data - G06F 11/2069: {Management of state, configuration or failover} - G06F 11/2074: {Asynchronous techniques} - G06F 16/2237: {Vectors, bitmaps or matrices} - G06F 11/2058: {using more than 2 mirrored copies} - G06F 11/2071: {using a plurality of controllers} - G06F 11/2082: {Data synchronisation} - G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract For synchronizing replication status, a copy module continuously replicates data from a first device designated with a device status of primary to a second device designated with a device status of secondary. A first peer-to-peer remote copy (PPRC) relationship is established between the first and second devices. The first and second devices store replication information comprising a bitmap with a replication status for each data block of the first device. The copy module further copies an instant point-in-time copy of the data from the second device to a copy device. In addition, the copy module copies the replication information from the second device to the copy device and links the replication information of the second device and copy devices. ## Claims ### Claim 1 An apparatus comprising: a computer readable storage medium storing program code executable by a processor, the program code comprising: a copy module continuously replicating data from a first device designated with a device status of primary to a second device designated with a device status of secondary, wherein a first peer-to-peer remote copy (PPRC) relationship is established between the first and second devices, the first and second devices storing replication information comprising a bitmap with a replication status for each data block of the first device, copying an instant point-in-time copy of the data from the second device to a copy device, copying the replication information from the second device to the copy device, and creating a link between the replication information of the second device and the replication information of the copy device. ### Claim 2 (depends on 1) The apparatus of claim 1, the copy module further copying the data from the second device to the copy device with the first device and the second device in a suspended first PPRC relationship, wherein changes to the data of the first device are not replicated to the second device and the second device has a device status of primary. ### Claim 3 (depends on 1) The apparatus of claim 1, wherein a copy relationship is established on the copy device and linked to the first PPRC relationship on the second device by creating a copy of the replication information from the second device on the copy device. ### Claim 4 (depends on 3) The apparatus of claim 3, the program code further comprising a validation module validating a new PPRC relationship by comparing the PPRC relationship replication status stored on the second device with the PPRC relationship replication status stored on the first device in response to the copy module receiving a failback command designating the copy device with a device status of primary and the first device with the device status of secondary, and the copy module terminating the first PPRC relationship on the second device, updating the device status of the first device to secondary, and replicating the copy device data to the first device using an OR of replication information bitmaps on the copy and first devices. ### Claim 5 A method for synchronizing replication status comprising: continuously replicating data from a first device designated with a device status of a primary to a second device designated with a device status of secondary, wherein a first peer-to-peer remote copy (PPRC) relationship is established between the first and second devices, the first and second devices storing replication information comprising a bitmap with a replication status for each data block of the first device; copying an instant point-in-time copy of the data from the second device to a copy device; copying the replication information from the second device to the copy device; and creating a link between the replication information of the second device and the replication information of the copy device ### Claim 6 (depends on 5) The method of claim 5, wherein the data is copied from the second device to the copy device with the first device and the second device in a suspended first PPRC relationship, wherein changes to the data of the first device are not replicated to the second device. ### Claim 7 (depends on 5) The method of claim 5, wherein a copy relationship is established on the copy device and linked to the first PPRC relationship on the second device by creating a copy of the replication information from the second device on the copy device. ### Claim 8 (depends on 7) The method of claim 7, wherein the first PPRC relationship is maintained if the copy relationship on the copy device is terminated. ### Claim 9 (depends on 7) The method of claim 7, further comprising in response to a failback command designating the copy device with a device status of primary and the first device with the device status of secondary, validating a new PPRC relationship by comparing the PPRC relationship replication status stored on the second device with the PPRC relationship replication status stored on the first device; terminating the first PPRC relationship on the second device; updating the device status of the first device to secondary; and replicating the copy device data to the first device using an OR of replication information bitmaps on the copy and first devices. ### Claim 10 (depends on 7) The method of claim 7, further comprising in response to a failback command designating the first device with the device status of primary and the copy device with a device status of secondary, validating a new PPRC relationship by comparing the replication status stored on the first device with the PPRC relationship replication status stored on the second device; terminating the first PPRC relationship on the second device; updating the device status of the copy device to secondary; and replicating the first device data to the copy device using an OR of replication information bitmaps on the copy and first devices. ### Claim 11 (depends on 7) The method of claim 7, further comprising in response to a failback command designating the second device with the device status of primary and the first device with the device status of secondary, validating the first PPRC by comparing the replication status stored on the second device with the replication status stored on the first device; terminating the copy relationship on the copy device; updating the device status of the first device to secondary; and replicating the second device data to the first device using an OR of replication information bitmaps on the second and first devices. ### Claim 12 (depends on 7) The method of claim 7, further comprising in response to a failback command designating the first device with the device status of primary and the second device with the device status of secondary, validating the first PPRC relationship by comparing the replication status stored on the first device with the replication status stored on the second device; terminating the second PPRC relationship on the copy device; updating the device status of the second device to secondary; and replicating the first device data to the second device using the OR of replication information bitmaps on the second and first devices. ### Claim 13 (depends on 7) The method of claim 7, further comprising: in response to receiving a withdraw command for the copy device, terminating the copy relationship if the copy of data on the second device is not completed by the withdraw command; and in response to receiving the withdraw command, maintaining the copy relationship if the copy of data on the second device is completed by the withdraw command. ### Claim 14 (depends on 5) The method of claim 5, wherein the replicating of the data from the first device to the second device, the copying instant point-in-time copy of the data from the second device to the copy device, and the copying of the replication information from the second device to the copy device is performed in response to an atomic command. ### Claim 15 (depends on 7) The method of claim 7, wherein the copy relationship on the copy device is terminated if the first PPRC relationship on the second device is terminated. ### Claim 16 A computer program product for synchronizing replication status, the computer program product comprising a computer readable storage medium having program code embodied therein, the program code readable/executable by a processor to: continuously replicating data from a first device designated with a device status of primary to a second device designated with a device status of secondary, wherein a first peer-to-peer remote copy (PPRC) relationship is established between the first and second devices, the first and second devices storing replication information comprising a bitmap with a replication status for each data block of the first device; copying an instant point-in-time copy of the data from the second device to a copy device; copying the replication information from the second device to the copy device; And creating a link between the replication information of the second device and the replication information of the copy device. ### Claim 17 (depends on 16) The computer program product of claim 16, wherein the data is copied from the second device to the copy device with the first device and the second device in a suspended first PPRC relationship, wherein changes to the data of the first device are not replicated to the second device. ### Claim 18 (depends on 16) The computer program product of claim 16, wherein a copy relationship is established on the copy device and linked to the first PPRC relationship on the second device by creating a copy of the replication information from the second device on the copy device. ### Claim 19 (depends on 18) The computer program product of claim 18, the program code further: in response to a failback command designating the copy device with a device status of primary and the first device with the device status of secondary, validating a new PPRC relationship by comparing the PPRC relationship replication status stored on the second device with the PPRC relationship replication status on the first device; terminating the first PPRC relationship on the second device; updating a status of the first device to secondary; and replicating the copy device data to the first device using an OR of replication information bitmaps on the copy and first devices. ### Claim 20 A method for deploying a computer program product, comprising integrating program code into a computing system, wherein the code in combination with the computing system performs the following: continuously replicating data from a first device designated with a device status of a primary to a second device designated with a device status of secondary, wherein a first peer-to-peer remote copy (PPRC) relationship is established between the first and second devices, the first and second devices storing replication information comprising a bitmap with a replication status for each data block of the first device; copying an instant point-in-time copy of the data from the second device to a copy device; copying the replication information from the second device to the copy device; and creating a link between the replication information of the second device and the replication information of the copy device.