StoreOnce 6600 Installation Planning and Preparation Guide

Transcription

1 StoreOnce 6600 Installation Planning and Preparation Guide Abstract This guide is intended for customers to prepare for HPE service specialists to install the HPE StoreOnce 6600 System. Following the procedures in the guide will help ensure that all environmental and networking prerequisites are in place before HPE service specialists arrive to install the product and carry out the initial configuration. This document assumes that the product has not yet been delivered. It does not describe the actual installation and configuration steps. Read this document and then complete the checklist at the beginning before the HPE service engineer arrives to install the HPE StoreOnce 6600 System. Part Number: BB Published: March 2017 Edition: 3

2 2017 Hewlett Packard Enterprise LP Notices The information contained herein is subject to change without notice. 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. Acknowledgments Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java and Oracle are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group.

3 Contents Checklist for completion before installation...5 Purpose of the StoreOnce checklist... 5 Verify customer details... 5 Verify product configuration...5 Verify location... 6 Verify Power/PDU requirements...7 Verify Optional Hardware requirements...7 Verify backup strategy requirements... 8 Verify network requirements...9 Verify Fibre Channel requirements...10 Verify miscellaneous requirements The HPE StoreOnce 6600 System StoreOnce 6600 system configuration Space requirements for HPE StoreOnce 6600 System...14 Further guidelines for locating the HPE StoreOnce 6600 System...14 Warnings and cautions Product specifications Product dimensions...16 Product weight...16 Power/Power Distribution Units requirements...16 Power specification...16 Power Distribution Units Introduction Half-height vertical form factor...18 Midheight form factor Full-height form factor...18 Connecting to your network What is a Virtual Interface (VIF)? Types of VIF address...20 Ethernet connectivity supported Ethernet connectivity not supported Physical Ethernet connection requirements Number of physical ports required...22 Network bonding modes...22 Subnets and IP address requirements VLAN guidelines Reserved IP address range...24 Firewalls Fibre Channel connection...25 Fibre Channel considerations...25 FC Login Considerations with StoreOnce Catalyst Contents 3

4 VTL port assignment considerations Preparing for installation Tools required...27 Related information Licenses User roles and accounts...28 Support and other resources Accessing Hewlett Packard Enterprise Support...29 Accessing updates Customer self repair Remote support...30 Warranty information Regulatory information Documentation feedback...31 Additional regulatory information...32 Belarus Kazakhstan Russia marking...32 Turkey RoHS material content declaration...33 Ukraine RoHS material content declaration Contents

5 Checklist for completion before installation Purpose of the StoreOnce checklist Use the checklists in this chapter to ensure that: You understood the location, power, and networking/fibre channel requirements of the product at the time of placing the order. The environment is ready for system installation. The information that the service specialist needs to install and configure the system is available. The rest of this guide contains detailed information about the choices that are presented in the checklists. If you are new to this product, it is recommended to read the guide before completing the checklists. Verify customer details Procedure Record the following information so it is available during the installation. 1. Customer Site Name:... Mailing Address:... Installation Site Address:... Site Telephone Number: Customer Contacts a. Name:... Telephone:... Alternate Telephone:... Address:... b. Name:... Telephone:... Alternate Telephone:... Address:... Verify product configuration Procedure Record the following information so it is available during the installation. 1. List hardware products purchased. Provide quantity and capacity, as appropriate. Racks and couplets:... Checklist for completion before installation 5

6 StoreOnce Optional Hardware:... Additional storage: Note any requirements for: Capacity upgrades and licenses... Replication and StoreOnce Catalyst licenses... Security Pack licenses... StoreOnce Optional Hardware licenses... Additional cabling requirements (make sure that the cables are prelaid) Ensure that the delivered materials match the Bill of Materials (BoM) and that there is no damage to boxes or components. Verify location Procedure At the time of placing the order, ensure that there is a suitable location with access to install the product. The location must be a data center environment and not an office environment and conform to the following requirements: 1. The receiving dock, storage area, and receiving area are large enough to allow movement of and access to crated or packed equipment. 2. The floors, elevators, and ramps are able to support the weight of the delivered equipment as it is moved to the installation location. 3. The installation location must provide: Sufficient space to accommodate the installed product. When installing two racks, install the units next to each other to ensure that there are no problems with cable lengths. NOTE: Sufficient space, at least 12 inches (30 cm), must be available to the right-hand side of the rack to ensure that there is enough clearance to maneuver the disks in and out of drawer 2. Ensure that there is also sufficient space to the front of the rack to extend the drawers fully approximately 43 inches (1080 mm) from the inside of the columns at the front of the rack. Appropriate power, air conditioning, cabling, and fire protection. Adequate protection from electrostatic discharge (ESD). Adequate protection from electrical/radio frequency interference. Adequate protection from dust, pollution, and particulate contamination. Adequate acoustic insulation for operating the system. 6 Verify location

7 Verify Power/PDU requirements NOTE: The Power/PDU requirement varies depending upon the number of racks, couplets and storage, and the input voltage. Procedure 1. At the time of placing the order, make sure that the location can support the HPE StoreOnce 6600 System s input power and power outlet requirements. 2. Before installation, confirm that you have specified the correct PDU for your geographical location and connector type and that you have sufficient power outlets. 3. PDU option and connector type Provide details of: PDU option:... Connector plug type:... Connector socket type: Power outlets Two outlets are required for each couplet. But it is recommended that each rack is installed with four outlets to allow for ease of expansion, even if the rack has only one couplet. Number of power outlets available:... Verify Optional Hardware requirements StoreOnce software supports the addition of 10 GbE Network and/or Fibre Channel PCIe cards to the basic configuration. The basic hardware configuration per server node consists of: Four 1 GbE network ports Two 10 GbE PCIe network ports in PCIe slots 1 and 4 Two blank PCIe slots in slots 5 and 6 The two blank PCIe slots are available for StoreOnce Optional Hardware. The required Optional Hardware kit must be ordered in addition to the basic configuration. IMPORTANT: Optional Hardware cards must be installed in pairs (to maintain high availability configurations). All nodes in the cluster must have the same type and model of card installed. Procedure 1. If you require VTL target libraries or StoreOnce Catalyst over Fibre Channel, you must purchase one of the Fibre Channel Optional Hardware kits. Have you ordered the required number of Fibre Channel StoreOnce Optional Hardware kits for PCIe slots 5 and 6? NOTE: The same Optional Hardware configuration must apply to all nodes in the cluster. If you require Fibre Channel connectivity, you must plan to install Fibre Channel cards in PCIe slots 5 and 6 of all nodes. For example, a two-couplet cluster will require eight Fibre Channel cards (2 x 4 nodes). Speed of FC connection required, 8 Gb or 16 Gb?... Verify Power/PDU requirements 7

8 Number of FC Optional Hardware kits ordered? If you do not intend to use Fibre Channel and require extra 10 GbE connectivity, have you ordered the required number of 10 GbE SFP Network StoreOnce Optional Hardware kits for PCIe slots 5 and 6? All 10 GbE cards are supplied with optical SFP+ transceivers. NOTE: All configurations have 10 GbE Network connectivity as standard because two 10 GbE cards are installed in PCIe slots 1 and 4. If you require Fibre Channel connectivity, do not plan to install 10 GbE Network cards in PCIe slots 5 and 6 of any node. Number of 10 GbE Optional Hardware kits ordered?... Verify backup strategy requirements Your backup strategy will impact upon networking and Fibre Channel decisions. IMPORTANT: Fibre Channel cards are not part of the basic configuration. If Fibre Channel connectivity is required, StoreOnce Optional Hardware Fibre Channel Kits must be purchased and installed in each node in the cluster. Procedure 1. Do you intend to create virtual tape libraries as backup targets (FC only)?... Which backup application will the system use? Do you intend to create NAS shares as backup targets?... (IPv4 and IPv6 are supported for NFS; only IPv4 is supported for CIFS) Which backup application are you using? If creating CIFS shares, will you be using Active Domain (AD) authorization?... NOTE: If the StoreOnce System is part of an AD domain, it is possible to add external users and groups on the same domain as StoreOnce users with access to all StoreOnce features. Is your domain server on an IPv4 or IPv6 network? The following AD domain details will be required to configure AD. Have them ready to provide to the HPE Support engineer. Once the StoreOnce System has been joined to an AD domain, you can configure users or groups on the StoreOnce System. The users or groups must exist on the AD domain, where the passwords are also configured. Only the name is required to configure AD users or groups on the StoreOnce System. a. Do you wish to create Local Administrators for the CIFS server only, Y/N?... b. Do you wish to create AD (External) users or groups with access to all StoreOnce features, Y/N?... c. Provide details if you want HPE Support to configure these users Verify backup strategy requirements

9 a. The AD domain name... b. The user name and password of the Domain Administrator or a delegated user with Domain Administrative rights... c. The type of network, IPv4 or IPv Do you intend to create StoreOnce Catalyst stores as backup targets over Ethernet?... Do you intend to create StoreOnce Catalyst stores as backup targets over FC?... Do you intend to use Federated Catalyst?... For StoreOnce Catalyst FC, decide how many FC logins will be required from the clients... Which backup application are you using?... If Symantec, have you installed the appropriate StoreOnce Catalyst OST plugin on the Media Servers?... Verify network requirements Network requirements must be defined and sufficient physical connections on switches and IP addresses must be available. IMPORTANT: It is essential that the information in the following section is completed and given to HPE Support Services before the install. The installation cannot proceed unless all networking parameters are known and the network infrastructure to support the required configuration is in place. Your HPE service specialist will provide you with a record of the Virtual IP addresses after the network configuration has been completed. You will use the Virtual IP addresses to connect to the StoreOnce Management Console (from the GUI or CLI) and to configure backup and replication targets. Procedure 1. Confirm the network cabling meets requirements. 1 GbE networks: verify that the cabling is CAT5E or CAT6 copper with RJ45 connectors? GbE network: what cabling is used for the 10 GbE Ethernet connections (optical or copper)?... (Optical SFP+ transceivers are supplied with the product and with 10 GbE SFP Optional Hardware Kits.) 2. Do you wish to configure all eight potential nodes in the cluster at installation (recommended)?... If not, how many are to be configured? Will your configuration implement 10 GbE Network StoreOnce Optional Hardware in PCIe slots 5 and 6? NOTE: If you use the Optional Hardware slots for 10 GbE cards, you cannot install Fibre Channel cards. The same Optional Hardware configuration must apply to all nodes in the cluster. 4. Do you wish to configure DNS servers? If yes, provide the IP addresses (up to 3, IPv4 and/or IPv6) Do you have sufficient physical network connections for your configuration? The number required depends upon the way that you configure each Port Set in the network configuration. See also Physical Ethernet connection requirements on page 21. Verify network requirements 9

10 6. The number of physical ports and requirement that ports are bonded restricts the number of available Port Sets. Decide how Management and Data subnets will be assigned to port sets. Port set used for Management subnet Port sets used for Data a. Which ports will be used to connect to the Data subnets? For example, both 10 GbE Ethernet ports for backup to StoreOnce target devices and two of the 1 GbE Ethernet ports for replication and StoreOnce Catalyst Copy. Ports used for back up to target devices... Ports used for Replication and/or StoreOnce Catalyst Copy... b. What network bonding mode will be used for each data port set?... c. Will each data port set be VLAN enabled?... d. Are jumbo Frame sizes required? (default = 1500 bytes, minimum = 1280 bytes, maximum = 9000 bytes)... a. Which ports will be used to connect to the Management subnet? (normally two or more of the 1 GbE Ethernet ports)... b. What IP address will be used for the Virtual Management Interface (to connect to the StoreOnce Management console)?... c. What network bonding mode will be used?... d. Are jumbo Frame sizes required? (default = 1500 bytes, minimum = 1280 bytes, maximum = 9000 bytes)... e. Is static routing required for the Management or Data subnet??... f. If yes, how many? (Up to 10 IPv4 and IPv6 static routes may be configured.) Have you calculated the total IP addresses required for your configuration?... To calculate this value, you must first define all subnets that will be configured for each port set. 8. Do you intend to use Data In Flight encryption?... You will require a Security Pack license installed on all couplets in the cluster. IMPORTANT: Data in flight encryption is intended to be used to secure links between data centers for StoreOnce Replication or Low-Bandwidth Catalyst Copy operations. Using Data In Flight Encryption for direct backup operations to the StoreOnce appliance over a local network is not supported due to the performance impact of the encryption. IPSEC is not supported for use on IPv6 subnets Verify Fibre Channel requirements Procedure If you are using VTL for backup, Fibre Channel connection is required. It is also required if you wish to use StoreOnce Catalyst over Fibre Channel on your system. 1. Have you ordered the required number of Fibre Channel StoreOnce Optional Hardware kits for PCIe slots 5 and 6? NOTE: The same Optional Hardware configuration must apply to all nodes in the cluster. If you require Fibre Channel connectivity, you must plan to install Fibre Channel cards in PCIe slots 5 and 6 of all nodes. For example, a two-couplet cluster will require eight Fibre Channel cards (2 x 4 nodes). 2. Is Fibre Channel configured correctly for Virtual Tape Libraries (VTL) and/or StoreOnce Catalyst and does the configuration support failover? 10 Verify Fibre Channel requirements

11 Verify miscellaneous requirements Procedure If NTP, and SNMP requirements are specified before installation, the HPE service specialist may be able to help you configure your system. StoreOnce Remote Support is configured on the StoreOnce GUI and provides a replacement for the HP Insight Remote Support (IRS) solution, which uses SNMP. 1. NTP is recommended for time synchronization. a. Do you want NTP server connection?... b. What is the IP address of the NTP servers? (Up to two NTP servers are supported) c. Will alerts be configured?... d. Who will receive the s? (Provide a list of addresses and what they will receive, that is, Information / Warning / Alert) e. SMTP server address... Mail From... Reply To Do you wish to use the integrated StoreOnce Remote Support feature?... StoreOnce Remote Support requires a connection through the customer firewall to connect to the StoreOnce System. What is the protocol (http / https / socks) and IP address for connection to the StoreOnce System?... Will you use proxy authentication?... If so, what are the credentials?... If an issue is reported that automatically generates a support case, HPE Support may wish to contact you. You will need to configure: Technical contact name... Technical contact phone details... address for service alert notification Do you wish to configure SNMP traps?... NOTE: SNMP traps are used by other tools internal to the organization and for HP Remote Insight Remote Support, IRS. However, you cannot use IRS at the same time as the StoreOnce Remote Support feature. Provide configuration settings IP address of SNMP management server... TRAP targets (Provide a list) Verify miscellaneous requirements 11

12 Community strings (Provide a list) Checklist for completion before installation

13 The HPE StoreOnce 6600 System StoreOnce 6600 system configuration The HPE StoreOnce 6600 System is supplied partially configured. It consists of one or two HP 642 Intelligent Rack Assemblies with stabilizers and internal network switches. The rack contains at least one base couplet (consisting of two server nodes and two disk enclosures) and two switches. The two switches are dedicated to support a network internal to the product. They cannot be used in an external network. Up to two couplets may be installed in each rack. Additional capacity expansion kits may be purchased to expand storage. Up to five StoreOnce 88 TB expansion kits may be installed per couplet; these expansion kits are additional disks that are installed in the existing disk enclosures. Further expansion is by adding a couplet Figure 1: 6600 StoreOnce couplet 1. Node B 5. 1U support shelf 2. Node A 6. Drawer 2 (right-hand side of enclosure) Table Continued The HPE StoreOnce 6600 System 13

14 3. Disk enclosure B 7. Drawer 1 (left-hand side of enclosure) 4. Disk enclosure A Space requirements for HPE StoreOnce 6600 System Sufficient space is required to the front and to the right-hand side of the rack to ensure that there is enough clearance to maneuver the disks in and out of drawer 2. To the front approximately 43 inches (1080 mm) from the inside of the front rack column and 40 inches (1000 mm) from the front of the rack. To the right at least 12 inches (300 mm). 80 mm 1080 mm 1000 mm Figure 2: Clearance required to maneuver disks in drawer mm Further guidelines for locating the HPE StoreOnce 6600 System Use the rack only for the StoreOnce 6600 system and supported couplet expansion. Do not plan to install additional units, such as Ethernet network switches, in the rack. If you do so, you may not be able to add a couplet. When installing a second couplet, it is located in rack positions U20 to U34 inclusive. If installing a two-rack system, the racks must be located next to each other to ensure that there are no problems with cable lengths. If installing a one-rack system, be sure to plan for future expansion. Warnings and cautions The customer is not expected to unpack and handle the product. However, if the customer does unpack or move the product, care must be taken to avoid damage to people and equipment. The following safety and handling instructions apply. 14 Space requirements for HPE StoreOnce 6600 System

15 WARNING: To reduce the risk of personal injury or damage to the equipment, before installing equipment be sure that: The leveling jacks are extended to the floor. The full weight of the rack rests on the leveling jacks. If it is a single-rack installation, the stabilizing feet are attached to the rack. The racks are coupled together in multiple-rack installations. Only one component is extended at a time. A rack may become unstable if more than one component is extended for any reason. WARNING: To reduce the risk of personal injury or equipment damage when unloading a rack: At least two people are required to unload a rack safely from a pallet. The weight of a 642 Intelligent Rack can be between that of a Single Couplet Rack (246 kg) and a fully configured two Couplet rack (910 kg). It can stand more than 2.1 m (7 ft) tall, and may become unstable when being moved on its casters. Never stand in front of a rack when it is rolling down the ramp from the pallet. Always handle a rack from both sides. The HPE StoreOnce 6600 System 15

16 Product specifications Product dimensions Table 1: Physical dimensions Shipping Rack x x inches (h x d x w) x x 90 cm Installed x x inches (h x d x w) x x cm Product weight The weight varies depending upon the number of racks, couplets, and storage. Table 2: Weight specifications (1 phase and 3 phase) kgs lbs Single couplet Single couplet with maximum storage added to couplet Two couplets Two couplets with maximum storage added to couplets Power/Power Distribution Units requirements Power specification The power factor is close to unity. Miniature Circuit Breakers (MCBs), type C, are required to prevent tripping with the initial power on surge of the racks. Table 3: Power specification at 208V Single rack configuration A W VA BTU/hour 1 couplet with minimum storage (30 disks) 1 couplet with maximum storage (140 disks) Table Continued 16 Product specifications

17 Single rack configuration A W VA BTU/hour 2 couplets with minimum storage in couplet 2 (170 disks) 2 couplets with maximum storage (280 disks) Table 4: Power specification at 220V Single rack configuration A W VA BTU/hour 1 couplet with minimum storage (30 disks) 1 couplet with maximum storage (140 disks) 2 couplets with minimum storage in couplet 2 (170 disks) 2 couplets with maximum storage (280 disks) Table 5: Power specification at 240V Single rack configuration A W VA BTU/hour 1 couplet with minimum storage (30 disks) 1 couplet with maximum storage (140 disks) 2 couplets with minimum storage in couplet 2 (170 disks) 2 couplets with maximum storage (280 disks) Power Distribution Units Introduction The HPE StoreOnce 6600 System supports a selection of Power Distribution Units. For further information on PDU features, refer to the Support page on and search on: Basic Power Distribution Units (bpdu) Remote Monitored Power Distribution Units (mpdu) Power Distribution Units 17

18 IMPORTANT: Specify which power option will be used when placing the order for the HPE StoreOnce 6600 System. Half-height vertical form factor All installations require two PDUs for a rack with a single couplet and four PDUs for a rack with two couplets. A rack with a single couplet may be installed with four PDUs but can be powered from only two of the PDUs. However, if future expansion to a second couplet is planned, it is advised to provision power for the remaining third and fourth connectors. Table 6: Basic Power Distribution Units PDU P/N Voltage VA (Max) Phase Input Connection H5M58A V Single NEMA L6-30P H5M68A V Single IEC A 3W H5M61A V Three-Phase Delta NEMA L15-30 Table 7: Remote Monitoring Power Distribution Units PDU P/N Voltage VA (Max) Phase Input Connection G9Z05A V Single NEMA L6-30P G9Z06A V Single IEC 332P6 Splashproof Midheight form factor All installations require two PDUs for a rack with both a single couplet and two couplets. Table 8: Basic Power Distribution Units PDU P/N Voltage VA (Max) Phase Input Connection H5M71A V Single IEC A 3W H5M72A / V Three-Phase WYE IEC A 5W Table 9: Remote Monitoring Power Distribution Units PDU P/N Voltage VA (Max) Phase Input Connection D9N55A V 400V Three-Phase WYE IEC 516P6 Splashproof Full-height form factor All installations require two PDUs for a rack with both a single couplet and two couplets. 18 Half-height vertical form factor

19 Table 10: Basic Power Distribution Units PDU P/N Voltage VA (Max) Phase Input Connection H5M73A / V Three-Phase WYE IEC A 5W H5M67A / V Three-Phase WYE IEC 530P6 Product specifications 19

20 Connecting to your network What is a Virtual Interface (VIF)? Each couplet is a paired combination of two nodes that are directly connected in failover pairs. If one node fails, the system is designed to failover to the other node without any external interaction from the customer. The StoreOnce System uses a concept called a Virtual Interface (VIF) to make failover possible. The physical IP addresses relate to the physical ports that are used to connect the StoreOnce System to the external network. The Virtual Interface (VIF) addresses are the IP addresses that the customer uses to connect to the StoreOnce System. Because these IP addresses are never directly linked to a physical port, they continue to function correctly if a node fails. Types of VIF address There are two instances of VIF addresses: the Cluster Management IP address and Data VIF IPs. Cluster Management IP address: The Cluster Management IP address is the address that you use to access the StoreOnce Management functions. Because the Cluster Management IP address is dynamic on the system, it can be active on the master node and passive on the other nodes. If the master node fails for any reason, the Virtual Management Console simply moves to another node and can still be accessed using the same Cluster Management IP address. There is only one Cluster Management IP address per StoreOnce System (the cluster), but each node requires a physical connection to the Management subnet and the Cluster Management VIF IP address must be in the same subnet range as the Management subnet. Assuming that the Management Console requires access to the external network (to allow access to the StoreOnce CLI and GUI), the Management subnet must use the same IP address protocol as the DNS servers. Data VIF IPs: The Data VIF IP addresses are the IP addresses that you use to configure Catalyst and NAS backup targets, VTL and NAS replication configurations, and Catalyst copy jobs. The Data VIF IP address is associated to a service set, which is the set of services (VTL, NAS, StoreOnce Catalyst, Catalyst Copy, replication, and so on), available for a node. If the physical node fails, the service set will failover to the other node in the couplet, and the Data VIF IP address will also failover to be used by the corresponding physical ports on the other node. No change is needed to the IP address of the service set, allowing hosts and the StoreOnce System to function correctly. Each couplet has two nodes and, therefore, two service sets. The number of Data VIF IP addresses per service set depends upon the number and type of data subnets that have been configured. Ethernet connectivity supported IPv4 and IPv6 are supported. IPv6 is available for low-bandwidth activities, low-bandwidth StoreOnce Catalyst backup, StoreOnce Catalyst Copy. NFS NAS share creation and NAS/VTL Replication and the StoreOnce CLI and GUI. IPv4 is required for CIFS NAS share creation and high-bandwidth StoreOnce Catalyst backup. (VTL backup is only available over FC.) DNS is supported. There may be only one Management subnet, which provides access to the StoreOnce CLI and GUI, and that must be configured on a port set that is not VLAN enabled. The Management subnet is typically on a 1 GbE IPv4 or IPv6 network. If configured to do so, data may also be sent across this network. 20 Connecting to your network

21 NOTE: A port set refers to the physical ports to which the subnet connects. The number of physical ports available and the requirement for network bonding on each port set restricts the number of port sets that can be created. For example: Management may be configured across one pair of 1 GbE ports, and backups may be configured across the standard pair of 10 GbE network port. StoreOnce Catalyst copy and replication may then be configured across the remaining pair of 1 GbE Ethernet network ports. NOTE: StoreOnce Optional Hardware provides the facility to add a second pair of 10 GbE network ports to each node, but only if Fibre Channel connection is not required. Port sets that are not VLAN-enabled may be configured with one Subnet that uses the IPv4 protocol and one subnet that uses the IPv6 protocol, which is referred to as dual stack IP configuration. Port sets that are VLAN enabled may be configured with multiple virtual subnets and each VLAN tag can support an IPv4 and an IPv6 subnet (up to a maximum of 128 VLANs across the whole cluster). A network gateway may be optionally configured in all subnets. This default network gateway will attempt to route any network traffic to IP addresses that are not in the configured subnets. If both IPv4 and IPv6 subnets are configured, one IPv4 and one IPv6 subnet must be designated as containing the default gateway. StoreOnce software supports Static Routing. This feature is available for the Management and Data network subnets of HPE StoreOnce 6600 Systems. It may be required where a Data subnet is configured for access across the WAN, and the Management subnet also requires access to a network that is not accessible via the configured default gateway (which is on the Data subnet). An example would be where the AD server is on an isolated management network subnet with routing restrictions. The network configuration applies to all nodes in the cluster. For example, you cannot have separate network configurations for each couplet in the cluster. The IPSec protocol is supported for subnet Data In Flight encryption. This feature requires a Security Pack license on each couplet in the cluster. IMPORTANT: Data in flight encryption is intended to be used to secure links between data centers for StoreOnce Replication or Low-Bandwidth Catalyst Copy operations. Using Data In Flight Encryption for direct backup operations to the StoreOnce appliance over a local network is not supported due to the performance impact of the encryption. IPSec cannot be configured on a management only subnet and it cannot be configured on an IPv6 subnet. Ethernet connectivity not supported DHCP VTL support on Ethernet using the iscsi protocol Physical Ethernet connection requirements Be aware of the following when preparing the network environment. All network subnets must use bonded ports to ensure high availability if failover occurs. Incorrect cabling can negate the high availability infrastructure of the product. It is recommended that there are two switches for each network to which you are connecting. For EACH bonded pair of cables, connect the first cable to Switch 1; connect the other cable to Switch 2. For Mode 4 (LACP) bonding, this configuration is only possible if the two switches are joined via a Virtual Switch Link. Ethernet connectivity not supported 21

22 If using separate subnets for data and management and multiple external switches are used, these switches must support a Multi-Chassis Link Aggregation protocol that is compatible with the rest of the network switch infrastructure. StoreOnce software allows you to define the amount of data contained in an Ethernet frame, the default it 1500 bytes. Larger size frames, often referred to as Jumbo frames, can improve performance of the Port Set; the maximum is 9000 bytes. Smaller frames are also supported; the minimum is 1280 bytes. IMPORTANT: Other devices on the network (clients and switches) must also be configured to enable Jumbo frames for transfer of frames larger than 1500 bytes to be possible and to avoid packets fragmenting or dropping. When using the 10 GbE network, optical SFP+ transceivers are supplied with the product and 10 GbE Optional Hardware kit. The 1 GbE ports have a RJ45 connection type; CAT6 is recommended, CAT5E is the minimum requirement. Number of physical ports required The number of physical connections that are required depends upon the port sets that you intend to configure for each subnet and the number of couplets in the system. Do not confuse this number with the number of IP addresses required. Table 11: Number of physical network ports required per port set Port Set Traffic type One couplet Two couplets Three couplets Four couplets 1 GbE ports 2 per node Management only GbE ports (basic) 10 GbE ports (optional) 2 per node Data only per node Data only GbE ports 4 per node Management and Data 1 GbE ports 3 per node Management and Data To calculate the total number of physical connections required Add the totals in the appropriate column. For example, on a 4 couplet system with Management on two 1 GbE Ethernet ports, Data on the two standard 10 GbE ports and Data on two Optional Hardware 10 GbE ports, 48 physical connections are required. Network bonding modes Each set of network ports on the appliance can be configured either on separate Subnets or in a bond with each other (1 GbE and 10 GbE ethernet ports cannot be bonded together). Three bonding modes are supported: 22 Number of physical ports required

23 Mode 1 (Active/Backup) Mode 1 is the most simple bonding mode; it allows network traffic via one active port only and requires no specific extra switch configuration. It is recommended for simple network connections. If the active network link fails, then traffic moves to the backup port. Mode 4 (IEEE 802.3ad Dynamic Link Aggregation) This bonding mode is also known as LACP and requires a special external switch configuration. It provides a link aggregation solution, increasing the bond physical bandwidth, but only works if all the ports in the bond are connected to one switch or switches joined by an interswitch link. It is recommended when: The customer wants to increase throughput to the StoreOnce appliance. Trunks between switches on the customer network already use LACP mode. The LACP protocol only works when it is configured on both the network switch and StoreOnce end of the connection. Refer to your switch documentation for information on LACP configuration. Mode 6 (Active Load Balancing) This mode provides a load balance solution. It does not require specific external switch configuration but does require the switch to allow ARP negotiation. It can be used in a 2 switch configuration. This configuration is recommended for backup data performance and also for resiliency of both data and management network connectivity. However, in some environments ARP packet negotiation may be disabled within the network infrastructure, so this mode may not be appropriate. NOTE: When using bonded ports the full performance of bonded links are only realized if multiple host servers are providing data, otherwise data will still use only one network path from the single server. Subnets and IP address requirements The total number of IP addresses that you require depends upon the number and type of subnets that you configure, and the number of couplets that you have installed. Use the following guidelines to develop a list of subnet details for the HPE Support engineer: The Management subnet requires one IP address per node (as well as the Management VIF). This IP address must be IPv4 or IPv6 and use the same protocol as DNS servers. Dual stack IP configuration, where a subnet for IPv4 and a subnet for IPv6 may be configured on the same Port Set, is supported for Data subnets or a Management with Data (Both) subnet. Data subnets that are not VLAN enabled require one physical IP address per node and one virtual IP address per node. Data subnets that are VLAN enabled require one IP address per node and a VLAN tag ID. When the network subnet is configured, you are prompted to provide an IP address for a gateway, which will be used for routing management and/or data traffic to and from an external network. In addition, two network subnets will be designated as containing the default gateways; one for IPv6 and one for IPv4 subnets. StoreOnce software supports Static Routing. This feature is available for the Management and Data network subnets of StoreOnce Systems. It may be required, if access to the StoreOnce management interface is required from networks that are not accessible via the configured gateway on that network. For example, it may be required, if the AD server is on an isolated management network subnet with routing restrictions. Up to 10 IPv4 or IPv6 static IP addresses may be defined for the Management subnet. A Domain Name is optional. Subnets and IP address requirements 23

24 VLAN guidelines The user can configure up to a total of 128 different VLAN Subnets on each StoreOnce System; the VLAN Subnets may be consecutive or nonconsecutive. It is not permitted to configure VLAN Subnets on a Port Set that uses Mode 6 network bonding or on a Port Set that is used for Management. Each VLAN tag interface is configured using the VLAN ID index, which is the same as the switch VLAN ID number and must be an integer from 2 to Each VLAN tag interface can be configured for use with one IPv4 and one IPv6 subnet. For example: if a VLAN tag ID was configured for use with ports eth 0 and eth1 on IPv4, it can also be configured for use on IPv6 with that Port Set. It cannot be used with any other Port Set. VLAN tagging does not increase bandwidth because the bandwidth is bound by the physical speed of the Port Set. The number of open streams is bound by the specification for the StoreOnce appliance. StoreOnce monitoring is on the physical Port Set, not on each VLAN Subnet. VLAN tagging is not a multitenancy solution. Once configured, all StoreOnce services can bind / listen to all VLAN Subnets. For example, the NAS shares are available on all configured Subnets, and permissions are required to regulate access to shares. Reserved IP address range The StoreOnce System uses the x.x IP range for its internal network and this IP address range is not available for the external network. If a customer network uses the x.x IP range, it may cause conflict and unpredictable results. Firewalls StoreOnce products require access to other StoreOnce products for Replication or Catalyst Copy operations or restores to clients from StoreOnce Catalyst stores or NAS Shares. Customers may have firewall settings that restrict network access to allow only certain traffic through the network. It is recommended that all of the IP addresses configured for the StoreOnce cluster, which includes both physical and virtual IPs for source and target, are allowed within the firewall settings to ensure network connectivity. 24 VLAN guidelines

25 Fibre Channel connection Fibre Channel considerations IMPORTANT: If you require VTL target libraries or StoreOnce Catalyst over Fibre Channel, you must purchase one of the Fibre Channel Optional Hardware kits. VTL library emulation is supported only on Fibre Channel; StoreOnce Catalyst stores are supported on Ethernet and Fibre Channel. NAS is not supported on Fibre Channel. The StoreOnce Management Console and some of the other StoreOnce features, such as replication and Catalyst Copy, always require an Ethernet connection. When using FC to back up hosts, you must also connect to an Ethernet port. Care must be taken to ensure that there is no single point of failure in switch or fabric zoning that will negate the failover capabilities of the StoreOnce System and its autonomic restart ability. Conformance to the following rules will help to ensure successful failover Fibre Channel switches used with StoreOnce Systems must support NPIV. The preferred topology uses NPIV (N_Port ID Virtualization). Direct attach (private loop) and direct attach (point to point) topologies are not supported. For a full list, see NOTE: The HP Brocade SAN Switches support NPIV natively but the Cisco SAN Switches require that it is turned on on each port used StoreOnce Catalyst over Fibre Channel functions the same as StoreOnce Catalyst over Ethernet. The backup application will not perceive a difference. However, some configuration is required to set up the backup and restore connections between the ports on the StoreOnce System and the ports on the client servers. This configuration is done using the Fibre Channel Settings tab on the StoreOnce GUI. Virtual library devices are assigned to an individual interface. Therefore, for best performance, configure FC ports and balance the virtual devices across interfaces to ensure that one link is not saturated while others are idle. To keep the backup/restore environment simple and less susceptible to the effects of changing or problematic SANs, use WWPN zoning (rather than port based). Ensure that there are two switches in each fabric. When using switched fabric mode, zone Fibre Channel devices on the switch so that they are accessible only from a single backup server device. This ensures that other SAN events, such as the addition and removal of other FC devices, do not cause unnecessary traffic to be sent to devices. It also ensures that SAN polling applications cannot reduce the performance of individual devices. FC Login Considerations with StoreOnce Catalyst It is important to determine the number of concurrent backups and restore streams required for each port and, where necessary, configure the StoreOnce System to accept the required number of FC logins from the clients or hosts. On Linux, it is possible that a single client HBA port talking to a single StoreOnce HBA port can open multiple concurrent connections; that is backup and restore streams. However, Windows has a queue depth of 1. Catalyst over FC implements a multi-lun solution to allow multiple simultaneous connections from a Windows client. By presenting multiple LUNs a host port can open multiple simultaneous connections to a Fibre Channel connection 25

26 target StoreOnce port. The Devices per Initiator Port value in the Fibre Channel Settings determines the number of backup and restore connections that are allowed for each client login to that port on the StoreOnce System. If multiple concurrent backup streams are required, increase this value. The maximum allowed is 64. If a StoreOnce target port is used ONLY for Linux backups, the Devices per Initiator Port can be left at 1. If a StoreOnce target port is used for Windows backups the Devices per Initiator Port must be calculated, as described in Table 14. The number of paths available to a particular client is calculated as: number of client ports zoned * number of StoreOnce node ports zoned * devices per initiator port Table 12: Example relationships between devices per initiator port and number of connections on Windows and HP-UX Client-side StoreOnce System Devices per Initiator port Number of concurrent backup and restore sessions (per service set) 1 port zoned to 4 ports ports zoned to 4 ports ports zoned to 4 ports ports zoned to 2 ports 4 16 VTL port assignment considerations There are two FC cards for each node in a couplet and, therefore, four FC ports on each node. When creating a library the user may select individual drives or FC ports 1 & 2, FC ports 3 & 4 or FC ports 1, 2, 3 & 4. Port 1 and port 3 are on the first FC card, which is in slot 6; port 2 and port 4 are on the second FC card, which is in slot 5. It is important to ensure that the system has been cabled correctly when connecting to the FC SAN. If the user wishes to select one of the combined port options, both FC cards must be connected. Drives can only appear on one port, so when you choose a pair of ports, drives are automatically distributed evenly across both ports to ensure best performance and failover. After creating the library, it is possible to change the drive assignments using the Edit function on the Interface Information tab on the StoreOnce Management Console for the selected library. 26 VTL port assignment considerations

27 Preparing for installation Tools required Ensure that a keyboard and monitor are available for use as a management console during the initial configuration stage. NOTE: HPE does not recommend using a KVM installed in the rack because this will cause problems when a second couplet is added. In a fully expanded rack, there is no space for locating a KVM within the rack. Complete the checklists in the rest of this document and present them to the HPE service engineers when they arrive to install and configure the system. All other tools are provided by the HPE service specialist. Related information The following StoreOnce System documentation is available. StoreOnce 6500 and 6600 System User Guide StoreOnce System CLI Reference Guide StoreOnce System Linux and UNIX Configuration Guide HPE StoreOnce 6600 System Capacity Upgrade Guide StoreOnce Software Release Notes (minimum version = ) Use the following link to access appropriate documents for your product: Licenses There are two types of license: Full license (not time limited) Instant on or Demo (time limited to 90 days): This license allows you to try out StoreOnce Catalyst and VTL and NAS Replication functionality before paying for a full license. (Security features, Optional Hardware, and capacity expansion are not included in the Demo license.) The StoreOnce System licensing requirements are: All capacity expansion kits must be licensed. Each storage expansion kit contains a license that must be loaded. Each Optional Hardware card requires a license and all must be loaded before being activated. A single-couplet HPE StoreOnce 6600 System requires four licenses; two for each server. A fully expanded HPE StoreOnce 6600 System has eight nodes, which means that 16 licenses are required. No licensing is required for VTL or NAS emulations. VTL and NAS replication requires a license (per couplet) on the target system. StoreOnce Catalyst devices require a license for backup and for copy, so licenses must be installed on both origin and destination systems. A StoreOnce Catalyst license, if necessary, must be installed on Preparing for installation 27

28 every couplet in the cluster. Without a StoreOnce Catalyst license for each couplet, the StoreOnce Catalyst feature is reported as unlicensed for the entire StoreOnce System. Security features (Data at Rest Encryption, Data in Flight Encryption, and Secure Erase) require a Security license. A Security license, if necessary, must be installed on every couplet in the cluster. If you do not add a Security license for each couplet, the Security feature is reported as unlicensed for the entire StoreOnce System. IMPORTANT: Data in flight encryption is intended to be used to secure links between data centers for StoreOnce Replication or Low-Bandwidth Catalyst Copy operations. Using Data In Flight Encryption for direct backup operations to the StoreOnce appliance over a local network is not supported due to the performance impact of the encryption. User roles and accounts Two roles define the permissions associated with a user; admin and user. Two default user accounts, one for each role, are created automatically when the system is installed. Administrator: Admin users can create and edit management and StoreOnce functions via the GUI and CLI. The default login and password are Admin and admin. The permissions role of the Administrator is admin. Operator: This account limits access to the GUI and CLI to monitoring and viewing. The default login and password are Operator and operator. The permissions role of the Operator is user. It is good practice to determine what other users will be required and what access to the system they require as part of the planning process. In particular, will the StoreOnce System be added to an Active Directory Domain? The following AD domain details will be required to configure AD. The AD domain name The user name and password of the Domain Administrator or a delegated user with Domain Administrative rights The type of network used by the domain server, IPv4 or IPv6 Once the StoreOnce System has been joined to an AD domain, you can configure external users or external groups on the StoreOnce System. The users or groups must exist on the AD domain. You can add AD domain users or groups with access to all StoreOnce features or you can add them as Local Administrators for the CIFS server only. Only the name is required to configure AD users or groups on the StoreOnce System; passwords are configured on the AD domain server. 28 User roles and accounts