This post is more than 5 years old
12 Posts
0
1842
SYMCLI command for Adaptive Copy throughput?
I usually have a mixture of SRDF/A and Adaptive Copy traffic in my environment, since I often am using acp_disk to do initial syncs, catch up after link outages, etc. I regularly log the output of SYMCLI command "symstat -sid -i 5 -reptype rdfa -v", which gives me helpful data on R1->R2 Throughput, Cache Uutilization, etc. However, this command never shows any data for the RDF Groups that are in acp_disk mode, and the manual page for symstat doesn't seem to indicate a way to see details on Adaptive Copy traffic (e.g. "-reptype acp_disk" would seem logical, but it's not there). Am I missing something obvious? I'm currently planning to craft up some tricky workarounds, e.g. log total network throughput (such as on my WAN router) and then subtract the SRDF/A traffic found from my existing command. But it would seem like there should be a more obvious way.
For what it's worth, I'm using SYMCLI v7.2 and VMAX1-SE with Enginuity 5785 on both sides.
Thanks!
--
Phil
PedalHarder
465 Posts
0
March 6th, 2011 15:00
With SRDF/A traffic, it's all or nothing at an RDF group. i.e. you cant have some devices in SRDF/A and others not within an RDF group. That's why you can do the symstat -RDFA option. With SRDF that is not SRDF/A mode, that limit is not there, so devices can be in different SRDF states on the same REDF group, hence no symstat at the RDF group for these modes.
You can however look at your throughput with 'symrdf -g query -i n' The -i (interval) when it's running shows throughput numbers at the bottom of the display for the DG in question.
dynamox
2 Intern
2 Intern
•
20.4K Posts
1
March 7th, 2011 08:00
Yes, that’s how much is owned to the other frame
rvbdphil
12 Posts
0
March 7th, 2011 08:00
Thanks Jason. That helps to understand why it would not be so simple to report on SRDF/A in the same way.
Regarding the other command you offered, the output in my case looks like this:
# symrdf -g PHIL_5B query -i 5
Device Group (DG) Name : PHIL_5B
DG's Type : RDF1
DG's Symmetrix ID : 000xxxxxxxxx (Microcode Version: 5875)
Remote Symmetrix ID : 000xxxxxxxxx (Microcode Version: 5875)
RDF (RA) Group Number : 92 (5B)
Source (R1) View Target (R2) View MODES
-------------------------------- ------------------------ ----- ------------
ST LI ST
Standard A N A
Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair
Device Dev E Tracks Tracks S Dev E Tracks Tracks MDAE STATE
-------------------------------- -- ------------------------ ----- ------------
DEV001 01BB RW 0 3083 RW 01BB WD 0 0 C.D. SyncInProg
DEV002 01BC RW 0 2969 RW 01BC WD 0 0 C.D. SyncInProg
DEV003 01BD RW 0 3426 RW 01BD WD 0 0 C.D. SyncInProg
DEV004 01BE RW 0 3220 RW 01BE WD 0 0 C.D. SyncInProg
DEV005 01BF RW 0 2630 RW 01BF WD 0 0 C.D. SyncInProg
DEV006 01C0 RW 0 3809 RW 01C0 WD 0 0 C.D. SyncInProg
DEV007 01C1 RW 0 3745 RW 01C1 WD 0 0 C.D. SyncInProg
DEV008 01C2 RW 0 3238 RW 01C2 WD 0 0 C.D. SyncInProg
DEV009 01C3 RW 0 3496 RW 01C3 WD 0 0 C.D. SyncInProg
DEV010 01C4 RW 0 3030 RW 01C4 WD 0 0 C.D. SyncInProg
Total -------- -------- -------- --------
Track(s) 0 32646 0 0
MB(s) 0.0 2040.4 0.0 0.0
Legend for MODES:
M(ode of Operation) : A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy
D(omino) : X = Enabled, . = Disabled
A(daptive Copy) : D = Disk Mode, W = WP Mode, . = ACp off
(Consistency) E(xempt): X = Enabled, . = Disabled, M = Mixed, - = N/A
The value that I think you're indicating would be Throughput (2040.4 in this case), based on context, I don't think is actually showing Throughput. Based on its position in the output (combined with the fact that my network would be physically incapable of moving data at the rate shown) I sense that this is actually telling me the number of MB of data that's currently out of sync between the R1 and R2. Would that be right?
--
Phil
dynamox
2 Intern
2 Intern
•
20.4K Posts
1
March 7th, 2011 14:00
Phil,
when i run symrdf query -i 10 ..after a couple of iterations, it shows the transfer rate in megabytes. Do you see that field ?
PedalHarder
465 Posts
1
March 7th, 2011 14:00
Note that the synchronisation rate is calculated for the period between each interval in the query. It is not an average. The longer the interval you have in the query, the more realistic the synchronisation rate will be in terns of estimating completion time.
rvbdphil
12 Posts
0
March 7th, 2011 14:00
Ah, right you are! Yes, I see it now. It's interesting because it certainly doesn't show up every time, but it's there sometimes.
Example output for others that may be watching the thread:
Device Group (DG) Name : PHIL_5B
DG's Type : RDF1
DG's Symmetrix ID : 000xxxxxxxxx (Microcode Version: 5875)
Remote Symmetrix ID : 000xxxxxxxxx (Microcode Version: 5875)
RDF (RA) Group Number : 92 (5B)
Source (R1) View Target (R2) View MODES
-------------------------------- ------------------------ ----- ------------
ST LI ST
Standard A N A
Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair
Device Dev E Tracks Tracks S Dev E Tracks Tracks MDAE STATE
-------------------------------- -- ------------------------ ----- ------------
DEV001 01BB RW 0 0 RW 01BB WD 0 0 C.D. Synchronized
DEV002 01BC RW 0 1 RW 01BC WD 0 0 C.D. SyncInProg
DEV003 01BD RW 0 83 RW 01BD WD 0 0 C.D. SyncInProg
DEV004 01BE RW 0 28 RW 01BE WD 0 0 C.D. SyncInProg
DEV005 01BF RW 0 190 RW 01BF WD 0 0 C.D. SyncInProg
DEV006 01C0 RW 0 185 RW 01C0 WD 0 0 C.D. SyncInProg
DEV007 01C1 RW 0 0 RW 01C1 WD 0 0 C.D. Synchronized
DEV008 01C2 RW 0 0 RW 01C2 WD 0 0 C.D. Synchronized
DEV009 01C3 RW 0 0 RW 01C3 WD 0 0 C.D. Synchronized
DEV010 01C4 RW 0 2 RW 01C4 WD 0 0 C.D. SyncInProg
Total -------- -------- -------- --------
Track(s) 0 489 0 0
MB(s) 0.0 30.6 0.0 0.0
Synchronization rate : 3.9 MB/S
Estimated time to completion : 00:00:08
Legend for MODES:
M(ode of Operation) : A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy
D(omino) : X = Enabled, . = Disabled
A(daptive Copy) : D = Disk Mode, W = WP Mode, . = ACp off
(Consistency) E(xempt): X = Enabled, . = Disabled, M = Mixed, - = N/A