DELL Solutions Enabler 10.0.0 TimeFinder Clone User Guide

Technologies
Dell Solutions Enabler 10.0.0 TimeFinder/ **Clone
CLI User Guide 10.0.0
August 2022
Rev. 02
**

Solutions Enabler 10.0.0 TimeFinder Clone

Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
© 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.
Preface
As part of an effort to improve its product lines, Dell Technologies periodically releases revisions of its software and hardware.
Functions that are described in this document may not be supported by all versions of the software or hardware. The product release notes provide the most up-to-date information about product features.
Contact your Dell Technologies representative if a product does not function properly or does not function as described in this document.
NOTE: This document was accurate at publication time. New versions of this document might be released on Dell Technologies Online Support (https://www.dell.com/support/home). Check to ensure that you are using the latest version of this document.
Purpose
This document is part of the Dell Solutions Enabler documentation set, and describes how to use TimeFinder Mirror, Clone, Snap, and VP Snap.
Audience
This document is intended for use by advanced command-line users and script programmers to manage various types of control operations on arrays and devices using the SYMCLI commands of the Dell Solutions Enabler software.
Related documentation
The following documents provide additional Solutions Enabler information:

Dell Solutions Enabler Release Notes| Describes new features and any known limitations.
---|---
Dell Solutions Enabler
Installation and Configuration Guide| Provides host-specific installation instructions.
Dell Solutions Enabler CLI Reference Guide| Documents the SYMCLI commands, daemons, error codes and option file parameters provided with the Solutions Enabler man pages.
Dell Solutions Enabler Array Controls and Management CLI User Guide| Describes how to configure array control, management, and migration operations using SYMCLI commands for arrays running HYPERMAX OS and PowerMaxOS.
Dell Solutions Enabler SRDF Family CLI User Guide| Describes how to configure and manage SRDF environments using SYMCLI commands.
Dell Solutions Enabler SRDF Family State Tables Guide| Describes the applicable pair states for various SRDF operations.
SRDF Interfamily Connectivity Information| Defines the versions of PowerMaxOS, HYPERMAX OS and Enginuity that can make up valid SRDF replication and SRDF/Metro configurations, and can participate in Non-Disruptive Migration (NDM).
Dell SRDF Introduction| Provides an overview of SRDF, its uses, configurations, and terminology.
Dell Solutions Enabler TimeFinder SnapVX CLI User Guide| Describes how to configure and manage TimeFinder SnapVX environments using SYMCLI commands.
Dell Solutions EnablerTimeFinder Clone CLI User Guide| Describes how to configure and manage TimeFinder Clone environments for HYPERMAX OS and PowerMaxOS using SYMCLI commands.
Dell SRDF/ Metro vWitness Configuration Guide| Describes how to install, configure, and manage SRDF/Metro using vWitness.
Dell Events and Alerts for PowerMax and HYPERMAX User Guide| Documents the SYMAPI daemon messages, asynchronous errors and message events, SYMCLI return codes, and how to configure event logging.

Typographical conventions
EMC uses the following style conventions in this document:
Table 1. Typographical conventions used in this content

Bold| Used for names of interface elements
Examples: Names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user selects or clicks)
---|---
Italic| Used for full titles of publications referenced in text
Monospace| Used for:
● System code
● System output, such as an error message or script
● Pathnames, filenames, prompts, and syntax
● Commands and options
Monospace italic| Used for variables
Monospace bold| Used for user input
[ ]| Square brackets enclose optional values.
|| A vertical bar indicates alternate selections. The bar means “or”.
{ }| Braces enclose content that the user must specify, such as x or y or z.
…| Ellipses indicate nonessential information that is omitted from the example.

Where to get help
Dell support, product, and licensing information can be obtained as follows:
NOTE: To open a service request through Dell Online Support, you must have a valid support agreement. Contact your Dell sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Product information| For documentation, release notes, software updates, or information about Dell Technologies products, go to Dell Technologies Online Support at https://www.dell.com/support/home.
---|---
Technical supporte-Licensing support| Dell Technologies offers various support options.
● Support by Product: Dell Technologies offers consolidated, product-specific information through the Dell Technologies Online Support site.
The Support by Product web pages: https://www.dell.com/support/home, select Product Support.
These pages offer quick links to Documentation, White Papers, Advisories (such as frequently used Knowledgebase articles) and Downloads. They also offer dynamic content such as presentations, discussion, relevant Customer Support Forum entries, and a link to Dell Technologies Live Chat.
● Dell Technologies Live Chat: Open a Chat or instant message session with a Dell Technologies Support Engineer.
To activate your entitlements and obtain your license files, go to the Service Center on Dell
Technologies Online Support (https://www.dell.com/support/home). Follow the directions on your License Authorization Code (LAC) letter that is emailed to you.
● Expected functionality may be unavailable because it is not licensed. For help with missing or incorrect entitlements after activation, contact your Dell Technologies Account Representative or Authorized Reseller.
● For help with any errors applying license files through Solutions Enabler, contact the Dell Technologies Customer Support Center.
● Contact the Dell Technologies worldwide Licensing team if you are missing the LAC letter or require further instructions on activating your licenses through the Online Support site.
○ licensing@dell.com
○ North America, Latin America, APJK, Australia, New Zealand: SVC4EMC (800-782-4362) and follow the voice prompts.
○ EMEA: +353 (0) 21 4879862 and follow the voice prompts.

Your comments
Your suggestions help improve the accuracy, organization, and overall quality of the documentation. Send your comments and feedback to: powermaxcontentfeedback@dell.com
Revision history
The following table presents the revision history of this document:
Table 2. Revision history

Introduction to TimeFinder/Clone

This chapter introduces the Dell Solutions Enabler TimeFinder/Clone and the SYMCLI command for this product.
Topics:

• Introduction to TimeFinder Family

Introduction to TimeFinder Family
Dell TimeFinder/Clone allows nondisruptive creation and management of point- in-time copies of data, enabling simultaneous action of business tasks that were previously sequential. TimeFinder creates and manages point-in-time copies of critical data that can be used for backups, decision support, and to refresh data warehouse, test, and development environments. The ability to access source data during the TimeFinder copy operation eliminates the backup window and provides benefits such as accelerated upgrades and high availability. TimeFinder can also shorten the maintenance window, minimize infrastructure costs, and improve service levels.
TimeFinder/Clone overview
TimeFinder/Clone uses the symclone CLI to create a point-in-time copy.
The TimeFinder/Clone operations are establish, or ( create , activate , recreate), restore , and terminate.
NOTE: For SGs, establish is the only operation for arrays running PowerMaxOS. Create/Activate/Recreate actions are not allowed.

TimeFinder/Clone command symclone is used to perform the following operations:

• Creates a copy session for making multiple data copies between a source SG or device and target SGs or devices.
  NOTE: For SGs, establishis the only operation for arrays running PowerMaxOS. Create/Activate/Recreate actions are not allowed.

• Creates and activates a copy session

• Activates a copy session to make data instantly accessible to multiple target hosts.

• Copies (incrementally) all subsequent changes made to a source SG or device to a target SG or device, after a clone session is fully copied.

• Restores data from a target SG or device back to a source SG or device or to another SG or device.

•  Terminates a copy session to remove holds on target SGs or devices and delete device pair information from the array.

• Queries information about the state of multiple copy sessions.

•  Verifies the state for selected devices.

• Lists all clone sessions that have been created on the array.
  NOTE: The Dell Solutions Enabler CLI Command Reference provides complete details about command syntax.

TimeFinder/Clone operations on SGs

This chapter describes TimeFinder/Clone operations on SGs.
NOTE: TimeFinder/Clone operations on SGs are only supported on arrays running PowerMaxOS.
Topics:

• TimeFinder/Clone of SGs overview
• Clone an SG
• Restore data from a target SG
• Terminate clone copy session for SGs

TimeFinder/Clone of SGs overview
For a high-level overview of TimeFinder/Clone functionality for SGs, refer to the Dell PowerMax 2500 and 8500: TimeFinder SnapVX and Clone whitepaper.
TimeFinder/Clone operations are performed using the s y m c l o n e command to create clone copies of a source SG on one or multiple target SGs.
A single source SG can have up to 256 clone copy sessions.
NOTE: For SGs, establish is the only operation for arrays running PowerMaxOS. Create/Activate/Recreate actions are not allowed.
Clone an SG
Description
Use the symclone establish command to create, and then immediately activate a copy session.
Examples
To clone the SG exampleSG, enter:
symclone – sid 118 – sgexampleSG establish – tsg targetExampleSG
NOTE: The symclone establish command sets the target device to Not Ready for a short period time. If using a file system, unmount the target host before performing the establish command.
Restore data from a target SG
Use the symclone restore command to restore an SG to the target SG. The restore operation requires that the session is differential and the device pair is in the Copied state.
Examples
To fully restore the SG backupSG to the target SG of ficeSG, enter:
symclone -sid 118 -sg backupSG restore -tsag officeSG
Terminate clone copy session for SGs
Description
Terminating a copy session deletes the pairing information in the array and removes any hold on the target SG. Terminating a session while the SGs are in the CopyinProg state causes the session to end. If the application has not finished accessing all of the data, the target copy is not a full copy.
The symclone terminate command is allowed for all clone pair states.
Examples
To terminate the clone session for SG officeSG, enter:
symclone -sid 118 -sg officeSG terminate -tsg backupSG
NOTE: A created and activated copy session may be terminated, but the data on the target SG is not valid unless the device state is COPIED.
If the state is CopyinProg, then apply the -symforce option to terminate the session. This eaves the target copy as an incomplete copy.
If the -not_ready option is applied to the copy session, Solutions Enabler leaves the target SGs in their prior Ready or NotReady state at the completion of the terminate operation. If the -not_ready option is not applied to the copy session, Solutions Enabler leaves the target SGs in the Ready state at the completion of the terminate, regardless of their state prior to the terminate operation.

TimeFinder/Clone operations on DGs, and CGs

This chapter describes how to perform TimeFinder/Clone operations on DGs, CGs.
NOTE: TimeFinder/Clone operations on device logical names (LdevName, PdevName and SymDevName) are not allowed in input with CGs and/or DGs on arrays running PowerMaxOS 10 (6079) and higher.
Topics :

• 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/Clone overview
For a high-level overview of TimeFinder/Clone functionality, refer to the Dell EMC Symmetrix TimeFinder Product Guide.
TimeFinder/Clone operations are performed using the s y m c l o n e command to create clone copies of a source device on one or multiple target devices.
A single source device can have up to 256 clone copy sessions.
Create TimeFinder clone copy session
Description
The symclone create commands defines the clone copy session requirements and sets the track protection bitmap on the source device to detect which tracks are being accessed by the target host or written to by the source host.
Data begins copying in the background when the clone session is activated and a full copy will become available to the host.
While background copying, the state of the device pair is CopyInProgress. When the operation completes, the state goes to Copied. However, once the session is activated, the data is available immediately to the target host.
Examples
To create a clone copy session between source device and target device in group ProdDB, enter:
symclone- g ProdDB create
Rules and restrictions
The following rules and restrictions apply to a clone copy:

• The target device is made Not Ready to its host and placed on hold status for clone copy session activity. This prevents other control operations from using the device.
•  The device pair state transitions from Create In Progress to Created when complete.
• The clone copy does not become accessible to its host until the copy session is activated. Activate a TimeFinder clone copy session contains greater detail.
• A device pair cannot be verified that it is in the Create In Progress state. After the copy session completes, issue a symcloneverify -created command to verify that the clone pair is successfully created.
• If a copy session is created and not activated, it can be terminated. However, the data on the target device should be considered invalid.

Create concurrent target device for each source device in a group
Description
When working with a composite or device group, use the symclone create or symclone establish command with the option – concurrent option to pair an additional target device with each source device in the group. When the copy session is created, an additional target device is paired with each source device in the group. For example, if there are two target devices paired with each source device in the group before creating the session, after the session is created there will be three target devices paired with each source device.
Examples
To pair an additional target device with each source device in group ProdDB, enter:
symclone- g ProdDB create- concurrent
To verify that each source device in group ProdDB has multiple targets, enter:
symclone- g ProdDB create- concurrent

Perform operations on devices in TimeFinder clone device list
Description
When working with a composite or device group, use the – tgt option to use devices from a local target list as targets for the specified action. See options below that can be paired with the with the – tgt option. See Dell Solutions Enabler Array Management CLI Product Guide for more information on creating and managing clone target lists.
The – tgt option works with all symclone actions, except for query and verify, as these actions are source device oriented and list all target devices paired with source devices by default, including TGT and RTGT.
When working with specific pairs, the symclone command supports the following target devices:
symld Ldev Name
sym dev Sym Dev Name
sympd Pdev Name
Syntax
For device groups, to copy from a local standard device to a local target, use the following syntax:
s y m c l o n e – g D g N a m e a c t i o n [ – t g t [ – b c v ] | – r d f [ – b c v | – t g t ] | – r b c v – t g t | – r r b c v |
– h o p 2 [ – t g t ] ] For composite groups, to copy from a local standard device to a local target, use the following syntax::
s y m c l o n e – c g C g N a m e a c t i o n [ – t g t [ – b c v ] | – r d f [ – b c v | – t g t ] | – r b c v – t g t | – r r b c v | – h o p 2 [ – t g t ] ]

Options
-rdf…………………… Specifies remote attached devices (RTGTs) as the target devices.
-hop2………… Specifies devices remotely associated on the second hop of a cascaded SRDF configuration (2TGTs) as the target devices.
Activate a TimeFinder clone copy session
Description
Activating the copy session starts the copy from the source device to the target device, and places the target device in the Read/Write state. The target host can access the cloned data and has access to data on the source host until the copy session is terminated.
NOTE: Cloned data is made available as a point-in-time copy at the time of activation and not at the time that the session was created.
To activate the clone copy session between target device and source device, enter:
symclone- g ProdDB activate
Make TimeFinder clone target device not ready to target host
Examples
To active the clone copy session between target device and source device and make the target device Not Ready to it’s host, enter:
symclone – g ProdDB activate- not _ ready
The clone copy can be made read/write enabled to the host using either the symdgready or symdevready command.
TimeFinder clone copy session consistency
The symclone activate command is used with the – consistent option to create clone copies that are consistent with the database up to the point where activation occurs. This feature is implemented using either the Enginuity Consistency Assist (ECS) feature or SRDF/A.
NOTE: If the R2 is in a consistent state and the copy session is pre- copying data, setting the consistent option invokes SRDF/A to maintain consistency, instead of ECA.
This feature is used to create clone copies that are consistent with the database up to the point in time that the activation occurs. The feature suspends writes to the source devices during the activation. When the activation has completed, writes are resumed and the target device contains a consistent production database copy of the source device at the time of activation.
The ECA feature is used to consistently activate copy sessions across multiple, heterogeneous hosts. ECA requires either a control host with no database, or a database host with a dedicated channel to the gatekeeper devices. In a SAN environment, gatekeepers and data devices may share the same FA port on the array but the gatekeepers must be available on a separate host HBA from the data devices. This requires a dedicated channel from a host HBA to the switch used to access only gatekeepers and not devices that contain host data. In this configuration, write intensive environments SYMAPI are able to freeze and then thaw I/O to the devices in the device group within the ECA window, regardless of the number of outstanding I/Os held by the HBA.
For detailed information on gatekeeper management, refer to the Dell Solutions Enabler Installation Guide.
The following figure shows how a control host can consistently activate a copy session that uses three database hosts that access devices on an array.
NOTE: When activating a copy session from an R2 device, if the SRDF pair is in adaptive copy mode, the – consistent option is not allowed.A device group, composite group, or a device file must be created on the controlling host for the target database to be consistently activated. Device groups can be created to include all of the devices being accessed or defined by database host access.
As shown in the above example, consistent activation of all copy sessions for Hosts A, B, and C can be done with a single command using a device group ( ProdAgrp) that includes all devices accessed by the three hosts. However, for consistent activation of copy sessions for a single host (Host A), without affecting other hosts, use a device group that includes only the  devices accessed by the single host.
Activate TimeFinder clone copy session consistency
Examples
To activate a consistent copy of the devices in group ProdDB, enter:
symclone – g ProdDB activate-consistent
Activate TimeFinder clone copy session for additional pair in a group
Examples
To activate a copy session for an additional clone pair in group ProdDB, enter:
NOTE: The copy session must exist prior to issuing the command.
symclone – g ProdDB activate – concurrent
Recreate TimeFinder clone copy device
Description
Use the symclon erecreate command to incrementally copy all subsequent changes made to the source device (made after the point-in-time copy was activated) to the target device.
Example
To recreate the copy session between target device and source device in group ProdDB, enter:
symclone – g ProdDB recreate
Restrictions
The following restrictions apply for the symclonere create operation:

• The session must have been activated to establish the new point-in-time copy.
• While in the Recreated state, the target device remains Not Ready to the host.

Recreate TimeFinder clone copy session using the establish command
Description
Use the symclone establish command, to recreate and then immediately activate a copy session with a single command.
Options
-concurrent ………………Activates an existing clone session for an additional clone pair in a group.
Examples
To recreate and then activate a previous copy session, enter:
symclone – g ProdDB establish
NOTE: The symclone establish command sets the target device to Not Ready for a short period time. If using a filesystem, unmount the target host before performing the establish command.
To recreate and then activate a copy session for an additional clone pair in group ProdDB, enter:
symclone – g ProdDB establish – concurrent
Recreate TimeFinder clone copy session for each pair in a group
When working with either a composite or device group, use the – concurrent option with the recreate action to recreate a clone session for each clone pair in a group.
Examples
To recreate a copy session for each clone pair in group ProdDB, enter:
symclone – g ProdDB recreate – concurrent
Restore data from target device
Use the symclonerestore command to copy target data to another device (full restore), or back to the original source device (incremental restore). The restore operation requires that the session is differential and the device pair is in the Copied state.
With a full restore ( – f u l l), the original session terminates and a copy session to the target of the restore starts.
With an incremental restore, the original session copy direction reverses and changed data is copied from the target device to the source device.
Examples
To fully restore data from the original target device to a device that was not involved in the original clone session, enter:
symclone – g ProdDB restore – full
**** NOTE: When constructing a symclon erestore command, the device receiving the data always appears first in the command, followed by the device from which the data is being copied.

Split a clone device pair
Description
Use the symclone split command to spit a clone device pair that is in the Restored state. The original source device becomes the source device for a future copy. and the establish or recreate command can be used.
Examples
To split a device pair. enter:
symelone -g ProdDB split
Terminate TimeFinder clone copy session
Description
Terminating a copy session deletes the pairing information in the array and removes any hotd on the target device. Terminating a session while the device pairs are in the CopyinProg state causes the session to end. If the application has not finished
accessing all of the data, the target copy is not a full copy.
The symclone terminate command is allowed for alt clone pair states.
Examples
To terminate the copy session for device pair, enter:
symelone -g FrodDB terminate
NOTE: A created and activated copy session may be terminated. but the data on the target device is not valid unless the device state is COPIED.
If the state is CopyinProg. then apply the -symforce option to terminate the session. This leaves the target copy as an incomplete copy.
If the -not_ready option és applied to the copy session. Solutions Enabler leaves the target devices in their prior Ready or NotReady state at the completion of the terminate operation. If the -not_ready option is not applied to the copy session.
Solutions Enabler leaves the target devices in the Ready state at the completion of the terminate. regardless of their state prior to the terminate operation.
Query TimeFinder clone copy session pairs
Description
The symcione query command is sent through a getekeeper device to the array and returns information about the state of a clone pair, all clone pairs in a device group, 8 composite group. or a device fite.
Syntax
To query target devices in 6 device group. composite group. or device file use the following syntax:
symclone -g DgName query
symclone -cg CgName query
symclone -f[ile] FileName query
Options
-offline
Retrieves target device information for the host database.
Examples
To query the state of the clone pairs in the prod device group. enter:
syaclone -g prod query
To query the state of SRDF-connected clone pairs in the prod device group. enter any of the following:
aymclone -g prod query -rdf
asymclone -g prod query -rdf -bev
aymclone -g prod query -rrbev
asymclone -g prod query -hop2
The results of the query inciude the following information for each member of a clone pair in a device group:

• Device name
• Number of invalid tracks
• Clone pair state

Query TimeFinder clone copy session pairs using the -summary option
Description
Use the -summary option with the symclone query command. to report the following results:

• Number of clone pairs in each clone pair state
• Number of invalid tracks

Options
-i, -c
Reports the sychronization rate and estimated time to complete a copy, for a specified time period ( – c) and at specified time intervals ( – i)
Examples
To view the number of clone pairs in the p r o d device group that are in each state, and to view the estimated time to completion, enter:
symclone- gprodquery – summary – i60
The – summary option can be used with the symclone verify command.
Verify TimeFinder clone copy session pair states
Description
Use the symclone verify command to verify that one or all clone pair(s) in a device group, composite group, or device file are in a particular state. The command can be used in scripts to verify that the clone device pair(s) are in a particular state prior to executing subsequent Solutions Enabler commands. If no device state qualifiers are specified, the default for the symclone verify, is to check for the Copied state.
Syntax
To verify target devices in a device group, composite group, or device file, use the following syntax:
s y m c l o n e – g D g N a m e v e r i f y
s y m c l o n e – c g C g N a m e v e r i f y
s y m c l o n e – f [ i l e ] F i l e N a m e v e r i f y
Options
NOTE: Add the – concurrent option with each of the following options to verify a concurrent clone pair.
-copied
Verifies that the copy sessions are in the Copied state (default).
-copyinprog
Verifies that the copy sessions are in the CopyInProgress state.
-created
Verifies that the copy sessions are in the Created state.
-recreated
Verifies that the copy sessions are in the Recreated state.
– restored
Verifies that the copy sessions are in the Restored state.
-split
Verifies that the copy sessions are in the Split state.
Examples
NOTE: For a multi-clone or concurrent clone device group, specifying the clone on the command line ensures that the verify operation checks the status of the clone. Otherwise, the verify operation checks the status of the standard device, which may no longer be established with the clone that you want to verify.
To return the status of standard device DEV001 with its last paired clone, enter:
symclone – g ProdBgrp verify DEV001
To return the status of a specific clone pair ( DEV001 with DEV005), enter:
symclone -g ProdBgrp verify DEV001 elm ld DEV005
To return the status every 30 seconds until all clone pairs in the device group (ProdBgrp) or composite group (MyConGrp) are in the Copied state. enter:
NOTE: If no device state qualifier is specified the command checks for the Copied state.
symclone -g ProdBgrp -i 30 verify
symclone -cg MyConGrp -i 30 verify
Possible return codes at 30-second intervals are zero (code symbol CLI_C_SUCCESS) if the verify criteria is met. or one of the return codes if none or not all of the devices meet the verify criteria. Refer to Return codes for TimeFinder clone copy verify session query for return codes.
Return codes for TimeFinder clone copy verify session query
Table 3. Return codes for verifying TimeFinder clone copy session

TimeFinder cascaded clone copy session
The target device of a clone session can be used as the source for one or more clone sessions. This cascading clone capability allows a clone operation to take place with a device that is already involved in a clone operation without ending the first clone session.
As the figure below shows, cascaded sessions are accepted from left to right. This means you can use TimeFinder to clone  device A to device B. Then, while the relationship between A and B is preserved, you can clone device B to device C. If you havesession A -> B -> C, then session B -> C can only be activated after session A -> B has been activated. Figure 2. Clone from clone target (both sessions are cascaded clone)
TimeFinder clone Restore to Target (incremental restore to cascaded clone target)
Restore to Target (RTT) allows you to perform an incremental restore to a cascaded clone target. For example, devices in an A -> B -> C cascaded clone session can copy data from device C to device A (through device B).
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 in cremental cloneestablish 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.

Creating multiple clone copies from a standard device
Creating multiple clone copies from a standard device illustrates creating multiple clone copies from a standard source device DEV001 on four standard target devices ( DEV005, DEV006, DEV007, and DEV008) with various hosts accessing them. NOTE:
A separate copy session must be created between the source device ( DEV001) and each target device ( DEV005, DEV006, DEV007, and DEV008).
Using composite groups to manage clone pairs across arrays
About this task
Using a composite group when a set of devices spans two arrays shows a production host locally connected to two arrays (A and B). A composite group is defined on the production host and includes source devices and target devices from each array.
The target devices can be standard devices or BCV devices. Another locally connected host allows access to the clone targets.Although clone copy operations might normally be performed from the production host (Using a composite group when a set of devices spans two arrays) because the composite group is defined there in its SYMAPI database, there are methods that would allow you to control clone operations from another locally connected host like the target host. One way is to copy the composite group definition to another host. A more efficient method is to enable Group Naming Services (GNS), which automatically propagates the composite group definition to the arrays and other locally attached hosts that are running the GNS daemon.
The following steps explain how to setup a composite group that spans two arrays as shown in Using a composite group when a set of devices spans two arrays:
Steps
1. From the production host. create a Regular type composite group (for example. MyGrp):
symeg create MyGrp -type regular
2. Add to the composite group those standard devices on array A (3087) and array B (3143) that are the source devices:
symeg -cg MyGrp -sid 3087 add dev 0072
symcg -cg MyGrp -sid 3143 add dev 0095
3. Associate a BCV target device from each array with the composite group:
symbcv -cg MyGrp -sid 3087 associate dev 0053
4. Create clone pair sessions from those devices in the composite group:
symclone -cg MyGrp create
5. Activate these clone pair sessions:
symclone -cg MyGrp activate
Command options with device files
Command options with device files lists the symelone control operations and the possible options to use when targeting device
Pairs specified in a device file of a given array.
Table 4. symclone -file control arguments and possible options

a. Not supported on arrays running PowerMaxOS 10 (6079) and higher.

TimeFinder State Rules Reference

This appendix helps you determine if the TimeFinder operation you want to complete is supported for devices in a particular pair state.
Topics:
TimeFinder/Clone operations
TimeFinder/Clone operations
This section describes the TimeFinder/Clone control operations that are allowed for devices in various pair states.
Basic TimeFinder/Clone operations
The following image shows the relationship between devices for a basic TimeFinder/Clone operation.Figure 5. Basic TimeFinder/Clone device relationship
In the following table:

• Pair state refers to the current state of the source-target pair.
• Operation refers to the intended control operation.
• Y indicates that the operation is allowable for that state.

Table 5. Basic TimeFinder/Clone operations

TimeFinder/ Clone
Source -> Target
Operation:| TimeFinder/Clone Source -> Target Pair state:
---|---
No session| Create in prog| Created| Recreated| Copy in progress| Copied| Copy on write| Copy on access| Inds| Restore in prog| Restored| Terminate in prog| Invalid| Failed
Create| Y| | | | | | | | | | | | |
Recreate c • d| | | | | Y| Y| | | Y| | | | | Y
Activate| | | Y| V| | | | | | | | | |
Full Establish| Y| | | | | | | | | | | | |
Incremental Establish| | | | | Y| Y| | | Y| | | | |
Full Restore| Y| | | | | Y| | | Y| | | | |
Incremental Restore| | | | | | Y| | | Y| | | | |
Split| | | | | | | | | | | Y| | |
Terminate| | Y| Y| Y| y C. f| y| Y| Y| Y| Y g| Y| Y| Y| Y

Table 5. Basic TimeFinder/Clone operations (continued)
a. Transient state.
b. State not available on PowerMaxOS 10 (6079) and higher.
c. Session must be differential.
d. All Clone sessions on PowerMaxOS 10 (6079) and higher are differential.
e. Requires -symmforce (not recommended).
f. Target data will be incomplete.
g. Source data will be incomplete.
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, TimeFinder Snap, and TimeFinder/Mirror copies.
Concurrent TimeFinder/Clone
The following image shows the relationship between devices for a TimeFinder/Clone pairing of a source device with two targets.Figure 6. Concurrent TimeFinder/Clone device relationships
NOTE:
The positions of Target 1 and Target 2 are interchangeable in the illustration above.
In the following table:

• Pair state refers to the current state of the Source-Target 1 pair.
• Operation refers to the intended control operation on the Source-Target 2 pair.
• Y indicates that the operation is allowable for that state.

Table 6. Concurrent TimeFinder/Clone operations

TimeFinder/ Clone
Source -> Target 2 Operation:| TimeFinder/Clone Source -> Target 1 Pair state:
---|---
No session| Create in prog a| Created| Recreated| Precopy b| Copy in progress| Copied| Copy on write b| Copy on access b| Split| Restore in prog| Restored| Terminate in prog| Invalid| Failed
Create| Y| | yc| Yc| yc| yc| yc| yc| yc| yc| yc| yc| | |
Recreate d • e| | | Y| Y| Y| Y| Y| Y| Y| Y| Y| y| | | Y
Activate| | | Y| Y| Y| Y| Y| Y| Y| Y| | Y| | |
Full Establish| Y| | yc| yc| yc| yc| yc| yc| yc| yc| | yc| | |
Incremental Establish| | | Y| Y| Y| Y| Y| Y| Y| Y| | Y| | |
Set Mode Copy f| | | Y| Y| Y| Y| Y| Y| Y| Y| | Y| | |
Set Mode Nocopy f. g| | | Y| Y| Y| Y| Y| Y| Y| Y| | Y| | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---
Set Mode
Precopy f| | | Y| Y| Y| Y| Y| Y| Y| Y| | Y| | |
Full Restore d| Y| | | | | | Y| | | Y| | | | |
Incremental Restored| | | | | | | | | | Y| | | | |
Split| | | Y| Y| | | Y| | | Y| | | | |
Terminate| | Y| Y| Y| `I| y h. i| y| Y| Y| Y| Y ti• I| Y| Y| Y| Y

a. Transient state.
b. This state is not available on PowerMaxOS 10 (6079) and higher.
c. Requires -concurrent flag only for dgleg operations.
d. Session must be differential.
e. All Clone sessions on PowerMaxOS 10 (6079) and higher are differential.
f. If not already set to this mode.
g. Cannot be differential.
h. Requires -symmforce (not recommended).
i. Target data will be incomplete.
j. Source data will be incomplete.
Cascaded TimeFinder/Clone operations
A cascaded copy operation occurs when a device is both the source of a copy and the target of a copy, such that the devices are in the relationship of A -> B -> C.
Cascaded TimeFinder/Clone (Clone off Clone): A – B
The following image shows the relationship between devices for a Clone off Clone operation in which source device A is paired with target device B and an additional session uses device B as a source paired with target device C. Figure 7. Clone off Clone device relationship: A - > B
Limitations

• 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 the following table:

• Pair state refers to the current state of the B-C pair.
• Operation refers to the intended control operation on the A-B pair.
• Y indicates that the operation is allowable for that state.

Table 7. Clone off Clone operations: A – B

a. Transient state.
b. State not available on PowerMaxOS 10 (6079) and higher.
c. Not allowed with the PRECOPY flag.
d. Session must be differential. All Clone sessions on PowerMaxOS 10 (6079) and higher are differential.
e. If not already set to this mode.
f. Not available on PowerMaxOS 10 (6079) and higher.
g. Cannot be differential.
Cascaded TimeFinder/Clone (Clone off Clone): B – C
The following image shows the relationship between devices for a Clone off Clone operation in which source device A is paired with target device B and an additional session uses device B as a source paired with target device C. Figure 8. Clone off Clone device relationship: B - > C
Limitations:

• Cascaded sessions cannot exceed two hops.

In the following table:

• Pair state refers to the current state of the A-B pair.
• Operation refers to the intended control operation on the B-C pair.
• Y indicates that the operation is allowable for that state.

Table 8. Clone off Clone operations: B – C

| TimeFinder/Clone A -> B Pair state:
---|---
TimeFinder/Clone B -> C Operation:| No session| Create in prog| Created| Recreated| Adontd| Copy in progress| pa!do)| Copy on write cr| Copy on access| Inds| Restore in prog| Restored| Terminate in prog a| Invalid| Failed
Create| Y| | Y| Y| Y C| Y| Y| Y| Y| Y| Y| Y| | |
Recreate d| Y| | Y| Y| Y C| Y| Y| Y| Y| Y| Y| Y| | | Y
Activate| Y| | | | | | Y| | | Y| Y| Y| | |
Full Establish| Y| | | | | | Y| | | Y| Y| Y| | |
Incremental Establish| Y| | | | | | Y| | | Y| Y| Y| | |
Set Mode Copy el| Y| | Y| Y| Y| Y| Y| Y| Y| Y| Y| Y| | |
Set Mode Nocopy e• g. f| Y| | Y| Y| Y| Y| Y| Y| Y| Y| Y| Y| | |
Set Mode Precopy e • 1| Y| | Y| Y| Y| Y| Y| Y| Y| Y| Y| Y| | |
Full Restore d| Y| | | | | | | | | | | Y| | |
Incremental Restore d| Y| | | | | | Y| | | Y| | Y| | |
Split| Y| | | | | | Y| | | Y| Y| Y| | |
Terminate| Y| Y| Y| Y| Y| Y| Y| Y| Y| Y| Y| Y| Y| Y| Y

a. Transient state.
b. State not available on PowerMaxOS 10 (6079) and higher.
c. Requires the PRECOPY flag. Precopy is not supported on PowerMaxOS 10 (6079) and higher.
d. Session must be differential. All Clone sessions on PowerMaxOS 10 (6079) and higher are differential.
e. If not already set to this mode.
f. Not available on PowerMaxOS 10 (6079) and higher.
g. Cannot be differential.

SRDF State Rules Reference

This appendix describes the applicable SRDF pair states that rule the TimeFinder SnapVX, TimeFinder/Clone, and TimeFinder/Snap copy session operations.
Topics:

• SRDF pair states
• State rules for TimeFinder/Clone operations

SRDF pair states
Certain TimeFinder copy operations are not allowed on devices that are SRDF protected, as these operations can conflict with each other. The availability of some actions depends on the current state of SRDF pairs. Refer to your product guide for details
about supported features.
The following table provides a description the various SRDF pair states.
Table 9. SRDF pair states

configuration which uses a Witness array:
● There are no invalid tracks between the two pairs.
● The R1 and the R2 are Ready (RW) to the hosts.
ActiveBias| The R1 and the R2 are currently in an SRDF/Metro configuration using bias:
● The user could have specified “use bias” during the establish/restore action or the Witness array is not vailable.
● There are no invalid tracks between the two pairs.
● The R1 and the R2 are Ready (RW) to the hosts.
Consistent| The R2 mirrors of SRDF/A devices are in a Consistent state. Consistent state signifies the normal state of operation for device pairs operating in asynchronous mode.
Failed Over| The R1 is currently Not Ready or write disabled and operations have been failed over to the R2.
Invalid| The default state when no other SRDF state applies. The combination of R1, R2, and SRDF link states and statuses do not match any other pair state. This state may occur if there is a problem at the disk director level.
Mixed| A composite device group SRDF pair state. There exists different SRDF pair states within a device group.
Partitioned| Solutions Enabler is currently unable to communicate through the corresponding SRDF path to the remote array. Partitioned may apply to devices within an RA group.
For example, if Solutions Enabler is unable to communicate to a remote array via an RA group, devices in that RA group will be marked as being in the Partitioned state.
R1 Updated| The R1 is currently Not Ready or write disabled to the host, there are no local invalid tracks on the R1 side, and the link is Ready or write disabled.
R1 UpdInProg| The R1 is currently Not Ready or write disabled to the host, there are invalid local (R1) tracks on the source side, and the link is Ready or write disabled.
Split| The R1 and the R2 are currently Ready to their hosts, but the link is Not Ready or write disabled.
Suspended| The SRDF links have been suspended and are Not Ready or write disabled. If the R1 is Ready while the links are suspended, any I/O will accumulate as invalid tracks owed to the R2.
Synchronized| The R1 and the R2 are currently in a Synchronized state. The same content exists on the R2 as the R1. There are no invalid tracks between the two pairs.
SyncInProg| A synchronization is currently in progress between the R1 and the R2. There are existing invalid tracks between the two pairs and the logical link between both sides of an SRDF pair is up.
Transmit Idle| The SRDF/A session cannot push data in the transmit cycle across the link because the link is down.

State rules for TimeFinder/Clone operations
This section identifies the s y m c l o n e copy actions that are available for use within each of the SRDF pair states.
This section refers to the copy source and the copy target. It is important to note that “source” and “target” refer to the direction of the data flow. In this context, these terms do not refer to the TimeFinder/Clone device pair relationship.
The following image shows an establish operation for which the R1 device is the source of the data for the clone copy operation.
In other words, the TimeFinder/Clone source device is the source for the clone copy. The following image shows a restore operation for which the R1 device is the target of the data for the clone copy operation. In other words, for a restore, the TimeFinder/Clone source device is the target of the clone copy. TF/Clone operations R1 source
Table 10. TF/Clone operations allowed when R1 is source of clone copy data

a. Action is not allowed if there are local R1 invalids or remote R2 invalids.
b. Action is not allowed if the -consistent option is specified.
TF/Clone operations R1 target
Table 11. TF/Clone operations allowed when R1 is target of clone copy data

a. Action is not allowed if there are local R1 invalids or remote R2 invalids.
b. The -force option must be applied.
c. Action is not allowed with CopyOnAccess. CopyOnAccess is not applicable on arrays running PowerMaxOS 10 (6079) and higher.
TF/Clone operations R2 source
Table 12. TF/Clone operations allowed when R2 is source of clone copy data

a. If the precopy option is not applied, the action is not allowed if either of the following applies (precopy is not supported on arrays running PowerMaxOS 10 (6079) and higher):

1. SRDF/A device-level write pacing is not activated and supported on the SRDF/A session, or
2. The SRDF pair is the R21-> R2 of a cascaded configuration and any of the following apply:

a. The R21 device is not pace-capable.
b. The precopy option (-precopy) must be applied for SRDF/A.
c. Action is not allowed if there are remote R1 invalids or local R2 invalids.
d. Action is not allowed if there are local R1 invalids or remote R2 invalids.
TF/Clone operations R2 target
Table 13. TF/Clone operations allowed when R2 is target of clone copy data

a. Action is not allowed if the target device is an R2 larger than the R1.
b. Action is not allowed if the R2 target device is in asynchronous mode.

SRDF State Rules Reference

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>