You might be able to try a symdev show on one of the clone source devices, it may show the activate time there.
This is based on the Solutions Enabler Symmetrix TimeFinder Family CLI Product Guide page 251 located at Home > Support > Technical Documentation and Advisories > Software ~ S ~ Documentation > Solutions Enabler > v7.x > General Reference
Message was edited by: MikeMac Added source of information.
bcksrv0_dr/root> symdev -sid 658 show 0181
Device Physical Name : /dev/vx/rdmp/c2t0d11s2
Device Symmetrix Name : 0181
Device Serial ID : 5800181000
Symmetrix ID : 000xxxxxx658
Attached BCV Device : N/A
Attached VDEV TGT Device : N/A
Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5773
Device WWN : 60060480000xxxxxx658533030313831
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0002
Device Block Size : 512
Device Capacity
{
Cylinders : 223296
Tracks : 3349440
512-byte Blocks : 214364160
MegaBytes : 104670
KiloBytes : 107182080
}
Device Configuration : RDF2+R-5 (Meta Head,
Non-Exclusive Access)
Device is WORM Enabled : No
Device is WORM Protected : No
SCSI-3 Persistent Reserve: Disabled
Dynamic Spare Invoked : No
Dynamic RDF Capability : RDF1_OR_RDF2_Capable
STAR Mode : No
STAR Recovery Capability : None
STAR Recovery State : NA
Device Service State : Normal
Device Status : Write Disabled (WD)
Device SA Status : Ready (RW)
Front Director Paths (2):
{
----------------------------------------------------------------------
POWERPATH DIRECTOR PORT LUN
--------- ---------- ---- -------- ---------
PdevName Type Type Num Sts VBUS TID SYMM Host
----------------------------------------------------------------------
/dev/vx/rdmp/c2t0d11s2 N/A FA 08A:0 RW 000 00 00B 00B
/dev/rdsk/c2t0d11s2 N/A FA 08A:0 RW 000 00 00B 00B
}
Meta Configuration : Striped
Meta Stripe Size : 960k (2 Cylinders)
Meta Device Members (12) :
{
----------------------------------------------------------------------
BCV DATA RDF DATA
---------------------------- --------------------------
Sym Cap Std Inv BCV Inv Pair R1 Inv R2 Inv Pair
Dev (MB) Tracks Tracks State Tracks Tracks State
----------------------------------------------------------------------
--> 0181 8723 - - N/A 0 0 Consistent
0182 8723 - - N/A 0 0 Consistent
0183 8723 - - N/A 0 0 Consistent
0184 8723 - - N/A 0 0 Consistent
0185 8723 - - N/A 0 0 Consistent
0186 8723 - - N/A 0 0 Consistent
0187 8723 - - N/A 0 0 Consistent
0188 8723 - - N/A 0 0 Consistent
0189 8723 - - N/A 0 0 Consistent
018A 8723 - - N/A 0 0 Consistent
018B 8723 - - N/A 0 0 Consistent
018C 8723 - - N/A 0 0 Consistent
----------------------------------------------------------------------
104670 - - 0 0
---------------------------------------------------
CLONE DATA
-------------------------------------
Src Cap Src Prot Tgt Pair
Dev (MB) Tracks Dev State
---------------------------------------------------
--> 0181 8723 0 0285 Copied
0182 8723 0 0286 Copied
0183 8723 0 0287 Copied
0184 8723 0 0288 Copied
0185 8723 0 0289 Copied
0186 8723 0 028A Copied
0187 8723 0 028B Copied
0188 8723 0 028C Copied
0189 8723 0 028D Copied
018A 8723 0 028E Copied
018B 8723 0 028F Copied
018C 8723 0 0290 Copied
---------------------------------------------------
104670 0
}
Mirror Set Type : [R1 Remote,RAID-5,RAID-5,N/A]
Mirror Set DA Status : [RW,RW,RW,N/A]
Mirror Set Inv. Tracks : [0,0,0,0]
Back End Disk Director Information
{
Hyper Type : R1 Remote
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
Hyper Type : RAID-5
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
Hyper Type : RAID-5
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
}
RAID-5 Device Information
{
Number of Tracks in a Stripe : 4
Overall Ready State of RAID-5 Device : Ready
Overall WriteProtect State of RAID-5 Device : Enabled
Member Number of the Failing Device : None
Member Number that Invoked the Spare : None
Disk Director (DA) that Owns the Spare : Inv
Copy Direction : N/A
RAID-5 Hyper Devices (3+1):
{
Removed a lot of stuff here...
}
}
Clone Device Information
{
Source (SRC) Device Symmetrix Name : 0181
Source (SRC) Device Group Name : N/A
Source (SRC) Composite Group Name : N/A
Target (TGT) Device Symmetrix Name : 0285
Target (TGT) Device Group Name : N/A
Target (TGT) Composite Group Name : N/A
State of Session (SRC ====> TGT) : Copied
Percent Copied : 100%
Time of Last Clone Action : Tue Apr 28 09:57:47 2009
Clone State Flags : (Copy) (Diff)
Number of Prot. Tracks for SRC Device : 0
Number of Indir Tracks for TGT Device : 0
Number of Changed Tracks for SRC Device: 0
Number of Changed Tracks for TGT Device: 0
}
RDF Information
{
Device Symmetrix Name : 0181
RDF Type : R2
RDF (RA) Group Number : 24 (17)
Remote Device Symmetrix Name : 0321
Remote Symmetrix ID : 000290104771
R2 Device Is Larger Than The R1 Device : False
RDF Pair Configuration : Normal
RDF STAR Mode : False
RDF Mode : Asynchronous
RDF Adaptive Copy : Disabled
RDF Adaptive Copy Write Pending State : N/A
RDF Adaptive Copy Skew (Tracks) : 65535
RDF Device Domino : Disabled
RDF Link Configuration : Fibre
RDF Link Domino : Disabled
Prevent Automatic RDF Link Recovery : Enabled
Prevent RAs Online Upon Power ON : Enabled
Device RDF Status : Ready (RW)
Device SA Status : Ready (RW)
Device RA Status : Write Disabled (WD)
Device Link Status : Ready (RW)
Device Suspend State : N/A
Device Consistency State : Enabled
RDF R2 Not Ready If Invalid : Disabled
Device RDF State : Write Disabled (WD)
Remote Device RDF State : Ready (RW)
RDF Pair State ( R1 <===> R2 ) : Consistent
Number of R1 Invalid Tracks : 0
Number of R2 Invalid Tracks : 0
RDFA Information:
{
Session Number : 23
Cycle Number : 2097
Number of Devices in the Session : 60
Session Status : Active
Session Consistency State : Enabled
Minimum Cycle Time : 00:00:30
Average Cycle Time : 00:00:30
Duration of Last cycle : 00:00:30
Session Priority : 33
Tracks not Committed to the R2 Side: 0
Time that R2 is behind R1 : 00:00:58
R1 Side Percent Cache In Use : 0
R2 Side Percent Cache In Use : 0
Transmit Idle Time : 00:00:00
R1 Side DSE Used Tracks : 0
R2 Side DSE Used Tracks : 0
}
}
Hi, reopening this discussion... something weird is happening to me. Every time I launch a symdev show of the same volume (00303), it returns a different time of the last clone... how is it possible??
I'm trying to dig out the KB solution for this, but basically it's down to when you run the command there can be up to 1 seond reported difference when the relative time is reported due to the time difference between host running cli and the array.
If you run the command a number of times you will see that the frequency is low when this happens. This doesn't mean that the clone time has changed in anyway just the host clock tick ont eh interpretation of the timestamp has an impact on the reporting..
MikeMac1
292 Posts
0
April 27th, 2009 13:00
This is based on the Solutions Enabler Symmetrix TimeFinder Family CLI Product Guide page 251 located at Home > Support > Technical Documentation and Advisories > Software ~ S ~ Documentation > Solutions Enabler > v7.x > General Reference
Message was edited by:
MikeMac
Added source of information.
xe2sdc
2.8K Posts
1
April 28th, 2009 01:00
Dr.diSousa
1 Rookie
1 Rookie
•
95 Posts
0
August 30th, 2018 06:00
Hi, reopening this discussion... something weird is happening to me. Every time I launch a symdev show of the same volume (00303), it returns a different time of the last clone... how is it possible??
Any idea what's happening here?!?
Thanks in advance
Bhaskar1
32 Posts
0
August 30th, 2018 06:00
Correct me if I am wrong , time difference between first and second command is 1 second, right ??
This is a scheduled clone activity. If so then the above o/p is correct .
rawstorage
419 Posts
0
August 30th, 2018 08:00
I'm trying to dig out the KB solution for this, but basically it's down to when you run the command there can be up to 1 seond reported difference when the relative time is reported due to the time difference between host running cli and the array.
If you run the command a number of times you will see that the frequency is low when this happens. This doesn't mean that the clone time has changed in anyway just the host clock tick ont eh interpretation of the timestamp has an impact on the reporting..
Dr.diSousa
1 Rookie
1 Rookie
•
95 Posts
0
September 3rd, 2018 09:00
I think I don't understand your statement....
In another output, we saw another second more of difference...
Dr.diSousa
1 Rookie
1 Rookie
•
95 Posts
0
September 3rd, 2018 09:00
Nope, is more than 1 sec, and the output shows the "Time of last clone action", not how much time ago was the command executed....right?
rawstorage
419 Posts
1
September 4th, 2018 03:00
This is still a 1 second difference it just happens to be the last second in the minute.
Dr.diSousa
1 Rookie
1 Rookie
•
95 Posts
1
September 13th, 2018 01:00
Ok, this could be the issue.
Thanks for your help