Sei sulla pagina 1di 9

EMC Symmetrix Timefinder survival guide

December 10, 2010 Juan Manuel 3 comments

During a previous project I had the opportunity to work very closely with the EMC people and Symmetrix arrays, in fact I got a couple of very good friends from that project. At the time I created a bunch of text files for my self reference about EMC SRDF and Timefinder technologies. Today I decided to review that files, give them some order, well sort of, and put them here as a survival guide/quick reference in the hope that will be of help to any of you. The first of this guides will be about EMC Symmetrix Timefinder. I dont have sample output for every command, been more than a year since the last time I work with Timefinder, to complement my own samples I got several outputs from the Timefinder manuals. This is not a complete Timefinder usage guide, just my personal notes taken from my direct experience with product. Timefinder Basics EMC Timefinder is a replication solution that creates full volume copies. For the full-HP guys out there this is very similar to the XP or EVA Business Copy product. There are two basic types of replication:

TimefinderClone Creates point-in-time copies. Timefinder/Snap Creates pointer-based replicas, snapshots, only the changed data is written.

There are several optional components.


Timefinder/Mirror. Timefinder/CG (Consistency Groups) Timefinder/EIM (Exchange Integration Modules) Timefinder/SIM (SQL Integration Modules)

Timefinder allows to retain multiple copies at different checkpoints for lowered RPO and RTO. Symcli basics Following is a list of the most basic symcli commands necessary to get your way around when you perform any Symmetrix task, including Timefinder.

- Get the list of the Symmetrix devices


root:/# symdev list Symmetrix ID: 00029xxxxxxx Device Name Directors Device --------------------------- ------------- -----------------------------------Cap Sym Physical SA :P DA :IT Config Attribute Sts (MB) --------------------------- ------------- -----------------------------------0000 Not Visible ???:? 01A:C0 BCV Asst'd RW 8632 0001 Not Visible ???:? 16C:D0 BCV Asst'd RW 8632 0002 Not Visible ???:? 01B:D0 BCV Asst'd RW 8632 0003 Not Visible ???:? 16D:C0 BCV Asst'd RW 8632 0048 Not Visible ???:? ???:?? VDEV N/Grp'd RW 8632 0049 Not Visible ???:? ???:?? VDEV N/Grp'd RW 8632 004A Not Visible ???:? ???:?? VDEV N/Grp'd RW 8632 004B Not Visible ???:? ???:?? VDEV N/Grp'd NR 8632 004C Not Visible ???:? ???:?? VDEV N/Grp'd NR 8632 004D Not Visible ???:? ???:?? VDEV N/Grp'd NR 8632 004E Not Visible ???:? ???:?? VDEV N/Grp'd NR 8632 004F Not Visible ???:? ???:?? VDEV N/Grp'd NR 8632 0050 Not Visible ???:? ???:?? VDEV N/Grp'd NR 8632 0051 Not Visible ???:? ???:?? VDEV N/Grp'd NR 8632 0052 Not Visible ???:? 16B:D1 2-Way Mir N/A (SV) RW 8632 0053 Not Visible ???:? 01C:C0 2-Way Mir N/A (SV) RW 8632 0054 Not Visible ???:? 16B:C0 2-Way Mir N/A (SV) RW 8632

- List all available devices from a device group


root:/# symld -g dg_oradev_01 list

- List host physical devices


root:/# sympd list

- List the disk groups:


root:/# /usr/symcli/bin/symdg list D E V I C E Name dg_oracle_prod1 dg_oracle_prod2 dg_rac_01 dg_clvx_01 dg_oradev_01 dg_timetest_02 grupo1 root:/# Type REGULAR REGULAR RDF1 RDF1 REGULAR RDF1 RDF1 Valid Yes Yes Yes Yes Yes Yes Yes G R O U P S Symmetrix ID 00029xxxxxxx 00029xxxxxxx 00029xxxxxxx 00029xxxxxxx 00029xxxxxxx 00029xxxxxxx 00029xxxxxxx Devs 26 21 23 5 3 16 22 Number of GKs BCVs VDEVs 0 0 0 0 0 0 0 26 21 23 5 0 16 0 0 0 0 0 0 0 0

- Add devices to a disk group

Add physical devices

root:/# symld -g dg_oradev_01 add pd /dev/dsk/c2t4d12

Add Symmetrix devices

root:/# symld -g dg_oradev_01 add 006E

- Get diskgroup detailed info.


root:/# /usr/symcli/bin/symdg show dg_prod_01 Group Name: dg_prod_01 : : : : : : : RDF1 (RDFA) No Yes 00029xxxxxxx Mon Nov 29 18:49:29 2007 EMC Corp ECC 2 0 2 0 0 0

Group Type Device Group in GNS Valid Symmetrix ID Group Creation Time Vendor ID Application ID Number Number Number Number Number Number of of of of of of

STD Devices in Group : Associated GK's : Locally-associated BCV's : Locally-associated VDEV's : Remotely-associated VDEV's(STD RDF): Remotely-associated BCV's (STD RDF):

Number of Remotely-associated BCV's (BCV RDF): Number of Remotely-assoc'd RBCV's (RBCV RDF) :

0 0

Standard (STD) Devices (2): { -------------------------------------------------------------------Sym Cap LdevName PdevName Dev Att. Sts (MB) -------------------------------------------------------------------DEV001 N/A 01C8 RW 8714 DEV002 N/A 01C9 RW 8714 } BCV Devices Locally-associated (2): { -------------------------------------------------------------------Sym Cap LdevName PdevName Dev Att. Sts (MB) -------------------------------------------------------------------BCV001 N/A 08A8 RW 8714 BCV002 N/A 08A9 RW 8714 } Device Group RDF Information { RDF Type RDF (RA) Group Number Remote Symmetrix ID

: R1 : 2 : 000287xxxxxx

(01)

R2 Device Is Larger Than The R1 Device : False RDF Pair Configuration RDF STAR Mode RDF RDF RDF RDF Mode Adaptive Copy Adaptive Copy Write Pending State Adaptive Copy Skew (Tracks) : Normal : False : : : : Synchronous Disabled N/A 32767

RDF Device Domino RDF Link Configuration RDF Link Domino Prevent Automatic RDF Link Recovery Prevent RAs Online Upon Power ON Device RDF Status Device RA Status Device Link Status Device Suspend State Device Consistency State RDF R2 Not Ready If Invalid Device RDF State

: Disabled : : : : Fibre Disabled Disabled Enabled (RW) (RW) (RW)

: Ready : Ready : Ready : N/A : Disabled : Disabled : Ready

(RW)

Remote Device RDF State RDF Pair State ( R1 <===> R2 )

: Write Disabled : Synchronized : 0 : 0

(WD)

Number of R1 Invalid Tracks Number of R2 Invalid Tracks RDFA Information: { Session Number Cycle Number Number of Devices in the Session Session Status Session Consistency State Minimum Cycle Time Average Cycle Time Duration of Last cycle Session Priority

: : : : : : : : :

1 0 491 Inactive N/A 00:00:30 00:00:00 00:00:00 33

Tracks not Committed to the R2 Side: 0 Time that R2 is behind R1 : 00:00:00 R1 Side Percent Cache In Use : 0 R2 Side Percent Cache In Use : 0 } } root:/#

Timfinder commands - Associate BCVs to a device group. There are two ways:
root:/# symbcv -sid xxxx -g dg_oradev_01 associate dev 0001

- Establish the mirrors


root:/# symmir -g dg_oradev_01 -full establish DEV001 BCV001

- Split operations.
root:/# symmir -g dg_oradev_01 split

There are several additional split modes and/or modifiers.

Instant

root:/# symmir -g dg_oradev_01 split -instant

Force

root:/# symmir -g dg_oradev_01 split -force

Differential

root:/# symmir -g dg_oradev_01 split -differential

Reverse

root/# symmir -g dg_oradev_01 reverse split

Reverse differential

root:/# symmir -g dg_oradev_01 reverse split -differential

- Restore the BCV mirrors. The restore operation will copy the data from the BCV to the Standard device.

Differential restore

root:/# symmir -g dg_oradev_01 restore

Full restore

root:/# symmir -g dg_oradev_01 -full restore

- Reestablish operations. It is very important to tell the difference between Restore and Reestablish. Reestablish will do a differential update from the Standard device to the BCV device.
root:/# symmir -g dg_oradev_01 establish

- Get the list of BCV devices


root:/# symbcv list Symmetrix ID: 00029xxxxxxx BCV Device Standard Device Status ------------------------------------ --------------------------- -----------Inv. Inv. Physical Sym RDF Att. Tracks Physical Sym Tracks BCV <=> STD ------------------------------------ --------------------------- -----------Not Visible 0030 (M) 0 N/A N/A 0 NeverEstab Not Visible 0031 (m) - N/A N/A - NeverEstab c4t1d0s2 0088 0 c4t0d0s2 0084 0 Split c4t1d1s2 0089 0 c4t0d1s2 0085 0 Split c4t1d2s2 008A 0 c4t0d2s2 0086 0 Split c4t1d3s2 008B 0 c4t0d3s2 0087 0 Split

- Get the state of mirroring of the device pairs within a device group

root:/# /usr/symcli/bin/symmir -g dg_oracle_prod_01 query Device Group (DG) Name: dg_oracle_prod_01 DG's Type : RDF1 DG's Symmetrix ID : 00029xxxxxxx Standard Device BCV Device State -------------------------- ------------------------------------- -----------Inv. Inv. Logical Sym Tracks Logical Sym Tracks STD <=> BCV -------------------------- ------------------------------------- -----------DEV001 DEV002 DEV003 DEV004 DEV005 DEV006 DEV007 DEV008 DEV009 DEV010 DEV011 Total Track(s) MB(s) Legend: (*): The paired BCV device is associated with this group. root:/# 0184 0186 0187 0188 0189 018E 018F 0190 0191 01C7 01CD 0 0 0 0 0 0 0 0 0 0 0 ------0 0.0 BCV001 BCV002 BCV003 BCV004 BCV005 BCV006 BCV007 BCV008 BCV009 BCV010 BCV011 039C 039E 039F 03A0 03A1 03A6 03A7 03A8 03A9 08A7 08AA * * * * * * * * * * * 0 0 0 0 0 0 0 0 0 0 0 ------0 0.0 Split Split Split Split Split Split Split Split Split Split Split

- List all BCV sessions in a Symmetrix array


root:/# symmir list -sid xxxx Symmetrix ID: 00000000xxxx Standard Device -------------------Invalid Sym Tracks -------------------002B 0 002E 0 002E 0 0032 0 00FF 0 0DF5 0 0DF5 0 0F70 0 0F71 0 0F93 0 1015 0 BCV Device ----------------------Invalid GBE Sym Tracks ----------------------0E0B 0 ... 0E00 0 ..X 0E0A 0 ... 0E0F 0 ... 00FD 0 ... 0DA5 0 ..X 0DA4 0 ..X 001B 3592 X.. 001C 4496 X.. 0DF9 0 ..X 1069 0 X.. State -------------STD <=> BCV -------------Synchronized Synchronized Synchronized Split Split Synchronized Synchronized SyncInProg SyncInProg Split Synchronized

Total Tracks MB(s)

-------0 0.0

-------8088 505.5

And we are done. As I said this is not a full guide so please if there is anything that you dont get please leave a comment and I will try to clarify. Also if any of you have additional tips or recipes for Timefinder please comment :-) Juanma.

Share this:

inShare0 More

Like this:
Like Be the first to like this. Categories: EMC, Storage Tags: BCV, EMC, EMC Timefinder, Storage, symcli, Symmetrix

Howto identify the EMC LUN ID in HP-UX 11iv3 Symmetrix arrays


May 10, 2010 Juan Manuel 3 comments DISCLAIMER NOTE: This method is based only on my personal experience working with HP-UX 11iv2, 11iv3 and EMC Symmetrix. I tested it with near a hundred LUNs from a DMX-3 and with six different servers. As far as I know this isnt an official or supported procedure neither from EMC nor from HP. Every time the storage people add a new LUN to your servers from an EMC disk array they provide you with a Logical device ID (or LUN ID) to identify the disk with PowerPath. If you are in HP-UX 11iv2 no problem here, just run a simple powermt command and look for the new LUN.
[root@totoro] / # powermt display dev=all | more ... ... Symmetrix ID=000281150123 Logical device ID=0CED state=alive; policy=SymmOpt; priority=0; queued-IOs=0

============================================================================= = ---------------- Host --------------- Stor -- I/O Path - -- Stats -### HW Path I/O Paths Interf. Mode State Q-IOs Errors ============================================================================= = 20 0/0/10/1/0.11.15.0.0.1.3 c7t1d3 SP A0 active alive 0 1 23 0/0/10/1/0.11.47.0.0.1.3 c8t1d3 SP B0 active alive 0 1 26 1/0/8/1/0.21.15.0.0.1.3 c10t1d3 SP A1 active alive 0 1 29 1/0/8/1/0.21.47.0.0.1.3 c11t1d3 SP B1 active alive 0 1 ... ...

But if you are in 11.31 you will find a small problem to perform this. PowerPath is not recommended in HP-UX 11iv3 because it can cause conflicts with the new native multiplathing of the v3. You can use the trick of doing a simple ll -tr in the /dev/disk directory just after the hardware scan and the device file creation, but this way is valid only if you have one or two disks with the same size. What if you have several disks with multiple sizes and want to use each disk for a different VG and/or task? The storage people will only provide the LUN IDs but you will not have the tool to match those IDs with your disks. Fortunately there is way to circumvent the lack of PowerPath in 11iv3. We are going to use the same disk as in the previous example, the 0CED. First get the disks serial number with scsimgr.
[root@totoro] / # scsimgr get_attr -D /dev/rdisk/disk30 -a serial_number SCSI ATTRIBUTES FOR LUN : /dev/rdisk/disk30 name = serial_number current = "100123CED000" default = saved =

Take note of the serial number. 100123CED000 As you can see the last the last three digits of the LUN ID are included in the disk serial number and if look carefully will see also the four last digits the Symmetrix ID (0123) just after the LUN ID. Juanma.

Potrebbero piacerti anche