advertisement
2
Requirements and specifications
This chapter provides system requirements for Hitachi Universal Replicator.
□
Requirements and specifications
Hitachi Virtual Storage Platform Hitachi Universal Replicator User Guide
2–1
System requirements
Universal Replicator operations are performed from the primary system to the secondary system, which contain the UR P-VOLs, S-VOLs, and master and restore journal volumes. 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
Number of VSP systems Two—one at the local site, one at the remote site.
A maximum of four VSP systems can be used at each site, and any combination — from one to four storage systems on one or both sites — can be used:
Storage systems at primary and secondary sites
VSP is required at the primary or secondary site. Any of the following can be paired with it:
• VSP (70-01-01-xx/xx or later)
• VSP G1000 (80-01-01-xx/xx or later)
• USP V/VM (60-07-51-xx/xx or later)
• TagmaStore USP/TagmaStore NSC (50-09-98-xx/xx or later)
• HUS VM (73-01-31-xx/xx or later)
Previous model storage systems supported
Universal Replicator
See previous item; see also Planning for previous models on page 3-16 .
• Must be installed on primary and secondary VSP 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 software volumes, see
Dynamic Provisioning on page B-5
• For information on expired licenses or exceeding licensed capacity, see the Hitachi Storage Navigator User
Guide.
Other licenses required TrueCopy is required. This applies whether or not TC volumes are shared with UR.
2–2
Requirements and specifications
Hitachi Virtual Storage Platform Hitachi Universal Replicator User Guide
Item Requirement
Interfaces • Storage
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 operations
Storage Administrator (System Resource
Management), to configure settings
• CCI:
Optional
Command device required
Supported host platforms
Data path
Refer to the Hitachi Data Systems interoperability matrix at http://www.hds.com/products/interoperability .
Fibre channel with either direct and switch connections.
When the system is connected to a VSP or 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 logical paths, which allows you to configure or change the configuration of multiple paths at the same time.
• A maximum of eight logical paths can be registered in a path group
• A maximum of 64 path groups can be set in a storage system.
• The following Hexadecimal values can be set as the path group ID:
0-255 when connected to VSP or VSP G1000
0 only when connected to USP V/VM, HUS VM,
TagmaStore USP, or TagmaStore NSC
• 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 the resync pair or 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.
Requirements and specifications
Hitachi Virtual Storage Platform Hitachi Universal Replicator User Guide
2–3
Item Requirement
Volumes • A P-VOL may be copied to one S-VOL.
• P-VOL and S-VOL must be equal in size.
• P-VOL and S-VOL must be of same emulation type.
• The maximum volume size of P-VOL and S-VOL is
4,194,304.000 MB (8,589,934,592 blocks). However, when TagmaStore USP or TagmaStore NSC is used as the primary or secondary system, the maximum volume size is 2,949,120.00 MB (6,039,797,760 blocks).
• The minimum volume size of P-VOL and S-VOL is
26.875MB (96,000 blocks).
• When TC is cascaded with UR, a data volume may be copied to multiple data centers.
Maximum number of pairs
Limited per VSP 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.
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
LUN Expansion (LUSE)
Cache and nonvolatile storage (NVS)
Must be operable for primary and secondary systems to ensure pair creation success. The remote 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, 1 GB 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
CCI consistency groups when multiple primary and secondary system
Required for disaster recovery.
• Up to two mirrors can be registered in one journal. One consistency group can be registered in each mirror. 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.
2–4
Requirements and specifications
Hitachi Virtual Storage Platform Hitachi Universal Replicator User Guide
Journals
Item Requirement
• Max. number: 256 (0 to 255) per storage system
• Recommended number per storage system: Up to 16
• Max. number of journal volumes: 64 per journal
• Max. number of data volumes: 8,192 per journal
See Planning journal volumes on page 3-7
for all requirements and restrictions.
Requirements and specifications
Hitachi Virtual Storage Platform Hitachi Universal Replicator User Guide
2–5
2–6
Requirements and specifications
Hitachi Virtual Storage Platform Hitachi Universal Replicator User Guide
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 1 Hitachi Virtual Storage Platform Hitachi Universal Replicator User Guide
- 3 Contents
- 11 Preface
- 12 Intended audience
- 12 Product version
- 12 Document revision level
- 12 Changes in this revision
- 12 Referenced documents
- 13 Document organization
- 14 Document conventions
- 14 Convention for storage capacity values
- 15 Accessing product documentation
- 15 Getting help
- 15 Comments
- 17 Universal Replicator overview
- 18 Universal Replicator software
- 18 How Universal Replicator works
- 19 Hardware and software components
- 20 VSP storage systems
- 21 Pair volumes
- 21 Journal volumes
- 22 Journals
- 23 Data path
- 23 Consistency groups and journals
- 23 Storage Navigator
- 23 Command Control Interface (CCI)
- 23 Reference Information
- 23 Overview of copy operations
- 24 Read and write I/O during remote copy
- 25 Differential data management
- 25 S-VOL write option
- 26 Pair status
- 27 Requirements and specifications
- 28 System requirements
- 33 Planning volumes, VSP systems
- 34 Plan and design workflow
- 35 Assessing business requirements for data recovery
- 35 Determining your RPO
- 35 Write-workload
- 36 Measuring write-workload
- 36 Sizing journal volumes
- 37 Planning journals
- 38 Data transfer speed considerations
- 38 RAID group configuration
- 39 Fibre-channel port configuration
- 39 Planning journal volumes
- 40 Planning pair volumes
- 40 Maximum number of pairs allowed
- 42 Maximum initial copy operations and priorities
- 43 Disaster recovery considerations
- 43 Host failover software
- 44 Sharing volumes with other VSP software volumes
- 44 Planning UR in multiple VSPs using a consistency group
- 46 Multiple journals per CCI consistency group
- 48 3DC configurations using 3 UR sites
- 48 Planning for previous models
- 49 Guidelines for preparing systems for UR
- 50 System option modes
- 55 Planning the data path
- 56 Data path design workflow
- 56 Sizing bandwidth
- 56 Five sizing strategies
- 57 Calculating bandwidth
- 61 Planning ports for data transfer
- 61 Port types
- 62 Determining required number of ports
- 62 Cable length and switch requirements
- 64 Supported data path configurations
- 67 Configuration operations
- 68 Configuration workflow
- 68 Defining fibre-channel port attributes
- 69 Configuring local and remote systems for UR
- 73 Configuring additional logical paths
- 74 Specifying number of concurrent initial/resync copies
- 76 Registering journal volumes in a journal
- 81 Pair operations
- 82 Pair operations workflow
- 82 Checking pair status
- 82 Creating the initial copy
- 87 Splitting pairs
- 89 Splitting mirrors
- 90 Creating point-in-time copies
- 90 Resynchronizing pairs
- 92 Resynchronizing mirrors
- 93 Deleting pairs
- 95 Deleting pairs in a mirror
- 97 Monitoring the system
- 98 Monitoring pair activity and status
- 98 Pair status definitions
- 106 Saving pair information to a text file
- 107 Monitoring copy operations data, I/O with Usage Monitor
- 108 Selecting data to be graphed
- 110 Manipulating graph, save data
- 110 Monitoring I/O and hardware performance with Performance Monitor
- 111 Monitoring journal (mirror) status
- 111 Storage Navigator mirror status definitions
- 112 CCI mirror status definitions
- 113 Monitoring logical path status
- 113 History of pair operations
- 115 Maintaining the system
- 116 Pair maintenance—changing the pair-split option
- 116 Journal and mirror maintenance
- 117 Changing options used by journals
- 119 Changing options used by mirrors
- 122 Deleting journal volumes from a journal
- 123 Deleting journals
- 123 Logical path maintenance
- 124 Modifying data-transfer time threshold
- 124 Deleting logical paths
- 125 Deleting the UR relationship
- 126 Managing power-off for systems and network devices
- 126 When power stops unexpectedly
- 126 Powering-off systems intentionally
- 128 Powering-off network relay devices
- 129 Disaster recovery operations
- 130 Overview
- 130 General recovery procedures
- 130 Preparing for recovery
- 130 Preparing for file and database recovery
- 131 Switching host operations to the secondary site
- 131 Reversing copy direction from secondary to primary sites
- 132 Resuming host operations at the primary site
- 133 Recovery for 3 UR data centers
- 133 Recovery for 3 UR DC cascade configuration
- 136 Recovery for 3 UR DC multi-target configuration
- 138 Recovery for 3 UR/TC data centers and 3 UR data centers
- 139 Recovery for 3 UR/TC DC cascade configuration
- 139 Recovery for 3 UR/TC DC multi-target configuration
- 142 Recovery in a delta resync configuration
- 143 Recovery in a 2DC configuration
- 144 Recovery for configurations with UR/ShadowImage
- 147 Troubleshooting
- 148 General troubleshooting
- 149 Troubleshooting logical paths
- 152 Troubleshooting by suspension type
- 153 Troubleshooting hardware problems affecting pairs
- 155 Troubleshooting with CCI
- 169 Service information messages (SIMs)
- 171 Miscellaneous troubleshooting
- 171 Delta resync operation
- 171 Suspension among journals
- 172 Calling the Hitachi Data Systems Support Center
- 173 3 UR data-center configurations
- 174 Overview
- 174 3 UR DC cascade configuration
- 175 Failure recovery
- 175 Requirements, restrictions, and notes
- 177 Setting up the 3 UR DC cascade configuration
- 178 3 UR DC multi-target configuration
- 179 Failure recovery
- 180 Requirements, restrictions, and notes
- 181 Setting up the 3 UR DC multi-target configuration
- 183 Sharing volumes
- 184 Volume types that can be shared with Universal Replicator
- 186 Cache Residency Manager
- 186 Data Retention Utility
- 187 Dynamic Provisioning
- 188 High Availability Manager (HAM)
- 188 LUN Expansion (LUSE)
- 189 LUN Manager
- 189 Thin Image and Copy-on-Write Snapshot
- 189 Configuration with TI and SS volumes
- 190 Sharing TI and SS volumes in 3DC configurations
- 192 Virtual LUN
- 192 Volume Migration
- 193 Configurations with TrueCopy
- 194 Sharing volumes with TrueCopy
- 195 3DC cascade configuration
- 195 Prerequisite information for 3DC cascade
- 196 Procedure for setting up 3DC cascade
- 196 3DC multi-target configuration
- 197 Prerequisite information for 3DC multi-target
- 198 Procedure for setting up 3DC multi-target
- 198 Delta resync configuration
- 200 Prerequisite information for creating delta resync pairs
- 200 Procedure for creating a delta resync pair
- 201 Prerequisite information for delta resync operation
- 202 Performing the delta resync operation
- 202 Assigning remote command devices
- 207 2 data center configuration
- 207 Prerequisite information for 2DC configuration
- 209 Procedure for a 2DC configuration
- 211 Configurations with ShadowImage
- 212 Overview
- 212 Configurations with ShadowImage primary volumes
- 214 Configurations with ShadowImage secondary volumes
- 214 Pair status and data currency
- 217 GUI reference
- 218 Journal Operation window
- 220 Journal Detail window
- 224 Change Journal Option dialog box
- 225 Change Mirror Option dialog box
- 227 Edit Journal Volumes dialog box
- 228 Pair Operation window
- 233 Detailed Information dialog box
- 233 Paircreate dialog box
- 236 Pairsplit-r dialog box
- 237 Pairresync dialog box
- 237 Pairsplit-S dialog box
- 238 Change Pair Option dialog box
- 239 Display Filter dialog box
- 240 DKC Operation window
- 242 Remote systems information
- 243 Logical Path Information
- 243 Port Information for the local system
- 245 DKC Status dialog box
- 247 Add DKC dialog box
- 248 DKC Option dialog box
- 248 Usage Monitor window
- 249 History window
- 251 Operations in History window
- 253 History window notes
- 254 Export operations history
- 254 Optional Operation window
- 257 Glossary
- 289 Index