Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
Solved!
Go to SolutionNeed help with symstat output
HI,
For below command, Im trying to understand which is the active cycle, Is it Capture/Apply or Transmit/Recieve? Please help to understand
C:\>symstat -i 5 -type cycle -g WIN_HOAPPSQLDB1 -RepType rdfa
SRDF/A Session Cycle Summary Information
Symmetrix ID : XXXXXXXXXX
Timestamp : 16:23:38
Session Cycle Time (sec) Cycle Size
----------- ------------------- -----------------------
RA FLGS Active Last
Device Group Name Grp TAS Cycle# Min Avg Last Switch Active Inact Shared
----------------- --- ---- ------ --- --- ---- ------ ------- ------- -------
WIN_HOAPPSQLDB1 31 1YA 42397 15 15 15 7 2 0 0
Legend for Session Flags:
T(ype) : 1 = RDF1, 2 = RDF2
A(SYNC) : Y = Yes, N = No
S(tatus) : A = Active, I = Inactive, - = N/A
Legend for the Attribute of Cycle Size:
RDF1: Active = Capture Inactive = Transmit
RDF2: Active = Apply Inactive = Receive
ScottBrightwell
9 Posts
1157
0
Posted February 9th, 2014 10:00
Your example is from the source '1' side (RDF-1). Therefore the active cycle is capturing host writes into cache. The inactive cycle refers to the period of transmitting across the link.
If you were doing symstat against the Target Array (RDF-2), 'Active' would refer to writing data to the R2 device , and 'Inactive' would be receiving data from the link.
Thanks Paul, the guide was helpful, But what i really want to understand is ,
When the R1 symm is capturing data for say 15 sec cycle time, Is the transmit happening at the same time for previous capture cycle, or does it happen once Capture is complete.
rawstorage
4 Apprentice
•
423 Posts
1157
0
Posted February 9th, 2014 22:00
Scott is correct here. And for further information the statistics from symstat are also discussed in the array management cli guide https://support.emc.com/docu46983_Solutions_Enabler_Symmetrix_Array_Management_CLI__7.6_Product_Guide.pdf?language=en_US
You have a full explanation on Page 266 on this particular output