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.
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.
Contents
About this guide ................................................................................. 11
Sharing protocol cluster support ................................................................................ 956
Power sequencing for cluster installation ..................................................................... 987
10
About this guide
This guide provides information about configuring, managing, and troubleshooting the HP ProLiant
SB460c SAN Gateway Storage Server.
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 Integrated Lights-Out 2 User Guide
• HP ProLiant Lights-Out 100 Remote Management User Guide
You can find these documents from the Manuals page of the HP Business Support Center website:
http://www.hp.com/support/manuals
In the Storage section, click Disk Storage Systems and then select your product.
Document conventions and symbols
Table 1 Document conventions
ElementConvention
Cross-reference links and e-mail addressesBlue text: Table 1
ttp://www.hp.com
Bold text
Monospace text
Website addressesBlue, underlined text: h
• 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
HP ProLiant SB460c SAN Gateway Storage Server 11
ElementConvention
Monospace, italic text
Monospace, bold 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.
• Code variables
• Command variables
Emphasized monospace text
TIP:
Provides helpful hints and shortcuts.
Rack stability
Rack stability protects personnel and equipment.
WARNING!
To reduce the risk of personal injury or damage to equipment:
• Extend leveling jacks to the floor.
• Ensure that the full weight of the rack rests on the leveling jacks.
• Install stabilizing feet on the rack.
• In multiple-rack installations, fasten racks together securely.
• Extend only one rack component at a time. Racks can become unstable if more than one component
is extended.
About this guide12
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. For North America, see the CSR
website:
http://www.hp.com/go/selfrepair
Product warranties
For information about HP StorageWorks product warranties, see the warranty information website:
http://www.hp.com/go/storagewarranty
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
•http://www.hp.com/go/storage
•http://www.hp.com/service_locator
•http://www.hp.com/support/manuals
•http://www.hp.com/support/downloads
HP ProLiant SB460c SAN Gateway Storage Server 13
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 Storage management overview
This chapter provides an overview of some of the components that make up the storage structure of
the HP ProLiant Storage Server.
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.
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 overview16
Arrays
S
S
S
S
g
• 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 server model, array configuration may not be possible or necessary.
L1
P1P3P2
gl0042
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.
1
B1
2
B4
3
B7
4
B2
B5
B8
B11B10B12
B3
B6
B9
l0043
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.
HP ProLiant SB460c SAN Gateway Storage Server 17
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 servers 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
Striping (no
fault tolerance)
No
RAID 1+0
Mirroring
If the failed
drives are not
mirrored to
each other
RAID 5
Distributed
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 server 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 overview18
It is important to note that a LUN may span all physical drives within a storage controller subsystem,
L
L
A2
but cannot span multiple storage controller subsystems.
A1
L3
1
2
L4
L5
gl0045
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 servers 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
HP ProLiant SB460c SAN Gateway Storage Server 19
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 server 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 server 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 overview20
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 server. However,
VSS can only use volumes that are NTFS formatted. Also, quota management is possible only on
NTFS.
Clustered server elements
Select storage servers support clustering. The HP ProLiant Storage Server supports 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.
CAUTION:
AppleTalk shares should not be created on clustered resources as this is not supported by Microsoft
Clustering, and data loss may occur.
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.
HP ProLiant SB460c SAN Gateway Storage Server 21
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 overview22
2 File server management
This chapter begins by identifying file services in Windows Storage Server 2003 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 2003 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. A Microsoft document titled
Storage Management in Windows Storage Server 2003 R2: File Server Resource Manager and
Storage Manager for Storage Area Networks is available at h
Storage Manager for SANs is only available on Standard and Enterprise editions of Windows Storage
Server 2003 R2.
ttp://download.microsoft.com/
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.
NOTE:
Single Instance Storage is only available on Standard and Enterprise editions of Windows Storage Server
2003 R2.
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,
HP ProLiant SB460c SAN Gateway Storage Server 23
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.
NOTE:
Windows SharePoint Services is only available on Standard and Enterprise editions of Windows Storage
Server 2003 R2.
HP Storage Server Management Console
The HP Storage Server Management Console is a user interface in Windows Storage Server 2003
R2 and Windows Unified Data Storage Server 2003 that provides one place to manage files or print
serving components. The console is accessible using Remote Desktop or a web browser.
The Storage Management page provides a portal to:
• File Server Resource Manager
• DFS Management
• Disk and Volume Management
• Single Instance Storage
• Indexing Service
• MSNFS (under Share folder)
• Cluster Management (under “Utilities”)
The Share Folder Management page provides a portal to Shared Folders, consisting of:
• Shares
• Sessions
• Open files
File services management
Information about the storage server in a SAN environment is provided in the HP ProLiant StorageServer SAN Connection and Management document located on the HP web site at http://
Certain storage servers ship with storage configured only for the operating system. The administrator
must configure data storage for the storage server. Other storage servers ship with pre-configured
storage for data. Depending on the type of storage server purchased, additional storage configuration
is required.
Configuring additional 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 server.
Table 3 Tasks and utilities needed for storage server configuration
• Create disk arrays—On storage servers 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 server.
Storage management utilityTask
HP Array Configuration Utility or Storage ManagerCreate disk arrays
HP Array Configuration Utility or Storage ManagerCreate logical disks from the array space
Windows Disk ManagementVerify newly created logical disks
Windows Disk ManagementCreate a volume on the new logical disk
CAUTION:
The first two logical drives are configured for the storage server 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.
• 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 server include the HP Array Configuration
Utility (ACU).
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.
HP ProLiant SB460c SAN Gateway Storage Server 25
NOTE:
The ACU is used to configure and manage array-based storage. Software RAID-based storage servers 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 server.
To open the ACU from the storage server 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 server 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 server; they are configured for the storage
server 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.
• 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.
File server management26
Disk Management utility
The Disk Management tool is a system utility for managing hard disks and the volumes, or partitions,
that they contain. Disk Management is used to initialize disks, create volumes, format volumes with
the FAT, FAT32, or NTFS file systems, and create fault-tolerant disk systems. Most disk-related tasks
can be performed in Disk Management without restarting the system or interrupting users. Most
configuration changes take effect immediately. A complete online help facility is provided with the
Disk Management utility for assistance in using the product.
NOTE:
• When the Disk Management utility is accessed through a Remote Desktop connection, this connection
can only be used to manage disks and volumes on the server. Using the Remote Desktop connection
for other operations during an open session closes the session.
• When closing Disk Management through a Remote Desktop connection, it may take a few moments
for the remote session to log off.
Guidelines for managing disks and volumes
• The first two logical drives are configured for the storage server 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.
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.
HP ProLiant SB460c SAN Gateway Storage Server 27
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 53 .
Configure the volumes on the server to perform the following tasks:
• Prevent further disk space use and log an event when a user exceeds a specified disk space limit.
• Log an event when a user exceeds a specified disk space warning level.
When enabling disk quotas, it is possible to set both the disk quota limit and the disk quota warning
level. The disk quota limit specifies the amount of disk space a user is allowed to use. The warning
level specifies the point at which a user is nearing his or her quota limit. For example, a user's disk
quota limit can be set to 50 megabytes (MB), and the disk quota warning level to 45 MB. In this case,
the user can store no more than 50 MB on the volume. If the user stores more than 45 MB on the
volume, the disk quota system logs a system event.
In addition, it is possible to specify that users can exceed their quota limit. Enabling quotas and not
limiting disk space use is useful to still allow users access to a volume, but track disk space use on a
per-user basis. It is also possible to specify whether or not to log an event when users exceed either
their quota warning level or their quota limit.
When enabling disk quotas for a volume, volume usage is automatically tracked from that point
forward, but existing volume users have no disk quotas applied to them. Apply disk quotas to existing
volume users by adding new quota entries on the Quota Entries page.
File server management28
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.
NOTE:
This section addresses only single storage server node configurations. If your server has Windows Storage
Server 2003 R2 Enterprise Edition, see the Cluster Administration chapter for expanding and extending
storage in a cluster environment.
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:
HP ProLiant SB460c SAN Gateway Storage Server 29
• Increase raw data storage
• Improve performance by increasing the number of spindles in a logical drive volume
• Change fault-tolerance (RAID) configurations
For more information about RAID levels, see the Smart Array Controller User Guide, or the document
titled Assessing RAID ADG vs. RAID 5 vs. RAID 1+0. Both are available at the Smart Array controller
web page or at 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
File server management30
Loading...
+ 102 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.