Protecting data segments in a computing environment

Patent metadata

Field	Value
Publication number	US-2016188239-A1
Application number	US-201615064839-A
Country	US
Kind code	A1
Filing date	Mar 9, 2016
Priority date	Jun 2, 2011
Publication date	Jun 30, 2016
Grant date	—

Abstract

Exemplary method, system, and computer program product embodiments for protecting data segments by a processor device in a computing environment, are provided. In one embodiment, by way of example only, a history table is configured to accompany data segments for consultation during a replication operation. If the history table indicates an ownership conflict, the replication operation is inhibited.

First claim

What is claimed is:

1 . A method for protecting a plurality of data segments by a processor device in a computing environment, comprising:
configuring a history table to accompany each of the plurality of data segments for consultation during a replication operation, wherein if the history table indicates an ownership conflict, the replication operation is inhibited; if an error occurs during the replication operation from a source location to a destination location causing at least one of a plurality of data segments to be deleted in the source location, performing:
executing a failback operation by a reverse replication process of the at least one of a plurality of data segments from the destination location to the source location, and
regaining ownership of the at least one of a plurality of data segments by the source location; and
pursuant to the failback operation, performing:
enabling the reverse replication process if an owner of the at least one of a plurality of data segments is a designated one of the destination location, and
adding an invalid owner notification in the history table, wherein the failback operation is identified for the designated one of the at least one destination location.

2 . The method of claim 1 , further including establishing an initial ownership of the plurality of data segments, including performing:
gaining ownership of a source location at the time of creation of the plurality of data segments, setting an ownership attribute with an ownership identification (ID) of the at least one source location in a grid context for the plurality of data segments, and listing the ownership ID of the plurality of data segments in the history table.

3 . The method of claim 1 , further including, in conjunction with the replication operation, sending the history table from a source location to a destination location.

4 . The method of claim 1 , further including, pursuant to a change of ownership of at least one of the plurality of data segments, performing:
waiving ownership of the at least one of the plurality of data segments for a source location, gaining the ownership of the at least one of the plurality of data segments by a destination location, and updating the ownership of the at least one of the plurality of data segments in the history table at both the source location and the destination location.

5 . The method of claim 1 , further including, if ownership of at least one of the plurality of data segments is obtained by a first and second destination location:
identifying the ownership conflict between the first and second destination location, sending an error notification of the ownership conflict, preventing the replication operation of the at least one of the plurality of data segments from the second destination location to a third destination location, and deleting the at least one of the plurality of data segments in the second destination location.

6 . The method of claim 1 , further including, in conjunction with the replication operation, performing:
if the at least one of a plurality of data segments does not exist in a destination location:
replicating the at least one of a plurality of data segments to the destination location, and
if the at least one of the plurality of cartridges does exist in the destination location:
comparing the history table in the destination location with the history table sent from a source location.

7 . The method of claim 6 , further including, pursuant to the comparing the history table in the destination location with history table sent from the source location, performing:
if the history table in the destination location is a prefix of the history table from the source location:
enabling the replication process of the at least one of a plurality of data segments, and
if the history table in the destination location is not the prefix of the history table from the source location:
inhibiting the replication process of the at least one of a plurality of data segments.

8 . A system for protecting a plurality of data segments in a computing environment, comprising:
at least one processor device, operable in the computing environment, wherein the at least one processor device is adapted for:
configuring a history table to accompany each of the plurality of data segments for consultation during a replication operation, wherein if the history table indicates an ownership conflict, the replication operation is inhibited,
if an error occurs during the replication operation from a source location to a destination location causing at least one of a plurality of data segments to be deleted in the source location, performing:
executing a failback operation by a reverse replication process of the at least one of a plurality of data segments from the destination location to the source location, and
regaining ownership of the at least one of a plurality of data segments by the source location, and

pursuant to the failback operation, performing:
enabling the reverse replication process if an owner of the at least one of a plurality of data segments is a designated one of the destination location, and
adding an invalid owner notification in the history table, wherein the failback operation is identified for the designated one of the at least one destination location.

9 . The system of claim 8 , wherein the at least one processor device is further adapted for performing:
establishing an initial ownership of the at least one of the plurality of cartridges, including performing at least one of:
gaining ownership of a source location at the time of creation of the plurality of data segments,
setting an ownership attribute with an ownership identification (ID) of the at least one source location in a grid context for the plurality of data segments, and
listing the ownership ID of the plurality of data segments in the history table.

10 . The system of claim 8 , wherein the at least one processor device is further adapted for, in conjunction with the changing ownership, performing:
selecting the at least one primary location in a grid context from a replication grid manager, and directly logging into the at least one primary location.

11 . The system of claim 8 , wherein the at least one processor device is further adapted for, in conjunction with the replication operation, sending the history table from a source location to a destination location.

12 . The system of claim 8 , wherein the at least one processor device is further adapted for, pursuant to a change of ownership of at least one of the plurality of data segments, performing:
waiving ownership of the at least one of the plurality of data segments for a source location, gaining the ownership of the at least one of the plurality of data segments by a destination location, and updating the ownership of the at least one of the plurality of data segments in the history table at both the source location and the destination location.

13 . The system of claim 8 , wherein the at least one processor device is further adapted for, if ownership of at least one of the plurality of data segments is obtained by a first and second destination location:
identifying the ownership conflict between the first and second destination location, sending an error notification of the ownership conflict, preventing the replication operation of the at least one of the plurality of data segments from the second destination location to a third destination location, and deleting the at least one of the plurality of data segments in the second destination location.

Assignees

• IBM

Inventors

• Akirav Shay H
• Drobchenko Elena
• Maoz Itay
• Paz Gil E
• Stotland Vadim

Classifications

• G06F3/0619 Primary

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

• G06F3/0665

  at area level, e.g. provisioning of virtual or logical volumes · CPC title

• G06F3/065

  Replication mechanisms · CPC title

• G06F3/0686

  Libraries, e.g. tape libraries, jukebox · CPC title

• G06F16/184 Primary

  implemented as replicated file system · CPC title