Dell Solutions Enabler 10.0.

0 TimeFinder
SnapVX
CLI User Guide
10.0.0

July 2022
Rev. 01
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.
 Contents

Figures..........................................................................................................................................5

Tables........................................................................................................................................... 6
Preface.........................................................................................................................................................................................7
Revision history.................................................................................................................................................................... 9

Chapter 1: Introduction to TimeFinder SnapVX............................................................................ 10

TimeFinder SnapVX overview......................................................................................................................................... 10
Generation numbers and snapset IDs...................................................................................................................... 11
Snapshot policy............................................................................................................................................................. 11
zDP snapshots.............................................................................................................................................................. 12
SnapVX CLI overview....................................................................................................................................................... 12
SnapVX supported configurations................................................................................................................................. 12
SnapVX operating modes.................................................................................................................................................12
Secure snaps....................................................................................................................................................................... 12
Consistent SnapVX snapshots........................................................................................................................................13
Snapshot policy.................................................................................................................................................................. 14
Expired snapshot rules......................................................................................................................................................15
Geometry Compatible Mode flag set issue with SnapVX controls........................................................................ 15

Chapter 2: Performing TimeFinder SnapVX Operations ............................................................... 16

Establish SnapVX snapshot............................................................................................................................................. 16
Rename SnapVX snapshot ..............................................................................................................................................17
Set SnapVX snapshot time to live (TTL)..................................................................................................................... 18
Set persistent SnapVX snapshot................................................................................................................................... 19
Convert SnapVX snapshot to secure snapshot.........................................................................................................20
Link a SnapVX snapshot...................................................................................................................................................21
Change SnapVX snapshot link mode............................................................................................................................ 22
Unlink SnapVX snapshot..................................................................................................................................................22
Relink SnapVX snapshot..................................................................................................................................................23
Restore SnapVX snapshot.............................................................................................................................................. 23
Terminate SnapVX snapshot.......................................................................................................................................... 24
Bulk terminate SnapVX snapshots.......................................................................................................................... 25

Chapter 3: TimeFinder SnapVX snapshot reporting .....................................................................27

Display SnapVX snapshot status................................................................................................................................... 27
Verify SnapVX snapshot status..................................................................................................................................... 32

Chapter 4: TimeFinder SnapVX Configurations and Examples ..................................................... 33

Cascading SnapVX snapshots........................................................................................................................................33
Determine fully defined SnapVX snapshot............................................................................................................ 34
Modified SnapVX point-in-time copies........................................................................................................................ 34
SnapVX behavior when adding source devices......................................................................................................... 34
SnapVX snapshot restore operations when adding source devices............................................................... 35
SnapVX snapshot link operations when adding source devices...................................................................... 35

Contents 3
 SnapVX relink operations when adding source devices.....................................................................................36
Common uses for SnapVX snapshot configurations................................................................................................ 36
Create targetless SnapVX snapshots and restore production volumes.........................................................36
Refresh multiple test or development environments from a SnapVX linked target....................................37
Provision test or development environments with cascading SnapVX snapshots......................................38

Chapter 5: TimeFinder SnapVX State Reference Rules.................................................................41

Determine SnapVX states/SRDF and ORS operations interaction....................................................................... 41
TimeFinder SnapVX operations states....................................................................................................................41
Determine SnapVX states......................................................................................................................................... 42
State rules for TimeFinder SnapVX operations with SRDF pair states................................................................45
SRDF pair states..........................................................................................................................................................45
TimeFinder SnapVX R1 source................................................................................................................................. 47
TimeFinder SnapVX R2 source................................................................................................................................ 48
TimeFinder SnapVX R1 target.................................................................................................................................. 48
TimeFinder SnapVX R2 target................................................................................................................................. 48
TimeFinder SnapVX operations with ORS pair states..............................................................................................49
State rules for source control operations with SnapVX and Clone source states............................................ 49
TimeFinder/Clone operations on a SnapVX source............................................................................................ 49
SnapVX source operations off Clone source........................................................................................................50
VP Snap operations on a SnapVX source.............................................................................................................. 51
7SnapVX operations on a VP Snap source............................................................................................................ 51
TimeFinder/Mirror operations on a SnapVX source........................................................................................... 52
SnapVX operations on a TimeFinder/Mirror source........................................................................................... 52
State rules for source control operations with SnapVX and Clone source states............................................ 53
ODM/OR target is TimeFinder/Clone source...................................................................................................... 53
ODM/OR target is TimeFinder/SnapVX source.................................................................................................. 54
TimeFinder/Clone source is ODM/OR target...................................................................................................... 55
TimeFinder/SnapVX source is ODM/OR target..................................................................................................56
Index........................................................................................................................................... 57

4 Contents
 Figures

1 Cascading snapshots.............................................................................................................................................. 33
2 Copying a modified point-in-time back to the source.................................................................................... 34
3 Storage group with two snapshots..................................................................................................................... 35
4 Source devices after a restore operation.......................................................................................................... 35
5 Target devices after a link operation.................................................................................................................. 35
6 SnapVX targetless snapshots............................................................................................................................... 38
7 SnapVX cascaded snapshots................................................................................................................................ 39

Figures 5
 Tables

1 Typographical conventions used in this content................................................................................................ 8

2 Revision history.......................................................................................................................................................... 9
3 Prerequisites and states for SnapVX control operations............................................................................... 41
4 Determine SnapVX State....................................................................................................................................... 42
5 SRDF pair states...................................................................................................................................................... 45
6 SnapVX control operations allowed on R1 source by SRDF state............................................................... 47
7 SnapVX control operations allowed on R2 source by SRDF state.............................................................. 48
8 SnapVX control operations allowed on R1 target by SRDF state................................................................ 48
9 SnapVX control operations allowed on R2 target by SRDF state............................................................... 49
10 Allowed TimeFinder/Clone operations (A->B) of SnapVX Source (A)...................................................... 50
11 Allowed SnapVX Source (A) operations off Clone Source (A).................................................................... 50
12 Allowed VP Snap operations (A->B) of SnapVX Source (A).........................................................................51
13 Allowed SnapVX Source (A) operations off VP Snap Source (A)............................................................... 52
14 Allowed TimeFinder/Mirror operations (A->B) on SnapVX Source (A).....................................................52
15 Allowed SnapVX Source (A) operations off TimeFinder/Mirror Source (A)............................................ 53
16 ODM/OR target is TimeFinder/Clone source.................................................................................................. 53
17 ODM/OR target is TimeFinder/SnapVX source.............................................................................................. 54
18 TimeFinder/Clone source is ODM/OR target.................................................................................................. 55
19 TimeFinder/SnapVX source is ODM/OR target.............................................................................................. 56

6 Tables
 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 SnapVX.

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 Describes new features and any known limitations.

Enabler 10.0.0
Release Notes
Dell Solutions Provides host-specific installation instructions.
Enabler
Installation and
Configuration
Guide
Dell Solutions Describes how to configure array control, management, and migration operations using SYMCLI
Enabler Array commands for arrays running HYPERMAX OS and PowerMaxOS.
Controls and
Management CLI
User Guide
Dell Solutions Documents the SYMCLI commands, daemons, error codes and option file parameters provided with the
Enabler CLI Solutions Enabler man pages.
Reference Guide
Dell Solutions Describes how to configure and manage SRDF environments using SYMCLI commands.
Enabler SRDF
Family CLI User
Guide

Special notice conventions used in this document

Dell Technologies uses the following conventions for special notices:

NOTE: A NOTE indicates important information that helps you make better use of your product.

Preface 7
 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.

Typographical conventions
Dell Technologies uses the following type style conventions in this document:

Table 1. Typographical conventions used in this content

Font Description
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:

Product Dell Technologies technical support, documentation, release notes, software updates, or information
information about Dell Technologies products can be obtained at https://www.dell.com/support/home (registration
required) or https://www.dell.com/en-us/dt/documentation/vmax-all-flash-family.htm.
Technical Dell Technologies offers various support options.
support ● 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.
e-Licensing To activate your entitlements and obtain your license files, go to the Service Center on Dell
support 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.

8 Preface
 ● 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.
SolVe Online and SolVe provides links to customer service documentation and procedures for common tasks. Go to
SolVe Desktop https://solve.dell.com/solve/home, or download the SolVe Desktop tool from https://www.dell.com/
support/home and search for SolVe Desktop. From SolVe Online or SolVe Desktop, load the PowerMax
and VMAX procedure generator.
NOTE: Authenticate (authorize) the SolVe Desktop tool. After it is installed, familiarize yourself with
the information under Help.

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
Provides a description of document changes.

Table 2. Revision history

Revision Description and/or change
1 This is the initial revision of the Dell Solutions Enabler TimeFinder SnapVX V10.0 CLI User Guide.
Changes in Solutions Enabler V10.0 include:
● Removed support for TimeFinder/Mirror, TimeFinder/VPSnap for arrays running PowerMaxOS 10
(6079).
● Removed support for TimeFinder/Snap for arrays running PowerMaxOS 5978 or lower.

Preface 9
 1
Introduction to TimeFinder SnapVX
This chapter introduces Dell Solutions Enabler TimeFinder SnapVX and the symsnapvx command.

Topics:
• TimeFinder SnapVX overview
• SnapVX CLI overview
• SnapVX supported configurations
• SnapVX operating modes
• Secure snaps
• Consistent SnapVX snapshots
• Snapshot policy
• Expired snapshot rules
• Geometry Compatible Mode flag set issue with SnapVX controls

TimeFinder SnapVX overview

Dell EMC TimeFinder SnapVX creates and manages point-in-time snapshots of critical data that can be used for backups,
decision support, and to refresh data warehouse, test, and development environments. SnapVX snapshots do not require target
volumes. SnapVX snapshots share back-end allocations with the source volume and other snapshots on the source volume.
TimeFinder SnapVX is supported on arrays running HYPERMAX OS 5977, PowerMaxOS 5978 and higher, and snapshots are
always consistent. Consistency across multiple arrays is achieved when source devices are in a composite group.
SnapVX reduces the steps to create and use point-in-time copies using two distinct activities:
● Create snapshot—SnapVX creates snapshots by storing changed tracks (deltas) directly in the Storage Resource Pool
(SRP) of the source device. You are not required to specify a target device and source/target pairs to create a snapshot. A
single source volume is allowed up to 256 manual snapshots, or a total of 1024 snapshots consisting of manual, snapshots,
automated snapshot policies, and legacy TimeFinder snapshots. Each snapshot can be assigned a user-defined name and
(optional) expiration date, both of which can be modified. One command creates a snapshot of single volume or an entire
storage group.
● Link to target—Access SnapVX snapshots by linking them to a host accessible volume (target). Up to 1024 target volumes
can link to snapshot(s) on a single source volume. The 1024 limit can consist of 1024 links to the same snapshot on a source
volume or multiple links to multiple snapshots on the source volume.
Snapshots can be cascaded from linked targets, and targets can be linked to snapshots of linked targets.
If there are multiple snapshots and an application must find a particular one, you can link and relink until the correct snapshot
is located.

There are three types of snapshots:

● Manual snapshots: these snapshots are taken manually by users with the symsnapvx establish command.
● Automated (or Snapshot policy) snapshots: these snapshots are taken automatically based on a configured Snapshot policy.
See the Dell Solutions Enabler Array Controls and Management CLI User Guide for details.
● zDP snapshots: these are snapshots are taken by the Automated Snapset Creation with Data Protector for z Systems
(zDP). These can be reported but cannot be acted on by Open Systems Solutions Enabler.
NOTE: SnapVX, along with FAST.X, is used to encapsulate devices on Dell EMC Data Domain systems for Dell EMC Storage
Direct, and allows for direct backup from arrays running HYPERMAX OS and PowerMaxOS to Data Domain systems.
Encapsulated Data Domain devices are fully recognized by arrays running HYPERMAX OS and PowerMaxOS, appear in
symsnapvx list command displays, and can be used as a filter when listing devices. For a description of Dell EMC
Storage Direct backup and restore operations with arrays running HYPERMAX OS or PowerMaxOS, see the EMC VMAX3
Family Product Guide for VMAX 100K, VMAX 200K, VMAX 400K with HYPERMAX OS, Dell EMC VMAX All Flash Product
Guide for VMAX 250F, 450F, 850F, 950F with HYPERMAX OS , and Dell PowerMax Family Product Guide. See Dell EMC

10 Introduction to TimeFinder SnapVX

 Storage Direct documentation for instructions on setting up, configuring, and using the integrated Storage Direct/VMAX3
and All Flash array solution.

Generation numbers and snapset IDs

Generation numbers
It is possible to have multiple snapshots with the same name for the same set of source volumes, and generation numbers
identify the different snapshots. Generation numbers are relative to existing snapshots at the time of creating or displaying
snapshots, and they change as snapshots are created and terminated. For example, if a recent snapshot is terminated, all older
snapshots have their generation number decreased by one.
The most recent snapshot always has generation 0. and all previous sessions have their generation numbers incremented by
one. Similarly, if a more recent snapshot is terminated, all older snapshots have their generation numbers decreased by one.
NOTE: Generation numbers are dynamic, but snapset IDs are not. Creating or terminating snapshots may cause generation
numbers of other snapshots to change. This could lead to situations where multiple users create snapshots on the same set
of volumes.
Snapset IDs
A snapset refers to a set of consistent snapshots that are taken together. If an SG contains 10 devices and a snapshot is taken,
there will be 10 consistent snapshots in the resulting snapset. A snapset is identified by an absolute, unique snapset ID.
Snapset IDs are unique 64-bit integers. This ID is generated by PowerMaxOS. It is guaranteed to be the same for all the
snapshots in a Snapset. Snapset ID values represent the time (from the point of view of the array) the snapshots were actually
taken. Larger values correspond to snapshots taken after ones with smaller values.
The snapset ID gives you a specific value making managing snapshots, especially restoring easier.
Snapset IDs are supported for manual snapshots and policy snapshots as well for arrays running PowerMaxOS 5978.669.669 or
higher.

Snapshot policy
Solutions Enabler V9.2 with arrays running PowerMaxOS 5978.669.669 supports Snapshot policies to request a stream of
consistent snapshots to be automatically taken for applications based on user-defined schedules. The symsnapvx CLI reports
both the automated and the manual snapshots on a device. Snapshots can be distinguished by the snapshot type flag.

zDP snapshots
Solutions Enabler V9.1 or higher with arrays running PowerMaxOS 5978.444.444 or higher supports reporting all the snapshots
on a device, including Automated Snapset Creation with Data Protector for z Systems (zDP) snapshots. Snapsets created by
zDP are not visible to previous versions of Solutions Enabler. To overcome this, a manual snapshot is created in PowerMaxOS
when a pre-9.1 version of Solutions Enabler requests snapshot data for devices against which there are new type of zDP
snapsets. This snapset will be in a state that trips the interaction rules of concern ensuring that the older Solutions Enabler will
not perform dangerous operations on these devices.
When a device is the target of new zDP snapset the system returns one dummy link target record with the correct source and
target devices for the actual link. The link dummy record has the same copy/nocopy state as the actual Automated snapset
record. If a device is link –nocopy target then all NDM and SRDF control actions are blocked on that device. Manufactured
snapshots are reported with the snapshot name “_Automated_Snapshot”.

Snapshot policy
Solutions Enabler V9.2 with arrays running PowerMaxOS 5978.669.669 supports Snapshot policies to request a stream of
consistent snapshots to be automatically taken for applications based on user-defined schedules. The symsnapvx CLI reports
both the automated and the manual snapshots on a device. Snapshots can be distinguished by the snapshot type flag.

Introduction to TimeFinder SnapVX 11

zDP snapshots
Solutions Enabler V9.1 or higher with arrays running PowerMaxOS 5978.444.444 or higher supports reporting all the snapshots
on a device, including Automated Snapset Creation with Data Protector for z Systems (zDP) snapshots. Snapsets created by
zDP are not visible to previous versions of Solutions Enabler. To overcome this, a manual snapshot is created in PowerMaxOS
when a pre-9.1 version of Solutions Enabler requests snapshot data for devices against which there are new type of zDP
snapsets. This snapset will be in a state that trips the interaction rules of concern ensuring that the older Solutions Enabler will
not perform dangerous operations on these devices.
When a device is the target of new zDP snapset the system returns one dummy link target record with the correct source and
target devices for the actual link. The link dummy record has the same copy/nocopy state as the actual Automated snapset
record. If a device is link –nocopy target then all NDM and SRDF control actions are blocked on that device. Manufactured
snapshots are reported with the snapshot name _Automated_Snapshot.

SnapVX CLI overview

The symsnapvx command performs the following operations:
● Creates snapshots
● Creates secure snapshots. Please read Secure snaps before creating secure snapshots for important information on
terminating these snapshots.
● Converts regular snapshots to secure snapshots
● Names or renames snapshots
● Sets snapshots to automatically terminate in a specified number of days and hours
● Creates links from snapshot data to host mapped target devices
● Automatically unlinks existing links and relinks to a different snapshot
● Unlinks a snapshot without relinking it to a different snapshot
● Removes snapshot from the system
● Restores snapshots by copying point-in-time data from a snapshot back to the original source device
● Verifies whether one or more devices are in the requested state
● Lists snapshots

SnapVX supported configurations

SnapVX is supported on VMAX3, VMAX All Flash and PowerMax systems.
Local operations will act upon the selected device itself, remote operations will act on the device's remote partner, and two hop
operations will act on the device's remote-remote partner.

SnapVX operating modes

SnapVX supports the following modes of operation:
● Single device
● Device list
● Device ranges
● DG group mode — uses STD device as source and TGT device as link targets.
● CG group mode — uses STD device as source and TGT device as link targets.
● SG group mode — only selects devices that are not gatekeepers.
Display examples throughout this chapter show how to execute SYMCLI commands using each mode of operation.

Secure snaps
For arrays running HYPERMAX OS Q2 2017 or higher, secure snapshots is an optional setting for SnapVX targetless snapshots
that prevent accidental or intentional deletion of snapshots. Terminating a secure snapshot while the retention period is in
effect is not allowed. When the retention time is reached the snapshot is automatically terminated only if there are no existing

12 Introduction to TimeFinder SnapVX

links or restore sessions. Extending the retention period is allowed but reducing it is not allowed. A traditional snapshot can be
converted to a secure snaphot, but a secure snapshot may not be converted to a traditional snapshot. All SnapVX operations
and rules for traditional snapshots regarding restores, linked target operations, and automatic expiration also apply to secure
snapshots.
CAUTION:

When implementing secure snaps a user should determine how many snapshots on an array must be secure. The
user should consider using secure snaps only on certain critical volumes, or only on a subset of the snapshots,
to capture particular points-in-time that are critical to the business, Length of retention time should also be
considered as part of the secure snapshot implementation. As always, proper planning and system sizing is
crucial, no matter the types or number of snapshots that will exist in an environment.

Secure snapshots may only be terminated after they expire or by customer-authorized Dell EMC Support. Refer
to Knowledgebase articles 498316 and 499975 for additional information.

Secure snapshots rules and allowable Solutions Enabler operations:

● The secure expiration time is available at the snapshot level.
● If the secure expiration time expires and the snapshot has no links or restore session, the snapshot is automatically deleted
by the system.
● If the secure expiration time expires and the snapshot has link to a device or has a restore session, the snapshot is
automatically deleted by the system only after the linked target is unlinked or the restore session is terminated.
● If the secured snapshot expiration time expires and the snapshot is linked to a device or has a restore session, the snapshot
is no longer secured and is identified as expired.
● A regular snapshot can be converted to secure snapshot by specifying a secure expiration time.
● A secure expiration time can only be extended forward in time and not set back in time from the current setting.
● A secure snapshot can be restored, renamed, linked, unlinked, set copy mode, and terminate a restore.
● A secure snapshot that fails can be terminated.

Solutions Enabler operations not allowed on secure snapshots:

● Terminating the snapshot if it is activated.
● Setting time to live (TTL) on the snapshot
● Setting the secure expiration time back in time from the current setting

Secure snapshot rules and restrictions on VMAX arrays running

HYPERMAX OS5977 Q217SR or higher (applies to FBA and CKD devices):
● New secure snapshots cannot be created when the SRP (Storage Resource Pool ) is above the RC (Reserve Capacity).
● Secure snaps are unique in the handling of host writes and snapshots when SRP or Replication Data Pointer Cache limits
are reached. Secure snaps are intended for use in cases where protecting specific point-in-time images are considered
the highest priority. When Reserved Capacity of an SRP is reached and a host write to a source volume requires a new
allocation in the SRP, secure snaps (unlike traditional snaps) are allowed to grow past the Reserved Capacity limit of the
SRP. Preserving the secure snaps also takes priority over host writes to those source volumes in the event the entire SRP
runs out of available capacity. This is the intent of secure snapshots. For example, in the event of an intentional attack or a
runaway application on a system, that is using up all of the available capacity, preserving the secure snaps allows the user to
restore from the secure snaps once the situation has been resolved.

Consistent SnapVX snapshots

By default, all SnapVX snapshots are consistent with the database when created and established. Depending on the state of the
devices at the time of the snapshot, SnapVX pauses I/O to ensure there are no writes to the source device while the snapshot
is created. When the activation completes, writes are resumed and the target device contains a consistent production database
copy of the source device at the time of activation.

Introduction to TimeFinder SnapVX 13

 NOTE: Snapshots on a composite group are consistent across the entire group, even if the composite group spans devices
across multiple VMAX3 and VMAX All Flash arrays.

Source device requirements for consistent snapshots:

● All devices must be R1 or R2; a mixture of R1 and R2 devices is not supported.
● A mixture of R1 and non-SRDF devices is allowed. The R1 devices can be a mixture of RW and NR on the SRDF link.
● A mixture of R2 and non-RDF devices is allowed if the R2 devices are NR on the SRDF link.
● A mixture of R1 and R21 devices is allowed if the R1->R21 is NR on the SRDF link.
● A mixture of R2 and R21 devices is allowed, if the following criteria is met:
○ R1->R2 and R1->R21 devices are all RW on the SRDF link.
○ R1->R2 and R1->R21 are all NR on the SRDF link.
If the source devices do not meet these criteria then the snapshot cannot be created unless a force flag is used. Using a force
flag forces the snapshot to be created; however, the consistency of the snapshot cannot be guaranteed.

Snapshot policy
Snapshot policies enable users to request a stream of consistent snapshots be automatically taken on the local array for
applications based on a set of attributes and schedules. These multiple, frequent, consistent point-in-time copies of data or
snapshots protect your production data and allow you to recover from data corruption or other damage with minimal data loss.

NOTE: Snapshot policies are only supported on arrays running PowerMaxOS 5978.669.669 or higher.

Snapshot policies can be linked, relinked, restored, terminated similarly to manual snapshots by specifying the service level name
as snapshot name and snapsetID as absolute generation number to uniquely identify the snapshot and/or snapset. A snapset
refers to a set of consistent snapshots that are taken together. If for example, an SG contains 10 devices and a snapshot is
taken the result is a snapset with 10 consistent snapshots.
These automated snapshots are taken by the Services Daemon (storsrvcsd) based on the specified attributes and schedule.
For these details, refer to the Solutions Enabler Array Controls and Management CLI User Guide.

Rules
The following rules and restrictions apply to snapshot policies and their automated snapshots:
For Snapshot policies:
● Snapshot policies do not support taking crash consistent snapshots across multiple arrays. Only single array crash
consistency is supported.
● A maximum of 4 policies can be assigned to an SG.
● 20 Snapshot policies are supported per array.
● For cascaded SGs, snapshot policies can be assigned to both the parent and child SG. If the same snapshot policy is
assigned to both parent and child, the setting on the child is ignored. If a snapshot policy is assigned to the parent SG, it
applies across all its child SGs.
● Automated snapshots taken across these children are consistent. This means that a child SG can fall under as many as
8 policies: 4 from its parent and 4 from itself. If a snapshot policy is assigned to only the child SG, that policy applies to
only that child. If the same snapshot policy is assigned to two child SGs, but not their parent SG, snapshots are generated
independently for each of the child SGs.
● Snapshot policies can be suspended. Suspending a policy prevents new snapshots from being taken and prevents existing
snapshots from being terminated. Suspending snapshot policies can be performed either at the policy level (applying to all
SGs that it is associated with) or at individual SGs that the snapshot policy has been associated with (applying only to that
SG).
● Snapshot policies can be modified except for the following actions:
○ The secure snapshot attribute on a snapshot policy cannot be modified.
○ If a snapshot policy with the secure attribute is currently associated with SGs, its Interval and Maximum Count attributes
can be modified so long as their expected lifetime (TTL is the product of Interval times the Maximum count) does not
decrease.
● A snapshot policy can be deleted if it is not currently assigned to any SGs.

14 Introduction to TimeFinder SnapVX

● If a device no longer falls under a snapshot policy, the corresponding snapshots are put into a Pending Terminate state.
They are automatically terminated once their TTL, assigned at the time they were originally taken, expires. The TTL of the
automated snapshots when the snapshot policy is set up must be less than or equal to 400 Days.
● If a snapshot policy is deleted, any snapshots that were taken against it are put into an Orphaned state, and given the
_Orphaned name.
For Snapshot policy automated snapshots:
● A maximum of 1024 snapshots can be supported on a device if there are no other snapshots present. If legacy TimeFinder
sessions (symclone, vpsnap, symmir) or manual snapshots are on the device, then the number of automated snapshots on a
device equals 1024 minus the manual and legacy sessions.
● Automated snapshots are supported on both FBA and CKD devices.
● TTL cannot be set on individual automated snapshots. TTL is assigned upon taking the snapshot.
● Although renaming automated snapshots to another automated snapshot name is not allowed, the policy they were
generated from can be renamed. In this case, all its snapshots will automatically have the new name.
● Automated snapshots cannot be converted to a secure level snapshot. Secure snapshots can be created using secure
snapshot policies only.
● Automated snapshots can be set persistent but these snapshots can still be manually terminated by a user. Secure snapshots
on the other hand can only be terminated after its secure expiration time has expired.
● SnapVX control actions (except for bulk terminate) are not allowed on a mixture of manual and automated snapshots on
devices in one single request.
● Control actions are not allowed using relative generation numbers with the automated snapshots on the devices if the
request contains snapshots with different snapsetIDs.
● It is recommended to exercise caution when using both zDP and Solution Enabler to create snapshots on a device. Having
zDP and automated or manual snapshots on a device count towards the total number of sessions. As a result, this might limit
the number of the maximum count of the supported snapshot type.
● The expiration timestamp is displayed only for automated snapshots with the Pending Delete attribute.
● EXPIRED is displayed for secure snapshots or automated snapshots with Pending Delete state when the TTL expires.
● Orphaned snapshots cannot be renamed, but they can still be used for link and restore operations.

Expired snapshot rules

The following rules apply to both regular and secure expired snapshots.

Allowable Solutions Enabler operations:

● TTL can be set to a future date or to NONE (removes TTL).
● Secure expiration time can be set to a future date.
● Unlink and terminate restore operations are allowed on the snapshot.
● A regular snapshot can be converted to secure snapshot by specifying a secure expiration time.

Solutions Enabler operations not allowed:

● Running the restore, rename, link, relink, set copy mode operations.

Geometry Compatible Mode flag set issue with

SnapVX controls
Because TimeFinder requires that source and target devices be the same size, the GCM (Geometry Compatible Mode) flag can
get automatically set on the target device during SnapVX operations. This flag should be cleared on the device before mapping
it to a host, otherwise, in order to clear the flag it must be unmapped from the host, which results in a data outage.
The symdev, symdg, symcg, symsg commands have the set/unset -gcm option to set or unset GCM for a device
or group. Refer to the Solutions Enabler CLI Reference Guide for more information on using these commands with the -gcm
attribute.

Introduction to TimeFinder SnapVX 15

 2
Performing TimeFinder SnapVX Operations
This chapter describes how to perform Timefinder SnapVX operations.
Topics:
• Establish SnapVX snapshot
• Rename SnapVX snapshot
• Set SnapVX snapshot time to live (TTL)
• Set persistent SnapVX snapshot
• Convert SnapVX snapshot to secure snapshot
• Link a SnapVX snapshot
• Change SnapVX snapshot link mode
• Unlink SnapVX snapshot
• Relink SnapVX snapshot
• Restore SnapVX snapshot
• Terminate SnapVX snapshot

Establish SnapVX snapshot

Description
The symsnapvx establish command creates and activates a SnapVX snapshot.

Syntax
symsnapvx establish [-secure <-delta <delta_time> | -absolute <date_time>> |
-ttl <-delta <delta_time> | -absolute <date_time>>]
[-both_sides]
[-preaction <ScriptFile>] [-postaction <ScriptFile>]

Options
-name <SnapshotName>
Snapshot name - case sensitive, maximum length of 32 alphanumeric character, dash (-) and underscore
(_) are legal characters.
-ttl
Sets the time to live (TTL) for a snapshot either as a number of days plus hours or hours from the
current host time, or to an absolute date and time in the future. When the TTL expires a snapshot is
identified as expired. Only snapshots without links or restore sessions can be terminated. If the snapshot
has links or restore sessions, it is terminated when the last link is unlinked or the restore session is
terminated. TTL is set using the following options:
NOTE: Refer to the examples in Set SnapVX snapshot time to live (TTL) for TTL formatting rules.

-secure
Creates a secure snapshot with a secure expiration time for a snapshot either as a number of days plus
hours, or hours from the current host time, or an absolute date and time in the future. Use extreme
caution with this option. When the secure expiration time expires a snapshot is identified as expired.

16 Performing TimeFinder SnapVX Operations

 Only snapshots without links or restore sessions can be terminated. If the snapshot has links, it is
terminated when the last link is unlinked. Secure expiration time is set using the following options:
NOTE: Refer to the examples in Set SnapVX snapshot time to live (TTL) for formatting rules for
setting expiration time.
● -delta Days[:hours] — Sets secure expiration time to 1 – 400 days plus 0 –23 hours from
current host time. Day format is days:hh (for hours, only whole numbers are valid and 0 value is
optional).
● -absolute Date[:hour] — Sets secure expiration time to an absolute date in the future, up
to a date 400 days from current host date, plus 0 –23 hours. Date format is MM/DD/YYYY:HH (for
hours, only whole numbers are valid and 0 value is optional).
-both_sides
Valid with DG, SG, or CG. Performs SnapVX operation on both local and remote snapshots. The
following rules apply when using this option:
● A mixture of R1 and R2 devices is not allowed.
● All the RDF devices in the SG must be in same RDF group.
● RDF pairs must be must be in Synchronous RDF mode and in Synchronous state, or in Active RDF
mode and in ActiveActive or ActiveBias state.
-preaction <ScriptFile>
Executes the specified script before a snapshot is established.
-postaction <ScriptFile>
Executes the specified script after a snapshot is established, using the following options:
● -delta Days — Executes the specified script after 1 to 400 days.
● -absolute Date — Executes the specified script after a date that is up to 400 days in the future.

Examples
To establish a snapshot named 600am for the source devices specified in Storage Group1, enter:

symsnapvx -sid 001 -sg StorageGroup1 -name 600am establish

To establish a snapshot named 600am for source device 55, enter:

symsnapvx -sid 001 -dev 55 -name 600am establish

To establish a snapshot named 600am and automatically terminate it in 2 days 23 hours, enter:

symsnapvx -sid 001 -sg StorageGroup1 -name 600am establish -ttl -delta 2:23

To establish a secure snapshot named 600am and automatically terminate it at noon on June 1 2017, enter:

symsnapvx -sid 001 -sg StorageGroup1 -name 600am establish -secure -absolute
06/01/2017:12

Snapshot generations
Each time a new snapshot with the same name is created (on the same source device), the new snapshot becomes generation
0, and all of the previous generation numbers are incremented. SnapVX supports up to 256 manual snapshots per source device.
A device can have total of 1024 snapshots including manual and automated policy snapshots, and legacy TimeFinder snapshots.

Rename SnapVX snapshot

Description
The symsnapvx rename command renames a SnapVX snapshot.

Performing TimeFinder SnapVX Operations 17

 NOTE: An expired secure or regular snapshot cannot be renamed.

Syntax
symsnapvx -g <DgName> -snapshot_name <SnapshotName> rename -name <NewSnapshotName>

Examples
To rename a snapshot named 400am to 600am, enter:

symsnapvx -sid 001 -g DeviceGroup1 -snapshot_name 400am rename -name 600am

Set SnapVX snapshot time to live (TTL)

Description
Use the set ttl option to set the time to live for a regular snapshot either as a number of days from set time or an absolute
date in the future. Only snapshots without links or restore sessions can be terminated. If the snapshot has links it will be
terminated when the last link is unlinked.
NOTE: Once the TTL is set for snapshot it can only be extended forward in time and not set back in time. Refer to
Examples below for invalid TTL values.

Options
set ttl
Sets the TTL to the specified days, date or removes TTL, using the following options:
● -delta Days[:hours] — Sets TTL to 1 – 400 days plus 0 –23 hours from current host time.
Day Format is days:hours (for hours, only whole numbers are valid and 0 value is optional).
● -absolute Date[:hour] — Sets TTL to an absolute date in the future, up to a date 400 days
from current host date, plus 0 –23 hours. Date format is MM/DD/YYYY:hours (for hours, only whole
numbers are valid and 0 value is optional).
● -delta NONE - Removes TTL.
-snapshot name <SnapshotName>
Specifies the snapshot name.

Examples
To set the TTL for snapshot named 600am and automatically terminate it after 3 days 6 hours, enter:

symsnapvx set ttl -nop -dev 3b5 -snapshot_name 600am -sid 476 -delta 3:6

SetTimeToLive operation execution is in progress for the device range(s). Please wait...

Polling for SetTimeToLive.........................................Started.

Polling for SetTimeToLive.........................................Done.

SetTimeToLive operation successfully executed for the device range(s)

To set the TTL for snapshot named 600am and automatically terminate it at noon on June 1 2017, enter:

symsnapvx set ttl -nop -dev 3b5 -snapshot_name 600am -sid 476 -absolute 06/01/2017:12

18 Performing TimeFinder SnapVX Operations

 SetTimeToLive operation execution is in progress for the device range(s). Please wait...

Polling for SetTimeToLive.........................................Started.

Polling for SetTimeToLive.........................................Done.

SetTimeToLive operation successfully executed for the device range(s)

TTL command fails if attempting to set a secure snapshot back in time from the current setting (noon on June 1 2017):
NOTE: Setting TTL back in time is allowed for regular snapshots.

symsnapvx set ttl -nop -dev 3b5 -snapshot_name 600am -sid 476 -absolute 06/01/2017:0

Invalid option value entered: 6/01/17:0

TTL command fails if attempting to set both days and hours to 0:

symsnapvx set ttl -nop -dev 3b5 -snapshot_name 600am -sid 476 -delta 0:0

The time to live is invalid

TTL command fails if both days and hours are not set:

symsnapvx set ttl -nop -dev 3b5 -snapshot_name 600am -sid 476 -delta :5

Invalid option value entered: :5

symsnapvx set ttl -nop -dev 3b5 -snapshot_name 600am -sid 476 -delta 5:

Invalid option value entered: 5:

Set persistent SnapVX snapshot

Description
Automated policy snapshots can be made persistent by using the set persistent command. Once an automated snapshot is
made persistent, it will no longer be automatically terminated.

NOTE: Manual snapshots cannot be made persistent.

Syntax
To set or clear the persistent flag, use:

symsnapvx set <persistent| nopersistent>

Options
persistent
Sets the persistent flag on a policy snapshot that will not be terminated by count based auto termination
when creating new policy snapshot on a device.
nopersistent
Clears the persistent flag.

Performing TimeFinder SnapVX Operations 19

Examples
To make generation 5 of the 600am snapshot persistent on array 001, enter:

symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name 600am -gen 5 set persistent

To clear the persistent flag from generation 5 of the 600am snapshot on array 001, enter:

symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name 600am -gen 5 set nopersistent

Convert SnapVX snapshot to secure snapshot

Description
Use the set secure option to convert a regular snapshot to a secure snapshot with a secure expiration time. The secure
expiration time is set as either as a number of days plus hours, or hours, from the current host time, or to an absolute date
and time in the future. Only snapshots without links or restore sessions can be terminated. If the snapshot has links it will be
terminated when the last link is unlinked. If the snapshot has a restore session it will be terminated when the restore session is
terminated.
Also use this command to reset a secure snapshot either from a previous set secure or establish -secure operation,
however a subsequent set secure operation must set a time greater than current expiration time setting.

Options
set secure
Creates a secure snapshot with a secure expiration time for a snapshot either as a number of days
from the current day/time or an absolute date in the future. When the secure expiration time expires a
snapshot is identified as expired.
NOTE: Refer to the examples in Set SnapVX snapshot time to live (TTL) for formatting rules for
setting expiration time.
● -delta Days[:hours] — Sets secure expiration time to 1 – 400 days plus 0 –23 hours from
current host time. Day format is days:hh (for hours, only whole numbers are valid and 0 value is
optional).
● -absolute Date[:hour] — Sets secure expiration time up to a date 400 days from current host
date plus 0 –23 hours. Date format is MM/DD/YYYY:HH (for hours, only whole numbers are valid
and 0 value is optional).
-snapshot name <SnapshotName>
Specifies the snapshot name.

Examples
To set the secure expiration time for snapshot named 600am and automatically terminate it after 3 days 6 hours, enter:

symsnapvx set secure -nop -dev 3b5 -snapshot_name 600am -sid 476 -delta 3:6

To set the secure expiration time for snapshot named 600am and automatically terminate it at noon on June 1 2017, enter:

symsnapvx set secure -nop -dev 3b5 -snapshot_name 600am -sid 476 -absolute 06/01/2017:12

20 Performing TimeFinder SnapVX Operations

Link a SnapVX snapshot
Description
To access a point-in time-copy, create a link from the snapshot data to a host mapped target device. SnapVX supports up to
1,024 linked targets per source device. Links can be a permanent copy on a target device, or a temporary copy that no longer
retains the point-in-time copy of the data once the link is removed.
NOTE: An expired secure or regular snapshot cannot be linked.

Syntax
To create a link from snapshot data, use the following syntax:

symsnapvx -sid <SymmID> -sg <SgName> -lnsg <SgName>

-snap <snapshot_name>
–snapid <snapsetID>
[-generation <GenerationNumber>]
link [-copy [-remote]] [-exact]

Options
-lnsg
Specifies a SG name for target devices.
-generation
Specifies the generation number on the source SG.
-snapid
Specifies the snapsetID on the source SG.
-copy
Specifies copy mode for link operation which performs a background copy to the target device. SnapVX
uses Copy mode to create full-volume copies of the data by copying it to the target device's SRP. If
Copy mode is not specified when linking the snapshot, the NoCopy link is the default.
-remote
Data is propagated to the remote mirror of the RDF device.
-exact
Pairs source and link devices by their ordinal positions in the selection. If not set, pairs source and link
devices by best match.

Examples
To create a Copy mode link to generation 5 of the 600am snapshot, enter:

symsnapvx -sid 001 -sg StorageGroup1 -lnsg StorageGroup2

-snapshot_name 600am -gen 5 link -copy

It is possible to add volumes to an SG that has active snapshots. The new volumes are included the next time a snapshot is
taken. However, the volumes are not included in previously existing snapshots. Linking from a source device that does not have
the specified snapshot makes the corresponding target device not ready when the snapshot is from a different generation. This
is because there is no data on that target for that time, and the application should not be using that device. The user must
decide the best course of action to remove or reintroduce extra volumes. If the SG is relinked to a generation of the snapshot
that contains all volumes in the SG, the volumes are automatically made ready and included in the session.
SnapVX behavior when adding source devices provides additional details.

Performing TimeFinder SnapVX Operations 21

 NOTE: If using Dell EMC Storage Direct Data Domain systems, before Storage Direct can be used to backup the production
database, the TimeFinder SnapVX link copy command must be run between the production and the backup devices. Full
instructions are listed in the Dell EMC Storage Direct documentation set.

Restrictions
The following restrictions apply when linking to a target:
● When linking to devices do not use devices that are the target of another link copy or another TimeFinder session.
● Devices with persistent track allocations cannot be used as link targets, this includes restores.
● Any pre-existing data that was exclusive to the target is lost during a link or relink.
● The target device must be of equal or greater size than the source device.
NOTE: By default, SnapVX allows the target device to be larger than the source device. If necessary, this setting can
be disabled. The Dell EMC Solutions Enabler CLI Command Reference contains information on changing the Option file
parameters.

Change SnapVX snapshot link mode

NOTE: An expired secure or regular snapshot cannot be set to copy mode.

set mode <copy | nocopy>

Sets the mode of an existing link. Copy mode creates a full-volume copy of the data by copying it to the
target device's SRP. Once the link is removed, both modes retain the point-in-time data.
NOTE:
● The set mode <copy | nocopy> operation is blocked on arrays running PowerMaxOS 10 (6079) and higher.
● link nocopy is not supported on arrays running PowerMaxOS 10 (6079) and higher. The actual copy is done only if
src and tgt devs are in different SRPs.

Examples
To set the link mode to NoCopy for generation 5 of the 600am snapshot, enter:

symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name 600am -gen 5 set mode nocopy

Unlink SnapVX snapshot

Description
The symsnapvx unlink command unlinks a snapshot without relinking to a different snapshot.
NOTE: Allows the unlink of a link nocopy session when the session is defined and the target device is the source of another
snapshot. The data is guaranteed as long as the define is complete at the time of the unlink operation.

Options
-symforce
Forces the operation to execute when normally it is rejected. If used when a link is copy in progress or
when a restore is restore in progress, causes an incomplete copy and data on the copy target is not
usable.

22 Performing TimeFinder SnapVX Operations

Example
To unlink generation 6 of the 600am snapshot, enter:

symsnapvx -sid 001 -sg StorageGroup1 -lnsg StorageGroup2 -snapshot_name 600am -gen 6
unlink

Relink SnapVX snapshot

Description
An existing snapshot can be unlinked and relinked to a different snapshot from the same source device. To relink a snapshot, a
link must already exist on at least one of the targets. Relinking can also be used on the same snapshot, which has the effect of
refreshing the point-in-time copy on the link target if it has been modified by host writes.
NOTE: An expired secure or regular snapshot cannot be relinked.

Options
-lnsg
Specifies a SG name for target devices.
-generation
Specifies the generation number on the source SG.
-snapid
Specifies the snapsetID on the source SG.
-copy
Specifies copy mode for relink operation which performs a background copy to the target device. If the
relink is in Copy mode, the copy is differential between the original linked snapshot and the newly linked
snapshot.
-remote
Data is propagated to the remote mirror of the RDF device. Not allowed on a NoCopy linked target.
-exact
Pairs source and link devices by their ordinal positions in the selection. If not set, pairs source and link
devices by best match.

Examples
To relink (in Copy mode) to generation 6 of the 600am snapshot, enter:

symsnapvx -sid 001 -sg StorageGroup1 -lnsg StorageGroup2

-snapshot_name 600am -gen 6 relink -copy

Restore SnapVX snapshot

Use the symsnapvx restore command to restore a snapshot's point-in-time data back to the original source device. SnapVX
restore operations are inherently differential, so only the changed tracks are copied back to the source device. An expired
secure or regular snapshot cannot be restored.

NOTE: A restore session must be terminated before terminating the original snapshot session.

Performing TimeFinder SnapVX Operations 23

Options
-preaction <ScriptFile>
Executes the specified script before a snapshot is restored.
-postaction <ScriptFile>
Executes the specified script after a snapshot is restored.
-remote
Specifies data will be copied to the remote mirror of the RDF device. Not allowed on nocopy linked
target.
-snapid <snapsetID>
Executes a restore using the snapsetID instead of relative generation generation number.

Examples
To restore generation 5 of the 6:00 AM snapshot, enter:

symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name 600am -gen 5 restore

If a source device is added to a storage group, the added device is missing snapshots that were created before the new device
was added. If a restore is requested for a snapshot that is missing for a newly added device, this new device is made Not Ready,
and the application should not be using this device. SnapVX behavior when adding source devices provides additional details.

Terminate SnapVX snapshot

Description
Terminating a snapshot removes the it from the system. To terminate a snapshot it must have no linked devices or restore
sessions. To unlink a snapshot refer to Unlink SnapVX snapshot.

Syntax
For terminate, use:

symsnapvx -sid <SymmID> -sg <SgName> -snapshot_name <SnapshotName>

[-generation <GenerationNumber>] | [-snapid [<snapsetID>]]
...
terminate [-restored [-symforce]]
[[[-keep_count <Count>] |
[-older_than -snapid <SnapsetID>] | -all ] -force]

Options
-restored
Terminates restores.
-symforce
Forces the operation to execute when normally it is rejected.
-keep_count
Specifies the number of most recent snapshots to be kept when terminating snapshots. This option
must be used along with the -force option. This option can only be used for automated policy
snapshots only.
-older_than

24 Performing TimeFinder SnapVX Operations

 Specifies all the policy snapshots with the SnapsetID lower (older) than the specified SnapsetID. This
option must be used along with the -force option. This option can only be used for automated policy
snapshots only.
-snapid
Executes a terminate command using the snapsetID instead of relative generation generation number on
the source SG.
-all
Terminates all snapshots on the devices for the given snapshot name.
-force
Attempts to force the operation even though one or more devices may not be in the normal, expected
state(s) for the specified operation. This is required for bulk terminating snapshots.
-snapshot_name
Specifies the snapshot name to be terminated

Examples
To terminate generation 5 of the 600am snapshot, enter:

symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name 600am -gen 5 terminate

To terminate the restore of generation 5 of the 600am snapshot, enter:

symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name 600am -gen 5 terminate -restored

To terminate all automated and manual snapshots on the devices with the 600am snapshot name if they are not in use, enter:

symsnapvx terminate -sid 001 -snap 600am -sg StorageGroup1 -all -force

To keep 5 of the most recent automated snapshots and terminate older snapshots on the device/devices, enter:

symsnapvx terminate -sid 001 -snap 600am -sg StorageGroup1 –keep_count 5 -force

Bulk terminate SnapVX snapshots

Description
Bulk terminate remove multiple snapshots from the system at once. Snapshots must have no linked devices or restore sessions.
NOTE: To bulk terminate snapshots on devices, the -force flag is required.

Syntax
For bulk terminate, use:

symsnapvx -sid <SymmID> -sg <SgName>

...
terminate -all_snapshot_names -force

Options
-force
Attempts to force the operation even though one or more devices may not be in the normal, expected
state(s) for the specified operation. This is required for bulk terminating snapshots.

Performing TimeFinder SnapVX Operations 25

-all_snapshot_names
Terminate all snapshots on the devices. For this operation, the -force flag is required

Examples
To bulk terminate all snapshots on StorageGroup1, enter:

symsnapvx terminate -sid 001 -sg StorageGroup1 - all_snapshot_names –force

26 Performing TimeFinder SnapVX Operations

 3
TimeFinder SnapVX snapshot reporting
This chapter describes how display and verify Timefinder SnapVX snapshot status.
Topics:
• Display SnapVX snapshot status
• Verify SnapVX snapshot status

Display SnapVX snapshot status

Description
The symsnapvx list command displays the state of all snapshots and links on individual devices, a device file, device ranges,
device group, composite group, or storage group or on the entire array. To display link status for a group, devices must be
associated with the group.
NOTE: When using the symsnapvx list command in environments with Storage Direct Data Domain systems, if a link is
in a force failed state due to non-supported configuration, the Failed flag column contains an “F”, as shown in the examples
below.

NOTE: The offline option that specifies that the Symmetrix data connection is offline and the operation uses the host
in-memory database is not supported with symsnapvx list reports. You can get the report on demand from the array.

Syntax
To display snapshots information, use the following syntax:

symsnapvx -sid <SymmID> list [[-bgdefinprog] [-secured] [-manual] [-policy] [-cloud]

[-zdp] [-expired] [-persistent]] | [-linked [-by_tgt]] [-restored]

-snapshot_name <SnapshotName>
[-generation <GenerationNumber>] | [-snapid [<snapsetID>]]

-sg <SgName> [-detail] [-snapshot_name <SnapshotName> [-snapid <SnapsetID>]]

-aggregate [-manual] | [-policy]

Options
-detail
Expanded display that provides all snapshot information.
-failed
Displays only failed snapshots or links.
-last_n
Displays only the specified generations for each device.
-linked
Displays the links associated with the selected devices. Requires -sid option when requesting all linked
targets in the array.
-restored

TimeFinder SnapVX snapshot reporting 27

 Displays only restored snapshots. Requires -sid option when requesting all restored targets in the
array.
-by_tgt
Displays all snapshots ordered by link target device and links on individual devices, a device file, device
ranges, device group, composite group, or storage group.
-bgdefinprog
Displays only the snapshots that were created on a target device when background define process was
in progress and the define is not complete yet. This is avilable on PowerMaxOS. Using this option on
earlier systems returns the message "No snapshot was found".
-manual
Reports only manual snapshots.
-policy
Reports only Snapshot policy (automated) snapshots.
-cloud
Reports only cloud snapshots.
-presistent
Reports only persistent snapshots.
-zdp
Reports only zDP snapshots.
-expired
Reports only expired snapshots.
-secured
Displays only snapshots with secured attribute.
-summary
Displays the summary for the specified snapshots.
-snapid
Displays the absolute generation number (snapset ID) for snapshots.
-aggregate
Reports only snapset aggregate summary on a SG. If used with the -detail option, a new flag "X"
indicates if a snapset outside of window, or the gap between the two snapsets is larger than the policy
interval. If a snapset is both outside of window and has a gap, then the flag "M" is set to indicate that as
‘M’ for ‘Mixed’.

Examples
To display the snapshots for devices on array 476, enter:

symsnapvx list -sid 476

To display the snapshot detail for device 3AA on array 476, enter:

symsnapvx list -dev 3AA -sid 476 -detail

To display the snapshot for device 28AA with a zDP snapshot on array 56, enter:

symsnapvx list -sid 56 -dev 28aa

To display only the snapshots with the secured attribute on array 476, enter:

symsnapvx list -sid 476 -secured

To display the links associated with the device 140 on array 86, enter:

symsnapvx -sid 86 list -dev 140 -linked

28 TimeFinder SnapVX snapshot reporting

To display all snapshots with their absolute generation number (snapset ID) on array 86, enter:

symsnapvx list -sid 086 -sg finance_sg –detail -snapid

To display only the snapset aggregate summary on SG1 on array 84, enter:

symsnapvx list -sid 084 –sg SG1 –aggregate

To display detailed snapset aggregate summary on array 84, enter:

Symsnapvx list -sid 084 -sg SG1 -aggregate -detail

Sample output
To list all snapshots on array:

Symmetrix ID : 000196801476 (Microcode Version: 5977)

------------------------------------------------------------------------------
Sym Num Flags
Dev Snapshot Name Gens FLRG TSEB Last Snapshot Timestamp
----- -------------------------------- ---- --------- ------------------------

...
003AA Monday 4 S... ...X Mon Jul 13 14:42:45 2017
...

Flags:
(F)ailed : X = General Failure, . = No Failure
: S = SRP Failure, R = RDP Failure, I = Establish in progress
M = Mixed Failure
(L)ink : X = Link Exists, . = No Link Exists
(R)estore : X = Restore Active, . = No Restore Active
(G)CM : X = GCM, . = Non-GCM
(T)ype : Z = zDP snapshot, S = Policy snapshot, P = Persistent snapshot,
: C = Cloud snapshot, . = Manual snapshot
(S)ecured : X = Secured, . = Not Secured
(E)xpanded : X = Source Device Expanded, . = Source Device Not Expanded
(B)ackground: X = Background define in progress, . = No Background define

To list snapshots for a device on an array:

Symmetrix ID : 000197600056 (Microcode Version: 5978)

------------------------------------------------------------------------------
Sym Num Flags
Dev Snapshot Name Gens FLRG TSEB Last Snapshot Timestamp
----- -------------------------------- ---- --------- ------------------------
028AA _Automated_Snapshot 1 …. .... Fri Aug 31 07:55:19 2018

Flags:
(F)ailed : X = General Failure, . = No Failure
: S = SRP Failure, R = RDP Failure, I = Establish in progress
M = Mixed Failure
(L)ink : X = Link Exists, . = No Link Exists
(R)estore : X = Restore Active, . = No Restore Active
(G)CM : X = GCM, . = Non-GCM
(T)ype : Z = zDP snapshot, S = Policy snapshot, P = Persistent snapshot,
: C = Cloud snapshot, . = Manual snapshot
(S)ecured : X = Secured, . = Not Secured
(E)xpanded : X = Source Device Expanded, . = Source Device Not Expanded
(B)ackground: X = Background define in progress, . = No Background define

TimeFinder SnapVX snapshot reporting 29

With -detail option for specified device:

Symmetrix ID : 000196801476 (Microcode Version: 5977)

------------------------------------------------------------------------------
Sym Flags
Dev Snapshot Name Gen FLRG TSEB Snapshot Timestamp
----- -------------------------------- ---- --------- ------------------------
003AA Monday 0 .... ...X Mon Jul 13 14:42:45 2017
Monday 1 .... .... Mon Jul 13 14:42:00 2017

---------------------------------------------------------
Snapshot Total
Dev Size Deltas Non-Shared
(Tracks) (Tracks) (Tracks) Expiration Date
---------- ---------- ---------- ------------------------
240 0 0 NA
240 0 0 NA
---------- ----------
0 0

Flags:

(F)ailed : X = Failed, . = No Failure

(L)ink : X = Link Exists, . = No Link Exists
(R)estore : X = Restore Active, . = No Restore Active
(G)CM : X = GCM, . = Non-GCM
(T)ype : Z = zDP snapshot, . = normal snapshot
(S)ecured : X = Secured, . = Not Secured

With -secured option:

Symmetrix ID : 000196801476 (Microcode Version: 5977)

------------------------------------------------------------------------------
Sym Num Flags
Dev Snapshot Name Gens FLRG TSEB Last Snapshot Timestamp
----- -------------------------------- ---- --------- ------------------------
001BF Monday 2 ..X. .X.. Wed Oct 10 13:45:08 2016
003AA Monday 1 .X.. .X.. Mon Sep 26 11:28:09 2016

Flags:

(F)ailed : X = General Failure, . = No Failure,

S = SRP Failure, R = RDP Failure, M = Mixed Failure
(L)ink : X = Link Exists, . = No Link Exists
(R)estore : X = Restore Active, . = No Restore Active
(G)CM : X = GCM, . = Non-GCM
(T)ype : Z = zDP snapshot, . = normal snapshot
(S)ecured : X = Secured, . = Not Secured
(E)xpanded : X = Source Device Expanded, . = Source Device Not Expanded
(B)ackground: X = Background define in progress, . = No Background define

With -linked option:

Symmetrix ID : 000197100086 (Microcode Version: 5978)

--------------------------------------------------------------------------------
Sym Link Flags
Dev Snapshot Name Gen Dev FCMDS Snapshot Timestamp
----- -------------------------------- ---- ----- ----- ------------------------
00140 Friday 0 00141 S.... Fri Jul 21 08:24:52 2017
00140 Friday 0 00142 S.... Fri Jul 21 08:24:52 2017

Flags:

(F)ailed : F = Force Failed, X = General Failure, . = No Failure,

S = SRP Failure, R = RDP Failure
(C)opy : I = CopyInProg, C = Copied, D = Copied/Destaged, . = NoCopy Link
(M)odified : X = Modified Target Data, . = Not Modified

30 TimeFinder SnapVX snapshot reporting

 (D)efined : X = All Tracks Defined, . = Define in progress
(S)napshot : X = Has snapshot waiting for define to complete
. = No snapshot waiting for define to complete

All snapshots with their absolute generation number (snapset ID) on array:
Storage Group (SG) Name : finance_sg
SG's Array ID : 000197100084 (Microcode Version: 5978)

------------------------------------------------------------------------------------------------------------------------------------------------
Snapshot Total
Sym Flags Dev Size Deltas Non-Shared
Dev Snapshot Name Snapid FLRG TSEB Snapshot Timestamp (Tracks) (Tracks) (Tracks) Expiration Date

----- -------------------------------- ------------ --------- ------------------------ ---------- ---------- ---------- ------------------------

043B4 finance_fri 99912348000 .... .... Fri Feb 2 10:18:08 2018 16395 0 0
NA
finance_fri 99912347500 .... .... Fri Feb 2 10:17:27 2018 16395 0 0
NA
...
HR_Daily 99912346000 .... S... Fri Feb 2 09:00:00 2018 16395 0 0 NA
...
HR_weekly 99912345000 .... S... Wed Jan 31 14:30:37 2018 16395 0 0
NA
...
HR_weekly 99912340000 .... S... Wed Jan 01 14:30:37 2018 16395 0 0 NA

043B5 finance_fri 99912348000 .... .... Fri Feb 2 10:18:08 2018 16395 0 0
NA
finance_fri 99912347500 .... .... Fri Feb 2 10:17:27 2018 16395 0 0
NA
...
HR_Daily 99912346000 .... S... Fri Feb 2 09:00:00 2018 16395 0 0 NA
...
HR_weekly 99912345000 .... S... Wed Jan 31 14:30:37 2018 16395 0 0
NA
...
HR_weekly 99912340000 .... S... Wed Jan 01 14:30:37 2018 16395 0 0 NA

Flags:
(F)ailed : X = General Failure, . = No Failure
: S = SRP Failure, R = RDP Failure, I = Establish in progress
M = Mixed Failure
(L)ink : X = Link Exists, . = No Link Exists
(R)estore : X = Restore Active, . = No Restore Active
(G)CM : X = GCM, . = Non-GCM
(T)ype : Z = zDP snapshot, S = Policy snapshot, P = Persistent snapshot,
: C = Cloud snapshot, . = Manual snapshot
(S)ecured : X = Secured, . = Not Secured
(E)xpanded : X = Source Device Expanded, . = Source Device Not Expanded
(B)ackground: X = Background define in progress, . = No Background define

Snapset aggregate summary with the -aggregate option on array:

Storage Group (SG) Name : sg1

SG's Array ID : 000197100084 (Microcode Version: 5978)

Snapshot Name Num Last Snapshot Timestamp

Gens
-------------------------------- ---- ------------------------
HR_Daily_10AM 10 Fri Feb 2 10:00:01 2018
FinanceWeekly 1 Wed Jan 31 18:00:01 2018

Detailed snapset aggregate summary on array:

Storage Group (SG) Name : sg1

SG's Array ID : 000197100084 (Microcode Version: 5978)

-----------------------------------------------------------------------------------------
-
Flags Number
Snapshot Name Snapid FLRG TSEBX Snapshot Timestamp
Devices
-------------------------------- ------------- ---------- ------------------------
-------
HR_Daily_10AM 99912346800 .... S.... Fri Feb 2 10:00:01 2018
10
99912345500 .... S.... Thu Feb 1 10:00:01 2018
9
…
99912344000 .... S.... Wed Jan 24 10:00:01 2018
5
...

Flags:
(F)ailed : X = General Failure, . = No Failure
: S = SRP Failure, R = RDP Failure, I = Establish in progress
M = Mixed Failure

TimeFinder SnapVX snapshot reporting 31

 (L)ink : X = Link Exists, . = No Link Exists
(R)estore : X = Restore Active, . = No Restore Active
(G)CM : X = GCM, . = Non-GCM
(T)ype : Z = zDP snapshot, S = Policy snapshot, P = Persistent snapshot,
: C = Cloud snapshot, . = Manual snapshot
(S)ecured : X = Secured, . = Not Secured
(B)ackground: X = Background define in progress, . = No Background define
E(X)ception : O = Out of Window, G = Gap after, M = Mixed, . = No exception

Verify SnapVX snapshot status

Description
Use the symsnapvx verify command to verify snapshot and link states.

Options
-by_tgt
Verifies by link target.
-copyinprog
Verifies that link(s) are in the CopyInProg state.
-copied
Verifies that link(s) are in the Copied state.
-defined
Use with verify -linked, -restored and -restinprog to wait until all tracks have been
defined.
-destaged
Verifies that all tracks are written to the link target.
-established
Verifies that snapshot is in Established state.
-estinprog
Verifies that snapshot is in EstInProg state.
-linked
Verifies that nocopy links are in Linked state.
-restored
Verifies that snapshots are in the Restored state.
-restinprog
Verifies that snapshots are in RestoreInProgress state.
--summary
Displays summary of snapshot

Example
To verify that generation 2 of snapshot is in restored state, enter:

symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name snapshot -gen 2 verify -restored

All of the devices are in the restored state

32 TimeFinder SnapVX snapshot reporting

 4
TimeFinder SnapVX Configurations and
Examples
This chapter describes various TimeFinder SnapVX configurations and describes common uses for SnapVX.
Topics:
• Cascading SnapVX snapshots
• Modified SnapVX point-in-time copies
• SnapVX behavior when adding source devices
• Common uses for SnapVX snapshot configurations

Cascading SnapVX snapshots

The target device of a snapshot can be used as the source device for additional snapshots.
The figure below shows Snapshot B cascading off of the target of Snapshot A, where the target of Snapshot A is the source for
Snapshot B.

Source

Snapshot A Target

Snapshot B

Figure 1. Cascading snapshots

There are no architectural restrictions on the number of cascading hops, and multiple targets can be linked from any of the
snapshots.
If the linked target is in NoCopy mode, the cascading snapshot is considered a dependent snapshot. Target devices cannot be
unlinked without removing dependent snapshots (in the reverse order of their creation). However, the copy mode is changed to
Copy the target can be unlinked once link is fully copied.
A relink operation to a target with dependent snapshot is allowed, but if the relink is in NoCopy mode, the unlink is allowed only
if there are no new snapshots off of that target device.
For HYPERMAX OS, a linked target must be fully defined before you can create snapshots off of it. When a target is first linked,
all of the tracks are undefined. At this point the target does not know where in the SRP the track is located, and host access
to the target must be derived from the SnapVX metadata. A background process eventually defines the tracks and updates the
thin device to point directly to the track location in the source device's SRP. For PowerMaxOS, creating a snapshot off the link
target if the link is not defined, or when restore is in progress and not defined yet is allowed, however these snapshots can only
be used once they are fully defined.

TimeFinder SnapVX Configurations and Examples 33

Determine fully defined SnapVX snapshot

Examples
To display the linked targets for devices listed in file snapvx_devices, enter:

symsnapvx list -sid 001 -sg StorageGroup1 -linked

Sample output
The output lists only those snapshots that have fully defined linked targets. The (D) flag indicates if all of the tracks for a linked
target are defined.

Device File Name : snapvx_devices

Device's Symmetrix ID : 000197100001 (Microcode Version: 5977)
-------------------------------------------------------------------------------
Sym Link Flgs
Dev Snapshot Name Gen Dev FCMD Snapshot Timestamp
----- -------------------------------- ---- ----- ---- ------------------------
00123 Tuesday_account_400pm 1 01122 .C.X Tue Feb 12 16:00:15 2013
00123 Tuesday_account_400pm 1 01126 .D.X Tue Feb 12 16:00:15 2013
00124 Tuesday_account_400pm 1 01123 .IX. Tue Feb 12 16:00:15 2013
00125 Tuesday_account_400pm 1 01124 .I.. Tue Feb 12 16:00:15 2013
Flgs:
(F)ailed : X = Failed,. = No Failure
(C)opy : I = CopyInProg, C = Copied, D = Copied/Destaged, . = NoCopy Link
(M)odifed : X = Modified Target Data, . = Not Modified
(D)efined : X = All Tracks Defined, . = Define in progress

Modified SnapVX point-in-time copies

Host writes to a linked target device do not change the point-in-time copy, so only the linked target device contains a modified
point-in-time copy. To copy a modified point-in-time copy back the original source device, establish a snapshot from the target
device and then create a Copy mode link of that snapshot back to the source device.
The figure below shows an example of copying a modified point-in-time copy back to the source by linking (in Copy mode) a
snapshot of the linked target back to the source device.
link
Snapshot B

link
Source Snapshot A Target

Figure 2. Copying a modified point-in-time back to the source

SnapVX behavior when adding source devices

Over time, an application may grow (or shrink) the number of devices that it uses. SnapVX automatically adjusts restore, link,
and relink operations to accommodate extra or missing snapshot names and generations.
The figure below shows a storage group with three source devices. Source device 3 is added to the storage group after the first
snapshot (Mon 12pm) was established, so that snapshot does not exist for that device.

34 TimeFinder SnapVX Configurations and Examples

 Source Mon 12pm
1 Tues 12pm

Source Mon 12pm

2 Tues 12pm

Source
3 Tues 12pm

Source Storage Group

Figure 3. Storage group with two snapshots

SnapVX snapshot restore operations when adding source devices

As shown in the figure below, if the Mon 12pm snapshot is restored, the point-in-time data is copied back to source device 1 and
source device 2, but source device 3 is marked NR because there is no data on that device for that point-in-time.

Source Mon 12pm

1 Tues 12pm

Source Mon 12pm

2 Tues 12pm

NR
Tues 12pm

Source Storage Group

Figure 4. Source devices after a restore operation

SnapVX snapshot link operations when adding source devices

As shown in the figure below, if target devices are linked to the Mon 12pm snapshot, target device 1 and target device 2 are
linked to the snapshot, but target device 3 is marked NR because there is no data on that target for that point-in-time.

Source Mon 12pm Target

1 Tues 12pm 1

Source Mon 12pm Target

2 Tues 12pm 2

NR NR
Tues 12pm

Source Storage Group Target Storage Group

Figure 5. Target devices after a link operation

NOTE: The link command can only be used when there are no links to any of the targets. If linking in Copy mode, the result
is a full copy.

TimeFinder SnapVX Configurations and Examples 35

SnapVX relink operations when adding source devices
The relink operation can only be used if a link exists on at least one of the targets. In Copy mode, if a link already exists for a
particular target, the result is an incremental copy. If there is no existing link for a target, then the result is a full copy.
If relinking from a source device that has the selected snapshot and generation, but the target device does not have an existing
link, a new link is created and the result is a full copy.
If relinking from a source device that does not have the selected snapshot and generation, the target device is marked NR. If
the target has an existing link, it is unlinked.
If relinking from a source device that has the selected snapshot and generation, and the target device has a previous link, the
relink results in an incremental copy.

Common uses for SnapVX snapshot configurations

This section describes commonly used SnapVX configurations, including:
● Create targetless SnapVX snapshots and restore production volumes
● Refresh multiple test or development environments from a SnapVX linked target
● Provision test or development environments with cascading SnapVX snapshots

Create targetless SnapVX snapshots and restore production

volumes
In the following example, snapshots of all devices in a storage group are created and retained for 2 days. This provides for up to
2 days of snapshots without consuming any additional device numbers or the cache overhead.
To create snapshots, enter:

symsnapvx -sid 001 -sg StorageGroup1 -name snapshot establish -ttl -delta 2

To list snapshots, enter:

symsnapvx -sid 001 list -sg StorageGroup1 -snapshot_name snapshot -detail -GB

NOTE: In this example, to create snapshots every 15 minutes, use a script or schedule to run the symsnapvx establish
command at 15 minute intervals.
Output:

Storage Group (SG) Name : StorageGroup1

SG's Symmetrix ID : 000196700001 (Microcode Version: 5977)
------------------------------------------------------------------------

Total
Sym Flgs Deltas Non-Shared
Dev Snapshot Name Gen FLRG TSEB Snapshot Timestamp (Tracks) (Tracks) Expiration Date
----- -------------- ---- --------- ------------------------- ----- ------ ------------------
00212 snapshot 0 .... .... Mon Jun 15 16:15:00 2015 142 11 Tue Jun 17 16:15:00 2015
snapshot 1 .... .... Mon Jun 15 16:00:00 2015 222 11 Tue Jun 17 16:00:00 2015
snapshot 2 .... .... Mon Jun 15 15:45:00 2015 272 0 Tue Jun 17 15:45:00 2015
------ -------
636 22
Flags:

(F)ailed : X = General Failure, . = No Failure,

S = SRP Failure, R = RDP Failure,
(L)ink : X = Link Exists, . = No Link Exists
(R)estore : X = Restore Active, . = No Restore Active
(G)CM : X = GCM, . = Non-GCM
(T)ype : Z = zDP snapshot, . = normal snapshot
(S)ecured : X = Secured, . = No Secure
(E)xpanded : X = Source Device Expanded, . = Source Device Not Expanded
(B)ackground: X = Background define in progress, . = No Background define

NOTE: Data Protector for z Systems (zDP™) snapshots, created and managed through Mainframe Enabler products, are
reported in Solutions Enabler by the flag (T) when issuing the symsnapvx list command. Automated zDP snapshots

36 TimeFinder SnapVX Configurations and Examples

 taken by Mainframe Enabler are reported with the snapshot name _zDP_XYZ, where XYZ is the internal zDP schedule id
used by zDP for that snapshot.
Any of the snapshots created in the previous example can be used to restore the source volumes. Before issuing any restore,
unmount the source volume from the application server to ensure that the data is fully refreshed on the host. Before issuing any
restore, unmount the source volume from the application server to ensure that the data is fully refreshed on the host.
To restore directly to the production volumes from snapshot generation 2 taken at 15:45pm, enter:

symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name snapshot -gen 2 restore

Execute Restore operation for Storage Group StorageGroup1 (y/[n]) ? y

Restore operation execution is in progress for the storage group StorageGroup1. Please
wait...
Polling for Restore..................................................Started.
Polling for Restore..................................................Done.
Restore operation successfully executed for the storage group StorageGroup1

When the restore command completes, the volumes are read/write accessible to the host and the restored data is instantly
available to the host. Therefore, the production volumes can be remounted and used immediately, and copying of any remaining
tracks, from the snapshot delta to the source volume, is done as a background task. The snapshot data is always preserved and
can be used again for a future restore, if needed, so writing to the source volume while restore operation is still copying data
does not affect the snapshots.
Typically the restore command completes in a few seconds, but the time to complete is dependent on the number of devices
involved in the restore operation. Use the verify option to verify that all devices are restored.
To verify that the snapshot is restored, enter:

symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name snapshot -gen 2 verify -restored

All of the devices are in the restored state

To terminate the restore session, enter:

symsnapvx -sid 001 -sg StorageGroup1 -snapshot_name snapshot -gen 2 terminate -restored

Execute Terminate operation for Storage Group StorageGroup1 (y/[n]) ? y

Terminate operation execution is in progress for the storage group StorageGroup1. Please
wait...
Polling for Terminate.............................................Started.
Polling for Terminate.............................................Done.
Terminate operation successfully executed for the storage group StorageGroup1

Refresh multiple test or development environments from a SnapVX

linked target
SnapVX “links” enable access to point-in-time copies by linking snapshot data to a host mapped target device.
Use SnapVX to provision multiple test or development environments using linked snapshots. Each linked storage group can
access the same snapshot or each can access a different snapshot version in either no copy or copy mode. Changes to the
linked volumes do not affect the snapshot data. To roll back a test development environment to the original snapshot image,
simply perform a relink operation.
NOTE: Target volumes must be unmounted before issuing the relink command to ensure that the host operating system is
not caching any filesystem data. Once the relink is complete, volumes can be remounted. Snapshot data is unchanged by
the linked targets, so it can also be used for restoring to production.
In the following figure, multiple servers/organizations link to snapshots for different uses. Each target is independent, and
changes to one target does not affect the other targets.

TimeFinder SnapVX Configurations and Examples 37

 Production BACKUP_SG TEST_SG DEV_SG QA_SG ……
Up to 1024

Linked Target SGs

SOURCE
SG Targetless
Targetless
Snapshot
Targetless
Snapshot
Targetless
Snapshot
Snapshot
Up to 256 Snapshots

Figure 6. SnapVX targetless snapshots

Link snapshottargetless_snapshot to target devices shown in the above figure:

symsnapvx -sid 001 -sg StorageGroup1 -lnsg BACKUP_SG -snapshot_name targetless_snapshot

link

symsnapvx -sid 001 -sg StorageGroup1 -lnsg TEST_SG -snapshot_name targetless_snapshot

-gen 1 link

symsnapvx -sid 001 -sg StorageGroup1 -lnsg DEV_SG -snapshot_name targetless_snapshot

-gen 2 link

symsnapvx -sid 001 -sg StorageGroup1 -lnsg QA_SG -snapshot_name targetless_snapshot -gen
3 link

Refresh (rollback) QA_SG target device to the original snapshot image:

symsnapvx -sid 001 -sg StorageGroup1 -lnsg QA_SG -snapshot_name targetless_snapshot -gen
3 relink

This process can be repeated for any of the other test environments.

Provision test or development environments with cascading

SnapVX snapshots
When sensitive data needs to be presented to test or development environments, some data may require obfuscation to protect
the data before presenting it to the test or development hosts. A cascading snapshot from a linked target and linking targets
from the cascaded snapshot provides the obscured data environment.

38 TimeFinder SnapVX Configurations and Examples

 Host process to
obfuscate DEVSG1
SourceSG1 sensitive data

k
Production

in
el
Link DEVSG2

/R
Snapshot TGT_SG1

nk
Copy or

Li
Nocopy Mode
DEVSG3
Snapshot

……
……
Copy or
Nocopy Mode DEVSG X

Figure 7. SnapVX cascaded snapshots

The cascading snapshot configuration, shown in the figure above, provides the following:
● Snapshots of production volumes can be linked to a target storage group which is part of a masking view for presenting to
an interim host. The interim host processes the host data to obfuscate sensitive data such as social security numbers.
● A snapshot from the target storage group is linked to multiple environments, which see the snapshot image without security
concerns.
● A relink operation can be performed at any stage on the target storage groups to roll back to a pristine snapshot image.
● At any point in the chain, linked snapshots can be converted to full independent copies if the first level linked copy needs to
be refreshed with a newer snapshot image.
● When the test or development environments need to be refreshed, a new snapshot from the source LUN can be taken and
relinked to the target storage group (TGT_SG).
Create original snapshot src_snap:

symsnapvx -sid 001 -sg SOURCESG1 -name src_snap establish

Link snapshot src_snap to TGT_SG1:

symsnapvx -sid 001 -sg SOURCESG1 -lnsg TGT_SG1 -snapshot_name src_snap link

At this point, TGT_SG1 can be mounted and updated by host processes.

Create snapshot obfuscated_snap off of TGT_SG1:

symsnapvx -sid 001 -sg TGT_SG1 -name obfuscated_snap establish

Link obfuscated_snap to the multiple development target devices:

symsnapvx -sid 001 -sg TGT_SG1 -lnsg DEVSG1 -snapshot_name obfuscated_snap link

symsnapvx -sid 001 -sg TGT_SG1 -lnsg DEVSG2 -snapshot_name obfuscated_snap link

symsnapvx -sid 001 -sg TGT_SG1 -lnsg DEVSG3 -snapshot_name obfuscated_snap link

Any of the snapshots can be refreshed at any stage. For example, the following command reverts DEVSG2in the development
environment back to it's original state when it was first linked:

TimeFinder SnapVX Configurations and Examples 39

 NOTE: Unmount the volumes at the host side prior to the relink.

symsnapvx -sid 001 -sg TGT_SG1 -lnsg DEVSG2 -snapshot_name obfuscated_snap relink

This process can be repeated to support multiple versions of the snapshots.

To terminate the snapshots in the previous example:
NOTE: Terminating snapshots in cascaded configuration requires that child snapshots that have a dependency on a higher
level snapshot must first be unlinked and terminated before the parent level can be terminated.
1. Unmount the DEVSG volumes on hosts.
2. Unlink the DEVSG storage groups from obfuscated_snap snapshot.
3. Terminate snapshot obfuscated_snap.
4. Terminate the original snapshot src_snap.
5. Remount DEVSG volumes on hosts.

40 TimeFinder SnapVX Configurations and Examples

 5
TimeFinder SnapVX State Reference Rules
This chapter details the TimeFinder SnapVX operations supported for devices in various pair states.
Topics:
• Determine SnapVX states/SRDF and ORS operations interaction
• State rules for TimeFinder SnapVX operations with SRDF pair states
• TimeFinder SnapVX operations with ORS pair states
• State rules for source control operations with SnapVX and Clone source states
• State rules for source control operations with SnapVX and Clone source states

Determine SnapVX states/SRDF and ORS operations

interaction
This section describes how SnapVX states are determined. This identifies SnapVX source device states and determines whether
the device can be used with various SRDF and ORS operations.
Display examples for each active state are shown in SnapVX State Determination Examples.

TimeFinder SnapVX operations states

The following table describes the prerequisites, transient states, and final states for all SnapVX control operations.

Table 3. Prerequisites and states for SnapVX control operations.

Operation Prerequisite Transient State Final State
Establish None Establish In Progress Established
Restore Established Restore In Progress Restored

If the source device is a link

target, it must be fully copied
before initiating the restore
operation.

Terminate Established Terminate in Progress NA

Establish In Progress
Restore In Progress

Terminate with Restored NA NA

FLAG1_RESTORED
Setmode Copy Linked NoCopy Link Copy In Progress Link Copied
Setmode NoCopy Link Copy In Progress or Link NA Linked
Copied
Set secure Established NA Secure snapshot
If the snapshot is a
secure snapshot either from
a previous set secure
or establish -secure

TimeFinder SnapVX State Reference Rules 41

Table 3. Prerequisites and states for SnapVX control operations. (continued)
Operation Prerequisite Transient State Final State

operation, a subsequent set

secure operation must set
a time greater than current
expiration time setting.

Set TTL Established NA NA

Link Established NA Linked
Link with FLAG1_COPY Established Link Copy In Progress Link Copied
Unlink Linked or NA NA

Link Copied
If the target is the source
of another snapshot, the link
must be fully copied.

Relink Linked or NA Linked

Link Copied

Relink with FLAG1_COPY Linked or Link Copy In Progress Link Copied

Link Copied

Rename Established NA NA

Determine SnapVX states

The following table details the SnapVX CLIs that are used to determine SnapVX states.

Table 4. Determine SnapVX State

SnapVX State SnapVX CLI Determine State

Established symsnapvx list The flags field indicates:

(F)ailed: = . for No Failure

Restore In Progress symsnapvx list -restored The Done(%) field is not at 100%
-detail

Restored symsnapvx list -restored The Done(%) field is at 100%

-detail

Terminate in Progress symsnapvx list The snapshot is still seen on the display.
Terminated symsnapvx list The snapshot is not seen on the display.
Failed symsnapvx list The flags field indicates:
(F)ailed:
● :X = General Failure
● . = No Failure
● :S = SRP Failure
● :R = RDP Failure
● :M = Mixed Failure

Link Copy In Progress symsnapvx list -link [-tgt] The flags field indicates:
-detail
(C)opy = I for CopyInProg

42 TimeFinder SnapVX State Reference Rules

Table 4. Determine SnapVX State (continued)
SnapVX State SnapVX CLI Determine State

The Done (%) field is not at 100%

Using -tgt is optional.

Link Copied symsnapvx list -link [-tgt] The flags field indicates:
-detail
(C)opy = C for Copied or D
for Copied/Destaged
The Done (%) field is at 100%
Using -tgt is optional.

Linked symsnapvx list -linked The flags field indicates :

(C)opy = . for NoCopy Link

Secured symsnapvx list -secured Secured snapshots seen on the display

SnapVX State Determination Examples

Established

#> symsnapvx -cg Sparrow -snapshot_name Bailey list

Composite Group (CG) Name : Sparrow

CG's Type : ANY
Number of Symmetrix Units : 1
CG's Symmetrix ID : 000197300076 (Microcode Version: 5977)
------------------------------------------------------------------------------
Sym Flags
Dev Snapshot Name Gen FLRG TSEB Snapshot Timestamp
----- -------------------------------- ---- --------- ------------------------
000A0 Bailey 1 .... Fri Oct 24 15:51:19 2014
000A1 Bailey 1 .... Fri Oct 24 15:51:19 2014

Flags:

(F)ailed : X = General Failure, . = No Failure,

S = SRP Failure, R = RDP Failure,
(L)ink : X = Link Exists, . = No Link Exists
(R)estore : X = Restore Active, . = No Restore Active
(G)CM : X = GCM, . = Non-GCM
(T)ype : Z = zDP snapshot, . = normal snapshot
(S)ecured : X = Secured, . = No Secure
(E)xpanded : X = Source Device Expanded, . = Source Device Not Expanded
(B)ackground: X = Background define in progress, . = No Background defined

Restore in Progress

#> symsnapvx -cg Sparrow -sna Bailey list -restored -detail

Composite Group (CG) Name : Sparrow

CG's Type : ANY
Number of Symmetrix Units : 1
CG's Symmetrix ID : 000197300076 (Microcode Version: 5977)
----------------------------------------------------------------------------
Sym Flgs Remaining Done
Dev Snapshot Name Gen FDS Snapshot Timestamp (Tracks) (%)
----- ------------------ ---- ------ ------------------------ ---------- -----

TimeFinder SnapVX State Reference Rules 43

 000A0 Bailey 0 ... Fri Oct 24 15:51:18 2014 72206 47
000A1 Bailey 0 ... Fri Oct 24 15:51:18 2014 0 100

Flgs:

(F)ailed : X = General Failure, . = No Failure,

S = SRP Failure, R = RDP Failure, M = Mixed Failure
(D)efined : X = All Tracks Defined, . = Define in progress
(S)napshot : X = Has snapshot waiting for define to complete
. = No snapshot waiting for define to complete

Restored

#> symsnapvx -cg Sparrow -sna Bailey list -restored -detail

Composite Group (CG) Name : Sparrow

CG's Type : ANY
Number of Symmetrix Units : 1
CG's Symmetrix ID : 000197300076 (Microcode Version: 5977)
--------------------------------------------------------------------------------
Sym Flgs Remaining Done
Dev Snapshot Name Gen FDS Snapshot Timestamp (Tracks) (%)
----- ----------------- ----- -------- -------------------------- -------- -----
000A0 Bailey 0 ... Fri Oct 24 15:51:18 2014 0 100
000A1 Bailey 0 ... Fri Oct 24 15:51:18 2014 0 100

Flgs:

(F)ailed : X = General Failure, . = No Failure,

S = SRP Failure, R = RDP Failure, M = Mixed Failure
(D)efined : X = All Tracks Defined, . = Define in progress
(S)napshot : X = Has snapshot waiting for define to complete
. = No snapshot waiting for define to complete

Link Copy in Progress

#> symsnapvx -cg Sparrow -sna Bailey list -linked -detail

Composite Group (CG) Name : Sparrow

CG's Type : ANY
Number of Symmetrix Units : 1
CG's Symmetrix ID : 000197300076 (Microcode Version: 5977)
--------------------------------------------------------------------------------
Sym Link Flgs Remaining Done
Dev Snapshot Name Gen Dev FCMDS Snapshot Timestamp (Tracks) (%)
----- --------------- ----- ----- ------ ----------------------- ---------- ----
000A0 Bailey 0 000B0 .I... Fri Oct 24 15:51:19 2014 118579 14
000A1 Bailey 0 000B1 .I... Fri Oct 24 15:51:19 2014 128275 7

Flgs:

(F)ailed : F = Force Failed, X = Failed, . = No Failure

(C)opy : I = CopyInProg, C = Copied, D = Copied/Destaged, . = NoCopy Link
(M)odified : X = Modified Target Data, . = Not Modified
(D)efined : X = All Tracks Defined, . = Define in progress
(S)napshot : X = Has snapshot waiting for define to complete
. = No snapshot waiting for define to complete

Link Copied

#> symsnapvx -cg Sparrow -sna Bailey list -linked -detail

Composite Group (CG) Name : Sparrow

CG's Type : ANY
Number of Symmetrix Units : 1

44 TimeFinder SnapVX State Reference Rules

 CG's Symmetrix ID : 000197300076 (Microcode Version: 5977)
--------------------------------------------------------------------------------
Sym Link Flgs Remaining Done
Dev Snapshot Name Gen Dev FCMDS Snapshot Timestamp (Tracks) (%)
----- --------------- ----- ----- ----- ------------------------ -------- ------
000A0 Bailey 0 000B0 .D.X. Fri Oct 24 15:51:18 2014 0 100
000A1 Bailey 0 000B1 .D.X. Fri Oct 24 15:51:18 2014 0 100

Flgs:

(F)ailed : F = Force Failed, X = Failed, . = No Failure

(C)opy : I = CopyInProg, C = Copied, D = Copied/Destaged, . = NoCopy Link
(M)odified : X = Modified Target Data, . = Not Modified
(D)efined : X = All Tracks Defined, . = Define in progress
(S)napshot : X = Has snapshot waiting for define to complete
. = No snapshot waiting for define to complete

Linked

#> symsnapvx -cg Sparrow -sna Bailey list -linked

Composite Group (CG) Name : Sparrow

CG's Type : ANY
Number of Symmetrix Units : 1
CG's Symmetrix ID : 000197300076 (Microcode Version: 5977)
--------------------------------------------------------------------------------
Sym Link Flgs
Dev Snapshot Name Gen Dev FCMDS Snapshot Timestamp
----- -------------------------------- ---- ----- ----- ------------------------
000A0 Bailey 0 000B0 ..... Fri Oct 24 15:51:18 2014
000A1 Bailey 0 000B1 ..... Fri Oct 24 15:51:18 2014

Flgs:

(F)ailed : F = Force Failed, X = Failed, . = No Failure

(C)opy : I = CopyInProg, C = Copied, D = Copied/Destaged, . = NoCopy Link
(M)odified : X = Modified Target Data, . = Not Modified
(D)efined : X = All Tracks Defined, . = Define in progress
(S)napshot : X = Has snapshot waiting for define to complete
. = No snapshot waiting for define to complete

State rules for TimeFinder SnapVX operations with

SRDF pair states
This section identifies the symsnapvx control operations that are available for SRDF pair states.

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 5. SRDF pair states

State Description
ActiveActive The R1 and the R2 are currently in the default SRDF/Metro
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.

TimeFinder SnapVX State Reference Rules 45

Table 5. SRDF pair states (continued)
State Description
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
available.
● 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.

46 TimeFinder SnapVX State Reference Rules

TimeFinder SnapVX R1 source
The following table identifies the SnapVX control operations that are allowed on R1 source device while SRDF is in various pair
states.

Table 6. SnapVX control operations allowed on R1 source by SRDF state

SRDF state

R1 updinprog
Partitioned1

Partitioned2

TransmitIdle
Sync in prog

Syncronized

ActiveActive
R1 updated
Suspended

Failed over

Consistent

ActiveBias
Invalid
Split
SnapVX Control operation
Establish Y a,b Y Y b Y b Y b Y b N Y N N Y a,b Y Y Y
Restore Y Y c Y Y N Y N N N N Y a,c Y a,c N N
a,c,d

Terminate Y Y Y Y Y Y Y Y Y Y Y Y Y Y

a. Action is not allowed if there are local invalids on the R1 side or remote invalids on the R2 side.
b. Not allowed on both sides of operation.
c. The remote option (-remote) must be applied.
d. Not allowed if the devie is part of an SRDF/Metro configuration.

NOTE: The Partitioned1 pair state indicates that the remote array is in the SYMAPI database and was discovered. The
Partitioned2 pair state indicates the remote array is not in the SYMAPI database and was not discovered, or was removed
from this database.

TimeFinder SnapVX State Reference Rules 47

TimeFinder SnapVX R2 source
The following table identifies the SnapVX control operations that are allowed on R2 source device while SRDF is in various pair
states.

Table 7. SnapVX control operations allowed on R2 source by SRDF state

SRDF state

R1 updinprog
Partitioned1

Partitioned2

TransmitIdle
Sync in prog

Syncronized

ActiveActive
R1 updated
Suspended

Failed over

Consistent

ActiveBias
Invalid
Split
SnapVX Control operation
Establish N Y a Y b,c Y c Y c Y c N Y c Y c N Y c N Y Y
Restore N N Y b Y b Y b Y b N N N N N N N N
Terminate Y Y Y Y Y Y Y Y Y Y Y Y Y Y

a. Not allowed if Adaptiv Copy.

b. Not allowed if target device is an R2 larger than the R1..
c. Not allowed on both sides operation.

NOTE: The Partitioned1 pair state indicates that the remote array is in the SYMAPI database and was discovered. The
Partitioned2 pair state indicates the remote array is not in the SYMAPI database and was not discovered, or was removed
from this database.

TimeFinder SnapVX R1 target

The following table identifies the SnapVX control operations that are allowed on R1 target device while SRDF is in various pair
states.

Table 8. SnapVX control operations allowed on R1 target by SRDF state

SRDF state
R1 updinprog
Partitioned1

Partitioned2

TransmitIdle
Sync in prog

Syncronized

ActiveActive
R1 updated
Suspended

Failed over

Consistent

ActiveBias
Invalid
Split

SnapVX Control operation

Link/Relink Y Y b,d Y d Y d N Y d N N N N Y Y N N
a,b,c,d a,b,d a,b,d

Link/Relink Copy Y Y b Y Y N Y N N N N Y a,b Y a,b N N

a,b,c

Unlink Y Y Y Y Y Y Y Y Y Y Y Y Y Y

a. Action is not allowed if there are local invalids on the R1 side or remote invalids on the R2 side.
b. The remote (-remote) option must be applied.
c. Not allowed if the device is part of an RDF/Metro configuration.
d. Only allowed if the array is running PowerMaxOS 5978.669.669.

TimeFinder SnapVX R2 target

The following table identifies the SnapVX control operations that are allowed on R2 target device while SRDF is in various pair
states.

48 TimeFinder SnapVX State Reference Rules

Table 9. SnapVX control operations allowed on R2 target by SRDF state
SRDF state

R1 updinprog
Partitioned1

Partitioned2

TransmitIdle
Sync in prog

Syncronized

ActiveActive
R1 updated
Suspended

Failed over

Consistent

ActiveBias
Invalid
Split
SnapVX Control operation
Link/Relink Copy N N Y a Y a Y b,a Y a N N N N N N N N
Terminate Y Y Y Y Y Y Y Y Y Y Y Y Y Y

a. Not allowed if target device is an R2 larger than the R1.

b. Not allowed if Async.

NOTE: The Partitioned1 pair state indicates that the remote array is in the SYMAPI database and was discovered. The
Partitioned2 pair state indicates the remote array is not in the SYMAPI database and was not discovered, or was removed
from this database.

TimeFinder SnapVX operations with ORS pair states

Only the SnapVX terminate command is allowed on the SnapVX source or target device that has ORS rcopy push or pull
sessions. The rcopy operation can be in the following states:
● None
● Create in prog
● Created
● Copy in progress
● Copy on write
● Copied
● Recreate in progress
● Recreated
● Terminate in Progress
● Failed
● Invalid
● Verify in progress
● Restore in progress
● Restored
● Precopy
● Sync in prog
● Syncronized
● Stopped

State rules for source control operations with SnapVX

and Clone source states
This section identifies the source control operations that are available for SnapVX and TimeFinder/Clone source states.

TimeFinder/Clone operations on a SnapVX source

The following table identifies the allowable TimeFinder/Clone operations (A->B) of SnapVX Source (A).
Allowed operations are noted by Ys.

TimeFinder SnapVX State Reference Rules 49

Table 10. Allowed TimeFinder/Clone operations (A->B) of SnapVX Source (A)
Clone Source Control SnapVX Source States (A)
Operations (A -> B)

No snapshot

Establish in progress

Restored

Failed
Established

Restore in prog

Terminate in prog
Create Y Y Y
Recreate Y Y Y
Activate Y Y Y
Full Establish Y Y Y
Incremental Establish Y Y Y
Set Mode Copy a Y Y Y
Set Mode Nocopy a Y Y Y
Set Mode Precopy a Y Y Y
Full Restore Y Y Y
Incremental Restore Y Y Y
Split Y Y Y
Terminate Y Y Y Y Y Y Y

a. This action is not supported on arrays running PowerMaxOS 10 (6079).

SnapVX source operations off Clone source

The following table identifies the allowable SnapVX Source (A) operations off Clone Source (A).
Allowed operations are noted by Ys.

Table 11. Allowed SnapVX Source (A) operations off Clone Source (A)
Snapvx Clone Source Pair States (A->B)
Source
Split
Copy on access
Copy in progress
Restored

Precopy

Copied

Restored

Failed
Created

Invalid
No session

Recreated

Copy on write

Restore in prog
Create in prog

Terminate in prog

Control
Operatio
n ( A-B):

Establish Y Y Y Y Y Y Y Y Y Y
Restore Y Y Y Y Y Y Y Y Y Y
Terminat Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
e
Rename Y Y Y Y Y Y Y Y Y Y Y Y
Set Y Y Y Y Y Y Y Y Y Y Y Y
secure/
TTL

50 TimeFinder SnapVX State Reference Rules

Table 11. Allowed SnapVX Source (A) operations off Clone Source (A) (continued)
Snapvx Clone Source Pair States (A->B)
Source

Split
Copy on access
Copy in progress
Restored

Precopy

Restored
Created

Copied

Failed
Invalid
No session

Recreated

Copy on write

Restore in prog
Create in prog

Terminate in prog
Control
Operatio
n ( A-B):

Link/ Y Y Y Y Y Y Y Y Y Y Y Y
Relink
Unlink Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
Set Mode Y Y Y Y Y Y Y Y Y Y Y Y

VP Snap operations on a SnapVX source

The following table identifies the allowable VP Snap operations (A->B) of SnapVX Source (A).
Allowed operations are noted by Ys.

Table 12. Allowed VP Snap operations (A->B) of SnapVX Source (A)

VP Snap Source - Target SnapVX Source States (A)
Operations (A -> B)
Establish in progress

Restored

Failed
No session

Established

Restore in prog

Terminate in prog
Create Y Y Y
Recreate Y Y Y
Activate Y Y Y
Full Establish Y Y Y
Incremental Establish Y Y Y
Incremental Restore Y Y Y
Terminate Y Y Y Y Y Y Y

7SnapVX operations on a VP Snap source

The following table identifies the allowable SnapVX Source (A) operations off VP Snap Source (A).
Allowed operations are noted by Ys.

TimeFinder SnapVX State Reference Rules 51

Table 13. Allowed SnapVX Source (A) operations off VP Snap Source (A)
Snapvx Source Control VP Snap Source->Target States (A->B)
Operation (A):

Copied

Restored

Failed
Created

Invalid
No session

Recreated

Copy on write

Restore in prog
Establish Y Y Y Y Y
Restore Y Y Y Y Y
Terminate Y Y Y Y Y Y Y Y Y
Rename Y Y Y Y Y Y
Set secure/TTL Y Y Y Y Y Y
Link/Relink Y Y Y Y Y Y
Unlink Y Y Y Y Y Y Y Y Y
Set Mode Y Y Y Y Y Y

TimeFinder/Mirror operations on a SnapVX source

The following table identifies the allowable TimeFinder/Mirror operations (A->B) on SnapVX Source (A).
Allowed operations are noted by Ys.

Table 14. Allowed TimeFinder/Mirror operations (A->B) on SnapVX Source (A)

TimeFinder/Mirror SnapVX Source States (A)
STD->BCV Operations
No snapshot

Establish in progress

Restored

Failed
Established

Restore in prog

Terminate in prog
(A -> B)

Full Establish Y Y Y
Incremental Establish Y Y Y
Split Y Y Y
Full Restore Y Y Y
Incremental Restore Y Y Y
Cancel Y Y Y Y Y Y Y

SnapVX operations on a TimeFinder/Mirror source

The following table identifies the allowable SnapVX Source (A) operations off TimeFinder/Mirror Source (A).
Allowed operations are noted by Ys.

52 TimeFinder SnapVX State Reference Rules

Table 15. Allowed SnapVX Source (A) operations off TimeFinder/Mirror Source (A)
Snapvx TimeFinder/Mirror STD->BCV Pair States (A->B)
Source

Split
Split no incremental

Split before sync

Restored

Split before restore

Syncronized
Never Established

Restore in prog
Sync in prog

Split in prog
Control
Operati
on (A):

Establish Y Y
Restore Y Y
Terminat Y Y Y Y Y Y Y Y Y Y
e
Rename Y Y
Set Y Y
secure/
TTL
Link/ Y Y
Relink
Unlink Y Y Y Y Y Y Y Y Y Y
Set Y Y
Mode

State rules for source control operations with SnapVX

and Clone source states
This section identifies the source control operations that are available for SnapVX and TimeFinder/Clone source states.

ODM/OR target is TimeFinder/Clone source

The following table shows the ODM/OR actions that are allowed based on the TimeFinder/Clone states when the ODM target
device is also an TF/Clone source

Table 16. ODM/OR target is TimeFinder/Clone source

ODM/OR Clone Source States
Control
Split
Copy on access
Copy in progress
Precopy

Copied

Restored

Failed
Created

Invalid
No session

Recreated

Copy on write

Restore in prog
Create in prog

Terminate in prog

Operation

cancel Y

recover
(CancelinProg/
CancelFailed)

commit Y Y Y Y Y Y Y Y Y Y Y

TimeFinder SnapVX State Reference Rules 53

Table 16. ODM/OR target is TimeFinder/Clone source (continued)
ODM/OR Clone Source States
Control

Split
Copy on access
Copy in progress
Precopy

Copied

Restored

Failed
Created

Invalid
No session

Recreated

Copy on write

Restore in prog
Create in prog

Terminate in prog
Operation

recover
(CommitInProg/
CommitFailed)

Create (not Y
allowed)
recover
(CreateInProg/
CreateFailed)

recover Y Y Y Y Y Y Y Y Y Y Y

(MigrateFailed)

cutover Y

recover
(CutoverInProg/
CutoverFailed)

ODM/OR target is TimeFinder/SnapVX source

The following table shows the ODM/OR actions that are allowed based on the TimeFinder/SnapVX states when the ODM/OR
target device is also a TimeFinder/SnapVX source.

Table 17. ODM/OR target is TimeFinder/SnapVX source

ODM/OR SnapVX source states
control
operations
No snapshot Establish in Established Restore in Restored Terminate in Failed
prog prog prog

cancel Y

recover
(CancelInProg
/
CancelFailed)

commit Y Y Y Y

recover
(CommitInPro
g/
CommitFailed
)

create (not Y
allowed)

54 TimeFinder SnapVX State Reference Rules

Table 17. ODM/OR target is TimeFinder/SnapVX source (continued)
ODM/OR SnapVX source states
control
operations
No snapshot Establish in Established Restore in Restored Terminate in Failed
prog prog prog

recover
(CreateInProg
/
CreateFailed)

recover Y Y Y Y

(MigrateFaile
d)

cutover Y

recover
(CutoverInPro
g/
CutoverFailed
)

TimeFinder/Clone source is ODM/OR target

The following table shows the TimeFinder/Clone actions that are allowed based on the ODM/OR states when the ODM/OR
target device is also a TimeFinder/Clone source.

Table 18. TimeFinder/Clone source is ODM/OR target

TimeFi DM states
nder/
Clone
control
operati
ons

Create/ Y Y Y
recreat
e
Activat Y Y Y
e
Establis Y Y Y
h
Termina Y Y Y
te
Restore
Split Y Y Y

TimeFinder SnapVX State Reference Rules 55

TimeFinder/SnapVX source is ODM/OR target
The following table shows the TimeFinder/SnapVX actions that are allowed based on the ODM/OR states when the ODM/OR
target device is also a TimeFinder/SnapVX source.

Table 19. TimeFinder/SnapVX source is ODM/OR target

TimeFinder/ DM states
Clone control
operations

Establish Y Y Y
Restore
Terminate Y Y Y

56 TimeFinder SnapVX State Reference Rules

Index
A set persistent SnapVX snapshot 19
set snapvx time to live 18, 20
audience 7 Snapshot policy 14
SnapVX added or removed source devices 34
SnapVX interaction rules 41
B SnapVX link operations 35
bulk terminate SnapVX snapshot 25 SnapVX relink operations 36
SnapVX restore operations 35
support information 7
C
cascading SnapVX snapshots 33 T
change snapvx snapshot link mode 22
comments 7 terminate SnapVX snapshot 24, 34
consistent snapvx snapshot 13, 15 TimeFinder cli overview 12
conventions for publication 7 TimeFinder SnapVX configurations 12
create SnapVX snapshots 36 TimeFinder SnapVX introduction 10–12
TimeFinder SnapVX operating modes 12

D
U
display snapshot status 27
unllink snapvx snapshot 22

E
V
establish SnapVX snapshot 16
verfity snapshot state 32

G
GCM flag behavior 15

L
link snapvx snapshot 21

M
modified SnapVX copies 34

O
ORS pair state rules 49

P
preface 7
provision test environments 38

R
refresh test environments 37
related documentation 7
relink snapvx snapshot 23
rename snapshot 17
restore snapvx snapshot 23

S
secure snapvx snapshot 12