Protection of former primary volumes in a synchronous replication relationship
View Patent ↗An aspect includes protecting a former primary volume in a synchronous replication relationship. A swap between a primary volume at a first site and a secondary volume at a second site is initiated such that the secondary volume becomes a new primary volume and the primary volume becomes the former primary volume. A fenced state is set as active for the former primary volume. The former primary volume is configured as a fenced volume based on the fenced state being active. Read and write access to the fenced volume is blocked while the fenced state is active.
1. A method for protecting a former primary volume in a synchronous replication relationship, comprising:
initiating a swap between a primary volume at a first site and a secondary volume at a second site such that the secondary volume becomes a new primary volume and the primary volume becomes the former primary volume;
setting a fenced state as active for the former primary volume;
configuring the former primary volume as a fenced volume based on the fenced state being active; and
blocking read and write access to the fenced volume while the fenced state is active.
2. The method of claim 1 , further comprising:
clearing the fenced state based on one of: an unfence command and a resynchronize operation; and
restoring read and write access to the former primary volume based on the clearing of the fenced state.
3. The method of claim 2 , wherein a fence command and the unfence command are accessible through one or more of: an application programming interface, a command line interface, and a graphical user interface.
4. The method of claim 1 , further comprising:
identifying the former primary volume to be configured as the fenced volume based on a parameter received with a fence command.
5. The method of claim 1 , wherein the swap is initiated as one of: a planned swap and an unplanned swap.
6. The method of claim 1 , further comprising:
returning a unique sense code upon an access attempt to the fenced volume while the fenced state is active.
7. The method of claim 1 , further comprising:
determining whether the configuring of the former primary volume as the fenced volume was successful; and
periodically reattempting to configure the former primary volume as the fenced volume based on determining that the configuring was unsuccessful.
8. The method of claim 1 , wherein the fenced state is persistent through a reset condition.
9. A system protecting a former primary volume in a synchronous replication relationship, comprising:
a storage controller at a first site coupled to a primary volume designated as the former primary volume upon a swap to a secondary volume at a second site; and
fencing control logic configured to establish the former primary volume as a fenced volume based on a fenced state being active, and further configured to block read and write access to the fenced volume while the fenced state is active.
10. The system of claim 9 , wherein the fencing control logic is further configured to clear the fenced state based on one of: an unfence command and a resynchronize operation, and to restore read and write access to the former primary volume based on the clearing of the fenced state.
11. The system of claim 10 , wherein a fence command and the unfence command are accessible through one or more application programming interfaces of the geographically dispersed parallel systems complex.
12. The system of claim 9 , wherein the fencing control logic is further configured to identify the former primary volume to be configured as the fenced volume based on a parameter received with a fence command.
13. The system of claim 9 , wherein the fencing control logic is further configured to return a unique sense code upon an access attempt to the fenced volume while the fenced state is active.
14. The system of claim 9 , wherein system is further configured to determine whether configuring of the former primary volume as the fenced volume was successful, and periodically reattempt to configure the former primary volume as the fenced volume based on determining that the configuring was unsuccessful.
15. The system of claim 9 , wherein the fenced state is persistent through a reset condition.
16. A computer program product for protecting a former primary volume in a synchronous replication relationship, the computer program product comprising:
a tangible non-transitory storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising:
setting a fenced state as active for a former primary volume at a first site upon a swap to a secondary volume at a second site;
configuring the former primary volume as a fenced volume based on the fenced state being active; and
blocking read and write access to the fenced volume while the fenced state is active.
17. The computer program product of claim 16 , further comprising:
clearing the fenced state based on one of: an unfence command and a resynchronize operation; and
restoring read and write access to the former primary volume based on the clearing of the fenced state.
18. The computer program product of claim 16 , further comprising:
identifying the former primary volume to be configured as the fenced volume based on a parameter received with a fence command.
19. The computer program product of claim 16 , further comprising:
returning a unique sense code upon an access attempt to the fenced volume while the fenced state is active.
20. The computer program product of claim 16 , further comprising:
determining whether the configuring of the former primary volume as the fenced volume was successful; and
periodically reattempting to configure the former primary volume as the fenced volume based on determining that the configuring was unsuccessful.