IBM DS6000 Series manual Interfaces for Copy Services, Consistency Group Example

LSS11

1st

Completed

This write operation is completed because LSS11 is not in an extended long busy condition.

Servers

2nd

3rd

independent for each write operation

LSS12

Wait

LSS13

Completed

This write operation is not completed because LSS12 is in an extended long busy condition.

This write operation is completed because LSS13 is not in an extended long busy condition.

(I/O sequence is not kept.)

Figure 6-14 Consistency Group: Example 3

In this case, the copy created by Consistency Group operation reflects only the 1st and 3rd write operation, not including the 2nd operation.

If you accept this result, you can use Consistency Group operation with your applications. But, if you cannot accept it, you should consider other procedures without Consistency Group operations. For example, you could stop your applications for a slight interval for the backup operations.

6.3 Interfaces for Copy Services

There are multiple interfaces for invoking Copy Services. We describe them in this section.

6.3.1 DS Management Console

Copy Service functions can be initiated over the following interfaces:

￿zSeries Host I/O Interface

￿DS Storage Manager Web-based Interface

￿DS Command-Line Interface (DS CLI)

￿DS open application programming interface (DS Open API)

DS Storage Manager, DS CLI, and DS Open API commands are issued via the Ethernet network, and these commands are invoked by the DS Management Console (MC). When the MC has the command requests, including those for Copy Services, from these interfaces, the

108DS6000 Series: Concepts and Architecture