HP StorageWorks
X3000 G2 Network Storage System User Guide
SWX image version 2.00.0a
Part Number: 5697-0592
First edition: November 2010
Legal and notice information
© Copyright 2010, 2010 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211
and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items
are licensed to the U.S. Government under vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set
forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation
or its subsidiaries in the United States and other countries.
Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java™ is a US trademark of Sun Microsystems, Inc.
Oracle is a registered US trademark of Oracle Corporation, Redwood City, California.
UNIX® is a registered trademark of The Open Group.
Warranty
WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website:
http://www.hp.com/go/storagewarranty
Contents
1 Installing and configuring the storage system ....................................... 13
Setup overview ......................................................................................................................... 13
Check kit contents .............................................................................................................. 13
Determine an access method ............................................................................................... 13
Locate the serial number, Certificate of Authenticity, and End User License Agreement ........................ 14
Install the storage system hardware ............................................................................................. 14
Connect to the storage system .................................................................................................... 14
Power on the server and log on .................................................................................................. 15
Confirm Windows activation ...................................................................................................... 16
Configure the storage system ...................................................................................................... 17
Complete system configuration ................................................................................................... 17
Additional access methods ......................................................................................................... 18
Using the remote browser method ......................................................................................... 18
Using the Remote Desktop method ........................................................................................ 18
Using the Telnet method ...................................................................................................... 19
Enabling Telnet ............................................................................................................ 19
Default storage settings .............................................................................................................. 19
Physical configuration ......................................................................................................... 19
Default boot sequence ........................................................................................................ 20
2 Storage system component identification ............................................. 21
HP X3400 G2 Network Storage Gateway hardware components ................................................... 21
HP X3800 G2 Network Storage Gateway hardware components ................................................... 23
HP X3800sb G2 Network Storage Gateway Blade hardware components ....................................... 27
SAS and SATA hard drive LEDs ................................................................................................... 28
Systems Insight Display LEDs ...................................................................................................... 30
Systems Insight Display LED combinations .................................................................................... 31
3 Administration tools .......................................................................... 33
Microsoft Windows Storage Server 2008 R2 administration tools ................................................... 33
Remote Desktop for Administration ....................................................................................... 33
Share and Storage Management .......................................................................................... 33
Single Instance Storage ....................................................................................................... 34
Print Management .............................................................................................................. 35
Network File System (NFS) User Mapping ............................................................................. 35
Configuring AD LDS ........................................................................................................... 36
Microsoft hotfix 2222746 .............................................................................................. 36
Phase 1 scripts ............................................................................................................ 36
Phase 2 scripts ............................................................................................................ 37
Script execution ........................................................................................................... 38
Verifying script execution .............................................................................................. 39
Shared access example ................................................................................................ 41
4 Storage management overview .......................................................... 49
X3000 G2 Network Storage System User Guide 3
Storage management elements ................................................................................................... 49
Storage management example ............................................................................................. 49
Physical storage elements .................................................................................................... 50
Arrays ........................................................................................................................ 51
Fault tolerance ............................................................................................................. 52
Online spares ............................................................................................................. 52
Logical storage elements ..................................................................................................... 52
Logical drives (LUNs) .................................................................................................... 52
Partitions .................................................................................................................... 53
Volumes ..................................................................................................................... 53
File system elements ............................................................................................................ 54
File sharing elements .......................................................................................................... 54
Volume Shadow Copy Service overview ................................................................................ 54
Using storage elements ....................................................................................................... 55
Clustered server elements .................................................................................................... 55
Network adapter teaming .......................................................................................................... 55
Management tools .................................................................................................................... 55
HP Systems Insight Manager ................................................................................................ 55
Management Agents .......................................................................................................... 56
5 File server management .................................................................... 57
File services features in Windows Storage Server 2008 R2 ............................................................ 57
Storage Manager for SANs ................................................................................................. 57
Single Instance Storage ....................................................................................................... 57
File Server Resource Manager .............................................................................................. 57
Windows SharePoint Services .............................................................................................. 57
File services management .......................................................................................................... 58
Configuring data storage .................................................................................................... 58
Storage management utilities ............................................................................................... 58
Array management utilities ............................................................................................ 59
Array Configuration Utility ............................................................................................ 59
Disk Management utility ............................................................................................... 60
Guidelines for managing disks and volumes .......................................................................... 60
Scheduling defragmentation ................................................................................................ 61
Disk quotas ....................................................................................................................... 61
Adding storage .................................................................................................................. 62
Expanding storage ...................................................................................................... 62
Extending storage using Windows Storage Utilities .......................................................... 62
Expanding storage for EVA arrays using Command View EVA ........................................... 63
Expanding storage using the Array Configuration Utility ................................................... 63
Volume shadow copies .............................................................................................................. 64
Shadow copy planning ....................................................................................................... 64
Identifying the volume .................................................................................................. 64
Allocating disk space ................................................................................................... 65
Identifying the storage area .......................................................................................... 66
Determining creation frequency ..................................................................................... 66
Shadow copies and drive defragmentation ............................................................................ 66
Mounted drives .................................................................................................................. 67
Managing shadow copies ................................................................................................... 67
The shadow copy cache file .......................................................................................... 68
Enabling and creating shadow copies ............................................................................ 69
Viewing a list of shadow copies ..................................................................................... 69
Set schedules .............................................................................................................. 70
Viewing shadow copy properties ................................................................................... 70
4
Redirecting shadow copies to an alternate volume ........................................................... 70
Disabling shadow copies .............................................................................................. 71
Managing shadow copies from the storage system desktop ..................................................... 71
Shadow Copies for Shared Folders ....................................................................................... 72
SMB shadow copies .................................................................................................... 73
NFS shadow copies ..................................................................................................... 74
Recovery of files or folders ............................................................................................ 74
Recovering a deleted file or folder .................................................................................. 74
Recovering an overwritten or corrupted file ...................................................................... 75
Recovering a folder ...................................................................................................... 75
Backup and shadow copies .......................................................................................... 76
Shadow Copy Transport ...................................................................................................... 76
Folder and share management ................................................................................................... 76
Folder management ............................................................................................................ 77
Share management ............................................................................................................ 83
Share considerations .................................................................................................... 83
Defining Access Control Lists ......................................................................................... 84
Integrating local file system security into Windows domain environments ............................. 84
Comparing administrative (hidden) and standard shares ................................................... 84
Managing shares ........................................................................................................ 85
File Server Resource Manager .................................................................................................... 85
Quota management ........................................................................................................... 85
File screening management ................................................................................................. 86
Storage reports .................................................................................................................. 86
Other Windows disk and data management tools ......................................................................... 86
Additional information and references for file services .................................................................... 86
Backup ............................................................................................................................. 86
HP StorageWorks Library and Tape Tools .............................................................................. 86
Antivirus ............................................................................................................................ 87
6 Cluster administration ....................................................................... 89
Cluster overview ....................................................................................................................... 89
Cluster terms and components .................................................................................................... 90
Nodes .............................................................................................................................. 90
Resources .......................................................................................................................... 90
Cluster groups ................................................................................................................... 91
Virtual servers .................................................................................................................... 91
Failover and failback .......................................................................................................... 91
Quorum disk ..................................................................................................................... 91
Cluster concepts ....................................................................................................................... 92
Sequence of events for cluster resources ................................................................................ 92
Hierarchy of cluster resource components .............................................................................. 93
Cluster planning ....................................................................................................................... 93
Storage planning ............................................................................................................... 94
Network planning .............................................................................................................. 94
Protocol planning ............................................................................................................... 95
Preparing for cluster installation .................................................................................................. 95
Before beginning installation ............................................................................................... 96
Using multipath data paths for high availability ...................................................................... 96
Checklists for cluster server installation .................................................................................. 96
Network requirements .................................................................................................. 96
Shared disk requirements .............................................................................................. 96
Cluster installation ..................................................................................................................... 97
Setting up networks ............................................................................................................ 97
X3000 G2 Network Storage System User Guide 5
Configuring the private network adapter ......................................................................... 97
Configuring the public network adapter .......................................................................... 98
Renaming the local area connection icons ...................................................................... 98
Verifying connectivity and name resolution ...................................................................... 98
Verifying domain membership ....................................................................................... 98
Setting up a cluster account .......................................................................................... 98
About the Quorum disk ................................................................................................ 98
Configuring shared disks .............................................................................................. 99
Verifying disk access and functionality ............................................................................ 99
Configuring cluster service software ............................................................................................. 99
Using Failover Cluster Management ...................................................................................... 99
Creating a cluster ............................................................................................................... 99
Adding nodes to a cluster .................................................................................................... 99
Geographically dispersed clusters ...................................................................................... 100
Cluster groups and resources, including file shares ...................................................................... 100
Cluster group overview ..................................................................................................... 100
Node-based cluster groups ......................................................................................... 101
Load balancing ......................................................................................................... 101
File share resource planning issues ..................................................................................... 101
Resource planning ..................................................................................................... 101
Permissions and access rights on share resources ........................................................... 102
NFS cluster-specific issues ........................................................................................... 102
Non cluster aware file sharing protocols .............................................................................. 103
Adding new storage to a cluster ......................................................................................... 103
Creating physical disk resources .................................................................................. 103
Creating file share resources ....................................................................................... 103
Creating NFS share resources ..................................................................................... 104
Shadow copies in a cluster ................................................................................................ 104
Extend a LUN in a cluster .................................................................................................. 104
MSNFS administration on a server cluster ............................................................................ 104
Best practices for running Server for NFS in a server cluster ............................................. 104
Print services in a cluster .......................................................................................................... 105
Creating a cluster printer spooler ........................................................................................ 105
Advanced cluster administration procedures ............................................................................... 106
Failing over and failing back ............................................................................................. 106
Restarting one cluster node ................................................................................................ 107
Shutting down one cluster node .......................................................................................... 107
Powering down the cluster ................................................................................................. 107
Powering up the cluster ..................................................................................................... 108
7 Troubleshooting, servicing, and maintenance ..................................... 109
Troubleshooting the storage system ............................................................................................ 109
WEBES (Web Based Enterprise Services) ................................................................................... 109
Maintenance and service ......................................................................................................... 110
Maintenance updates ....................................................................................................... 110
System updates .......................................................................................................... 110
Firmware updates ............................................................................................................. 110
Certificate of Authenticity ......................................................................................................... 110
Workarounds for common issues .............................................................................................. 111
8 System recovery ............................................................................. 113
The System Recovery DVD ........................................................................................................ 113
Restore the factory image ......................................................................................................... 113
Using a USB Flash Drive for System Recovery ............................................................................. 114
6
Create a System Recovery USB Flash Drive .......................................................................... 114
Use the USB Flash Drive for System Recovery ....................................................................... 115
Managing disks after a restoration ............................................................................................ 116
9 Support and other resources ............................................................ 117
Contacting HP ........................................................................................................................ 117
Typographic conventions ......................................................................................................... 117
Rack stability .......................................................................................................................... 118
Customer self repair ................................................................................................................ 118
HP Insight Remote Support software .......................................................................................... 119
A Regulatory compliance notices ........................................................ 121
Regulatory compliance identification numbers ............................................................................ 121
Federal Communications Commission notice .............................................................................. 121
FCC rating label .............................................................................................................. 121
Class A equipment ..................................................................................................... 121
Class B equipment ..................................................................................................... 122
Declaration of Conformity for products marked with the FCC logo, United States only ............... 122
Modification .................................................................................................................... 122
Cables ............................................................................................................................ 122
Canadian notice (Avis Canadien) ............................................................................................. 122
Class A equipment ........................................................................................................... 122
Class B equipment ............................................................................................................ 123
European Union notice ............................................................................................................ 123
Japanese notices .................................................................................................................... 123
Japanese VCCI-A notice .................................................................................................... 123
Japanese VCCI-B notice .................................................................................................... 123
Japanese VCCI marking .................................................................................................... 123
Japanese power cord statement .......................................................................................... 124
Korean notices ....................................................................................................................... 124
Class A equipment ........................................................................................................... 124
Class B equipment ............................................................................................................ 124
Taiwanese notices ................................................................................................................... 124
BSMI Class A notice ......................................................................................................... 124
Taiwan battery recycle statement ........................................................................................ 125
Turkish recycling notice ............................................................................................................ 125
Laser compliance notices ......................................................................................................... 126
English laser notice ........................................................................................................... 126
Dutch laser notice ............................................................................................................. 126
French laser notice ........................................................................................................... 127
German laser notice ......................................................................................................... 127
Italian laser notice ............................................................................................................ 127
Japanese laser notice ........................................................................................................ 128
Spanish laser notice ......................................................................................................... 128
Recycling notices .................................................................................................................... 128
English recycling notice ..................................................................................................... 128
Bulgarian recycling notice ................................................................................................. 129
Czech recycling notice ...................................................................................................... 129
Danish recycling notice ..................................................................................................... 129
Dutch recycling notice ....................................................................................................... 129
Estonian recycling notice ................................................................................................... 130
Finnish recycling notice ..................................................................................................... 130
French recycling notice ...................................................................................................... 130
German recycling notice ................................................................................................... 130
X3000 G2 Network Storage System User Guide 7
Greek recycling notice ...................................................................................................... 131
Hungarian recycling notice ................................................................................................ 131
Italian recycling notice ...................................................................................................... 131
Latvian recycling notice ..................................................................................................... 131
Lithuanian recycling notice ................................................................................................. 132
Polish recycling notice ....................................................................................................... 132
Portuguese recycling notice ................................................................................................ 132
Romanian recycling notice ................................................................................................. 132
Slovak recycling notice ...................................................................................................... 133
Spanish recycling notice .................................................................................................... 133
Swedish recycling notice ................................................................................................... 133
Battery replacement notices ...................................................................................................... 134
Dutch battery notice .......................................................................................................... 134
French battery notice ........................................................................................................ 135
German battery notice ...................................................................................................... 135
Italian battery notice ......................................................................................................... 136
Japanese battery notice .................................................................................................... 136
Spanish battery notice ...................................................................................................... 137
Glossary .......................................................................................... 139
Index ............................................................................................... 141
8
Figures
HP X3400 G2 front panel components ...................................................................... 211
HP X3400 G2 front panel LEDs ................................................................................ 222
HP X3400 G2 rear panel components ....................................................................... 223
HP X3400 G2 rear panel LEDs ................................................................................. 234
HP X3800 G2 front panel components ...................................................................... 245
HP X3800 G2 front panel LEDs and buttons ............................................................... 256
HP X3800 G2 rear panel components ....................................................................... 257
HP X3800 G2 rear panel LEDs and buttons ............................................................... 268
HP X3800sb G2 front panel components ................................................................... 279
HP X3800sb G2 front panel LEDs ............................................................................. 2810
SAS/SATA hard drive LEDs ....................................................................................... 2911
Systems Insight Display LEDs ..................................................................................... 3012
AD LDS Role and Instance ........................................................................................ 3713
AD LDS script execution help screen .......................................................................... 3914
ADSI Edit Connection Settings dialog box .................................................................. 4015
NFS-mapped users and groups in ADSI Edit ............................................................... 4116
NFS Advanced Sharing dialog box ........................................................................... 4317
NFS Share Permissions dialog box ............................................................................ 4318
Permissions for NfsTest dialog box ............................................................................. 4419
Advanced Security Settings for file.txt ........................................................................ 4520
Select User or Group dialog box ............................................................................... 4621
Replace owner on subcontainers and objects .............................................................. 4722
Permissions for NfsTest dialog box ............................................................................. 4723
Storage management process example ...................................................................... 5024
Configuring arrays from physical drives ...................................................................... 5125
RAID 0 (data striping) (S1-S4) of data blocks (B1-B12) ................................................ 5126
Two arrays (A1, A2) and five logical drives (L1 through L5) spread over five physical
27
drives .................................................................................................................... 53
System administrator view of Shadow Copies for Shared Folders ................................... 6728
Shadow copies stored on a source volume ................................................................. 6829
Shadow copies stored on a separate volume .............................................................. 6830
Accessing shadow copies from My Computer ............................................................. 7231
X3000 G2 Network Storage System User Guide 9
Client GUI ............................................................................................................. 7332
Recovering a deleted file or folder ............................................................................. 7533
Properties dialog box, Security tab ............................................................................ 7834
Advanced Security settings dialog box, Permissions tab ............................................... 7935
User or group Permission Entry dialog box ................................................................. 8036
Advanced Security Settings dialog box, Auditing tab ................................................... 8137
Select User or Group dialog box ............................................................................... 8138
Auditing Entry dialog box for folder name NTFS Test ................................................... 8239
Advanced Security Settings dialog box, Owner tab ..................................................... 8340
Storage system cluster diagram ................................................................................. 9041
Cluster concepts diagram ......................................................................................... 9242
10
Tables
Storage system RAID configurations ........................................................................... 201
HP X3400 G2 front panel LED descriptions ................................................................ 222
HP X3400 G2 rear panel LED descriptions ................................................................. 233
HP X3800 G2 front panel LED and button descriptions ................................................ 254
HP X3800 G2 rear panel LED and button descriptions ................................................. 265
HP X3800sb G2 front panel LED descriptions ............................................................. 286
SAS and SATA hard drive LED combinations ............................................................... 297
Systems Insight Display LED descriptions .................................................................... 308
Systems Insight Display LEDs and internal health LED combinations ................................ 319
Summary of RAID methods ....................................................................................... 5210
Tasks and utilities needed for storage system configuration ........................................... 5811
Sharing protocol cluster support ................................................................................ 9512
Power sequencing for cluster installation ..................................................................... 9713
Document conventions ........................................................................................... 11714
X3000 G2 Network Storage System User Guide 11
12
1 Installing and configuring the storage system
Setup overview
The HP StorageWorks X3000 G2 Network Storage System comes preinstalled with the Microsoft
Windows® Storage Server™ 2008 R2 Enterprise Edition x64operating system with Microsoft iSCSI
Software Target and a Microsoft Cluster Service (MSCS) license included.
IMPORTANT:
• Windows Storage Server 2008 R2 x64 operating systems are designed to support 32–bit applic-
ations without modification; however, any 32–bit applications that are run on these operating
systems should be thoroughly tested before releasing the storage system to a production environ-
ment.
• Windows Storage Server x64 editions support only x64-based versions of Microsoft Management
Console (MMC) snap-ins, not 32-bit versions.
Check kit contents
Remove the contents, making sure you have all the components listed below. If components are missing,
contact HP technical support.
• HP StorageWorks X3000 G2 Network Storage System (with operating system preloaded)
• Power cord(s)
• Safety and Disposal Documentation CD
• HP StorageWorks Storage System Recovery DVD
• End User License Agreement
• Certificate of Authenticity Card
• Slide rail assembly
• HP ProLiant Essentials Integrated Lights-Out Advanced Pack
NOTE:
HP StorageWorks X3800 G2 Network Storage Systems support Integrated Lights-Out 3 (iLO 3) remote
management software. All other storage system models support iLO 2.
Determine an access method
Before you install the storage system, you need to decide on an access method.
X3000 G2 Network Storage System User Guide 13
The type of access you select is determined by whether or not the network has a Dynamic Host
Configuration Protocol (DHCP) server. If the network has a DHCP server, you can install the storage
system through the direct attachment or remote management methods. If your network does not have
a DHCP server, you must access the storage system through the direct attachment method.
The direct attachment method requires a display, keyboard, and mouse. These components are not
provided with the storage system.
IMPORTANT:
Only the direct attach and remote management access methods can be used to install the storage
system. After the storage system installation process is complete and the system's IP address has been
assigned, you can then additionally use the remote browser and remote desktop methods to access
the storage system.
Locate the serial number, Certificate of Authenticity, and End User License Agreement
For technical support purposes, locate the storage system's serial number, 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 storage system's serial number is located in several places:
• Top of the storage system or blade
• Back of the storage system
• Inside the storage system shipping box
• Outside of the storage system shipping box
The storage system's Certificate of Authenticity (COA) card is located inside the storage system shipping
box. There is also a COA sticker with product key affixed to the top of the storage system or blade.
The storage system's printed End User License Agreement (EULA) is located in the media kit that is
shipped with the storage system. There is also an electronic copy of the EULA installed with the storage
system at %SystemDrive%\Windows\System32\license.rtf.
Install the storage system hardware
If your storage system is fully racked and cabled, move ahead to Connect to the storage system.
For X3400 and X3800 G2 storage systems, install the rail kit and insert and secure the storage system
into the rack by following the HP Rack Rail Kit Installation Instructions.
ForX3800sb G2 G2 storage systems, install the server blade by following the procedures documented
in the provided HP StorageWorks X3800sb G2 Network Storage Gateway Blade Quick Start Guide.
Connect to the storage system
Use either the direct connect or remote management method to connect to the storage system.
Installing and configuring the storage system14
IMPORTANT:
Only the direct attach and remote management access methods can be used to install the storage
system. After the storage system installation process is complete and the system's IP address has been
assigned, you can then additionally use the remote browser and remote desktop methods to access
the storage system.
• Direct attach — Connect the following cables to the back panel of the storage system in the follow-
ing sequence: keyboard, mouse, network cable, monitor cable, and power cable. For blade
products, connect the cables to the server blade by using an HP c-Class Blade SUV cable. This
access method is mandatory if your network does not have a Dynamic Host Configuration Protocol
(DHCP) server.
NOTE:
The keyboard, mouse, and monitor are not provided with the storage system.
HP c-Class Blade SUV cable require USB-compatible devices.
• Remote management — Access the storage system using the Integrated Lights-Out remote manage-
ment method:
1. Ensure that a network cable is connected to the iLO port located on the back of the storage
system.
2. Locate the iLO Network Settings tag attached to the storage system and record the default
user name, password, and DNS name.
3. From a remote computer, open a standard Web browser and enter the iLO management
hostname of the storage system.
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.
4. Using the default user information provided on the iLO Network Settings tag, log on to the
storage system.
For detailed instructions on using iLO remote management software, see the HP Integrated Lights–Out
2 User Guide or HP ProLiant Integrated Lights-Out 3 User Guide.
Power on the server and log on
Power on the server after installing the hardware and connecting the cables. Powering on the server
for the first time initiates the storage system installation process.
X3000 G2 Network Storage System User Guide 15
1. Power on the system by pushing the power button on the front panel. If using iLO, click Momentary
Press on the Power Management page to power on the server, then click Launch on the Status
Summary page to open the iLO Integrated Remote Console and complete the installation process.
The storage system starts and displays an HP Network Storage System installation screen. The
storage system installation process takes approximately 10–15 minutes.
NOTE:
Your storage system comes pre-installed with the Microsoft Windows Storage Server 2008
R2 operating system. There is no operating system installation required.
When the storage system installation process nears completion, the Windows Storage Server
2008 R2 desktop displays the following message: The user's password must be changed before
logging on the first time. Log on to the storage system by establishing an Administrator password:
2. Click OK.
3. Type an Administrator password in the New password box.
4. Re-type the Administrator password in the Confirm password box.
5. Click the blue arrow next to the Confirm password box.
6. Click OK.
After the Administrator password has been set, the storage system completes the installation
process and restarts.
7. When prompted, press CTRL+ALT+DELETE to log on to the system. If using iLO, on the iLO
Integrated Remote Console tab, click the button labeled CAD and then click the Ctrl-Alt-Del menu
item.
IMPORTANT:
After establishing the new Administrator password, be sure to remember it and record it in a safe
place if needed. HP has no way of accessing the system if the new password is lost.
Confirm Windows activation
Immediately after installing the storage system, confirm that your copy of the Microsoft® Windows®
Storage Server™ 2008 R2 operating system has been activated.
IMPORTANT:
Some storage systems may not automatically activate Windows during the system installation process.
To check the activation status of Windows, open Control Panel (Start > Control Panel) and then
double-click System. If your copy of Windows has been activated, the status under Windows activation
will read Windows is activated. If your copy of Windows has not been activated, you must manually
activate it within three days of the initial storage system installation.
To manually activate your copy of Windows:
1. If needed, change your locale settings (Control Panel > Regional and Language Options).
Installing and configuring the storage system16
2. Record the product key located on the Certificate of Authenticity.
3. In Control Panel, double-click System.
4. Under Windows Activation, click Activate Windows Now.
5. Follow the on-screen instructions. Be sure to choose the Type a different product key option when
prompted for a product key.
Microsoft Windows Storage Server 2008 R2 cannot be fully activated online. During the activation
process, you will be provided with a telephone number to call to complete the process. Be sure to
have the product key available when calling this number.
Configure the storage system
The HP StorageWorks Initial Configuration Tasks window launches automatically on logon. Use this
tool to perform setup tasks such as setting the time zone, network configuration, changing the computer
name, and joining a domain. When the HP StorageWorks Initial Configuration Tasks window is
closed, HP Server Manager is launched automatically. Use HP Server Manager for further customizing
of the storage system, such as adding roles and features, and share and storage management.
For detailed information about configuration options in HP StorageWorks Initial Configuration Tasks
and Server Manager, see the online help.
Complete system configuration
After the storage system is physically set up and the basic configuration is established, you must
complete additional setup tasks. Depending on the deployment scenario of the storage system, these
steps can vary. These additional steps can include:
• Running Microsoft Windows Update—HP highly recommends that you run Microsoft Windows
updates to identify, review, and install the latest, applicable, critical security updates on the storage
system.
• Creating and managing users and groups—User and group information and permissions determine
whether a user can access files. If the storage system is deployed into a workgroup environment,
this user and group information is stored locally on the device. By contrast, if the storage system
is deployed into a domain environment, user and group information is stored on the domain.
• Joining workgroup and domains—These are the two system environments for users and groups.
Because users and groups in a domain environment are managed through standard Windows or
Active Directory domain administration methods, this document discusses only local users and
groups, which are stored and managed on the storage system. For information on managing users
and groups on a domain, see the domain documentation available on the Microsoft web site.
If the storage system is deployed in a domain environment, the domain controller will store new
accounts on the domain; however, remote systems will store new accounts locally unless they are
granted permissions to create accounts on the domain.
• Using Ethernet NIC teaming (optional)—All models are equipped with an HP or Broadcom NIC
Teaming utility. The utility allows administrators to configure and monitor Ethernet network interface
controller (NIC) teams in a Windows-based operating system. These teams provide options for
increasing fault tolerance and throughput.
• Adjusting logging for system, application, and security events.
• Installing third-party software applications—For example, these might include an antivirus applic-
ation that you install.
• Registering the server — To register the server, refer to the HP Registration website (http://re-
gister.hp.com).
X3000 G2 Network Storage System User Guide 17
Additional access methods
After the storage system installation process is complete and the system's IP address has been assigned,
you can then additionally use the remote browser, Remote Desktop, and Telnet methods to access the
storage system.
Using the remote browser method
The storage system ships with DHCP enabled on the network port. If the server is placed on a
DHCP-enabled network and the IP address or server name is known, the server can be accessed
through a client running Internet Explorer 5.5 (or later) on that network, using the TCP/IP 3202 port.
IMPORTANT:
Before you begin this procedure, ensure that you have the following:
• Windows-based PC loaded with Internet Explorer 5.5 (or later) on the same local network as the
storage system
• DHCP-enabled network
• Server name or IP address of the storage system
To connect the server to a network using the remote browser method, ensure that the client is configured
to download signed ActiveX controls.
To connect the storage system to a network using the remote browser method
1. On the remote client machine open Internet Explorer and enter https:// and the server name
of the storage system followed by a hyphen (-), and then:3202. For example, https://
labserver-:3202. Press Enter.
NOTE:
If you are able to determine the IP address from your DHCP server, you can substitute the
IP address for the server name. For example: 192.100.0.1:3202.
2. Click OK on the Security Alert prompt.
3. Log on to the storage system with the administrator user name and password.
IMPORTANT:
If you are using the remote browser method to access the storage system, always close the remote
session before closing your Internet browser. Closing the Internet browser does not close the remote
session. Failure to close your remote session impacts the limited number of remote sessions allowed
on the storage system at any given time.
Using the Remote Desktop method
Remote Desktop provides the ability for you to log onto and remotely administer your server, giving
you a method of managing it from any client. Installed for remote administration, Remote Desktop
Installing and configuring the storage system18
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 storage system to a network using the Remote Desktop method
1. On the PC client, select Start > Run. At Open, type mstsc, then click OK.
2. Enter the IP address of the storage system in the Computer box and click Connect.
3. Log on to the storage system with the administrator user name and password.
Using the Telnet method
Telnet is a utility that lets users connect to machines, log on, and obtain a command prompt remotely.
Telnet is preinstalled on the storage system but must be activated before use.
CAUTION:
For security reasons, Telnet is disabled by default. The service needs to be modified to enable access
to the storage system with Telnet.
Enabling Telnet
The Telnet service needs to be enabled prior to its access.
1. In Server Manager, expand the Configuration node in the left panel.
2. Click System and Network Settings.
3. Under System Settings Configuration, click Telnet.
4. Check the Enable Telnet access to this server check box and then click OK.
Default storage settings
HP StorageWorks X3000 G2 Network Storage Systems are preconfigured with default storage
settings. This section provides additional details about the preconfigured storage.
Physical configuration
The logical disks reside on physical drives as shown in the table below.
As of the SWX image version 1.2, the DON'T ERASE volume that was created on earlier versions of
HP StorageWorks Network Storage System models is no longer used.
IMPORTANT:
The first two logical drives are configured for the storage system operating system.
The Operating System volume default factory settings can be customized after the operating system
is up and running. The following settings can be changed:
• RAID level can be changed to any RAID level except RAID 0
• OS logical drive size can be changed to 60 GB or higher
X3000 G2 Network Storage System User Guide 19
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
(RAID level other than RAID 0 and OS logical drive size of 60 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 storage system using the factory default settings listed in
the table below.
HP StorageWorks X3000 G2 Network Storage Systems do not include preconfigured data volumes.
The administrator must configure data storage for the storage system. See “Configuring data
storage” on page 58 for more information.
The system reserved partition contains the operating system boot loader and allows you to enable
BitLocker Drive Encryption for the Operating System volume.
Table 1 Storage system RAID configurations
Logical Disk 1Server model
• HP StorageWorks X3400 G2 Network Storage
Gateway
• HP StorageWorks X3800 G2 Network Storage
Gateway
• HP StorageWorks X3800sb G2 Network Storage
Gateway Blade
• Operating System Volume
• RAID 1+0
• Physical Drives 0–1
NOTE:
In the HP Array Configuration Utility (ACU), logical disks are labeled 1 and 2. In Microsoft Disk
Manager, logical disks are displayed as 0 and 1. For HP Smart Array configuration information, see
http://h18004.www1.hp.com/products/servers/proliantstorage/arraycontrollers/.
If the operating system has a failure that might result from corrupt system files, a corrupt registry, or
the system hangs during boot, see “System recovery” on page 113.
Default boot sequence
The BIOS supports the following default boot sequence:
1. DVD-ROM
2. Bootable USB flash drive
3. HDD
4. PXE (network boot)
Under normal circumstances, the storage systems boot up from the OS logical drive.
• If the system experiences a drive failure, the drive displays an amber disk failure LED.
• If a single drive failure occurs, it is transparent to the operating system.
Installing and configuring the storage system20
2 Storage system component identification
This chapter provides illustrations of the storage system hardware components.
NOTE:
The keyboard, mouse, and monitor are used only for the direct attached method of accessing the
server. They are not provided with your storage system.
HP X3400 G2 Network Storage Gateway hardware components
The following figures show components and LEDs located on the front and rear panels of the X3400
G2 Network Storage Gateway.
Figure 1 HP X3400 G2 front panel components
.
1. DVD-RW drive
2. Serial label pull tab
3. Two (2) USB ports
4. Four (4) 3.5” hot-plug SAS/SATA hard drive bays
NOTE:
See “SAS and SATA hard drive LED combinations” on page 29 for HDD LED status descriptions.
X3000 G2 Network Storage System User Guide 21
Figure 2 HP X3400 G2 front panel LEDs
.
Table 2 HP X3400 G2 front panel LED descriptions
StatusItem / Description
Green = System health is normal.
1. Internal health LED
Amber = System health is degraded.
Red = System health is critical.
Off = System health is normal (when in standby mode).
2. NIC 1 link/activity LED
3. NIC 2 link/activity LED
4. Drive activity LED
5. Power On/Standby button and system
power LED
6. UID button/LED
Green = Network link exists.
Flashing green = Network link and activity exist.
Off = No network link exists.
Green = Drive activity is normal.
Off = No drive activity exists.
Green = Normal (system on)
Amber = System is in standby, but power is still applied.
Off = Power cord is not attached or the power supply has failed.
Blue = Identification is activated.
Flashing blue = System is being managed remotely.
Off = Identification is deactivated.
Figure 3 HP X3400 G2 rear panel components
.
Storage system component identification22
1. Power cord connector
2. Mouse connector
3. 10/100/1000 NIC 1 connector/shared iLO 2 management port
4. 10/100/1000 NIC 2 connector
5. Serial connector
6. Low profile PCIe slot cover (x16 slot open)
7. Full-sized PCIe slot (occupied by Smart Array P212 controller)
8. Dedicated iLO 2 management port (this port is optional and must be purchased separately)
9. Video connector
10. USB connectors (2)
11. Keyboard connector
Figure 4 HP X3400 G2 rear panel LEDs
.
Table 3 HP X3400 G2 rear panel LED descriptions
StatusItem / Description
Blue = Activated
1. UID button/LED
2. NIC/iLO 2 link
3. NIC/iLO 2 activity
Flashing = System is being managed remotely.
Off = Deactivated
Green or flashing green = Activity exists.
Off = No activity exists.
Green = Link exists.
Off = No link exists.
HP X3800 G2 Network Storage Gateway hardware components
The following figures show components and LEDs located on the front and rear panels of the X3800
G2 Network Storage Gateway.
X3000 G2 Network Storage System User Guide 23
Figure 5 HP X3800 G2 front panel components
.
1. Quick release levers (2)
2. Systems Insight Display
NOTE:
See “Systems Insight Display LEDs” on page 30 and “Systems Insight Display LED
combinations” on page 31 for LED status information.
3. Eight (8) 2.5” SFF SAS / SATA hot plug hard drive bays
NOTE:
See “SAS and SATA hard drive LED combinations” on page 29 for HDD LED status descriptions.
4. DVD-RW drive
5. Video connector
6. USB connectors (2)
Storage system component identification24
Figure 6 HP X3800 G2 front panel LEDs and buttons
.
Table 4 HP X3800 G2 front panel LED and button descriptions
StatusItem / Description
Blue = Activated
1. UID LED and button
2. System health LED
Flashing blue = System being remotely managed
Off = Deactivated
Green = Normal
Amber = System degraded
Red = System critical
To identify components in degraded or critical state, see
3. Power On/Standby
button and system power
LED
Green = System on
Amber = System in standby, but power is still applied
Off = Power cord not attached or power supply failure
Figure 7 HP X3800 G2 rear panel components
.
1. PCIe slot 5
X3000 G2 Network Storage System User Guide 25
2. PCIe slot 6
3. PCIe slot 4 (occupied by P812 Smart Array controller)
4. PCIe slot 2
5. PCIe slot 3 (SAS Expander)
6. PCIe slot 1
7. Power supply 2 (standard)
8. Power supply 1 (standard)
9. USB connectors (2)
10. Video connector
11. NIC 1 connector
12. NIC 2 connector
13. Mouse connector
14. Keyboard connector
15. Serial connector
16. iLO 3 connector
17. NIC 3 connector
18. NIC 4 connector
Figure 8 HP X3800 G2 rear panel LEDs and buttons
.
Table 5 HP X3800 G2 rear panel LED and button descriptions
StatusItem / Description
1. Power supply LED
2. UID LED/button
Storage system component identification26
Green = Normal
Off = System is off or power supply has failed
Blue = Activated
Flashing blue = System being managed remotely
Off = Deactivated
3. NIC/iLO 3 activity LED
StatusItem / Description
Green = Network activity
Flashing green = Network activity
Off = No network activity
4. NIC/iLO 3 link LED
Green = Network link
Off = No network link
HP X3800sb G2 Network Storage Gateway Blade hardware components
The following figures show components and LEDs located on the front panel of the X3800sb G2
Network Storage Gateway.
Figure 9 HP X3800sb G2 front panel components
.
1. SUV connector
2. Serial label pull tab
3. Release button
4. Server blade release lever
5. Power On / Standby button
6. Hard drive bay 1
7. Hard drive bay 2
X3000 G2 Network Storage System User Guide 27
Figure 10 HP X3800sb G2 front panel LEDs
.
Table 6 HP X3800sb G2 front panel LED descriptions
StatusItem / Description
Blue = Identified
1. UID LED
2. Health LED
3. Flex-10 NIC 1 LED
4. Flex-10 NIC 2 LED
Blue flashing = Active remote management
Off = No active remote management
Green = Normal
Flashing = Booting
Amber = Degraded condition
Red = Critical condition
Green = Network linked
Green flashing = Network activity
Off = No link or activity
Green = Network linked
Green flashing = Network activity
Off = No link or activity
—5. Reserved
Green = On
6. System power LED
Amber = Standby (auxiliary power available
Off = Off
SAS and SATA hard drive LEDs
The following figure shows SAS/SATA hard drive LEDs. These LEDs are located on all HP ProLiant
hot plug hard drives.
Storage system component identification28
Figure 11 SAS/SATA hard drive LEDs
.
Table 7 SAS and SATA hard drive LED combinations
1. Fault/UID LED (amber/blue)
Amber, flashing regularly (1
Hz)
Amber, flashing regularly (1
Hz)
(green)
On, off, or flashingAlternating amber and blue
On, off, or flashingSteadily blue
On
Flashing regularly (1 Hz)
Flashing regularly (1 Hz)Off
Status2. Online/activity LED
The drive has failed, or a predictive failure alert has
been received for this drive; it also has been selected
by a management application.
The drive is operating normally, and it has been selected by a management application.
A predictive failure alert has been received for this
drive. Replace the drive as soon as possible.
The drive is online, but it is not active currently.OnOff
Do not remove the drive. Removing a drive may
terminate the current operation and cause data loss.
The drive is part of an array that is undergoing capacity expansion or stripe migration, but a predictive
failure alert has been received for this drive. To
minimize the risk of data loss, do not replace the
drive until the expansion or migration is complete.
Do not remove the drive. Removing a drive may
terminate the current operation and cause data loss.
The drive is rebuilding, or it is part of an array that
is undergoing capacity expansion or stripe migration.
Amber, flashing regularly (1
Hz)
Flashing irregularly
OffSteadily amber
The drive is active, but a predictive failure alert has
been received for this drive. Replace the drive as
soon as possible.
The drive is active, and it is operating normally.Flashing irregularlyOff
A critical fault condition has been identified for this
drive, and the controller has placed it offline. Replace the drive as soon as possible.
X3000 G2 Network Storage System User Guide 29
1. Fault/UID LED (amber/blue)
Status2. Online/activity LED
(green)
Amber, flashing regularly (1
Hz)
Off
OffOff
Systems Insight Display LEDs
The HP Systems Insight Display LEDs represent the system board layout. The display enables diagnosis
with the access panel installed.
A predictive failure alert has been received for this
drive. Replace the drive as soon as possible.
The drive is offline, a spare, or not configured as
part of an array.
Figure 12 Systems Insight Display LEDs
.
Table 8 Systems Insight Display LED descriptions
StatusItem / Description
Green = Network link
1. NIC link/activity LED
2. Power cap
Storage system component identification30
Flashing green = Network link and activity
Off = No link to network. If the power is off, view the rear panel RJ-45
LEDs for status.
To determine Power cap status, see “Systems Insight Display LED combin-
ations” on page 31.
StatusItem / Description
Green = AMP mode enabled
3. AMP status
All other LEDs
Amber = Failover
Flashing amber = invalid configuration
Off = AMP modes disabled
Off = Normal
Amber =Failure
For detailed information on the activation of these LEDs, see “Systems
Insight Display LED combinations” on page 31.
Systems Insight Display LED combinations
When the internal health LED on the front panel illuminates either amber or red, the server is
experiencing a health event. Combinations of illuminated system LEDs and the internal health LED
indicate system status.
Table 9 Systems Insight Display LEDs and internal health LED combinations
Systems Insight
Display LED and
color
Processor failure,
socket X (amber)
PPM failure, slot X
(amber)
DIMM failure, slot X
(amber)
DIMM failure, all
slots in one bank
(amber)
color
Red
Red
Red
StatusInternal health LED
One or more of the following conditions may exist:
• Processor in socket X has failed.
• Processor X is not installed in the socket.
• Processor X is unsupported.
• ROM detects a failed processor during POST.
Processor in socket X is in a pre-failure condition.Amber
One or more of the following conditions may exist:
• PPM in slot X has failed.
• PPM is not installed in slot X, but the corresponding pro-
cessor is installed.
DIMM in slot X has failed.Red
DIMM in slot X is in a pre-failure condition.Amber
One or more DIMMs has failed. Test each bank of DIMMs by
removing all other DIMMs. Isolate the failed DIMM by replacing
each DIMM in a bank with a known working DIMM.
DIMM failure, all
slots in all banks
(amber)
Online spare
memory (amber)
Red
One or more DIMMs has failed. Test each bank of DIMMs by
removing all other DIMMs. Isolate the failed DIMM by replacing
each DIMM in a bank with a known working DIMM.
Bank X failed over to the online spare memory bank.Amber
X3000 G2 Network Storage System User Guide 31
Systems Insight
Display LED and
color
Online spare
memory (flashing
amber)
StatusInternal health LED
color
Invalid online spare memory configuration.Red
Online spare
memory (green)
Mirrored memory
(amber)
Mirrored memory
(flashing (amber)
Mirrored memory
(green)
Overtemperature
(amber)
Riser interlock (amber)
Fan (amber)
Online spare memory enabled and not failed.Green
Bank(s) X failed over to the mirrored memory bank(s).Amber
Invalid mirrored memory configuration.Red
Mirrored memory enabled and not failed.Green
The Health Driver has detected a cautionary temperature level.Amber
The server has detected a hardware critical temperature level.Red
PCI riser cage is not seated.Red
One fan has failed or is removed.Amber
Two or more fans have failed or are removed.Red
Storage system component identification32
3 Administration tools
HP StorageWorks X3000 G2 Network Storage Systems include several administration tools to simplify
storage system management tasks.
Microsoft Windows Storage Server 2008 R2 administration tools
Microsoft® Windows® Storage Server 2008 R2 operating systems provide a user interface for initial
server configuration, unified storage system management, simplified setup and management of storage
and shared folders, and support for Microsoft iSCSI Software Target. It is specially tuned to provide
optimal performance for network-attached storage. Windows Storage Server 2008 R2 provides
significant enhancements in share and storage management scenarios, as well as integration of
storage system management components and functionality.
Remote Desktop for Administration
You can remotely administer storage systems by using Remote Desktop for Administration (formerly
known as Terminal Services in Remote Administration mode). You can use it to administer a computer
from virtually any computer on your network. Based on Terminal Services technology, Remote Desktop
for Administration is specifically designed for server management.
Remote Desktop for Administration does not require the purchase of special licenses for client computers
that access the server. It is not necessary to install Terminal Server Licensing when using Remote
Desktop for Administration.
You can use Remote Desktop for Administration to log on to the server remotely with any of the
following features:
• Remote Desktop Connection
• Remote Web Administration
• Windows Server Remote Administration Applet
For more information, see the Windows Storage Server 2008 R2 Help.
Share and Storage Management
With the Share and Storage Management snap-in provided in this release, you can more easily set
up and manage shared folders and storage. Share and Storage Management provides the following:
• MMC-based management of shared folders and storage.
• Provision Storage Wizard for creating and configuring storage for file sharing and block sharing,
including creating LUNs on storage subsystems, as well as creating and formatting volumes on
LUNs or server disks.
X3000 G2 Network Storage System User Guide 33
NOTE:
You must have a VDS Hardware Provider that is appropriate for your storage system installed in
order to provision storage on an iSCSI target. If you have Microsoft iSCSI Software Target running
on a Windows Storage Server 2008 R2 storage system, install the Microsoft iSCSI Software Target
VDS Hardware Provider on the client computer.
• Provision a Shared Folder Wizard for creating and configuring shared folders that can be accessed
by using either the server message block (SMB) or NFS protocol.
• Single Instance Storage (SIS) can be enabled or disabled for each volume that is displayed in
Share and Storage Management. SIS recovers disk space by reducing the amount of redundant
data stored on a volume. It identifies identical files, storing only a single copy of the file in the SIS
Common Store, and replacing the files with pointers to the file in the SIS Common Store.
The Share and Storage Management snap-in makes it possible to complete most of the administrative
tasks that are required to create and manage shared folders and volumes without having to use the
Shared Folder Management, Storage Manager for SANs, or Disk Management snap-ins. These tasks
include configuring quotas to restrict the quantity of data, configuring file screening to prevent certain
file types or only allowing certain file types defined by the administrator, and enabling indexing.
For more information, see the Windows Storage Server 2008 R2 Help.
Single Instance Storage
The Single Instance Storage (SIS) feature reduces the amount of space that is used to store data on a
volume. SIS does this by replacing duplicate files with logical links that point to a single copy of the
file in the SIS Common Store, which is a hidden folder that is located in the root directory of the
volume.
SIS consists of two primary components that together maintain a database of file signatures. These
components include:
• Groveler service - The Groveler service scans the hard-disk volumes on a server for duplicate
copies of files. If the service locates duplicate copies of files, the information about the duplicates
is sent to the Single Instance Storage Filter. The Groveler service runs as a user-level service.
• Single Instance Storage Filter - The Single Instance Storage Filter is a file system filter service that
manages duplicate copies of files on hard-disk volumes. When notified by the Groveler service
of duplicate copies of files, this component copies one instance of a duplicate file into a central
folder. The duplicate is then replaced by a link (a reparse point) to the central copy. The link file
contains information about the original file, such as its current location, size, and attributes. The
Single Instance Storage Filter runs in kernel mode.
The Single Instance Storage Filter service cannot be stopped. If this service is disabled, the linked files
are not accessible. If the central folder is deleted, the linked files can become permanently inaccessible.
If you stop the Groveler service, the files cannot be automatically linked, but the existing linked files
can still be accessible.
You can enable SIS on a maximum of 20 volumes per computer. SIS cannot act upon any files that
are referenced through junction points, and it cannot be used with any file system except the NTFS
file system. SIS will not process files that are 32 kilobytes or less in size.
If you need to access data that is stored on a SIS volume, which might be required for backup and
recovery operations, you must either run or have installed Single Instance Storage Filter on your
computer.
Backup and recovery by using SIS has the following requirements:
Administration tools34
• The backup software used must support SIS-enabled volumes.
• The SIS volume, SIS Common Store folder, and reparse points (links) to the files must be restored
to a Windows 2000 NTFS version 5.0 (or later) file system or partition that supports reparse points
or junction points.
• The Single Instance Storage Filter must be installed or enabled to access the data in the SIS volume.
• The backup program must be capable and configured to backup and restore the reparse points
or junction points (links) to the files, and the SIS volume and the SIS Common Store folder must
be selected.
To enable Single Instance Storage on a volume:
1. In Server Manager, select Roles > File Services > Share and Storage Management.
2. Select the Volumes tab.
3. Right-click a volume and select Properties.
4. Select the Advanced tab.
5. Select the Enable SIS on this volume check box.
6. Click OK.
For more information, see the Windows Storage Server 2008 R2 Help.
Print Management
Print Management is an MMC snap-in that you can use to view and manage printers and print servers
in your organization. You can use Print Management from any computer running Windows Storage
Server 2008 R2, and you can manage all network printers on print servers running Windows 2000
Server, Windows Server 2003, Windows Storage Server 2003, Windows Storage Server 2003 R2,
Windows Storage Server 2008, or Windows Storage Server 2008 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 2008 R2 Help.
Network File System (NFS) User Mapping
Network File System (NFS) 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 HP X3000 G2 Network Storage Systems.
All of the following types of NFS account mapping are supported: Active Directory® Domain Services
(AD DS) mapped user access, Active Directory® Lightweight Directory Services (AD LDS) mapped
user access, unmapped anonymous user access, and unmapped UNIX user access.
For more detailed information about each of these access methods, see the NFS Account Mapping
in Windows Server 2008 R2 whitepaper, which is available for download at:
X3000 G2 Network Storage System User Guide 35
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=
5f4c294c-8692-4235-8236-8ea809ae71f7 .
Configuring AD LDS
To simplify AD LDS mapped user access, HP provides the scripts that Microsoft describes in the NFS
Account Mapping in Windows Server 2008 R2 whitepaper. The whitepaper describes two phases
of scripts. Phase 1 scripts are used to install and prepare your system for NFS account mapping.
Phase 2 scripts are used to configure specific users and groups for NFS account mapping.
For more detailed information about the Phase 1 and Phase 2 scripts, see the Microsoft Knowledge
Base article Description of scripts to use to simplify user account mapping between a UNIX client and
a Windows-based server at http://support.microsoft.com/kb/973840.
Microsoft hotfix 2222746
HP supports Microsoft hotfix 2222746. This hotfix applies to Windows Storage Server 2008 R2 as
well as the products listed in the KB article. The hotfix addresses the following problem: File permissions
are incorrectly set when you share a folder on a Windows Server 2008-based or Windows Storage
Server 2008-based NFS server. For full details of this hotfix, see http://support.microsoft.com/kb/
2222746.
The incorrect behavior that the hotfix addresses occurs when using AD LDS mapped user access. HP
has installed this hotfix on the storage system but has not enabled it by default. You can enable it by
setting the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NfsServer\NlmNsm\AutoCorrectPrimaryGroup
Type: REG_DWORD
Value: 0x1
After enabling the hotfix by setting the registry subkey, you must restart the storage system in order
for the hotfix to take effect.
Phase 1 scripts
Phase 1 scripts are located in the c:\hpnas\components\postinstaller\adlds folder. You
enable AD LDS NFS mapping by running factory-setup-adlds.cmd. The command is run without any
arguments. The script installs two Roles and one Instance:
• Active Directory Lightweight Directory Services (AD LDS) Role
• An AD LDS Instance named NFSInstance.
• Services for Network File System (NFS) under the File Services Role
To verify the installation of the AD LDS Role and Instance, in Administrative Tools, select Server
Manager. If the AD LDS Role was successfully installed, you will see Active Directory Lightweight
Directory Services listed under Roles. Click on it and you will see NFSInstance listed under
SystemServices if that instance was successfully installed.
Administration tools36
Figure 13 AD LDS Role and Instance
.
To verify the installation of the Services for Network File System (NFS) Role, in Server Manager, under
Roles, click File Services. In the System Services table, Server for NFS is listed.
Phase 2 scripts
Phase 2 scripts are located in the c:\hpnas\components\ADLDS folder. You create NFS mappings
for users and groups by running the nfs-adlds-config.js script. This script takes as inputs a standard
UNIX password file and a standard UNIX group file. For each user or group in these files a Windows
user or group account is created if one does not already exist. Next, the script examines the UNIX
password file to extract the User ID and Group ID of each user. From these, a mapping is created on
the Windows system that associates the User ID and Group ID with the UNIX account that has the
same User ID and Group ID. Similarly, the script examines the UNIX group file, extracts the Group
ID, and forms a mapping on the Windows system that associates the Group ID with the UNIX group
having the same ID. This mapping is what allows directories and files to be accessed from either the
Windows NFS server or the UNIX NFS client using the same User ID and Group ID.
The nfs-adlds-config.js script will also add Windows users to the appropriate Windows groups for
the newly created user and group accounts. It does this by examining the relationships between users
and groups in the password and group files that were given as inputs to the script.
Password and Group file syntax
You can create the password and group files yourself or copy them from the NFS client at /etc/passwd
and /etc/group.
Each line of a standard UNIX password file follows this format:
user:password:UID:GID:comment:home directory:command shell
All fields are required, but the only fields that are used are the user, UID, and GID fields. If you are
creating these files yourself, you may want to leave the other fields blank.
X3000 G2 Network Storage System User Guide 37
Each line of a standard UNIX group file follows this format:
group:password:GID:group list
All fields are required, but only the group, GID, and group list fields are used. The GID field
value must match the GID field value in the password file for those users that belong to the group.
NOTE:
If you create the group and password files, you must have corresponding users and groups on the
UNIX system. The correspondence is through the numeric UID and GID; however, the user names
and group names can be different. For example, the UNIX root group can be associated with a
Windows group named rootgroup as long as its group ID of 0 is the same between them.
IMPORTANT:
• User names in the password file cannot match group names in the group file. Windows does not
allow user names and group names to be the same. An example of this is the root user which
typically belongs to the root group on a UNIX system. You would need to rename one of these.
For example, in the group file, you might rename the root group to rootgroup.
• User and group names in Windows are case insensitive. If the password or group files contain
accounts whose names differ only in their case, you will need to delete or rename entries in those
files.
• Users within the password file must have unique user IDs. Groups within the group file must have
unique group IDs.
• All users included in the password file are imported. Consider editing the file before running the
configuration script to retain only the users that you want mapped.
• All groups in the group file are imported. Consider editing the file before running the configuration
script to retain only the groups that you want mapped.
Script execution
You configure NFS mapping for AD LDS by executing the nfs-adlds-config.js script that is located in
the c:\hpnas\components\ADLDS folder. Executing the script with no command line options will
display the following help screen:
Administration tools38
Figure 14 AD LDS script execution help screen
.
As a best practice, specify all of the above parameters so that Windows accounts and NFS mappings
are created; however, you can provide finer control as follows. If you omit the /ldf option, the script
creates Windows accounts but not NFS mappings. Likewise, omitting the /usercmd option creates
NFS mappings but not Windows accounts.
The /execute option controls whether Windows accounts and NFS mappings are actually made to
the system. Omitting the /execute option will still create the output files (these are the
generateusers.cmd and ldf.out files as shown above). You can then examine these files to
see the actions that would have been performed had the /execute option been included.
The /userpassword option specifies the password that the script assigns when creating Windows
accounts for new users. You must use a password that meets the password strength requirements of
your system. By default Windows Storage Server 2008 R2 requires strong passwords. If you specify
a password that does not meet the requirements, the script will not inform you. It will create the
Windows account with a blank password and establish the NFS mapping. Until you change the
password to a non-blank value, NFS mapping is disabled for that Windows account. Any attempts
in UNIX to use that mapped user will result in Permissions Denied or Input/Output errors.
NOTE:
If users are created with a blank password because the /userpassword option was not given or
the specified password does not meet the password strength requirements of the system, those users
can log into the system console without the security that a strong password provides.
Verifying script execution
The following steps describe how to verify that the proper Windows accounts were created and the
NFS mappings were made when the nfs-adlds-config.js script is run. If there are problems, examine
the log file specified by using the /log option.
After the script is successfully executed, the users in the password file exist as Windows Users and
the groups from the group file exist as Windows Groups. You can verify this with Server Manager:
1. Click Start, right click Computer, and then select Manage.
2. Expand the Configuration and Local Users and Groups nodes.
The imported users and groups are listed in the Users and Groups folders, respectively.
X3000 G2 Network Storage System User Guide 39
The newly-created NFS mappings are stored as Active Directory objects and can be verified as follows:
1. Click Start > Administrative Tools > ADSI Edit.
2. On the Action menu, select Connect to....
3. In the Connection Settings dialog box, under Computer, select the radio button labeled Select or
type a domain or server: (Server|Domain[:port]).
4. In the Select or type a domain or server: (Server|Domain[:port]) field, type localhost:389 and
then click OK.
Figure 15 ADSI Edit Connection Settings dialog box
.
5. Expand the Default naming context [localhost:389] node to open CN=nfs, DC=nfs, and then
CN=Users.
The list of NFS-mapped users and groups appears under CN=Users. In the figure below, root, john
and mary are NFS mapped users. rootgroup and users are NFS mapped groups. These users and
groups must also exist on the UNIX system in order for NFS mapping to work correctly between UNIX
and Windows.
Administration tools40
Figure 16 NFS-mapped users and groups in ADSI Edit
.
Because the imported users and groups are now Windows users and groups as well as UNIX users
and groups, you can use NFS sharing so that volumes, folders and files are visible in both the Windows
file system and the UNIX file system. When you set ownership or permissions in the Windows file
system, the proper ownership and permissions are set on the UNIX side. Likewise, setting ownership
or permissions in the UNIX file system results in proper values on the Windows file system.
Shared access example
The following example illustrates how to use the provided AD LDS scripts. By following the procedures,
you will create a password and group file that serves as input for the nfs-adlds-config.js script. You
will then create a Windows folder that you will set to be NFS shared by the group Everyone. You will
then mount this folder in UNIX and observe how a file created in UNIX is owned by the corresponding
mapped user on the Windows system. Similarly you will create a file in Windows, change its ownership
to an NFS mapped user, and observe that it is owned by the proper user and group in UNIX. Finally,
you will restrict the properties of the Windows shared folder so that it is accessible by a single user
instead of the group Everyone.
NOTE:
This example assumes that the system is not part of an Active Directory domain or is part of an Active
Directory domain but will be using AD LDS for user name mapping.
IMPORTANT:
To ensure proper NFS user name mapping behavior when AD LDS is used for user name mapping, you must
enable Microsoft hotfix 2222746, which is installed on the storage system but is not enabled it by default. You
can enable it by setting the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NfsServer\NlmNsm\AutoCorrectPrimaryGroup
Type: REG_DWORD
Value: 0x1
After setting the registry subkey, restart the storage system.
X3000 G2 Network Storage System User Guide 41
Step 1
Step 2
If you have not already run the Phase 1 script factory-setup-adlds.cmd, do so now. The script is located
in the c:\hpnas\components\postinstaller\adlds folder.
On the Windows system, in the C:\hpnas\components\ADLDS folder, create a file named
passwdfile containing:
root:x:0:0:root:/root:/bin/bash
user1:x:2701:5700:A sample user:/home/user1:/bin/sh
Create a file named groupfile containing:
rootgroup:x:0:
allusers:x:5700:
On the UNIX system, edit the /etc/passwd file to have an account for user1 with a user ID of 2701
and a group ID of 5700. Edit the /etc/group file to have a group account for allusers with a group
ID of 5700. On the UNIX side you do not need to create a group named rootgroup because the
existing group named root has a group ID of 0.
NOTE:
If you are taking the /etc/group file from the UNIX system and preparing it as input for
nfs-adlds-config.js, you must rename the root group to something else such as
rootgroup
. This solves
the conflict with the root user. As described earlier, Windows does not allow the same name to be
used for both a user and a group.
Step 3
Step 4
Execute the phase 2 script c:\hpnas\components\ADLDS in a command window as follows:
nfs-adlds-config.js /passwd:passwdfile /group:groupfile /ldf:out.ldf /
usercmd:generateusers.cmd /userpassword:c0mpleX! /execute /log:log.txt
Examine log.txt to ensure that there are no errors. Error messages that read System error 1379: The
specified local group already exists can be ignored.
Follow the steps in “Verifying script execution” on page 39 to verify that appropriate Windows user
and group accounts are created and expected NFS mappings are established.
Create a folder C:\NfsTest. Right-click the folder and select Properties. Click the NFS Sharing tab and
then click the Manage NFS Sharing button. Check the Share this folder check box. In the Share name
field, type NfsTest. Clear the Enable unmapped user access check box.
Administration tools42
Figure 17 NFS Advanced Sharing dialog box
.
Click the Permissions button. In the Type of access list, select Read-Write. Check the Allow root access
check box.
Figure 18 NFS Share Permissions dialog box
.
Click OK twice to return to the NfsTest Properties dialog box.
X3000 G2 Network Storage System User Guide 43
Step 5
In the NfsTest Properties dialog box, select the Security tab. This tab shows the current security settings
for the folder. The following steps will add permissions for Everyone to have access to the NfsTest
folder. To do this, click Edit… and then click Add…. Under Group or user names: type Everyone and
then click OK. In the Permissions for NfsTest dialog box, check the Allow check box for Full control
under Permissions for Everyone.
Step 6
Step 7
Figure 19 Permissions for NfsTest dialog box
.
Click OK to dismiss the Permissions for NfsTest dialog box and then click OK to dismiss the NfsTest
Properties dialog box.
On the UNIX system as root, mount the NFS share. A typical command is as follows where
10.30.15.20 is the IP address of the Windows system:
> mkdir /mnt/nfstest
> mount –t nfs 10.30.15.20:/NfsTest /mnt/nfstest
As root, create a file in the mounted directory:
> touch /mnt/nfstest/rootfile
On the Windows system, open Windows Explorer to C:\NfsTest. Properties for rootfile are displayed.
To display the owner of rootfile, add the Owner column: right-click the column header, select More...,
Administration tools44
Step 8
check the Owner check box and then click OK. Note that root is part of the owner name. This verifies
that NFS mapping is functional for the root user.
On the Windows system as Administrator, create a file file.txt in C:\NfsTest. Windows Explorer now
displays its properties:
On the UNIX system, issue a listing of the /mnt/nfstest directory. This listing displays the following
information. Note that file permissions on your system may be different than those shown here.
The reason that the owner of file.txt is nfsnobody is that the file is owned by the Windows Administrators
group, which is not an NFS mapped group.
Step 9
In this step, you will change the owner of file.txt to user1. On the Windows system, in Windows
Explorer, right-click file.txt, select Properties and then select the Security tab. Click Advanced, select
the Owner tab, and then click Edit… . Click Other users or groups... , type user1 in the dialog box,
and then click OK.
Figure 20 Advanced Security Settings for file.txt
.
Click OK three times to return to Windows Explorer. The file file.txt is now owned by user1.
X3000 G2 Network Storage System User Guide 45
Step 10
Step 11
On the UNIX system, issue a listing of the /mnt/nfstest directory. Because you changed the owner
of file.txt on the Windows system to user1, the owner of the file on the UNIX side is also user1.
Because user1 is in the allusers group on the Windows system, the group ownership of file.txt is
allusers on the UNIX side.
If the group for file.txt is listed as nfsnobody, you must enable Microsoft hotfix 2222746 and restart
the storage system as described in “Shared access example” on page 41.
In this step, you will modify the permissions on the shared folder to restrict access to the shared folder
to a group smaller than Everyone by changing the ownership of the shared folder and then specifying
permissions for that owner.
First, remove the file rootfile from /mnt/nfstest on the UNIX system.
In Windows Explorer, right-click the NfsTest folder, select Properties, and then select the Security tab.
Click Advanced, select the Owner tab, and then click Edit…. Click Other users or groups… and type
user1 in the Enter the object name to select field.
Figure 21 Select User or Group dialog box
.
Click OK to return to the Advanced Security Settings for NfsTest dialog box. Check the Replace owner
on subcontainers and objects check box.
Administration tools46
Figure 22 Replace owner on subcontainers and objects
.
Click OK four times to dismiss the Properties dialog box. Return to the Properties dialog box, select
the Security tab, and then click Edit. Select Everyone in the list of groups and user names and then
click Remove. Next, click Add and add user1. Select full control for its permissions.
Figure 23 Permissions for NfsTest dialog box
.
Click OK twice to dismiss the NfsTest Permissionsand Properties dialog boxes.
On the UNIX side, you can now issue the su user1 command, then issue the cd /mnt/nfstest
command, and create files in that directory.
You can also access the mounted directory as root. If you want to restrict this, return to the NFS Share
Permissions dialog box as shown in Figure 18 on page 43 and clear the Allow root access check
box.
X3000 G2 Network Storage System User Guide 47
Administration tools48
4 Storage management overview
This chapter provides an overview of some of the components that make up the storage structure of
the storage system.
Storage management elements
Storage is divided into four major divisions:
• Physical storage elements
• Logical storage elements
• File system elements
• File sharing elements
Each of these elements is composed of the previous level's elements.
Storage management example
Figure 24 depicts many of the storage elements that one would find on a storage device. The following
sections provide an overview of the storage elements.
X3000 G2 Network Storage System User Guide 49
Figure 24 Storage management process example
.
Physical storage elements
The lowest level of storage management occurs at the physical drive level. Minimally, choosing the
best disk carving strategy includes the following policies:
• Analyze current corporate and departmental structure.
• Analyze the current file server structure and environment.
• Plan properly to ensure the best configuration and use of storage.
• 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.
Storage management overview50
Arrays
• Include the appropriate number of physical drives in the arrays to create logical storage elements
of desired sizes.
See Figure 25. With an array controller installed in the system, the 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 storage system model, array configuration may not be possible or necessary.
Figure 25 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 Figure 26.
Figure 26 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 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.
X3000 G2 Network Storage System User Guide 51
Fault tolerance
Drive failure, although rare, is potentially catastrophic. For example, using simple striping as shown
in Figure 26, failure of any hard drive leads to failure of all logical drives in the same array, and
hence to data loss.
To protect against data loss from hard drive failure, storage systems should be configured with fault
tolerance. HP recommends adhering to RAID 5 configurations.
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 10 Summary of RAID methods
Maximum number of hard
drives
Tolerant of single hard
drive failure?
Tolerant of multiple simultaneous hard drive failures?
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.
RAID 0 Strip-
ing (no fault
tolerance)
No
RAID 1+0 Mir-
roring
If the failed
drives are not
mirrored to
each other
RAID 5 Distrib-
uted Data
Guarding
RAID 6 (ADG)
Storage system dependent14N/AN/A
YesYesYesNo
Yes (two drives can fail)No
Logical storage elements
Logical storage elements consist of those components that translate the physical storage elements to
file system elements. The storage system 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.
Storage management overview52
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.
Figure 27 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 storage 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 disks to dynamic and
back to basic and to manage the volumes residing on dynamic disks. Other options include the ability
to delete, extend, mirror, and repair these elements.
Partitions
Volumes
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.
When planning dynamic disks and volumes, there is a limit to the amount of growth a single volume
can undergo. Volumes are limited in size and can have no more than 32 separate LUNs, with each
LUN not exceeding 2 terabytes (TB), and volumes totaling no more than 64 TB of disk space.
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
X3000 G2 Network Storage System User Guide 53
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.
NOTE:
Dynamic disks cannot be used for clustering configurations because Microsoft Cluster only supports
basic disks.
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 storage system supports several file sharing protocols, including Distributed File System (DFS),
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, a storage 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.
Storage management overview54
Shadow copies should 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.
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.
Formats consist of NTFS, FAT32, and FAT. All three types can be used on the storage system. However,
VSS can only use volumes that are NTFS formatted. Also, quota management is possible only on
NTFS.
Clustered server elements
HP StorageWorks X3000 Network Storage Systems support 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.
Network adapter teaming
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.
Management tools
HP Systems Insight Manager
HP SIM is a web-based application that allows system administrators to accomplish normal
administrative tasks from any remote location, using a web browser. HP SIM provides device
management capabilities that consolidate and integrate management data from HP and third-party
devices.
IMPORTANT:
You must install and use HP SIM to benefit from the Pre-Failure Warranty for processors, SAS and
SCSI hard drives, and memory modules.
X3000 G2 Network Storage System User Guide 55
For additional information, refer to the Management CD in the HP ProLiant Essentials Foundation Pack
or the HP SIM website (http://www.hp.com/go/hpsim).
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
thirdparty SNMP management platforms. Management Agents are installed with every SmartStart
assisted installation or can be installed through the HP 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 HP ProLiant
Essentials Foundation Pack or the HP website (http://www.hp.com/servers/manage).
Storage management overview56
5 File server management
This chapter begins by identifying file services in Windows Storage Server 2008 R2. The remainder
of the chapter describes the many tasks and utilities that play a role in file server management.
File services features in Windows Storage Server 2008 R2
Storage Manager for SANs
The Storage Manager for SANs (also called Simple SAN) snap-in enables you to create and manage
the LUNs that are used to allocate space on storage arrays. Storage Manager for SANs can be used
on SANs that support Virtual Disk Server (VDS). It can be used in both Fibre Channel and iSCSI
environments.
For more information on Storage Manager for SANs, see the online help.
Single Instance Storage
Single Instance Storage (SIS) provides a copy-on-write link between multiple files. Disk space is
recovered by reducing the amount of redundant data stored on a server. If a user has two files sharing
disk storage by using SIS, and someone modifies one of the files, users of the other files do not see
the changes. The underlying shared disk storage that backs SIS links is maintained by the system and
is only deleted if all the SIS links pointing to it are deleted. SIS automatically determines that two or
more files have the same content and links them together.
File Server Resource Manager
File Server Resource Manager is a suite of tools that allows administrators to understand, control, and
manage the quantity and type of data stored on their servers. By using File Server Resource Manager,
administrators can place quotas on volumes, actively screen files and folders, and generate
comprehensive storage reports.
By using File Server Resource Manager, you can perform the following tasks:
• Create quotas to limit the space allowed for a volume or folder and to generate notifications when
the quota limits are approached and exceeded.
• Create file screens to screen the files that users can save on volumes and in folders and to send
notifications when users attempt to save blocked files.
• Schedule periodic storage reports that allow users to identify trends in disk usage and to monitor
attempts to save unauthorized files, or generate the reports on demand.
Windows SharePoint Services
Windows SharePoint Services is an integrated set of collaboration and communication services
designed to connect people, information, processes, and systems, within and beyond the organization
firewall.
X3000 G2 Network Storage System User Guide 57
File services management
Information about the storage system in a SAN environment is provided in the HP StorageWorks SAN
Manuals page located on the HP web site at www.hp.com/go/SDGManuals.
Configuring data storage
HP StorageWorks X3000 G2 Network Storage Systems are configured only for the operating system.
The administrator must configure data storage for the storage system.
Configuring additional data storage involves creating arrays, logical disks, and volumes. Table 11
shows the general task areas to be performed as well as the utilities needed to configure storage for
an HP Smart Array-based storage system.
Table 11 Tasks and utilities needed for storage system configuration
Storage management utilityTask
HP Array Configuration UtilityCreate disk arrays
HP Array Configuration UtilityCreate logical disks from the array space
Windows Disk ManagementVerify newly created logical disks
Windows Disk ManagementCreate a volume on the new logical disk
• Create disk arrays—On storage systems with configurable storage, physical disks can be arranged
as RAID arrays for fault tolerance and enhanced performance, and then segmented into logical
disks of appropriate sizes for particular storage needs. These logical disks then become the volumes
that appear as drives on the storage system.
CAUTION:
The single logical drive is configured for the storage system operating system and should not be
altered in any manner. If the operating system logical drive is altered, the system recovery process
may not function properly when using the System Recovery DVD. Do not tamper with the local C:
volume. This is a reserved volume and must be maintained as it exists.
The fault tolerance level depends on the amount of disks selected when the array was created. A
minimum of two disks is required for RAID 0+1 configuration, three disks for a RAID 5 configuration,
and four disks for a RAID 6 (ADG) configuration.
• Create logical disks from the array space—Select the desired fault tolerance, stripe size, and size
of the logical disk.
• Verify newly created logical disks—Verify that disks matching the newly created sizes are displayed.
• Create a volume on the new logical disk—Select a drive letter and enter a volume label, volume
size, allocation unit size, and mount point (if desired).
Storage management utilities
The storage management utilities preinstalled on the storage system include the HP Array Configuration
Utility (ACU).
File server management58
Array management utilities
Storage devices for RAID arrays and LUNs are created and managed using the array management
utilities mentioned previously. For HP Smart Arrays use the ACU.
NOTE:
The ACU is used to configure and manage array-based storage. Software RAID-based storage systems
use Microsoft Disk Manager to manage storage. You need administrator or root privileges to run the
ACU.
Array Configuration Utility
The HP ACU supports the Smart Array controllers and hard drives installed on the storage system.
To open the ACU from the storage system desktop:
NOTE:
If this is the first time that the ACU is being run, you will be prompted to select the Execution Mode
for ACU. Selecting Local Application Mode allows you to run the ACU from a Remote Desktop, remote
console, or storage system web access mode. Remote service mode allows you to access the ACU
from a remote browser.
1. Select Start > Programs > HP Management Tools > Array Configuration Utility.
2. If the Execution Mode for ACU is set to Remote Mode, log on to the HP System Management
Homepage. The default user name is administrator and the password is the Windows Storage
Server 2008 R2 administrator password that is set by the storage system administrator.
To open the ACU in browser mode:
NOTE:
Confirm that the ACU Execution Mode is set to remote service.
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 HP System Management Homepage. The default user name is administrator and
the default password is hpinvent.
3. Click Array Configuration Utility on the left side of the window. The ACU opens and identifies
the controllers that are connected to the system.
Some ACU guidelines to consider:
• Do not modify the single logical drive of the storage system; it is configured for the storage system
operating system.
• Spanning more than 14 disks with a RAID 5 volume is not recommended.
• Designate spares for RAID sets to provide greater protection against failures.
• RAID sets cannot span controllers.
X3000 G2 Network Storage System User Guide 59
• A single array can contain multiple logical drives of varying RAID settings.
• Extending and expanding arrays and logical drives is supported.
The HP Array Configuration Utility User Guide is available for download at http://www.hp.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 connec-
tion 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
• The single logical drive is configured for the storage system operating system and should not be
altered in any manner. If this logical drive is altered, the system recovery process may not function
properly when using the System Recovery DVD. Do not tamper with the local C: volume. This is a
reserved volume and must be maintained as it exists.
• HP does not recommend spanning array controllers with dynamic volumes. The use of software
RAID-based dynamic volumes is not recommended. Use the array controller instead; it is more efficient.
• 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
shadow copies, encryption, and compression.
• Only basic disks can be formatted as FAT or FAT32.
• Read the online Disk Management help found in the utility.
File server management60
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.
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” on page 85 .
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
X3000 G2 Network Storage System User Guide 61
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
quota-enabled 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.
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
File server management62
• 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 http://h18000.www1.hp.com/products/servers/proliantstorage/arraycontrollers/
documentation.html.
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.
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.
Expanding storage for EVA arrays using Command View EVA
Presenting a virtual disk offers its storage to a host. To make a virtual disk available to a host, you
must present it. You can present a virtual disk to a host during or after virtual disk creation. The virtual
disk must be completely created before the host presentation can occur. If you choose host presentation
during virtual disk creation, the management agent cannot complete any other task until that virtual
disk is created and presented. Therefore, HP recommends that you wait until a virtual disk is created
before presenting it to a host.
For more information, see the HP StorageWorks Command View EVA User Guide.
Expanding storage using the Array Configuration Utility
The Array Configuration Utility enables online capacity expansion of the array and logical drive for
specific MSA storage arrays, such as the MSA1000 and MSA1500. For more information, use the
ACU online help, or the procedures to “Expand Array” in the HP Array Configuration Utility User
Guide
Expand logical drive
This option in the ACU increases the storage capacity of a logical drive by adding unused space on
an array to the logical drive on the same array. The unused space is obtained either by expanding
an array or by deleting another logical drive on the same array. For more information, use the ACU
online help, or the “Extend logical drive” procedure in the HP Array Configuration Utility User Guide
X3000 G2 Network Storage System User Guide 63
Volume shadow copies
NOTE:
Select storage systems 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, a storage 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?
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.
File server management64
NOTE:
Shadow copies should 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.
X3000 G2 Network Storage System User Guide 65
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 storage systems.
If a separate volume will be used for the storage area (where shadow copies are stored), the maximum
size should 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 storage 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.
File server management66
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.
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 Figure 28) to
turn on the Shadow Copies feature, select the volumes to be copied, and determine the frequency
with which shadow copies are made.
Figure 28 System administrator view of Shadow Copies for Shared Folders
.
X3000 G2 Network Storage System User Guide 67
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
Figure 29). The cache file is located in a hidden protected directory titled “System Volume Information”
off of the root of each volume for which shadow copy is enabled.
Figure 29 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 Figure 30).
Figure 30 Shadow copies stored on a separate volume
.
File server management68
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.
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.
NOTE:
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
properties” on page 70.
Viewing a list of shadow copies
To view a list of shadow copies on a volume:
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.
X3000 G2 Network Storage System User Guide 69
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.
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:
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.
File server management70
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 storage system desktop
To access shadow copies from the storage system desktop:
The storage system desktop can be accessed by using Remote Desktop to manage shadow copies.
1. On the storage system desktop, double-click My Computer.
2. Right-click the volume name, and select Properties.
X3000 G2 Network Storage System User Guide 71
3. Click the Shadow Copies tab. See Figure 31.
Figure 31 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; this includes 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 currently only available for
Windows XP and Windows 2000 SP3+.
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.
NOTE:
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.
File server management72
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 View, Copy, or Restore from the
Previous Versions tab. (See Figure 32). Both individual files and folders can be restored.
Figure 32 Client GUI
.
When users view a network folder hosted on the storage system 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 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.
X3000 G2 Network Storage System User Guide 73
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
.@GMT-YYYY.MM.DD-HH:MM:SS. To prevent common tools from needlessly enumerating the
pseudo-subdirectories, 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
.@GMT-2003.04.27-04:00:00
.@GMT-2003.04.28-04:00:00
.@GMT-2003.04.29-04: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:
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 View.
5. View the folder and select the file or folder to recover. The view may be navigated multiple folders
deep.
File server management74
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.
Figure 33 Recovering a deleted file or folder
.
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:
1. Right-click the overwritten or corrupted file, and then click Properties.
2. Click Previous Versions.
3. To view the old version, click View. 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:
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.
X3000 G2 Network Storage System User Guide 75
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.
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 storage system supports several file-sharing protocols, including DFS, NFS, FTP, HTTP, and
Microsoft SMB. This section discusses overview information as well as procedures for the setup and
File server management76
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:
1. Using Windows Explorer, access the folder or file that needs to be changed, and then right-click
the folder.
X3000 G2 Network Storage System User Guide 77
2. Click Properties, and then click the Security tab.
Figure 34 Properties dialog box, 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 the Security 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.
File server management78
3. To modify ownership of files, or to modify individual file access level permissions, click Advanced.
Figure 35 illustrates the properties available on the Advanced Security Settings dialog box.
Figure 35 Advanced Security settings dialog box, Permissions tab
.
Other functionality available in the Advanced Security Settings dialog box is illustrated in Figure
35 and includes:
• Add a new user or group—Click Add, 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 click Edit.
X3000 G2 Network Storage System User Guide 79
4. Enable or disable permissions by selecting the Allow box to enable permission or the Deny box
to disable permission. If neither box is selected, permission is automatically disabled. Figure 36
illustrates the Edit screen and some of the permissions.
Figure 36 User or group Permission Entry dialog box
.
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.
File server management80
Figure 37 Advanced Security Settings dialog box, Auditing tab
.
5. Click Add to display the Select User or Group dialog box.
Figure 38 Select User or Group dialog box
.
NOTE:
Click Advanced to search for users or groups.
6. Select the user or group.
X3000 G2 Network Storage System User Guide 81
7. Click OK.
The Auditing Entry dialog box is displayed.
Figure 39 Auditing Entry dialog box for folder name NTFS Test
.
8. Select the desired Successful and Failed audits for the user or group.
9. Click OK.
NOTE:
Auditing must be enabled to configure this information. Use the local Computer Policy Editor to
configure the audit policy on the storage system.
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.
File server management82
Figure 40 Advanced Security Settings dialog box, Owner tab
.
The current owner of the file or folder is listed at the top of the screen. To take ownership:
1. Click the appropriate user or group in the Change owner to list.
2. If it is also necessary to take ownership of subfolders and files, enable the Replace owner on
subcontainers and objects box.
3. 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 the storage system 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 considerations
Planning the content, size, and distribution of shares on the storage system can improve performance,
manageability, and ease of use.
X3000 G2 Network Storage System User Guide 83
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 the storage system 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 storage system 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 file-level permissions override the share permissions.
Comparing administrative (hidden) and standard shares
CIFS 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 CIFS server.
File server management84
• Standard shares are shares that do not end in a $ character. Standard shares are listed whenever
a CIFS client browses for available shares on a CIFS server.
The storage system supports both administrative and standard CIFS 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-cluster-aware
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 servers. 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 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.
X3000 G2 Network Storage System User Guide 85
File screening management
On the File Screening Management node of the File Server Resource Manager snap-in, you can
perform the following tasks:
• 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.
Other Windows disk and data management tools
When you install certain tools, such as Windows Support Tools or Windows Resource Kit Tools,
information about these tools might appear in Help and Support Center. To see the tools that are
available to you, look in the Help and Support Center under Support Tasks, click Tools, and then click
Tools by Category.
NOTE:
The Windows Support Tools and Windows Resource Kit Tools, including documentation for these
tools, are available in English only. If you install them on a non-English language operating system
or on an operating system with a Multilingual User Interface Pack (MUI), you see English content
mixed with non-English content in Help and Support Center. To see the tools that are available to
you, click Start, click Help and Support Center, and then, under Support Tasks, click Tools.
Additional information and references for file services
Backup
HP recommends that you back up the print server configuration whenever a new printer is added to
the network and the print server configuration is modified.
HP StorageWorks Library and Tape Tools
HP StorageWorks Library and Tape Tools (L&TT) provides functionality for firmware downloads,
verification of device operation, maintenance procedures, failure analysis, corrective service actions,
and some utility functions. It also provides seamless integration with HP hardware support by generating
and e-mailing support tickets that deliver a snapshot of the storage system.
File server management86
Antivirus
For more information, and to download the utility, see the StorageWorks L&TT web site at http://
h18006.www1.hp.com/products/storageworks/ltt.
The server should be secured by installing the appropriate antivirus software.
X3000 G2 Network Storage System User Guide 87
File server management88
6 Cluster administration
One important feature of HP StorageWorks X3000 G2 Network Storage System models 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.
X3000 G2 Network Storage System User Guide 89
Figure 41 Storage system cluster diagram
.
Cluster terms and components
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
Cluster administration90
• CIFS 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.
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
Each cluster must have a shared disk called the Quorum disk. 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:
X3000 G2 Network Storage System User Guide 91
• 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
Figure 42 illustrates a typical cluster configuration with the corresponding storage elements. The
diagram progresses from the physical disks to the file shares, showing the relationship between both
the cluster elements and the physical devices underlying them. While the diagram only illustrates two
nodes, the same concepts apply for multi-node deployments.
Figure 42 Cluster concepts diagram
.
Sequence of events for cluster resources
The sequence of events in the diagram includes:
1. Physical disks are combined into RAID arrays and LUNs.
2. LUNS are designated as basic disks, formatted, and assigned a drive letter via Disk Manager.
Cluster administration92
3. Physical Disk resources are created for each basic disk inside Failover Cluster Management.
4. Directories and folders are created on assigned drives.
5. Cluster components (virtual servers, file shares) are created, organized in groups, and placed
within the folders using Failover Cluster Management exclusively.
Hierarchy of cluster resource components
Figure 42 depicts the cluster resource hierarchy as follows:
• Physical Disk resources are placed in a cluster group and relate to the basic disk. When a Physical
Disk resource is created through Failover Cluster Management, the resource should be inserted
into an existing cluster group or a corresponding group should be created for the resource to
reside in.
• File share resources are placed in a group and relate to the actual directory on the drive on which
the share is being created.
• An IP Address resource is formed in the group and relates to the IP address by which the group's
virtual server is identified on the network.
• A Network Name resource is formed in the group and relates to the name published on the network
by which the group is identified.
• The Group is owned by one of the nodes of the cluster, but may transition to the other nodes during
failover conditions.
The diagram illustrates a cluster containing two nodes. Each node has ownership of one group.
Contained within each group are file shares that are known on the network by the associated Network
Name and IP address. In the specific case of Node1, file share Eng1 relates to E:\Eng1. This file
share is known on the network as \\Fileserver1\Eng1 with an IP address of 172.18.1.99.
For cluster resources to function properly, two very important requirements should be adhered to:
• Dependencies between resources of a group must be established. Dependencies determine the
order of startup when a group comes online. In the above case, the following order should be
maintained:
1. File Share—Dependent on Physical Disk Resource and Network Name
2. Network Name—Dependent on IP Address
Failure to indicate the dependencies of a resource properly may result in the file share attempting
to come online prior to the physical disk resource being available, resulting in a failed file share.
• Groups should have a Network Name resource and an IP Address resource. These resources are
used by the network to give each group a virtual name. Without this virtual reference to the group,
the only way to address a share that is created as a clustered resource is by node name. Physical
node names do not transition during a failover, whereas virtual names do.
For example, if a client maps a network share to \\Node1\Eng1 instead of \\Fileserver1\Eng1,
when Node1 fails and Node2 assumes ownership, the map will become invalid because the reference
in the map is to \\Node1. If the map were created to the virtual name and Node1 were to fail, the
map would still exist when the group associated with Eng1 failed over to Node2.
The previous diagram is an example and is not intended to imply limitations of a single group or
node. Groups can contain multiple physical disks resources and file shares and nodes can have
multiple groups, as shown by the group owned by Node2.
Cluster planning
Requirements for taking advantage of clustering include:
X3000 G2 Network Storage System User Guide 93
• Storage planning
• Network planning
• Protocol planning
Storage planning
For clustering, a basic disk must be designated for the cluster and configured as the Quorum disk.
Additional basic disks are presented to each cluster node for data storage as physical disk resources.
The physical disk resources are required for the basic disks to successfully work in a cluster environment,
protecting it from simultaneous access from each node.
The basic disk must be added as a physical disk resource to an existing cluster group or a new cluster
group needs to be created for the resource. Cluster groups can contain more than one physical disk
resource depending on the site-specific requirements.
NOTE:
The LUN underlying the basic disk should be presented to only one node of the cluster using selective
storage presentation or SAN zoning, or having only one node online at all times until the physical
resource for the basic disk is established.
In preparing for the cluster installation:
• 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.
Network planning
Clusters require more sophisticated networking arrangements than a stand alone storage 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
• 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:
Cluster administration94
• 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.
HP recommends placing cluster aware and non cluster aware protocols on different file shares.
Table 12 Sharing protocol cluster support
Client VariantProtocol
Linux
iSCSI
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.
Standards-based iSCSI
initiator
Cluster Aware (supports failover)
Supported on cluster
nodes
YesYesWindowsCIFS/SMB
YesYesUNIXNFS
YesNoWebHTTP
YesYesManyFTP
YesNoNovellNCP
NoNoAppleAppleTalk
YesYes
Preparing for cluster installation
This section provides the steps necessary to cluster HP StorageWorks X3000 Network Storage Systems.
X3000 G2 Network Storage System User Guide 95
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 recom-
mended.) Additional LUNs may also be presented for use as shared disk resources.
• Cluster configurations should 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
HP 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 datapath 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.
• 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).
Cluster administration96
• 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 Table 13 to determine which nodes and storage devices should be presented during each step.
Table 13 Power sequencing for cluster installation
Setting up networks
Setting up
shared disks (including the Qurom disk)
Verifying disk
configuration
Configuring the
first node
Configuring additional nodes
Node 1Step
Additional
Nodes
Not PresentedOnOn
PresentedOffOn
PresentedOnOff
PresentedOffOn
PresentedOnOn
PresentedOnOnPost-installation
CommentsStorage
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.
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.
• On the General 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.
X3000 G2 Network Storage System User Guide 97
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
HP 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
HP makes the following Quorum disk recommendations:
• Dedicate a separate disk resource for a Quorum disk. Because the failure of the Quorum disk
would cause the entire cluster to fail, HP strongly recommends that the disk resource be a RAID 1
configuration.
• Create a partition with a minimum of 50 megabytes (MB) to be used as a Quorum disk. HP recom-
mends a Quorum disk be 500 MB.
HP recommends assigning the drive letter Q for the Quorum disk. It is also helpful to label the volume
Quorum.
NOTE:
It is possible to change the Quorum disk by clicking the Quorum button. This displays a list of available
disks that can be used for the Quorum disk. Select the appropriate disk, and then click OK to continue.
Cluster administration98
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.
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
50 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.
X3000 G2 Network Storage System User Guide 99
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.
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.
Cluster administration100
Loading...