Upload
sri-charan
View
223
Download
0
Embed Size (px)
Citation preview
7/29/2019 TimeFInder State Rules
1/30
TimeFinder State Rules Reference 339
A
This appendix lists the TimeFinder control operations that are allowed for devices invarious pair states.
Overview...................................................................................................................... 340 TimeFinder/Clone operations................................................................................... 342
TimeFinder/Snap operations .................................................................................... 354 TimeFinder/Mirror operations ................................................................................. 361
TimeFinder State RulesReference
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
2/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide340
TimeFinder State Rules Reference
Overview
This appendix allows you to determine if the TimeFinder operation you want tocomplete is supported for devices in a particular pair state.
To determine which tables you should view for a particular configuration:
1. Go to the appropriate section for the operation that you want to perform and lookat the basic operations table. For example, if you want to perform aTimeFinder/Clone operation, go to TimeFinder/Clone operations and look atTable 25, Basic TimeFinder/Clone operations. If the operation is supported onthe device in its current pair state, go to the next step.
2. If the device is part of a concurrent copy operation, look at the appropriate tablein the concurrent operations section. A concurrent copy operation occurs whenmultiple copies are made from the same source. These copies can be anycombination of TimeFinder/Clone, TimeFinder/Mirror, and TimeFinder/Snap.
Figure 52 illustrates a concurrent copy operation.
Figure 52 Concurrent copy operation
For example, if you want to complete a TimeFinder/Clone operation on a devicethat is part of a concurrent copy operation in which both a clone and a snap aremade from the same source device, look at Table 28, ConcurrentTimeFinder/Clone operations: Clone and Snap. If the operation is supported on
the device in its current pair state, go to the next step.
3. If the device is part of a cascaded copy operation, look at the appropriate table inthe cascaded operations section. A cascaded copy operation occurs when a deviceis both the source of a copy and the target of a copy, such that the devices are inthe relationship of A > B > C. Examples of cascaded operations include Clone offClone, Snap off Clone, and Snap off BCV.
Figure 52 illustrates a cascaded copy operation.
Figure 53 Cascaded copy operation
A
B
C
A B C
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
3/30
Overview 34
TimeFinder State Rules Referenc
For cascaded operations, you must consider which hop in the cascade you areinterested in. For example, assume that your device is part of a Snap off Cloneoperation in which a device (B) is the target of a clone (A > B) and the source of asnap (B > C).
Figure 52 illustrates this example.
Figure 54 Cascaded copy example (Snap off Clone)
If you are interested in the TimeFinder/Clone hop of the cascade, look at Table 33,Snap off Clone operations: Source to Target, on page 353 of theTimeFinder/Clone Operations section. If you are interested in theTimeFinder/Snap hop of the cascade, look at Table 39, Snap off Cloneoperations: B to VDEV, on page 360 of the TimeFinder/Snap Operations section.
If the operation you want to complete is listed as supported in each of the appropriatetables, then that operation is supported on your device.
A B CClone
Clone source Snap target (VDEV)Clone target/Snap source
Snap
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
4/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide342
TimeFinder State Rules Reference
TimeFinder/Clone operations
This section describes the TimeFinder/Clone control operations that are allowed fordevices in various pair states.
Basic TimeFinder/Clone operations
Figure 55 illustrates the relationship between devices for a basic TimeFinder/Cloneoperation.
Figure 55 Basic TimeFinder/Clone device relationship
In Table 25, Pair state refers to the current state of the source-target pair, andOperation refers to the intended control operation. A check mark indicates that theoperation is allowable for that state.
a. Transient state.
b. Session must be differential.
c. If not already set to this mode.
d. Requires -symmforce (not recommended).
e. Target data will be incomplete.
f. Source data will be incomplete.
Source Target
Table 25 Basic TimeFinder/Clone operations
TimeFinder/CloneSource > Target
Pair state:
TimeFinder/CloneSource > TargetOperation: N
oSession
CreateinProgressa
Created
Recreated
Precopy
CopyinProgress
Copied
CopyonWrite
CopyonAccess
Split
RestoreinProgress
Restored
TerminateinProgressa
Invalid
FAILED
Create
Recreate b
Activate
Full Establish
Incremental Establish
Set Mode Copy c
Set Mode Nocopy c
Set Mode Precopy c
Full Restore b
Incremental Restore b
Split
Terminate d, e d, f
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
5/30
TimeFinder/Clone operations 343
TimeFinder State Rules Referenc
Concurrent TimeFinder/Clone operations
A concurrent copy occurs when a source device is copied to multiple different targets.These copy operations can be any combination of TimeFinder/Clone, TimeFinderSnap, and TimeFinder/Mirror copies.
Concurrent TimeFinder/CloneFigure 56 illustrates the relationship between devices for a TimeFinder/Clone pairingof a source device with two targets.
Figure 56 Concurrent TimeFinder/Clone device relationships
Note: The positions of Target 1 and Target 2 are interchangeable in the illustration above.
Source
arget 1
Target 2
State
Operation
http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
6/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide344
TimeFinder State Rules Reference
In Table 26, Pair state refers to the current state of the Source-Target 1 pair, andOperation refers to the intended control operation on the Source-Target 2 pair. Acheck mark indicates that the operation is allowable for that state.
a. Transient state.
b. Session must be differential.
c. If not already set to this mode.
d. Requires -symmforce (not recommended).
e. Target data will be incomplete.
f. Source data will be incomplete.
Table 26 Concurrent TimeFinder/Clone operations
TimeFinder/Clone
Source > Target 1Pair state:
TimeFinder/CloneSource > Target 2Operation: N
oSession
CreateinProgressa
Created
Recreated
Precopy
CopyinProgress
Copied
CopyonWrite
CopyonAccess
Split
RestoreinProgress
Restored
TerminateinProgressa
Invalid
FAILED
Create
Recreate b
Activate
Full Establish
Incremental Establish
Set Mode Copy c
Set Mode Nocopy c
Set Mode Precopy c
Full Restore b
Incremental Restore b
Split
Terminate d,e d, f
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
7/30
TimeFinder/Clone operations 345
TimeFinder State Rules Referenc
Concurrent TimeFinder/Clone: Clone and Mirror
Figure 57 illustrates the relationship between devices for a concurrent pairing of asource device with a TimeFinder/Clone target and a TimeFinder/Mirror BCV.
Figure 57 Concurrent TimeFinder/Clone device relationships: Clone and Mirror
Note: The positions of Target and BCV are interchangeable in the illustration above.
In Table 27, Pair state refers to the current state of the STD-BCV pair, andOperation refers to the intended control operation on the Source-Target pair. Acheck mark indicates that the operation is allowable for that state.
a. Session must be differential.
b. If not already set to this mode.
Source
Target
BCV
Operatio
n
State
Table 27 Concurrent TimeFinder/Clone operations: Clone and Mirror
TimeFinder/MirrorSTD > BCV
Pair state:
TimeFinder/CloneSource > Target
Operation: NeverEstablished
SynchInProgress
Synchronized
RestoreinProgress
Restored
SplitNoIncremental
SplitInProgress
Split
SplitBeforeSync
SplitBeforeRestore
Create
Recreate a
Activate
Full Establish
Incremental Establish
Set Mode Copy b
Set Mode Nocopy b
Set Mode Precopy b
Full Restore a
Incremental Restore a
Split
Terminate
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
8/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide346
TimeFinder State Rules Reference
Concurrent TimeFinder/Clone: Clone and Snap
Figure 58 illustrates the relationship between devices for a concurrent pairing of asource device with a TimeFinder/Clone target and a TimeFinder/Snap VDEV.
Figure 58 Concurrent TimeFinder/Clone device relationships: Clone and Snap
Note: The positions of Target and VDEV are interchangeable in the illustration above.
In Table 28, Pair state refers to the current state of the Source-VDEV pair, andOperation refers to the intended control operation on the Source-Target pair. Acheck mark indicates that the operation is allowable for that state.
a. Transient state.
b. Session must be differential.
c. If not already set to this mode.
Source
Target
VDEV
Operatio
n
State
Table 28 Concurrent TimeFinder/Clone operations: Clone and Snap
TimeFinder/SnapSource > VDEV
Pair state:
TimeFinder/CloneSource > TargetOperation: N
oSession
CreateinProgressa
Created
Recreated
CopyonWrite
RestoreinProgress
Restored
TerminateinProgressa
Invalid
FAILED
Create
Recreate b
Activate
Full Establish
Incremental Establish
Set Mode Copy c
Set Mode Nocopy c
Set Mode Precopy c
Full Restore b
Incremental Restore b
Split
Terminate
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
9/30
TimeFinder/Clone operations 347
TimeFinder State Rules Referenc
Cascaded TimeFinder/Clone operations
A cascaded copy operation occurs when a device is both the source of a copy and thetarget of a copy, such that the devices are in the relationship of A > B > C.
Cascaded TimeFinder/Clone (Clone off Clone): A > B
Figure 59 illustrates the relationship between devices for a Clone off Clone operationin which source device A is paired with target device B and an additional session usesdevice B as a source paired with target device C.
Figure 59 Clone off Clone device relationship: A > B
Limitations
Cascading with thin devices is supported on Enginuity 5875 and above.
Mixed thick and thin devices are not supported. All devices in a cascaded sessionmust be thick or thin.
Cascaded sessions cannot exceed two hops.
In Table 29, Pair state refers to the current state of the B-C pair, and Operationrefers to the intended control operation on the A-B pair. A check mark indicates thatthe operation is allowable for that state.
A B COperation State
Table 29 Clone off Clone operations: A > B (page 1 of 2)
TimeFinder/Clone
B > C
Pair state:
TimeFinder/Clone
A > B
Operation: NoSession
CreateinProgr
essa
Created
Recreated
Precopy
CopyinProgress
Copied
CopyonWrite
CopyonAcces
s
Split
RestoreinProg
ress
Restored
TerminateinPr
ogressa
Invalid
FAILED
Create d d
Recreate b d d
Activate
Full Establish
Incremental Establish
Set Mode Copy c
Set Mode Nocopy c
Set Mode Precopy b
Full Restore b
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
10/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide348
TimeFinder State Rules Reference
a. Transient state.
b. Session must be differential.
c. If not already set to this mode.
d. Not allowed with the PRECOPY flag.
e. Requires Enginuity 5875 or higher.
Cascaded TimeFinder/Clone (Clone off Clone): B > C
Figure 60 illustrates the relationship between devices for a Clone off Clone operationin which source device A is paired with target device B and an additional session usesdevice B as a source paired with target device C.
Figure 60 Clone off Clone device relationship: B > C
Limitations:
Cascading with thin devices is supported on Enginuity 5875 and above.
Mixed thick and thin devices are not supported. All devices in a cascaded sessionmust be thick or thin.
Cascaded sessions cannot exceed two hops.
Incremental Restore b e
Split
Terminate
Table 29 Clone off Clone operations: A > B (page 2 of 2)
TimeFinder/Clone
B > C
Pair state:
TimeFinder/CloneA > B
Operation: NoSessio
n
CreateinProgressa
Created
Recreated
Precopy
CopyinP
rogress
Copied
CopyonW
rite
CopyonA
ccess
Split
Restorein
Progress
Restored
Terminate
inProgressa
Invalid
FAILED
B CState Operation
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
11/30
TimeFinder/Clone operations 349
TimeFinder State Rules Referenc
In Table 30, In Table 28, Pair state refers to the current state of the A-B pair, andOperation refers to the intended control operation on the B-C pair. A check markindicates that the operation is allowable for that state.
a. Transient state.
b. Session must be differential.
c. If not already set to this mode.
d. Requires the PRECOPY flag.
e. Requires Enginuity 5875 or higher.
Mirror off Clone: Source > STD
Figure 61 illustrates the relationship between devices for a Mirror off Clone operationin which the TimeFinder/Clone source device is paired with a target device and anadditional session uses that device as the STD for TimeFinder/Mirror paired with aBCV.
Figure 61 Mirror off Clone device relationship
Table 30 Clone off Clone operations: B > C
TimeFinder/Clone
A > BPair state:
TimeFinder/Clone
B > C Operation: NoSession
CreateinProgressa
Created
Recreated
Precopy
CopyinProgress
Copied
CopyonWrite
CopyonAccess
Split
RestoreinProgress
Restored
TerminateinProgre
ssa
Invalid
FAILED
Create d
Recreate b d
Activate
Full Establish
Incremental Establish
Set Mode Copy c
Set Mode Nocopy c
Set Mode Precopy c
Full Restore b
Incremental Restore b e e
Split e
Terminate
Source STD BStateOperation
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
12/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide350
TimeFinder State Rules Reference
Limitations:
Thin BCVs are only supported for Enginuity 5875 and above.
Cascading with thin devices is supported on Enginuity 5875 and above.
Mixed thick and thin devices are not supported. All devices in a cascaded sessionmust be thick or thin.
Cascaded sessions cannot exceed two hops.
In Table 31, Pair state refers to the current state of the STD-BCV pair, andOperation refers to the intended control operation on the Source-STD pair. A checkmark indicates that the operation is allowable for that state.
a. Session must be differential.
b. If not already set to this mode.
c. Requires Enginuity 5875 or higher.
Table 31 Mirror off Clone operations: Source > STD
TimeFinder MirrorSTD > BCV
Pair state:
TimeFinder/Clone
Source > STDOperation: N
everEstablished
SynchInProgress
Synchronized
Resto
reinProgress
Resto
red
SplitNoIncremental
SplitInProgress
Split
SplitBeforeSync
SplitBeforeRestore
Create
Recreate a
Activate
Full Establish
Incremental Establish
Set Mode Copy b
Set Mode Nocopy b
Set Mode Precopy b
Full Restore a
Incremental Restore a c
Split
Terminate
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
13/30
TimeFinder/Clone operations 35
TimeFinder State Rules Referenc
Clone off Mirror: BCV > Target
Figure 62 illustrates the relationship between devices for a Clone off Mirror operationin which the TimeFinder/Mirror STD device is paired with a BCV device and anadditional session uses that device as the source for TimeFinder/Clone paired with atarget device.
Figure 62 Clone off Mirror device relationship
Limitations:
Thin BCVs are only supported for Enginuity 5875 and above.
Cascading with thin devices is supported on Enginuity 5875 and above.
Mixed thick and thin devices are not supported. All devices in a cascaded sessionmust be thick or thin.
Cascaded sessions cannot exceed two hops.
TD BCV TargetState Operation
http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
14/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide352
TimeFinder State Rules Reference
In Table 32, Pair state refers to the current state of the STD-BCV pair, andOperation refers to the intended control operation on the BCV-Target pair. A checkmark indicates that the operation is allowable for that state.
a. Session must be differential.
b. If not already set to this mode.
c. Requires Enginuity 5875 or higher.
Snap off Clone: Source > Target
Figure 63 illustrates the relationship between devices for a Snap off Clone operationin which the TimeFinder/Clone source device is paired with a target device and anadditional session uses the target device as the source for TimeFinder/Snap pairedwith a VDEV.
Figure 63 Snap off Clone device relationship
Note: The TimeFinder/Snap session is not considered to be a hop and does not contribute tothe two hop maximum.
Table 32 Clone off Mirror operations: BCV > Target
TimeFinder/Mirror
STD > BCVPair state:
TimeFinder/CloneBCV > TargetOperation: N
everEstablished
SynchInProgress
Synchronized
RestoreinProgress
Restored
SplitNoIncremental
SplitInProgress
Split
SplitBeforeSync
SplitBeforeRestore
Create
Recreate a
Activate
Full Establish
Incremental Establish
Set Mode Copy b
Set Mode Nocopy b
Set Mode Precopy b
Full Restore a
Incremental Restore a c c
Split c
Terminate
Source TargetStateOperation
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
15/30
TimeFinder/Clone operations 353
TimeFinder State Rules Referenc
In Table 33, Pair state refers to the current state of the Target-VDEV pair, andOperation refers to the intended control operation on the Source-Target pair. Acheck mark indicates that the operation is allowable for that state.
a. Transient state.
b. Session must be differential.
c. If not already set to this mode.
d. Not allowed with the PRECOPY flag.
e. Requires Enginuity 5875 or higher.
Table 33 Snap off Clone operations: Source to Target
TimeFinder/Snap
Target > VDEVPair state:
TimeFinder/CloneSource > TargetOperation: N
oSession
CreateinProgressa
Created
Recreated
CopyonWrite
RestoreinProgress
Restored
TerminateinProgressa
Invalid
FAILED
Create d d
Recreate b d d
Activate
Full Establish
Incremental Establish
Set Mode Copy c
Set Mode Nocopy c
Set Mode Precopy c
Full Restore b
Incremental Restore b e
Split
Terminate
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
16/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide354
TimeFinder State Rules Reference
TimeFinder/Snap operations
This section describes the TimeFinder/Snap control operations that are allowed fordevices in various pair states.
Basic TimeFinder/Snap Operations
Figure 64 illustrates the relationship between devices for a basic TimeFinder/Cloneoperation.
Figure 64 Basic snap device relationship
In Table 34, Pair state refers to the current state of the Source-VDEV pair, andOperation refers to the intended control operation. A check mark indicates that theoperation is allowable for that state.
a. Transient state.
b. Requires Enginuity 5774 or above.c. The restore to a third device must not be related to any session associated with the TimeFinder/Snap source device. The
third device must be the same thick or thin configuration as the TimeFinder/Snap source device.
d. Requires -symforce (not recommended).
Source VDEV
Table 34 Basic TimeFinder/Snap operations
TimeFinder/CloneSource > VDEV
Pair state:
TimeFinder/CloneSource > VDEVOperation: N
oSession
CreateinProgressa
Created
Recreated
CopyonWrite
RestoreinProgress
Restored
TerminateinProgressa
Invalid
FAILED
Create
Create - duplicate
Duplicate
Recreate b
Activate
Full Restore c
Incremental Restore
Terminate d
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
17/30
TimeFinder/Snap operations 355
TimeFinder State Rules Referenc
Concurrent TimeFinder/Snap operations
A concurrent copy occurs when a source device is copied to multiple different targets.These copy operations can be any combination of TimeFinder/Clone, TimeFinderSnap, and TimeFinder/Mirror copies.
ConcurrentTimeFinder/Snap Figure 65 illustrates the relationship between devices for a TimeFinder/Clone pairingof a source device with two targets.
Figure 65 Concurrent TimeFinder/Snap device relationships
Note:
The positions of VDEV 1 and VDEV 2 are interchangeable in the illustration above.
In Table 35, Pair state refers to the current state of the Source-VDEV 1pair, andOperation refers to the intended control operation on the Source-VDEV 2 pair. Acheck mark indicates that the operation is allowable for that state.
a. Transient state.
b. Requires Enginuity 5774 or above.
c. The restore to a third device must not be related to any session associated with the TimeFinder/Snap source device. Thethird device must be the same thick or thin configuration as the TimeFinder/Snap source device.
Source
VDEV 1
VDEV 2VDEV 2
State
Operation
Table 35 Concurrent TimeFinder/Snap operations
TimeFinder/SnapSource > VDEV 1
Pair state:
TimeFinder/Snap
Source > VDEV 2Operation: N
oSession
CreateinProgressa
Created
Recreated
Copy
onWrite
RestoreinProgressa
Restored
Term
inateinProgress
Invalid
FAILED
Create
Create - duplicate
Duplicate
Recreate b
Activate
Full Restore c
Incremental Restore
Terminate
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
18/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide356
TimeFinder State Rules Reference
Concurrent TimeFinder/Snap: Snap and Mirror
Figure 66 illustrates the relationship between devices for a concurrent pairing of asource device with a TimeFinder/Snap VDEV and a TimeFinder/Mirror BCV.
Figure 66 Concurrent TimeFinder/Snap device relationships: Snap and Mirror
Note: The positions of VDEV and BCV are interchangeable in the illustration above.
In Table 36, Pair state refers to the current state of the STD-BCV pair, andOperation refers to the intended control operation on the Source-VDEV pair. Acheck mark indicates that the operation is allowable for that state.
a. Requires Enginuity 5774 or above.
b. The restore to a third device must not be related to any session associated with the TimeFinder/Snap source device. Thethird device must be the same thick or thin configuration as the TimeFinder/Snap source device.
Source
VDEV
BCV
Operatio
n
State
Table 36 Concurrent TimeFinder/Snap operations: Snap and Mirror
TimeFinder/MirrorSTD > BCV
Pair state:
TimeFinder/SnapSource > VDEV
Operation: NeverEstablished
SynchInProgress
Synchronized
RestoreinProgress
Restored
SplitNoIncremental
SplitInProgress
Split
SplitBeforeSync
SplitBeforeRestore
Create
Create - duplicate
Duplicate
Recreate a
Activate
Full Restore b
Incremental Restore
Terminate
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
19/30
TimeFinder/Snap operations 357
TimeFinder State Rules Referenc
Concurrent TimeFinder/Snap: Snap and Clone
Figure 67 illustrates the relationship between devices for a concurrent pairing of asource device with a TimeFinder/Snap VDEV and a TimeFinder/Clone Target.
Figure 67 Concurrent TimeFinder/Snap device relationships: Snap and Clone
Note: The positions of Target and VDEV are interchangeable in the illustration above.
In Table 37, Pair state refers to the current state of the Source-Target pair, andOperation refers to the intended control operation on the Source-VDEV pair. Acheck mark indicates that the operation is allowable for that state.
a. Transient state.
b. Requires Enginuity 5774 or above.
c. The restore to a third device must not be related to any session associated with the TimeFinder/Snap source device. Thethird device must be the same thick or thin configuration as the TimeFinder/Snap source device.
Source
VDEV
arge
Operatio
n
State
Table 37 Concurrent TimeFinder/Snap operations: Snap and Clone
TimeFinder/CloneSource > Target
Pair state:
TimeFinder SnapSource > VDEVOperation: N
oSession
CreateinProgressa
Created
Recreated
Precopy
CopyinProgress
Copied
CopyonWrite
CopyonAccess
Split
RestoreinProgress
Restored
TerminateinProgressa
Invalid
FAILED
Create
Create - duplicate
Duplicate
Recreate b
Activate
Full Restore c
Incremental Restore
Terminate
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
20/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide358
TimeFinder State Rules Reference
Cascaded TimeFinder/Snap operations
A cascaded copy operation occurs when a device is both the source of a copy and thetarget of a copy, such that the devices are in the relationship of A > B > C.
Snap off Mirror: BCV > VDEV
Figure 68 illustrates the relationship between devices for a Snap off Mirror operationin which the TimeFinder/Mirror STD device is paired with a BCV device and anadditional session uses that device as the source for TimeFinder/Snap paired with aVDEV.
Figure 68 Snap off Mirror device relationship
Limitations:
Cascading with thin devices is supported on Enginuity 5875 and above.
Mixed thick and thin devices are not supported. All devices in a cascaded sessionmust be thick or thin.
Cascaded sessions cannot exceed two hops.
The TimeFinder/Snap session is not considered to be a hop and does notcontribute to the two hop maximum. Therefore, the STD > BCV pairing could bepreceded by a clone session such that the final cascade is Clone Source > STD >BCV > VDEV.
STD BCV VDEVState Operation
http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
21/30
TimeFinder/Snap operations 359
TimeFinder State Rules Referenc
In Table 38, Pair state refers to the current state of the STD-BCV pair, andOperation refers to the intended control operation on the BCV-VDEV pair. A checkmark indicates that the operation is allowable for that state.
a. Requires Enginuity 5774 or above.
b. The restore to a third device must not be related to any session associated with the TimeFinder/Snap source device. Thethird device must be the same thick or thin configuration as the TimeFinder/Snap source device.
c. Requires Enginuity 5775 or higher.
Snap off Clone: B > VDEV
Figure 69 illustrates the relationship between devices for a Snap off Clone operationin which the TimeFinder/Clone source device is paired with a target device and anadditional session uses the target device as the source for TimeFinder/Snap pairedwith a VDEV.
Figure 69 Snap off Clone device relationship
Limitations:
Cascading with thin devices is supported on Enginuity 5875 and above.
Mixed thick and thin devices are not supported. All devices in a cascaded sessionmust be thick or thin.
Cascaded sessions cannot exceed two hops.
The TimeFinder/Snap session is not considered to be a hop and does notcontribute to the two hop maximum. Therefore, the STD > BCV pairing could bepreceded by a clone session such that the final cascade is Clone Source > STD >BCV > VDEV.
Table 38 Snap off Mirror operations: BCV > VDEV
TimeFinder Mirror
STD > BCVPair State:
TimeFinder/SnapBCV > VDEVOperation: N
everEstablished
SynchInProgress
Synchronized
RestoreinProgress
Restored
SplitNoIncremental
SplitInProgress
Split
SplitBeforeSync
SplitBeforeRestore
Create
Create - duplicate
Duplicate
Recreate a
Activate
Full Restore b
Incremental Restore c
Terminate
A B VDEVState Operation
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
22/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide360
TimeFinder State Rules Reference
In Table 39, Pair state refers to the current state of the A-B pair, and Operationrefers to the intended control operation on the B-VDEVpair. A check mark indicatesthat the operation is allowable for that state.
a. Transient State
b. Requires Enginuity 5774 or above.
c. The restore to a third device must not be related to any session associated with the TimeFinder/Snap source device. Thethird device must be the same thick or thin configuration as the TimeFinder/Snap source device.
d. Requires Enginuity 5775 or higher.
Table 39 Snap off Clone operations: B to VDEV
TimeFinder/CloneA > B
Pair state:
TimeFinder/SnapB > VDEV
Operation: NoSession
CreateinProgressa
Created
Recreated
Precopy
CopyinProgress
Copied
CopyonWrite
CopyonAccess
Split
RestoreinProgress
Restored
TerminateinProgressa
Invalid
FAILED
Create
Create - duplicate
Duplicate
Recreate b
Activate
Full Restore c
Incremental Restore d d d
Terminate
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
23/30
TimeFinder/Mirror operations 36
TimeFinder State Rules Referenc
TimeFinder/Mirror operations
This section describes the TimeFinder/Mirror control operations that are allowed fordevices in various pair states.
Basic TimeFinder/Mirror operations
Figure 70 illustrates the relationship between devices for a basic TimeFinder/Mirroroperation.
Figure 70 Basic TimeFinder/Mirror device relationship
Limitations:
With Enginuity 5874 and higher, all TimeFinder/Mirror operations are done with
TimeFinder/Clone Emulation. With Enginuity 5874 and lower, the default modeis native TimeFinder/Mirror, and TimeFinder/Clone Emulation is a selectableoption.
RAID5 and RAID6 BCVs automatically use TimeFinder/Clone Emulation.
Thin BCVs are supported with Enginuity 5875 and higher.
In Table 40, Pair state refers to the current state of the STD-BCV pair, andOperation refers to the intended control operation. A check mark indicates that theoperation is allowable for that state.
a. Requires -symmforce (not recommended)
b. Results in the Split Before Sync state, which indicates that the BCV data is not complete.
c. Results in the Split Before Restore state, which indicates that the STD data in not complete.
STD BCV
Table 40 Basic TimeFinder/Mirror operations
TimeFinder/Mirror
STD > BCVPair state:
TimeFinder MirrorSTD > BCVOperation: N
everEstablished
SynchInProgres
s
Synchronized
RestoreinProgress
Restored
SplitNoIncremental
SplitInProgress
Split
SplitBeforeSync
SplitBeforeRestore
Full Establish
Incremental Establish
Split a, b a, c
Full Restore
Incremental Restore
Cancel
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
24/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide362
TimeFinder State Rules Reference
Concurrent TimeFinder/Mirror operations
A concurrent copy occurs when a source device is copied to multiple different targets.These copy operations can be any combination of TimeFinder/Clone, TimeFinderSnap, and TimeFinder/Mirror copies.
Concurrent TimeFinder/MirrorFigure 71 illustrates the relationship between devices for a TimeFinder/Mirrorpairing of a STD device with two BCVs.
Figure 71 Concurrent TimeFinder/Mirror device relationships
Note: The positions of BCV 1 and BCV 2 are interchangeable in the illustration above.
Limitations:
With Enginuity 5874 and higher, all TimeFinder/Mirror operations are done withTimeFinder/Clone Emulation. With Enginuity 5874 and lower, the default modeis native TimeFinder/Mirror, and TimeFinder/Clone Emulation is a selectableoption.
RAID5 and RAID6 BCVs automatically use TimeFinder/Clone Emulation.
Thin BCVs are supported with Enginuity 5875 and higher.
In Table 41, Pair state refers to the current state of the STD-BCV 1 pair, and
Operation refers to the intended control operation on the STD-BCV 2 pair. A checkmark indicates that the operation is allowable for that state.
STD
BCV 1
BCV 1
State
Operation
Table 41 Concurrent TimeFinder/Mirror operations
TimeFinder/MirrorSTD > BCV 1
Pair state:
TimeFinder/MirrorSTD > BCV 2Operation: N
everEstablished
SynchInProgress
Synchronized
RestoreinProgress
Restored
SplitNoIncremental
SplitInProgress
Split
SplitBeforeSync
SplitBeforeRestore
Full Establish
Incremental Establish
Split
Full Restore
Incremental Restore
Cancel
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
25/30
TimeFinder/Mirror operations 363
TimeFinder State Rules Referenc
Concurrent TimeFinder/Mirror: Mirror and Clone
Figure 72 illustrates the relationship between devices for a concurrent pairing of aSTD device with a TimeFinder/Mirror BCV and a TimeFinder/Clone target.
Figure 72 Concurrent TimeFinder/Mirror device relationships: Mirror and Clone
Note: The positions of BCV and Target are interchangeable in the illustration above.
Limitations:
With Enginuity 5874 and higher, all TimeFinder/Mirror operations are done withTimeFinder/Clone Emulation. With Enginuity 5874 and lower, the default mode
is native TimeFinder/Mirror, and TimeFinder/Clone Emulation is a selectableoption.
RAID5 and RAID6 BCVs automatically use TimeFinder/Clone Emulation.
Thin BCVs are supported with Enginuity 5875 and higher.
In Table 42, Pair state refers to the current state of the STD-Target pair, andOperation refers to the intended control operation on the STD-BCV pair. A checkmark indicates that the operation is allowable for that state.
a. Transient state.
STD
BCV
arge
Operatio
n
State
Table 42 Concurrent TimeFinder/Mirror operations: Mirror and Clone
TimeFinder/CloneSTD > Target
Pair state:
TimeFinder/MirrorSTD > BCVOperation: N
oSession
CreateinProgressa
Created
Recreated
Precopy
CopyinProgress
Copied
CopyonWrite
CopyonAccess
Split
RestoreinProgress
Restored
TerminateinProgressa
Invalid
FAILED
Full Establish
Incremental Establish
Split
Full Restore
Incremental Restore
Cancel
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
26/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide364
TimeFinder State Rules Reference
Concurrent TimeFinder/Mirror: Mirror and Snap
Figure 73 illustrates the relationship between devices for a concurrent pairing of aSTD device with a TimeFinder/Mirror BCV and a TimeFinder/Snap VDEV.
Figure 73 Concurrent TimeFinder/Mirror device relationships: Mirror and Snap
Note: The positions of BCV and VDEV are interchangeable in the illustration above.
Limitations:
With Enginuity 5874 and higher, all TimeFinder/Mirror operations are done withTimeFinder/Clone Emulation. With Enginuity 5874 and lower, the default modeis native TimeFinder/Mirror, and TimeFinder/Clone Emulation is a selectableoption.
RAID5 and RAID6 BCVs automatically use TimeFinder/Clone Emulation.
Thin BCVs are supported with Enginuity 5875 and higher.
In Table 43, Pair state refers to the current state of the STD-VDEV pair, andOperation refers to the intended control operation on the STD-BCV pair. A checkmark indicates that the operation is allowable for that state.
a. Transient state.
STD
BCV
Operatio
n
State
Table 43 Concurrent TimeFinder/Mirror operations: Mirror and Snap
TimeFinder/SnapSTD > VDEV
Pair state:
TimeFinder/MirrorSTD > BCVOperation: N
oSession
CreateinProgress
a
Created
Recreated
CopyonWrite
RestoreinProgres
s
Restored
TerminateinProgr
essa
Invalid
FAILED
Full Establish
Incremental Establish
Split
Full Restore
Incremental Restore
Cancel
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
27/30
TimeFinder/Mirror operations 365
TimeFinder State Rules Referenc
Cascaded TimeFinder/Clone operations
A cascaded copy operation occurs when a device is both the source of a copy and thetarget of a copy, such that the devices are in the relationship of A > B > C.
Clone off Mirror: STD > BCV
Figure 74 illustrates the relationship between devices for a Clone off Mirror operationin which the TimeFinder/Mirror STD device is paired with a BCV and an additionalsession uses that device as the source for TimeFinder/Clone paired with a targetdevice.
Figure 74 Clone off Mirror device relationship
Limitations:
With Enginuity 5874 and higher, all TimeFinder/Mirror operations are done withTimeFinder/Clone Emulation. With Enginuity 5874 and lower, the default modeis native TimeFinder/Mirror, and TimeFinder/Clone Emulation is a selectableoption.
RAID5 and RAID6 BCVs automatically use TimeFinder/Clone Emulation.
Thin BCVs are supported with Enginuity 5875 and higher.
Mixed thick and thin devices are not supported. All devices in a cascaded sessionmust be thick or thin.
Cascaded sessions cannot exceed two hops.
In Table 44, Pair state refers to the current state of the BCV-Target pair, andOperation refers to the intended control operation on the STD-BCV pair. A check
mark indicates that the operation is allowable for that state.
a. Transient state.
STD BCV TargetStateOperation
Table 44 Clone off Mirror operations: STD > BCV
TimeFinder/CloneBCV > Target
Pair state:
TimeFinder/MirrorSTD > BCVOperation: N
oSession
CreateinProgressa
Created
Recreated
Precopy
CopyinProgress
Copied
CopyonWrite
CopyonAccess
Split
RestoreinProgress
Restored
TerminateinProgressa
Invalid
FAILED
Full Establish
Incremental Establish
Split
Full Restore
Incremental Restore
Cancel
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
28/30
EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 7.3 Product Guide366
TimeFinder State Rules Reference
Mirror off Clone: STD > BCV
Figure 75 illustrates the relationship between devices for a Mirror off Clone operationin which the TimeFinder/Clone source device is paired with a target device and anadditional session uses that device as the STD for TimeFinder/Mirror paired with aBCV.
Figure 75 Mirror off Clone device relationship
Limitations:
With Enginuity 5874 and higher, all TimeFinder/Mirror operations are done withTimeFinder/Clone Emulation. With Enginuity 5874 and lower, the default modeis native TimeFinder/Mirror, and TimeFinder/Clone Emulation is a selectableoption.
RAID5 and RAID6 BCVs automatically use TimeFinder/Clone Emulation.
Thin BCVs are supported with Enginuity 5875 and higher. Mixed thick and thin devices are not supported. All devices in a cascaded session
must be thick or thin.
Cascaded sessions cannot exceed two hops.
In Table 45, Pair state refers to the current state of the Source-STD pair, andOperation refers to the intended control operation on the STD-BCV pair. A checkmark indicates that the operation is allowable for that state.
a. Transient state.
Source STD BCVState Operation
Table 45 Mirror off Clone operations STD > BCV
TimeFinder/CloneSource > STD
Pair state:
TimeFinder/MirrorSTD > BCVOperation: N
oSession
CreateinProgres
sa
Created
Recreated
Precopy
CopyinProgress
Copied
CopyonWrite
CopyonAccess
Split
RestoreinProgre
ss
Restored
TerminateinProg
ressa
Invalid
FAILED
Full Establish
Incremental Establish
Split
Full Restore
Incremental Restore
Cancel
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
29/30
TimeFinder/Mirror operations 367
TimeFinder State Rules Referenc
Snap off Mirror: STD > BCV
Figure 76 illustrates the relationship between devices for a Snap off Mirror operationin which the TimeFinder/Mirror STD device is paired with a BCV device and anadditional session uses the BCV device as the source for TimeFinder/Snap pairedwith a VDEV.
Figure 76 Snap off Mirror device relationship
Limitations:
With Enginuity 5874 and higher, all TimeFinder/Mirror operations are done withTimeFinder/Clone Emulation. With Enginuity 5874 and lower, the default modeis native TimeFinder/Mirror, and TimeFinder/Clone Emulation is a selectableoption.
RAID5 and RAID6 BCVs automatically use TimeFinder/Clone Emulation.
Thin BCVs are supported with Enginuity 5875 and higher.
Mixed thick and thin devices are not supported. All devices in a cascaded sessionmust be thick or thin.
Cascaded sessions cannot exceed two hops.
In Table 46, Pair state refers to the current state of the BCV-VDEV pair, andOperation refers to the intended control operation on the STD-BCV pair. A checkmark indicates that the operation is allowable for that state.
a. Transient state.
STD BCV VDEVStateOperation
Table 46 Snap off Mirror operations: STD to BCV
TimeFinder/SnapBCV > VDEV
Pair state:
Source-->Target
TimeFinder/MirrorSTD > BCV Operation: N
oSession
CreateinProgressa
Created
Recreated
CopyonWrite
RestoreinProgress
Restored
TerminateinProgressa
Invalid
FAILED
Full Establish
Incremental Establish
Split
Full Restore
Incremental Restore
Cancel
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-7/29/2019 TimeFInder State Rules
30/30
TimeFinder State Rules Reference