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.
WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website:
h
ttp://www.hp.com/go/storagewarranty
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.
Printed in the US
Contents
About this guide ................................................................................. 11
Summary of RAID methods ....................................................................................... 222
Tasks and utilities needed for storage system configuration ........................................... 283
Sharing protocol cluster support ................................................................................ 654
Power sequencing for cluster installation ..................................................................... 675
X1800sb and X3800sb Network Storage Blade 9
10
About this guide
This guide provides information about the following HP StorageWorks Network Storage Systems:
• HP StorageWorks X1800sb Network Storage Blade
• HP StorageWorks X3800sb Network Storage Gateway Blade
The HP StorageWorks X1800sb Network Storage Blade and HP StorageWorks X3800sb Network
Storage Gateway Blade are based on HP ProLiant BL460c G6 Server Blade hardware. The HP
StorageWorks X1800sb Network Storage Blade also can be used with an optional HP StorageWorks
SB40c Storage Blade for internal shared storage and file serving or as a gateway to additional
external storage.
For more information about these HP BladeSystem products, go to http://www.hp.com/go/blades.
Intended audience
This guide is intended for technical professionals with knowledge of:
• Microsoft® administrative procedures
• System and storage configurations
Related documentation
The following documents [and websites] provide related information:
• HP StorageWorks X1800sb Network Storage Blade installation instructions
• HP StorageWorks X3800sb Network Storage Gateway Blade installation instructions
• HP StorageWorks X1000 Automated Storage Manager user guide
• HP Integrated Lights-Out 2 User Guide
To obtain HP StorageWorks X1000 and X3000 Network Storage System documentation, go to http:/
/www.hp.com/go/nas, select your product family, product model, click Support for your product,
and then click Manuals.
Document conventions and symbols
Table 1 Document conventions
ElementConvention
Cross-reference links and e-mail addressesBlue text: Table 1
ttp://www.hp.com
Website addressesBlue, underlined text: h
X1800sb and X3800sb Network Storage Blade 11
Bold text
Monospace text
ElementConvention
• Keys that are pressed
• Text typed into a GUI element, such as a box
• GUI elements that are clicked or selected, such as menu
and list items, buttons, tabs, and check boxes
Text emphasisItalic text
• File and directory names
• System output
• Code
• Commands, their arguments, and argument values
Monospace, italic text
Monospace, bold text
• Code variables
• Command variables
Emphasized monospace text
WARNING!
Indicates that failure to follow directions could result in bodily harm or death.
CAUTION:
Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT:
Provides clarifying information or specific instructions.
NOTE:
Provides additional information.
TIP:
Provides helpful hints and shortcuts.
Rack stability
Rack stability protects personnel and equipment.
About this guide12
WARNING!
To reduce the risk of personal injury or damage to equipment:
• Extend leveling jacks to the floor.
• Ensure that the full weight of the rack rests on the leveling jacks.
• Install stabilizing feet on the rack.
• In multiple-rack installations, fasten racks together securely.
• Extend only one rack component at a time. Racks can become unstable if more than one component
is extended.
HP technical support
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
Before contacting HP, collect the following information:
• Product model names and numbers
• Technical support registration number (if applicable)
• Product serial numbers
• Error messages
• Operating system type and revision level
• Detailed questions
Customer self repair
HP customer self repair (CSR) programs allow you to repair your StorageWorks product. If a CSR
part needs replacing, HP ships the part directly to you so that you can install it at your convenience.
Some parts do not qualify for CSR. Your HP-authorized service provider will determine whether a
repair can be accomplished by CSR.
For more information about CSR, contact your local service provider, or see the CSR website:
http://www.hp.com/go/selfrepair
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/go/e-updates
After registering, you will receive e-mail notification of product enhancements, new driver versions,
firmware updates, and other product resources.
HP websites
For additional information, see the following HP websites:
•http://www.hp.com
X1800sb and X3800sb Network Storage Blade 13
•http://www.hp.com/go/storage
•http://www.hp.com/service_locator
•http://www.hp.com/support/manuals
•http://www.hp.com/support/downloads
Documentation feedback
HP welcomes your feedback.
To make comments and suggestions about product documentation, please send a message to
storagedocsFeedback@hp.com. All submissions become the property of HP.
About this guide14
1 Administration tools
HP StorageWorks X1000 and X3000 Network Storage Systems include several administration tools
to simplify storage system management tasks. HP StorageWorks X1000 Network Storage Systems
include the HP X1000 Automated Storage Manager (ASM) in addition to HP storage utilities and
Microsoft® Windows® Storage Server 2008 administration tools.
HP StorageWorks X1000 Automated Storage Manager
After installing and setting up your storage system, you can begin managing your storage using the
HP Automated Storage Manager (HP ASM). HP ASM comes preinstalled on all HP X1000 Network
Storage Systems.
NOTE:
HP ASM is not supported on HP X3000 Network Storage Systems.
ASM provides storage-allocation wizards that walk you through the process of allocating and
configuring storage on your HP Network Storage System to host application data and shared folders.
The storage-allocation wizards also allow you to schedule backups, snapshots, and replication of
hosted application data and shared folders. Other wizards are provided to help you set up Exchange
Server storage, SQL Server database storage, storage for user-defined applications, and storage for
shared folders.
For more information about using the HP Automated Storage Manager, see the HP ASM online help
or the HP StorageWorks X1000 Automated Storage Manager user guide. Go to http://www.hp.com/
go/nas, select your product family, select your product model, click Support for your product, and
then click Manuals.
Microsoft Windows Storage Server 2008 administration tools
Microsoft® Windows® Storage Server 2008 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 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.
X1800sb and X3800sb Network Storage Blade 15
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 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.
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 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 Help.
Microsoft Services for Network File System
Microsoft Services for Network File System (NFS) is a component of Windows Storage Server 2008
that provides a file-sharing solution for enterprises that have a mixed Windows and UNIX environment.
By using Microsoft Services for NFS, you can configure storage services to make it possible for users
to store and access files on the storage system, and to transfer files between the storage system and
UNIX computers by using the NFS protocol.
In Windows Storage Server 2008, you can complete the initial configuration of Microsoft Services
for NFS by using the Microsoft Services for NFS Configuration Guide, which includes an Identity
Administration tools16
Mapping Setup Wizard. After completing the initial Microsoft Services for NFS configuration, you
can use the Microsoft Services for NFS console for ongoing maintenance and administration.
If you are using Windows Storage Server 2008 in an environment that does not include an Active
Directory directory service domain, you can install Active Directory Application Mode (ADAM) on
your storage system to provide user name mapping for NFS. Microsoft Services for NFS can use any
RFC 2307 compliant Lightweight Directory Access Protocol (LDAP) service to provide username
mapping services.
For more information, see the Windows Storage Server 2008 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:
• 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.
For more information, see the Windows Storage Server 2008 Help.
X1800sb and X3800sb Network Storage Blade 17
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, 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,
or Windows Storage Server 2008.
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 Help.
Administration tools18
2 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 1 depicts many of the storage elements that one would find on a storage device. The following
sections provide an overview of the storage elements.
X1800sb and X3800sb Network Storage Blade 19
Figure 1 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 overview20
Arrays
• Include the appropriate number of physical drives in the arrays to create logical storage elements
of desired sizes.
See Figure 2. 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 2 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 3.
Figure 3 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.
X1800sb and X3800sb Network Storage Blade 21
Fault tolerance
Drive failure, although rare, is potentially catastrophic. For example, using simple striping as shown
in Figure 3, 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 2 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 overview22
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 4 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 and can be composed of only one
basic disk no larger than 2 TB. Basic disks can also only contain up to four primary partitions, or
three primary partitions and one extended partition. In addition, the partitions on them cannot be
extended beyond the limits of a single LUN. 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.
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
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
X1800sb and X3800sb Network Storage Blade 23
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.
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.
Storage management overview24
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.
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).
X1800sb and X3800sb Network Storage Blade 25
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 overview26
3 File server management
This chapter begins by identifying file services in Windows Storage Server 2008. 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
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.
X1800sb and X3800sb Network Storage Blade 27
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 X1000 and X3000 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 3
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 3 Tasks and utilities needed for storage system configuration
Storage management utilityTask
Create disk arrays
Create logical disks from the array space
• 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 first two logical drives are configured for the storage system operating system and should not
be altered in any manner. If the first two logical drives are altered, the system recovery process
may not function properly when using the System Recovery DVD. Do not tamper with the “DON’T
ERASE” or local C: volume. These are reserved volumes and must be maintained as they exist.
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.
HP Array Configuration Utility or HP Automated Storage
Manager
HP Array Configuration Utility or HP Automated Storage
Manager
Windows Disk ManagementVerify newly created logical disks
Windows Disk ManagementCreate a volume on the new logical disk
• 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 management28
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.
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 default password is hpinvent.
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 first two logical drives of the storage system; they are 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.
• A single array can contain multiple logical drives of varying RAID settings.
X1800sb and X3800sb Network Storage Blade 29
• 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 first two logical drives are configured for the storage system operating system and should not
be altered in any manner. If the first two logical drives are altered, the system recovery process
may not function properly when using the System Recovery DVD. Do not tamper with the “DON’T
ERASE” or local C: volume. These are reserved volumes and must be maintained as they exist.
• 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 management30
Loading...
+ 72 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.