Browse Prior Art Database

Graphical Method for Specifying Session Copy Sets Candidates

IP.com Disclosure Number: IPCOM000167098D
Original Publication Date: 2008-Jan-30
Included in the Prior Art Database: 2008-Jan-30
Document File: 2 page(s) / 21K

Publishing Venue

IBM

Abstract

A graphical procedure for creating multiple copy service relationships allows users a simple method for defining volumes that should participate in a copy services session.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

Graphical Method for Specifying Session Copy Sets Candidates

Disclosed is a process for specifying multiple copy services relationships through a graphical interface. Users specify copy sets to be included in a session.

A copy set is a set of volumes that participate in a copy services relationship. Each volume in a copy set has a specific role in the copy services relationship. For example, a three volume copy set is composed of a set of three volumes. As changes are made to the first volume in the relationship, the changes are propagated to the second volume in the relationship, and then to the third volume.

Groups of copy sets can be combined to form a session. Sessions are containers for multiple copy sets, where the consistency of the data in the copy sets is managed by session operations. A session type specifies rules for copying data, as well as restrictions that are placed on volumes taking part in the copy sets. For example, a session rule may state that all volumes taking part in a copy set must be of the same capacity. Another session rule may specify that all volumes in a session must be of the same volume type (homogeneous).

The user is guided through a set of panels, one for each role in the copy set. On each panel, the user selects a volume that is to be selected for the particular role in the copy set. Volumes are selected on each panel by first selecting the storage subsystem and logical volume grouping in which the volume resides. Examples of a logical volume grouping would be a Logical Subsystem on an Enterprise Storage Subsystem and an IO Group on a SAN Volume Controller. An example panel is shown in Figure 1.

Instead of limiting the user to selecting individual volumes to be matched, the user is able to create multiple volume relationships at one time. This is accomplished by allowing the user to create volume relationships at three different levels; storage subsystem, logical volume grouping, and individual volume.

The storage subsystem level allows the user to create copy sets for every volume on multiple storage subsystems. To do this, the user would select a particular storage subsystem on the first panel, indicating that all of the volumes on the storage subsystem should be placed into a copy set role. The user would then select another storage subsystem for each additional role in the copy set. The end result is that all of the volumes on each storage device would be placed into a selected role in a copy set.

The logical volume grouping level works in a similar manner. The user selects a logical volume grouping for each role in the copy set. The volumes in each logical volume grouping are then placed in copy sets.

After selecting a storage subsystem, logical volume grouping, or individual volume for each role in the volume relationship, the end result is a list of user selections. These selections can be fed into a matching algorithm that selects individual volum...