Hitachi Command Control Interface (CCI) User and Reference Guide
295
Figure 4.71 shows examples of the pairsyncwait command with and without the
-nowait
option. The output of the pairsyncwait command is:
UnitID
: Unit ID in case of multiple storage system connection
CTGID
: CTGID within Unit ID
Q-Marker
: The latest sequence # of MCU PVol (Marker) when the command is received.
Status
: The status after the execution of command.
Q-Num
: The number of process queue to wait for synchronization within the CTGID.
QM-Cnt
: The number of remaining Q-Markers within CT group of the Unit.
HORCAsync/UR sends a token called “dummy recordset” at regular intervals, therefore
QM-Cnt always shows “2” or “3” even if Host has NO writing.
Following is an arithmetic expression for determining the remaining Data in a CT group:
Remaining data in CT group = Sidefile capacity * Sidefile percentage / 100
Sidefile percentage is the rate showed to “%” column with “PAIR” state by Pairdisplay
command. Sidefile capacity is the capacity within 30% to 70% of the cache setting as the
sidefile.
Following is an arithmetic expression for determining the average data per Q-Marker in a
CT group:
Data per Q-Marker = Remaining data in CT group / QM-Cnt
# pairsyncwait -g oradb -nowait
Å
-nowait is specified.
UnitID CTGID Q-Marker Status Q-Num
0 3
01003408ef
NOWAIT 2
# pairsyncwait -g oradb -t 100
Å
-nowait is not specified.
UnitID CTGID Q-Marker Status Q-Num
0 3 01003408ef DONE 2
# pairsyncwait -g oradb -t 1
UnitID CTGID Q-Marker Status Q-Num
0 3
01003408ef
TIMEOUT 3
# pairsyncwait -g oradb -t 100 -m
01003408ef
UnitID CTGID Q-Marker Status Q-Num
0 3 01003408ef DONE 0
# pairsyncwait -g oradb -t 100
UnitID CTGID Q-Marker Status Q-Num
0 3 01003408ef BROKEN 0
# pairsyncwait -g oradb -t 100 -m
01003408ef
UnitID CTGID Q-Marker Status Q-Num
0 3 01003408ef
CHANGED
0
É
Q-Marker(01003408ef) is invalid when PVOL was
resynchronized while this command is executed.
Figure 4.71 Pairsyncwait Command Examples
Summary of Contents for TAGMASTORE MK-90RD011-25
Page 2: ......
Page 8: ...viii Preface ...
Page 18: ...xviii Contents ...
Page 180: ...162 Chapter 3 Preparing for CCI Operations ...
Page 250: ...232 Chapter 4 Performing CCI Operations Vol Type logical unit LU type e g OPEN V OPEN 9 ...
Page 370: ...352 Chapter 5 Troubleshooting ...
Page 388: ...370 Acronyms and Abbreviations ...