Cloning a Copy of a STD to other BCV Using SYMCLI

 

Topic

Managing TimeFinder

Selections

Select TimeFinder Action: Managing TimeFinder with Solutions Enabler SYMCLI

Select operating system: Solaris

Select a task: Managing TimeFinder/Clone

Select a task: Cloning a copy of a STD to a BCV

 

 

Contents

·             TimeFinder/Clone Standard to BCV.. 4

 


 

 

·        TimeFinder/Clone Standard to BCV 

 

Overview

In the following TimeFinder/Clone example, the data from three source (STD) devices is copied to three target (BCV) devices. A device group is used to control these clone operations.

 

This procedure is based on content from the following EMC manual:

·         EMC Solutions Enabler Symmetrix TimeFinder Family Product Guide

 

You can download the guide from EMC Online Support (registration required): https://support.EMC.com

 

 

1.   

Select devices

To list the devices on the Symmetrix array, enter:

 

   symdev –sid SymmID list

 

Select the devices to use for the clone operation. This example will use standard devices 101, 102, and 103, and BCV devices 215, 216, and 217.

 

 

2.   

Create the device group

Use the symdg command to create a device group. This example names the device group clonegrp:

 

   symdg create clonegrp –type regular

 

 

3.   

Add the standard devices to the device group

Add the source and target devices to the device group. In the following example the devices are added using the –range option, as follows:

 

  symld –g clonegrp addall dev –range 101:103 –sid 0041

 

By default, their logical device names will be DEV001, DEV002, and DEV003, respectively.

 

 

4.   

Associate the BCV devices

The following command associates three BCV devices (0215, 0216, and 0217) with the device group.

symbcv -g clonegrp associateall dev -range 215:217

 

 

5.   

Check the device group for existing copy sessions

Use the symclone query command to check the device group for any current copy sessions.

 

symclone -g clonegrp query

 

The sample output from this command follows:

 

Device group 'clonegrp' does not have any devices that are Clone source devices

 

 

6.   

Create the clone copy session

The following command, by default, creates CopyOnAccess copy sessions for the standards and BCVs, pairing them in the order that they were added to the device group (for example, the first standard device, 0101, with the first BCV device, 0215).

 

   symclone -g clonegrp create -v -noprompt

 

'Create' operation execution is in progress for device group 'clonegrp'.
Please wait...

 

'Create' operation successfully executed for device group 'clonegrp'.

 

 

7.   

Activate the clone copy session

Use the symclone activate command to activate the clone copy session.

 

   symclone -g clonegrp activate

 

 

8.   

Query the clone copy session

Use the symclone query command to display the clone pairs and to show the changed state of each (from Created to CopyOnAccess).

 

   symclone -g clonegrp query

 

Device Group (DG) Name: clonegrp

DG's Type             : REGULAR

DG's Symmetrix ID     : 000187900041

 

      Source Device          Target Device       State     Copy

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

                Protected

Logical   Sym   Tracks    Logical     Sym  CG SRC <=> TGT  (%)

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

 

DEV001    0101     138090 BCV001      0215 .X CopyOnAccess   0

DEV002    0102     138090 BCV002      0216 .X CopyOnAccess   0

DEV003    0103     138090 BCV003      0217 .X CopyOnAccess   0

Total            --------

  Track(s)         414270

  MB(s)           12945.9

 

Legend:

 

(C): The background copy setting is active for this pair.

(G): The Target device is associated with this group.

 

 

9.   

Terminate the clone copy sessions

Use the symclone terminate command to end the clone pair sessions of all three clone pairs in the device group.

 

   symclone -g clonegrp terminate

 

The symclone query command with the –multi option checks the device group for any current copy sessions. Because all copy sessions for devices in the device group were stopped, the output confirms that there are no longer any clone devices in the group.

 

Device group 'clonegrp' does not have any devices that are Clone source devices

 

 

 

7Table of Contents