hitachi virtual storage platform g1000 hitachi universal ... · product version contents getting...

Product Version

Contents

Getting Help

FASTFIND LINKS

Hitachi Virtual Storage Platform G1000Hitachi Universal Replicator User Guide

MK-92RD8023-02

Hitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

ii

© 2014 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users.

Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at https://portal.hds.com.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation.

Notice on Export Controls: The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server,ESCON, FICON, FlashCopy, IBM, HyperSwap, Lotus, MVS, RS/6000, S/390,System z9, System z10, Tivoli, VM/ESA, z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of International Business Machines Corporation.>

All other trademarks, service marks, and company names in this document or website are properties of their respective owners.

Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

https://portal.hds.com

iiiHitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiIntended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiProduct version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiRelease notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiDocument revision level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiChanges in this revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiReferenced documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiDocument conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiConvention for storage capacity values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xivAccessing product documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvGetting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvComments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

1 Universal Replicator overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Universal Replicator software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2How Universal Replicator works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Hardware and software components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Hitachi Virtual Storage Platform G1000 storage systems . . . . . . . . . . . . . . 1-5Pair volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Journal volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Splitting Mirrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Resynchronizing a mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Deleting a mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Data path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Consistency groups and journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Device Manager - Storage Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Command Control Interface (CCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Overview of copy operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Initial copy operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10


iv

Update copy operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Read and write I/O during remote copy. . . . . . . . . . . . . . . . . . . . . . . . . 1-11Differential data management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11S-VOL write option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Pair status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

2 Requirements and specifications . . . . . . . . . . . . . . . . . . . . . . . . . 2-1System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

3 Planning volumes, VSP G1000 systems. . . . . . . . . . . . . . . . . . . . . 3-1Plan and design workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Assessing business requirements for data recovery . . . . . . . . . . . . . . . . . . . . 3-3

Determining your RPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Write-workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Measuring write-workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Data transfer speed considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

RAID group configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Fibre-channel port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Sizing journal volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Planning journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Planning journal volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Planning pair volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Maximum number of pairs allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Calculating maximum number of pairs . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Maximum initial copy operations and priorities . . . . . . . . . . . . . . . . . . . . 3-10Disaster recovery considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Host failover software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Sharing volumes with other VSP G1000 software volumes. . . . . . . . . . . . . . . 3-12Planning UR in multiple VSP G1000s using a consistency group . . . . . . . . . . . 3-12Planning for previous models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Guidelines for preparing systems for UR . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

System option modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

4 Planning the data path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Data path design workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Sizing bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Five sizing strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Calculating bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Sizing bandwidth for peak write-workload . . . . . . . . . . . . . . . . . . . . . . 4-3Sizing bandwidth for peak rolling average write-workload . . . . . . . . . . . 4-4Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Packet loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Planning ports for data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Port types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

vHitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

Cable length and switch requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Supported data path configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

5 UR configuration operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Configuration workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Defining fibre-channel port attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Configuring primary and secondary systems for UR . . . . . . . . . . . . . . . . . . . . 5-3Configuring additional remote paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Creating journals and adding journal volumes . . . . . . . . . . . . . . . . . . . . . . . . 5-6Assigning an MP blade to a journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

6 UR pair operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Pair operations workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Checking pair status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Creating the UR initial copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Splitting UR pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Splitting mirrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Creating point-in-time copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Resynchronizing UR pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Resynchronizing mirrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10Deleting UR pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Deleting pairs in a mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13

7 Monitoring the UR system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Monitoring pair activity, status, license capacity . . . . . . . . . . . . . . . . . . . . . . . 7-2

Pair status definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Additional information on pair status . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6UR PSUS types and behaviors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7UR PSUE types and behaviors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Monitoring UR pair synchronous rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Monitoring UR operations history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Operation descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Saving pair information to a text file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Monitoring journal (mirror) status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Device Manager - Storage Navigator mirror status definitions. . . . . . . . . . 7-13CCI mirror status definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Monitoring UR remote connections, path status . . . . . . . . . . . . . . . . . . . . . . 7-14

8 Maintaining the UR system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Pair maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Changing number of copies allowed per initial copy operation . . . . . . . . . . 8-2Changing pair options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Forcibly deleting pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3


vi

Journal and mirror maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Changing options used by journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Changing options used by mirrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Adding an additional journal volume to an existing journal . . . . . . . . . . . . 8-8Replacing a journal volume in a journal . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Deleting journal volumes from a journal . . . . . . . . . . . . . . . . . . . . . . . . 8-10Deleting journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Remote path maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12Modifying data-transfer time threshold . . . . . . . . . . . . . . . . . . . . . . . . . 8-12Deleting remote paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12Deleting the UR relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

Managing power-off for systems and network devices . . . . . . . . . . . . . . . . . 8-14When power stops unexpectedly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15

When power is removed from primary or secondary system . . . . . . . . 8-15When power is removed from network relay devices . . . . . . . . . . . . . 8-15

Powering-off systems intentionally . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15Powering-off the primary or secondary system . . . . . . . . . . . . . . . . . . 8-15Powering-off primary and secondary systems at the same time . . . . . . 8-16

Powering-off network relay devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

9 UR disaster recovery operations . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2General recovery procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Preparing for recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Preparing for file and database recovery . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Switching host operations to the secondary site . . . . . . . . . . . . . . . . . . . 9-3Reversing copy direction from secondary to primary site . . . . . . . . . . . . . 9-3Resuming host operations at the primary site . . . . . . . . . . . . . . . . . . . . . 9-4

Recovery for 3DC UR/TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5Recovery for 3DC UR/TC cascade configuration . . . . . . . . . . . . . . . . . . . . 9-5Recovery for 3DC UR/TC multi-target configuration . . . . . . . . . . . . . . . . . 9-5

Recovering from primary site failure . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6Recovering from primary and secondary site failure (3DC multi-target) . . 9-7

Recovery in a delta resync configuration . . . . . . . . . . . . . . . . . . . . . . . . . 9-8Problems with pair status during delta resync recovery . . . . . . . . . . . . . 9-9

Recovery in a 2DC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9Recovery for UR/SI configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

10 UR troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1General troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2Remote paths status problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3Troubleshooting by suspension type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6Troubleshooting hardware problems affecting pairs . . . . . . . . . . . . . . . . . . . 10-7Troubleshooting with CCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9Service information messages (SIMs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-23

viiHitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

Miscellaneous troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23Delta resync operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23Suspension among journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23

Calling the Hitachi Data Systems Support Center . . . . . . . . . . . . . . . . . . . . 10-24

A Sharing UR volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Volume types that can be shared with Universal Replicator . . . . . . . . . . . . . . . A-2Cache Residency Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4Data Retention Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4Dynamic Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5global storage virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6LUN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6Resource Partition Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6Thin Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Configurations with TI volumes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7Universal Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9Virtual LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9Volume Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

B Configurations with TrueCopy . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Sharing volumes with TrueCopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23DC cascade configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Prerequisite information for 3DC cascade . . . . . . . . . . . . . . . . . . . . . . . . B-3Procedure for setting up 3DC cascade . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

3DC multi-target configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4Prerequisite information for 3DC multi-target . . . . . . . . . . . . . . . . . . . . . . B-5Procedure for setting up 3DC multi-target . . . . . . . . . . . . . . . . . . . . . . . . B-6

Delta resync configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6Creating the delta resync pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7Setting up remote command devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8Assigning mirrors to remote command devices . . . . . . . . . . . . . . . . . . . . B-9Releasing remote command device assigned to a mirror . . . . . . . . . . . . . B-11Performing the delta resync operation . . . . . . . . . . . . . . . . . . . . . . . . . . B-12

Problems that can occur in the delta resync operation . . . . . . . . . . . . . B-132 data center configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14

Prerequisite information for 2DC configuration . . . . . . . . . . . . . . . . . . . . B-14Specifications and restrictions for UR pair operations. . . . . . . . . . . . . . B-15Specifications and restrictions for TC pair operations . . . . . . . . . . . . . . B-16

Procedure for a 2DC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16

C Configurations with ShadowImage . . . . . . . . . . . . . . . . . . . . . . . C-1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2Configurations with SI primary volumes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2Configurations with SI secondary volumes . . . . . . . . . . . . . . . . . . . . . . . . . . C-4


viii

Pair status and data currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4

D UR CLI reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1Configuration commands and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2Pair operation commands and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3Monitoring commands and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4Maintenance commands and options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4Consistency group commands and options. . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

E UR GUI reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1Journals window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3Journal Volumes window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-5Journal Properties window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-8Create Journals wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-10

Create Journals window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-10Select Journal Volumes dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-13Create Journals confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . E-14

Assign Journal Volumes wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-15Assign Journal Volumes window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-15Assign Journal Volumes confirmation window. . . . . . . . . . . . . . . . . . . . . E-16

Delete Journals window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-17Edit Journal Options wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-18

Edit Journal Options window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-18Edit Journal Options confirmation window . . . . . . . . . . . . . . . . . . . . . . . E-19

Assign MP Blade wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-19Assign MP Blade window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-20Assign MP Blade confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . E-20

Edit Mirror Options wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-21Edit Mirror Options window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-21Edit Mirror Options confirmation window . . . . . . . . . . . . . . . . . . . . . . . . E-22

Assign Remote Command Devices wizard . . . . . . . . . . . . . . . . . . . . . . . . . . E-23Assign Remote Command Devices window. . . . . . . . . . . . . . . . . . . . . . . E-23Assign Remote Command Devices confirmation window . . . . . . . . . . . . . E-24

Release Remote Command Devices window. . . . . . . . . . . . . . . . . . . . . . . . . E-24View Pair Synchronous Rate window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-25View Pair Properties window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-26Split Pairs wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-29

Split Pairs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-29Split Pairs confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-31

Split Mirrors wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-32Split Mirrors window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-32Split Mirrors confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-34

Resync Pairs wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-36Resync Pairs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-36Resync Pairs confirmation window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-38

ixHitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

Resync Mirrors wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-39Resync Mirrors window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-39

Delete Pairs wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-41Delete Pairs window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-41

Force Delete Pairs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-42Delete Mirrors wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-42

Delete Mirrors window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-42Delete Mirrors confirmation window. . . . . . . . . . . . . . . . . . . . . . . . . . . . E-44

Edit Pair Options wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-45Edit Pair Options window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-45Edit Pair Options confirmation window. . . . . . . . . . . . . . . . . . . . . . . . . . E-46

Glossary

Index


x

Preface xiHitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

Preface

This document describes and provides instructions for using Hitachi Universal Replicator to plan, configure, and perform pair operations on the Hitachi Virtual Storage Platform G1000 (VSP G1000) storage system.

Please read this document carefully to understand how to use this product, and maintain a copy for reference purposes.

□ Intended audience

□ Product version

□ Release notes

□ Document revision level

□ Changes in this revision

□ Referenced documents

□ Document conventions

□ Convention for storage capacity values

□ Accessing product documentation

□ Getting help

□ Comments


xii Preface

Intended audienceThis document is intended for system administrators, Hitachi Data Systems representatives, and authorized service providers who install, configure, and operate the Hitachi Virtual Storage Platform G1000 storage system.

Readers of this document must be familiar with the following:• Data processing and understands RAID systems and their basic

functions.• The Hitachi Virtual Storage Platform G1000 system and has read the

Hitachi Virtual Storage Platform G1000 Hardware Guide.• The Hitachi Command Suite software and the Hitachi Command Suite

User Guide or the Hitachi Device Manager - Storage Navigator software and the Hitachi Virtual Storage Platform G1000 Mainframe System Administrator Guide.

• Remote replication and disaster recovery configurations for enterprise storage data centers.

Product versionThis document revision applies to VSP G1000 microcode 80-02-0x or later.

Release notesThe Hitachi Virtual Storage Platform G1000 Release Notes are available on the Hitachi Data Systems Portal: https://portal.hds.com. Read the release notes before installing and using this product. They may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document.

Document revision level

Changes in this revision • References to SUSOP (03) are deleted from Monitoring pair activity,

status, license capacity on page 7-2.• New information on the mirror relationship between the master and

restore journal is added in Mirror on page 1-6 and System requirements on page 2-2.

• Clarification of pair status is added in Monitoring pair activity, status, license capacity on page 7-2 (second bullet).

• The description of S-VOL access for PSUS status is updated in Pair status definitions on page 7-3.

Revision Date Description

MK-92RD8023-00 April 2014 Initial release

MK-92RD8023-01 August 2014 Supersedes and replaces MK-92RD8023-00

MK-92RD8023-02 October 2014 Supersedes and replaces MK-92RD8023-01

https://portal.hds.com

Preface xiiiHitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

• Detailed information about the Flush and Purge Split Mode options is added in Table 7-1 S-VOL consistency statuses on page 7-8.

Referenced documentsHitachi Virtual Storage Platform G1000:• Hitachi TrueCopy® User Guide, MK-92RD8019• Hitachi ShadowImage® User Guide, MK-92RD8021• Hitachi Thin Image User Guide, MK-92RD8011• Hitachi Virtual Storage Platform G1000 Global-Active Device User Guide,

MK-92RD8072• Hitachi Virtual Storage Platform G1000 Provisioning Guide for Open

Systems, MK-92RD8014• Hitachi Command Suite User Guide, MK-90HC172• Hitachi Virtual Storage Platform G1000 Hardware Guide, MK-92RD8007

Document conventionsThis document uses the following terminology conventions:

This document uses the following typographic conventions:

Convention Description

Hitachi Virtual Storage Platform G1000, VSP G1000

Unless otherwise noted, these terms refer to all models of the Hitachi Virtual Storage Platform G1000 storage system.

Important Procedures in this manual are tailored to the Device Manager - Storage Navigator (HDvM - SN) GUI. When using this GUI, “Local Storage System” displays for the system you have accessed on the HDvM - SN server. As a result, if you access the remote site’s HDvM - SN server, the GUI displays “Local Storage System” to refer to the pair’s remote (secondary) system. Likewise, the GUI in this case identifies the storage system connecting to the accessed system as the “Remote Storage System”. However, this manual uses the terms ”primary storage system” or “primary system” for the storage system in which the primary volume (P-VOL) is located in the local site, and “secondary storage system” or “secondary system” for the storage system in which the secondary volume (S-VOL) is located in the remote site, unless otherwise noted.


Regular text bold In text: keyboard key, parameter name, property name, hardware label, hardware button, hardware switchIn a procedure: user interface item

Italic Variable, emphasis, reference to document title, called-out term


xiv Preface

This document uses the following icons to draw attention to information:

Convention for storage capacity valuesPhysical storage capacity values (for example, disk drive capacity) are calculated based on the following values:

Logical storage capacity values (for example, logical device capacity) are calculated based on the following values:

Screen text Command name and option, drive name, file name, folder name, directory name, code, file content, system and application output, user input

< > (angle brackets) Variable (used when italic is not enough to identify variable)

[ ] (square brackets) Optional value

{ } (braces) Required or expected value

| (vertical bar) Choice between two or more options or arguments


Icon Meaning Description

Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively.

Note Provides information that is essential to the completion of a task.

Caution Warns that failure to take or avoid a specified action can result in adverse conditions or consequences (for example, loss of access to data).

WARNING Warns the user of severe conditions, consequences, or both (for example, destructive operations).

Physical capacity unit Value

1 kilobyte (KB) 1,000 (103) bytes

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical capacity unit Value

1 block 512 bytes

Preface xvHitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

Accessing product documentationThe VSP G1000 user documentation is available on the HDS Support Portal: https://portal.hds.com. Check this site for the most current documentation, including important updates that may have been made after the release of the product.

Getting helpThe Hitachi Data Systems Corporation customer support staff is available 24 hours a day, seven days a week. If you need technical support, log on to the HDS Support Portal for contact information: https://portal.hds.com

CommentsPlease send us your comments on this document: [email protected]. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation.

Thank you!

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

1 cylinder (cyl) • OPEN-V: 960 KB• Other than OPEN-V: 720 KB

Logical capacity unit Value

https://portal.hds.comhttps://portal.hds.com


xvi Preface

1

Universal Replicator overview 1–1Hitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

Universal Replicator overview

With Hitachi Universal Replicator (UR), you create and maintain a remote copy of a data volume on a Hitachi Virtual Storage Platform G1000 (VSP G1000) storage system.

This guide provides instructions for planning, configuring, operating, maintaining, and troubleshooting a Universal Replicator system.

Important: Procedures in this manual are tailored to the Device Manager - Storage Navigator (HDvM - SN) GUI. When using this GUI, “Local Storage System” displays for the system you have accessed on the HDvM - SN server.

As a result, if you access the secondary site’s HDvM - SN server, the GUI displays information for the pair’s secondary system under “Local Storage System”. Likewise, the GUI in this case identifies the storage system connected to the accessed system (in this case, the primary system) as the “Remote Storage System”.

□ Universal Replicator software

□ How Universal Replicator works

□ Hardware and software components

□ Reference Information


1–2 Universal Replicator overview

Universal Replicator software With Universal Replicator, you copy application data from a primary storage volume in the primary VSP G1000 storage system to a secondary system at a remote location. The volume in the secondary system is the secondary volume and is an asynchronous block-for-block copy of the primary storage volume. The copied data is consistent with primary volume data and therefore available for recovering the primary volume if the need arises.

Universal Replicator is designed to support a secondary site hundreds and even thousands of miles from the primary site, making recovery from region-wide disasters possible.

Universal Replicator is also designed to limit impact on the primary system. Updates sent from a host to the primary production volume on the primary system are copied to a master journal volume. The secondary system “pulls” data from the journal volume across the communication link to the backup-volume, the secondary volume. The primary system is free to perform its role as a transaction processing resource rather than as a replication engine.

How Universal Replicator worksRemote replication occurs using journal volumes on the primary and secondary systems.

• The journal volume on the primary system is called the “master journal volume”.

• The journal volume on the secondary system is called the “restore journal volume”.

Replication occurs in the following sequence:1. Journal obtain - When the host sends an update to the primary volume

(P-VOL), the primary system’s journal-obtain function triggers a copy of the updated data to the master journal volume. The host assigns write-sequence numbers to the data sent to the

master journal volume.

Figure 1-1 Basic sequence in Universal Replicator operations


Write-sequence numbers and other metadata attached to journal data ensure consistency of the data in the P-VOL.

2. Journal copy - Data is copied from the master journal to the restore journal. When the master journal has data, the data is transferred to the

restore journal. When data transfer is complete and the secondary volume (S-VOL) is updated, master journal data is discarded.

Data copy to the restore journal is initiated by the read-journal command issued by the secondary system.

Data copy occurs on a continual basis unless there is no data in the master journal. The request for data from the secondary system is repeated as soon as the previous read operation is completed.

Journal data is removed from the master journal only when the primary system receives notification that the data has been consistently updated on the secondary data volumes.

3. Journal-restore - The S-VOL is updated with changed data from the restore journal. Data is copied to the S-VOL according to the write sequence

numbers, ensuring data consistency. When journal-restore is completed, the data in the restore journal is

discarded, the primary system is notified the data has been written to the S-VOL, and the master journal data is discarded.

Hardware and software componentsA typical configuration consists of a VSP G1000 system with or without externally attached storage system on both primary and secondary sites, a host or hosts connected to the systems, Universal Replicator software on both systems, data path connections, and interface tools for configuring and managing Universal Replicator. • The primary and secondary VSP G1000 systems are connected using

dedicated fibre-channel data paths that can include fibre-channel switches. Data paths are routed from the fibre-channel ports on the primary system to the ports on the secondary system, and from the secondary system to the primary system.

• The host is connected to the VSP G1000 using a fibre-channel or fibre-channel-over-Ethernet (FCoE) target port.

Note: Please note the following:• The primary system discards journal data in the master journal volume

when it receives the sequence number of the restore journal, which is attached to the read journal command from the secondary system. This applies also when the primary and secondary systems are connected through a channel extender.

• Performance is affected because of journal-to-journal copying. Usage rates are also affected. See Read and write I/O during remote copy on page 1-11 for more high level information on Universal Replicator operations.



• Device Manager - Storage Navigator, whose GUI is used to view and operate Universal Replicator, is connected to the system via an internal connection and to client sessions via a LAN.

A Universal Replicator system consists of the following:• P-VOLs and S-VOLs on the primary and secondary VSP G1000• Master and restore journal volumes on the primary and secondary VSP

G1000• Master and restore journals on the primary and secondary VSP G1000

The master journal consists of the primary volumes and master journal volumes.

The restore journal consists of the secondary volumes and restore journal volumes.

Management software consists of:• Device Manager - Storage Navigator graphical user interface (GUI)• Command Control Interface (CCI)

Universal Replicator components are illustrated in the following figure and described in greater detail in the following topics.

Figure 1-2 Universal Replicator components


Hitachi Virtual Storage Platform G1000 storage systemsUniversal Replicator can be operated using two VSP G1000 systems, one at the primary site and one at the secondary site. The primary system consists of the main control unit and service processor (SVP). The secondary system consists of the remote control unit and its SVP.• Each VSP G1000 system can function simultaneously as a primary and

secondary system. • The primary system communicates with the secondary system over

dedicated fibre-channel remote copy connections.• The primary system controls the primary storage volume (P-VOL) and

the following operations: Host I/O write to the P-VOL P-VOL data copy to the master journal

• The secondary system controls the secondary storage volume (S-VOL) and the following operations: Initial copy and update copy between the P-VOL and restore journal. Journal commands to the primary system. Journal data copy from the master to the restore journal Restore journal data copy to the S-VOL Pair status management and configuration (for example, rejecting

write I/Os to the S-VOLs).

Pair volumesOriginal data is stored in the P-VOL and the copy is stored in the S-VOL. The pair can be paired, split, resynchronized, and released. When synchronized, the volumes are paired; when split, new or changed data sent to the P-VOL is not copied to the S-VOL. When resynchronized, changed data is copied to the S-VOL. If a disaster occurs, production operations can be transferred to the S-VOL. When the primary site is functional again, operations can be transferred and data can be copied back to the P-VOL.

The P-VOL remains available to the host for read and write I/O operations. The secondary system rejects write I/Os for the S-VOL by way of command rejection or intervention request, unless the Secondary Volume Written option is enabled. Then, write I/O is allowed to the S-VOL while the pair is split. In this instance, S-VOL and P-VOL track maps keep track of differential data and use it to resynchronize the pair.

Journal volumesFor Universal Replicator operations, journal volumes are required on the primary and secondary systems.• Updates to the P-VOL are copied to the master journal volume in the

primary system. See the illustration in Journals on page 1-6.• Master journal data is copied to the restore journal volume on the

secondary system.



• Journal volumes can have different volume sizes and different RAID configurations.

For information on planning journal volumes, see Sizing journal volumes on page 3-5 .

JournalsJournals help you manage data consistency between multiple P-VOLs and S-VOLs. A journal is a group of one or more data volumes and the related journal volume. Like consistency groups, you can use journals to create multiple pairs, and to split, resynchronize, and release multiple pairs. Journals are required on the primary and secondary systems.

Each data volume and its associated journal volume reside in the same journal. • The master journal contains master journal volumes and is associated

with the P-VOL.• The restore journal contains restore journal volumes and is associated

with the S-VOL

Each pair relationship between journals is called a "mirror". A mirror ID identifies a pair relationship between journals. When the pair is created, it is assigned a mirror ID.

MirrorThe relationship of a master journal and a restore journal is called a “mirror”. A mirror is in Active status when it contains only pairs in COPY status (those not synchronized, with initial copy operation in progress) and

Figure 1-3 Journals


pairs in PAIR status (those synchronized, with initial copy operation completed). Usually pairs are in PAIR status and thus mirrors are in Active status.

Splitting MirrorsWhen you split a mirror, all the pairs in the mirror are split and copy operations of data from the master journal to the restore journal stops. To split a mirror, you must place the mirror in Active status. When mirror splitting is completed, the mirror status becomes Stopped.

Updated data is not reflected to the S-VOL while the pair is split, but only later when the pair is resynchronized. To resynchronize all the pairs in the mirror, resynchronize the mirror itself.

You can select whether or not to enable the S-VOL write operation in the Secondary Volume Written option when you split a mirror. If the Secondary Volume Written option is enabled, the host can write the data to the S-VOL while the pair is split.

Tip: Universal Replicator assumes that pair operations are performed in units of mirrors. Be sure to perform pair split and resync operations for each mirror. Requests to perform a split or resync operation for each pair might be rejected.



You can also split a mirror after synchronizing the P-VOL and S-VOL. In that case, select Flush in Split Mode. This allows you to reflect the updated data to the S-VOL when the pair is split. When the secondary system accepts the pair split, all the journal data that has been held for the pair is written to the S-VOL. If no journal data (update data) comes to the pair for a fixed period of time, the pair status changes to PSUS. When all pairs in the journal are placed in the PSUS status, volume copying is complete, and the mirror status becomes Stopped.

Resynchronizing a mirrorWhen you resynchronize a mirror, data copying from the P-VOL to S-VOL in all pairs in the mirror restarts. To resynchronize a mirror, make sure that the mirror status is Stopped.

Deleting a mirrorWhen you delete a mirror, all the pairs in the mirror are deleted, and data copying from the master journal to the restore journal stops. Specify one of the following modes when deleting a mirror.

Tip: To create a complete copy of the data volumes in the mirror, you need to stop I/O operations from the host. Creating an instantaneous copy on demand and a copy created in such a way are called “point-in-time copy”.

Note: Resynchronize mirrors while I/O load is low. Especially when different types of pairs are mixed in the same consistency group, mirror resync operation at high I/O load might result in a pair resync failure, with the pair being split (the pair status becomes PSUE).


• Normal: The mirror is deleted only when the primary system can change the mirror status to Initial.

• Force: The mirror is forcibly deleted even when the primary system cannot communicate with the secondary system.

If the mirror status does not change to Initial after 5 or more minutes from when you start an operation to delete a mirror in Force mode, restart the delete operation in Force mode to ensure all pairs in the mirror are deleted.

After each delete operation in Force mode, wait at least five minutes before you create pairs in the same journal. Otherwise the paircreate operation might fail.

Data pathThe physical transmission link between the primary and secondary systems is called the data path. Universal Replicator commands and data are transmitted through the fibre-channel data path and switches. The data path is connected to the primary and secondary systems through two types of fibre-channel ports, Initiator and RCU Target ports. Universal Replicator requires paths in both directions. More specifically, it requires paths with Initiator ports in the primary system connected to RCU Target ports in the secondary system, and paths with Initiator Ports in the secondary system connected to RCU Target ports in the primary system.

One data path connection in each direction is required. It is recommended that you use two or more independent connections to provide hardware redundancy. A maximum of eight paths in each direction can be used.

For more information, see Planning the data path on page 4-1.

Consistency groups and journalsJournals are used in Universal Replicator to guarantee data consistency across multiple pairs. Consistency groups are used in other replication software for the same purpose. The journal group number is the consistency group number used in BCM or CCI. The journal group number may be different in the primary and secondary storage systems.

Device Manager - Storage Navigator Device Manager - Storage Navigator provides a GUI and command line interface for accessing and managing the storage system, including Universal Replicator.

Device Manager - Storage Navigator communicates with the SVP of each system over defined TCP/IP connections.

Command Control Interface (CCI)CCI provides a command line interface for accessing and managing the storage system, including Universal Replicator. You can perform the same Universal Replicator operations with CCI as you can with Device Manager - Storage Navigator. In addition, you can automate pair operations using scripts.



If you want to use CCI but it is not installed, contact your Hitachi Data Systems account team.

Reference InformationThe following topics describe UR copy operations and other features.

Overview of copy operationsCopy operations include initial and update copy, as well as the underlying operations that are executed, such as journal processing and differential data management.

Initial copy operation

When the initial copy is executed, all data in the P-VOL is copied in sequence directly to the S-VOL. Primary journal volumes are not used during the initial copy; however, the copied data in this operation is referred to as “base journal data”. • Creating or resynchronizing two or more pairs within the same journal

results in the base journal data being copied to the respective S-VOLs, one at a time. This extends the time required for all the operations to be completed.

• An initial copy operation can be performed to establish the pair — with no data copied between the volumes. This can be done when data in the P-VOLs and S-VOLs are identical.

• Universal Replicator pair data can also be copied using a TrueCopy initial copy operation. Doing this reduces the time to complete the copy operation. See Planning pair volumes on page 3-7 for more information.

Update copy operation

When a host has new or changed information, the following occurs in the primary system:• The update is written to the P-VOL• The update is copied to the master journal along with metadata that

includes sequence and other consistency information.The secondary system issues the read-journal command (independent of host I/O activity). At this time, the following occurs: Any data in the master journal is sent to the restore journal. The updated data is copied to the S-VOL. Journal data on the primary and secondary systems is discarded

when data consistency is established in the copy.

Note: Journal data is transferred using special I/O operations initiated by the secondary system, called RIO (remote I/O). RIO provides the most efficient type of data transfer. Make sure that your channel extenders are capable of supporting RIO. Contact Hitachi Data Systems Support Center for more information.


If an update copy operation fails, the secondary system suspends the affected pair or all pairs in the journal, depending on the type of failure. The suspended pair or journal returns to Paired status when the primary and secondary systems are resynchronized.

Read and write I/O during remote copyThe primary system reads from the P-VOL when it receives a read I/O command. If the read fails, the redundancy provided by RAID 1, RAID 5, or RAID 6 technology recovers the failure. The primary system does not read the S-VOL for recovery.

When a primary system receives a write I/O command for a P-VOL in PAIR status, the system performs the write operation and performs the update copy operation. The write operation completes independently of the update copy operations on the S-VOL.

The secondary system updates the S-VOL according to the write sequence number in the journal data. This maintains data consistency between P-VOL and S-VOL.

If the P-VOL write operation fails, the primary system reports a unit check and does not create the journal data for this operation. As mentioned, if the update copy operation fails, the secondary system suspends either the affected pair or all Universal Replicator pairs in the journal, depending on the type of failure. When the suspended pair or journal is resynchronized, the primary and secondary systems negotiate the resynchronization of the pairs.

During normal operations, the secondary system does not allow S-VOLs to be online (mounted). Therefore, hosts cannot read from and write to S-VOLs. However, if the Secondary Volume Written option is enabled, write access to an S-VOL is allowed while the pair is split. The pair must be split from the primary system for the option to take effect.

To reduce the overhead associated with remote copy activities and to maximize rate of data transfer, the VSP G1000 uses a special write command for initial and update copy operations. This command transfers the control parameters and the fixed-block architecture (FBA) format data for consecutive updated records in a track using a single write operation. It eliminates the overhead required for performing FBA-to-count-key-data (CKD) and CKD-to-FBA conversions.

Differential data managementDifferential data is the data that is changed in the P-VOL while a pair is split or suspended. This changed data has not been written to the S-VOL. This data is stored in a track bitmap. When the pair is resynchronized, the primary system merges the P-VOL and S-VOL bitmaps, and the differential data is copied to the S-VOL.

The number of bitmap areas required is based on the number of volumes being replicated and the size of the volumes. This affects the maximum possible number of pairs that can be created in the system.



S-VOL write optionWhen splitting a pair, you can set an option (Secondary Volume Written) allowing write I/O to the S-VOL. The Secondary Volume Written option can be specified only when you are connected to the primary system, and it applies only to the specified pairs. When you resynchronize a split pair whose S-VOL is write-enabled, the secondary system sends the S-VOL track bitmap to the primary system, which merges the P-VOL and S-VOL bitmaps to determine which tracks are out of sync. This ensures proper resynchronization of the pair.

Pair statusEvery pair operation results in a change in pair status. Also, when you want to perform an operation, the pair must have a specific status in order to for the operation to run.

You will monitor pair status to ensure that you can perform the desired operation, and to ensure that an operation completed successfully.

To become familiar with the operations that result in the pair statuses, it is recommended that you review Pair status definitions on page 7-3 .

2

Requirements and specifications 2–1Hitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

Requirements and specifications

This chapter provides system requirements for Hitachi Universal Replicator.

□ System requirements


2–2 Requirements and specifications

System requirementsUniversal Replicator operations are performed from the primary system to the secondary system. Copy operations are carried out via the data path.

General requirements for these and all UR components are listed below.

Table 2-1 General system requirements

Item Requirement

Supported storage systems

VSP G1000 can be paired with the following:• VSP G1000 (80-01-01-xx/xx or later)• VSP (70-06-xx-xx/xx or later)• USP V/VM (60-08-4x-xx/xx or later)• HUS VM (73-03-xx-xx/xx or later)

Number of storage systems

Two—one at the primary site, one at the secondary site. A maximum of four VSP G1000 systems can be used at each site, and any combination — from one to four storage systems on one or both sites — can be used:

Maximum number of secondary systems allowed (System)

Four secondary UR, URz, and TC systems can be set per primary system.

Universal Replicator • Must be installed on primary and secondary VSP G1000 systems.

• License keys required.• UR and URz can coexist in the same storage system.• For licensing capacity requirements when UR volumes

are shared with other VSP G1000 software volumes, see Dynamic Provisioning on page A-5

• For information on expired licenses or exceeding licensed capacity, see the Hitachi Command Suite User Guide.

Other licenses required • TrueCopy is required, whether or not TC volumes are shared with UR.

• Disaster Recovery Extended. Used for 3DC configurations and UR operations in multiple primary and secondary storage systems.

• Dynamic Provisioning. DP-VOLs are required for journal volumes.


Interfaces • Device Manager - Storage Navigator: Must be LAN-attached to the primary system. Not required on the secondary system, but

recommended in order to change UR parameters and access the S-VOL for disaster recovery and maintenance.

The following roles are required:Storage Administrator (Remote Copy), to perform pair operationsStorage Administrator (System Resource Management), to configure settings

• CCI: Optional Command device required When using virtual storage machine volumes,

specify VSP G1000 LDEV ID, serial number, and virtual information in the configuration definition file.

Supported host platforms

Refer to the Hitachi Data Systems interoperability matrix at http://www.hds.com/products/interoperability.

Data path Fibre channel with either direct and switch connections. 16FC8 package must be used. 8FC16 and 16FE10 packages do not support the initiator port and the RCU target port.When both systems are VSP G1000, you can use multiple path groups. This is done by registering path groups with multiple path group IDs in the same storage system. But note that only one path group can be specified for a mirror. Up to eight paths can be registered in one path group.

Path group Groups of remote paths, which allows you to configure or change the configuration of multiple paths at the same time. • A maximum of eight remote paths can be registered in a

path group• A maximum of 64 path groups can be set in a storage

system. • The range of values for the path group ID is 0-255.• For a mirror, the same path group ID must be used to

connect the primary storage system to the secondary system as is used to connect the systems in the reverse direction.

• The path group is specified during the create pair operation. It cannot be changed by resynchronization or the swap operation.

• Path groups can be created and specified using CCI. See configuration setting commands in Command Control Interface User and Reference Guide and sample configuration definition files in Command Control Interface Installation and Configuration Guide.

• It is recommended that you specify different paths and path groups for TC and UR secondary systems when using CU Free.

Item Requirement

http://www.hds.com/products/interoperability



Pair volumes • A P-VOL may be copied to one S-VOL.• The P-VOL and S-VOL must be equal in size. • The P-VOL and S-VOL must be of same emulation type.• Supported emulation types for OPEN system pair

volumes: OPEN-V

• The maximum size of the P-VOL and S-VOL is 4,194,304.000 MB (8,589,934,592 blocks).

• The minimum volume size of the P-VOL and S-VOL is 46.875MB (96,000 blocks).

• When TC is cascaded with UR, a data volume may be copied to multiple data centers.

Journals and journal volumes

• Maximum number of journals supported per storage system: 256 (0 to 255)

• Recommended number of journals per storage system: Up to 16 per storage system

• Maximum number of journal volumes: 2. If two are registered, only one is used (the first one registered). The second is not used unless needed for maintenance, or to replace the first one.

• Maximum journal volume size: 60TB• Minimum journal volume size: 1.5GB• Maximum number of data volumes per journal: 8,192• Emulation types for journal volumes: OPEN-V. Journal

volumes must be DP-VOLs.• The relationship between a master journal and a restore

journal is called a mirror. Mirror IDs are 0 to 3.For more information, see Planning journal volumes on page 3-6.

Supported volume types Virtual LUN: • Can be used for data and journal volumes.• S-VOL capacity must equal P-VOL capacity.Cache Residency Manager:• Data volume: yes• Journal volume: no

Maximum number of pairs

Limited per VSP G1000 system. See Maximum number of pairs allowed on page 3-8.

Supported RAID groups • RAID1, RAID5, and RAID6 are supported for both data and journal volumes.

• RAID1, RAID5, and RAID6 can co-exist in the same journal.

Item Requirement


Cache and nonvolatile storage (NVS)

Must be operable for primary and secondary systems to ensure pair creation success. The secondary system cache must be configured to adequately support UR remote-copy workloads, as well as local workload activity. In general, increase cache capacity by 25 percent for UR. Also, several GBs should be added for each journal on the system.Note: When pair status is COPY, neither cache nor shared memory can be added to or removed from the system. When either of these tasks is to be performed, first split any pairs in COPY, status, then resynchronize when the cache or shared memory operation is completed.

Host failover software Required for disaster recovery.

CCI consistency groups when multiple primary and secondary system

• Up to four journals can be registered in one CCI consistency group number. If there are four systems, you must create one journal for each system.

• Up to 8,192 pairs. You can register the total number of pairs in the journals within one CCI consistency group. However, it is recommended that you register only up to 4,096 pairs.

Item Requirement

3

Planning volumes, VSP G1000 systems 3–1Hitachi Virtual Storage Platform G1000 Hitachi Universal Replicator User Guide

Planning volumes, VSP G1000 systems

This chapter provides information and instructions for planning Universal Replicator volumes, VSP G1000 systems, and other important requirements and restrictions.

□ Plan and design workflow

□ Assessing business requirements for data recovery

□ Write-workload

□ Data transfer speed considerations

□ Sizing journal volumes

□ Planning journals

□ Planning journal volumes

□ Planning pair volumes

□ Disaster recovery considerations

□ Sharing volumes with other VSP G1000 software volumes

□ Planning UR in multiple VSP G1000s using a consistency group

□ Planning for previous models

□ Guidelines for preparing systems for UR


3–2 Planning volumes, VSP G1000 systems

Plan and design workflow Planning the Universal Replicator system is tied to your organization’s business requirements and production system workload. This means defining business requirements for disaster downtime and measuring the amount of changed data your storage system produces over time. With this information, you can calculate the size of journal volumes and the amount of bandwidth required to transfer update data over the data path network.

The plan and design workflow consists of the following:• Assess your organization’s business requirements to determine recovery

requirements.• Measure your host application’s write-workload in MB per second and

write-input/output per second (IOPS) to begin matching actual data loads with the planned UR system.

• Use collected data along with your organization’s recovery point objective (RPO) to size UR journal volumes. Journal volumes must have enough capacity to hold accumulating data over extended periods.The sizing of journal volumes can be influenced by the amount of bandwidth you settle on. These factors are interrelated. You may actually adjust journal volume size in conjunction with bandwidth to fit the organization’s needs.

• Use IOPS to determine data transfer speed into and out of the journal volumes. Data transfer speed is determined by the number of Fibre-Channel ports you assign to UR, and by RAID group configuration. You need to know port transfer capacity and the number of ports that your workload data will require.

• Use collected workload data to size bandwidth for the fibre-channel data path. As mentioned, bandwidth and journal volume sizing, along with data transfer speed, are interrelated. Bandwidth may be adjusted with the journal volume capacity and data transfer speed you plan to implement.

• Design the data path network configuration, based on supported configurations, fibre-channel switches, and the number of ports your data transfer requires.

• Plan data volumes (primary and secondary volumes), based on the sizing of P-VOL and S-VOL, RAID group considerations, and so on.

• Understand operating system requirements for data and journal volumes.

• Adjust cache memory capacity for UR.

Some tasks will be handled by HDS personnel. The planning information you need to address is provided in the following topics.


Assessing business requirements for data recovery In a UR system, when the data path continues to transfer changed data to the secondary site, journals remain fairly empty. However, if a path failure or a prolonged spike in write-data that is greater than bandwidth occurs, data flow stops. Changed data that is no longer moving to the secondary system builds up in the master journal.

To ensure that journals can hold the amount of data that could accumulate, they must be sized according to the following:• The maximum amount of time that journals could accumulate data. You

develop this information by determining your operation’s recovery point objective (RPO).

• The amount of changed data that your application generates. This is done by measuring write-workload.

Determining your RPO Your operation’s recovery point is the maximum time that can pass after a failure or disaster occurs before data loss is greater than the operation can survive.

For example, if the operation can survive one hour’s worth of lost data, and a disaster occurs at 10:00 am, then the system must be corrected by 11 a.m.

In regards to journal sizing, the journal must have the capacity to hold the data that could accumulated in one hour. If RPO is 4 hours, then the journal must be sized to hold 4-hour’s worth of accumulating data.

To assess RPO, the host application’s write-workload must be known.

With write-workload and IOPS, you or your organization’s decision-makers can analyze the number of transactions write-workload represents, determine the number of transactions the operation could loose and still remain viable, determine the amount of time required to recover lost data from log files or key it in, and so on. The result is your RPO.

Write-workload Write-workload is the amount of data that changes in your production system in MB per second. As you will see, write-workload varies according to the time of day, week, month, quarter. That is why workload is measured over an extended period.

With the measurement data, you can calculate workload averages, locate peak workload, and calculate peak rolling averages, which show an elevated average. With this data you will calculate the amount of data that accumulates over your RPO time, for example, 2 hours. This will be a base capacity for your journal volumes or represent a base amount of bandwidth your system requires.



Whether you select average, rolling average, or peak workload is based on the amount of bandwidth you will provide the data path (which is also determined by write-workload). Bandwidth and journal volume capacity work together and depend on your strategy for protecting data.

Measuring write-workloadWorkload data is best collected using the IBM Resource Measurement Facility (RMF). You will use IOPS to set up a proper data transfer speed, which you ensure through RAID group configuration and by establishing the number of fibre-channel ports your UR system requires. Each RAID group has a maximum transaction throughput; the ports and their microprocessors have an IOPS threshold.

Workload and IOPS collection is best performed during the busiest time of month, quarter, and year. This helps you to collect data that shows your system’s actual workloads during high peaks and spikes, when more data is changing, and when the demands on the system are greatest. Collecting data over these periods ensures that the UR design you develop will support your system in all workload levels.

Data transfer speed considerations This topic discusses the speed that data must be transferred in order to maintain the UR system your are designing.

The ability of your UR system to transfer data in a timely manner depends directly on the following two factors:• RAID group configuration• Fibre-channel port configuration

Both of these elements must be planned to be able to handle the amount of data and number of transactions your system will move under extreme conditions.

RAID group configuration A RAID group can consist of physical volumes with a different number of revolutions, physical volumes of different capacities, and physical volumes of different RAID configurations (for example, RAID-1 and RAID-5). The data transfer speed of RAID groups is affected by physical volumes and RAID configurations.

Fibre-channel port configurationThe fibre-channel ports on your VSP G1000 system have an IOPS threshold. Use the performance monitoring information for the number of IOPS your production system generates to calculate the number of fibre-channel ports the UR system requires.

Please see Planning ports for data transfer on page 4-7 for a full discussion on the type and number of fibre-channel ports required for your system.


Sizing journal volumes Journals volumes should be sized to meet all possible data scenarios, based on your business requirements. If the amount of data exceeds capacity, performance problems and suspensions result.

Hitachi recommends a capacity of 6 GB or more. Journal volumes cannot be registered if capacity is lower than 1.5 GB.

To calculate journal size1. Follow the instructions for Measuring write-workload on page 3-4.2. Use your system’s peak write-workload and your organization’s RPO to

calculate journal size. For example:RPO = 2 hours

Write-workload = 30 MB/sec

Calculate write-workload for the RPO. In the example, write-workload over a two-hour period is calculated as follows:30 MB/second x 60 seconds = 1800 MB/minute

1800 MB/minute x 60 minutes = 108,000 MB/hour

108000 MB/hour x 2 = 416,000 MB/2 hours

Basic journal volume size = 416,000 MB (416 GB)

Journal volume capacity and bandwidth size work together. Also, your strategy for protecting your data may allow you to adjust bandwidth or the size of your journal volumes. For a discussion on sizing strategies, see Five sizing strategies on page 4-2.

Planning journals UR manages pair operations for data consistency through the use of journals. UR journals enable update sequence consistency to be maintained across a group of volumes.

Understanding the consistency requirements for an application (or group of applications) and their volumes will indicate how to structure journals.

For example, databases are typically implemented in two sections. The bulk of the data is resident in a central data store, while incoming transactions are written to logs that are subsequently applied to the data store.

If the log volume “gets ahead” of the data store, it is possible that transactions could be lost at recovery time. Therefore, to ensure a valid recovery image on a replication volume, it is important that both the data store and logs are I/O consistent by placing them in the same journal.

The following information about journal volumes and journals will help you plan your journals.

Note: If you are planning for disaster recovery, the secondary system must be large enough to handle the production workload, and therefore, must be the same size as master journals.



• A journal consists of one or more journal volumes and associated data volumes.

• A journal can have only P-VOLs/master journals, or S-VOLs/restore journals.

• A journal cannot belong to more than one storage system (primary or secondary).

• All the P-VOLs, or S-VOLs, in a journal must belong to the same storage system.

• Data volumes in different virtual storage machines cannot be registered in the same journal.

• Master and restore journal IDs that are paired can be different.If using a consistency group number, the consistency group number of the P-VOL and S-VOL must be the same.

• Each pair relationship in a journal is called a "mirror". Each pair is assigned a mirror ID. The maximum number of mirror IDs is 4 (0 to 3) per system.

• When UR and URz are used in the same system, individual journals must be dedicated either to one or the other, not both.

• Master and restore journals are managed according to the journal ID.• Review journal specifications in System requirements on page 2-2. • A journal can contain a maximum of 2 journal volumes.

Planning journal volumes In addition to sizing journal volumes, you must also be aware of the following requirements and restrictions. • Only DP-VOLs whose emulation type is OPEN-V can be used for journal

volumes. • Volumes in a virtual storage machine cannot be used as journal volume.• A journal ID can be used in one virtual storage machine only.• Volumes to which a path is set from a host cannot be registered as

journal volumes.• Journal volumes must be registered in a journal before the initial copy

operation is performed.• Journal volumes must be registered on both the primary and secondary

systems.• You can register two journal volumes in a journal in each primary

storage system and secondary system. Though two can be registered, only one is used (the first one registered). The second is not used unless needed for maintenance, or to replace the first one.

• Journal volumes should be sized according to RPO and write-workload. See Sizing journal volumes on page 3-5 for more information.

• Journal volumes in a journal can have different capacities.


• A master journal volume and the corresponding restore journal volume can have different capacities.

• The number of journal volumes in the master journal does not have to be equal to the number of volumes in the restore journal.

• A data volume and its associated journal volume can belong to only one journal.

• Data volumes and journal volumes in the same journal must belong to the same controller.

• Do not register a volume to a journal during quick formatting. Doing so stalls the operation.

• Journal volume capacity is not included in accounting capacity. • Journal volumes consist of two areas: One area stores journal data, and

the other area stores metadata for remote copy.

See the following for more information about journals and journal volumes:• The “Journals” item in System requirements on page 2-2• Planning journals on page 3-5

Planning pair volumes The following information can help you prepare volumes for configuration. Also, see system requirements and specifications in Requirements and specifications on page 2-1 for more information.• The emulation and capacity for the S-VOL must be the same as for the

P-VOL• When the S-VOL is connected to the same host as the P-VOL, the S-VOL

must be defined to remain offline.• When creating multiple pairs in the same operation using SN, make sure

that you set up S-VOL LUNs in a way that allows the system to correctly match them to selected P-VOLs. Even though you select multiple volumes as P-VOLs in the Device Manager - Storage Navigator Create UR Pairs procedure, you are able to specify only one S-VOL. The system automatically assigns LUs on the secondary system as S-VOLs for the other selected P-VOLs according to LUN.You will have two options for specifying how the system matchs S-VOLs to P-VOLs.- Interval: The interval you specify will be skipped between LDEV numbers in the secondary system.For example, suppose you specify LU 01 as the initial (base) S-VOL, and specify 3 for Interval. This results in secondary system LDEV 04 being assigned to the next P-VOL, 07 assigned to the subsequent P-VOL, and so on. To use Interval, you set up secondary system LDEV numbers according to the interval between them.- Relative Primary Volume. The difference is calculated between the LDEV numbers of two successive P-VOLs. S-VOLs are assigned according to the closest LUN number.



For example, if the LUN numbers of three P-VOLs are 1, 5, and 6; and you set LUN numbers for the initial S-VOL (Base Secondary Volume) at 2, the LUN numbers of the three S-VOLs will be set at 2, 6, and 7, respectively.

• You can create a UR pair using a TrueCopy initial copy, which takes less time. To do this, system option 474 must be set on the primary and secondary systems. Also, a script is required to perform this operation. For more on system option 474 and how to do this operation, see System option modes on page 3-16.

• UR supports the Virtual LUN feature, which allows you to configure custom LUs that are smaller than standard LUs. When custom LUs are assigned to a UR pair, the S-VOL must have the same capacity as the P-VOL. For details about Virtual LUN feature, see the Hitachi Virtual Storage Platform G1000 Provisioning Guide for Open Systems.

• Identify the volumes that will become the P-VOLs and S-VOLs. Note the port, host group ID, and LUN ID of each volume. This information is used during the initial copy operation.

• You can create multiple pairs at the same time. Review the prerequisites and steps in Creating the UR initial copy on page 6-2.

• When you create a UR pair, you will have the option to create only the relationship, without copying data from P-VOL to S-VOL. You can use this option only when data in the two volumes is identical.

Maximum number of pairs allowed You can create up to 65,280 pairs on a VSP G1000 system. The maximum number for your system is limited by:1. The number of cylinders in the volumes, which must be calculated.2. The number of bitmap areas required for Universal Replicator data and

journal volumes. This is calculated using the number of cylinders.

Calculating maximum number of pairs

To calculate the number of cylinders

Use the following formula:

Caution: The bitmap areas that are used for Universal Replicator are also used for Universal Replicator for Mainframe, TrueCopy, and TrueCopy for Mainframe. If you use UR with any of these products, use the total number of each pair’s bitmap areas to calculate the maximum number of pairs. In addition, if UR and TC share the same volume, use the total number of both pairs regardless of whether the shared volume is primary or secondary.

Note: In the calculations below, note the following:• ceil () indicates that the value between the parentheses must be

rounded up to the nearest integer.• Number of logical blocks indicates volume capacity measured in blocks.

Number of logical blocks - Volume capacity (in bytes) / 512


Number of cylinders = (ceil ( (ceil (number of logical blocks / 512)) / 15))

To calculate the number of required bitmap areas:

Use the following formulaceil((number of cylinders x 15) / 122,752) )

where:• number of cylinders x 15 indicates the number of slots• 122,752 is the number of slots that a bitmap area can manage

To calculate the maximum number of pairs

The maximum number of pairs is determined by the following:• The number of bitmap areas required for Universal Replicator (calculated

above).• The total number of bitmap areas in the storage system, which is

65,536. Bitmap areas reside in an additional shared memory, which is required for Universal Replicator. Bitmap areas are used not only by Universal Replicator, but also by

Universal Replicator for Mainframe, TrueCopy, and TrueCopy for Mainframe. Therefore, the number of bitmap areas used by these other program products (if any) must be subtracted from 65,536, with the difference used to calculate the maximum number of pairs available for Universal Replicator.

If TrueCopy and Universal Replicator share the same volume, you must use the total number of bitmap areas for both pairs regardless of whether the shared volume is primary or secondary.

• The maximum number of pairs supported per storage system, which is 65,280. If CCI is used, it is 65,279.

Note: Doing this calculation for multiple volumes can result in inaccuracies. Perform the calculation for each volume seperately, then total the bitmap areas. The following examples show correct and incorrect calculations. Two volumes are used: one of 10,017 cylinders and another of 32,760 cylinders

Correct calculation

ceil ((10,017 x 15) / 122,752) = 2

ceil ((32,760 x 15) / 122,752) = 5

Total: 7

Incorrect cal

hitachi virtual storage platform g1000 hitachi universal ... · product version contents getting...

Documents