- Notes, cautions, and warnings
- Preface
- Introduction to TimeFinder/Clone
- TimeFinder/Clone operations on SGs
- TimeFinder/Clone operations on DGs, and CGs
- TimeFinder/Clone overview
- Create TimeFinder clone copy session
- Activate a TimeFinder clone copy session
- Recreate TimeFinder clone copy device
- Restore data from target device
- Split a clone device pair
- Terminate TimeFinder clone copy session
- Query TimeFinder clone copy session pairs
- Verify TimeFinder clone copy session pair states
- TimeFinder cascaded clone copy session
- Creating multiple clone copies from a standard device
- Using composite groups to manage clone pairs across arrays
- Command options with device files
- TimeFinder State Rules Reference
- SRDF State Rules Reference
Dell Solutions Enabler 10.0.0 TimeFinder/Clone CLI User Guide
TimeFinder cascaded clone configuration rules
When using a clone from a clone target, the following rules apply:
- If the session state is CopyInProg, SyncInProg or RestoreInProg, the -symforce flag is required.
- The Recreate and incremental clone establish commands are allowed only on differential sessions.
- A 2 hop (device A -> target device B -> target device C) cascaded relationship is allowed. Any attempt to establish a 3 hop relationship (D -> C when A -> B -> C or Z -> A when A -> B -> C) will fail. Although circular cascading A -> B -> A is not allowed, devices A and B can have additional multiple targets. For example: A -> B(1) -> C(1) and A -> B(2) and A -> B(3) -> C(2). With two separate clone pairs like A-B and C-D, a create, full establish, or full restore between B and C is allowed.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\