SYMMETRIX CLONE OPERATION

Steps for SYM CLONE operation:

·              Create a device group

symdg create DGNAME  -type regular

·              Add production devices to device group

symld -g DGNAME    add dev 00C3:00DB

symld -g DGNAME add dev 022B:03F3

·              Check information about the device group

symdg show DGNAME

·              Add clone devices to device group

symld -g DGNAME add dev 1A03:1A1B -tgt

symld -g DGNAME add dev  1AD3:1C9B -tgt

·              Check information about the device group

symdg show DGNAME

·              Create a clone copy session

symclone -g DGNAME create -exact -differential -precopy –tgt  

(For additional allocation)

symclone -g DGNAME create -differential -precopy –tgt  DEV063  SYM ld TRG063

precopy      : Starts copying tracks in the background

differential : For subsequent cloning to the same target i.e. incremental

·              Verify the clone session

symclone -g DGNAME verify

·              Query the clone copy session

symclone -g DGNAME query

·              Put the Oracle database in hot back-up mode

·              Activate the clone session

symclone -g DGNAME activate -tgt

·              Verify the clone session

symclone -g DGNAME verify

·              Query the clone copy session

symclone -g DGNAME query

·              Bring the Oracle database out of hot back-up mode

·              Verify the clone session

symclone -g DGNAME verify -copied

Check for status – All of the devices in group ' DGNAME' are in the 'Copied' state

·              Query the clone copy session

symclone -g DGNAME query

Check for the copied state of the device pair

·              Confirm the clone devices are visible on back-up host and as required. Do the needful configuration on the back-up host. Initiate back-up.

·              Confirm back-up completion.

Do the needful configuration on the back-up host.

·              Recreate the clone session

symclone -g DGNAME recreate -precopy –tgt

Changed tracks since the last activate action will be copied over to the target device i.e. incremental changes.

·              Verify the clone session

symclone -g DGNAME verify

·              Query the clone copy session

symclone -g DGNAME query

Hitachi Virtual storage Platform(VSP) Architecture

Major Improvements:

* 3D Scaling: Scale Up

                    Scale Out

                    Scale Deep

*Major Controller Architecture Design.

*High Performance SAS Back-end (SAN attached storage)

*Better storage Capacity and Better I/O Performance.

*Improved Heat Management.

Enhance 3D Scaling:

Scale Up: It describes how Hitachi VSP Architecture supports seamless capacity upgrades in single Controller Chassis System. Additional Cache,Processing,Storage & Connectivity can be added Non-disruptively.

Scale Out: it describes how VSP seamlessly grow to a two control chassis configuration that

delivers the greatest storage capacity, I/O performance & Power utilization.

Scale Deep: Describes Hitachi's Virtualization in the controller. Capability to connect & manage virtualized storage.

Supports 247 of external virtualized storage.

Has 1 or 2 Engine. Each Engine is one DKC

One Controller Chassis:

VSP Control chassis fully modular.

One Control Chassis supports one or two VSD(Microprocessor blades) pairs.

One Control chassis supports two or four cache memory features from 16GB to 256 GB.

The internal controller architecture is like Histar-E network because of internal components & interconnections of VSP.

Internal Controller Architecture

The DKC ==> Disk Controller is made up these five main Components.

FED,BED,Chache,Grid Switch & Microprossers.

VSD Board(Microprosser Blades):

Two to Four Chassis.

   Each board includes one intel 2.33 GHz core dual intel Xeon CPU with four processor blades, independent of CHAs and DKAs and can be shared across BEDs and FEDs.

     

VSD This is the Shared/Control Memory component of the VSP, called the Virtual Storage Directors.

VSD Board

·         GSW – Grid Switches:

•        Full duplex switches

•        Min of 2 switches to a maximum of 4

•        Provides interconnection between the FEDs, BEDs and the CMs.

•        They also connect the control signals between the virtual storage directors (MPs) and the CM boards.

SVPs – 2 – Both SVPs mounted Controller Chassis 0

Contains HDD or SDD drives 8 SAS switches

 Two Types of Drive Chassis:

• 80 disks capable 3.5” HDDs & Max number of 3.5” HDDs – 1280

 • 128 Disks capable 2.5” HDDs or SSDs &Max number of 2.5” HDDs - 2048 .

Maximum Configuration:

• 6 Rack twin version of the minimum configuration, containing 2 controller chassis, up to 16 drive   chassis .

•        The total space of the highest configuration is 2.5 PB.

•        Maximum number of Volumes supported – 64K .

•        Maximum Size of creatable volume = 4TB(60TB meta).