IP Library Granted Patent US 9,594,645
Granted Patent B2
US 9,594,645 · App. 15/083,511 · Granted Mar 14, 2017

Protecting data segments in a computing environment

Inventors: Shay H. Akirav (Petach-Tikva, IL); Elena Drobchenko (Raanana, IL); Itay Maoz (Haifa, IL); Gil E. Paz (Yehud, IL); Vadim Stotland (Petach-Tikva, IL)
Assignee: INTERNATIONAL BUSINESS MACHINES CORPORATION
G06F11/1471G06F3/065G06F3/0619G06F3/0665G06F3/0683G06F3/0686G06F11/1474G06F17/30174G06F17/30212G06F17/30233G06F2201/805G06F2201/82G06F2201/85
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,594,645
App. No.
15/083,511
Granted
Mar 14, 2017
Kind
B2
Abstract

Various embodiments for protecting data segments by a processor device in a computing environment, are provided. In one embodiment, a method comprises, if an error occurs during a 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 from the destination location to the source location, and regaining ownership of the data segments by the source location; and pursuant to the failback operation, performing: enabling the reverse replication process if an owner of the data segments is a designated one of the destination location, and adding an invalid owner notification in a history table, wherein the failback operation is identified for the designated one of the at least one destination location.

Claims (102)

1. A method for protecting a plurality of data segments by a processor device in a computing environment, comprising:

if an error occurs during a 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 a 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 configuring the history table to accompany each of the plurality of data segments for consultation during the replication operation, wherein if the history table indicates an ownership conflict, the replication operation is inhibited; and

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 2 , 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 2 , 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 2 , 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 2 , 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:

if an error occurs during a 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 a 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:

configuring the 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, and

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 9 , 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 9 , 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 9 , 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 9 , 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.

14. The system of claim 9 , wherein the at least one processor device is further adapted for, 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.

15. The system of claim 14 , wherein the at least one processor device is further adapted for, 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.

16. A computer program product for protecting a plurality of data segments by a processor device, the computer program product comprising a non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

an executable portion for, if an error occurs during a 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

an executable portion for, 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 a history table, wherein the failback operation is identified for the designated one of the at least one destination location.

17. The computer program product of claim 16 , further including:

an executable portion for configuring the history table to accompany each of the plurality of data segments for consultation during the replication operation, wherein if the history table indicates an ownership conflict, the replication operation is inhibited; and

an executable portion for 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.

18. The computer program product of claim 17 , further including an executable portion for, in conjunction with the replication operation, sending the history table from a source location to a destination location.

19. The computer program product of claim 17 , further including an executable portion 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.

20. The computer program product of claim 17 , further including an executable portion 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.

21. The computer program product of claim 17 , further including an executable portion for, 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.

22. The computer program product of claim 21 , further including an executable portion for, 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.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 29, 2016
From: AKIRAV, SHAY H.; DROBCHENKO, ELENA; MAOZ, ITAY; PAZ, GIL E.; STOTLAND, VADIM
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 038281/0722 →
Continuity (3)
Continuation 13801449 · Mar 13, 2013
Continuation 13152099 · Jun 2, 2011
Related Publication 20160210206A1 · Jul 21, 2016