Status

3par remote copy manuals

LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF

File Name:3par remote copy manuals.pdf
Size: 3821 KB
Type: PDF, ePub, eBook

Category: Book
Uploaded: 2 May 2019, 23:10 PM
Rating: 4.6/5 from 784 votes.

Status: AVAILABLE

Last checked: 14 Minutes ago!

In order to read or download 3par remote copy manuals ebook, you need to create a FREE account.

Download Now!

eBook includes PDF, ePub and Kindle version

✔ Register a free 1 month Trial Account.

✔ Download as many books as you like (Personal use)

✔ Cancel the membership at any time if not satisfied.

✔ Join Over 80000 Happy Readers

3par remote copy manualsSearch Document title: HPE 3PAR Remote Copy Software User Guide (3PAR OS 3.3.1 MU1). 25 Oct 2018 According to this HPE 3PAR Remote Copy Software User Guide (pages 326, 327, and 328), the createsv -rcopy command works with all RC firmware, software and user manuals information for HPE 3PAR Remote Copy Software 17 Jun 2016 Software Documentation, and Technical Data for Commercial Items are. HP 3PAR Remote Copy Software User Guide. Published: August 2017. Abstract. This guide is for. Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it. OK Settings Your choices regarding cookies on this site. Functional cookies Performance cookies Advertising cookies Save settings Cancel Your preferences have been updated. In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page. Close Please upgrade your browser to improve your experience. The service goes WARN (by default) for STARTUP, SHUTDOWN or NODEDUP. To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser. You can download the paper by clicking the button above. Related Papers HPE 3PAR StoreServ Architecture By Gabriel Martinez Technical white paper HP 3PAR StoreServ Architecture Table of contents By arbnor mehana VDRS: An inexpensive approach to server disaster recovery By Debanjan Saha Storing, Managing, and Protecting Digital Information Information Storage and Management EMC Education Services By Vaishali K Information Storage and Management By Surina Siya READ PAPER Download pdf. Discover everything Scribd has to offer, including books and audiobooks from major publishers.http://dongkinhtourhue.com/upload/4-speed-manual-transmission-with-granny-gear.xml

Tags:
• 3par remote copy manual, 3par remote copy user guide, 3par remote copy user guide 3.3.1, hpe 3par remote copy user guide, 3par remote copy user guide 3.3 1 mu2, 3par remote copy user guide 3.2.2, 3par remote copy software user guide, hp 3par remote copy user s guide, 3par remote copy user guide 3.2.1, 3par remote copy manuals, 3par remote copy manuals pdf, 3par remote copy manuals download, 3par remote copy manuals free, 3par remote copy manuals online.

Report this Document save Save 3PAR Remote Copy For Later 37 views 0 0 upvotes 0 0 downvotes 3PAR Remote Copy Uploaded by Vinay Prudhvi Description: This document helps us in learning about 3par remote copy Full description save Save 3PAR Remote Copy For Later 0 0 upvotes, Mark this document as useful 0 0 downvotes, Mark this document as not useful Embed Share Jump to Page You are on page 1 of 37 Search inside document Browse Books Site Directory Site Language: English Change Language English Change Language. HPE 3PAR Remote Copy Software User. Guide. Part Number: QL226-10559 For HPE 3PAR OS 3.1.1 and earlier, the pair of HBAs used for RCFC links must Get HP HP 3PAR Operating System Software HP 3PAR Remote Copy 3.1.1 Software User's Guide. Get all HP manuals! This guide is for System and Storage Administrators who monitor and direct To use Remote Copy, you must use the HP 3PAR Command Line Interface (CLI). All Rights Reserved. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Remote copy setup methods 2. Select a remote copy configuration. 3PAR Remote Copy configurations 3. Select a network connection type.http://www.boostergas.fr/userfiles/4-speed-manual-transmission-shifter.xml Reviewing 3PAR Remote Copy requirements See also: 1-to-N remote copy considerations SLD remote copy considerations 4. To make sure that the system is prepared for remote copy configuration, review the requirements and restrictions. Gathering setup information 5. Configure the remote copy transport layer. Setting the transport layer When you have set the foundation for your remote copy system, continue to Setting up the remote copy servers. 12 Setting the foundation for HPE 3PAR Remote Copy 13 Remote copy setup Remote copy setup methods If you are a new user setting up HPE 3PAR Remote Copy for the first time, use one of the following methods: Follow the setup steps, as they relate to your remote copy system, in Setting the foundation for HPE 3PAR Remote Copy on page 12 and Setting up the remote copy servers on page 39. Use the Remote Copy Setup wizard in the HPE 3PAR Management Console. Use the HPE 3PAR Management Console to set up a simple 1-to-1 remote copy configuration between two storage systems. For more complex 1-to-1 configurations, as well as for N-to-1, M-to-N, and SLD configurations, use the HPE 3PAR Command-Line Interface to set up and configure remote copy. The HPE 3PAR Management Console User Guide is available at the following website: Hewlett Packard Enterprise Information Library ( Use the HPE 3PAR StoreServ Management Console SSMC to manage remote copy features. As of SSMC 3.0, the SSMC supports all configurations and modes listed in the support matrix for HPE 3PAR OS The supported configurations include 1-to-1, N-to-M, SLD, and 3PAR Peer Persistence, including 3DC. The supported group modes include synchronous, asynchronous periodic, and asynchronous streaming.http://www.drupalitalia.org/node/67595 See: HPE 3PAR Command Line Interface Administrator Guide HPE 3PAR StoreServ Storage Concepts Guide The documents are available at the following website: Hewlett Packard Enterprise Information Library ( For more information, search the web for the Hewlett Packard Enterprise technical white paper Disastertolerant solutions with HPE 3PAR Remote Copy Remote copy setup 13 14 Reviewing 3PAR Remote Copy requirements Procedure 1. Review general considerations for all configurations. General requirements on page 14 System restrictions on page 15 Software restrictions on page 15 Transport layer considerations on page 25 Creating remote copy virtual volumes on page Review considerations applicable to your remote copy configuration. 1-to-N remote copy considerations on page 46 SLD remote copy considerations on page 55 General requirements HPE 3PAR Remote Copy requires the use of a minimum of two HPE 3PAR StoreServ Storage systems. You must have HPE 3PAR Remote Copy licenses for all storage systems participating in remote copy replication. For more information about licensing and features, see the HPE 3PAR StoreServ Storage Concepts Guide, available at the following website: Hewlett Packard Enterprise Information Library ( The physical connections between all storage systems used with HPE 3PAR Remote Copy must be made through an IP-capable network or an FC SAN network. Make sure that your firewall is set to allow traffic over the designated RCIP ports, TCP 5785 and Make sure that all RCIP ports have unique IP addresses. To use remote copy to copy virtual volumes and perform replication and disaster recovery, you can use the 3PAR Management Console or the HPE 3PAR CLI.https://www.arquetopia.org/images/3par-inform-management-console-manual.pdf For more information about the 3PAR Management Console, the HPE 3PAR CLI, and the commands used with remote copy, see: HPE 3PAR Command Line Interface Reference HPE 3PAR Command Line Interface Administrator s Manual HPE 3PAR Management Console User Guide HPE 3PAR StoreServ Management Console User Guide The documents are available at the following website: Hewlett Packard Enterprise Information Library ( General considerations Distance between the systems. Systems in the same room can be connected through network adapter (NIC) switches, or through FC networks. Longer distances require other topologies. To use remote copy for disaster recovery, place the secondary storage system at a remote site, far enough away that the two sites are unlikely to be affected by the same disaster. In synchronous replication mode, the latency of remote copy writes increases with distance. Bandwidth. RCIP configurations can fully use all 1 Gbps links during the synchronization process. If you use networks with lower throughput, the throughput between systems running HPE 3PAR Remote Copy software might be capped by the network. Connection requirements. For more information, see Setting the transport layer on page 25. Data availability and speed. 14 Reviewing 3PAR Remote Copy requirements 15 To maintain availability, you must use more than one link to connect storage systems. HPE 3PAR Remote Copy requires at least two separate network connections between storage systems to ensure availability in case one of the networks fails. For optimal availability, connect the two HPE 3PAR StoreServ Storage systems to separate network equipment. When there are multiple physical links between the storage systems, HPE 3PAR Remote Copy uses all the available links that are configured for the same replication mode (synchronous or asynchronous periodic) to transmit data in parallel. When there are multiple physical links between the storage systems, HPE 3PAR Remote Copy uses all the available links that are configured for the same replication mode (synchronous, asynchronous periodic, or asynchronous streaming) to transmit data in parallel. System restrictions For more information about HPE 3PAR OS support levels, see the HPE 3PAR Operating System Upgrade Pre-Planning Guide, available at the following website: Hewlett Packard Enterprise Information Library ( Hewlett Packard Enterprise recommends that interrupt coalescing be disabled on the RCFC ports. To disable interrupt coalescing on the RCFC ports, use the SSMC, or see the controlport command in the HPE 3PAR Command Line Interface Reference. These guides are available at the following website: Hewlett Packard Enterprise Information Library ( Software restrictions HPE 3PAR Remote Copy does not support self-mirroring configurations. It cannot use a storage system to replicate its own primary volumes to itself. HPE 3PAR Remote Copy does not support multi-hop configurations. It cannot replicate a primary volume group to a secondary system and then replicate the volume group again from the secondary system to a third storage system. To limit the potential for data loss, Hewlett Packard Enterprise recommends that synchronous mode replication be used whenever the additional write latency induced by the network, plus the write latency induced by the target array, will not exceed the maximum write latency tolerable by the application whose data is being replicated. Remote copy and virtual domains HPE 3PAR Remote Copy checks for the presence of HPE 3PAR Virtual Domains (domains) on the secondary system to verify that you have mirrored the virtual volume to the same secondary system domain name as the primary-system domain name. For instructions on setting up domains, see the HPE 3PAR Command Line Interface Administrator Guide. When volumes are admitted to a remote copy group for which a virtual domain has been defined, the volumes on both sides must share the same domain name. System restrictions 15 16 If you are using volume autocreation, define the local user CPG and the target user CPG, as well as the local snapshot CPG and target snapshot CPG, when you create the group. All the CPGs defined must share the same domain name. Additional Information: For more information about domains and the HPE 3PAR Virtual Domains license, see the HPE 3PAR StoreServ Storage Concepts Guide. For instructions on setting up domains, see the HPE 3PAR Command Line Interface Administrator Guide, the HPE 3PAR StoreServ Management Console User Guide, or the HPE 3PAR Management Console Help. These documents are available on the following website: Hewlett Packard Enterprise Information Library ( 16 Remote copy setup 17 3PAR Remote Copy configurations Remote copy configurations are based on the relationship between a pair of storage systems, known as the remote copy pair. Within a remote copy pair, the primary storage system is the system that holds the volumes that are copied to the secondary storage system. HPE 3PAR Remote Copy supports the following configurations: M-to-N configurations: Unidirectional 1-to-1 configuration on page 17 Bidirectional 1-to-1 configuration on page 18 N-to-1 configuration on page 18 1-to-N configuration on page 19 Synchronous long-distance configuration on page 20 Review the remote copy configurations and select the configuration that is best suited for your system. To learn more about the asynchronous streaming feature, see the following topics: Asynchronous streaming mode on page 142 Asynchronous streaming mode for 1-to-1 configurations on page 204 Asynchronous streaming mode volume groups on page 148 Asynchronous streaming replication during normal operation on page 293 Asynchronous streaming replication during WAN failure on page 293 Setting snapshot frequency for asynchronous streaming mode on page 148 Snapshots in asynchronous streaming mode on page 327 Tracking asynchronous streaming volume groups on page 101 M-to-N remote copy configurations Unidirectional 1-to-1 configuration In a unidirectional 1-to-1 remote copy configuration, each storage system in the pair plays only one role: one system is the primary system, and one system is the secondary system. Figure 1: Unidirectional 1-to-1 remote copy on page 17 illustrates a unidirectional 1-to-1 remote copy configuration. The primary storage system holds only primary volume groups, and the secondary storage system holds only secondary volume groups. Primary storage system (System1) Primary volume group X (groupx) Primary volume group to secondary volume group Indicates direction of data replication Secondary storage system (System2) Secondary volume group X (groupx.r ) Figure 1: Unidirectional 1-to-1 remote copy 3PAR Remote Copy configurations 17 18 Bidirectional 1-to-1 configuration In a bidirectional 1-to-1 remote copy configuration, each storage system in the pair functions as both the primary and secondary system, and each system contains both primary and secondary volume groups. Each system provides backup for the other, according to the direction of replication specified for each volume group. Figure 2: Bidirectional 1-to-1 remote copy on page 18 illustrates a bidirectional 1-to-1 remote copy configuration. System1 System2 Primary volume group X (groupx) groupx to groupx.r Secondary volume group X (groupx.r ) Secondary volume group Y (groupy.r ) groupy to groupy.r Indicates direction of data replication Primary volume group Y (groupy) Figure 2: Bidirectional 1-to-1 remote copy N-to-1 configuration An N-to-1 remote copy configuration is composed of multiple remote copy pairs. NOTE: Because the secondary system participates in one remote copy pair for each primary system, a secondary system with one or two primary systems needs only two controller nodes. A secondary system with three or more primary storage systems must have four or more controller nodes. You can set up N-to-1 remote copy with up to four unidirectional or bidirectional remote copy pairs, as long as the remote secondary system has the minimum number of nodes required to support the number of source systems. 18 Bidirectional 1-to-1 configuration 19 Figure 3: N-to-1 remote copy on page 19 illustrates an N-to-1 configuration where: Bidirectional remote copy is maintained between remote copy pair System3 and System4. Unidirectional remote copy is maintained between System1 and System4 and between System2 and System4. One primary system participates in four remote copy pairs, one for each secondary system. You can set up 1-to-N remote copy in any of the following configurations: Four bidirectional remote copy pairs. Four unidirectional remote copy pairs. Figure 4: 1-to-N remote copy on page 20 illustrates a 1-to-N configuration, where: Unidirectional remote copy is maintained between a remote copy pair, System1 and System3. Data replication occurs without the need for dedicated remote copy pairs. The transport layer can be RCFC, RCIP, or FCIP, or a mixture of these, with up to five links per node. Only one RCIP link per node is provided; the other links may be RCFC or FCIP. To change the transport layer between the members of a remote copy pair, you must first remove the targets and set up all the groups again. Replication modes can be synchronous periodic, asynchronous periodic, asynchronous streaming, or a mixture of these. Synchronous long-distance configuration A synchronous long distance (SLD) remote copy configuration is composed of two targets: one synchronous group and one asynchronous periodic group. In SLD remote copy, one primary system uses two backup systems and participates in two remote copy pairs, one for each secondary system. In an SLD configuration, remote copy volume groups from the primary system are replicated to the two separate target arrays simultaneously. Data is replicated to one target in synchronous mode and to the second in asynchronous periodic mode. The target systems must each have appropriate network connections to the source systems to support the replication mode being used. There is no requirement that the closer of the two secondary systems be replicated to synchronously. While it is not a requirement, Hewlett Packard Enterprise recommends that remote copy be set up: Synchronously between the primary system and the closer of the two secondary systems be replicated to synchronously. In asynchronous periodic mode between the primary system and the secondary system that is physically farther apart (and therefore likely to share a lesser connection). SLD configurations differ from 1-to-N configurations as follows: 20 M-to-N configuration 21 In SLD configurations, remote copy volumes on the primary system are in a remote copy relationship with two secondary volume groups. Virtual volumes in the primary system are included in two primary groups, one copied to a secondary system in synchronous mode, and one copied to the other secondary system in asynchronous periodic mode. The two primary groups can be started and stopped independently of each other. For the SLD volume groups, one remote copy pair must be configured in synchronous mode and the other in asynchronous periodic mode. The SLD volume groups on the two backup systems are configured with a standby link for additional failover and recovery options. To set up SLD remote copy: 1. Remote copy is set up in synchronous mode between the primary system and one secondary system. For more information, see Synchronous mode on page Remote copy is set up in asynchronous periodic mode between the primary system and secondary system that are physically farthest apart (and therefore share a lesser connection). For more information, see Asynchronous periodic mode on page 141. The asynchronous periodic connection can be either all IP connections or, if all the SLD systems are fournode storage systems, all FC over IP network connections. For more information, see Fibre Channel over IP networks on page 23 and IP Networks on page 23. NOTE: SLD remote copy links can be bidirectional between two HPE 3PAR StoreServ Storage systems that are in synchronous relationship with each other. This bidirectional synchronous relationship enables customers to configure two SLD configurations among three HPE 3PAR StoreServ Storage systems. Figure 5: SLD remote copy on page 21 illustrates an SLD remote copy configuration. Primary system (SystemA) Primary volume group A (groupa) Asynchronous periodic mode Synchronous mode Secondary system (SystemB) (Standby link) Secondary system (SystemC) Secondary volume group A (groupa.r 1 ) Secondary volume group A (groupa.r 2 ) Figure 5: SLD remote copy Because SLD configurations include a standby link, as illustrated in Figure 5: SLD remote copy on page 21, this configuration allows for an alternate replication path and recovery path during a failover. 3PAR Remote Copy configurations 21 22 3PAR 3PAR 3PAR 3PAR Selecting network connections Procedure 1. Review possible network connections. IP Networks on page 23 Fibre Channel networks on page 22 Fibre Channel over IP networks on page Review general network information for remote copy. Reviewing 3PAR Remote Copy requirements on page 14 Network connection types Storage systems in a remote copy pair are connected through a dedicated link or through a network, as illustrated in Figure 6: Remote copy links on page 22. RCIP connects two systems over GigE ports. FCIP is RCFC that is extended over a long-distance wide area network (WAN) using FCIP routers. Where latency and bandwidth are not concerns, and where the anticipated amount of data to be replicated is high, FCIP can be a better choice than RCIP over network adapter (NIC). FCIP allows asynchronous periodic data replication over longer distances, without introducing network adapter (NIC) into the SAN. Fibre Channel networks RCFC can be set up only on storage systems that communicate over FC SAN. Be sure that you understand the FC SAN that is used to connect the storage systems. Remote Copy systems must be configured to be in the same FC SAN and zone. Each storage system should have a pair of HBAs installed for load sharing and fault tolerance. Before HPE 3PAR OS 3.1.2, an RCFC transport layer required that an HBA on at least two different nodes in the HPE 3PAR StoreServ Storage system be configured for and dedicated to remote copy. In addition, the front-end ports on an HBA had to be entirely configured for RCFC; their use could not be for different transport methods. For HPE 3PAR OS and later, the 3PAR StoreServ 7000 storage allowed ports on an HBA to be configured individually for both host and remote copy support. The HBA can be shared by the host and 22 Selecting network connections 23 RCFC only; it cannot be shared by RCFC and DISK; by the host and DISK; or by the host, RCFC, and DISK. All other storage platforms still needed the entire front-end HBA to be configured for RCFC. As of HPE 3PAR OS MU2, the same HBA port configuration functionality that is allowed on 3PAR StoreServ 7000 Storage systems is allowed on 3PAR StoreServ Storage systems. For newer storage systems, such as the 3PAR StoreServ 8000 Storage and the 3PAR StoreServ Storage, individual ports can be set either on a front-end HBA for RCFC or for host connectivity. IP Networks The network adapter (NIC) interface and the management Ethernet port of the HPE 3PAR StoreServ Storage system controller node must be on different IP subnets. If you configure the interface and port on the same subnet, remote copy packets might go over the management port and would no longer be available to the HPE 3PAR Remote Copy. Hosts that access the HPE 3PAR StoreServ Storage systems for management purposes must not be on the same subnet as the RCIP ports. If you add host computers to the remote copy subnet, IP packets might arrive through the management interfaces and leave through the RCIP interfaces. NOTE: Be sure that you understand the IP network that will be used to connect the storage systems. Industrystandard rules governing IP networks apply. Fibre Channel over IP networks In a Fibre Channel over IP (RCFC over IP) network setup, on all systems, use FC connections that pass through routers to cross an IP network. Synchronous replication mode is not allowed when running RCFC over a SAN fabric extended over IP. For more information, see Volume group replication modes on page 139. IP Networks 23 24 Gathering setup information Procedure 1. Contact your network administrator to obtain: IP addresses or 64-bit World Wide Name (WWN) address information for the interfaces of the storage systems Gateway IP addresses, netmask, and IP addresses for each link Any additional details about the network connections that might be useful 2. Verify that the firewall settings allow the remote copy systems access to TCP port 5785 and port Gathering setup information 25 Setting the transport layer Procedure 1. Review transport layer requirements. See: Transport layer considerations on page Set the transport layer. See: Remote copy over IP on page 26 Setting up remote copy over Fibre Channel on page 33 Setting up RCFC over an IP network on page 37 For more information about the CLI commands in this chapter, see: Remote copy command descriptions on page 310 HPE 3PAR Command Line Interface Reference, available at the following website: Hewlett Packard Enterprise Information Library ( Transport layer considerations RCIP RCFC For RCIP, each storage system in the remote copy configuration must have at least two nodes. For RCIP configurations, the array management interface cannot be on the same subnet as the RCIP network. For RCIP, each network adapter (NIC) interface must use a unique IP address. With RCIP, a pair of IP ports on the node pairs in an array may have a remote copy relationship with up to two other arrays. In other words, a pair of RCIP ports on an array may send data to up to two different remote copy targets on two different arrays, and may be the remote copy target for those same two arrays. Guaranteed bandwidth on the network is especially important when replicating synchronously over RCIP; the bandwidth must be large enough to ensure that no performance issues arise from replicating data synchronously. For asynchronous periodic replication, the bandwidth must be large enough to ensure that the RPO can be met. For RCFC, each storage system should have a pair of HBAs installed. The HBA pair is required for load sharing and fault tolerance. The HBAs in each storage system connect those systems through FC SAN, using FC cable connections (see Figure 7: Remote copy links on page 26). NOTE: When configuring an RCFC port, ensure the IntCoal attribute is disabled. For instructions on how to disable this attribute, see Disabling IntCoal on page 34. For HPE 3PAR OS and later, individual ports can be configured for RCFC and host-connect on a common HBA, for the following HPE 3PAR StoreServ Storage systems: 3PAR StoreServ Storage 3PAR StoreServ Storage 3PAR StoreServ 9000 Storage 3PAR StoreServ 8000 Storage 3PAR StoreServ 7000 Storage For more information, see Configuring ports for RCFC on page 33. Network address translation HPE 3PAR Remote Copy does not support network address translation (NAT) over RCIP or FCIP. Remote copy over IP RCIP initial remote copy pair Figure 8: Network and RCIP setup example initial pair on page 26 illustrates the initial remote copy pair in an RCIP configuration. These links use a network adapter (NIC) port from each of the nodes in the storage systems that belong to the remote copy pair. RCIP configurations can use up to eight links between systems. Up to eight nodes can each have one network adapter (NIC) port contributing links to an RCIP remote copy pair. If these ports were not set up during the initial setup of the storage system, or if the configuration has changed, reconfigure the ports before you set up the remote copy transport layer. CAUTION: The network adapter (NIC) interface and the management Ethernet port of the HPE 3PAR StoreServ Storage controller node must be on different IP subnets. If the management interface and RCIP ports are configured on the same subnet, remote copy packets might go over the management port, and would therefore not be available to the HPE 3PAR Remote Copy software. Setting up the remote copy interface for RCIP Procedure 1. To start remote copy, issue the following command: startrcopy 2. Issue the following command for an Ethernet port on one remote copy system: cli controlport rcip addr Where: IP address assigned to the Ethernet port Netmask to be assigned Location of a primary system Ethernet port, expressed as node:slot:port 3. To confirm that you want to make the gateway change, enter y. 4.