advertisement
HPE StoreVirtual 3000 File Controller
Administrator Guide
Abstract
This document describes how to install, configure, and maintain HPE StoreVirtual 3000 File
Controller and is intended for system administrators. For the latest version of this guide, go to https://www.hpe.com/support/manuals.
Part Number: C8S69-96121
A
Published: March 2017
Edition: 1
©
2016, 2017 Hewlett Packard Enterprise Development 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 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.
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
Microsoft
®
and Windows
®
are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Java
™
is a US trademark of Sun Microsystems, Inc.
UNIX
®
is a registered trademark of The Open Group.
Contents
HPE StoreVirtual 3000 File Controller........................................................8
Installing HPE StoreVirtual 3000 File Controller ....................................10
Configuring HPE StoreVirtual 3000 File Controller ............................... 17
Managing HPE StoreVirtual 3000 File Controller....................................49
Contents
3
Administration tools..................................................................................62
Storage management overview................................................................65
File server management............................................................................72
4 Contents
Integrating local file system security into Windows domain environments.................. 94
Comparing administrative (hidden) and standard shares............................................ 94
Management tools..................................................................................... 97
Cluster administration...............................................................................99
Contents
5
Troubleshooting, servicing, and maintenance......................................114
6 Contents
Recovering HPE StoreVirtual 3000 File Controller .............................. 132
Backing up and restoring HPE StoreVirtual 3000 File Controller with Windows Recovery
Product Feedback....................................................................................140
Iternity iCAS............................................................................................. 141
Support and other resources................................................................. 142
Operating system logical drives............................................................ 145
Network ports...........................................................................................146
Warranty and regulatory information.....................................................149
Contents
7
HPE StoreVirtual 3000 File Controller
The HPE StoreVirtual 3000 File Controller enables simplified file and application storage. This reduces your cost of ownership by simplifying management, increasing resource utilization, centralizing growth, and protecting data.
Features
The HPE StoreVirtual 3000 File Controller provides the following advantages:
• Efficiently maximizing resources through file and data management without increasing costs.
• Hewlett Packard Enterprise and Microsoft management integration, including Microsoft Server Manager and System Center and HPE 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 HPE StoreVirtual 3000 File Controller features, go to: https://
www.hpe.com/us/en/storage/storevirtual.html
Hardware components
This section provides illustrations of the HPE StoreVirtual 3000 File Controller hardware components.
HPE StoreVirtual 3000 File Controller hardware components
This section illustrates the components and LEDs located on the front and rear panels of the HPE StoreVirtual
3000 File Controller.
The chassis configuration for the HPE StoreVirtual 3000 File Controller system includes two HPE Proliant
DL120 Gen9 Server.
Figure 1: HPE StoreVirtual 3000 File Controller front panel components
1. Access Panel
3. USB 2.0 connector
2. Serial label pull tab
4. UID LED
5. Health LED 6. NIC status LED
7. Power On/Standby button and system power LED 8. 4LFF drive
8 HPE StoreVirtual 3000 File Controller
Figure 2: HPE StoreVirtual 3000 File Controller rear panel LEDs and buttons
1. Slot 3 PCIe3 x8 (8, 4, 1)*
3. Slot 1 PCIe3 x16 (16, 8, 4, 1)
5. Power supply power LED
7. Embedded 2x1GbE network adapter
2. Slot 2 PCIe3 x8 (8, 4, 1)
4. Non-hot-plug power supply
6. Power supply power connection
8. 4LFF drive
9. Video connector 10. USB 3.0 connectors
* Slot 3 supports PCIe x16 (16, 8, 4, 1) if the GPU riser cage is installed.
Software components
Windows Storage Server 2016 Standard Edition comes preinstalled and activated on the HPE StoreVirtual
3000 File Controller. The system configuration also includes the Initial Configuration Tasks window,
Network Configuration Tasks window, which are used to set up and manage HPE StoreVirtual 3000 File
Controller.
The Windows Server Manager > Tools > StoreVirtual menu provides a collection of HPE and Microsoft utilities that are useful for managing HPE StoreVirtual 3000 File Controller. 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 HPE StoreVirtual 3000 File Controller, configuring email alerts, registering product, provisioning storage, and protecting your server. For more information on the ICT tasks, see
Configuring HPE StoreVirtual 3000 File Controller . Using Windows Server Manager > File and Storage
Services, you can also create virtual disks and place volumes on the virtual disks.
Software components
9
Installing HPE StoreVirtual 3000 File Controller
Setup overview
The HPE StoreVirtual 3000 File Controller comes preinstalled with the Microsoft Windows Storage Server
2016 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 HPE StoreVirtual 3000 File Controller.
Default roles describes the default roles:
10 Installing HPE StoreVirtual 3000 File Controller
Table 1: Default roles
Role
File and Storage Services
Print and Document Services
Web Server (IIS)
Role service
• File and iSCSI Services
◦ File Server
◦ Branch Cache for Network Files
◦ Data Deduplication
◦ Distributed File System (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 Server
• Internet Printing
• Line Printer Daemon (LPD) Service
• 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
– .NET Extensibility 4.6
– ASP
– ASP.NET 4.6
Installing HPE StoreVirtual 3000 File Controller
11
Role Role service
– ISAPI Extensions
– ISAPI Filters
• Management Tools
◦ IIS Management Console
◦ IIS 10 Management Compatibility
– IIS 10 Metabase Compatibility
Verify the kit contents
Remove the contents, ensuring that you have all of the following components. If components are missing, contact technical support.
Hardware
• HPE StoreVirtual 3000 File Controller system (with operating system preloaded)
• Power cords
• Rail kit
Media and documentation
• HPE StoreVirtual 3000 File Controller Quick Start Guide
• Safety and Disposal Documentation CD
• HPE System Recovery DVD (if ordered)
• End User License Agreement
• Certificate of Authenticity Card
• 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 serial number of HPE StoreVirtual 3000 File Controller, Certificate of Authenticity (COA), and End User License Agreement (EULA). Record the serial number and COA product key and make a print copy of the EULA as needed.
The Certificate of Authenticity (COA) label is used to:
• Replace the main board/motherboard.
• Upgrade the factory-installed operating system using the Microsoft Upgrade program for license validation.
• Reinstall the operating system because of a failure that has permanently disabled it.
NOTE:
It is important that you maintain the COA or a copy of the COA license information. In the event of a system board replacement the COA will be needed to re-establish the license of the operating system.
The serial number is located in several places:
• Top of the HPE StoreVirtual 3000 File Controller system
• Back of the HPE StoreVirtual 3000 File Controller system
• Inside the HPE StoreVirtual 3000 File Controller system’s shipping box
• Outside the HPE StoreVirtual 3000 File Controller system’s shipping box
12 Verify the kit contents
The COA card is located inside the shipping box. There is also a COA sticker with product key affixed to the top of the HPE StoreVirtual 3000 File Controller system. The electronic copy of the EULA installed with the system is available at %SystemDrive%\Windows\System32\license.rtf.
Installing the HPE StoreVirtual 3000 File Controller hardware
StoreVirtual 3000 File Controller.
For HPE StoreVirtual 3000 File Controller systems, install the rail kit and insert and secure the storage system into the rack by following the Rack Rail Kit Installation Instructions.
Validate network information
Complete the tests in Validation tests (clustered system) or Validation tests (standalone system) ,
depending on your configuration, to verify network connectivity. Consult with your network administrator to confirm test results.
Table 2: Validation tests (clustered system)
Test Command(s) to execute Successful?
(Y/N)
Ping the IP address of Node 2 from Node 1.
ping <node 2 address>
Ping the name of Node 2 from
Node 1.
ping <node 2 name> ping <node 2 fqdn> ping <node 1 address>
Ping the IP address of Node 1 from Node 2.
Ping the name of Node 1 from
Node 2.
ping <node 1 name> ping <node 1 fqdn>
Verify forward and reverse DNS information for Node 1 is correct.
nslookup <node 1 address> nslookup <node 1 name> nslookup <node 1 fqdn>
Verify forward and reverse DNS information for Node 2 is correct.
nslookup <node 2 address> nslookup <node 2 name> nslookup <node 2 fqdn>
Ping the domain controller from
Node 1.
ping <domain controller address> ping <domain controller name> ping <domain controller fqdn>
Table Continued
Installing the HPE StoreVirtual 3000 File Controller hardware
13
Test Command(s) to execute Successful?
(Y/N)
Ping the domain controller from
Node 2.
Verify the network path to the domain controller and DNS servers is correct.
ping <domain controller address> ping <domain controller name> ping <domain controller fqdn> pathping <domain controller address> pathping <domain controller name> pathping <DNS server address> (repeat for each DNS server) pathping <DNS server name> (repeat for each
DNS server)
Table 3: Validation tests (standalone system)
Test Command(s) to execute Successful?
(Y/N)
Ping the IP address of the HPE
StoreVirtual 3000 File Controller 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 HPE
StoreVirtual 3000 File Controller system.
ping <system address>
Ping the name of the HPE
StoreVirtual 3000 File Controller 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 HPE StoreVirtual 3000
File Controller system.
ping <node 1 name> ping <node 1 fqdn>
If you will be adding the HPE StoreVirtual 3000 File Controller system to an Active Directory domain, some additional tests include:
Table Continued
14 Installing HPE StoreVirtual 3000 File Controller
Test Command(s) to execute Successful?
(Y/N)
Ping the domain controller from the HPE StoreVirtual 3000 File
Controller system.
ping <domain controller address> ping <domain controller name>
Verify the network path to the domain controller and DNS servers is correct.
pathping <domain controller address> pathping <domain controller name> 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. HPE recommends that you also verify the iLO IP address and name resolution; however, this is not critical to support the cluster and file server.
Connecting to HPE StoreVirtual 3000 File Controller
Use either the direct attach or iLO method to connect to HPE StoreVirtual 3000 File Controller.
IMPORTANT:
Only the direct attach and iLO access methods can be used to install HPE StoreVirtual 3000 File
Controller. When the installation process completes and the server’s IP addresses have been assigned, you can then additionally use the remote desktop method to access HPE StoreVirtual 3000 File
Controller.
• 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 HPE StoreVirtual 3000
File Controller in this sequence: keyboard, mouse, network cables, monitor cable, and power cable.
NOTE:
The keyboard, mouse, and monitor are not provided with HPE StoreVirtual 3000 File Controller.
• iLO—Access HPE StoreVirtual 3000 File Controller using the iLO remote management method:
1. Connect a network cable to the iLO port located on the back of the HPE StoreVirtual 3000 File
Controller system.
2. Connect a power cable to HPE StoreVirtual 3000 File Controller.
3. Locate the iLO Network Settings tag attached to the HPE StoreVirtual 3000 File Controller 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 HPE StoreVirtual 3000 File Controller.
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 HPE StoreVirtual 3000 File Controller.
Connecting to HPE StoreVirtual 3000 File Controller
15
For detailed instructions on using iLO remote management software, see the HPE iLO 4 User Guide, which you can search for (by product name) at https://www.hpe.com/support/manuals.
Power on the server and log on
Procedure
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 HPE StoreVirtual 3000 File Controller 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 HPE StoreVirtual 3000 File Controller system installation process takes approximately 10–15 minutes.
3. After installation completes and the server (or servers if deploying a cluster) reboots, you will be prompted to log in with the Administrator password that was designated during initial configuration.). If you are deploying a cluster, continue to work only with the server on which you used the Setup Windows Wizard.
16 Power on the server and log on
Configuring HPE StoreVirtual 3000 File
Controller
The HPE StoreVirtual 3000 File Controller systems can be deployed in the following configurations:
• Standalone, which you can also use to configure in a single-node cluster configuration or join the node to an existing Windows Failover Cluster. Windows Failover clusters can be a minimum of one node and contain up to eight nodes in one cluster configuration.
• Two-node failover cluster, which can have additional cluster nodes added after the initial setup of a failover cluster (windows failover clusters can be created with just one node and can have a maximum of eight nodes using the StoreVirtual 3000 File Controller systems).
The Initial Configuration Tasks window reflects the steps necessary to set up the system in a single-node configuration. Once that has been done, see the guidelines for creating a Windows failover cluster in the following Microsoft Technet article:
Failover Clustering Overview
When you first powered on the servers, you were asked if you wanted to deploy as a standalone or twonode cluster configuration. The Initial Configuration Task window reflects the steps for setting up the
Configuration Tasks window provides the steps to set up the system in a standalone or single-node
cluster configuration. If the two-node cluster is selected, the steps for creating a two-node cluster is provided by ICT.
If you wanted to create a cluster with more than one node and selected the standalone configuration when you first powered on the server, you can continue to follow the installation steps for the single-node cluster.
To join a node to an existing cluster, follow the steps in the Configure Cluster section.
It is recommended to complete the initial installation and setup of the StoreVirtual Storage Array before completing the configuration of the StoreVirtual File Controller. The administrator login and virtual IP address is required to configure the StoreVirtual during ICT.
Initial Configuration Tasks
The Initial Configuration Task (ICT) window enables you to configure your system. After the initial configuration is complete, the ICT window launches automatically for a user who is a member of the local administrator group. You can open only one instance of the ICT at a time.
Use ICT to perform the following configuration 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.
• Create storage pools and virtual disks.
• Enable software updates and enhancements directly from Windows update.
• Set up optional data protection solutions on the HPE StoreVirtual 3000 File Controller with cloud-based data backup by replicating data using Vision Solutions Double-Take Availability. Both of these data protection solutions require separate licensing, but are available to use for a limited time via a free trial license.
The online help is available for each configuration task in the ICT window. You can launch the online help by clicking F1.
Configuring HPE StoreVirtual 3000 File Controller
17
Standalone or Single Node Configuration
Once the HPE StoreVirtual 3000 File Controller is connected to your network and to external storage enclosures (if present), powered up and logged on, the system needs to be configured for completing the installation. 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.
NOTE:
• The ICT refreshes periodically, as indicated by a message in the lower right corner of the window. If you select an ICT task while a refresh is in progress, there is a delay before the application for that task is launched. You can also refresh ICT by pressing F5.
• When a single-node cluster is converted to a two or more node cluster, the ICT window is launched on all nodes because the RunDiscovery registry key does not get updated when the cluster is created.
The following tasks are included in the ICT:
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:
HPE 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.
• 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 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 > StoreVirtual > Save Reseller information.
◦ Double-click the System Tools folder on the desktop and select Save Reseller Information.
Networking
This task group enables you to set the network IP and domain of HPE StoreVirtual 3000 File Controller . The following tasks are included in this group:
• Configure networking—Enables you to configure the network interfaces using the Network Configuration
Tool (NCT) wizard. For detailed information on NCT, see Using the Network Configuration Tool.
• Provide computer name and domain—Enables you to specify the computer name and domain.
Windows Storage Server 2012 is installed with a randomly generated computer name. You may find the
18 Standalone or Single Node Configuration
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.
◦ HPE 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, clickProvide computer name and domain in the Initial
Configuration Tasks window and then click Change on the Computer Name tab.
Storage Management
You can use the following options to register for SMI-S provider and check the MPIO configuration:
• Connecting to StoreVirtual iSCSI Storage Arrays
• Connect to StoreVirtual Fibre Channel Storage Arrays
• Register StoreVirtual Storage Array
• Fibre Channel or iSCSI Initiator configuration
Connecting to StoreVirtual iSCSI Storage Arrays
To connect to StoreVirtual iSCSI Storage Array, first set up the StoreVirtual Storage Array to export storage to the StoreVirtual File Controller as per the instructions in the StoreVirtual Storage documentation. Next, configure the StoreVirtual File Controller iSCSI initiator with the StoreVirtual Storage Array Virtual IP to allow the file controller to logon and connect the storage on the StoreVirtual Storage Array.
• Launch the iSCSI Initiator properties from Server Manager→Tools.
• In the Discovery tab page, click Discover portal to add the IP address of the Virtual IP address.
• Click OK.
• After discovery, all the Targets from the StoreVirtual storage array will be listed in the Discovered Targets box. Select the one you want to connect, and click on Connect button to allow the initiator to connect to the StoreVirtual storage array and access the associated disks.
• Connect to Target dialog box appears.
◦ If CHAP is configured, then click on the Advance button and enter the authentication information.
◦ If the system for MPIO is configured, ensure to check Enable-Multi Path.
Verify that there are multiple connections (minimum of four sessions added) by selecting the connection and the appropriate properties. This enables the iSCSI multiple paths to the StoreVirtual Storage Array.
Storage Management
19
The iSCSI initiator configuration on the StoreVirtual File Controller is now complete and you will be able to access the disks from the file controller.
Connect to StoreVirtual Fibre Channel Storage Arrays
To connect through fibre channel to the StoreVirtual Storage Array from the StoreVirtual File Controller, follow the instructions in the StoreVirtual Storage Array setup documentation and export volumes to servers or server clusters.
Register StoreVirtual Storage Array
Registering the StoreVirtual Storage Array enables the StoreVirtual File Controller to gather information about the state of the storage array. This process adds the Storage Management Initiative Specification (SMI-S) provider for the StoreVirtual Storage Array to the list of storage providers that the StoreVirtual File Controller has been granted access to.
For more information about SMI-S, see http://www.snia.org/forums/smi/tech_programs/smis_home.
Procedure
1. If the StoreVirtual array's SMI-S provider is not registered, then select Register Storevirtual from the menu and enter the Virtual IP address (VIP) assigned during the set up of the StoreVirtual Storage Array.
2. Register the StoreVirtual provider using the registration tool. When prompted, enter the IP address of the array and registration credentials. By default the SMI-S registration tool attempts to establish a connection through HTTPS using port 5989.
If a different protocol is required or a different port is configured on the array, you must perform the
StoreVirtual registration at an elevated PowerShell command prompt. For more information, refer to the storage array documentation.
3. To launch the StoreVirtual Storage Array provider registration tool, click Register SMI-S provider.
The login is the StoreVirtual Storage Array Administrative account established at the time of implementation. The IP address is the Virtual IP address established on the StoreVirtual Storage Array.
For additional information about the StoreVirtual Array Management, refer to the specific StoreVirtual manuals available for your system. Once the StoreVirtual Storage Array is registered, the status of Other
provider registered is indicated within the ICT.
NOTE:
If the system restart causes the un-registration of the StoreVirtual provider, a start up script will run in the background which will re-register the StoreVirtual with the saved data. This is only applicable if previously or initially the StoreVirtual registration was done using Array Registration Tool.
You can execute “Get-StorageProvider” powershell cmdlet to check if an array is registered. If the Array registration fails in startup, a message is displayed indicating if you want to open the Array
Registration tool.
4. Registering the StoreVirtual 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 Full PowerShell commandlet at an elevated PowerShell prompt.
Multi-Path IO configuration
Clicking Multi-Path IO configuration link launches the MPIO control panel to configure MPIO.
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
20 Configuring HPE StoreVirtual 3000 File Controller
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 StoreVirtual 3000 file controller. These settings are not available in the standalone StoreVirtual 3000 systems.
Notifications
This task group enables you to configure email alerts and register for proactive notifications.
The following tasks are included in this group:
• Configure email alerts—Enables you to configure the email accounts to 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 Windows Server Manager and select Tools→StoreVirtual→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 HPE product registration page.
IMPORTANT:
HPE strongly recommends registering the 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→StoreVirtual→Register Product.
Storage Configuration
The Provision StoreVirtual Storage task group enables you to create virtual disks, create volume onto the virtual disk and to create a file share onto the newly created volume. The following tasks are included in this group:
Create virtual disks
Clicking this link will open a IP Address pop-up which allows the user to enter the StoreVirtual IP address.
This will open the StoreVirtual web UI window which allows the user to create a StoreVirtual Storage array volume or volumes and export the same to the StoreVirtual File Controller or StoreVirtual File Controller cluster.
NOTE:
The StoreVirtual storage array volume consists of a logical entity made up of storage on one or more
StoreVirtual storage arrays. The StoreVirtual storage array volumes when exported will display as virtual disks on the StoreVirtual File Controller disk management interfaces.
Notifications
21
Procedure
1. Click Create Virtual Disks for StoreVirtual File Controller in the Configure Cluster task group in the
ICT.
The StoreVirtual Web UI is displayed.
2. Enter the username and password to login and the StoreVirtual array window is displayed.
3. Select Volumes from the StoreVirtual drop-down menu to display the Volumes screen.
4. Click Create Volumes and the Create Volume window is displayed.
5. Specify the name for a volume (name must be unique and 1 to 27 characters. Avoid spaces, equals, double quotes and semicolons).
6. Specify the volume size (the default size is 500 GiB).
7. Click Create to create the virtual disk.
Once the virtual disk is created, export the volume to allow the StoreVirtual File Controller(s) to utilize the volumes.
Export volume to StoreVirtual File Controller cluster
1. Click on the volume created.
2. Click +Export to StoreVirtual File Controller or Server cluster in the Exports menu.
The Export to Server or Server Cluster window opens.
3. Click on Server button to export the storage to only one server. To export the storage to multiple server, click on Server Cluster button.
For more information on configuring the server or server cluster, refer to StoreVirtual Array manuals or online help.
4. Click Select to select the server or server cluster from the drop-down menu.
5. Select Read/Write in the Permissions drop-down menu assigned to this export.
6. Click Export to export virtual disk to a StoreVirtual File Controller server or cluster.
The volume is now exported to the server or server cluster and you have the option to either create and export more volumes or proceed to the section ??? to complete the configuration of the storage.
NOTE:
Any volumes that are present during configuring of the StoreVirtual File Controller for Failover
Clustering are added to the cluster storage.
Create Volume
Clicking this link opens the Disk Management Console window which allows the user to bring the exported virtual disk online and create a volume onto the virtual disk.
Firstly, the Virtual disk has to appear online. The following is the procedure to bring virtual disk online:
Procedure
1. Click Create Volumes in the Configure Cluster task group in the ICT.
2. The Disk Management Console window opens that displays the list of virtual disks created.
Click on the new virtual disk and click online to bring the virtual disk online.
3. The Virtual Disk Manager pop-up window appears. Click OK.
Create Simple Volume
1. Right-click on the newly created volume to select New Simple Volume.
2. The New Simple Volume wizard appears. Click Next to specify the volume size.
3. Click Next and the Assign Drive Letter or Path screen appears.
4. Click Assign the following drive letter radio button and click Next.
22 Configuring HPE StoreVirtual 3000 File Controller
5. The Format Partition screen appears. Click Format this volume with the following settings radio button to specify the settings.
6. Click Next and the Completing the New Volume wizard appears.
7. Click Finish to close the wizard. The requested resource is in use message appears.
8. Click OK.
Create New Spanned Volume
1. Right-click on the newly created volume to select New Spanned Volume.
The Welcome to the New Simple Volume wizard appears. Click Next.
2. Click Next.
The New Spanned Volume wizard opens.
3. In the Select Window screen, select the available disk to span through the virtual disk.
4. Click OK.
Create Share
Clicking this link opens the Computer Management Console window which allows the user to create a share onto the newly created volume.
Procedure
1. Click Create Share in the Configure Cluster task group in the ICT.
2. The Computer Management Console window is displayed. Click Shared Folders from the System
Tools drop-down menu.
3. Click Shares on the left-side of the window to specify the folder name.
4. Right-click on any existing folder path to select New Share.
5. The Create A Shared Folder Wizard is displayed. You need to browse to specify the folder path and click
Next.
6. The Name, Description, and Settings screen is displayed that allows the user to specify the share name.
Click Next.
7. The Shared Folder Permissions screen is displayed. Click All users have a read-only access radio button.
8. Click Finish.
The Sharing Successful screen is displayed. The status message and the summary is displayed.
9. Click Finish to close the wizard.
Configure Cluster
This task group enables you to create a cluster or join an existing node to a cluster using the Cluster
Configuration tool. To access the Cluster Configuration tool, click Create cluster or Join a cluster in the ICT window. The links to these tasks in the ICT window are disabled if any of the following conditions exist:
• The domain is not joined.
• The user is not logged in as a domain user.
• The status in the Storage Status task group is Storage not found.
• The cluster is already created or joined.
You can also use the Cluster Configuration tool to validate a cluster. If you click the Validate Cluster button before creating a cluster, the system validates the current node to check if it is suitable for the cluster. If you click the Validate Cluster button after creating a cluster, the cluster that you just created is validated.
Depending on the storage elements and number of nodes, the cluster validation might take several minutes. If the cluster creation or joining is not successful, appropriate messages are displayed on the screen. The log details are saved in the Cluster Configuration Tool.txt file, which is available at C:\nas\logs
\Cluster Configuration Tool.
Configure Cluster
23
Prepare a Witness Disk
Preparing a witness disk requires that a new virtual disk and volume be created. If the virtual disk and volume
used for the witness disk.
Create cluster
Clicking this link launches the Cluster Configuration tool that enables you to create a cluster. Perform the following steps to create a cluster:
Procedure
1. Click Create cluster in the Configure Cluster task group in ICT.
The Cluster Configuration tool is launched.
2. Enter the cluster name in Provide Cluster Name.
3. Click Validate Cluster to validate the node. This step is optional.
4. Click Create Cluster.
The Cluster created successfully message is displayed.
Consider the following when assigning a cluster name:
• The maximum length for a cluster name is 15 characters.
• The name must not contain any special characters, such as \ /*? < >| and “.
• The name must be unique. No other system or cluster present in the domain must have the same name.
Join a cluster
Clicking this link launches the Cluster Configuration tool that enables you to join an existing node to a cluster.
Perform the steps to join a cluster:
Procedure
1. Click Join a cluster in the Configure Cluster task group in ICT.
The Cluster Configuration tool is launched.
2. Enter the cluster name in Provide Cluster Name.
3. Click Validate cluster to validate the node.
4. Click Join cluster to join the node to the cluster.
The Joined to cluster successfully message is displayed.
Consider the following when assigning a cluster name:
• The maximum length for a cluster name is 15 characters.
• The name must not contain any special characters, such as \ /*? < >| and “.
• The name must be unique. No other system or cluster present in the domain should have the same name.
Protect This Server
This task group enables you to check that your HPE StoreVirtual 3000 File Controller system receives critical software updates and enhancements directly from the Microsoft website. The following tasks are included in this group:
• Enable automatic updating—Opens the Update & security Settings page where users can confirm
Update status and Update settings. All updates are downloaded and installed automatically and users can choose the system will reboot automatically when system is inactive or can be notified to schedule a reboot by opening Restart options. The Windows Update feature simplifies the task of updating the operating system, and saves administrator’s time. Features on the Windows Update dialog box are configurable by members of the administrators group on the local computer.
24 Protect This Server
HPE recommends the following for updates:
Users can configure how updating Microsoft products when Windows update takes place by opening
Advanced options.
◦ Run Download and Install Updates immediately after system installation.
◦ Subscribe to HPE customer advisories using Subscriber's choice for business. For more information, see Subscription Service. Ensure to check if firmware and related device drivers are up-to-date based upon information for your system at the HPE Support & Drivers website.
◦ Apply regular HPE StoreEasy Storage Service Releases.
• Vision Solution Double-Take Availability Information—Opens an HTML page that displays details about installing the trial 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
NOTE:
HPE 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 HPE StoreVirtual 3000 File Controller 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 HPE StoreVirtual 3000 File Controller, these steps can vary. These additional steps can include:
• Running Microsoft Windows Update—HPE highly recommends that you run Microsoft Windows updates to identify, review, and install the latest, applicable, critical security updates on HPE StoreVirtual 3000 File
Controller.
• Creating and managing users and groups—User and group information and permissions determine whether a user can access files. If the HPE StoreVirtual 3000 File Controller system is deployed into a workgroup environment, this user and group information is stored locally on the device. By contrast, if HPE
StoreVirtual 3000 File Controller is deployed into a domain environment, user and group information is stored on the domain.
• Configuring event notification.
• 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 HPE StoreVirtual 3000 File Controller—To register, see the HPE registration website (https://
h41360.www4.hpe.com/promo-signup.php?jumpid=hpr_r1002_usen_link2).
Two-node cluster configuration
After you have completed the physical installation of the HPE StoreVirtual 3000 File Controller and before you deploy the new system in your enterprise, you must configure your system. You can configure your system using the ICT window which opens automatically at logon for any user who is a member of the local administrators group. You can open only one instance of the ICT at a time. The system configuration and cluster deployment is completed from the first node (or local node). The first node is the server that was initially chosen to run the Set Up Windows wizard as described in the Quick Start Guide for your HPE
StoreVirtual 3000 File Controller system. Perform the tasks in ICT in order.
Complete system configuration
25
NOTE:
• When creating a cluster, ensure that both nodes have the same hardware configuration.
• The ICT refreshes periodically, as indicated by a message in the lower right corner of the window. If you select an ICT task while a refresh is in progress, there is a delay before the application for that task is launched. You can also refresh ICT by pressing F5.
• Many tasks are enabled only when the ICT can connect to the second node.
• 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.
The following tasks are included in the ICT:
Connection Status
Clicking on this link provides the user the ability to re-enter the secondary node IP address.
When the StoreVirtual 3000 File Controller powers up, and if you are creating a two-node cluster, the first node discovers the second node by default. This default connection occurs only if a physical connection exists between the two nodes. If you are creating a two-node cluster, the first node discovers the second node by default. This default connection occurs only if a physical connection exists between the two nodes. For
StoreVirtual 3000 File Controller, you must physically connect a cable on each node as shown in figure 1. If the default connection does not occur and the Unable to discover the second node message is displayed, follow the steps in Connect to the second node to manually connect the nodes.
Figure 3: Connecting the StoreVirtual File Controllers
Connect to the second node
Determining the IP address of the second node:
1. Using a browser, open a remote console to the second node with iLO. For more information on iLO access to the StoreVirtual File Controllers, 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 StoreVirtual File Controller
(the default password is HPEStorage!).
26 Connection Status
3. From the Start screen on the desktop, select Control Panel→Network and Internet →Network and
Sharing Center.
NOTE:
In Windows Storage Server 2016, 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 Cluster Internal.
5. Click Details.
6. Record the IPv4 address in the Network Connection Details box. Use this IP address to manually connect to the second node.
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 manually connect to the second node in ICT:
1. Click Connect to the second node. The Connect to second node dialog box appears.
2. Enter the IP address for the second node and click Apply.
For information on troubleshooting, see Troubleshooting, servicing, and maintenance
NOTE:
Windows Storage Server 2016 allows you to enter more than one IP address. Hewlett Packard
Enterprise only supports creating a two-node cluster through ICT. Enter only the address of the second node that will be a member of the cluster.
Networking
Clicking this link launches the Network Configuration Tool wizard that enables you to configure network interfaces, network teams, VLANs, and network interface IP addresses. You can also import the network configuration using the NCTConfig.xml file, which is the network configuration file. You can launch NCT directly using the following methods:
• Open a command prompt or PowerShell and type NCT.
• Open Server Manager and select Tools→StoreVirtual→Configure Networking.
• Double-click the System Tools folder on the desktop and click Configure Networking.
• Click Configure Networking on the Start screen.
• Click the Configure Networking icon on the desktop.
The NCT is divided into two panes. When you launch NCT to configure network interfaces or validate the network configuration, the network configuration discovery is initiated. When the system discovery is complete, the left pane or interface pane, lists the discovered interfaces and their operational state. On twonode clustered systems, the interfaces are listed in the respective node tab and all network configurations are applied to both nodes in a cluster automatically when using DHCP addressing. Only static IP address assignment is unique. Except when configuring IP addresses, selecting the interfaces has no effect. The right pane displays the current configuration step. Hovering over a network interface in the interface pane displays the device name, interface name, and status. For example, the interface might be disabled, disconnected, or enabled.
Networking
27
IMPORTANT:
While using NCT, if you change the network configuration of the system using any other tool, the changes are reflected in NCT only when you close and re-launch it. You must not change the settings of the interface used to access the system, for example, using remote desktop access. This will disconnect the Remote Desktop connections. Hewlett Packard Enterprise recommends using iLO until the network interfaces are configured. If a remote desktop session is being used, you can find the IP address of the iLO interface using the iLO Configuration Settings at System Tools Folder in the desktop.
The wizard includes the following sections:
• Network Interface IP Configuration
• Network Configuration Summary
Network Interfaces Settings
Network Interfaces enables you to configure the physical network interfaces to suit your environment.
To configure an interface:
Procedure
1. Select the Configure check box to enable changes to the network interface. The Cluster Internal interface and the interface used to communicate with the second node (if different) is excluded from the configuration. If you clear the check box, the interface is excluded from all configurations and is not modified.
2. Enter the new interface name. The new name that you enter must not contain special characters, such as
\ /*? < >| and “.
3. Click Next to proceed to the Network Team Configuration step.
The physical network interfaces that are part of a team or used for RDP cannot be configured. For such interfaces, the Configure check box is disabled.
Network Team Configuration
NOTE:
• It is optional to configure a network team. If you do not want to create network teams, click Next to proceed to the Network VLAN configuration step. The Do not configure network teams now option is selected by default.
• The Network Team Configuration (optional) window is displayed only if there are no pre-existing teams.
Network Team Configuration enables you to configure new teams. Teaming is used to increase available bandwidth, load balancing, and improving fault tolerance. The maximum number of teams that you can create is equal to the number of physical network interfaces on the system. On clustered systems, the number of teams created on the local node is same as the number of teams created on the remote node. Team creation on the remote node is automatic.
To create network teams if there are no existing teams:
Procedure
1. Select Configure network teams now and enter the number of teams you want to create in Number of
teams.
2. Click Next.
28 Configuring HPE StoreVirtual 3000 File Controller
To create network teams in the case of existing teams:
1. Select the physical network interfaces on the Network Interfaces window and click Next.
2. Select the Create check box and do the following:
a. Enter the team name.
b. Select the team type from Type. The default selection is Switch Independent/Dynamic.
NOTE:
The number of teams displayed for configuration or deletion depends on the number of physical network interfaces that you select. For example, if you select two interfaces for configuration, two rows will appear for team creation.
3. Click Next.
The network interfaces that are not included in any team are displayed.
4. Select the network interfaces that you want to include in the new team.
5. Click Next to proceed to the Network VLAN configuration step.
The Network Team Configuration window also enables you to delete an existing team by selecting the
Delete check box. The Delete check box is enabled only if a team exists. When you delete an existing team, the physical network interface included in that team can be used for new teams.
NOTE: When a team is created, a default virtual network interface is also created. To remove the default virtual interface, assign one or more VLAN IDs on theNetwork VLAN Configuration window and select the remove the default virtual network interface check box.
While creating network teams, the interfaces claimed by one team cannot be added to any other team. The team that these interfaces belong to is displayed next to the interface name. If all adapters are already claimed by one or more teams, a warning message is displayed. You can either go back and remove some interfaces from the previously created teams or skip the creation of a team.
• If some of the physical network interfaces included in the team are disconnected while other interfaces are connected, the team status is displayed as degraded.
• If all physical network interfaces included in the team are disconnected, the team status is displayed as disconnected.
The network teams are displayed in the interface pane when you proceed to the IP Address Configuration step.
Network VLAN Configuration
NOTE: It is optional to configure VLAN assignments. If you choose not to configure VLAN assignments, only the default team interface is created. Click Next to skip this step and go to the IP Address
Configuration step.
Network VLAN Configuration enables you to configure VLAN assignments. A maximum of 32 network interfaces, consisting of both physical and virtual are allowed. The default VLAN ID is 0, but the VLAN IDs can have a value from 0 to 4094. Each VLAN ID assigned to a physical network interface or network team creates a virtual network interface. Both physical and virtual interfaces created for network teams can have VLAN IDs assigned to them. If a physical interface is assigned a VLAN ID, a team is created with a single physical interface. A virtual interface with the VLAN ID is then created in the team.
To assign VLAN IDs:
Procedure
1. Select the Configure VLAN IDs now and click Next.
2. Select one of the following options and enter the VLAN ID in the respective fields:
Configuring HPE StoreVirtual 3000 File Controller
29
• Add a single VLAN ID—Select to add a single VLAN ID.
• Add discrete VLAN IDs—Select to add the VLAN IDs as comma separated values.
• Add a range of VLAN IDs—Select to specify the VLAN IDs using a start and end value with an increment. For example, a start value of 2 and an end value of 20 with an increment of 5 would assign
VLAN IDs 2, 7, 12, and 17.
3. Select the Remove the default virtual network interface check box to remove the default virtual interface from a team. This step is optional.
NOTE:
If a default virtual interface is deleted, the system will not receive any packets on the team or physical NIC unless you assign one or more VLAN IDs.
4. Click Next to proceed to the Network Interface IP Configuration step.
The VLAN assignments are displayed in the interface pane when you proceed to the Network Interface IP
Configuration step.
NOTE: If you select Do not configure network interface VLAN identifiers now after you assign
VLAN IDs to teams and adapters, the assigned IDs are not removed. You must go through each VLAN page and select the Do not add a VLAN ID to this team implicitly for all teams and adapters.
Network Interface IP Configuration
Network Interface IP Configuration enables you to begin the IP address configuration by selecting the interface on which you want to make changes using the interface pane. Each interface that can be configured is enabled on the system, even if no changes are made to the interface. The IP addresses that you assign can be static or dynamically assigned using DHCP.
To configure the IP information for an interface:
Procedure
1. Select Use DHCP to assign IP address and gateway to dynamically assign an IP address using DHCP or select Assign a static IP address and gateway to assign a static IP address.
IMPORTANT:
If you select Assign a static IP address and gateway, the DNS server address must also be static and you must also assign a network mask. Assigning a default gateway address is optional.
2. Select Use DHCP to assign DNS server addresses or Assign a static IP address and gateway. If you selected the Assign a static IP address and gateway option in the above step, the Assign a static IP
addresses for DNS option is selected by default and you cannot change it.
3. Click Next to proceed to the Network Configuration Summary step.
IMPORTANT:
Hewlett Packard Enterprise recommends that you check each interface before clicking Next on this window.
For clustered systems, all IP settings for an interface are copied to the remote node interface, except the IP address of the interface. To set the IP address on the remote node, click the Remote Node tab and enter the
IP address. Setting the IP address on the remote node is required only if the local node interface is assigned a static address.
30 Configuring HPE StoreVirtual 3000 File Controller
NOTE:
Configuring multiple interfaces on the same subnet is highly discouraged unless a proper routing infrastructure is configured in the environment and different gateways are specified for each interface.
Multiple interfaces on the same subnet can cause client access and domain join issues.
The network defined by the IP address and subnet mask is used to validate the gateway, if one is specified. If an interface is assigned a static address, its configuration is validated against other interface settings when a different interface is selected or when you click Next.
Network Configuration Summary
Network Configuration Summary enables you to view a summary of all configuration changes that will take place on the system. Before proceeding, confirm that the changes are appropriate. If some configurations are not required or not valid, click Previous or use the navigation links at the bottom of the page to correct the errors. To apply the configuration changes, click Apply. When you apply the changes and click Next, the details of each task configured is displayed. If some errors are encountered when the changes are applied, the same are displayed on the Errors tab.
When you apply the configuration changes, the system automatically creates and saves the network configuration file (NCTConfig.xml) at C:\Program Files\HPE\StoreEasy NetworkConfiguration
Wizard. This file includes the network configuration details. Only a user who is a member of the local administrator group can modify the contents of this file. The system creates the NCTConfig.xml file depending on the sequence in which the NCT wizard completes the network configuration tasks successfully.
For example, if the physical network interface configuration is successful, but the creation of teams or VLANs fails, then the NCTConfig.xml file is created with only the physical network interfaces listed in the file. The
VLANs and teams are not listed. This is because in this case, the NCT wizard successfully completed the network interface task, even though the other tasks were unsuccessful. However, if the physical network interface task fails, then the NCTConfig.xml file is not created at all because the validation failed at the first task. When the file is created successfully, you can use it to import the configuration from one server to another.
Important considerations while working with the NCTConfig.xml file are:
• Do not rename the XML tags in the file. Renaming the tags might lead to errors while applying the configuration.
• Do not rename the NCTConfig.xml file.
• Do not edit the contents of the PciKey tag. Editing this tag causes errors.
• You can edit only specific XML tags, such as, Name, AdapterIPConfiguration, and
AdapterHWInformation.
• If the NCTConfig.xml file is corrupt or the tags are invalid, a message is displayed on the screen indicating the same. You cannot reuse the same file. In such cases, NCT uses the system discovery state for further configurations.
For more information on importing the network configuration, see Importing network configuration.
Network Validation
Network Validation enables you to validate network settings. Network validation requires that all network interfaces that you want to test be connected.
NOTE:
• It is optional to validate network settings. However, Hewlett Packard Enterprise recommends using the network validation system to confirm that your network settings are valid and to help diagnose environmental network issues.
• You can launch only the Network Validation section of NCT by executing the NCT -validate command in a command prompt or PowerShell.
Configuring HPE StoreVirtual 3000 File Controller
31
To begin network validation:
Procedure
1. Select Validate the network configuration now.
2. Enter the name of the domain controller for the domain that your system will be a part of and IP address of the domain controller in the respective fields. The IP address of the domain controller is also necessary to fully validate the network configuration. If you do not want to join the system to a domain, you can leave these fields blank. In addition to the domain controller address, enter the IP address of a system for each of the interfaces.
3. Click Validate.
When the validation begins, the user interface might seem unresponsive. Each interface is tested in order and validation success or failure is noted in the output window. The validation progress is also displayed on the taskbar. The validation results are saved at c:\nas\logs\NetworkConfigTool. Each validation result is saved in a file named with the time and date the validation was performed . When the validation completes, the validation results are noted in the ICT window.
The following points describe the messages displayed in Network Validation:
• Network configuration not validated —The system is not able to validate the configuration.
• Network configuration validated —The system is able to complete the validation.
• Network validation failed —This message indicates that one or more validations steps failed.
Importing network configuration
The NCTConfig.xml file enables you to import the network configuration settings from one server to another and apply the network configuration settings for all interfaces at one instance. After successfully importing the settings, when you launch NCT, a confirmation message is displayed indicating if you want to use the last used network configuration settings. If you click Yes, the NCT wizard loads the network configuration details from the NCTConfig.xml file and displays the existing interface details along with the team details. You can reconfigure the desired network interface from the available interfaces and create new teams or delete existing teams.
IMPORTANT:
While changing the interface name, you must change only the prefix associated with the default VLAN.
For example, if the complete interface name is Ethernet 2 Team –VLAN Default, then you must change only the prefix, that is, Ethernet 2 Team. The default VLAN name, which is VLAN Default in this example, must not be changed.
To import the network configuration settings from the NCTConfig.xml file:
1. Open the NCTConfig.xml file and edit the IP configuration of the adapter in the
<AdapterIPConfiguration> tag.
2. Edit the interface name, if required.
3. Save the file and copy it to C:\Program Files\HPE\StoreEasy NetworkConfiguration Wizard on the server on which you want to import the configuration.
4. Launch NCT and when prompted, click Yes to use the last saved configuration.
The NCT wizard loads and displays the configuration details from the NCTConfig.xml file.
5. Click Next when the discovery completes.
6. Make required network configuration changes on the respective windows.
7. Click Apply on the Network Configuration Summary window to apply the changes.
8. Click Validate on the Network Configuration Validation window to validate the changes.
If the XML file import is unsuccessful, it could be due to one of the following reasons:
32 Configuring HPE StoreVirtual 3000 File Controller
• The file is corrupt.
• The number of adapters in the XML file and the number of adapters on the system on which you want to import the file do not match.
• The file name is different from NCTConfig.xml.
• The file is copied to a different location or folder.
• The XML tags other than the ones you can edit are edited.
For more information on the NCTConfig.xml file and its usage, see the StoreVirtual 3000 File Controller
Administration Guide.
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 Full from 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-StorageProvider command 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 HPE StoreVirtual 3000 File Controller Management Console software to manage the Disk Array, see the HPE 3PAR Disk Array product documentation.
Storage Management
You can use the following options to register for SMI-S provider and check the MPIO configuration:
• Connecting to StoreVirtual iSCSI Storage Arrays
• Connect to StoreVirtual Fibre Channel Storage Arrays
• Register StoreVirtual Storage Array
• Fibre Channel or iSCSI Initiator configuration
Shared Storage
33
Connecting to StoreVirtual iSCSI Storage Arrays
To connect to StoreVirtual iSCSI Storage Array, first set up the StoreVirtual Storage Array to export storage to the StoreVirtual File Controller as per the instructions in the StoreVirtual Storage documentation. Next, configure the StoreVirtual File Controller iSCSI initiator with the StoreVirtual Storage Array Virtual IP to allow the file controller to logon and connect the storage on the StoreVirtual Storage Array.
• Launch the iSCSI Initiator properties from Server Manager→Tools.
• In the Discovery tab page, click Discover portal to add the IP address of the Virtual IP address.
• Click OK.
• After discovery, all the Targets from the StoreVirtual storage array will be listed in the Discovered Targets box. Select the one you want to connect, and click on Connect button to allow the initiator to connect to the StoreVirtual storage array and access the associated disks.
• Connect to Target dialog box appears.
◦ If CHAP is configured, then click on the Advance button and enter the authentication information.
◦ If the system for MPIO is configured, ensure to check Enable-Multi Path.
Verify that there are multiple connections (minimum of four sessions added) by selecting the connection and the appropriate properties. This enables the iSCSI multiple paths to the StoreVirtual Storage Array.
The iSCSI initiator configuration on the StoreVirtual File Controller is now complete and you will be able to access the disks from the file controller.
Connect to StoreVirtual Fibre Channel Storage Arrays
To connect through fibre channel to the StoreVirtual Storage Array from the StoreVirtual File Controller, follow the instructions in the StoreVirtual Storage Array setup documentation and export volumes to servers or server clusters.
Register StoreVirtual Storage Array
Registering the StoreVirtual Storage Array enables the StoreVirtual File Controller to gather information about the state of the storage array. This process adds the Storage Management Initiative Specification (SMI-S) provider for the StoreVirtual Storage Array to the list of storage providers that the StoreVirtual File Controller has been granted access to.
For more information about SMI-S, see http://www.snia.org/forums/smi/tech_programs/smis_home.
Procedure
1. If the StoreVirtual array's SMI-S provider is not registered, then select Register Storevirtual from the menu and enter the Virtual IP address (VIP) assigned during the set up of the StoreVirtual Storage Array.
2. Register the StoreVirtual provider using the registration tool. When prompted, enter the IP address of the array and registration credentials. By default the SMI-S registration tool attempts to establish a connection through HTTPS using port 5989.
If a different protocol is required or a different port is configured on the array, you must perform the
StoreVirtual registration at an elevated PowerShell command prompt. For more information, refer to the storage array documentation.
3. To launch the StoreVirtual Storage Array provider registration tool, click Register SMI-S provider.
The login is the StoreVirtual Storage Array Administrative account established at the time of implementation. The IP address is the Virtual IP address established on the StoreVirtual Storage Array.
For additional information about the StoreVirtual Array Management, refer to the specific StoreVirtual manuals available for your system. Once the StoreVirtual Storage Array is registered, the status of Other
provider registered is indicated within the ICT.
34 Configuring HPE StoreVirtual 3000 File Controller
NOTE:
If the system restart causes the un-registration of the StoreVirtual provider, a start up script will run in the background which will re-register the StoreVirtual with the saved data. This is only applicable if previously or initially the StoreVirtual registration was done using Array Registration Tool.
You can execute “Get-StorageProvider” powershell cmdlet to check if an array is registered. If the Array registration fails in startup, a message is displayed indicating if you want to open the Array
Registration tool.
4. Registering the StoreVirtual 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 Full PowerShell commandlet at an elevated PowerShell prompt.
Multi-Path IO configuration
Clicking Multi-Path IO configuration link launches the MPIO control panel to configure MPIO.
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 StoreVirtual 3000 file controller. These settings are not available in the standalone StoreVirtual 3000 systems.
Notifications
This task group enables you to configure email alerts and register for proactive notifications.
The following tasks are included in this group:
• Configure email alerts—Enables you to configure the email accounts to 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 Windows Server Manager and select Tools→StoreVirtual→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 HPE product registration page.
IMPORTANT:
HPE strongly recommends registering the 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:
Notifications
35
◦ Double-click the Register Product icon on the desktop.
◦ Click Register Product on the Start screen.
◦ Open Server Manager and select Tools→StoreVirtual→Register Product.
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:
HPE 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.
• 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 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 > StoreVirtual > Save Reseller information.
◦ Double-click the System Tools folder on the desktop and select Save Reseller Information.
Configure Cluster
The cluster configuration tasks are disabled if shared storage is not discovered. You can perform the following tasks in cluster configuration:
• Provide cluster name and domain
• Prepare witness disk
• Create virtual disks for StoreVirtual file controller
• Create volume for StoreVirtual file controller
• Validate and create the cluster
Provide cluster name and domain
Select Provide cluster name and domain to open the Microsoft Cluster Name and Domain Join wizard.
Follow the instructions within the wizard. Specifically, the wizard will require the following information to complete the task:
• An Active Directory domain—Both nodes will be joined to this domain as member StoreVirtual File
Controllers.
• A domain user account—The account must have Create Computer Objects and Read All Properties permissions in the domain.
• The desired cluster management name and cluster node names—The cluster node names are automatically derived from the cluster name, but they may be individually modified.
• A new local administrators password—The new password will be applied to both nodes for convenience of setup, but can be changed on either or both nodes at a later date. There is no requirement that the password be the same on both nodes.
Both nodes restart when you complete the wizard. After the restart, log in using a domain login account that has appropriate rights to manage and administer a failover cluster.
Prepare a Witness Disk
Preparing a witness disk requires that a new virtual disk and volume be created. If the virtual disk and volume
36 System Settings
disk, then create the volume to be used for the witness disk. Note that when a cluster is created, the smallest volume found that meets the witness disk requirements is used at the witness disk.
Create virtual disks for StoreVirtual file controller
Prerequisites
Clicking this link will open a IP Address pop-up which allows the user to enter the StoreVirtual IP address.
This will open the StoreVirtual web UI window which allows the user to create a StoreVirtual Storage array volume or volumes and export the same to the StoreVirtual File Controller or StoreVirtual File Controller cluster.
NOTE:
The StoreVirtual storage array volume consists of a logical entity made up of storage on one or more
StoreVirtual storage arrays. The StoreVirtual storage array volumes when exported will display as virtual disks on the StoreVirtual File Controller disk management interfaces.
Clicking this link opens the StoreVirtual Web UI window which allows the user to create volume and export the same to the StoreVirtual File Controller or StoreVirtual File Controller cluster.
Procedure
1. Click Create Virtual Disks for StoreVirtual File Controller in the Configure Cluster task group in the
ICT.
The StoreVirtual Web UI is displayed.
2. Enter the username and password to login and the StoreVirtual array window is displayed.
3. Select Volumes from the StoreVirtual drop-down menu to display the Volumes screen.
4. Click Create Volumes and the Create Volume window is displayed.
5. Specify the name for a volume.
Note: Name must be unique and 1 to 27 characters. Avoid spaces, equals, double quotes and semicolons.
6. Specify the volume size (the default size is 500 GiB).
7. Click Create to create the virtual disk.
Once the virtual disk is created, export the volume to allow the StoreVirtual File Controller(s) to utilize the volumes.
Exporting to StoreVirtual File Controller cluster
1. Click on the volume created.
2. Click +Export to StoreVirtual File Controller or Server cluster in the Exports menu.
The Export to Server or Server Cluster window opens.
3. Click on Server cluster button to export the storage to only one server. To export the storage to multiple server, click on Server Cluster button.
For more information on configuring the server or server cluster, refer to StoreVirtual Array manuals or online help.
4. Click Select to select the server or server cluster from the drop-down menu.
5. Select Read/Write in the Permissions drop-down menu assigned to this export.
6. Click Export to export virtual disk to a StoreVirtual File Controller server or cluster.
The volume is now exported to the server or server cluster and you have the option to either create and
the configuration of the storage.
Configuring HPE StoreVirtual 3000 File Controller
37
NOTE:
Any volumes that are present at the time that the StoreVirtual File Controller is configured for Failover
Clustering are added to the cluster storage.
Create Volume for StoreVirtual File Controller
Clicking this link opens the Disk Management Console window which allows the user to bring the exported virtual disk online and create a volume onto the virtual disk.
To bring Virtual disk online
1. Click Create Volumes in the Configure Clustertask group in the ICT.
The Disk Management Console window opens that displays the list of virtual disks created.
2. Click on the new virtual disk.
3. Click online to bring the virtual disk online.
The Virtual Disk Manager pop-up window appears.
4. Click OK.
Create Simple Volume
1. Right-click on the newly created volume to select New Simple Volume.
The New Simple Volume wizard appears.
2. Click Next to specify the volume size.
3. Click Next.
The Assign Drive Letter or Path screen appears
4. Click Assign the following drive letter radio button.
5. Click Next.
The Format Partition screen appears.
6. Click Format this volume with the following settings radio button to specify the settings.
The Completing the New Volume wizard appears.
7. Click Next.
8. Click Finish to close the wizard.
The requested resource is in use message appears.
9. Click OK.
Create New Spanned Volume
1. Right-click on the newly created volume to select New Spanned Volume.
The Welcome to the New Simple Volume wizard appears. Click Next.
2. Click Next.
The New Spanned Volume wizard opens.
3. In the Select Window screen, select the available disk to span through the virtual disk.
4. Click OK.
Validate and create the cluster
NOTE:
To perform this task, you must use a domain account that is a member of the local administrators group.
This task is enabled only when ICT can connect to the second node and neither node is part of a cluster.
38 Configuring HPE StoreVirtual 3000 File Controller
Procedure
1. Select Validate and Create cluster.
The Cluster Validation and Setup Wizard opens. The wizard preselects the two nodes as candidates for clustering.
2. Click Validate to begin the cluster validation, which may take several minutes.
3. When the validation completes, a View validation testing report link is provided. Click the link to view the report.
NOTE:
The following warning in the validation report is expected for each of the two nodes:
Category : Network : Validate IP Configuration Node <node name> has an IPv4 address 169.254.x.x configured as Automatic Private IP Address (APIPA) for adapter Cluster Internal. This adapter will not be added to the Windows
Failover Cluster. If the adapter is to be used by Windows Failover
Cluster, the IPv4 properties of the adapter should be changed to allow assignment of a valid IP address that is not in the APIPA range. APIPA uses the range of 169.254.0.1 thru 169.245.255.254 with subnet mask of
255.255.0.0.
This warning is due to the Cluster Internal network that is auto configured with an IPv4 address on each node. Despite the warning message, the adapter is added to the cluster as an internal network, so you can ignore this warning.
Other warnings are expected if you have not configured all network adapters. In this case, the warnings similar to the following are displayed:
Category : Network : Validate IP Configuration Adapters Server Management and 1 GbE Public 1 on node <node name> have IP addresses on the same subnet. This may be intentional, since both adapters are currently Not
Operational.
These warnings may also be ignored, or the warnings can be avoided altogether by disabling unused network adapters using the Control Panel.
4. Click Next after reviewing the validation report.
The Cluster Management Name window is displayed with the cluster name chosen in the Provide cluster name and domain ICT task.
5. Change the cluster management name, if necessary.
This name becomes the DNS name associated with the virtual IP addresses used to manage the cluster.
6. Enter the IP address, if it is needed for the network and then click Next.
If there are more volumes other than the Cluster Witness disk, the Highly Available File Server Name screen is displayed. If there are no additional volumes, the Review Settings and Create Failover Cluster screen is displayed.
7. If you want to create a new file server, change the file server name if necessary and click Next.
If you do not want to create a new file server, select the Do not create a new file server check box and click Next.
8. Review the settings on the Review Settings and Create Failover Cluster screen and then click Create when ready to create the cluster.
The process takes a few minutes and when complete the Confirmation screen is displayed indicating the failover cluster is created.
9. Click Close.
Configuring HPE StoreVirtual 3000 File Controller
39
Cluster Creation
Perform the following steps to validate and create a cluster:
Validating a cluster
Before you create a failover cluster, HPE strongly recommend 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. To validate a cluster:
Procedure
1. 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 from the Tools menu, select
Failover Cluster Manager.
2. In the Failover Cluster Manager pane, under Management, click Validate Configuration.
Figure 4: Failover Cluster Manager
3. On the Before You Begin page, click Next.
4. On the Select Servers or a Cluster page, enter the NetBIOS name or fully qualified domain name of a server that you plan to add as a failover cluster node and 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 semicolon.
For example, enter the names in the server1.contoso.com, server2.contoso.com format. When you are finished, click Next.
40 Configuring HPE StoreVirtual 3000 File Controller
Figure 5: Validate a Configuration Wizard
5. On the Testing Options page, click Run all tests (recommended), and then click Next.
6. On the Confirmation page, click Next.
The Validating page displays the status of the running tests.
7. On the Summary page, do either of the following:
a. 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.
b. 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 6: Validate a Configuration Wizard
Creating a cluster
Perform the following steps to create a cluster:
• Start Server Manager.
• From the Tools menu, select Failover Cluster Manager.
• In the Failover Cluster Manager pane, under Management, click Create Cluster.
• The Create Cluster Wizard opens.
Configuring HPE StoreVirtual 3000 File Controller
41
Figure 7: Failover Cluster Manager
• On the Before You Begin page, click Next.
• 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 8: Create Cluster Wizard
42 Configuring HPE StoreVirtual 3000 File Controller
Figure 9: Create Cluster Wizard—Select Servers
• If you skipped validation earlier, the Validation Warning page appears. HPE recommends that you run cluster validation. Only clusters that pass all validation tests are supported by Microsoft. To run the validation tests, click Yes, and then click Next. Complete the Validate a Configuration Wizard.
• On the Access Point for Administering the Cluster page, do the following:
◦ In the Cluster Name box, enter the name that you want to use to administer the cluster. Before you enter the name, review the following information:
– During cluster creation, this name is registered as the cluster computer object (also known as the cluster name object or CNO) in AD DS. If you specify a NetBIOS name for the cluster, the CNO is created in the same location where the computer objects for the cluster nodes reside. This can be either the default Computers container or an OU.
– To specify a different location for the CNO, you can enter the distinguished name of an OU in the
Cluster Name box. For example,
CN=ClusterName, OU=Clusters, DC=Contoso, DC=com.
– If a domain administrator has prestaged the CNO in a different OU than where the cluster nodes reside, specify the distinguished name that the domain administrator provides.
◦ If the server does not have a network adapter that is configured to use DHCP, you must configure one or more static IP addresses for the failover cluster. Select the check box next to each network that you want to use for cluster management. Click Address next to a selected network, and then enter the IP address that you want to assign to the cluster. This IP address (or addresses) will be associated with the cluster name in Domain Name System (DNS).
◦ When you are finished, click Next.
Configuring HPE StoreVirtual 3000 File Controller
43
Figure 10: Create Cluster Wizard—Access Point
• On the Confirmation page, review the settings. By default, the Add all eligible storage to the cluster check box is selected. Clear this check box if you want to do either of the following:
1. Configure storage later.
2. Create clustered storage spaces through Failover Cluster Manager or Failover Clustering Windows
PowerShell cmdlets, and have not yet created storage spaces in File and Storage Services.
Figure 11: Create Cluster Wizard—Confirmation
• Click Next to create the failover cluster.
• On the Summary page, confirm that the failover cluster is successfully created. If there were any warnings or errors, view the summary output or click View Report to view the full report. Click Finish.
44 Configuring HPE StoreVirtual 3000 File Controller
NOTE:
Category : Network : Validate IP Configuration Node <node name> has an
IPv4 address 169.254.x.x configured as Automatic Private IP Address
(APIPA)for adapter Cluster Internal. This adapter will not be added to the
Windows Failover Cluster. If the adapter is to be used by Windows Failover
Cluster, the IPv4 properties of the adapter should be changed to allow assignment of a valid IP address that is not in the APIPA range. APIPA uses the range of 169.254.0.1 through 169.245.255.254 with subnet mask of
255.255.0.0.
Other warnings are expected if you have not configured all network adapters. In this case, the warnings similar to the following are displayed: Category : Network : Validate IP
ConfigurationAdapters Server Management and 1 GbE Public 1 on node
<node_name> have IP addresses on the same subnet. This may be intentional, since both adapters are currently Not Operational.
These warnings may also be ignored or the warnings can be avoided altogether by disabling unused network adapters using the Control Panel.
These warning are due to the Cluster Internal network that is auto configured with an IPv4 address on each node. Despite the warning message, the adapter is added to the cluster as an internal network, so you can ignore this warning.
• To confirm that the cluster is created, verify that the cluster name is listed under Failover Cluster
Manager in the navigation tree. You can expand the cluster name, and then click items under Nodes,
Storage or Networks to view the associated resources.
Figure 12: Failover Cluster Manager
Protect This Cluster
Use Cluster-Aware Updating (CAU) to ensure that your server receives critical software updates and
enhancements directly from Windows Update. Additionally, you can get more information about Vision
Solution Double-Take Availability Information products that have special HPE customer pricing.
• Vision Solution Double-Take Availability Information
Protect This Cluster
45
Cluster-Aware Updating
Cluster-Aware Updating (CAU) is a reliable, automated, and integrated update feature that enables updating of clustered servers with little or no loss in availability during the update process.
During an update, CAU performs the following tasks:
• Puts each node of the cluster into node maintenance mode.
• Moves the clustered roles off the node.
• Installs the updates and any dependent updates.
• Performs a restart if necessary.
• Brings the node out of maintenance mode.
• Restores the clustered roles on the node.
• Moves to update the next node.
CAU can coordinate the complete cluster updating operation in two modes:
• Self-updating mode—The CAU clustered role is configured as a workload on the failover cluster that is to be updated, and an associated update schedule is defined. The cluster updates itself at scheduled times by using a default or custom Updating Run profile. During the Updating Run, the CAU Update Coordinator process starts on the node that currently owns the CAU clustered role, and the process sequentially performs updates on each cluster node. In self-updating mode, CAU can update the failover cluster by using a fully automated, end-to-end updating process. An administrator can also trigger updates ondemand in this mode, or simply use the remote-updating approach if desired. In self-updating mode, an administrator can get summary information about an Updating Run in progress by connecting to the cluster and running the Get-CauRun Windows PowerShell cmdlet.
• Remote-updating mode—A remote computer that is running Windows Storage Server 2016, which is called an Update Coordinator, is configured with the CAU tools. The Update Coordinator is not a member of the cluster that is updated during the Updating Run. From the remote computer, the administrator triggers an on-demand Updating Run by using a default or custom Updating Run profile. Remote-updating mode is useful for monitoring real-time progress during the Updating Run, and for clusters that are running on Server Core installations of Windows Storage Server 2016.
NOTE:
• Each cluster node must be configured to allow WinRM Remoting, which is enabled by default in
Windows Storage Server 2016.
• The Windows Update (WU) functionality on each node in the cluster must not be configured to autoupdate the cluster node. However, Hewlett Packard Enterprise recommends that you set WU to automatic download on the cluster nodes to minimize the time an Updating Run might take and to increase the odds that an Updating Run might complete within the planned IT maintenance window.
Alternatively, Cluster-Aware Updating still works even if you choose to disable the automatic download setting of the Windows Update functionality on each cluster node.
• Cluster Aware Updating works with both Microsoft update service and enterprise level Windows server update service (WSUS).
For more information about Cluster-Aware Updating, see the following Microsoft Technet article:
Cluster-Aware Updating overview
To use Cluster-Aware Updating:
1. In the Cluster-Aware Updating section, click Use Cluster-Aware Updating to help keep this cluster
secure and up-to-date.
The Cluster-Aware Updating screen is displayed.
2. Select the necessary options for cluster updates. For information on using the various screen options, see the CAU online help.
46 Cluster-Aware Updating
Enable automatic updating
Clicking this link opens the Update & security Settings page where users can confirm Update status and
Update settings. Click Change settings to select the way Windows updates are downloaded and installed.
Hewlett Packard Enterprise 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 administrator’s time. Features on the Windows Update dialog box are configurable by members of the administrators group on the local computer. All updates are downloaded and installed automatically and users can choose the system will reboot automatically when system is inactive or can be notified to schedule a reboot by opening Restart options.
Hewlett Packard Enterprise recommends the following for updates: Users can configure how updating
Microsoft products when Windows update takes place by opening Advanced options.
• Run Download and Install Updates immediately after system installation.
• Apply regular HPE StoreEasy Storage Service Releases.
Vision Solution Double-Take Availability Information
Vision Solutions offers replication products to address disaster recovery and high availability needs. Clicking this link 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.
Configuring failover properties for multi-site environments
You can configure failover properties for multi-site environments using DFS Management, which is available from the Tools menu in Windows Server Manager (Tools > DFS Management).
For detailed instructions, see the Microsoft TechNet article, DFS Step-by-Step Guide for Windows Server
2008, which is available at:
http://technet.microsoft.com/en-us/library/cc732863(v=ws.10).aspx
NOTE:
• The information in the article applies to Windows Storage Server 2012, Windows Storage Server
2012 R2 and Windows Storage Server 2016.
• The article provides instructions to configure both DFS Namespace and DFS Replication.
• The prerequisites listed in the article are already installed with the HPE StoreVirtual 3000 File
Controller.
• You can start at the section entitled, Overview of the DFS Management Snap-in.
Additional access methods
After the HPE StoreVirtual 3000 File Controller installation process is complete and the system's IP address has been assigned, you can additionally use the Remote Desktop and Telnet methods to access the system.
Using the Remote Desktop method
Remote Desktop provides the ability for you to log on to and remotely administer your server, giving you a method of managing it from any client. Installed for remote administration, Remote Desktop allows only two concurrent sessions. Leaving a session running takes up one license and can affect other users. If two sessions are running, additional users will be denied access.
To connect the HPE StoreVirtual 3000 File Controller system to a network using the Remote Desktop method:
Enable automatic updating
47
Procedure
1. On the PC client, select Start > Windows PowerShell. Type mstsc and press Enter.
2. Enter the IP address of the HPE StoreVirtual 3000 File Controller in the Computer box and click Connect.
3. Log on to the HPE StoreVirtual 3000 File Controller with the administrator user name and password.
Using the Telnet method
Telnet is a utility that enables you to connect to machines, log on, and obtain a command prompt remotely. By default, Telnet server is not installed.
48 Using the Telnet method
Managing HPE StoreVirtual 3000 File Controller
After you have completed the initial setup of the system using the ICT window, use Windows Server Manager to manage the system. The Server Manager is automatically launched when you close ICT. You can also launch Server Manager from the HPE StoreVirtual 3000 File Controller desktop by clicking the shortcut icon on the task bar. The local HPE StoreVirtual 3000 File Controller system as well as other Windows servers may be managed, as described in the Manage Multiple, Remote Servers with Server Manager article on
Microsoft TechNet.
Windows Server Manager can also be used for remote management of HPE StoreVirtual 3000 File Controller by installing it on a Windows 8\10 client as part of Remote Server Administration tools. To download the tools, go to Microsoft Download Center.
NOTE:
The Tools menu of Windows Server Manager is not applicable to a remote system under management.
It applies only to the local system.
Many storage related tasks are accomplished with the File and Storage Services option in Server Manager.
The Tools menu contains the common utilities familiar to Windows administrators. The Tools > StoreVirtual menu group contains HPE-specific management tools as well as some of the commonly used Windows tools related to managing a HPE StoreVirtual 3000 File Controller system. The Tools > StoreEasy menu contains the following options:
• Collect System Reports—Launches the data collection and diagnostic tool. Collect System Reports is a data collection and diagnostic tool. This tool collects extensive data about the state of the HPE StoreVirtual
3000 File Controller that is used by HPE Support to diagnose any problems. Data collection progress is shown, and when complete, Windows Explorer opens to the folder containing a time-stamped .cab archive with the collected information. The folder is C:\Windows\HPSReports\Enhanced\Report\cab. HPE
Support will provide an FTP site to which the .cab file may be uploaded.
• Configure Email Alerts—Launches the Event Notifier Configuration Wizard that enables you to configure the email recipients that should be notified of hardware events.
• Configure Networking—Launches the Network Configuration Tool.
• Documentation—Launches the online help.
• Evaluate Deduplication Savings—Launches the Windows ddpeval.exe tool which can be used to evaluate the storage space that would be saved by enabling deduplication on a particular volume.
• File Share Snapshots—Launches the Windows tool for scheduling and configuring storage for snapshots of a file share.
• iLO Settings—Launches the Lights-Out Online Configuration Utility.
• Register Product—Launches the HPE Product Registration page to register the product.
• Save reseller information—Launches theReseller Information Toolthat enables you to enter the reseller and purchasing information.
• View Logs—Opens the StoreEasy log directory.
Using the Network Configuration Tool
The NCT wizard enables you to configure the network interfaces on HPE StoreVirtual 3000 File Controller.
NCT analyzes all available network interfaces of the HPE StoreVirtual 3000 File Controller system and allows you to choose different network configurations to reduce the chances of any incorrect configuration. It also validates the configuration to help troubleshoot errors in the networking environment.
Managing HPE StoreVirtual 3000 File Controller
49
IMPORTANT:
HPE strongly recommends you to use this tool for configuring network interfaces.
You can also import the network configuration using the network configuration file. For more information on
the network configuration file, see Managing the network configuration file and Importing network
You can launch the NCT directly using the following methods:
• Open a command prompt or PowerShell and type NCT.
• Open Server Manager and select Tools > StoreVirtual > Configure Networking.
• Double-click the System Tools folder on the desktop and click Configure Networking.
• Click Configure Networking on the Start screen.
• Click the Configure Networking icon on the desktop.
The NCT is divided into two panes. When you launch NCT to configure network interfaces or validate the network configuration, the network configuration discovery is initiated. When the system discovery completes, the left pane or interface pane lists the discovered interfaces and their operational state. The right pane displays the current configuration step. Hovering over a network interface in the interface pane displays the device name, interface name, and status. For example, the interface might be disabled, disconnected, or enabled.
IMPORTANT:
While using NCT, if you change the network configuration of the system using any other tool, the changes are reflected in NCT only when you close and relaunch it.
50 Managing HPE StoreVirtual 3000 File Controller
The NCT wizard includes the following sections:
• Network Interface IP Configuration
• Network Configuration Summary
Network Interfaces
Network Interfaces enables you to configure the physical network interfaces to suit your environment.
To configure an interface:
Procedure
1. Select the Configure check box for the interface that you want to configure. If you clear the check box, the interface is excluded from all configurations and is not modified.
2. Enter the new interface name. The new name that you enter must not contain special characters, such as
\ /*? < >| and “.
3. Click Next to proceed to the Network Team Configuration step.
The physical network interfaces that are part of a team or used for RDP cannot be configured. For such interfaces, the Configure check box is disabled.
Network Team Configuration
Network adapter teaming is software-based technology used to increase a server's network availability and performance. Teaming enables the logical grouping of physical adapters in the same server (regardless of whether they are embedded devices or Peripheral Component Interconnect (PCI) adapters) into a virtual adapter. This virtual adapter is seen by the network and server-resident network-aware applications as a single network connection. For more information on Microsoft's implementation of Network Teaming, go to
https://technet.microsoft.com/en-us/library/hh831648.aspx.
Network Team Configuration enables you to configure new teams. Teaming is used to increase available bandwidth, load balancing, and improving fault tolerance. The maximum number of teams that you can create is equal to the number of physical network interfaces on the system. On clustered systems, the number of teams created on the local node is same as the number of teams created on the remote node. Team creation on the remote node is automatic.
NOTE:
• It is optional to configure a network team. If you do not want to create network teams, click Next to proceed to the Network VLAN configuration step. The Do not configure network teams now option is selected by default.
• The Network Team Configuration (optional) window is displayed only if there are no pre-existing teams.
To create network teams if there are no existing teams:
Procedure
1. Select Configure network teams now and enter the number of teams you want to create in Number of
teams
2. Click Next to proceed to the Network VLAN configuration step.
To create network teams in the case of existing teams:
Network Interfaces
51
1. Select the physical network interfaces on the Network Interfaces window and click Next.
2. Select the Create check box and do the following:
a. Enter the team name.
b. Select the team type from Type. The default selection is Switch Independent/Dynamic.
NOTE:
The number of teams displayed for configuration or deletion depends on the number of physical network interfaces that you select. For example, if you select two interfaces for configuration, two rows will appear for team creation.
3. Click Next.
The network interfaces that are not included in any team are displayed.
4. Select the network interfaces that you want to include in the new team.
5. Click Next to proceed to the Network VLAN configuration step.
The Network Team Configuration window also enables you to delete an existing team by selecting the
Delete check box. The Delete check box is enabled only if a team exists. When you delete an existing team, the physical network interface included in that team can be used for new teams.
NOTE: When a team is created, a default virtual network interface is also created. To remove the default virtual interface, assign one or more VLAN IDs on the Network VLAN Configuration window and select the remove the default virtual network interface check box.
While creating network teams, the interfaces claimed by one team cannot be added to any other team. The team that these interfaces belong to is displayed next to the interface name. If all adapters are already claimed by one or more teams, a warning message is displayed. You can either go back and remove some interfaces from the previously created teams or skip the creation of a team.
• If some of the physical network interfaces included in the team are disconnected while other interfaces are connected, the team status is displayed as degraded.
• If all physical network interfaces included in the team are disconnected, the team status is displayed as disconnected.
The network teams are displayed in the interface pane when you proceed to the IP Address Configuration step.
Use the network configuration tool to configuring network interfaces.
52 Managing HPE StoreVirtual 3000 File Controller
Network VLAN Configuration
NOTE: It is optional to configure VLAN assignments. If you choose not to configure VLAN assignments, only the default team interface is created. Click Next to skip this step and go to the IP Address
Configuration step.
Network VLAN Configuration enables you to configure VLAN assignments. The default VLAN ID is 0, but the
VLAN IDs can have a value from 0 to 4094. Each VLAN ID assigned to a physical network interface or network team creates a virtual network interface. Both physical and virtual interfaces created for network teams can have VLAN IDs assigned to them. If a physical interface is assigned a VLAN ID, a team is created with a single physical interface. A virtual interface with the VLAN ID is then created in the team.
To assign VLAN IDs:
Network VLAN Configuration
53
Procedure
1. Select the Configure VLAN IDs now and click Next.
2. Select one of the following options and enter the VLAN ID in the respective fields:
• Add a single VLAN ID—Select to add a single VLAN ID.
• Add discrete VLAN IDs—Select to add the VLAN IDs as comma separated values.
• Add a range of VLAN IDs—Select to specify the VLAN IDs using a start and end value with an increment. For example, a start value of 2 and an end value of 20 with an increment of 5 would assign
VLAN IDs 2, 7, 12, and 17.
3. Select the Remove the default virtual network interface check box to remove the default virtual interface from a team. This step is optional.
NOTE:
If a default virtual interface is deleted, the system will not receive any packets on the team or physical NIC unless you assign one or more VLAN IDs.
4. Click Next to proceed to the Network Interface IP Configuration step.
The VLAN assignments are displayed in the interface pane when you proceed to the Network Interface IP
Configuration step.
NOTE: If you select Do not configure network interface VLAN identifiers now after you assign
VLAN IDs to teams and adapters, the assigned IDs are not removed. You must go through each VLAN page and select the Do not add a VLAN ID to this team implicitly for all teams and adapters.
Network Configuration Summary
Network Configuration Summary enables you to view a summary of all configuration changes that will take place on the system. Before proceeding, confirm that the changes are appropriate. If some configurations are not required or not valid, click Previous or use the navigation links at the bottom of the page to correct the errors. To apply the configuration changes, click Apply. When you apply the changes and click Next, the details of each task configured is displayed. If some errors are encountered when the changes are applied, the same are displayed on the Errors tab.
When you apply the configuration changes, the system automatically creates and saves the network configuration file (NCTConfig.xml) at C:\Program Files\HPE\StoreEasy NetworkConfiguration
Wizard. This file includes the network configuration details. Only a user who is a member of the local administrator group can modify the contents of this file. The system creates the NCTConfig.xml file depending on the sequence in which the NCT wizard completes the network configuration tasks successfully.
For example, if the physical network interface configuration is successful, but the creation of teams or VLANs fails, then the NCTConfig.xml file is created with only the physical network interfaces listed in the file. The
VLANs and teams are not listed. This is because in this case, the NCT wizard successfully completed the network interface task, even though the other tasks were unsuccessful. However, if the physical network interface task fails, then the NCTConfig.xml file is not created at all because the validation failed at the first task. When the file is created successfully, you can use it to import the configuration from one server to another.
Important considerations while working with the NCTConfig.xml file are:
• Do not rename the XML tags in the file. Renaming the tags might lead to errors while applying the configuration.
• Do not rename the NCTConfig.xml file.
• Do not edit the contents of the PciKey tag. Editing this tag causes errors.
54 Network Configuration Summary
• You can edit only specific XML tags, such as, Name, AdapterIPConfiguration, and
AdapterHWInformation.
• If the NCTConfig.xml file is corrupt or the tags are invalid, a message is displayed on the screen indicating the same. You cannot reuse the same file. In such cases, NCT uses the system discovery state for further configurations.
For more information on importing the network configuration, see Importing network configuration.
Network Interface IP Configuration
Network Interface enables you to begin the IP address configuration by selecting the interface on which you want to make changes using the interface pane. Each interface that can be configured is enabled on the system, even if no changes are made to the interface. The IP addresses that you assign can be static or dynamically assigned using DHCP.
To configure the IP information for an interface:
Network Interface IP Configuration
55
Procedure
1. Select Use DHCP to assign IP address and gateway to dynamically assign an IP address using DHCP or select Assign a static IP address and gateway to assign a static IP address.
IMPORTANT:
If you select Assign a static IP address and gateway, the DNS server address must also be static and you must also assign a network mask. Assigning a default gateway address is optional.
2. Select Use DHCP to assign DNS server addresses or Assign a static IP address and gateway. If you selected the Assign a static IP address and gateway option in the above step, the Assign a static IP
addresses for DNS option is selected by default and you cannot change it.
3. Click Next to proceed to the Network Configuration Summary step.
IMPORTANT:
HPE recommends that you check each interface before clicking Next on this window.
56 Managing HPE StoreVirtual 3000 File Controller
The network defined by the IP address and subnet mask is used to validate the gateway, if one is specified. If an interface is assigned a static address, its configuration is validated against other interface settings when a different interface is selected or when you click Next.
Network Validation
Network Validation enables you to validate and configure the network settings. Network validation requires that all network interfaces that you want to test be connected.
NOTE:
• It is optional to validate the network settings. However, HPE recommends using the network validation system to confirm that your network settings are valid and to help diagnose environmental network issues.
• You can launch only the Network Validation section of NCT by executing the NCT -validate command in a command prompt or PowerShell.
To begin network validation:
Procedure
1. Select Validate the network configuration now.
2. Enter the name of the domain controller for the domain that your system will be a part of and IP address of the domain controller in the respective fields. If you do not want to join the system to a domain, you can leave these fields blank.
3. Click Validate.
Network Validation
57
When the validation begins, the user interface may seem unresponsive. Each interface is tested in order and validation success or failure is noted in the output window. Validation results are also saved at c:\nas\logs
\NetworkConfigTool. Each validation result is saved in a file named with the time and date the validation was performed.
Managing the network configuration file
The NCTConfig.xml file is created when you apply the network configuration changes by clicking Apply on the Network Configuration Summary window. This file includes the network configuration details. Only a user who is a member of the local administrator group can modify the contents of this file. The system creates the NCTConfig.xml file depending on the sequence in which the NCT wizard completes the network configuration tasks successfully. For example, if the physical network interface configuration is successful, but the creation of teams or VLANs fails, then the NCTConfig.xml file is created with only the physical network interfaces listed in the file. The VLANs and teams are not listed. This is because in this case, the NCT wizard successfully completed the network interface task, even though the other tasks were unsuccessful. However, if the physical network interface task fails, then the NCTConfig.xml file is not created at all because the validation failed at the first task. When the file is created successfully, you can use it to import the configuration from one server to another. Important considerations while working with the NCTConfig.xml
file are:
• Do not rename the XML tags in the file. Renaming the tags might lead to errors while applying the configuration.
• Do not rename the NCTConfig.xml file.
• Do not edit the contents of the PciKey tag. Editing this tag causes errors.
• If the NCTConfig.xml file is corrupt or the tags are invalid, a message is displayed on the screen indicating the same. You cannot reuse the same file. In such cases, NCT uses the system discovery state for further configurations.
Sample network configuration file
<?xml version="1.0" encoding="utf-8"?>
<!--This XML file has been generated by the Network Configuration Tool after successful application of user settings-->
<!--Created - 10 Wed Dec 2014 04:50-->
<NetworkConfigurationTool>
<SystemSerialNumber-2M23330589>
<Interfaces>
<Interface ifIndex="16">
<Name>Ethernet 41</Name>
<Description>HP Ethernet 1Gb 4-port 331FLR Adapter #4</Description>
<IsMediaConnected>false</IsMediaConnected>
<IsNetEnabled>false</IsNetEnabled>
<AdapterHWInformation>
<BindingOrder>0</BindingOrder>
<Bus>3</Bus>
<Device>0</Device>
<Function>3</Function>
<InstanceID>{DABD5F10-C2A9-40ED-9701-F4EEE1FE6B60}</InstanceID>
<PciKey>3:0:3</PciKey>
</AdapterHWInformation>
<AdapterIPConfiguration>
<DefaultGateway>16.78.88.1</DefaultGateway>
<DHCPEnabled>false</DHCPEnabled>
<IPAddress>16.78.88.20</IPAddress>
<PrimaryDNS></PrimaryDNS>
<SecondaryDNS></SecondaryDNS>
58 Managing the network configuration file
<TertiaryDNS></TertiaryDNS>
<StaticEnabled>true</StaticEnabled>
<SubnetMask>255.255.248.0</SubnetMask>
<IsDHCPDNS>false</IsDHCPDNS>
<IsDHCPIP>false</IsDHCPIP>
<IsStaticDNS>true</IsStaticDNS>
<IsStaticIP>true</IsStaticIP>
</AdapterIPConfiguration>
<DNSDomainName></DNSDomainName>
<IsAvailableforTeam>true</IsAvailableforTeam>
<IsMemberofTeam>false</IsMemberofTeam>
<IsLocal>true</IsLocal
<IsVirtualLAN>false</IsVirtualLAN>
</Interface>
<Teams>
<Team>
<Name>Team1</Name>
<TeamingMode>SwitchIndependent</TeamingMode>
<LoadBalancingAlgorithm>Dynamic</LoadBalancingAlgorithm>
<TeamStatus>Down</TeamStatus>
<IsLocal>false</IsLocal>
<VLANforTeam>
<DefaultVLAN></DefaultVLAN>
<DiscreteVLAN/>
<SingleVLAN>45</SingleVLAN>
<StepVLANRange></StepVLANRange>
<IsProperStep>true</IsProperStep>
<RangeVLAN/>
<UpperRangeLimit></UpperRangeLimit>
<LowerRangeLimit></LowerRangeLimit>
<VLANType>SingleVLAN</VLANType>
<VLANIDs>
<VLANID>45</VLANID>
</VLANIDs>
<CanMoveForward>true</CanMoveForward>
</VLANforTeam>
<TeamMembers>
<TeamMember>Ethernet 3</TeamMember>
</TeamMembers>
</Team>
</Teams>
</SystemSerialNumber-2M23330589>
</NetworkConfigurationTool>
In the NCTConfig.xml file, you can edit only the following tags:
• <Name>—Contains the physical network interface name.
• <AdapterHWInformation>—Contains the hardware information of the physical network interface. You can edit all subtags within this tag, such as <BindingOrder>, <Bus>, <Device>, and so on. However, you cannot edit the <PciKey> tag.
• <AdapterIPConfiguration>—Contains the IP configuration of the network interface. You can edit all subtags within this tag, such as <DefaultGateway>, <DHCPEnabled>, <IPAddress>, and so on.
The following table describes the sample values for these tags:
Managing HPE StoreVirtual 3000 File Controller
59
Tag
<Name>
<DHCPEnabled>
<IsDHCPIP> and <IsDHCPDNS>
<StaticEnabled>
<IsStaticIP> and
<IsStaticDNS>
<IPAddress>
<SubnetMask>
<DefaultGateway>
<PrimaryDNS>
<SecondaryDNS>
<TertiaryDNS>
Sample value
Ethernet 3, 1 GbE Public 1, and so on.
true or false.
• If DHCPEnabled is set to true, the value in this tag must be set to true.
• If DHCPEnabled is set to false, the value in this tag must be set to false.
true or false.
• If StaticEnabled is set to true, the value in this tag must be set to true.
• If StaticEnabled is set to false, the value in this tag must be set to false.
16.78.90.32, 10.1.2.21, 128.90.34.123, and so on.
255.255.248.0,255.255.0.0, and so on.
16.78.88.1, 128.90.34.21, and so on.
16.78.22.12, 128.89.23.12, and so on.
16.78.22.12, 128.89.23.12, and so on.
16.78.22.12, 128.89.23.12, and so on.
IMPORTANT:
• If the DHCPEnabled or StaticEnabled tags are modified, the values in the IsDHCPIP,
IsDHCPDNS, IsStaticIP, and IsStaticDNS tags must be changed accordingly.
• If the StaticEnabled, IsStaticIP, and IsStaticDNS tags are set to True and no values are specified for IPAddress, SubnetMask, and PrimaryDNS, the setting of the IP configuration fails.
• The StaticEnabled and DHCPEnabled tags cannot be set to true at the same time.
Importing network configuration
The NCTConfig.xml file enables you to directly import the network configuration settings from one server to another and apply the network configuration settings for all adapters at one instance. After successfully importing the settings, when you relaunch NCT, a confirmation message is displayed indicating if you want to use the last used network configuration settings. If you click Yes, the NCT wizard loads the network configuration details from the NCTConfig.xml file and displays the existing interface details along with the team details. You can reconfigure the desired network interface from the available interfaces and create new teams or delete existing teams.
IMPORTANT:
While changing the interface name, you must change only the prefix associated with the default VLAN.
For example, if the complete interface name isEthernet 2 Team –VLAN Default, then you must change only the prefix, that is, Ethernet 2 Team. The default VLAN name, which is VLAN Default in this example, must not be changed.
To import the network configuration settings from the NCTConfig.xml file:
60 Importing network configuration
Procedure
1. Open the NCTConfig.xml file and edit the IP configuration of the adapter in the
<AdapterIPConfiguration> tag.
2. Edit the interface name, if required.
3. Save the file and copy it to C:\Program Files\HPE\StoreEasy NetworkConfiguration Wizard on the server on which you want to import the configuration.
4. Launch NCT and when prompted, click Yes to use the last saved configuration.
The NCT wizard loads and displays the configuration details from the NCTConfig.xml file.
5. Click Next when the discovery completes.
6. Make required network configuration changes on the respective windows.
7. Click Apply on the Network Configuration Summary window to apply the changes.
8. Click Validate on the Network Configuration Validation window to validate the changes.
If the XML file import is unsuccessful, it could be due to one of the following reasons:
• The file is corrupt.
• The number of adapters in the XML file and the number of adapters on the system on which you want to import the file do not match.
• The file name is different fromNCTConfig.xml.
• The file is copied to a different location or folder.
• The XML tags other than the ones you can edit are edited.
Managing HPE StoreVirtual 3000 File Controller
61
Administration tools
HPE StoreVirtual 3000 File Controller systems include several administration tools to simplify storage system management tasks.
Microsoft Windows Storage Server 2016 administration tools
Microsoft Windows Storage Server 2016 operating systems provide a user interface for initial server configuration, unified storage system management, simplified setup and management of storage and shared folders, and iSCSI targets. It is specially tuned to provide optimal performance for network-attached storage.
Windows Storage Server 2016 provides significant enhancements in share and storage management scenarios, as well as integration of storage system management components and functionality.
Remote Administration
The following tools are available for remote management of the system:
• Remote Desktop
• Server Manager on a Windows 8\10 client via RSAT tools
• Remote PowerShell
File and Storage Services
File and Storage Services includes technologies that help you set up and manage one or more file servers, which are servers that provide central locations on your network where you can store files and share them with users. If users need access to the same files and applications, or if centralized backup and file management are important to your organization, you should set up one or more servers as a file server by installing the File and Storage Services role and the appropriate role services.
Administrators can use the File and Storage Services role to setup and manage multiple file servers and their storage by using Server Manager or Windows PowerShell. Some of the specific applications include the following:
• Use Data deduplication to reduce the disk space requirements of your files, saving money on storage.
• Use iSCSI Target Server to create centralized, software-based, and hardware-independent iSCSI disk subsystems in storage area networks (SANs).
• Use Server Manager to remotely manage multiple file servers from a single window.
• Use Windows PowerShell to automate the management of the majority of administration tasks for file servers.
For more information, see the Windows Storage Server 2016 Help.
Data Deduplication
Data deduplication involves finding and removing duplication within data without compromising its fidelity or integrity. The goal is to store more data in less space by segmenting files into small variable-sized chunks
(32–128 KB), identifying duplicate chunks, and maintaining a single copy of each chunk. Redundant copies of the chunk are replaced by a reference to the single copy. The chunks are compressed and then organized into special container files in the System Volume Information folder.
After a volume is enabled for deduplication and the data is optimized, the volume contains the following:
62 Administration tools
Procedure
1. Unoptimized files —For example, unoptimized files could include files that do not meet the selected fileage policy setting, system state files, alternate data streams, encrypted files, files with extended attributes, files smaller than 32 KB, other reparse point files, or files in use by other applications.
2. Optimized files—Files that are stored as reparse points that contain pointers to a map of the respective chunks in the chunk store that are needed to restore the file when it is requested.
3. Chunk store—Location for the optimized file data.
4. Additional free space—The optimized files and chunk store occupy much less space than they did prior to optimization.
To enable data deduplication on a volume:
1. Open Windows Server Manager.
2. Select File and Storage Services and then select Volumes.
3. Right-click a data volume and select Configure Data Deduplication.
The Deduplication Settings window is displayed.
4. Do the following:
a. Select the workload for the volume.
b. Enter the number of days that should pass between file creation and when files are deduplicated.
c. Identify any file type extensions that should not be deduplicated.
d. Click Add to browse to any folders containing files that should not be deduplicated.
5. Click Apply to apply these settings or click Set Deduplication Schedule to configure a deduplication schedule.
For more information, see the Windows Storage Server 2016 Help.
Print Management
Use Print Management to view and manage printers and print servers in your organization. You can use Print
Management from any computer running Windows Storage Server 2016 and you can manage all network printers on print servers running Windows Storage Server 2008, Windows Storage Server 2008 R2, Windows
Storage Server 2012, or Windows Storage Server 2012 R2.
Print Management provides details such as the queue status, printer name, driver name, and server name.
You can also set custom views by using the Print Management filtering capability. For example, you can create a view that displays only printers in a particular error state. You can also configure Print Management to send e-mail notifications or run scripts when a printer or print server needs attention. The filtering capability also allows you to bulk edit print jobs, such as canceling all print jobs at once. You can also delete multiple printers at the same time.
Administrators can install printers remotely by using the automatic detection feature, which finds and installs printers on the local subnet to the local print server. Administrators can log on remotely to a server at a branch location, and then install printers remotely.
For more information, see the Windows Storage Server 2016 Help.
Network File System User Mapping
NFS (Network File System) is a network file sharing protocol that allows remote access to files over a network and is typically used in networks with computers running UNIX, Linux, or Mac OS operating systems. NFS is supported on all HPE StoreVirtual 3000 File Controller systems.
The following types of NFS account mapping are supported:
• Active Directory
®
Domain Services (AD DS) mapped user access
• Unmapped anonymous user access
• Unmapped UNIX user access
Print Management
63
For more information about NFS, see the following Microsoft website:
The Storage Team at Microsoft – File Cabinet Blog
64 Administration tools
Storage management overview
This chapter provides an overview of some of the components that make up the storage structure of HPE
StoreVirtual 3000 File Controller.
Storage management elements
Storage is divided into four major elements:
• Physical storage elements
• Logical storage elements
• File system elements
• File sharing elements
Each of these element is composed of the previous level's elements.
Storage management example
Storage management process example depicts many of the storage elements that one would find on HPE
StoreVirtual 3000 File Controller. The following sections provide an overview of the storage elements.
Storage management overview
65
Figure 13: Storage management process example
Physical storage elements
The lowest level of storage management occurs at the physical drive level. Choosing the best physical disk configuration requires understanding the following:
• Current corporate and departmental structure
• Current file server structure and environment
• Best configuration and use of storage
66 Physical storage elements
◦ Determine the desired priority of fault tolerance, performance, and storage capacity.
◦ Use the determined priority of system characteristics to determine the optimal striping policy and RAID level.
• Include the appropriate number of physical drives in the arrays to create logical storage elements of desired sizes.
Arrays
capacity of several physical drives (P1–P3) can be logically combined into one or more logical units (L1) called arrays. When this is done, the read/write heads of all the constituent physical drives are active simultaneously, dramatically reducing the overall time required for data transfer.
NOTE:
Depending on the HPE StoreVirtual 3000 File Controller model, array configuration may not be possible or necessary.
Figure 14: Configuring arrays from physical drives
Because the read/write heads are simultaneously active, the same amount of data is written to each drive during any given time interval. Each unit of data is termed a block. The blocks form a set of data stripes over
all the hard drives in an array, as shown in RAID 0 (data striping) (S1-S4) of data blocks (B1-B12).
Figure 15: RAID 0 (data striping) (S1-S4) of data blocks (B1-B12)
For data in the array to be readable, the data block sequence within each stripe must be the same. This sequencing process is performed by the Smart Array controller, which sends the data blocks to the drive write heads in the correct order.
A natural consequence of the striping process is that each hard drive in a given array contains the same number of data blocks.
NOTE:
If one hard drive has a larger capacity than other hard drives in the same array, the extra capacity is wasted because it cannot be used by the array.
Arrays
67
Fault tolerance
in the same array, and hence to data loss.
To protect against data loss from hard drive failure, HPE StoreVirtual 3000 File Controller must be configured with fault tolerance.
The table below summarizes the important features of the different kinds of RAID supported by the Smart
Array controllers. The decision chart in the following table can help determine which option is best for different situations.
Table 4: Summary of RAID methods
Maximum number of hard drives
RAID 0
Striping (no fault tolerance)
N/A
RAID 1+0
Mirroring
N/A
Yes
RAID 5
Distributed
Data
Guarding
14
Yes
RAID 6
(ADG)
RAID 50 RAID 60
Storage system dependent
14
Yes Yes
Storage system dependent
Yes Tolerant of single hard drive failure?
No
Tolerant of multiple simultaneous hard drive failures?
No If the failed drives are not mirrored to each other
No Yes (two drives can fail)
No Yes (Two drives can fail)
Online spares
Further protection against data loss can be achieved by assigning an online spare (or hot spare) to any configuration except RAID 0. This hard drive contains no data and is contained within the same storage subsystem as the other drives in the array. When a hard drive in the array fails, the controller can then automatically rebuild information that was originally on the failed drive onto the online spare. This quickly restores the system to full RAID level fault tolerance protection. However, unless RAID Advanced Data
Guarding (ADG) is being used, which can support two drive failures in an array, in the unlikely event that a third drive in the array should fail while data is being rewritten to the spare, the logical drive still fails.
Logical storage elements
Logical storage elements consist of those components that translate the physical storage elements to file system elements. The HPE StoreVirtual 3000 File Controller uses the Window Disk Management utility to manage the various types of disks presented to the file system. There are two types of LUN presentation: basic disk and dynamic disk. Each of these types of disk has special features that enable different types of management.
Logical drives (LUNs)
While an array is a physical grouping of hard drives, a logical drive consists of components that translate physical storage elements into file system elements. A LUN may also be referred to as a virtual disk.
68 Fault tolerance
It is important to note that a LUN may span all physical drives within a storage controller subsystem, but cannot span multiple storage controller subsystems. The multiple storage controller subsystems could indicate multiple controllers or external enclosures.
Figure 16: Two arrays (A1, A2) and five logical drives (L1 through L5) spread over five physical drives
NOTE:
This type of configuration may not apply to all HPE StoreVirtual 3000 File Controller systems and serves only as an example.
Through the use of basic disks, you can create primary partitions or extended partitions. Partitions can only encompass one LUN. Through the use of dynamic disks, you can create volumes that span multiple LUNs.
You can use the Windows Disk Management utility to convert basic disks to dynamic disks or dynamic disks to basic disks and to manage the volumes residing on dynamic disks. Other options include the ability to delete, extend, mirror, and repair these elements.
Partitions
Partitions exist as either primary partitions or extended partitions. The master boot record (MBR) disk partitioning style supports volumes up to 2 terabytes in size and up to 4 primary partitions per disk (or three primary partitions, one extended partition, and unlimited logical drives). Extended partitions allow the user to create multiple logical drives. These partitions or logical disks can be assigned drive letters or be used as mount points on existing disks. If mount points are used, it should be noted that Services for UNIX (SFU) does not support mount points at this time. The use of mount points in conjunction with NFS shares is not supported.
The GUID partition table (GPT) disk partitioning style supports volumes up to 18 exabytes in size and up to
128 partitions per disk. Unlike MBR partitioned disks, data critical to platform operation is located in partitions instead of unpartitioned or hidden sectors. In addition, GPT partitioned disks have redundant primary and backup partition tables for improved partition data structure integrity.
On the Volumes tab in the disk properties dialog box in Disk Management, disks with the GPT partitioning style are displayed as GUID Partition Table (GPT) disks, and disks with the MBR partitioning style are displayed as Master Boot Record (MBR) disks.
Volumes
When planning volumes, you must consider the limitations of the file system that you choose for formatting the volumes. The default file system for Windows 2016 is NTFS.
The operating system supports FAT32, FAT, NTFS, and Resilient File System (ReFS). All file system types can be used on the HPE StoreVirtual 3000 File Controller system. However, VSS can only use volumes that are NTFS formatted. Also, quota management is possible only on NTFS.
NTFS enables you to create an NTFS volume up to 16 TB using the default cluster size (4KB) for large volumes. You can create NTFS volumes up to 256 TB using the maximum cluster size of 64 KB. The formula for the maximum NTFS volume size is ([2 ^32 * cluster size] —64KB) for Windows 2016. Starting Windows
2012, Microsoft introduced ReFS which works well with large data sets without performance impact. ReFS is not only designed to support volume sizes of 2^64 bytes (allowed by Windows stack addresses), but it also supports larger volume sizes of up to 2^78 bytes using 16 KB cluster sizes. This format also supports 2^64-1
Partitions
69
byte file sizes, 2^64 files in a directory, and the same number of directories in a volume. For more information on ReFS, seehttps://technet.microsoft.com/en-us/library/hh831724.aspx..
The RAID level of the LUNs included in a volume must be considered. All of the units that make up a volume should have the same high-availability characteristics. In other words, the units should all be of the same
RAID level. For example, it would not be a good practice to include both a RAID 1+0 and a RAID 5 array in the same volume set. By keeping all the units the same, the entire volume retains the same performance and high-availability characteristics, making managing and maintaining the volume much easier. If a dynamic disk goes offline, the entire volume dependent on the one or more dynamic disks is unavailable. There could be a potential for data loss depending on the nature of the failed LUN.
Volumes are created out of the dynamic disks, and can be expanded on the fly to extend over multiple dynamic disks if they are spanned volumes. However, after a type of volume is selected, it cannot be altered.
For example, a spanning volume cannot be altered to a mirrored volume without deleting and recreating the volume, unless it is a simple volume. Simple volumes can be mirrored or converted to spanned volumes.
Fault-tolerant disks cannot be extended. Therefore, selection of the volume type is important. The same performance characteristics on numbers of reads and writes apply when using fault-tolerant configurations, as is the case with controller-based RAID. These volumes can also be assigned drive letters or be mounted as mount points off existing drive letters.
The administrator should carefully consider how the volumes will be carved up and what groups or applications will be using them. For example, putting several storage-intensive applications or groups into the same dynamic disk set would not be efficient. These applications or groups would be better served by being divided up into separate dynamic disks, which could then grow as their space requirements increased, within the allowable growth limits.
File system elements
File system elements are composed of the folders and subfolders that are created under each logical storage element (partitions, logical disks, and volumes). Folders are used to further subdivide the available file system, providing another level of granularity for management of the information space. Each of these folders can contain separate permissions and share names that can be used for network access. Folders can be created for individual users, groups, projects, and so on.
File sharing elements
The HPE StoreVirtual 3000 File Controller system supports several file sharing protocols, including Network
File System (NFS), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), and Microsoft Server
Message Block (SMB). On each folder or logical storage element, different file sharing protocols can be enabled using specific network names for access across a network to a variety of clients. Permissions can then be granted to those shares based on users or groups of users in each of the file sharing protocols.
Volume Shadow Copy Service overview
The Volume Shadow Copy Service (VSS) provides an infrastructure for creating point-in-time snapshots
(shadow copies) of volumes. VSS supports 64 shadow copies per volume.
Shadow Copies of Shared Folders resides within this infrastructure, and helps alleviate data loss by creating shadow copies of files or folders that are stored on network file shares at pre-determined time intervals. In essence, a shadow copy is a previous version of the file or folder at a specific point in time.
By using shadow copies, the HPE StoreVirtual 3000 File Controller system can maintain a set of previous versions of all files on the selected volumes. End users access the file or folder by using a separate client add-on program, which enables them to view the file in Windows Explorer.
Shadow copies must not replace the current backup, archive, or business recovery system, but they can help to simplify restore procedures. For example, shadow copies cannot protect against data loss due to media failures; however, recovering data from shadow copies can reduce the number of times needed to restore data from tape.
70 File system elements
Using storage elements
The last step in creating the element is determining its drive letter or mount point and formatting the element.
Each element created can exist as a drive letter, assuming one is available, and/or as mount points on an existing folder or drive letter. Either method is supported. However, mount points cannot be used for shares that will be shared using Microsoft Services for Unix. They can be set up with both but the use of the mount point in conjunction with NFS shares causes instability with the NFS shares.
Clustered server elements
HPE StoreVirtual 3000 File Controller systems supports clustering. These storage systems support several file sharing protocols including DFS, NFS, FTP, HTTP, and Microsoft SMB. Only NFS, FTP, and Microsoft
SMB are cluster-aware protocols. HTTP can be installed on each node but the protocols cannot be set up through cluster administrator, and they will not fail over during a node failure.
Network names and IP address resources for the clustered file share resource can also be established for access across a network to a variety of clients. Permissions can then be granted to those shares based on users or groups of users in each of the file sharing protocols.
Using storage elements
71
File server management
This chapter describes the tasks and utilities that play a role in file server management.
File services management
Information about the HPE StoreVirtual 3000 File Controller system in a SAN environment is provided in the
SAN Design Reference Guide, located on the HPE web site at www.hp.com/go/SDGmanuals.
Storage management utilities
The storage management utilities preinstalled on the HPE StoreVirtual 3000 File Controller system include the Smart Storage Administrator (SSA) .
Array management utilities
Storage devices for RAID arrays and LUNs are created and managed using the array management utilities mentioned previously. For Smart Arrays, use SSA.
NOTE:
The SSA is used to configure and manage array-based storage. Software RAID-based HPE StoreVirtual
3000 File Controller systems use Microsoft Disk Manager to manage storage. You need administrator or root privileges to run the SSA.
Smart Storage Administrator
The SSA supports the Smart Array controllers and hard drives installed on the HPE StoreVirtual 3000 File
Controller system.
To open SSA from the HPE StoreVirtual 3000 File Controller desktop:
NOTE: If this is the first time you are running SSA, you will be prompted to select the Execution Mode for SSA. Selecting Local Application Mode allows you to run the SSA from a Remote Desktop, remote console, or HPE StoreVirtual 3000 File Controller web access mode. Remote service mode allows you to access the SSA from a remote browser.
Procedure
1. Click Start and then scroll down to System Tools. Select System Tools > Smart Storage Administrator.
2. If the Execution Mode for SSA is set to Remote Service Mode, log on to the HP System Management
Homepage. The default user name is Administrator and the password is the Windows Storage Server
2016 administrator password that is set by the HPE StoreVirtual 3000 File Controller system administrator.
The password is case-sensitive. To open the SSA in browser mode:
To open the SSA in browser mode:
NOTE: Confirm that the SSA Execution Mode is set to Remote Service Mode.
1. Open a browser and enter the server name or IP address of the destination server. For example, http:// servername:2301 or http://192.0.0.1:2301.
2. Log on to the HPW System Management Homepage. The default user name is Administrator and the default password is the password that you created while initially setting up the server.
3. Click Smart Storage Administrator on the left side of the window. The SSA opens and identifies the controllers that are connected to the system.
72 File server management
The HP Smart Storage Administrator User Guide is available for download at http://www.hpe.com/support/
manuals.
Disk Management utility
The Disk Management tool is a system utility for managing hard disks and the volumes, or partitions, that they contain. Disk Management is used to initialize disks, create volumes, format volumes with the FAT, FAT32, or
NTFS file systems, and create fault-tolerant disk systems. Most disk-related tasks can be performed in Disk
Management without restarting the system or interrupting users. Most configuration changes take effect immediately. A complete online help facility is provided with the Disk Management utility for assistance in using the product.
NOTE:
• When the Disk Management utility is accessed through a Remote Desktop connection, this connection can only be used to manage disks and volumes on the server. Using the Remote
Desktop connection for other operations during an open session closes the session.
• When closing Disk Management through a Remote Desktop connection, it may take a few moments for the remote session to log off.
Guidelines for managing disks and volumes
• A single logical drive is configured for the HPE StoreVirtual 3000 File Controller operating system and should not be altered in any manner. This is a reserved volume and must be maintained as it exists.
• HPE does not recommend spanning array controllers with dynamic volumes. The use of software RAIDbased dynamic volumes is not recommended. The hardware-based RAID configuration capabilities of the smart array controllers should be utilized due to being more efficient than software-based RAID configurations.
• Use meaningful volume labels with the intended drive letter embedded in the volume label, if possible. (For example, volume e: might be named “Disk E:.”) Volume labels often serve as the only means of identification.
• Record all volume labels and drive letters in case the system needs to be restored.
• When managing basic disks, only the last partition on the disk can be extended unless the disk is changed to dynamic.
• Basic disks can be converted to dynamic, but cannot be converted back to basic without deleting all data on the disk.
• Basic disks can contain up to four primary partitions (or three primary partitions and one extended partition).
• Format drives with a 16 K allocation size for best support of shadow copies, performance, and defragmentation.
• NTFS formatted drives are recommended because they provide the greatest level of support for deduplication shadow copies, encryption, and compression.
• The size of the NTFS volumes should be limited to 64TB or smaller in size if you are wanting to use Deduplication or Volume Shadow Copy Server (VSS). De-duplication and VSS do not support volumes larger than 64TB volumes. Also, writable snapshots or snapshots larger than 64 TB are not supported.
• Basic disks that are larger than 2TB should be formatted in GUID partition table (GPT) style.
• For further information refer to the Disk Management help found in the utility.
Scheduling defragmentation
Defragmentation is the process of analyzing local volumes and consolidating fragmented files and folders so that each occupies a single, contiguous space on the volume. This improves file system performance.
Because defragmentation consolidates files and folders, it also consolidates the free space on a volume. This reduces the likelihood that new files will be fragmented.
Disk Management utility
73
Defragmentation for a volume can be scheduled to occur automatically at convenient times. Defragmentation can also be done once, or on a recurring basis.
NOTE:
Scheduling defragmentation to run no later than a specific time prevents the defragmentation process from running later than that time. If the defragmentation process is running when the time is reached, the process is stopped. This setting is useful to ensure that the defragmentation process ends before the demand for server access is likely to increase.
If defragmenting volumes on which shadow copies are enabled, use a cluster (or allocation unit) size of 16 KB or larger during the format. Otherwise defragmentation registers as a change by the Shadow Copy process.
This increase in the number of changes forces Shadow Copy to delete snapshots as the limit for the cache file is reached.
CAUTION:
Allocation unit size cannot be altered without reformatting the drive. Data on a reformatted drive cannot be recovered.
For more information about disk defragmentation, read the online help.
Disk quotas
Disk quotas track and control disk space use in volumes.
NOTE:
To limit the size of a folder or share, see Quota management.
Configure the volumes on the server to perform the following tasks:
• Prevent further disk space use and log an event when a user exceeds a specified disk space limit.
• Log an event when a user exceeds a specified disk space warning level.
When enabling disk quotas, it is possible to set both the disk quota limit and the disk quota warning level. The disk quota limit specifies the amount of disk space a user is allowed to use. The warning level specifies the point at which a user is nearing his or her quota limit. For example, a user's disk quota limit can be set to 50 megabytes (MB), and the disk quota warning level to 45 MB. In this case, the user can store no more than 50
MB on the volume. If the user stores more than 45 MB on the volume, the disk quota system logs a system event.
In addition, it is possible to specify that users can exceed their quota limit. Enabling quotas and not limiting disk space use is useful to still allow users access to a volume, but track disk space use on a per-user basis.
It is also possible to specify whether or not to log an event when users exceed either their quota warning level or their quota limit.
When enabling disk quotas for a volume, volume usage is automatically tracked from that point forward, but existing volume users have no disk quotas applied to them. Apply disk quotas to existing volume users by adding new quota entries on the Quota Entries page.
NOTE:
When enabling disk quotas on a volume, any users with write access to the volume who have not exceeded their quota limit can store data on the volume. The first time a user writes data to a quotaenabled volume, default values for disk space limit and warning level are automatically assigned by the quota system.
For more information about disk quotas, read the online help.
74 Disk quotas
NOTE:
The quota information reported on a NFS file share when viewed from a linux system will reflect the entire volume size. In order to provide each user with a notification of quota information for their NFS shares it is recommended that a quota template be created through the File Server Resource Manager.
For more information go to https://technet.microsoft.com/en-us/library/hh831701(v=ws.11).aspx
Adding storage
Expansion is the process of adding physical disks to an array that has already been configured. Extension is the process of adding new storage space to an existing logical drive on the same array, usually after the array has been expanded.
Storage growth may occur in three forms:
• Extend unallocated space from the original logical disks or LUNs.
• Alter LUNs to contain additional storage.
• Add new LUNs to the system.
The additional space is then extended through a variety of means, depending on which type of disk structure is in use.
Expanding storage
Expansion is the process of adding physical disks to an array that has already been configured. The logical drives (or volumes) that exist in the array before the expansion takes place are unchanged, because only the amount of free space in the array changes. The expansion process is entirely independent of the operating system.
NOTE:
See your storage array hardware user documentation for further details about expanding storage on the array.
Extending storage using Windows Storage Utilities
Volume extension grows the storage space of a logical drive. During this process, the administrator adds new storage space to an existing logical drive on the same array, usually after the array has been expanded. An administrator may have gained this new storage space by either expansion or by deleting another logical drive on the same array. Unlike drive expansion, the operating system must be aware of changes to the logical drive size.
You extend a volume to:
• Increase raw data storage
• Improve performance by increasing the number of spindles in a logical drive volume
• Change fault-tolerance (RAID) configurations
For more information about RAID levels, see the Smart Array Controller User Guide, or the document titled
Assessing RAID ADG vs. RAID 5 vs. RAID 1+0. Both are available at the Smart Array controller web page or at www.hpe.com/info/enterprise/docs.
Extend volumes using Disk Management
The Disk Management snap-in provides management of hard disks, volumes or partitions. It can be used to extend a dynamic volume only.
NOTE:
Disk Management cannot be used to extend basic disk partitions.
Adding storage
75
Guidelines for extending a dynamic volume:
• Use the Disk Management utility.
• You can extend a volume only if it does not have a file system or if it is formatted NTFS.
• You cannot extend volumes formatted using FAT or FAT32.
• You cannot extend striped volumes, mirrored volumes, or RAID 5 volumes.
For more information, see the Disk Management online help.
Volume shadow copies
NOTE:
Select HPE StoreVirtual 3000 File Controller can be deployed in a clustered as well as a non-clustered configuration. This chapter discusses using shadow copies in a non-clustered environment.
The Volume Shadow Copy Service provides an infrastructure for creating point-in-time snapshots (shadow copies) of volumes. Shadow Copy supports 64 shadow copies per volume.
A shadow copy contains previous versions of the files or folders contained on a volume at a specific point in time. While the shadow copy mechanism is managed at the server, previous versions of files and folders are only available over the network from clients, and are seen on a per folder or file level, and not as an entire volume.
The shadow copy feature uses data blocks. As changes are made to the file system, the Shadow Copy
Service copies the original blocks to a special cache file to maintain a consistent view of the file at a particular point in time. Because the snapshot only contains a subset of the original blocks, the cache file is typically smaller than the original volume. In the snapshot's original form, it takes up no space because blocks are not moved until an update to the disk occurs.
By using shadow copies, an HPE StoreVirtual 3000 File Controller system can maintain a set of previous versions of all files on the selected volumes. End users access the file or folder by using a separate client add-on program, which enables them to view the file in Windows Explorer. Accessing previous versions of files, or shadow copies, enables users to:
• Recover files that were accidentally deleted. Previous versions can be opened and copied to a safe location.
• Recover from accidentally overwriting a file. A previous version of that file can be accessed.
• Compare several versions of a file while working. Use previous versions to compare changes between two versions of a file.
Shadow copies cannot replace the current backup, archive, or business recovery system, but they can help to simplify restore procedures. Because a snapshot only contains a portion of the original data blocks, shadow copies cannot protect against data loss due to media failures. However, the strength of snapshots is the ability to instantly recover data from shadow copies, reducing the number of times needed to restore data from tape.
Shadow copy planning
Before setup is initiated on the server and the client interface is made available to end users, consider the following:
• From what volume will shadow copies be taken?
• How much disk space should be allocated for shadow copies?
• Will separate disks be used to store shadow copies?
• How frequently will shadow copies be made?
76 Volume shadow copies
Identifying the volume
Shadow copies are taken for a complete volume, but not for a specific directory. Shadow copies work best when the server stores user files, such as documents, spreadsheets, presentations, graphics, or database files.
NOTE:
Shadow copies must not be used to provide access to previous versions of application or e-mail databases.
Shadow copies are designed for volumes that store user data such as home directories and My Documents folders that are redirected by using Group Policy or other shared folders in which users store data.
Shadow copies work with compressed or encrypted files and retain whatever permissions were set on the files when the shadow copies were taken. For example, if a user is denied permission to read a file, that user would not be able to restore a previous version of the file, or be able to read the file after it has been restored.
Although shadow copies are taken for an entire volume, users must use shared folders to access shadow copies. Administrators on the local server must also specify the \\servername\sharename path to access shadow copies. If administrators or end users want to access a previous version of a file that does not reside in a shared folder, the administrator must first share the folder.
NOTE:
Shadow copies are available only on NTFS, not FAT or FAT32 volumes.
Files or folders that are recorded by using Shadow Copy appear static, even though the original data is changing.
Allocating disk space
When determining the amount of space to allocate for storing shadow copies, consider both the number and size of files that are being copied, as well as the frequency of changes between copies. For example, 100 files that only change monthly require less storage space than 10 files that change daily. If the frequency of changes to each file is greater than the amount of space allocated to storing shadow copies, no shadow copy is created.
Administrators should also consider user expectations of how many versions they will want to have available.
End users might expect only a single shadow copy to be available, or they might expect three days or three weeks worth of shadow copies. The more shadow copies users expect, the more storage space administrators must allocate for storing them.
Setting the limit too low also affects backup programs that use shadow copy technology because these programs are also limited to using the amount of disk space specified by administrators.
NOTE:
Regardless of the volume space that is allocated for shadow copies, there is a maximum of 64 shadow copies for any volume. When the 65th shadow copy is taken, the oldest shadow copy is purged.
The minimum amount of storage space that can be specified is 350 megabytes (MB). The default storage size is 10 percent of the source volume (the volume being copied). If the shadow copies are stored on a separate volume, change the default to reflect the space available on the storage volume instead of the source volume. Remember that when the storage limit is reached, older versions of the shadow copies are deleted and cannot be restored.
Identifying the volume
77
CAUTION:
To change the storage volume, shadow copies must be deleted. The existing file change history that is kept on the original storage volume is lost. To avoid this problem, verify that the storage volume that is initially selected is large enough.
Identifying the storage area
To store the shadow copies of another volume on the same file server, a volume can be dedicated on separate disks. For example, if user files are stored on H:\, another volume such as S:\can be used to store the shadow copies. Using a separate volume on separate disks provides better performance and is recommended for heavily used HPE StoreVirtual 3000 File Controller systems.
If a separate volume will be used for the storage area (where shadow copies are stored), the maximum size must be changed to No Limit to reflect the space available on the storage area volume instead of the source volume (where the user files are stored).
Disk space for shadow copies can be allocated on either the same volume as the source files or a different volume. There is a trade-off between ease of use and maintenance versus performance and reliability that the system administrator must consider.
By keeping the shadow copy on the same volume, there is a potential gain in ease of setup and maintenance; however, there may be a reduction in performance and reliability.
CAUTION:
If shadow copies are stored on the same volume as the user files, note that a burst of disk input/output
(I/O) can cause all shadow copies to be deleted. If the sudden deletion of shadow copies is unacceptable to administrators or end users, it is best to use a separate volume on separate disks to store shadow copies.
Determining creation frequency
The more frequently shadow copies are created, the more likely that end users will get the version that they want. However, with a maximum of 64 shadow copies per volume, there is a trade-off between the frequency of making shadow copies and the amount of time that the earlier files will be available.
By default, the HPE StoreVirtual 3000 File Controller system creates shadow copies at 0700 and 1200,
Monday through Friday. However, these settings are easily modified by the administrator so that the shadow copy schedule can better accommodate end user needs.
Shadow copies and drive defragmentation
When running Disk Defragmenter on a volume with shadow copies activated, all or some of the shadow copies may be lost, starting with the oldest shadow copies.
If defragmenting volumes on which shadow copies are enabled, use a cluster (or allocation unit) size of 16 KB or larger. Using this allocation unit size reduces the number of copy outs occurring on the snapshot.
Otherwise, the number of changes caused by the defragmentation process can cause shadow copies to be deleted faster than expected. Note, however, that NTFS compression is supported only if the cluster size is 4
KB or smaller.
NOTE:
To check the cluster size of a volume, use the fsutil fsinfo ntfsinfo command. To change the cluster size on a volume that contains data, back up the data on the volume, reformat it using the new cluster size, and then restore the data.
78 Identifying the storage area
Mounted drives
A mounted drive is a local volume attached to an empty folder (called a mount point) on an NTFS volume.
When enabling shadow copies on a volume that contains mounted drives, the mounted drives are not included when shadow copies are taken. In addition, if a mounted drive is shared and shadow copies are enabled on it, users cannot access the shadow copies if they traverse from the host volume (where the mount point is stored) to the mounted drive.
For example, assume there is a folder F:\data\users, and the Users folder is a mount point for G:\. If shadow copies are enabled on both F:\ and G:\, F:\data is shared as \\server1\data, and G:\data
\users is shared as \\server1\users. In this example, users can access previous versions of \
\server1\data and \\server1\users but not \\server1\data\users.
Managing shadow copies
The vssadmin tool provides a command line capability to create, list, resize, and delete volume shadow copies. The system administrator can make shadow copies available to end users through a feature called
“Shadow Copies for Shared Folders.” The administrator uses the Properties menu (see System
administrator view of Shadow Copies for Shared Folders) to turn on the Shadow Copies feature, select
the volumes to be copied, and determine the frequency with which shadow copies are made.
Figure 17: System administrator view of Shadow Copies for Shared Folders
The shadow copy cache file
The default shadow copy settings allocate 10 percent of the source volume being copied (with a minimum of
350 MB), and store the shadow copies on the same volume as the original volume. (See Shadow copies
Information” off of the root of each volume for which shadow copy is enabled.
Mounted drives
79
Figure 18: Shadow copies stored on a source volume
The cache file location can be altered to reside on a dedicated volume separate from the volumes containing
files shares. (See Shadow copies stored on a separate volume).
Figure 19: Shadow copies stored on a separate volume
The main advantage to storing shadow copies on a separate volume is ease of management and performance. Shadow copies on a source volume must be continually monitored and can consume space designated for file sharing. Setting the limit too high takes up valuable storage space. Setting the limit too low can cause shadow copies to be purged too soon, or not created at all. By storing shadow copies on a separate volume space, limits can generally be set higher, or set to No Limit. See the online help for instructions on altering the cache file location.
CAUTION:
If the data on the separate volume L: is lost, the shadow copies cannot be recovered.
80 File server management
Enabling and creating shadow copies
Enabling shadow copies on a volume automatically results in several actions:
• Creates a shadow copy of the selected volume.
• Sets the maximum storage space for the shadow copies.
• Schedules shadow copies to be made at 7 a.m. and 12 noon on weekdays.
NOTE:
• Creating a shadow copy only makes one copy of the volume; it does not create a schedule.
• After the first shadow copy is created, it cannot be relocated. Relocate the cache file by altering the
cache file location under Properties prior to enabling shadow copy. See Viewing shadow copy
Viewing a list of shadow copies
To view a list of shadow copies on a volume:
Procedure
1. Access Disk Management.
2. Select the volume or logical drive, then right-click on it.
3. Select Properties.
4. Select Shadow Copies tab.
All shadow copies are listed, sorted by the date and time they were created.
NOTE:
It is also possible to create new shadow copies or delete shadow copies from this page.
Set schedules
Shadow copy schedules control how frequently shadow copies of a volume are made. There are a number of factors that can help determine the most effective shadow copy schedule for an organization. These include the work habits and locations of the users. For example, if users do not all live in the same time zone, or they work on different schedules, it is possible to adjust the daily shadow copy schedule to allow for these differences.
Do not schedule shadow copies more frequently than once per hour.
NOTE:
When deleting a shadow copy schedule, that action has no effect on existing shadow copies.
Viewing shadow copy properties
The Shadow Copy Properties page lists the number of copies, the date and time the most recent shadow copy was made, and the maximum size setting.
NOTE:
For volumes where shadow copies do not exist currently, it is possible to change the location of the cache file. Managing the cache files on a separate disk is recommended.
Enabling and creating shadow copies
81
CAUTION:
Use caution when reducing the size limit for all shadow copies. When the size is set to less than the total size currently used for all shadow copies, enough shadow copies are deleted to reduce the total size to the new limit. A shadow copy cannot be recovered after it has been deleted.
Redirecting shadow copies to an alternate volume
IMPORTANT:
Shadow copies must be initially disabled on the volume before redirecting to an alternate volume. If shadow copies are enabled and you disable them, a message appears informing you that all existing shadow copies on the volume will be permanently deleted.
To redirect shadow copies to an alternate volume:
Procedure
1. Access Disk Management.
2. Select the volume or logical drive, then right-click on it.
3. Select Properties.
4. Select the Shadow Copies tab.
5. Select the volume that you want to redirect shadow copies from and ensure that shadow copies are disabled on that volume; if enabled, click Disable.
6. Click Settings.
7. In the Located on this volume field, select an available alternate volume from the list.
NOTE: To change the default shadow copy schedule settings, click Schedule.
8. Click OK.
9. On the Shadow Copies tab, ensure that the volume is selected, and then click Enable.
Shadow copies are now scheduled to be made on the alternate volume.
Disabling shadow copies
When shadow copies are disabled on a volume, all existing shadow copies on the volume are deleted as well as the schedule for making new shadow copies.
CAUTION:
When the Shadow Copies Service is disabled, all shadow copies on the selected volumes are deleted.
Once deleted, shadow copies cannot be restored.
Managing shadow copies from the HPE StoreVirtual 3000 File Controller system desktop
The HPE StoreVirtual 3000 File Controller desktop can be accessed by using Remote Desktop to manage shadow copies.
Procedure
1. Select Start > Explorer.
2. Right-click the volume name, and select Properties.
3. Click the Shadow Copies tab. See Accessing shadow copies from My Computer.
82 Redirecting shadow copies to an alternate volume
Figure 20: Accessing shadow copies from My Computer
Shadow Copies for Shared Folders
Shadow copies are accessed over the network by supported clients and protocols. There are two sets of supported protocols, SMB and NFS. All other protocols are not supported, including HTTP, FTP, AppleTalk, and NetWare Shares. For SMB support, a client-side application denoted as Shadow Copies for Shared
Folders is required. The client-side application is available for Windows XP, Windows 2000 SP3+, and later operating system versions.
No additional software is required to enable UNIX users to independently retrieve previous versions of files stored on NFS shares.
NOTE:
• Shadow Copies for Shared Folders supports retrieval only of shadow copies of network shares. It does not support retrieval of shadow copies of local folders.
• Shadow Copies for Shared Folders clients are not available for HTTP, FTP, AppleTalk, or NetWare shares. Consequently, users of these protocols cannot use Shadow Copies for Shared Folders to independently retrieve previous versions of their files. However, administrators can take advantage of Shadow Copies for Shared Folders to restore files for these users.
Shadow Copies for Shared Folders
83
SMB shadow copies
Windows users can independently access previous versions of files stored on SMB shares by using the
Shadow Copies for Shared Folders client. After the Shadow Copies for Shared Folders client is installed on the user's computer, the user can access shadow copies for a share by right-clicking on the share to open its
Properties window, clicking the Previous Versions tab, and then selecting the desired shadow copy. Users can view, copy, and restore all available shadow copies.
Shadow Copies for Shared Folders preserves the permissions set in the access control list (ACL) of the original folders and files. Consequently, users can only access shadow copies for shares to which they have access. In other words, if a user does not have access to a share, he also does not have access to the share's shadow copies.
The Shadow Copies for Shared Folders client pack installs a Previous Versions tab in the Properties window of files and folders on network shares.
Users access shadow copies with Windows Explorer by selecting Open, Copy, or Restore from the
Previous Versions tab. (See Client GUI). Both individual files and folders can be restored.
Figure 21: Client GUI
When users view a network folder hosted on the HPE StoreVirtual 3000 File Controller for which shadow copies are enabled, old versions (prior to the snapshot) of a file or directory are available. Viewing the properties of the file or folder presents users with the folder or file history—a list of read-only, point-in-time
84 SMB shadow copies
copies of the file or folder contents that users can then open and explore like any other file or folder. Users can view files in the folder history, copy files from the folder history, and so on.
NFS shadow copies
UNIX users can independently access previous versions of files stored on NFS shares via the NFS client; no additional software is required. Server for NFS exposes each of a share's available shadow copies as a pseudo-subdirectory of the share. Each of these pseudo-subdirectories is displayed in exactly the same way as a regular subdirectory is displayed.
The name of each pseudo-subdirectory reflects the creation time of the shadow copy, using the format [email protected]:MM:SS. To prevent common tools from needlessly enumerating the pseudosubdirectories, the name of each pseudo-subdirectory begins with the dot character, thus rendering it hidden.
The following example shows an NFS share named “NFSShare” with three shadow copies, taken on April 27,
28, and 29 of 2003 at 4 a.m.
NFSShare
[email protected]:00:00
[email protected]:00:00
[email protected]:00:00
Access to NFS shadow copy pseudo-subdirectories is governed by normal access-control mechanisms using the permissions stored in the file system. Users can access only those shadow copies to which they have read access at the time the shadow copy is taken. To prevent users from modifying shadow copies, all pseudo-subdirectories are marked read-only, regardless of the user's ownership or access rights, or the permissions set on the original files.
Server for NFS periodically polls the system for the arrival or removal of shadow copies and updates the root directory view accordingly. Clients then capture the updated view the next time they issue a directory read on the root of the share.
Recovery of files or folders
There are three common situations that may require recovery of files or folders:
• Accidental file deletion, the most common situation
• Accidental file replacement, which may occur if a user selects Save instead of Save As
• File corruption
It is possible to recover from all of these scenarios by accessing shadow copies. There are separate steps for accessing a file compared to accessing a folder.
Recovering a deleted file or folder
To recover a deleted file or folder within a folder:
Procedure
1. Access to the folder where the deleted file was stored.
2. Position the cursor over a blank space in the folder. If the cursor hovers over a file, that file is selected.
3. Right-click, select Properties from the bottom of the menu, and then click the Previous Versions tab.
4. Select the version of the folder that contains the file before it was deleted, and then click Open.
5. View the folder and select the file or folder to recover. The view may be navigated multiple folders deep.
6. Click Restore to restore the file or folder to its original location. Click Copy to allow the placement of the file or folder to a new location.
NFS shadow copies
85
Recovering an overwritten or corrupted file
Recovering an overwritten or corrupted file is easier than recovering a deleted file because the file itself can be right-clicked instead of the folder. To recover an overwritten or corrupted file:
Procedure
1. Right-click the overwritten or corrupted file, and then click Properties.
2. Click Previous Versions.
3. To view the old version, click Open. To copy the old version to another location, click Copy to replace the current version with the older version, click Restore.
Recovering a folder
To recover a folder:
Procedure
1. Position the cursor so that it is over a blank space in the folder to be recovered. If the cursor hovers over a file, that file is selected.
2. Right-click, select Properties from the bottom of the menu, and then click the Previous Versions tab.
3. Click either Copy or Restore.
Clicking Restore enables the user to recover everything in that folder as well as all subfolders. Clicking
Restore does not delete any files.
Backup and shadow copies
Shadow copies are only available on the network via the client application, and only at a file or folder level as opposed to the entire volume. Hence, the standard backup associated with a volume backup will not work to back up the previous versions of the file system. To answer this particular issue, shadow copies are available for backup in two situations. If the backup software in question supports the use of shadow copies and can communicate with underlying block device, it is supported, and the previous version of the file system will be listed in the backup application as a complete file system snapshot. If the built-in backup application
NTbackup is used, the backup software forces a snapshot, and then uses the snapshot as the means for backup. The user is unaware of this activity and it is not self-evident although it does address the issue of open files.
Shadow Copy Transport
Shadow Copy Transport provides the ability to transport data on a Storage Area Network (SAN). With a storage array and a VSS-aware hardware provider, it is possible to create a shadow copy on one server and import it on another server. This process, essentially “virtual” transport, is accomplished in a matter of minutes, regardless of the size of the data.
A shadow copy transport can be used for a number of purposes, including:
• Tape backups
An alternative to traditional backup to tape processes is transport of shadow copies from the production server onto a backup server, where they can then be backed up to tape. Like the other two alternatives, this option removes backup traffic from the production server. While some backup applications might be designed with the hardware provider software that enables transport, others are not. The administrator should determine whether or not this functionality is included in the backup application.
• Data mining
The data in use by a particular production server is often useful to different groups or departments within an organization. Rather than add additional traffic to the production server, a shadow copy of the data can be made available through transport to another server. The shadow copy can then be processed for different purposes, without any performance impact on the original server.
86 Recovering an overwritten or corrupted file
The transport process is accomplished through a series of DISKRAID command steps:
1. Create a shadow copy of the source data on the source server (read-only).
2. Mask off (hide) the shadow copy from the source server.
3. Unmask the shadow copy to a target server.
4. Optionally, clear the read-only flags on the shadow copy.
The data is now ready to use.
Folder and share management
The HPE StoreVirtual 3000 File Controller supports several file-sharing protocols, including NFS, FTP, HTTP, and Microsoft SMB. This section discusses overview information as well as procedures for the setup and management of the file shares for the supported protocols. Security at the file level and at the share level is also discussed.
NOTE:
Select servers can be deployed in a clustered or non-clustered configuration. This section discusses share setup for a non-clustered deployment.
Folder management
Volumes and folders on any system are used to organize data. Regardless of system size, systematic structuring and naming conventions of volumes and folders eases the administrative burden. Moving from volumes to folders to shares increases the level of granularity of the types of data stored in the unit and the level of security access allowed.
Folders can be managed using Server Manager. Tasks include:
• Accessing a specific volume or folder
• Creating a new folder
• Deleting a folder
• Modifying folder properties
• Creating a new share for a volume or folder
• Managing shares for a volume or folder
Managing file-level permissions
Security at the file level is managed using Windows Explorer.
File level security includes settings for permissions, ownership, and auditing for individual files.
To enter file permissions:
• Using Windows Explorer, access the folder or file that needs to be changed, and then right-click the folder.
• Click Properties, and then click the Security tab.
Folder and share management
87
Figure 22: Properties screen, Security tab
• Several options are available on the Security tab:
◦ To add users and groups to the permissions list, click Add. Follow the dialog box instructions.
◦ To remove users and groups from the permissions list, highlight the desired user or group, and then click Remove.
◦ The center section of theSecurity tab lists permission levels. When new users or groups are added to the permissions list, select the appropriate boxes to configure the common file-access levels.
• To modify ownership of files, or to modify individual file access level permissions, click Advanced.
• Advanced Security settings screen, Permissions tab illustrates the properties available on the
Advanced Security Settings screen.
88 File server management
Figure 23: Advanced Security settings screen, Permissions tab
• Other functionality available in the Advanced Security Settings screen is illustrated in Advanced
Security settings screen, Permissions tab and includes:
◦ Add a new user or group—ClickAdd, and then follow the dialog box instructions.
◦ Remove a user or group—Click Remove.
◦ Replace permission entries on all child objects with entries shown here that apply to child
objects—This allows all child folders and files to inherit the current folder permissions by default.
◦ Modify specific permissions assigned to a particular user or group—Select the desired user or group, and then clickEdit.
• Enable or disable permissions by selecting the Allow box to enable permission or the Deny box to disable
Entry screen illustrates the Edit screen and some of the permissions.
File server management
89
Figure 24: User or group Permission Entry screen
• Another area of the Advanced Security Settings is the Auditing tab. Auditing allows you to set rules for the auditing of access, or attempted access, to files or folders. Users or groups can be added, deleted, viewed, or modified through the Advanced Security Settings Auditing tab.
90 File server management
Figure 25: Advanced Security Settings screen, Auditing tab
• Click Add to display the Auditing Entry screen.
File server management
91
Figure 26: Auditing Entry for New Volume screen
• Click Select a principal to display the Select User or Group screen.
Figure 27: Select User or Group screen
NOTE:
Click Advanced to search for users or groups.
• Select the user or group.
• Click OK.
• Select the desired Successful and Failed audits for the user or group.
• Click OK.
92 File server management
NOTE: Auditing must be enabled to configure this information. Use the local Computer Policy Editor to configure the audit policy on HPE StoreVirtual 3000 File Controller.
The Owner tab allows taking ownership of files. Typically, administrators use this area to take ownership of files when the file ACL is incomplete or corrupt. By taking ownership, you gain access to the files, and then manually apply the appropriate security configurations.
Figure 28: Advanced Security Settings screen
The current owner of the file or folder is listed at the top of the screen. To take ownership:
• Click the appropriate user or group in the Change owner to list.
• If it is also necessary to take ownership of subfolders and files, enable the Replace owner on
subcontainers and objects box.
• Click OK.
Share management
There are several ways to set up and manage shares. Methods include using Windows Explorer, a command line interface, or Server Manger.
NOTE:
Select servers can be deployed in a clustered as well as a non-clustered configuration. This chapter discusses share setup for a non-clustered deployment.
As previously mentioned, the file-sharing security model of HPE StoreVirtual 3000 File Controller is based on the NTFS file-level security model. Share security seamlessly integrates with file security. In addition to discussing share management, this section discusses share security.
Share management
93
Share considerations
Planning the content, size, and distribution of shares on the HPE StoreVirtual 3000 File Controller can improve performance, manageability, and ease of use.
The content of shares should be carefully chosen to avoid two common pitfalls: either having too many shares of a very specific nature, or of having very few shares of a generic nature. For example, shares for general use are easier to set up in the beginning, but can cause problems later. Frequently, a better approach is to create separate shares with a specific purpose or group of users in mind. However, creating too many shares also has its drawbacks. For example, if it is sufficient to create a single share for user home directories, create a “homes” share rather than creating separate shares for each user.
By keeping the number of shares and other resources low, the performance of HPE StoreVirtual 3000 File
Controller is optimized. For example, instead of sharing out each individual user's home directory as its own share, share out the top-level directory and let the users map personal drives to their own subdirectory.
Defining Access Control Lists
The Access Control List (ACL) contains the information that dictates which users and groups have access to a share, as well as the type of access that is permitted. Each share on an NTFS file system has one ACL with multiple associated user permissions. For example, an ACL can define that User1 has read and write access to a share, User2 has read only access, and User3 has no access to the share. The ACL also includes group access information that applies to every user in a configured group. ACLs are also referred to as permissions.
Integrating local file system security into Windows domain environments
ACLs include properties specific to users and groups from a particular workgroup server or domain environment. In a multidomain environment, user and group permissions from several domains can apply to files stored on the same device. Users and groups local to the HPE StoreVirtual 3000 File Controller can be given access permissions to shares managed by the device. The domain name of the storage system supplies the context in which the user or group is understood. Permission configuration depends on the network and domain infrastructure where the server resides.
File-sharing protocols (except NFS) supply a user and group context for all connections over the network.
(NFS supplies a machine-based context.) When new files are created by those users or machines, the appropriate ACLs are applied.
Configuration tools provide the ability to share permissions out to clients. These shared permissions are propagated into a file system ACL, and when new files are created over the network, the user creating the file becomes the file owner. In cases where a specific subdirectory of a share has different permissions from the share itself, the NTFS permissions on the subdirectory apply instead. This method results in a hierarchical security model where the network protocol permissions and the file permissions work together to provide appropriate security for shares on the device.
NOTE:
Share permissions and file-level permissions are implemented separately. It is possible for files on a file system to have different permissions from those applied to a share. When this situation occurs, the filelevel permissions override the share permissions.
Comparing administrative (hidden) and standard shares
SMB supports both administrative shares and standard shares.
• Administrative shares are shares with a last character of $. Administrative shares are not included in the list of shares when a client browses for available shares on a SMB server.
• Standard shares are shares that do not end in a $ character. Standard shares are listed whenever a SMB client browses for available shares on a SMB server.
94 Share considerations
The HPE StoreVirtual 3000 File Controller supports both administrative and standard SMB shares. To create an administrative share, end the share name with the $ character when setting up the share. Do not type a $ character at the end of the share name when creating a standard share.
Managing shares
Shares can be managed using Server Manager. Tasks include:
• Creating a new share
• Deleting a share
• Modifying share properties
• Publishing in DFS
NOTE:
These functions can operate in a cluster on select servers, but should only be used for non-clusteraware shares. Use Cluster Administrator to manage shares for a cluster. The page will display cluster share resources.
CAUTION:
Before deleting a share, warn all users to exit that share and confirm that no one is using that share.
File Server Resource Manager
File Server Resource Manager (FSRM) is a suite of tools that allows administrators to understand, control, and manage the quantity and type of data stored on their HPE StoreVirtual 3000 File Controller. Some of the tasks you can perform are:
• Quota management
• File screening management
• Storage reports
Server Manager provides access to FSRM tasks.
For procedures and methods beyond what are described below, see the HPE StoreVirtual 3000 File
Controller Online Help.
Quota management
On the Quota Management node of the File Server Resource Manager snap-in, you can perform the following tasks:
• Create quotas to limit the space allowed for a volume or folder and generate notifications when the quota limits are approached or exceeded.
• Generate auto quotas that apply to all existing folders in a volume or folder, as well as to any new subfolders created in the future.
• Define quota templates that can be easily applied to new volumes or folders and that can be used across an organization.
File screening management
On the File Screening Management node of the File Server Resource Manager snap-in, you can perform the following tasks:
Managing shares
95
• Create file screens to control the types of files that users can save and to send notifications when users attempt to save blocked files.
• Define file screening templates that can be easily applied to new volumes or folders and that can be used across an organization.
• Create file screening exceptions that extend the flexibility of the file screening rules.
Storage reports
On the Storage Reports node of the File Server Resource Manager snap-in, you can perform the following tasks:
• Schedule periodic storage reports that allow you to identify trends in disk usage.
• Monitor attempts to save unauthorized files for all users or a selected group of users.
• Generate storage reports instantly.
96 Storage reports
Management tools
Update tool
The Update Tool is used to install hotfixes and updated HPE components on the HPE Storage system. The utility “Update Tool” is designed to provide an integrated, enhanced and seamless end user experience exploiting the cluster aware update (CAU) feature. It presents a uniform graphical user interface to upgrade standalone and cluster nodes from local and remote processors. In addition to that, this interface allows performing the complete operations with minimal number of clicks while keeping a provision for advanced parameter selection exploiting the underlying framework.
Installing updates using the Update Tool Procedure
1. Double-click the Update Tool icon on the desktop to launch the tool.The available modes to install the updates appear.
2. Select a mode: Standalone, Co-ordinate or Cluster mode
3. Click Next.
If you select:
• Standalone mode, the system navigates to the Update Tool Summary page.
• Cluster mode or Co-ordinator mode, the system navigates to the Update Tool Input page.
4. On the Update Tool Input page, enter the required settings and click Next.The Update Tool Summary page appears.
5. Click Install. The installation starts and the tool navigates to the Update Tool Result page, which provides the status of the installation.
NOTE: For Standalone mode, you cannot cancel the installation after the installation starts.
6. Click Open Log to view the log files that the system generates during the update installation.
NOTE: For a cluster system, you must select individual nodes and then click Open Logto view the logs for that particular node.
7. The update will complete installation after you reboot the system.
Click OK to exit the tool.
• If no component in the SR package requires reboot, the application closes.
Systems Insight Manager
Systems Insight Manager (SIM) is a web-based application that allows system administrators to accomplish normal administrative tasks from any remote location, using a web browser. SIM provides device management capabilities that consolidate and integrate management data from HPE and third-party devices.
IMPORTANT:
You must install and use SIM to benefit from the Pre-Failure Warranty for processors, SAS and SCSI hard drives, and memory modules.
For additional information, refer to the Management CD in the HPE ProLiant Essentials Foundation Pack or the SIM website (http://www.hpe.com/info/hpesim). For the latest version of SIM, refer to the HPE SPOCK website (http://www.hpe.com/storage/spock).
Management Agents
Management Agents provide the information to enable fault, performance, and configuration management.
The agents allow easy manageability of the server through HP SIM software, and third-party SNMP management platforms. Management Agents are installed with every SmartStart assisted installation or can
Management tools
97
be installed through the HPE PSP. The Systems Management homepage provides status and direct access to in-depth subsystem information by accessing data reported through the Management Agents. For additional information, refer to the Management CD in the HPE ProLiant Essentials Foundation Pack or the HPE website https://www.hpe.com/us/en/servers/management.html.
98 Management tools
Cluster administration
One important feature of HPE StoreVirtual 3000 File Controller systems is that they can operate as a single node or as a cluster. This chapter discusses cluster installation and cluster management issues.
Cluster overview
A failover cluster is a group of independent computers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software. If one of the cluster nodes fails, another node begins to provide service (a process known as failover). Users experience a minimum of disruptions in service.
Up to eight server nodes can be connected to each other and deployed as a no single point of failure
(NSPOF) cluster. Utilizing a private network allows communication amongst themselves in order to track the state of each cluster node. Each node sends out periodic messages to the other nodes; these messages are called heartbeats. If a node stops sending heartbeats, the cluster service fails over any resources that the node owns to another node. For example, if the node that owns the Quorum disk is shut down for any reason, its heartbeat stops. The other nodes detect the lack of the heartbeat and another node takes over ownership of the Quorum disk and the cluster.
Clustering servers greatly enhances the availability of file serving by enabling file shares to fail over to additional storage systems if problems arise. Clients see only a brief interruption of service as the file share resource transitions from one server node to the other.
Figure 29: Storage system cluster diagram
Cluster terms and components
Cluster administration
99
Nodes
The most basic parts of a cluster are the servers, referred to as nodes. A server node is any individual server in a cluster, or a member of the cluster.
Resources
Hardware and software components that are managed by the cluster service are called cluster resources.
Cluster resources have three defining characteristics:
• They can be brought online and taken offline.
• They can be managed in a cluster.
• They can be owned by only one node at a time.
Examples of cluster resources are IP addresses, network names, physical disk resources, and file shares.
Resources represent individual system components. These resources are organized into groups and managed as a group. Some resources are created automatically by the system and other resources must be set up manually. Resource types include:
• IP address resource
• Cluster name resource
• Cluster quorum disk resource
• Physical disk resource
• Virtual server name resources
• SMB file share resources
• NFS file share resources
• FTP file share resources
• iSCSI resources
Cluster groups
Cluster resources are placed together in cluster groups. Groups are the basic unit of failover between nodes.
Resources do not fail over individually; they fail over with the group in which they are contained.
Virtual servers
A virtual server is a cluster group that consists of a static IP Address resource and a Network Name resource.
Several virtual servers can be created. By assigning ownership of the virtual servers to the different server nodes, the processing load on the storage systems can be distributed between the nodes of a cluster.
The creation of a virtual server allows resources dependent on the virtual server to fail over and fail back between the cluster nodes. Cluster resources are assigned to the virtual server to ensure non-disruptive service of the resources to the clients.
Failover and failback
Failover of cluster groups and resources happens:
• When a node hosting the group becomes inactive.
• When all of the resources within the group are dependent on one resource, and that resource fails.
• When an administrator forces a failover.
A resource and all of its dependencies must be located in the same group so that if a resource fails over, all of its dependent resources fail over.
When a resource is failed over, the cluster service performs certain procedures. First, all of the resources are taken offline in an order defined by the resource dependencies. Secondly, the cluster service attempts to transfer the group to the next node on the preferred owner's list. If the transfer is successful, the resources are brought online in accordance with the resource dependency structure.
100 Nodes
The system failover policy defines how the cluster detects and responds to the failure of individual resources in the group. After a failover occurs and the cluster is brought back to its original state, failback can occur automatically based on the policy. After a previously failed node comes online, the cluster service can fail back the groups to the original host. The failback policy must be set before the failover occurs so that failback works as intended.
Quorum disk
A Quorum disk is recommended for clusters with an even number of cluster nodes. The Quorum disk is the shared storage used by the cluster nodes to coordinate the internal cluster state. This physical disk in the common cluster disk array plays a critical role in cluster operations. The Quorum disk offers a means of persistent storage. The disk must provide physical storage that can be accessed by all nodes in the cluster. If a node has control of the quorum resource upon startup, it can initiate the cluster. In addition, if the node can communicate with the node that owns the quorum resource, it can join or remain in the cluster.
The Quorum disk maintains data integrity by:
• Storing the most current version of the cluster database
• Guaranteeing that only one set of active communicating nodes is allowed to operate as a cluster
Cluster concepts
Microsoft Failover Clustering groups individual systems together to improve availability, scalability, maintainability, and workload management. These benefits improve as the number of cluster nodes is increased.
Cluster planning
Requirements for taking advantage of clustering include:
• Storage planning
• Network planning
• Protocol planning
Storage planning
The HPE StoreVirtual 3000 File Controller system is organized into logical data layers that contain:
• Physical disks
• Chunklets
• Logical disks
• CPG
• Virtual volumes
For detailed definitions and concepts related to the HPE StoreVirtual 3000 File Controller, see http://
www.hpe.com/support/manuals.
Network planning
Clusters require more sophisticated networking arrangements than a standalone system. A Windows NT domain or Active Directory domain must be in place to contain the cluster names, virtual server names, and user and group information. A cluster cannot be deployed into a non domain environment.
All cluster deployments have at least six network addresses and four network names:
• The cluster name (Unique NETBIOS Name) and IP address
• Node A's name and IP address
• Node B's name and IP address
Quorum disk
101
• At least one virtual server name and IP address for virtual server A
• Cluster Interconnect static IP addresses for Node A and Node B
In multi-node deployments, additional network addresses are required. For each additional node, three static
IP addresses are required.
Virtual names and addresses are the only identification used by clients on the network. Because the names and addresses are virtual, their ownership can transition from one node to the other during a failover, preserving access to the resources in the cluster group.
A cluster uses at least two network connections on each node:
• The private cluster interconnect or “heartbeat” crossover cable connects to one of the network ports on each cluster node. In more than two node deployments, a private VLAN on a switch or hub is required for the cluster interconnect.
• The public client network subnet connects to the remaining network ports on each cluster node. The cluster node names and virtual server names have IP addresses residing on these subnets.
NOTE:
If the share is to remain available during a failover, each cluster node must be connected to the same network subnet. It is impossible for a cluster node to serve the data to a network to which it is not connected.
Protocol planning
Not all file sharing protocols can take advantage of clustering. If a protocol does not support clustering, it will not have a cluster resource and will not failover with any cluster group. In the case of a failover, a client cannot use the virtual name or virtual IP address to access the share since the protocol cannot failover with the cluster group. The client must wait until the initial node is brought back online to access the share.
HPE recommends placing cluster aware and non cluster aware protocols on different file shares.
Table 5: Sharing protocol cluster support
Protocol Client Variant
SMB
NFS
Cluster Aware
(supports failover)
Yes
Yes
Supported on cluster nodes
Yes
Yes
HTTP
FTP
NCP
AppleTalk iSCSI
Windows
UNIX
Linux
Web
Many
Novell
Apple
Standards-based iSCSI initiator
No
Yes
No
No
Yes
Yes
Yes
Yes
No
Yes
102 Protocol planning
NOTE:
AppleTalk is not supported on clustered disk resources. AppleTalk requires local memory for volume indexing. On failover events, the memory map is lost and data corruption can occur.
Preparing for cluster installation
This section provides the steps necessary to cluster HPE StoreVirtual 3000 File Controller.
Before beginning installation
Confirm that the following specifications have been met before proceeding:
• The Quorum disk has been created from shared storage and is at least 50 MB, (500 MB is recommended.)
Additional LUNs may also be presented for use as shared disk resources.
• Cluster configurations must be deployed with dual data paths for high availability. Dual data paths from each node enable a path failure to occur that does not force the failover of the node. Clusters can be configured with single path, but if a failure in the path does occur, all of the node resources will be failed to the non-affected node.
Using multipath data paths for high availability
HPE recommends that cluster configurations be deployed with dual data paths for high availability. Clusters can be configured with single path, but if a failure in the path occurs, all of the node resources will be failed to the non-affected node. Pathing software is required in configurations where multipathing to the storage is desired or required. Multipathing software allows for data path failure to occur without forcing a node failover.
Checklists for cluster server installation
These checklists assist in preparing for installation. Step-by-step instructions begin after the checklists.
Network requirements
• A unique NetBIOS cluster name
• For each node deployed in the cluster the following static IP addresses are required:
◦ One for the network adapters on the private network.
◦ One for the network adapters on the public network.
◦ One for the virtual server itself.
A single static cluster IP address is required for the entire cluster.
• A domain user account for Cluster service (all nodes must be members of the same domain).
• Each node should have at least two network adapters—one for connection to the public network and the other for the node-to-node private cluster network. If only one network adapter is used for both connections, the configuration is unsupported. A separate private network adapter is required for HCL certification.
Shared disk requirements
NOTE:
Do not allow more than one node access the shared storage devices at the same time until Cluster service is installed on at least one node and that node is online. This can be accomplished through selective storage presentation, SAN zoning, or having only one node online at all times.
Preparing for cluster installation
103
• All shared disks, including the Quorum disk, must be accessible from all nodes. When testing connectivity between the nodes and the LUN, only one node should be given access to the LUN at a time.
• All shared disks must be configured as basic (not dynamic).
• All partitions on the disks must be formatted as NTFS.
Cluster installation
During the installation process, nodes are shut down and rebooted. These steps guarantee that the data on disks that are attached to the shared storage bus is not lost or corrupted. This can happen when multiple nodes try to simultaneously write to the same disk that is not yet protected by the cluster software.
Use Power sequencing for cluster installation to determine which nodes and storage devices should be
presented during each step.
Table 6: Power sequencing for cluster installation
Step Node 1 Storage Comments
Setting up networks
On
Additional
Nodes
On Not
Presented
Setting up shared disks
(including the
Qurom disk)
Verifying disk configuration
On
Off
Off
On
Presented
Presented
Verify that all storage devices on the shared bus are not presented;
Power on all nodes.
Shut down all nodes. Present the shared storage, then power on the first node.
Configuring the first node
Configuring additional nodes
On
On
Postinstallation
On
Off
On
On
Presented
Presented
Presented
Shut down first node, power on next node. Repeat this process for all cluster nodes.
Shut down all nodes; power on the first node.
Power on the next node after the first node is successfully configured. Complete this process for all cluster nodes.
At this point all cluster nodes should be on.
To configure the Cluster service on the storage system, an account must have administrative permissions on each node.
Setting up networks
Verify that all network connections are correct, with private network adapters connected to other private network adapters only, and public network adapters connected to the public network.
Configuring the private network adapter
The following procedures are best practices provided by Microsoft and should be configured on the private network adapter.
104 Cluster installation
• On theGeneral tab of the private network adapter, ensure that only TCP/IP is selected.
• Ensure that the Register this connection's address in DNS is not selected in the DNS tab under advanced settings for Internet Protocol (TCP/IP) Properties.
• In all cases, set static IP addresses for the private network connector.
Configuring the public network adapter
While the public network adapter's IP address can be automatically obtained if a DHCP server is available, this is not recommended for cluster nodes. HP strongly recommends setting static IP addresses for all network adapters in the cluster, both private and public. If IP addresses are obtained though DHCP, access to cluster nodes could become unavailable if the DHCP server goes down. If DHCP must be used for the public network adapter, use long lease periods to assure that the dynamically assigned lease address remains valid even if the DHCP service is temporarily lost. Keep in mind that Cluster service recognizes only one network interface per subnet.
Renaming the local area connection icons
HPE recommends changing the names of the network connections for clarity. The naming helps identify a network and correctly assign its role. For example, “Cluster interconnect” for the private network and “Public connection” for the public network.
Verifying connectivity and name resolution
To verify name resolution, ping each node from a client using the node's machine name instead of its IP address.
Verifying domain membership
All nodes in the cluster must be members of the same domain and able to access a domain controller and a
DNS Server.
Setting up a cluster account
The Cluster service requires a domain user account under which the Cluster service can run. This user account must be created before installing Cluster service, because setup requires a user name and password. This user account should be a unique domain account created specifically to administer this cluster. This user account will need to be granted administrator privileges.
About the Quorum disk
HPE makes the following Quorum disk recommendations:
• The minimum size required by Microsoft for the Quorum disk is 512 MB.
• Use the recommended HPE StoreVirtual 3000 File Controller configuration based on the workload or use case. The RAID level that you select depends on the behavior of writes versus reads I/O.
• If you want to assign a drive letter to the Quoram disk, it is suggested that you assign the drive letter Q.
Optionally, you may provide a distinct name, such as Quorum or Witness to the Quorum disk.
Configuring shared disks
Use the Windows Disk Management utility to configure additional shared disk resources. Verify that all shared disks are formatted as NTFS and are designated as Basic.
Additional shared disk resources are automatically added into the cluster as physical disk resources during the installation of cluster services.
Verifying disk access and functionality
Write a file to each shared disk resource to verify functionality.
Configuring the public network adapter
105
At this time, shut down the first node, power on the next node and repeat the Verifying Disk Access and
Functionality step above for all cluster nodes. When it has been verified that all nodes can read and write from the disks, turn off the cluster nodes and power on the first, and then continue with this guide.
Configuring cluster service software
Failover Cluster Management provides the ability to manage, monitor, create and modify clusters and cluster resources.
Using Failover Cluster Management
Failover Cluster Management shows information about the groups and resources on all of your clusters and specific information about the clusters themselves.
Creating a cluster
During the creation of the cluster, Failover Cluster Management will analyze and verify the hardware and software configuration and identify potential problems. A comprehensive and easy-to-read report is created, listing any potential configuration issues before the cluster is created.
Some issues that can occur are:
• No shared disk for the Quorum disk. A shared disk must be created with a NTFS partition at least 512 MB in size.
• Use of DHCP addresses for network connections. All Network adapters must be configured with static IP addresses in a cluster configuration.
• File Services for Macintosh and Service for NetWare are not supported in a cluster configuration.
• Dynamic Disks are not supported in a cluster configuration.
• Errors appear on a network adapter that is not configured or does not have an active link. If the network adapter is not going to be used it should be disabled.
Adding nodes to a cluster
Only the Quorum disk should be accessible by the new node while the new node is not a member of the cluster. The new node should not have access to the other LUNs in the cluster until after it has joined the cluster. After the node has joined the cluster, the LUNs may be presented to the new node. Move the physical disk resources over to the new node to confirm functionality.
CAUTION:
Presenting other LUNs to the non-clustered system could lead to data corruption.
Geographically dispersed clusters
Cluster nodes can be geographically dispersed to provide an additional layer of fault tolerance.
Geographically dispersed clusters are also referred to as stretched clusters.
The following rules must be followed with geographically dispersed clusters:
• A network connection with latency of 500 milliseconds or less ensures that cluster consistency can be maintained. If the network latency is over 500 milliseconds, the cluster consistency cannot be easily maintained.
• All nodes must be on the same subnet.
Cluster groups and resources, including file shares
The Failover Cluster Management tool provides complete online help for all cluster administration activities.
106 Configuring cluster service software
Cluster resources include administrative types of resources as well as file shares. The following paragraphs include overview and planning issues for cluster groups, cluster resources, and clustered file shares.
Creating and managing these resources and groups must be managed through Failover Cluster
Management.
Cluster group overview
A default cluster group is automatically created when the cluster is first created. This default cluster group contains an Internet Protocol (IP) Address resource, a Network Name resource, and the Quorum disk resource. When the new cluster is created, the IP address and the cluster name that were specified during setup are set up as the IP address and network name of this default cluster group.
CAUTION:
Do not delete or rename the Cluster Group or IP Address. Doing so results in losing the cluster and requires reinstallation of the cluster.
When creating groups, the administrator's first priority is to gain an understanding of how to manage the groups and their resources. Administrators may choose to create a resource group and a virtual server for each node that will contain all resources owned by that node, or the administrator may choose to create a resource group and virtual server for each physical disk resource. Additionally, the administrator should try to balance the load of the groups and their resources on the cluster between the nodes.
Node-based cluster groups
Creating only one resource group and one virtual server for each node facilitates group and resource administration. This setup allows administrators to include all file share resources under one group. Clients access all of the resources owned by one node through a virtual server name.
In node-based cluster groups, each group has its own network name and IP address. The administrator decides on which node to place each physical disk resource. This configuration provides a very coarse level of granularity. All resources within a group must remain on the same node. Only two IP addresses and network names are required. This configuration creates less overhead for resource and network administration. A possible disadvantage of this approach is that the resource groups can potentially grow large when many file shares are created.
Load balancing
The creation of separate cluster groups for each virtual server provides more flexibility in balancing the processing load on the cluster between the two nodes. Each cluster group can be assigned to a cluster node with the preferred owner parameter. For example, if there are two cluster groups, the cluster could be set up to have the first cluster group owned by Node A and the second cluster group owned by Node B. This allows the network load to be handled by both devices simultaneously. If only one cluster group exists, it can only be owned by one node and the other node would not serve any network traffic.
File share resource planning issues
SMB and NFS are cluster-aware protocols that support the Active/Active cluster model, allowing resources to be distributed and processed on both nodes at the same time. For example, some NFS file share resources can be assigned to a group owned by a virtual server for Node A and additional NFS file share resources can be assigned to a group owned by a virtual server for Node B.
Configuring the file shares as cluster resources provides for high availability of file shares. Because the resources are placed into groups, ownership of the files can easily move from one node to the other, as circumstances require. If the cluster node owning the group of file shares should be shut down or fail, the other node in the cluster will begin sharing the directories until the original owner node is brought back on line.
At that time, ownership of the group and its resources can be brought back to the original owner node.
Cluster group overview
107
Resource planning
Procedure
1. Create a cluster group for each node in the cluster with an IP address resource and a network name resource.
Cluster resource groups are used to balance the processing load on the servers. Distribute ownership of the groups between the virtual servers.
2. For NFS environments, configure the NFS server.
NFS specific procedures include entering audit and file lock information as well as setting up client groups and user name mappings. These procedures are not unique to a clustered deployment and are detailed in the Microsoft Services for NFS section within the “Other network file and print services” chapter. Changes to NFS setup information are automatically replicated to all nodes in a cluster.
3. Create the file share resources.
4. Assign ownership of the file share resources to the resource groups.
a. Divide ownership of the file share resource between the resource groups, which are in turn distributed between the virtual servers, for effective load balancing.
b. Verify that the physical disk resource for this file share is also included in this group.
c. Verify that the resources are dependent on the virtual servers and physical disk resources from which the file share was created.
Permissions and access rights on share resources
File Share and NFS Share permissions must be managed using the Failover Cluster Management tool versus the individual shares on the file system themselves via Windows Explorer. Administering them through the
Failover Cluster Management tool allows the permissions to migrate from one node to other. In addition, permissions established using Explorer are lost after the share is failed or taken offline.
NFS cluster-specific issues
For convenience, all suggestions are listed below:
• Back up user and group mappings.
To avoid loss of complex advanced mappings in the case of a system failure, back up the mappings whenever the mappings have been edited or new mappings have been added.
• Map consistently.
Groups that are mapped to each other should contain the same users and the members of the groups should be properly mapped to each other to ensure proper file access.
• Map properly.
◦ Valid UNIX users should be mapped to valid Windows users.
◦ Valid UNIX groups should be mapped to valid Windows groups.
◦ Mapped Windows user must have the “Access this computer from the Network privilege” or the mapping will be squashed.
◦ The mapped Windows user must have an active password, or the mapping will be squashed.
• In a clustered deployment, create user name mappings using domain user accounts.
Because the security identifiers of local accounts are recognized only by the local server, other nodes in the cluster will not be able to resolve those accounts during a failover. Do not create mappings using local user and group accounts.
• In a clustered deployment, administer user name mapping on a computer that belongs to a trusted domain.
108 Resource planning
If NFS administration tasks are performed on a computer that belongs to a domain that is not trusted by the domain of the cluster, the changes are not properly replicated among the nodes in the cluster.
• In a clustered deployment, if PCNFS password and group files are being used to provide user and group information, these files must be located on each node of the system.
Example: If the password and group files are located at c:\maps on node 1, then they must also be at c:
\maps on node 2. The contents of the password and group files must be the same on both nodes as well.
These password and group files on each server node must be updated periodically to maintain consistency and prevent users or groups from being inadvertently squashed.
Non cluster aware file sharing protocols
Services for Macintosh (SFM), File and Print Services for NetWare, HTTP file sharing protocols are not cluster aware and will experience service interruption if installed on a clustered resource during failover events of the resource. Service interruptions will be similar to those experienced during a server outage. Data that has not been saved to disk prior to the outage will experience data loss. In the case of SFM, it is not supported because SFM maintains state information in memory. Specifically, the Macintosh volume index is located in paged pool memory. Using SFM in clustered mode is not supported and may result in data loss similar in nature to a downed server should the resource it is based on fails over to the opposing node.
Adding new storage to a cluster
Present the new storage to one node in the cluster. This can be accomplished through selective storage presentation or through SAN zoning.
The tasks described below are used to add storage to a cluster. See the online help for clustering for additional details.
Creating physical disk resources
A physical disk resource must reside within a cluster group. An existing cluster group can be used or a new cluster group must be created. For information on creating disk resources, see the cluster online help topic
Physical Disk resource type.
NOTE:
• Physical disk resources usually do not have any dependencies set.
• In multi-node clusters it is necessary to specify the node to move the group to. When a cluster group is moved to another node, all resources in that group are moved.
• When a physical disk resource is owned by a node, the disk appears as an unknown, unreadable disk to all other cluster nodes. This is a normal condition. When the physical disk resource moves to another node, the disk resource then becomes readable.
Creating file share resources
To create a file share resource, see two clustering online help topics:
• Create a cluster-managed file share.
• Using a server cluster with large numbers of file shares.
NOTE:
• A file share resource must reside in the same cluster group as the physical disk resource it will reside on.
• The physical disk resource specified in this step must reside in the same cluster group as specified in the beginning of this wizard.
Non cluster aware file sharing protocols
109
Creating NFS share resources
To create an NFS share resource, see MSNFS administration on a server cluster.
Shadow copies in a cluster
It is recommended that the location of the cache file be placed on a separate disk from the original data. In this case, a physical disk resource for the cache file disk should be created in the same cluster group as the intended Shadow Copy resource and the volume for which snapshots will be enabled. The resource should be created prior to the establishment of Shadow Copies. The Shadow Copy resource should be dependent on both the original physical disk resource and the physical disk resource that contains the cache file.
For more information, see the following topics in the clustering online help:
• Using Shadow Copies of Shared Folders in a server cluster.
• Enable Shadow Copies for shared folders in a cluster.
Extend a LUN in a cluster
To extend a LUN on a storage array in a cluster, review the requirements and procedures from the storage array hardware provider for expanding or extending storage.
MSNFS administration on a server cluster
The Microsoft Services for Network File System (NFS) online help provides server cluster information for the following topics:
• Configuring shared folders on a server cluster
◦ Configuring an NFS share as a cluster resource.
◦ Modifying an NFS shared cluster resource.
◦ Deleting an NFS shared cluster resource.
• Using Microsoft Services for NFS with server clusters
◦ Understanding how Server for NFS works with server clusters.
◦ Using Server for NFS on a server cluster.
• Configuring User Name Mapping on a server cluster
For further details, see the online help for Microsoft Services for Network File System.
Best practices for running Server for NFS in a server cluster
• Stop Server for NFS before stopping the server cluster.
• Ensure share availability when a node fails.
• Use the appropriate tool to manage Network File System (NFS) share cluster resources.
• Avoid conflicting share names.
• Ensure the availability of audit logs.
• Move file shares or take them offline before stopping Server for NFS.
• Take resources offline before modifying.
• Administer Server for NFS only from computers in a trusted domain.
• Restart the Server for NFS service after the cluster service restarts.
• Choose the appropriate sharing mode.
• Use the command line properly when creating or modifying NFS share cluster resources.
• Use hard mounts.
• Use the correct virtual server name.
110 Creating NFS share resources
Print services in a cluster
The Windows Storage Server 2012 or 2016 Cluster service implementation increases availability of critical print servers. A print spooler service on a clustered print server may be hosted on any of the nodes in the cluster. As with all cluster resources, clients should access the print server by its virtual network name or virtual IP address.
Creating a cluster printer spooler
Printer spoolers should be created in a separate group dedicated to this purpose for ease of management.
For each printer spooler, a physical resource is required to instantiate the print spooler resource. In some cases, dedicated physical resources are not available and hence sharing of the physical resource among other members of the group is acceptable, remembering that all members of a group are managed as a unit.
Hence, the group will failover and failback as a group.
To create a printer spooler:
Procedure
1. Create a dedicated group (if required).
2. Create a physical resource (disk) (if required, see note).
3. Create an IP address resource for the Virtual Server to be created (if required, see note).
4. Create a Virtual Server Resource (Network Name) (if required, see note).
NOTE:
If the printer spool resource is added to an existing group with a physical resource, IP address, and virtual server resource, steps 1-4 are not required.
5. Create a Print Spool resource.
6. To add a printer to the virtual server:
a. Double-click the printers and faxes icon.
b. Right-click the new screen, and then click add printer. A wizard starts.
c. Click create a new port, and then click Next.
d. Enter the IP address of the network printer.
e. Update the Port Name if desired, click Next, and then click Finish.
f. Select the appropriate driver, and then click Next.
g. If presented with a dialog to replace the driver present, click keep the driver, and then click Next.
h. Name the printer, and then click Next.
i. Provide a share name for the printer for network access, and then click Next.
j. Provide location information and comments, and then click Next.
k. Click Yes to print a test page, click Next, and then click Finish.
l. A dialog box appears regarding the test page. Select the appropriate answer.
The Printer Spool is now a clustered resource.
Advanced cluster administration procedures
Failing over and failing back
As previously mentioned, when a node goes offline, all resources dependent on that node are automatically failed over to another node. Processing continues, but in a reduced manner, because all operations must be processed on the remaining node(s). In clusters containing more than two nodes, additional fail over rules can be applied. For instance, groups can be configured to fail over different nodes to balance the additional work load imposed by the failed node. Nodes can be excluded from the possible owners list to prevent a resource
Print services in a cluster
111
from coming online on a particular node. Lastly the preferred owners list can be ordered, to provide an ordered list of failover nodes. Using these tools, the failover of resources can be controlled with in a multinode cluster to provide a controlled balanced failover methodology that balances the increased work load.
Because operating environments differ, the administrator must indicate whether the system will automatically fail the resources (organized by resource groups) back to their original node or will leave the resources failed over, waiting for the resources to be moved back manually.
NOTE:
If the storage system is not set to automatically fail back the resources to their designated owner, the resources must be moved back manually each time a failover occurs.
Restarting one cluster node
CAUTION:
Restarting a cluster node should be done only after confirming that the other node(s) in the cluster are functioning normally. Adequate warning should be given to users connected to resources of the node being restarted. Attached connections can be viewed through Server Manager on the storage system
Desktop using Terminal Services. From Failover Cluster Manager, select a file server role and then view the shares for that role.
The physical process of restarting one of the nodes of a cluster is the same as restarting a storage system in single node environment. However, additional caution is needed.
Restarting a cluster node causes all cluster resources served by that node to fail over to the other nodes in the cluster based on the failover policy in place. Until the failover process completes, any currently executing read and write operations will fail. Other node(s) in the cluster will be placed under a heavier load by the extra work until the restarted node comes up and the resources are moved back.
Shutting down one cluster node
CAUTION:
Shutting down a cluster node must be done only after confirming that the other node(s) in the cluster are functioning normally. Adequate warning should be given to users connected to resources of the node being shutdown.
Shutting down a cluster node causes all cluster resources served by that node to fail over to the other node(s). This causes any currently executing client read and write operations to fail until the cluster failover process completes. The other node(s) are placed under a heavier load by the extra work until the second node is powered up and rejoins the cluster.
Powering down the cluster
The power down process for the storage system cluster is similar to the process for a single node, but with the cluster, extra care must be taken with the storage subsystem and the sequence of the shutdown.
The power down process is divided into two main steps:
Procedure
1. Shutting down the cluster nodes.
2. Removing power from the cluster nodes.
The sequence of these steps is critical. The devices must be shut down before the storage subsystem.
Improperly shutting down the nodes and the storage subsystem causes corruption and loss of data.
112 Restarting one cluster node
CAUTION:
Before powering down the cluster nodes, follow the proper shutdown procedure as previously illustrated.
See Shutting down one cluster node. Only one cluster node should be shut down at a time.
Powering up the cluster
The power up process for the storage system cluster is more complex than it is for a single node because extra care must be taken with the storage subsystem.
The sequence of the power up steps is critical. Improper power up procedures can cause corruption and loss of data.
CAUTION:
Do not power up the cluster nodes without first powering up the storage subsystem, and verifying it is operating normally.
Nodes should be powered up separately allowing one node to form the cluster prior to powering up the additional node(s). To power up the cluster nodes:
Procedure
1. After the storage subsystem is confirmed to be operating normally, power up a single node. Wait for the node to come completely up before powering up the subsequent node(s).
If more than one node is powered up at the same time, the first node that completes the sequence gains ownership of the cluster quorum and controls the cluster database. Designate a particular node as the usual cluster quorum owner by always powering up that node first and letting it completely restart before powering up additional cluster node(s).
2. Power up the additional cluster node(s). Each node should be allowed to start fully, prior to starting a subsequent node.
Powering up the cluster
113
Troubleshooting, servicing, and maintenance
Cause
The HPE StoreVirtual 3000 File Controller provides several monitoring and troubleshooting options. You can access the following troubleshooting alerts and solutions to maintain the system health:
• Notification alerts
• System Management Homepage (SMH)
• Hardware component LEDs
• HPE and Microsoft support websites
• HPE Insight Remote Support software
• Microsoft Systems Center Operations Manager (SCOM) and Microsoft websites
• Cluster Specific Troubleshooting
• HPE SIM 7.4 or later, which is required for proper HPE StoreVirtual 3000 File Controller/HP SIM integration.
NOTE:
◦ For the latest version of HPE SIM, refer to the HPE SPOCK website (http://www.hpe.com/
storage/spock).
◦ Integration with HPE SIM is only supported using the WBEM/WMI interfaces. Do not attempt to configure HP SIM to use the ProLiant SNMP agents, because the configuration is untested and unsupported. The ProLiant SNMP agents are enabled on the HPE StoreVirtual 3000 File
Controller by default and must not be disabled as they are used for internal management functions. If they are enabled for external client consumption, HPE SIM must be configured so it does not attempt to communicate with these agents.
IMPORTANT:
You must execute the Update-StorageProviderCache -DiscoveryLevel 3 –PassThru command when you connect a storage device to the server for the first time.
Generic Windows event based troubleshooting
Event Viewer can be used for event analysis. When Event Viewer is opened, the left-hand pane displays a folder view, where you can find all of the different event logs, as well as the views that can be customized with events from many logs at once. For instance, the Administrative Events view in recent versions of Windows displays all of the Error, Warning, and Critical events whether they originated from the Application log or the
System log. The middle pane displays a list of events, and clicking on it will display the details of the event in the preview pane – or you can double-click on any of them to pull it up in a separate window, which can be handy when you are looking through a big set of events and want to find all the important things before beginning an internet search. The right-hand pane gives you quick access to actions like creating custom views, filtering, or even creating a scheduled task based on a particular event.
Maintaining HPE StoreVirtual 3000 File Controller
HPE recommends the following maintenance guidelines for upgrading your system components (operating system, software, firmware, and drivers), depending on your environment:
IMPORTANT:
It is recommended that HPE StoreEasy Service Releases be installed as released. These service releases contain important Windows Updates and Hot Fixes.
• If security updates are important for your operating environment, you can:
114 Troubleshooting, servicing, and maintenance
◦ Use Microsoft Windows Update to download updates.
◦ Download and install specific security updates as needed from the Microsoft Security TechCenter website:http://technet.microsoft.com/security/default.aspx
• If your maintenance policy is to only update servers to the most current and tested versions of the system components, you can install the latest HPE service release. To find the latest service release, go to
https://www.hpe.com/support and search for your specific product. You can also register your product on the HPE support and drivers page to receive notification of new service releases for your product.
Service releases are released periodically. The latest service release requires the previous service release as a prerequisite. For more information, see the latest service release notes.
• If your maintenance policy allows you to update servers to the most current versions of the system components for which HPE StoreVirtual 3000 File Controller has not completed testing and bundled as a service release, then apply the latest HPE Service Pack for Proliant (SPP) from http://www.hpe.com/go/
spp. The latest firmware and driver updates can be retrieved for your specific product or the underlying server platform from https://www.hpe.com/support by selecting HPE Server, Storage and Networking and then searching for the server platform (for example, HPE Proliant DL120 Gen9 Server platform) to find specific updates.
• HPE recommends updating the operating system, software, firmware, and NIC drivers simultaneously (in the same update window) to ensure proper operation of HPE StoreVirtual 3000 File Controller.
Determining the current HPE StoreVirtual 3000 File
Controller software version
1. Log in to the server blade.
2. Open a command window.
3. Enter the reg query command as shown in the following example:
C:\> reg query HKLM\Software\Wow6432Node\Hewlett-Packard Enterprise
\StorageWorks /s
The following information appears:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Hewlett-Packard Enterprise
\StorageWorks\QuickRestore
BASE REG_SZ 5.00.0.4
QRVersion REG_SZ 5.00.0a.145
The QRVersion field lists the version.
HPE System Management Homepage
The HPE System Management Homepage (SMH) is a web-based interface that consolidates and simplifies single system management for HPE servers and storage. The SMH is the primary tool for identifying and troubleshooting hardware issues in HPE StoreVirtual 3000 File Controller. You may choose this option to diagnose a suspected hardware problem. Go to the SMH main page and open the Overall System Health
Status and the Component Status Summary sections to review the status of the HPE StoreVirtual 3000 File
Controller hardware.
By aggregating the data from HPE web-based agents and management utilities, the SMH provides a common, easy-to-use interface for displaying the following information:
• Hardware fault and status monitoring
• System thresholds
Determining the current HPE StoreVirtual 3000 File Controller software version
115
• Diagnostics
• Software and firmware version control for an individual server
The SMH Help menu provides documentation for using, maintaining, and troubleshooting the application. For more information about the SMH software, go to https://www.hpe.com/support/manuals and enter System
Management Homepage in the Search box. Select HPE System Management Homepage Software. A list of documents and advisories is displayed. To view SMH user guides, select User Guide.
Starting the System Management Homepage application
To start the application, double-click the HP System Management Homepage desktop shortcut or enter https://hostname:2381/ in Internet Explorer. The hostname can be localhost or the IP address of the server you want to monitor. To log into SMH, enter the same username and password you use to log in to the server. Users who have administrative privileges on the server have the same privileges in the SMH application.
To view the SMH of one server from another server, you must modify the Windows firewall settings as follows:
Procedure
1. Open the Control Panel and select System Security > Windows Firewall > Allowed Programs.
2. Select Allow another program and click Browse in the Add a Program dialog box.
3. Navigate to C:\hp\hpsmh\bin and select hpsmhd. Click Open and then click Add. HP System
Management Homepage displays in the Allowed Programs and Features window.
4. Select Home/work (Private) and Public and click OK.
5. To access the SMH on another server, enter the following URL:
NOTE:
Port 2381 may need to be opened in the system’s firewall, if applicable.
System Management Homepage main page
System Management Homepage main page shows the SMH main page.
116 Starting the System Management Homepage application
Figure 30: System Management Homepage main page
The page provides system, subsystem, and status views of the server and displays groupings of systems and their status.
Troubleshooting, servicing, and maintenance
117
NOTE:
• NICs will display with a failed status (red icon) if they are unplugged. To remove unused NICs from the system status, you can disable them by selecting
Control Panel > Hardware > Device Manager, right-click on the specific NIC, and then select
Disable.
• When you remove a disk or disconnect a cable, the SMH interface might not display alerts when you click the Refresh button. You can force a hard refresh by clicking the Home button or by navigating to the problem area. The default refresh interval is two minutes. To change the interval in the
Settings menu, select Autorefresh, and then Configure Page refresh settings. The minimum interval is five seconds and the maximum is 30 minutes.
Overall System Health Status
A webapp sets the value of the Overall System Health Status icon by using a predefined heuristic. If no webapp can determine the status, the worst possible status is displayed in the Component Status Summary section.
Component Status summary
The Component Status Summary section displays links to all subsystems that have a critical, major, minor, or warning status. If there are no critical, major, minor or warning items, the Component Status Summary section displays no items.
Enclosure
This section provides information about the enclosure cooling, IDs, power, Unit Identification LED, PCIe devices, and I/O modules.
NOTE:
A large number of disk errors may indicate that an I/O module has failed. Inspect the I/O module LEDs on the system and any disk enclosures, and replace any failed component. A large number of disk errors may indicate that an I/O module has failed. Inspect the I/O module LEDs on the HPE StoreVirtual
3000 File Controller system and any disk enclosures, and replace any failed component.
• Because both a system and drive fan are required, the maximum and minimum number of fans required is two. If either fan becomes degraded, the system could shut down quickly. Because the fans are not mutually redundant, even if the status of a single fan has changed, the new status is reported immediately in the Components Status Summary section on the SMH main page.
• When the Enclosure Manager IP address is set incorrectly, the enclosure status displayed is Lost communication. Because the Enclosure Manager has lost communication with the external network, none of the other items in the Enclosure Information section can be displayed.
Network
This section shows the status of the network connections.
Storage
This section displays information about the Smart Array and storage controllers within HPE StoreVirtual 3000
File Controller. The Storage System page is organized as a left panel and a main page:
118 Troubleshooting, servicing, and maintenance
Figure 31: Storage system
The left panel provides links to information about the following items:
• Controller
Select a storage controller to view its type, status, firmware version, and serial number.
• Physical Drives
This section provides an overview of all disk drives attached to the controller. Drives are identified and grouped as assigned, unassigned, and spare drives. Each physical drive is listed as a separate entry in the Storage System submenu. Select any of the physical drives to display more information about the drive.
Troubleshooting, servicing, and maintenance
119
NOTE:
Spare drives are only used when a disk drive fails. Until a spare drive is used, it remains offline and its LEDs will remain off.
• Logical DrivesA list of logical drives associated with the controller appears in the left panel tree view.
Select one of the logical volume entries to display the status of the volume, fault tolerance (RAID level), and capacity (volume size). A link to the logical volume storage pool is also displayed.
• Tape Drives
This section provides information about tape drives, if they are included.
• Storage Boxes
This section provides an overview of the disk drives that are listed individually in the Physical Drives section.
System
This section displays status for various system components.
Version Control
This section provides information about the Version Control Agent.
Operating system
This section provides information about the operating system storage volumes.
Software
This section provides information about system firmware and software.
Known issues
Known issues identifies known issues with HPE StoreVirtual 3000 File Controller when the HPE StoreVirtual
3000 File Controller Administrator Guide was last published and provides workarounds to mitigate them.
Table 7: Known issues
Issue Resolution
HPS Reports 9.8 execution crashes .
Create virtual disk for file server wizard is not visible on top of ICT at times, but the wizard launches.
Default cluster ICT opens post installation for standalone system.
In Windows Server 2016 the icons does not show on taskbar.
Validate & Create Cluster in ICT fails.
Run RPC locator services from services.msc and then run HPSReports again. in NFS RPC info.
Minimize ICT the wizard is opened behind ICT window.
Do not use the Initial Configuration Task started in background the installation will launch the correct ICT that needs to be used.
User needs to turn on the taskbar color manually.
It has to validate the configuration and proceed with the cluster creation.
This issue may not appear in customized ICT.
Table Continued
120 Known issues
Issue Resolution
In StoreVirtual 3000 File
Controller after clicking YES in the cluster option, user have to manually accept EULA on the remote node to proceed.
Cluster creation needs the cluster service to be running but if the domain user doesn't have admin privilege, the service remains in disabled state, causing the cluster creation to fail.
After clicking YES in cluster option in primary node, the remote node has to be configured and the EULA has to be accepted automatically.
Domain user needs to be added to admin group for creating cluster.
On some HPE StoreVirtual 3000
File Controller systems, a momentary press of the power button results in an operating system shutdown.
Confirm that the power settings for the HPE StoreVirtual 3000 File
Controller system ignore the power button or disable the power button in the system BIOS.
There may be errors from DFS and NFS logged in the Event
Viewer after the HPE
StoreVirtual 3000 File Controller system is configured.
These errors can be ignored.
Mounted data volumes are not remounted after performing a system recovery. These data volumes are not damaged or destroyed but they are not visible after a system recovery operation.
To restore the mount points to their original locations, you must record them prior to running system recovery.
1. Using Windows Disk Manager, record the mount points of the volumes within the root directory of each volume.
2. After running system recovery, scan the system to find data volumes that are not assigned drive letters.
3. Temporarily mount the volumes that are not assigned drive letters.
4. Locate the recorded list of mount points and remount the temporarily mounted volumes to the correct locations according to the record.
Network interfaces that are configured to use DHCP might not retrieve a DHCP address immediately if the configuration and network validation fails for these interfaces in the Network
Configuration Tool.
Perform the following steps to restart the network interface:
1. Open a command prompt and enter ncpa.cpl to open the network control panel.
2. Right-click on the interface that is configured for DHCP and does not have an address, and then select Disable.
3. Right-click on the interface that is configured for DHCP and does not have an address, and then select Enable.
Table Continued
Troubleshooting, servicing, and maintenance
121
Issue Resolution
After initial installation or a system recovery, the connection status for the second node is listed as “The second node is not accessible”.
You will need to obtain the Cluster Internal IP address and add it manually to the registry:
1. Use iLO or Remote Desktop to log in to the second node and retrieve the Cluster Internal IP address.
2. Open a Command Prompt or PowerShell on the first node.
3. Enter the following command, replacing <ClusterInternalIP> with the IP address obtain in step 1: reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft
\OEMOOBE /v RemoteNodeIpAddress /t REG_SZ /d
<ClusterInternalIP> /f
The message "Display will be complete when the storage inventory has finished..." appears in Server Manager and pool data does not display.
This issue occurs if the server has been added to the domain and a cluster has been created. Local administrators cannot view this information. Once a server is added to a domain and a cluster is created, you must log in to Server Manager as a domain user.
Network teaming cannot be configured during initial system configuration.
Do not create network teams until after the initial configuration tasks have been completed. If a system is to be connected to a network where specific VLANs with VLAN tagging enabled (for example, for connecting to a domain controller), it is recommended that the network switch be temporarily configured to pass untagged network packets on the specific
VLAN or to configure the network interface properties to operate using the specific VLAN ID. Configuring VLAN settings is accomplished by opening the properties dialog for the network interface and then configuring the network adapter by clicking Configure.
Table Continued
122 Troubleshooting, servicing, and maintenance
Issue Resolution
During initial system configuration, the Initial
Configuration Tasks window may display the following message:
Connecting to remote server 169.254.2.111
failed with the following error message:
The WinRM client cannot process the request. If the authentication scheme is different from
Kerberos, or if the client computer is not joined to a domain, then
HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting.
Use winrm.cmd to configure TrustedHosts.
Note that computers in the TrustedHosts list might not be authenticated.
This may be cause by having multiple interfaces on the same network subnet as that used by the network interface names “Cluster Internal”. By default, the Cluster Internal network uses an APIPA address
(169.254.0.0/16). This is the default subnet used by other network interfaces that are connected and there is no DHCP server. This results in multiple network routes between nodes.
Disable or disconnect network interfaces that are connected to networks where no DHCP server is available. During the initial configuration you will be given the opportunity to assign network addresses to other network interfaces. After addresses are assigned the network interfaces can be reconnected or enabled.
Table Continued
Troubleshooting, servicing, and maintenance
123
Issue Resolution
When attempting to use Failover
Cluster Manager to add a File
Share to an HA File Server on the cluster, the Add Share wizard will not start.
Set the system level proxy to explicitly bypass the HA file servers. For example, instead of using the following command: netsh winhttp set proxy myproxy.fabrikam.com:80
"<local>" set the proxy using a command like the following: netsh winhttp set proxy myproxy.fabrikam.com:80
"<local>;*.fabrikam.com"
Also, attempting to use Failover
Cluster Manager to view any existing shares on file servers in the cluster, just results in a perpetual “Loading” message.
This happens when a system level HTTP proxy server is set.
Some users will require a system level proxy to make
Cluster Aware Updating work, but if one is set, it is important to explicitly prevent access to your
HA file servers from using the proxy.
In this example, “*.fabrikam.com” is the client access point used on the HA file servers.
The SMI-S provider registration with HPE StoreVirtual 3000 File
Controller might fail due to the following reason:
• No network connectivity existing between the array and node.
To register SMI-S provider, ensure that the array is reachable from the node. Perform the following steps on all nodes:
1. Open an elevated PowerShell command prompt.
2. Enter the following commands for HTTP and HTTPs SMI-S provider:
a. Register-SmisProvider -ConnectionUri http://
<ipadress>:<port-no>.
NOTE:
For HTTPs port SMI-S provider, enter Register-
SmisProvider -ConnectionUri https://
<ipadress>:<port-no>.
b. 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.
Virus Scanning Recommendation
Using Virus scanning might lead to instability in a system in specific conditions. For Microsoft Virus scanning recommendation, refer to Virus scanning recommendations.
Hewlett Packard Enterprise Support websites
To troubleshoot problems with the HPE StoreVirtual 3000 File Controller, select HPE Server, Storage and
Networking at the HPE Support & Drivers website (https://www.hpe.com/support). Enter HPE StoreVirtual
3000 File Controller or component information (for example, SAS I/O module). After entering the details, use the following links for troubleshooting information:
124 Virus Scanning Recommendation
• Drivers, software & firmware. —Provides drivers and software for your operating system.
• Top issues & solutions—Provides a listing of customer notices, advisories, and bulletins applicable for the product or component.
• Manuals—Provides the latest user documentation applicable to the product or component. User guides can be a useful source for troubleshooting information. For HPE StoreVirtual
3000 File Controller, the following ProLiant server manuals may be useful for troubleshooting assistance:
◦ The following guides contain specific troubleshooting information for the server.
◦ ProLiant Gen9 Troubleshooting Guide, Volume I: Troubleshooting
◦ ProLiant Gen9 Troubleshooting Guide, Volume II: Error messages
You can access these manuals at http://www.hpe.com/support/proliantgen9/docs.
IMPORTANT:
Some troubleshooting procedures found in ProLiant server guides may not apply to particular HPE
StoreVirtual 3000 File Controller model. If necessary, check with your HPE Support representative for further assistance.
For HPE StoreVirtual 3000 File Controller manuals, go to www.hpe.com/support/Manuals.
For software-related components and issues, online help or user guide documentation may offer troubleshooting assistance. Known issues, workarounds and service releases are addressed in this guide or the release notes.
◦ Customer notices—Address informational topics about the HPE StoreVirtual 3000 File Controller.
◦ Customer advisories—Address know issues and solutions or workarounds.
NOTE:
You must register for Subscriber's Choice to receive customer advisories and notices.
Microsoft Systems Center Operations Manager
Microsoft Systems Center Operations Manager (SCOM) provides comprehensive monitoring, performance management, and analysis tools to maintain Windows OS and application platforms. This solution allows you to monitor Microsoft Windows environments and HP storage products through a common OpsMgr console. To download HP management packs for Microsoft System Center Operations Manager, including installation, configuration, and usage documentation, visit the HP Management Packs for Microsoft Systems Center site at:
http://www.hpe.com/info/Quickspecs-Overview
Microsoft Systems Center Operations Manager
125
Removing and replacing hardware components
For information on removing and replacing a hardware component, follow the component removal and replacement instructions in the appropriate ProLiant user guide. The following is the ProLiant model for HPE
StoreVirtual 3000 File Controller product:
• HPE StoreVirtual 3000 File Controller—HPE Proliant DL120 Gen9 Server platform.
NOTE:
After replacing the system board, you must ensure that the correct Product ID is reflected in the system
BIOS and that the product name is installed on the replacement part. The correct product name is important for applications such as System Insight Manager and Insight Remote Support. To install the correct product name, browse to the C:\nas\components\support\naming folder. Locate and run the Smart Component that applies to your system. After running the Smart Component, you must shut down and then restart your system for the changes to take effect. On multi-node clusters, such as HPE
StoreVirtual 3000 File Controller systems, HPE recommends that you move cluster resources to another node before shutting down the node that is being renamed. If you run the incorrect Smart Component, the product name will be set incorrectly, but it will not affect your system in any other way.
Surface Scan Analysis
Hewlett Packard Enterprise Smart Array controllers perform a background surface analysis during inactive periods, continually scanning all drives for media defects. Hewlett Packard Enterprise Smart Array controllers can also detect media defects when accessing a bad sector during busy periods. If an Hewlett Packard
Enterprise Smart Array controller finds a recoverable media defect, the controller automatically remaps the bad sector to a reserve area on the disk drive. If the controller finds an unrecoverable media defect and you have configured a fault-tolerant logical drive, the controller automatically regenerates the data and writes it to the remapped reserved area on the disk drive. Surface Scan Analysis interval can be tuned from UI and it should be noted that, disabling Surface Scan Analysis will prevent the controller from proactively finding and correcting disk surface errors, which may lead to data loss.
Cluster Specific Issues
This section describes the cluster specific issues and the troubleshooting methods.
During the QR process the ILO White screen appears.
126 Removing and replacing hardware components
Figure 32: ILO White Screen
Perform the following to avoid this error:
• Reset the server.
• Press F9.
• Select System Configuration
⇒BIOS/Platform Configuration (RBSU)⇒PCI Device Enable/Disable .
• Select Slot 2: HP Store Fabric 8Gb Dual Port PCI-e FC HBA – FC and disable.
Figure 33: System Settings
• Press F10 to save the changes. Then Exit and Reboot.
Troubleshooting, servicing, and maintenance
127
No disk found in Slot0b pop-up appears during System Installation and Recovery screen QR process.
While QR’ing the server using the USB, the No disk found in Slot0b pop-up appears, if the USB is formatted as NTFS. Format the USB as FAT32 and not NTFS to avoid the pop-up.
The pop-up also appears if the SSD drives are not in the correct position. Check and place the drives in the correct slot.
Figure 34: QR error
Not a valid configuration…. pop-up appears in System Installation and Recovery window during the QR process.
Perform the following steps to avoid this erorr:
• Reset the server.
• Press F10 (Intelligent Provisioning).
• Select HP Smart Storage Administrator (HPSSA).
• Delete all logical drives and create a fresh logical drive.
• Reset the server again and follow the QR process.
Validation of cluster fails in Failover Cluster Manager. The configuration is not suitable for Clustering message is displayed.
128 Troubleshooting, servicing, and maintenance
Perform the following steps to troubleshoot the above issue:
• Check the Validation report.
• If the Storage fails, map the shared storage to both the nodes with which cluster is to be made.
• If the Network fails, check the Internal cluster cabling.
Cluster service not running in services.msc
In this case, firstly, check if both the cluster nodes are up. Run powershell command Get-clusteras administrator in the node in which the cluster services is not running.
If the error persists, it means the node is no more part of the cluster. In this case, rejoin the node to the cluster using Connect to Cluster from the Failover Cluster Manager.
Could not start the Cluster Service on Local Computer
Figure 35: Services.msc
Ensure that everything is running correctly. Stop and restart the Cluster service or completely re-create the cluster after evicting the nodes and destroying it.
Create Cluster Wizard Errors
In Failover Cluster Manager, while adding IP of nodes with which cluster is to be created, an error message
The node cannot be contacted. Ensure the node is powered on and connected to network
Ensure that the node is powered on.
Troubleshooting, servicing, and maintenance
129
In a Failover Cluster Manager, while adding IP of nodes with which cluster is to be created, an error message
The computer <computer name> is joined to a cluster appears.
To make the node to be a part of the new cluster, the node has be disconnected from the previous cluster Run powershell.
Run powershell (Run as Administrator)Remove-ClusterNode command to remove the node from a failover cluster and try adding the node to the cluster again.
NOTE:
After the node is removed, it no longer functions as part of the cluster unless you add it back to the cluster.
Figure 36: Create Cluster wizard issue2
Failover Cluster Failure
130 Troubleshooting, servicing, and maintenance
Figure 37: Failover Cluster Failure
The failover cluster failover error results either due to hardware failure in one node of a two-node cluster or due to the operating system failure.
The hardware failure may be caused by a failure in the SCSI card or in the operating system. In such case, remove the failed node from the failover cluster using the Powershell command (Run as Administrator)
Remove-ClusterNode or Evict node from the Failover Cluster Manager. Address the hardware failure with the computer offline, bring the machine back up and add the repaired node back to the existing cluster.
In operating system failure, the node is offline, but is not irretrievably broken. Therefore, recover and validate the node again. Make necessary repairs, bring the computer back up and add the repaired node back to the failover cluster instance.
For more information, refer to: https://technet.microsoft.com/windows-server-docs/get-started/windows-
server-2016.
Troubleshooting, servicing, and maintenance
131
Recovering HPE StoreVirtual 3000 File
Controller
This chapter describes how to restore the HPE StoreVirtual 3000 File Controller system to its factory default state. You can perform a system recovery using the System Recovery DVD (if ordered). If you have not ordered the System Recovery DVD, you can download the free System Recovery image from https://
h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=P4A93-11001 and save the image file in a USB flash drive or DVD to perform system recovery. For information on creating a system
recovery USB flash drive or DVD, see Creating a USB flash drive with an image file from HPE Software
Depot and Creating a DVD with an image file from HPE Software Depot
NOTE:
Disconnect any external storage from that server prior to booting the server to recover the image.
Otherwise, you might experience a hang due to the system trying to enumerate the volumes in the external storage.
System Recovery DVD
The System Recovery DVD can be ordered optionally with HPE StoreVirtual 3000 File Controller. Using the
System Recovery DVD, you can install an image or recover from a catastrophic failure.
At any time, you may boot from the DVD and restore the server to the factory condition. This enables you to recover the system if all other means to boot the server fail.
While the recovery process makes every attempt to preserve the existing data volumes, you must have a backup of your data before recovering the system.
IMPORTANT:
All data on the original OS logical drive is erased during the recovery process.
During system recovery, you can replace the existing drives with drives of the same size or larger. HPE recommends that the replacement drives be the same type as the original drives, but it is not required.
However, drives in the same RAID group must all be the same type (you cannot mix drive types in a RAID group).
If you replace any disk drives and then perform a system recovery, you must ensure that the replacement drives do not contain a logical drive. Use the Option ROM Configuration for Arrays (ORCA) utility to delete logical drives. For more information about ORCA, see the Configuring Arrays on HPE Smart Array Controllers
Reference Guide, which is available at:
http://www.hpe.com/support/manuals
Using the System Recovery DVD to save system data
Boot the System Recovery DVD and when prompted, select Windows Recovery Environment. Perform the following steps:
Procedure
1. Select the keyboard layout.
2. Select Troubleshoot > Advanced Options > Command Prompt.
3. Enter WPEINIT and wait for approximately ten seconds before proceeding.
4. Enter IPCONFIG at the command prompt to confirm that the network interface has an IP address.
132 Recovering HPE StoreVirtual 3000 File Controller
NOTE:
• If your network is not using DHCP, manually assign the IP address and DNS information. The following are some examples of the commands for manually assigning an IP address:
◦ netsh interface ip set address "connection name" static 192.168.0.101
255.255.255.0 192.168.0.1
◦ netsh interface ip add dns "connection name" 208.67.222.222
◦ netsh interface ip add dns "connection name" 208.67.220.220 index=2
For more information on using the netsh command, go to https://technet.microsoft.com/en-
us/library/bb490943.aspx.
• Starting the network might take some time. Continue to the next step only after a valid IP address is assigned to the network interface.
5. Enter NET USE Z: \\servername\sharename at the command prompt, where \\servername
\sharename is the UNC path to a network share where the data will be copied.
6. If prompted, enter the username and password for the share that you are accessing.
When the share is mapped to the Z: drive, you can use Robocopy to copy files from the system to the network share. For more information on Robocopy, see https://technet.microsoft.com/library/
cc733145.aspx.
Drive letters are not assigned after a restore
When a system that has existing data volumes (non-operating system volumes) is restored using the System
Recovery DVD, the data volumes will not have drive letters assigned to them. This is by design. The volume labels are retained and can be used to identify the data volumes.
You can assign drive letters to volumes using diskpart.exe or Disk Management.
Procedure
1. To use Disk Management:
2. Click Start > Windows PowerShell.
3. The Windows PowerShell window opens.
4. Enter diskmgmt.msc and press Enter.
5. The Disk Management window opens.
6. Right-click the disk and partition the one for which you want to assign a drive letter and select Change
Drive Letter and Paths.
Creating a system recovery USB flash drive using the
System Recovery DVD
If you create a backup copy of the System Recovery DVD using a USB flash drive, you can also use it to restore the system.
To create a system recovery USB flash drive using the System Recovery DVD:
Procedure
1.
Obtain a blank 8 GB or larger USB flash drive.
2.
Insert the USB flash device into your workstation or laptop.
3.
Open an elevated command prompt with Administrator privileges.
4.
At the command prompt, enter diskpart.
5.
At the diskpart prompt, enter list disk.
6.
Identify the disk number that corresponds to the flash drive. This is typically the last disk listed.
Drive letters are not assigned after a restore
133
7.
Enter sel disk <USB drive number> (for example, sel disk 4).
8.
Enter clean. This deletes everything from the USB flash device, so ensure that you have the proper disk selected.
9.
Enter create par primary.
10. Enter sel par 1.
11. Enter format fs=fat32 quick.
12. Enter active to mark the partition as active.
13. Enter assign letter=<drive letter> to assign a drive letter to the USB drive (for example, assign letter=U).
14. Enter exit to quit diskpart context commands.
15. Insert the System Recovery DVD into the computer.
16. Using Windows Explorer or a comparable utility, open the DVD so that all contents are visible, including hidden and system files.
17. Select all files (including bootmgr) on the DVD.
18. Copy all of the selected files to the root of the USB flash drive.
Creating a USB flash drive with an image file from HPE
Software Depot
To create a system recovery USB flash drive with an image file from HPE Software Depot:
Procedure
1.
After downloading the image file you should mount the ISO locally so that you will have access to the files. Insert a USB flash drive into the system.
2.
Open an elevated command prompt with Administrator privileges, type diskpart, and then press Enter.
3.
Type list disk to determine the USB flash drive number or drive letter and press Enter.
4.
Note the drive number or drive letter of the USB flash drive.
5.
Type select disk <x>, where <x> is the drive number or drive letter of the USB flash drive and press
Enter.
6.
Type clean to delete the data from the USB flash drive and press Enter.
7.
Type create part pri to create a new primary partition in the USB flash drive and press Enter.
8.
Type select part 1 to select the partition that you just created and press Enter.
9.
Type format fs=fat32 quick to format the partition and press Enter.
IMPORTANT:
Since the server platforms are configured with Unified Extensible Firmware Interface (UEFI), you must format the USB flash drive as FAT32 instead of NTFS. To format the partition as FAT32, type format fs=fat32 quick and press Enter.
10. Type active to mark the partition as active and press Enter.
11. Type Exit to quit diskpart context commands and press Enter.
12. Copy the installation files included in the disc image file (ISO) to the root of the USB flash drive.
Creating a DVD with an image file from HPE Software Depot
To create a system recovery DVD with an image file from HPE Software Depot:
Procedure
1. Insert a blank dual layer DVD in the drive.
2. Locate the ISO image file on your system and then double-click it.
134 Creating a USB flash drive with an image file from HPE Software Depot
3. The Windows Disk Image Burner window appears.
4. Select the disk burner that you want to use. This is applicable only if you have more than one disk burners.
5. Select Verify disc after burning to verify that the ISO image has burned correctly.
6. Click Burn.
7. On completion, the appropriate status is displayed on the screen.
Restoring the factory image with a DVD or USB flash device
Procedure
1. Do one of the following:
a. For direct access, insert the System Recovery DVD or a bootable USB flash device (prepared with a
System Recovery image).
b. For remote management access, connect to the server using iLO from a client PC. Insert the System
Recovery DVD in the client PC or attach a bootable USB flash device that is prepared with a System
Recovery image.
2. Reboot the server blade to either the USB flash device or USB DVD drive.
3. The system BIOS attempts to boot to the USB device first by default. Watch the monitor output during the boot as you may need to press a key to boot to the USB media.
NOTE:
If directly connected, you may have to change the BIOS settings to ensure proper boot sequence. If connected remotely, you may have to change some iLO settings to ensure proper boot sequence.
4. Click the option for the StoreEasy System Recovery.
5. The recovery process completes with minimal user intervention required. The server automatically reboots more than once.
IMPORTANT:
Do not interrupt the recovery process.
6. When the recovery process completes, the Set Up Windows wizard appears. The next steps depend on
whether you are recovering both server blades (see Recovering both servers) or recovering a single
blade (see Recovering a single server).
7. Remove the directly connected DVD or flash device (or remotely connected iLO virtual DVD or flash device) from the server. Be sure to reconnect any external storage that was detached and reboot the server before proceeding.
Recovering both servers
If both server nodes are being recovered, the process is similar to configuring a new HPE StoreVirtual 3000
File Controller system delivered from the factory.
NOTE:
Although the recovery process restores the HPE StoreVirtual 3000 File Controller system to the factory version, it does not restore the EMU and iLO address configuration to the factory defaults. The EMU and iLO address configuration will be the same as it was prior to system recovery.
For each server, follow the steps in Restoring the factory image with a DVD or USB flash device.
Restoring the factory image with a DVD or USB flash device
135
Recovering a single server
If only one of the two server nodes is being recovered, the process is slightly more involved because you want to join the recovered server to an existing Windows failover cluster. If you do not have a functional
The following procedure describes how to re-image one of the server nodes of the HPE StoreVirtual 3000 File
Controller system, and then rejoin the server to the Windows failover cluster:
Procedure
1.
Follow the steps in Restoring the factory image with a DVD or USB flash device.
2.
When the Set Up Windows wizard appears, select your desired language, regional settings, keyboard layout, and accept the EULA. After completing the wizard, an attempt is made to discover the second node. The attempt fails and the following error message displays.
Figure 38: Error message during second node discovery
3.
Click Cancel. A pop-up window displays with the following message:
Do you want to ignore the second node? If so, you must run the wizard manually later to configure the second node.
4.
Click Yes.
The installation continues and eventually the server reboots. After the reboot, Windows automatically logs on as the local Administrator, and launches the Initial Configuration Tasks (ICT) window. However, you will not be using the ICT to configure the node.
5.
Check the Do not show this window at next logon box in the lower left corner of the window, and close the ICT window. There will be messages warning about inconsistencies between the nodes. Confirm that you wish to close the ICT.
6.
Change the password for the local administrator account by pressing CTRL+ALT+DELETE. (If you are using an iLO remote console, you must select the CTRL-ALT-DEL item from the Keyboard menu.) Select
Change a password. Enter the old password, which is what you had designated during the initial configuration of the system,, then enter a new password.
7.
Select the time and date shown in the lower right corner of the task bar. Click the Change date and time
settings link. Set the time zone of the server to be the same time zone as the other HPE StoreVirtual
3000 File Controller server and the domain controller. Adjust the time of day, if needed.
8.
Windows Server Manager opens when the ICT window is closed. If it is not open, launch it from the shortcut on the task bar to the right of the Windows Start button.
9.
As shown in figure Changing the computer name/domain, click the computer name, and then click
Change in the System Properties window. Enter a new computer name for the node, and select Domain to provide the Active Directory domain name to which the server will be joined. This must be the same domain that contains the existing one node cluster. You are prompted for the credentials of a domain
136 Recovering a single server
account that has permissions to add a computer to the domain. After the changes have been made, accept the prompt to restart the server.
Figure 39: Changing the computer name/domain
10. After the server has rebooted, log on as the local administrator. To manage the server as a cluster member in the future, use at least one domain user as a member of the local administrators group. In
Server Manager, select Configuration > Local Users and Groups to add any domain users to the
Administrators group.
11. Remove the failed node from the cluster (also called evicting the node) before you add the newly recovered node to the cluster. See the following Microsoft article for more information:
12. http://technet.microsoft.com/en-us/library/cc784955(v=WS.10).aspx
13. To add the recovered server blade to the cluster, log on to the other server (the server that is part of the existing one node cluster) as a domain user. Do not use the Initial Configuration Tasks (ICT) window.
Follow the instructions at the following website to add the recovered server to the cluster:
14. http://technet.microsoft.com/en-us/library/cc730998.aspx
Backing up and restoring HPE StoreVirtual 3000 File
Controller with Windows Recovery Environment
To use Windows Recovery Environment, you must have created a system backup with the Windows Server
Backup utility. You can either perform a single back up or schedule a regular back up.
Perform the following steps to create a one-time system backup using Server Manager:
Procedure
1. Open Server Manager and click Tools > Windows Server Backup.
2. In the Local Backup window, create one-time backup of the data by performing one of the following steps:
• From the Action menu, select Backup Once.
• In the left pane, right-click on Local Backup and select Backup Once.
3. The Backup Once Wizard is launched.
4. During one-time backup, the Different options option is selected by default. The Schedule backup
options is unavailable. Click Next to continue.
5. Select Full Server (recommended) to backup all server data, applications, and system state and click
Next to continue.
Backing up and restoring HPE StoreVirtual 3000 File Controller with Windows Recovery Environment
137
6. Select Remote shared folder as the destination type and click Next to continue.
7. Enter the path to the remote folder in Location and select the desired option in the Access control group.
Click Next to continue.
8. Review the items selected for the backup and click Backup.
9. A backup of the items is created and saved at the specified destination. The backup activity is also displayed on the Local Backup window.
Perform the following steps to restore the system with Windows Recovery Environment:
• Do one of the following:
1. For direct access, connect the cable and insert the System Recovery DVD in the StoreEasy system or attach a bootable USB flash drive that is prepared with a System Recovery image.
2. For remote management access, connect to the server using iLO from the client PC. Insert the System
Recovery DVD in the StoreEasy system or attach a bootable USB flash device that is prepared with a
System Recovery image.
• Reboot the server to either the USB flash device or USB DVD drive.
• The system BIOS attempts to boot to the USB device by default. Watch the monitor output during the boot as you may need to press a key to boot to the USB media.
NOTE:
If directly connected, you might have to change the BIOS settings to ensure proper boot sequence. If connected remotely, you might have to change some iLO settings to ensure proper boot sequence.
• In Windows Boot Manager, select Windows Recovery Environment.
• The recovery environment is loaded and the System Recovery Options wizard opens.
• Select the keyboard layout.
• Select Troubleshoot to access the repair tools that allow you to recover or troubleshoot Windows.
• Select Advanced options to access the advanced repair options.
• Select System Image Recovery to restore the system using a previously created system recovery image.
• Select the target operating system to be restored.
• The Re-image your computer wizard is launched, which scans the computer for a system image. If it is unable to locate a system image, the following message is displayed:
• Attach an external drive or insert a DVD that contains the backup files and click Retry. If you want to recover from the network, click Cancel.
• Select one of the following options and click Next:
1. Use the latest available image—Select to use the backup image that was recently created. If you are restoring from the network, this option is unavailable.
2. Select a system image—Select to restore from the network.
• If you are restoring from the network, click Advanced, and then select Search for a system image on
the network.
• Click Yes on the confirmation message to proceed with the network connectivity.
• Enter the share path where the backup image is stored and click OK.
• Enter the network login credentials for authentication and click OK.
• Select the system image from the list and click Next.
• Select the date and time of the system image that you want to restore and click Next.
138 Recovering HPE StoreVirtual 3000 File Controller
• Select Format and repartition disks to delete existing partitions and reformat all disks during the restore process and click Next. If you do not want to restore certain disks, click Exclude Disks.
NOTE: If the Format and repartition disks option is unavailable, click Install Drivers to install the drivers for the disks that you want to restore.
• Verify the system image details and click Finish to start the recovery process.
• Click Yes on the confirmation message to proceed with Windows recovery.
IMPORTANT:
Do not interrupt the recovery process.
When the system recovery completes, the system reboots. If you had external storage that was detached as recommended than reattach the storage and reboot the server.
Proceed with reconfiguring the server, following the steps in this administrator guide for configuring the system.
Recovering HPE StoreVirtual 3000 File Controller
139
Product Feedback
The Product Feedback feature enables you to send your suggestions, ideas on product improvement, or feedback on HPE StoreVirtual 3000 File Controller to [email protected]. You can access the Product Feedback dialog box using the following methods:
• Double-click the Product Feedback icon on the desktop.
• Click Product Feedback on the Start screen.
140 Product Feedback
Iternity iCAS
Get open, flexible, and expandable long-term archiving using HPE StoreVirtual with iTernity Compliant
Archive Solution (iCAS). Now validated to meet SEC 17a-4(f) requirements. A shortcut to iCAS is provided on the desktop and Start screen. See the Iternity website for more information about iCAS and to sign up for a free trial.
Iternity iCAS
141
Support and other resources
Accessing Hewlett Packard Enterprise Support
• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:www.hpe.com/
assistance
• To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website:www.hpe.com/support/hpesc
Information to collect
• Technical support registration number (if applicable)
• Product name, model or version, and serial number
• Operating system name and version
• Firmware version
• Error messages
• Product-specific reports and logs
• Add-on products or components
• Third-party products or components
Accessing updates
• Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method.
• To download product updates, go to either of the following:
◦ Hewlett Packard Enterprise Support Center
Get connected with updates
page:www.hpe.com/support/e-updates
◦ Software Depot website:www.hpe.com/support/softwaredepot
• To view and update your entitlements, and to link your contracts, Care Packs, and warranties with your profile, go to the Hewlett Packard Enterprise Support Center
More Information on Access to Support Materials
page:www.hpe.com/support/AccessToSupportMaterials
IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett
Packard Enterprise Support Center. You must have an HPE Passport set up with relevant entitlements.
142 Support and other resources
Websites
Website
Hewlett Packard Enterprise Information Library
Hewlett Packard Enterprise Support Center
Contact Hewlett Packard Enterprise Worldwide
Subscription Service/Support Alerts
Software Depot
Customer Self Repair
Insight Remote Support
Single Point of Connectivity Knowledge (SPOCK)
Storage compatibility matrix
Storage white papers and analyst reports
Link www.hpe.com/info/enterprise/docs www.hpe.com/support/hpesc www.hpe.com/assistance www.hpe.com/support/e-updates www.hpe.com/support/softwaredepot www.hpe.com/support/selfrepair www.hpe.com/info/insightremotesupport/docs www.hpe.com/storage/spock www.hpe.com/storage/whitepapers
Rack stability
Rack stability protects personnel and equipment.
WARNING:
To reduce the risk of personal injury or damage to equipment:
• Extend leveling jacks to the floor.
• Ensure that the full weight of the rack rests on the leveling jacks.
• Install stabilizing feet on the rack.
• In multiple-rack installations, fasten racks together securely.
• Extend only one rack component at a time. Racks can become unstable if more than one component is extended.
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience.
Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website:
www.hpe.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty, Care Pack Service, or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution
Websites
143
based on your product’s service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.
For more information and device support details, go to the following website:
www.hpe.com/info/insightremotesupport/docs
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback
([email protected]). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
144 Documentation feedback
Operating system logical drives
IMPORTANT:
The first two logical drives are configured for the HPE StoreVirtual 3000 File Controller system operating system.
The Operating System volume default factory settings can be customized after the operating system is up and running. The OS logical drive size can be changed to 120 GB or higher.
If the Operating System volume is customized and the System Recovery DVD is run at a later time, the
System Recovery process will maintain the custom settings as long as the above criteria are met (OS logical drive size of 120 GB or higher) and the OS volume is labeled System. If the storage system arrays are deleted and the System Recovery DVD is run, the System Recovery process will configure the HPE
Controller system RAID configurations .
HPE StoreVirtual 3000 File Controller systems do not include preconfigured data volumes. The administrator must configure data storage for HPE StoreVirtual 3000 File Controller.
The system reserved partition contains the operating system boot loader and allows you to enable BitLocker
Drive Encryption for the Operating System volume.
Table 8: HPE StoreVirtual 3000 File Controller system RAID configurations
Server model
• StoreVirtual 3000 File Controller
Logical Disk 1
• Operating System Volume (120 GB)
• RAID 1
• Physical Drives 1–2
NOTE:
In the HP Smart Storage Administrator, mapping of logical disks begins at 1. In Microsoft Disk Manager, mapping begins at 0.
If the operating system has a failure that might result from corrupt system files, a corrupt registry, or the
system hangs during boot, see Recovering HPE StoreVirtual 3000 File Controller .
Operating system logical drives
145
Network ports
The following table provides information on the local and remote network ports that are used by various HPE
StoreVirtual 3000 File Controller applications.
Table 9: Local and remote ports
Application Local port number
NetBIOS TCP Port 49258 49258
Network Storage System-
HTTPS-3202
Network Storage System-
HTTP-3201
Microsoft iSCSI Software
Target Service-UDP-138
Microsoft iSCSI Software
Target Service-TCP-135
Microsoft iSCSI Software
Target Service-TCP-3260
OEM OOBE Discovery
Service (WSD-IN)
OEM OOBE Discovery
Service (WSD-OUT)
LPD Service
Windows Standards-
Based Storage
Management CIM-XML indications inbound
Windows Standards-
Based Storage
Management SLP outbound
3202
3201
138
135
3260
3702
Any
515
5990
427
Failover Clusters
(DCOM-RPC-EPMAP-In)
Failover Clusters -
Named Pipes (NP-In)
Failover Clusters (UDP-
Out & In)
Failover Clusters (TCP-
In)
135
445
3343
3343
SNMP Service (UDP Out) Any
SNMP Service (UDP In) 161
DFS Management (SMB-
In)
445
Remote port number
Any
Any
Any
Any
Any
Any
Any
3702
Any
Any
Any
Any
Any
3343
Any
161
Any
Any
Enable
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Table Continued
146 Network ports
Application Local port number
DFS Management
(DCOM-In)
File Server Remote
Management (SMB-In)
File Server Remote
Management (DCOM-In)
Server for NFS (NFS-
UDP-In)
Portmap for UNIX-based
Software (TCP-In)
Windows Sync Share
(HTTPS-In)
Windows Sync Share
(HTTP-In)
World Wide Web
Services (HTTPS Traffic-
In)
World Wide Web
Services (HTTP Traffic-
In)
Messaging System-
HTTP-3202
Messaging System-
HTTP-3201
Remote Desktop - User
Mode (TCP-In)
Remote Desktop - User
Mode ((UDP-In)
Core Networking -
Dynamic Host
Configuration Protocol for
IPv6(DHCPV6-Out)
Core Networking -
Dynamic Host
Configuration Protocol for
IPv6(DHCPV6-In)
Core Networking -
Dynamic Host
Configuration Protocol
(DHCP-Out)
Core Networking -
Dynamic Host
Configuration Protocol
(DHCP-In)
135
445
135
2049
111
443
80
443
80
3202
3201
3389
3389
546
546
68
68
547
67
67
Any
Any
Any
Any
Any
547
Any
Any
Any
Any
Any
Remote port number
Any
Any
Any
Yes
Yes
Yes
Yes
Yes
Enable
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Table Continued
Network ports
147
Application
Remote Desktop - User
Mode (UDP-In)
Remote Desktop - User
Mode (TCP-In)
File and Printer Sharing
(LLMNR-UDP-Out)
File and Printer Sharing
(LLMNR-UDP-In)
Windows Remote
Management (HTTP-In)
File and Printer Sharing
(NB-Session-In)
File and Printer Sharing
(NB-Session-Out)
File and Printer Sharing
(SMB-In)
File and Printer Sharing
(SMB-Out)
File and Printer Sharing
(NB-Name-In)
File and Printer Sharing
(NB-Name-Out)
File and Printer Sharing
(NB-Datagram-In)
File and Printer Sharing
(NB-Datagram-Out)
Local port number
3389
3389
Any
5355
5985
139
Any
445
Any
137
Any
138
Any
Any
445
Any
137
Any
Any
Any
139
Any
138
Remote port number
Any
Any
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Enable
Yes
Yes
Yes
148 Network ports
Warranty and regulatory information
For important safety, environmental, and regulatory information, see Safety and Compliance Information for
Server, Storage, Power, Networking, and Rack Products, available at www.hpe.com/support/Safety-
Compliance-EnterpriseProducts.
Warranty information
HPE ProLiant and x86 Servers and Options www.hpe.com/support/ProLiantServers-Warranties
HPE Enterprise Servers www.hpe.com/support/EnterpriseServers-Warranties
HPE Storage Products www.hpe.com/support/Storage-Warranties
HPE Networking Products www.hpe.com/networking/warranty
Regulatory information
Belarus Kazakhstan Russia marking
Manufacturer and Local Representative Information
Manufacturer information:
• Hewlett Packard Enterprise, 3000 Hanover Street, Palo Alto, CA 94304, U.S.
Local representative information Russian:
• Russia
:
• Belarus
:
• Kazakhstan
:
Warranty and regulatory information
149
Local representative information Kazakh:
• Kazakhstan
:
Manufacturing date:
The manufacturing date is defined by the serial number.
CCSYWWZZZZ (serial number format for this product)
Valid date formats include:
• YWW, where Y indicates the year counting from within each new decade, with 2000 as the starting point; for example, 238: 2 for 2002 and 38 for the week of September 9. In addition, 2010 is indicated by 0, 2011 by 1, 2012 by 2, 2013 by 3, and so forth.
• YYWW, where YY indicates the year, using a base year of 2000; for example, 0238: 02 for 2002 and 38 for the week of September 9.
Turkey RoHS material content declaration
Türkiye Cumhuriyeti: EEE Yönetmeliğine Uygundur
Ukraine RoHS material content declaration
Обладнання відповідає вимогам Технічного регламенту щодо обмеження використання деяких небезпечних речовин в електричному та електронному обладнанні, затвердженого постановою
Кабінету Міністрів України від 3 грудня 2008 № 1057
150 Turkey RoHS material content declaration
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project