HP StoreEasy 3000 Storage Administrator Guide

(1)

HP StoreEasy 3000 Storage Administrator

Guide

This document describes how to install, configure, and maintain all models of HP StoreEasy 3000 Storage and is intended for system administrators. For the latest version of this guide, go tohttp://www.hp.com/support/StoreEasy3000Manuals.

HP Part Number: B7D88-96385 Published: June 2015

Edition: 1

(2)

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, 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.

The information contained herein is subject to change without notice. The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein.

Links to third-party websites take you outside the HP website. HP has no control over and is not responsible for information outside HP.com.

Acknowledgments

Microsoft® and Windows® are trademarks of the Microsoft group of companies.

Java™ is a US trademark of Sun Microsystems, Inc.

UNIX® is a registered trademark of The Open Group.

Warranty

WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website:

http://www.hp.com/go/storagewarranty

(3)

1 HP StoreEasy 3000 Storage...8

Features...8

Hardware components...8

HP StoreEasy 3850 Gateway Storage hardware components...8

HP StoreEasy 3850 Gateway Blade Storage hardware components...11

Drive LED definitions...13

Systems Insight Display LED combinations...14

Software components...14

2 Installing the storage system...16

Setup overview...16

Default roles...16

Verify the kit contents...18

Locate the serial number, Certificate of Authenticity, and End User License Agreement...18

Install the storage system hardware...19

Validate network information...19

Connect to the storage system...20

Power on the server and log on...21

3 Configuring the storage system...22

System Settings...22

Networking...23

Storage Management...24

Register SMI-S provider...24

Register SMI-S provider (standalone profile)...24

Multi-Path IO configuration...24

Notifications...25

Storage Configuration...25

Create Storage Pools...25

Create Volumes...25

Protect This Server...25

Complete system configuration...26

Cluster Configuration...27

Provisioning cluster shared storage...27

Adding a node to an existing cluster...28

Heartbeat Network...29

Shared Storage...30

Cluster Creation...31

Protect This Cluster...37

Cluster-Aware Updating...38

Free Autonomy LiveVault 30–day trial...39

Vision Solution Double-Take Availability Information...39

Using server core...39

Additional access methods...40

Using the Remote Desktop method...40

Using the Telnet method...40

4 Managing the storage system...41

Using the Network Configuration Tool...41

Network Interfaces...42

Network Team Configuration...43

Network VLAN Configuration...44

Network Interface IP Configuration...44

Contents 3

(4)

Network Configuration Summary...45

Network Validation...45

Managing the network configuration file...45

Importing network configuration...47

Using the HP System Dashboard...48

Viewing the dashboard overview...49

Viewing event details...51

Viewing storage details...52

Viewing network details...55

Viewing system details...58

Managing the dashboard configuration file...60

HP Notification System...62

5 Administration tools...63

Microsoft Windows Storage Server 2012 R2 administration tools...63

Remote Administration...63

File and Storage Services...63

Data Deduplication...63

Print Management...64

Network File System User Mapping...64

6 Storage management overview...66

Storage management elements...66

Storage management example...66

Physical storage elements...67

Arrays...68

Fault tolerance...68

Online spares...69

Logical storage elements...69

Logical drives (LUNs)...69

Partitions...70

Volumes...70

File system elements...70

File sharing elements...71

Volume Shadow Copy Service overview...71

Using storage elements...71

Clustered server elements...71

Network adapter teaming...71

Management tools...72

HP Systems Insight Manager...72

Management Agents...72

7 File server management...73

File services management...73

Storage management utilities...73

Array management utilities...73

Smart Storage Administrator...73

Disk Management utility...74

Guidelines for managing disks and volumes...74

Scheduling defragmentation...75

Disk quotas...75

Adding storage...76

Expanding storage...76

Extending storage using Windows Storage Utilities...76

Extend volumes using Disk Management...76

Expanding storage for EVA arrays using HP P6000 Command View...77

4 Contents

(5)

Expanding storage using the Array Configuration Utility...77

Expand logical drive...77

Volume shadow copies...77

Shadow copy planning...78

Identifying the volume...78

Allocating disk space...78

Identifying the storage area...79

Determining creation frequency...79

Shadow copies and drive defragmentation...79

Mounted drives...79

Managing shadow copies...80

The shadow copy cache file...80

Enabling and creating shadow copies...82

Viewing a list of shadow copies...82

Set schedules...82

Viewing shadow copy properties...82

Redirecting shadow copies to an alternate volume...82

Disabling shadow copies...83

Managing shadow copies from the storage system desktop...83

Shadow Copies for Shared Folders...84

SMB shadow copies...85

NFS shadow copies...86

Recovery of files or folders...86

Recovering a deleted file or folder...86

Recovering an overwritten or corrupted file...87

Recovering a folder...87

Backup and shadow copies...87

Shadow Copy Transport...87

Folder and share management...88

Folder management...88

Share management...94

Share considerations...94

Defining Access Control Lists...94

Integrating local file system security into Windows domain environments...94

Comparing administrative (hidden) and standard shares...95

Managing shares...95

File Server Resource Manager...95

Quota management...96

File screening management...96

Storage reports...96

8 Cluster administration...97

Cluster overview...97

Cluster terms and components...98

Nodes...98

Resources...98

Cluster groups...98

Virtual servers...98

Failover and failback...98

Quorum disk...99

Cluster concepts...99

Sequence of events for cluster resources...100

Hierarchy of cluster resource components...100

Cluster planning...101

Storage planning...101

Contents 5

(6)

Network planning...102

Protocol planning...102

Preparing for cluster installation...103

Before beginning installation...103

Using multipath data paths for high availability...103

Checklists for cluster server installation...103

Network requirements...103

Shared disk requirements...104

Cluster installation...104

Setting up networks...105

Configuring the private network adapter...105

Configuring the public network adapter...105

Renaming the local area connection icons...105

Verifying connectivity and name resolution...105

Verifying domain membership...105

Setting up a cluster account...105

About the Quorum disk...105

Configuring shared disks...106

Verifying disk access and functionality...106

Configuring cluster service software...106

Using Failover Cluster Management...106

Creating a cluster...106

Adding nodes to a cluster...106

Geographically dispersed clusters...106

Cluster groups and resources, including file shares...107

Cluster group overview...107

Node-based cluster groups...107

Load balancing...107

File share resource planning issues...108

Resource planning...108

Permissions and access rights on share resources...108

NFS cluster-specific issues...108

Non cluster aware file sharing protocols...109

Adding new storage to a cluster...109

Creating physical disk resources...109

Creating file share resources...110

Creating NFS share resources...110

Shadow copies in a cluster...110

Extend a LUN in a cluster...110

MSNFS administration on a server cluster...111

Best practices for running Server for NFS in a server cluster...111

Print services in a cluster...111

Creating a cluster printer spooler...111

Advanced cluster administration procedures...112

Failing over and failing back...112

Restarting one cluster node...112

Shutting down one cluster node...113

Powering down the cluster...113

Powering up the cluster...113

9 Troubleshooting, servicing, and maintenance...114

Maintaining your storage system...114

Determining the current storage system software version...115

HP System Management Homepage...115

Starting the System Management Homepage application...115

6 Contents

(7)

System Management Homepage main page...116

Certificate of Authenticity...118

HP System Dashboard...118

Known issues...120

Error codes...124

HP Insight Management CSP WBEM Providers for Windows error codes...124

HP Support websites...125

Autonomy LiveVault...126

Microsoft Systems Center Operations Manager...126

Removing and replacing hardware components...126

10 Storage system recovery...127

System Recovery DVD...127

Using the System Recovery DVD to save system data...127

Drive letters are not assigned after a restore...128

Restoring the factory image with a DVD or USB flash device...128

Using a USB flash drive for storage system recovery...129

Recovering both servers...129

Recovering a single server...129

Backing up and restoring the system with Windows Recovery Environment...131

11 HP Product Feedback...134

12 Iternity iCAS...135

13 Support and other resources...136

Contacting HP...136

HP technical support...136

Subscription service...136

Related information...136

HP websites...136

Rack stability...137

Customer self repair...137

14 Documentation feedback...138

A Operating system logical drives...139

B Network ports...140

C Regulatory information...147

Belarus Kazakhstan Russia marking...147

Turkey RoHS material content declaration...147

Ukraine RoHS material content declaration...147

Warranty information...147

Glossary...149

Index...151

Contents 7

(8)

1 HP StoreEasy 3000 Storage

The HP StoreEasy 3000 Storage products enable simplified file and application storage. These products reduce your cost of ownership by simplifying management, increasing resource utilization, centralizing growth, and protecting data.

Features

The HP StoreEasy 3000 Storage provides the following advantages:

• Efficiently maximizing resources through file and data management without increasing costs.

• HP and Microsoft management integration, including Microsoft Server Manager and System Center and HP Systems Insight Manager and iLO (Integrated Lights Out).

• Each system ships from the factory with preintegrated hardware and preloaded software, to significantly reduce the time and complexity of installation.

For more information about HP StoreEasy 3000 Storage features, go to:

http://www.hp.com/go/StoreEasy3000

Hardware components

This section provides illustrations of the storage system hardware components.

HP StoreEasy 3850 Gateway Storage hardware components

The following figures show components and LEDs located on the front and rear panels of the HP StoreEasy 3850 Gateway Storage.

The chassis configuration for the HP StoreEasy 3850 Storage system includes two 2u-nodes (XL190r) installed in an r2600 chassis. The node numbering in the chassis when using 2u XL190r servers are enumerated as node 1 and node 3 in the r2600 chassis.

Figure 1 HP StoreEasy 3850 Gateway Storage front panel components

2. Operating system disk for node 1 1. Left bezel ear

4. Right bezel ear 3. Operating system disk for node 3

5. Chassis serial label pull tab

8 HP StoreEasy 3000 Storage

(9)

Figure 2 HP StoreEasy 3850 Gateway Storage front panel LEDs and buttons

Status Description

Item

Solid green = System on Power On/Standby button

and system power LED (Node 1)*

1

Flashing green = Performing power on sequence Solid amber = System in standby

Off = No power present**

2

Solid green = Normal Health LED (Node 2)*

3

Flashing amber = System degraded Flashing red = System critical***

4

5

6

7

Solid blue = Activated UID button/LED*

8

Flashing blue:

• 1 Hz/cycle per sec = Remote management or firmware upgrade in progress

• 4 Hz/cycle per sec = iLO manual soft reboot sequence initiated

• 8 Hz/cycle per sec = iLO manual hard reboot sequence in progress

Hardware components 9

(10)

Status Description

Item

Off = Deactivated Solid green = System on Power On/Standby button

9

* When the LEDs described in this table flash simultaneously, a power fault has occurred.

** Facility power is not present, power cord is not attached, no power supplies are installed, power supply failure has occurred, or the front I/O cable is disconnected.

*** If the health LED indicates a degraded or critical state, review the system IML or use iLO to review the system health status.

NOTE: The LEDs of Node 1 and Node 2 are not enabled because the r2600 chassis contains only two 2U nodes.

Figure 3 HP StoreEasy 3850 Gateway Storage rear panel components

2. RCM module 1. Node 3

4. Power supply 1 3. Power supply 2

5. Node 1

Figure 4 HP StoreEasy 3850 Gateway Storage rear panel LEDs

Status Description

Item

Solid green = Normal Power supply 2 LED

1

Off = One or more of the following conditions exist:

• Power is unavailable

• Power supply has failed

(11)

Status Description

Item

• Power supply is in standby mode

• Power supply error Solid green = Normal Power supply 1 LED

2

Off = One or more of the following conditions exist:

• Power is unavailable

• Power supply has failed

• Power supply is in standby mode

• Power supply error

Figure 5 2U node rear panel components

Description Item

Node serial number and iLO label pull tab 1

SUV connector 2

USB 3.0 connector 3

Dedicated iLO port (optional) 4

NIC connector 1 5

NIC connector 2 6

HP StoreEasy 3850 Gateway Blade Storage hardware components

The following figures show components and LEDs located on the front and rear panels of the HP StoreEasy 3850 Gateway Blade Storage.

(12)

Figure 6 HP StoreEasy 3850 Gateway Blade Storage front panel components

2. Server blade release button 1. Hard drive bay 1

4. Hard drive bay 2 3. Server blade release lever

6. Serial label pull tab 5. HP c-Class Blade SUV connector (behind the serial label

pull tab)

Figure 7 HP StoreEasy 3850 Gateway Blade Storage front panel LEDs and buttons

Status Description

Item

Solid Green = Normal (System is powered on) Health status LED bar

1

Flashing Green = Power On/Standby Button service is being initialized

Flashing Amber = Degraded condition Flashing Red = Critical condition Off = Normal (System is in standby) Solid Green = System is powered on.

System power LED 2

Flashing Green = System is waiting to power on; Power On/Standby button is pressed.

Solid Amber = System is in standby; Power On/Standby Button service is initialized.

Off and the Health Status LED bar is off = The system has no power.

Off and the Health Status LED bar is flashing green = The Power On/Standby Button service is being initialized.

Solid Blue = Identified UID LED

3

Flashing Blue = Active remote management Off = No active remote management Green = Network linked

FlexibleLOM LED 4

(13)

Status Description

Item

Flashing Green = Network activity Off = No link or activity

NOTE: For more troubleshooting steps, refer to the platform hardware information. The following list identifies the ProLiant model for each HP StoreEasy 3000 Storage:

• 3850 Gateway Storage—HP Apollo r2600 24SFF CTO Chassis with HP ProLiant XL190r Gen9 CTO Server

• 3850 Gateway Blade Storage—HP ProLiant BL460c Gen9 Server Blade The ProLiant documentation is available at:

http://www.hp.com/go/proliantgen9/docs

Drive LED definitions

The following figure shows the drive LEDs. These LEDs are located on all HP ProLiant hot plug hard drives.

Figure 8 Drive LEDs

Definition Status

LED Item

The drive is being identified by a host application.

Solid blue Locate

1

The drive carrier firmware is being updated or requires an update.

Flashing blue

Drive activity Rotating green

Activity ring 2

No drive activity Off

Do not remove the drive. Removing the drive causes one or more of the logical drives to fail.

Solid white Do not remove

3

Removing the drive does not cause a logical drive to fail.

Off

The drive is a member of one or more logical drives.

Solid green Drive status

4

The drive is rebuilding or performing a RAID migration, stripe size migration, capacity expansion, or logical drive extension, or is erasing.

Flashing green

The drive is a member of one or more logical drives and predicts the drive will fail.

Flashing amber/green

The drive is not configured and predicts the drive will fail.

Flashing amber

The drive has failed.

Solid amber

The drive is not configured by a RAID controller.

Off

(14)

Systems Insight Display LED combinations

When the health LED on the front panel illuminates either amber or red, the server is experiencing a health event. Combinations of illuminated Systems Insight Display LEDs, the system power LED, and the health LED indicate system status.

Table 1 Systems Insight Display LEDs and internal health LED combinations

Status System power LED Health LED

Systems Insight Display LED and color

One or more of the following conditions might exist:

Amber Red

Processor (amber)

• Processor in socket X has failed.

• Processor X is not installed in the socket.

• Processor X is unsupported.

• ROM detects a failed processor during POST.

Processor in socket X is in a pre-failure condition.

Green Amber

One or more DIMMs have failed.

Green Red

DIMM (amber)

DIMM in slot X is in a pre-failure condition.

Green Amber

The Health Driver has detected a cautionary temperature level.

Green Amber

Over temp (amber)

The server has detected a hardware critical temperature level.

Amber Red

The PCI riser cage is not seated properly.

Green Red

PCI riser (amber)

One fan has failed or is removed.

Green Amber

Fan (amber)

Two or more fans have failed or are removed.

Green Red

One or more of the following conditions may exist:

Amber Red

Power supply

(amber) • Only one power supply is installed and that power

supply is in standby.

• Power supply fault

• System board fault

One or more of the following conditions may exist:

Green Amber

• Redundant power supply is installed and only one power supply is functional.

• AC power cord is not plugged into redundant power supply.

• Redundant power supply fault

• Power supply mismatch at POST or power supply mismatch through hot-plug addition

Standby Amber

— Power cap (off)

Waiting for power Flashing green

— Power cap (green)

Power is available.

Green

—

Software components

Windows Storage Server 2012 R2 Standard Edition comes preinstalled and activated on the HP StoreEasy 3830 Storage. Windows Storage Server 2012 R2 Standard Edition comes preinstalled and activated on HP StoreEasy 3850 Storage. The storage system configuration also includes the

(15)

HP Initial Configuration Tasks window, Windows Server Manager, and HP StoreEasy tools, which are used to set up and manage your storage system.

NOTE: Windows Storage Server 2012 R2 Standard Edition is installed in the Server with a GUI mode by default. You can switch to Server Core Installation mode. However, the Server Core Installation mode is only supported on an HP StoreEasy Storage system when the operating environment does not require user interaction (such as in a data center). Any activity that requires the use of a GUI must be done in the Server with a GUI mode. For more information about installation options, see the Windows Server Installation Options article on Microsoft TechNet at:

http://technet.microsoft.com/library/hh831786.aspx

To switch to Server Core mode, see“Using server core” (page 39)for more information.

The Windows Server Manager→Tools→HP StoreEasy menu provides a collection of HP and Microsoft utilities that are useful for managing the storage system. The Initial Configuration Tasks window assists during the initial out of box setup by configuring items, such as system settings, setting the network IP and domain of the HP StoreEasy Storage system, configuring email alerts, registering product, provisioning storage, and protecting your server. For more information on the ICT tasks, see“Configuring the storage system” (page 22). Using Windows Server Manager→File and Storage Services, you can also create virtual disks and place volumes on the virtual disks.

Software components 15

(16)

2 Installing the storage system

Setup overview

The HP StoreEasy 3850 Storage comes preinstalled with the Microsoft Windows Storage Server 2012 R2 Standard Edition operating system with Microsoft iSCSI Software Target and a Microsoft Cluster Service (MSCS) license included.

Default roles

This section includes the list of roles that come preinstalled with HP StoreEasy 3850 Storage.

Table 2 (page 17) describes the default roles:

16 Installing the storage system

(17)

Table 2 Default roles

Role service Role

File and Storage Services • File and iSCSI Services

File Server

◦

Branch Cache for Network Files

◦

Data Deduplication

◦

DFS Replication

◦

File Server Resource Manager

◦

File Server VSS Agent Service

◦

iSCSI Target Server

◦

iSCSI Target Storage Provider (VDS and VSS hardware providers)

◦

Server for NFS

◦

Work Folders

• Storage Services

Print and Document Services • Print Server

• Internet Printing

• LPD Service

Web Server (IIS) • Web Server

Common HTTP Features

◦

– Default Document – Directory Browsing – HTTP Errors Static Content – HTTP Redirection

◦

Health and Diagnostics HTTP Logging –

– Logging Tools – Request Monitor – Tracing

◦

Performance

– Static Content Compression

◦

^Security

Request Filtering –

– Basic Authentication – Windows Authentication

◦

Application Development

nl

– .NET Extensibility 4.5 – ASP

– ASP.NET 4.5

Setup overview 17

(18)

Table 2 Default roles (continued)

Role service Role

ISAPI Extensions –

– ISAPI Filters

• Management Tools

◦

IIS Management Console

◦

IIS 6 Management Compatibility – IIS 6 Metabase Compatibility

Verify the kit contents

Remove the contents, ensuring that you have all of the following components. If components are missing, contact HP technical support.

Hardware

• HP StoreEasy 3000 Storage system (with operating system preloaded)

• Power cords

• Rail kit

Media and documentation

• HP StoreEasy 3850 Gateway Storage Quick Start Guide or HP StoreEasy 3850 Gateway Blade Storage Quick Start Guide (depending on your product)

• Safety and Disposal Documentation CD

• HP System Recovery DVD

• End User License Agreement

• Certificate of Authenticity Card

• HP ProLiant Essentials Integrated Lights-Out Advanced Pack

Locate the serial number, Certificate of Authenticity, and End User License

Agreement

For technical support purposes, locate the storage system's serial number, COA (Certificate of Authenticity), and EULA (End User License Agreement). Record the serial number and COA product key and make a print copy of the EULA as needed.

The storage system's serial number is located in several places:

• Top of the storage system or blade

• Back of the storage system

• Inside the storage system shipping box

• Outside of the storage system shipping box

The storage system's COA card is located inside the storage system shipping box. There is also a COA sticker with product key affixed to the top of the storage system or blade. The electronic copy of the EULA installed with the storage system is available at %SystemDrive%\Windows\

System32\license.rtf.

(19)

Install the storage system hardware

If your storage system is fully racked and cabled, go to“Connect to the storage system” (page 20).

For 3850 Gateway Storage systems, install the rail kit and insert and secure the storage system into the rack by following the HP Rack Rail Kit Installation Instructions.

For 3850 Gateway Blade Storage systems, install the server blade by following the procedures documented in the Quick Start Guide provided for your model.

Validate network information

Complete the tests inTable 3 (page 19) orTable 4 (page 20), depending on your configuration, to verify network connectivity. Consult with your network administrator to confirm test results.

Table 3 Validation tests (clustered system)

Successful? (Y/N) Command(s) to execute

Test

ping <node 2 address>

Ping the IP address of Node 2 from Node 1.

ping <node 2 name>

ping <node 2 fqdn>

Ping the name of Node 2 from Node 1.

ping <node 1 address>

Ping the IP address of Node 1 from Node 2.

ping <node 1 name>

ping <node 1 fqdn>

Ping the name of Node 1 from Node 2.

nslookup <node 1 address>

nslookup <node 1 name>

Verify forward and reverse DNS information for Node 1 is correct.

nslookup <node 1 fqdn>

nslookup <node 2 address>

nslookup <node 2 name>

Verify forward and reverse DNS information for Node 2 is correct.

nslookup <node 2 fqdn>

ping <domain controller address>

ping <domain controller name>

Ping the domain controller from Node 1.

ping <domain controller fqdn>

Ping the domain controller from Node 2.

ping <domain controller fqdn>

pathping <domain controller address>

pathping <domain controller name>

Verify the network path to the domain controller and DNS servers is correct.

pathping <DNS server address>(repeat for each DNS server)

pathping <DNS server name>(repeat for each DNS server)

Install the storage system hardware 19

(20)

Table 4 Validation tests (standalone system)

Successful? (Y/N) Command(s) to execute

Test

ping <system address>

Ping the IP address of the StoreEasy system from another system on the same network.

ping <system address>

Ping the IP address of some other system on the same network form the StoreEasy system.

ping <node 1 name>

ping <node 1 fqdn>

Ping the name of the StoreEasy system from another system on the same network.

ping <node 1 name>

ping <node 1 fqdn>

Ping the name of some other system on the same network form the StoreEasy system.

If you will be adding the StoreEasy system to an Active Directory domain, some additional tests include:

Ping the domain controller from the StoreEasy system.

pathping <domain controller address>

pathping <domain controller name>

Verify the network path to the domain controller and DNS servers is correct.

pathping <DNS server address>(Repeat for each DNS server)

pathping <DNS server name>(Repeat for each DNS server)

Additionally, verify that the DNS information is valid for the cluster and file server. HP recommends that you also verify the iLO IP address and name resolution; however, this is not critical to support the cluster and file server.

Connect to the storage system

Use either the direct attach or iLO method to connect to the storage system.

IMPORTANT: Only the direct attach and iLO access methods can be used to install the storage system. After the storage system installation process is complete and the server’s IP addresses have been assigned, you can then additionally use the remote desktop method to access the storage system.

• Direct attach—This access method is mandatory if your network does not have a DHCP (Dynamic Host Configuration Protocol) server. Connect the following cables to the back panel of the storage system in this sequence: keyboard, mouse, network cables, monitor cable, and power cable.

NOTE: The keyboard, mouse, and monitor are not provided with the storage system.

• iLO—Access the storage system using the iLO remote management method:

1. Connect a network cable to the iLO port located on the back of the storage system.

2. Connect a power cable to the storage system.

3. Locate the iLO Network Settings tag attached to the storage system and record the default user name, password, and DNS name.

4. From a remote computer, open a standard Web browser and enter the iLO management hostname of the storage system.

(21)

NOTE: By default, iLO obtains the management IP address and subnet mask from your network’s DHCP server. The hostname found on the iLO tag is automatically registered with your network’s DNS server. If the DHCP configuration is not possible or the system is not found in DNS, use the direct attach method to configure iLO with a static IP address.

5. Using the default user information provided on the iLO Network Settings tag, log on to iLO, and then launch a remote console to the storage system.

For detailed instructions on using iLO remote management software, see the HP iLO 4 User Guide, which you can search for (by product name) athttp://www.hp.com/support/

manuals.

Power on the server and log on

1. Power on the system by pushing the power button on the front panel. If using iLO, click Momentary Press under the Power Switch menu of the remote console.

IMPORTANT: If you are deploying a cluster, only interact with one of the servers. After powering on both servers, the Setup Windows Wizard and the Initial Configuration Tasks must be run from only one server.

The storage system starts and displays the Setup Windows wizard, in which you select language and regional settings and accept the license agreement.

2. After completing the wizard, you are asked if you want to configure a standalone system or a two-node cluster. Click Yes to configure your system as a cluster or click No to configure your system as a standalone server. The storage system installation process takes approximately 10–15 minutes.

3. After installation completes and the server (or servers if deploying a cluster) reboots, you are automatically logged on as the local administrator (using the default Windows Administrator password of HPinvent!). If you are deploying a cluster, continue to work only with the server on which you used the Setup Windows Wizard.

Power on the server and log on 21

(22)

3 Configuring the storage system

The HP ICT (Initial Configuration Tasks) window launches automatically at logon for any user who is a member of the local administrators group. Use ICT to perform the following tasks:

• Update system settings, such as changing the local administrator password, time zone, save reseller information, and so on.

• Launch Network Configuration wizard to configure and validate the network configuration.

• Configure email alerts and register product.

• Enable software updates and enhancements directly from Windows update.

• Register for a free trial of Autonomy LiveVault and get more information on Vision Solution Double-Take Availability Information products.

You can open only one instance of the ICT at a time. If you do not want to open the ICT window every time you logon, select the Do not show this window at the next logon check box in the window. You can also launch ICT by opening a command prompt and typing

C:\Windows\System32\OEMOOBE\OEMOOBE.EXE. The following tasks are included in the ICT:

• System Settings

• Networking

• Notifications

• Storage Configuration

• Protect This Server

NOTE: Microsoft Storage Spaces are not supported on HP StoreEasy 3000 Storage.

System Settings

This task group enables you to configure the system settings. The following tasks are included in this group:

• Set local administrator password—Enables you to change the administrator user password.

The default password is the password that you entered during the initial setup of the server.

To change the password, enter the new password in the New password and Confirm password fields and click OK.

IMPORTANT: HP cannot assist with lost passwords.

• Set time zone—Enables you to change the date and time settings. You can change the time zone, date and time, and synchronize the date and time with an Internet time server.

• Enable Windows error reporting—Enables you to send the description of problems on your server to Microsoft and look for steps you can take to resolve them. Select the desired setting and click OK.

• Enable customer experience improvement program—Enables you to participate in the customer experience program. Microsoft Corporation collects statistical information about your system configuration, performance of some components of Windows, and certain types of events.

Windows periodically uploads a small file to Microsoft that contains a summary of the information collected. Select the desired setting and click OK.

• Save reseller information—Enables you to enter details of the reseller from whom you purchased the system and purchasing details for future reference. The asset serial number is added by

22 Configuring the storage system

(23)

default and you cannot change it. Enter the details in the respective fields and click OK to save the information.

You can also access the Reseller Information Tool using the following methods:

◦

Open Server Manager and click Tools→HP StoreEasy→Save Reseller information.

◦

Double-click the System Tools folder on the desktop and select Save Reseller Information.

The reseller information is also available on the Hardware tab in the HP System Dashboard.

Networking

This task group enables you to set the network IP and domain of HP StoreEasy 3000 Storage. The following tasks are included in this group:

• Configure networking—Enables you to configure the network interfaces using the HP NCT (Network Configuration Tool) wizard. For detailed information on NCT, see“Using the Network Configuration Tool” (page 41).

• Provide computer name and domain—Enables you to specify the computer name and domain.

Windows Storage Server 2012 R2 is installed with a randomly generated computer name.

You may find the server easier to access remotely and easier to recognize in reports and logs if you assign it a name that is meaningful to you and that fits with the naming scheme for computers in your organization.

Consider the following when assigning a computer name:

◦

The recommended length for most languages is 15 characters or fewer. For languages that require more storage space per character, such as Chinese, Japanese, and Korean, the recommended length is 7 characters or fewer.

◦

HP recommends that you use only Internet-standard characters in the computer name.

Standard characters are the numbers from 0 through 9, uppercase and lowercase letters from A through Z, and the hyphen (-) character. Computer names cannot consist entirely of numbers.

◦

If you are using DNS on the network, you can use a wider variety of characters. These include Unicode characters and other non-standard characters, such as the ampersand (&). Using nonstandard characters may affect the ability of non-Microsoft software to operate on the network.

◦

The maximum length for a computer name is 63 bytes. If the name is longer than 15 bytes (15 characters in most languages, 7 characters in some), computers that are running Windows NT 4.0 and earlier will recognize this computer by the first 15 bytes of the name only. In addition, there are additional configuration steps for a name that is longer than 15 bytes.

◦

If a computer is a member of a domain, you must choose a computer name that differs from any other computer in the domain. To avoid name conflicts, the computer name should be unique on the domain, workgroup, or network.

In a Windows Active Directory Domain, passwords and permissions for computer objects and user accounts are easier to manage due to being stored in a centralized database that is replicated among the domain controllers.

To name the computer and join it to a domain, click Provide computer name and domain in the HP Initial Configuration Tasks window and then click Change on the Computer Name tab.

Networking 23

(24)

Storage Management

You can use the following options to register for SMI-S provider and check the MPIO configuration:

• Register SMI-S provider

• Multi-Path IO configuration

Register SMI-S provider

If no provider is registered, register the SMI-S provider using the registration tool. When prompted, enter the IP address of the array and registration credentials. A secure (HTTPS) connection is used to connect to port 5989 on the array. An HTTP connection is used to connect to port 5988 on the array. If a different protocol is required or a different port is configured on the array, you must perform the SMI-S registration at an elevated PowerShell command prompt. For more details, refer to the storage array documentation. Registering the SMI-S provider through ICT automatically updates the operating system storage provider cache. This operation might take several minutes.

You can update the cache manually by invoking the Update-StorageProviderCache –DiscoveryLevel FullPowerShell commandlet at an elevated PowerShell prompt.

After registering the provider or if a provider is already registered on the system, Other provider registered is displayed in the ICT window.

Register SMI-S provider (standalone profile)

SMI-S is a storage standard that enables management of the heterogeneous storage vendor systems.

You can configure a StoreEasy system as SMI-S Client to manage your SAN disk arrays. The File and Storage Services option in Windows Server Manager can take advantage of SMI-S providers, providing a GUI interface for managing the basic array functionality.

To register SMI-S provider on HP StoreEasy 3000 Storage:

1. Open an elevated PowerShell command prompt.

2. Enter the following commands for HTTP and HTTPs SMI-S provider:

1. Register-SmisProvider -ConnectionUri http://<ipaddress of the storage array>:<port-no>.

NOTE: For HTTPs port SMI-S provider, enter Register-SmisProvider

-ConnectionUri https://<ipadress of the storage array>:<port-no>. 2. Update-StorageProviderCache -DiscoveryLevel 3 -PassThru.

3. Enter Get-StorageProvider to verify the registration of SMI-S provider.

If the registration is successful, SMI-S provider is displayed as registered on the system.

Multi-Path IO configuration

MPIO configuration is automatic if a virtual volume is exported to the File Controller and the volume is exported over multiple paths to the same File Controller. The state of the configuration is displayed in the ICT window. You can open the MPIO properties applet at an elevated PowerShell or

Command prompt by entering the mpiocpl command. You must have a volume (LUN) presented to the gateway before you can claim it using the MPIO properties applet. Using Control Panel, select the DSM that matches your storage array. A DSM is required by your storage vendor. When complete, a message is displayed indicating that system reboot is needed. Do not reboot the system at this point. Open the applet at an elevated PowerShell or command prompt by entering mpiocpl.

NOTE: MPIO settings are available in ICT for Cluster 3000. These settings are not available in the standalone 3000 system.

(25)

Notifications

This task group enables you to configure e-mail alerts and register for proactive notifications. The following tasks are included in this group:

• Configure email alerts—Enables you to configure the email accounts that should receive alerts when significant events occur. Using the Event Notifier Configuration wizard, you can add SMTP server IP addresses and send a sample email to check if the email alerts have been configured properly. You can also access the Event Notifier Configuration wizard directly using the following methods:

◦

Open Server Manager and select Tools→HP StoreEasy→Configure e-mail alerts.

◦

Double-click the System Tools folder on the desktop and select Configure Email Alerts.

◦

Click Event Notifier Config on the Start screen.

• Register Product—Opens a web browser to the HP product registration page. HP strongly recommends registering your system so that you can receive proactive notifications of system updates, critical issues, and announcements of feature updates. If your system is connected to a network that can access the Internet, you can perform the product registration from any other system. You can also access the Register Product link using the following methods:

◦

Double-click the Register Product icon on the desktop.

◦

Click Register Product on the Start screen.

◦

Open Server Manager and select Tools→HP StoreEasy→Register Product.

Storage Configuration

Storage provisioning tasks are performed in this group.

NOTE: Prior to configuring the storage pools, both MPIO and SMI-S registration configurations must be completed as per the storage devices installation and configuration guides.

Create Storage Pools

For more information on connecting and presenting storage volumes to the gateway, see the documentation for the storage subsystem connected to the gateway. After the volumes (LUNs) are created on the storage system, you must update the storage provider cache. To update the storage provider cache, invoke Update-StorageProviderCache –DiscoveryLevel Full from an elevated PowerShell command prompt.

Create Volumes

A new volume requires that a new virtual disk be created also. Click on the Create Volumes link to start the New Virtual Disk wizard. Create the virtual disk in an existing storage pool. The New Volume Wizard is started by default when you complete the new Virtual Disk Wizard. Create a new volume in the virtual disk that you just created.

Protect This Server

This task group enables you to check that your server receives critical software updates and enhancements directly from the Microsoft website. The following tasks are included in this group:

• Enable automatic updating—Opens the Windows Update dialog box that you can use to select the way Windows updates are downloaded and installed. HP recommends that you do not select automatic updates to avoid unexpected system restarts after updates are applied. The Windows Update feature simplifies the task of updating the operating system, and saves

Notifications 25

(26)

administrator’s time. Features on the Windows Update dialog box are configurable by members of the administrators group on the local computer.

HP recommends the following for updates:

◦

Under Important updates, select one of the following options:

Download updates but let me choose whether to install them (default option) –

– Check for updates but let me choose whether to download and install them

◦

Under Recommended updates, select Give me recommended updates the same way I receive important updates.

◦

Run Download and Install Updates immediately after system installation.

◦

Subscribe to HP customer advisories using Subscriber's choice for business. For more information, seeSubscription service. Ensure to check if firmware and related device drivers are up-to-date based upon information for your system at the HP Support & Drivers website.

◦

Apply regular HP StoreEasy Storage Service Releases.

• Free Autonomy LiveVault 30–day trial—Begins the registration process for a free 30-day trial of the Autonomy LiveVault cloud based backup system. If your system is not connected to the Internet, you can signup by visitingLiveVault. You can also access the Free Autonomy LiveVault 30–day trial link using the following methods:

◦

Double-click the Free LiveVault 30-day Trial icon on the desktop.

◦

Click Free LiveVault 30-day Trial on the Start screen.

• Vision Solution Double-Take Availability Information—Opens an HTML page that displays details about installing the trail version of the Double-Take Availability software. The trial version provides you an opportunity to evaluate the software in your environment. You can also access the HTML page directly by double-clicking the Vision Solution Double-Take Availability Information icon on the desktop.

Complete system configuration

IMPORTANT: HP recommends that you validate your configuration when using clusters. Whether you create a cluster through the ICT or the Failover Cluster Manager, one of the first steps is validating your configuration using the Microsoft cluster validation tool. If you choose to skip the validation step, you can still validate the cluster after it is created.

After the storage system is physically set up and you have completed all of the required tasks in the Initial Configuration Tasks window, you may want to complete additional setup tasks. Depending on the deployment scenario of the storage system, these steps can vary. These additional steps can include:

• Running Microsoft Windows Update—HP highly recommends that you run Microsoft Windows updates to identify, review, and install the latest, applicable, critical security updates on the storage system.

• Creating and managing users and groups—User and group information and permissions determine whether a user can access files. If the storage system is deployed into a workgroup environment, this user and group information is stored locally on the device. By contrast, if the storage system is deployed into a domain environment, user and group information is stored on the domain.

• Configuring event notification.

(27)

• Adjusting logging for system, application, and security events.

• Installing third-party software applications—For example, these might include an antivirus application that you install.

• Registering the server—To register the server, see the HP registration website (http://

register.hp.com).

Cluster Configuration

After you have completed the physical installation of the HP StoreEasy 3000 Storage and before you deploy the new system in your enterprise, you must determine the type of cluster configuration that is desired. The HP StoreEasy 3000 Storage systems can be configured in a failover cluster configuration. This section describes the steps required to configure a single-node cluster or a two-node failover cluster.

NOTE:

• When creating a two-node cluster, ensure that all nodes have the same hardware configuration.

• SMI-S Provisioning must be configured to your external storage arrays. For more information, seeStorage Management.

• The ICT is intended for initial setup, so once it is complete, you can select the Do not show this window at the next logon check box at the bottom of the window. If you want to launch the ICT at a later time, enter the c:\windows\system32\oemoobe\oemoobe.exe command.

Provisioning cluster shared storage

HP StoreEasy 3000 Storage products are NAS gateway products that provide file services for SAN or array block storage. By presenting LUNs from the SAN or array to the HP StoreEasy 3000 Storage, you can offer SMB and NFS file shares to clients. This also enables other Windows based features such as snapshots (volume shadow copies), data deduplication, directory quotas and much more.

All storage provisioning for HP StoreEasy 3000 Storage is done on the particular array used for storage. Consult the documentation for your particular array to perform the necessary tasks involved in presenting LUNs to the HP StoreEasy 3000 Storage. In general, you should follow the array’s guidelines for providing storage to Windows Storage Server 2012 or 2012 R2. This will also likely involve such tasks as cabling, configuring ports, zoning, and configuring MPIO.

Supported arrays include, but are not limited to the following:

• HP 3PAR StoreServ Storage

• HP EVA P6000 Storage

• HP XP P9000 Storage

• HP StoreVirtual 4000 Storage

• HP P2000 G3 MSA Array Systems

NOTE: For instructions on how to connect the HP StoreEasy 3000 Storage to an HP 3PAR StoreServ system, see the HP 3PAR Windows Server 2012 and Windows Server 2008 Implementation Guide, which is available at:

http://www.hp.com/support/manuals

Under storage, select Storage Software, and then select HP 3PAR Operating System Software under Storage 3PAR Device Management Software. The Implementation Guide is listed in the Setup and install – general section.

Cluster Configuration 27

(28)

Deploying two or more HP StoreEasy 3000 Storage systems as a Windows Failover Cluster enables highly available services such as file shares, iSCSI targets, and more. To create a cluster with two or more nodes, use Windows Failover Cluster Manager or equivalent PowerShell cmdlets.

Adding a node to an existing cluster

A cluster can consist of up to eight nodes. A dedicated network switch is recommended for connecting the cluster heartbeat when more than two nodes are used. Alternately, a dedicated VLAN on an existing switch can be used.

1. Add the new node to the same domain as the other nodes before adding the new node to the cluster.

2. Ensure that the shared storage is connected to the new node and shared LUNs are presented or exported to the new node.

3. Record the IP address for the Cluster Internal network. From the Start menu on the desktop, select Control Panel→Network and Internet→Network and Sharing Center. In the “View your active networks” section, select Cluster Internal,right-click and select Settings, and then click Details. . Record the IP address displayed in Autoconfiguration IPv4 Address. Unless the address has been assigned, the address will be an APIPA IP address, such as 169.X.X.X.

4. Disconnect the interconnect cable and connect it from Port 1 of the first node to any port on the switch. Assign the IP address that was recorded in step 3 (for example, 169.X.X.1) 5. Connect Port 1 of the second node to the next port on the same switch and assign an IP address

(for example, 169.X.X.2).

6. Connect Port 1 of the new node to the next port on the same switch and assign an IP address (for example, 169.X.X.3).

7. From the first node, select the Windows Server Manager icon on the desktop taskbar, and then select Tools→Failover Cluster Manager.

8. Existing clusters are displayed in the left navigation pane. Right-click the cluster name and select Add Node or select the cluster name to view the Add Node option under Configure in the main viewing pane.

9. Click Add Node.

The Add Node Wizard opens. Navigate through the wizard to enter the details about the new node (server IP address or hostname). When finished, the new node is added to the cluster. All nodes can be joined to the cluster simultaneously. HP recommends that you add

(29)

a single node at a time verifying cluster operation with each node addition. Cluster validation must also be run when each node is added.

10. Verify that the cluster resources can perform failover:

a. Under Navigate in the main viewing pane, click Roles. Verify that a file server is listed (if not, create one). Right-click the file server name and select Move. There are two move options: Best Possible Node and Select Node.

b. Click Select Node.

The Move Clustered Role window opens. Select the newly added node to move the resource to and click OK. The operation must be successful to indicate the nodes can failover.

Repeat the procedure for each additional node.

Heartbeat Network

When configuring the HP StoreEasy 3000 Storage system for a two-node cluster, it is important to dedicate a minimum of one network port on each server to heartbeat network communications.

NOTE: The heartbeat network configuration is not necessary for a single-node cluster. However, to add a second node to this cluster in future, reserve a physical network port.

It is recommended to utilize the network ports as depicted infigure 1for the heartbeat. Also, it is recommended that you rename these network ports on each system to reflect that this is the

"heartbeat" or "internal cluster" network connection.

Figure 9 Connecting the servers

Assigning an IP address to the heartbeat on each node:

1. Using a browser, open a remote console to each node with iLO. For more information on iLO access to the servers, see the Quick Start Guide or Administrator Guide for your model.

2. Log on to Windows on the second node with the administrator password for the server.

3. From the Start screen on the desktop, select Control Panel→Network and Internet→Network and Sharing Center.

NOTE: In Windows Storage Server 2012 R2, a Windows icon displays by default in the bottom task bar. To access the Start Screen, click the Windows icon in the lower left task bar.

Click the down arrow at the bottom of the screen to display all menus and applications available from the Start screen. You can also access the Start Screen by pressing the Windows key on your keyboard.

4. In the View your active networks section, select the network port that you utilized for the heartbeat.

5. Click Details.

(30)

6. Record the IPv4 address in the Network Connection Details box. You can assign a static address to each node or using the automatic private IP addressing (APIPA) IP address. The important thing to note is that the IP addressing be a unique network segment from the rest of your network IP addressing scheme.

NOTE: Unless an IP address is assigned either statically or through DHCP, the address will use an automatic private IP addressing (APIPA) IP address, between 169.254.0.1 through 169.254.255.254.

To verify heartbeat network:

1. Connect to each node.

2. Issue a ping command from each node to the other node. If this is successful then you can proceed to the next step.

For information on troubleshooting, see“Troubleshooting, servicing, and maintenance” (page 114) NOTE: Windows Storage Server 2012 R2 allows you to enter more than one IP address.

Shared Storage

It is necessary to have established at least one shared LUN between the two nodes prior to creating the two node failover cluster. Follow the instructions for your particular array on how to configure the shared storage so that both nodes have visibility to the storage.

The Following are the requirements for shared storage that will enable creation of a two node cluster:

1. Create a LUN that will be used as a witness disk or quorum disk.

• Create a LUN of at least 544 MB. This will allow for a volume size of the required 512 MB after NTFS formatting.

• Present the LUN to all hosts that will be part of the cluster.

2. Optionally, create an additional LUN or LUNs that will be assigned to the first file server.

When the Validate and Create the Cluster ICT task is run, the wizard will look for additional LUNs. If any are found, the wizard will provide an option to create a file server in addition to creating the cluster. The Validate and Create the Cluster wizard uses the following logic to assign LUNs:

• The smallest LUN that is larger than 500 MB will be used as the quorum disk in the cluster.

• Any additional LUNs will be assigned to the file server that will be created.

• If you want to create a file server when the cluster is created, provision an additional LUN.

NOTE: If one or more volumes of LUNs are exported to the nodes but their unique IDs do not match or are not listed, you must update the storage provider cache by invoking

Update-StorageProviderCache –DiscoveryLevel Fullfrom an elevated Administrator PowerShell command prompt on each server. However, if updating the cache does not resolve the issue, ensure that the HBAs or network adapters used to connect the storage are identical and have the same firmware and driver versions. You must reboot both nodes if changes are made to the firmware or drivers. If you still face issues with updating the storage provider cache, run the cmdlet Get-StorageProvidercommand on each node to validate that the system can access the storage. For more information, see the installation and setup information for your shared storage solution.

For the supported versions of HP 3PAR Management Console software to manage the Disk Array, see the HP 3PAR Disk Array product documentation.

(31)

NOTE: To view shared storage for iSCSI connectivity to the 3PAR disk array, complete the Configure Networking task in ICT. It is necessary to complete the Configure Network task in ICT when utilizing the HP 3PAR management console or command line utility from the host that is currently being configured which enables the host to connect to the 3PAR disk array through the network. Consider utilizing HP 3PAR Virtual Domains software to increase security and to achieve greater storage service levels for both users and applications. For more information, see HP 3PAR StoreServ Storage Concepts Guide.

For more information, seeHP 3PAR Windows Server 2012 and Windows Server 2008 Implementation GuideandBest practices for HP 3PAR StoreServ File Controllers.

Cluster Creation

1. Validate the cluster.

Before you create the failover cluster, HP recommends that you validate the configuration to make sure that the hardware and hardware settings are compatible with failover clustering.

Microsoft supports a cluster solution only if the complete configuration passes all validation tests and if all hardware is certified for the version of Windows Server that the cluster nodes are running.

a. On a computer that has the Failover Cluster Management Tools installed from the Remote Server Administration Tools, or on a server where you installed the Failover Clustering feature, start Failover Cluster Manager. To do this on a server, start Server Manager, and then on the Tools menu, click Failover Cluster Manager.

b. In the Failover Cluster Manager pane, under Management, click Validate Configuration.

Figure 10 Failover Cluster Manger

2. On the Before You Begin page, click Next.

3. On the Select Servers or a Cluster page, in the Enter name box, enter the NetBIOS name or the fully qualified domain name of a server that you plan to add as a failover cluster node, and then click Add. Repeat this step for each server that you want to add. To add multiple servers at the same time, separate the names by a comma or by a semicolon. For example, enter the names in the format server1.contoso.com, server2.contoso.com. When you are finished, click Next.

(32)

Figure 11 Validate a Configuration Wizard

4. On the Testing Options page, click Run all tests (recommended), and then click Next.

5. On the Confirmation page, click Next.

The Validating page displays the status of the running tests.

6. On the Summary page, do either of the following:

• If the results indicate that the tests completed successfully and the configuration is suited for clustering, and you want to create the cluster immediately, make sure that the Create the cluster now using the validated nodes check box is selected, and then click Finish.

Then, continue to Create the Cluster Failover procedure.

• If the results indicate that there were warnings or failures, click View Report to view the details and determine which issues must be corrected. Realize that a warning for a particular validation test indicates that this aspect of the failover cluster can be supported, but might not meet the recommended best practices.

Figure 12 Validate a Configuration Wizard

(33)

7. Create a cluster.

a. Start Server Manager.

b. On the Tools menu, click Failover Cluster Manager.

c. In the Failover Cluster Manager pane, under Management, click Create Cluster.

The Create Cluster Wizard opens.

Figure 13 Failover Cluster Manager

d. On the Before You Begin page, click Next.

e. If the Select Servers page appears, in the Enter name box, enter the NetBIOS name or the fully qualified domain name of a server that you plan to add as a failover cluster node, and then click Add. Repeat this step for each server that you want to add. To add multiple servers at the same time, separate the names by a comma or a semicolon. For example, enter the names in the format server1.contoso.com;

server2.contoso.com. When you are finished, click Next.

Figure 14 Create Cluster Wizard—Select Servers