hit counter script

Growth Within Global Mirror Configurations - IBM System storage DS6000 Series Redbook

Copy services with ibm system z
Hide thumbs Also See for System storage DS6000 Series:
Table of Contents

Advertisement

Host
channels
FICON
Host
Figure 25-4 Remote storage disk subsystem with D volumes
You should still put the B and C volumes in different ranks. It is further recommended that you
configure corresponding B and C volumes in such a way that these volumes have an affinity
to the same server. It would also be ideal to have the B volumes connected to a different DA
pair than the C volumes.

25.5 Growth within Global Mirror configurations

When you add a rather large number of volumes at once to an existing Global Mirror session,
then the available resources for Global Copy within the affected ranks might be over-utilized
or even monopolized by the initial copy pass. To avoid too much impact, consider adding
many new volumes to an existing Global Mirror session in stages. If possible, and as a rough
rule of thumb, add only a few volumes in a rank during application peak I/O periods. After the
first initial copy is complete, add the next few volumes. Again, as a rule of thumb, plan for
adding one or two volumes in a rank during peak I/O load for the first initial copy pass. If
possible, then plan a massive add of new Global Copy volumes into an existing session
during off-peak periods.
340
IBM System Storage DS6000 Series: Copy Services with IBM System z
A
A1
Primary
Primary
Primary
PENDING
Rank 1
A
FCP
A2
Primary
Primary
Primary
PENDING
Rank 2
A
A3
Primary
Primary
Primary
PENDING
Rank 3
Local site
links
FCP
Host
Remote site
Primary
A
Primary
Primary
C3
B1
Primary
Se condar y
Tertiary
PENDING
Rank 1
Primary
A
Primary
Primary
C1
B2
Primary
Se condar y
Tertiary
PENDING
Rank 2
Primary
A
Primary
Primary
B3
C2
Primary
Se condar y
Tertiary
PENDING
Rank 3
Primary
A
Primary
Primary
D1
D2
Primary
A
Primary
D3
Primary
Rank 4

Advertisement

Table of Contents
loading

Table of Contents