HP ProLiant SB460c SAN Gateway Storage Server user guide Part number: AN583-96001 First edition: September 2008
Legal and notice information © Copyright 1999, 2008 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.
Contents About this guide ................................................................................. 11 Intended audience .................................................................................................................... Related documentation .............................................................................................................. Document conventions and symbols .............................................................................................
Array Configuration Utility ............................................................................................ 26 Disk Management utility ............................................................................................... 27 Guidelines for managing disks and volumes .......................................................................... 27 Scheduling defragmentation ................................................................................................ 27 Disk quotas ......
3 Print services ................................................................................... 57 Microsoft Print Management Console .......................................................................................... New or improved HP print server features .................................................................................... HP Web Jetadmin ..............................................................................................................
Installing the AppleTalk protocol ........................................................................................... Installing File Services for Macintosh ..................................................................................... Completing setup of AppleTalk protocol and shares ................................................................ Print services for Macintosh ..................................................................................................
Verifying disk access and functionality .......................................................................... Configuring cluster service software ........................................................................................... Using Cluster Administrator ............................................................................................... Using Cluster Administrator remotely ............................................................................
Class A equipment ........................................................................................................... Class B equipment ............................................................................................................ Declaration of conformity for products marked with the FCC logo, United States only ................ Modifications .................................................................................................................. Cables ......................
Figures 1 Storage management process example ...................................................................... 16 2 Configuring arrays from physical drives ...................................................................... 17 3 RAID 0 (data striping) (S1-S4) of data blocks (B1-B12) ................................................ 17 4 Two arrays (A1, A2) and five logical drives (L1 through L5) spread over five physical drives .........................................................................
Tables 1 Document conventions ............................................................................................. 11 2 Summary of RAID methods ....................................................................................... 18 3 Tasks and utilities needed for storage server configuration ............................................ 25 4 Authentication table ................................................................................................
About this guide This guide provides information about configuring, managing, and troubleshooting the HP ProLiant SB460c SAN Gateway Storage Server.
Convention Element Monospace, italic Monospace, bold text 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.
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.
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.
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.
Physical Disks Single Server Cluster Implementation RAID Arrays Storage Elements Logical Drives Selective Storage Presentaion Visible Disks Logical Storage Elements Partitioning NTFS Volumes Q: File System Elements Shadow Copy Elements File Folders Shadow Copies (Snapshots) \Engineering \Marketing \Users \Sales \Users from 02/10/03 09:30 \snapshot.0 R: from 02/10/03 09:30 \snapshot.0 from 02/10/03 11:30 \snapshot.1 R: from 02/10/03 11:30 \snapshot.
• Include the appropriate number of physical drives in the arrays to create logical storage elements of desired sizes. Arrays 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.
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.
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. A1 A2 L3 L1 L4 L2 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.
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.
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.
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.
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.
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.
Configurable and pre-configured storage 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.
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.
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.
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.
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.
• 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.
Volume shadow copies NOTE: Select storage servers 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.
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.
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.
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.
Figure 5 System administrator view of Shadow Copies for Shared Folders The shadow copy cache file The default shadow copy settings allocate 10 percent of the source volume being copied (with a minimum of 350 MB), and store the shadow copies on the same volume as the original volume. (See Figure 6). 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.
F: G: H: L: cache file cache file cache file Figure 7 Shadow copies stored on a separate volume The main advantage to storing shadow copies on a separate volume is ease of management and performance. Shadow copies on a source volume must be continually monitored and can consume space designated for file sharing. Setting the limit too high takes up valuable storage space. Setting the limit too low can cause shadow copies to be purged too soon, or not created at all.
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 37. 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.
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.
Managing shadow copies from the storage server desktop To access shadow copies from the storage server desktop: The storage server desktop can be accessed by using Remote Desktop to manage shadow copies. 1. On the storage server desktop, double-click My Computer. 2. Right-click the volume name, and select Properties. 3. Click the Shadow Copies tab. See Figure 8.
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.
Figure 9 Client GUI When users view a network folder hosted on the storage server 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.
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.
Figure 10 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...
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.
Folder and share management The HP ProLiant Storage Server 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 management of the file shares for the supported protocols. Security at the file level and at the share level is also discussed. NOTE: Detailed information on setting up and managing NFS and NCP shares is discussed in Microsoft Services for Network File System (MSNFS).
2. Click Properties, and then click the Security tab. Figure 11 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.
3. To modify ownership of files, or to modify individual file access level permissions, click Advanced. Figure 12 illustrates the properties available on the Advanced Security Settings dialog box. Figure 12 Advanced Security settings dialog box, Permissions tab Other functionality available in the Advanced Security Settings dialog box is illustrated in Figure 12 and includes: • Add a new user or group—Click Add, and then follow the dialog box instructions. • Remove a user or group— Click Remove.
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 13 illustrates the Edit screen and some of the permissions. Figure 13 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.
Figure 14 Advanced Security Settings dialog box, Auditing tab 5. Click Add to display the Select User or Group dialog box. Figure 15 Select User or Group dialog box NOTE: Click Advanced to search for users or groups. 6. Select the user or group.
7. Click OK. The Auditing Entry dialog box is displayed. Figure 16 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 server. The Owner tab allows taking ownership of files.
Figure 17 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.
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.
• 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 server 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 the HP Storage Server Management Console.
• Define quota templates that can be easily applied to new volumes or folders and that can be used across an organization. File screening management On the File Screening Management node of the File Server Resource Manager snap-in, you can perform the following tasks: • Create file screens to control the types of files that users can save and to send notifications when users attempt to save blocked files.
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 management
3 Print services Microsoft Print Management Console Print Management in the Microsoft Windows Server 2003 R2 operating system is a Microsoft Management Console (MMC) snap-on that system administrators can use to perform common print management tasks in a large enterprise. It provides a single interface that administrators can use to perform printer and print server management tasks efficiently with detailed control.
Network printer drivers Updated print drivers for HP network printers are preinstalled on the storage server. If a Service Release DVD has been run on the server, there are updated HP network print drivers in the C:\hpnas\PRINTERS folder. Print services management Print services information to plan, set up, manage, administer, and troubleshoot print servers and print devices are available online using the Help and Support Center feature.
• Web-based printer management with the ability to administer, connect to, and view printers through a web browser. • Internet printing enabling users to connect to a printer using the printer's URL. A Microsoft white paper discussing the uses of both components can be obtained at http:// www.microsoft.com/windowsserver2003/techinfo/overview/internetprint.mspx. Planning considerations for print services Before configuring the print server, the following checklist of items should be followed: 1.
be created on the print server. The utility is located on the storage server in the C:\hpnas\Components\Install Network Printer Wizard folder. Sustaining print administration tasks Tasks that need to be performed regularly to support the print services include: • Monitoring print server performance using the built-in performance monitoring tool in the Windows Server operating system. • Supporting printers that include adding, moving, and removing printers as requirements change.
Internet is required, or the utility can be pointed to a local location where the firmware images are stored. For more information on upgrading HP Jetdirect print server firmware, see http:// h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpj06917. Printer server scalability and sizing A Microsoft technical paper overviews several key factors that influence the capacity of a given print server configuration.
• Stop and restart the spooler service, or restart the print server. Troubleshooting The online help or Help and Support Center feature should be used to troubleshoot general and common print-related problems. Printing help can be accessed by selecting Start > Help and Support, then the Printers and Faxes selection under Help Contents. The same print troubleshooting information can be accessed at http://www.microsoft.
4 Microsoft Services for Network File System (MSNFS) This chapter discusses networking features in Microsoft Services for Network File System (MSNFS). MSNFS Features MSNFS is an update to the NFS components that were previously available in Services for UNIX 3.5.
• Administration components • Password synchronization • Server for NIS The UNIX Identity Management component is not enabled by default on the storage server. To install this component: 1. Access Add/Remove Programs. 2. Select Add/Remove Windows Components > Active Directory Services > Details. 3. Install Identity Management for UNIX.
• Client for NFS Normally, a Windows-based computer cannot access files on a UNIX computer. A computer running Windows Server 2003 R2 and Client for NFS, however, can access files stored on a UNIX-based NFS server. The Client for NFS feature of the Microsoft Services for NFS component is not preinstalled on the storage server although information about this feature appears in the online help. To enable Client for NFS: 1. Go to Add/Remove Programs. 2.
UNIX computers follow advisory locking for all lock requests. This means that the operating system does not enforce lock semantics on a file, and applications that check for the existence of locks can use these locks effectively. However, Server for NFS implements mandatory locks even for those locking requests that are received through NFS. This ensures that locks acquired through NFS are visible through the server message block (SMB) protocol and to applications accessing the files locally.
To install the Authentication software on the domain controllers: 1. From the SFU 3.5 files, locate the directory named SFU35SEL_EN. 2. On the domain controller where the Authentication software is being installed use Windows Explorer to: a. Open the shared directory containing setup.exe. b. Double-click the file to open it. Windows Installer is opened. NOTE: If the domain controller used does not have Windows Installer installed, locate the file InstMSI.exe on the SFU 3.5 directory and run it.
2. In the console tree, right-click the domain for which you want to raise functionality, and then click Raise Domain Functional Level. 3. In Select an available domain functional level, click Windows Server 2003. 4. Click Raise.
Managing access using the .maphosts file The User Name Mapping component of MSNFS acts as an intermediary between NFS servers and NFS clients on a network containing UNIX hosts and Windows-based computers. To maintain the implicit trust relationship between NFS client and host computers, administrators can control which computers can access User Name Mapping by editing the .maphosts in the %windir%\msnfs directory of the storage server. Conditions to allow or deny access include: • If the .
7. Assign the Everyone group the appropriate permissions on the NFS Share. 8. Enable anonymous access to the share. To enable anonymous access to an NFS share, do the following: 1. Open Windows Explorer by clicking Start > Run, and entering Explorer. 2. Navigate to the NFS share. 3. Right-click the NFS Share, and then click Properties. 4. Click NFS Sharing. 5. Select the Allow Anonymous Access checkbox. 6. Change from the default of -2,-2, if desired. 7. Click Apply. 8. Click OK.
You can back up and restore User Name Mapping data at any time. Because the database is backed up to a file, you can use that file to copy the mapping database to another server. This provides redundancy for the sake of fault tolerance. NOTE: If you obtain information from multiple NIS domains, it is assumed that each domain has unique users and user identifiers (UIDs). User Name Mapping does not perform any checks.
Microsoft Services for NFS troubleshooting The following information on how to troubleshoot issues with Microsoft Services for NFS is available using the online help: • General issues • Troubleshooting Server for NFS • Troubleshooting User Name Mapping For further details, see the online help for Microsoft Services for Network File System. Microsoft Services for NFS command-line tools Table 5 provides a listing of Windows command-line administration tools.
comply with Request for Comments (RFC) 1179. The combination of the LPR and LPD are included in print services for UNIX. Print services for UNIX is not preinstalled on the print server. To install print services for UNIX: 1. Log on as administrator or as a member of the Administrators group. 2. Select Start > Control Panel, and then click Add or Remove Programs. 3. Click Add/Remove Windows Components. 4.
Microsoft Services for Network File System (MSNFS)
5 Other network file and print services This chapter discusses file and print services for NetWare and Macintosh. File and Print Services for NetWare (FPNW) File and Print Services for NetWare (FPNW) is one part of the Microsoft software package called Services for NetWare. The most common use of the NetWare network operating system is as a file and print server.
Managing File and Print Services for NetWare FPNW resources are managed through Server Manager. Server Manager can be used to modify FPNW properties and manager shared volumes. Use File and Print Services for NetWare to: • Access files, modify file settings and permissions from Computer Management, and use third party tools that can be used with NetWare servers. • Create and manage user accounts by using Active Directory Users and Computers. • Perform secured log-ons.
2. Select FPNW, and then click Properties. Figure 19 File and Print Services for NetWare dialog box 3. Enter an FPNW Server Name and Description. This server name must be different from the server name used by Windows or LAN Manager-based clients. If changing an existing name, the new name is not effective until stopping and restarting FPNW. For example, in Figure 19 the Windows server name is Alamo and the FPNW server name is Alamo_FPNW. 4. Indicate a Home directory root path.
Adding local NetWare users 1. From the storage server desktop, click the Management Console icon, click Core Operating System, and then click Local Users and Groups. 2. Right-click the Users folder, and then click New User. Figure 20 New User dialog box 3. Enter the user information, including the user's User name, Full name, Description, and Password. 4. Click Create. 5. Repeat these steps until all NetWare users have been entered. Enabling local NetWare user accounts 1.
2. Click the NetWare Services tab. Figure 21 NetWare Services tab 3. Select Maintain NetWare compatible login. 4. Set other NetWare options for the user, and then click OK. NOTE: The installation of File and Print Services for NetWare also creates a supervisor account, which is used to manage FPNW. The supervisor account is required if the storage server was added as a bindery object into NDS.
Creating a new NCP share To create a new file share: 1. From the storage server desktop, select Start > Settings > Control Panel > Administrative Tools > Server Manager. 2. Select File and Print Service for NetWare> Shared Volumes. 3. Click Create Volume. 4. Specify the volume name and path. 5. Click Permissions to set permissions. 6. Click Add to add additional users and groups, and to set their permissions. 7. Highlight the desired user or group, and then click Add. 8.
Millennium clients, these non–Windows clients do not receive driver updates from the print server after a driver is initially downloaded. The same connection methods are available: drag and drop, the Add Printer Wizard, referencing a UNC path, or double-clicking the shared printer icon. Additional resources For more information about using and configuring File and Print Services for NetWare, see the online help.
CAUTION: AppleTalk shares should not be created on clustered resources because data loss can occur due to local memory use. • To set up AppleTalk shares • To configure AppleTalk sharing properties • To allow client permission to an AppleTalk share If AppleTalk is enabled for your server configuration, specify which AppleTalk clients are granted access to each share. Access can be granted or denied on the basis of client host name.
6 Enterprise storage servers Some HP ProLiant Storage Servers use the Microsoft® Windows® Unified Data Storage Server 2003 operating system. This operating system provides unified storage server management capabilities, simplified setup and management of storage and shared folders, and support for Microsoft iSCSI Software Target.
2. Type the network name or the network IP address of the storage server followed by /admin (for example, http://myStorageServer/admin). 3. In Remote Administration Desktop, provide the appropriate credentials. NOTE: Administrative credentials are not required to establish a browser-based connection, but are required to manage the storage server.
Wizards To support creation and management of iSCSI targets, virtual disks, and snapshots, the iSCSI Software Target snap-in provides several wizards. Create iSCSI Target Wizard This section describes how to create an iSCSI Target using the Create iSCSI Target Wizard. 1. 2. 3. 4. 5. 6. Log on to the storage server using an account with administrative privileges. Open the Microsoft iSCSI Software Target MMC snap-in by clicking Start > Programs > Administrative Tools > Microsoft iSCSI Software Target.
Figure 23 Advanced Identifiers page Figure 24 Add/Edit Identifier page 8. 9. Click Next. Click Finish to complete the wizard and create the iSCSI Target. Create Virtual Disk Wizard This section describes how to create an iSCSI Virtual Disk using the Create Virtual Disk Wizard. NOTE: In order to create iSCSI Virtual Disks, it is required that physical disks are formatted as NTFS. 1. 2. 3. 4. 5. 86 In the Microsoft iSCSI Software Target MMC snap-in, click the Devices node.
6. 7. 8. 9. Enter a description for the iSCSI virtual disk (optional) and click Next. On the Access page, click Add to assign the iSCSI virtual disk to an iSCSI Target. On the Add Targets dialog box, select a Target and click OK. Click Finish to complete the wizard and create the iSCSI virtual disk. NOTE: If you delete a virtual disk, it is removed from the iSCSI Software Target MMC snap-in, but the virtual disk file (.vhd) is not removed from the physical disk.
9. Click Finish to complete the wizard and schedule snapshots. Hardware provider To support advanced management of iSCSI virtual disks and snapshots, you can use the Microsoft iSCSI Software Target Virtual Disk Service Hardware Provider, which comes preinstalled on the HP ProLiant Storage Server. Microsoft Windows Server 2003 introduced Virtual Disk Service (VDS), a set of application programming interfaces (APIs) that provides a single interface for managing disks.
7 Cluster administration NOTE: Not all HP ProLiant Storage Servers can be clustered. See the HP ProLiant Storage Server QuickSpecs to determine if your storage server can be clustered. Windows Storage Server 2003 Release 2 clusters can include up to eight nodes. One important feature of the HP ProLiant Storage Server clusterable models is that they can operate as a single node or as a cluster. This chapter discusses cluster installation and cluster management issues.
Cluster Node A Cluster Node B Private Network Node A HBA 2 Node A HBA 1 + + + + + + + + +++++++++++++++++++++++++++++++++++++++++++++++++++ + + + Node B + Node B HBA 1 HBA 2 SAN Switch SAN Switch Storage Area Network Cluster Quorum Mirrorset LUN 1 Data RAID set Node A LUN 2 Data RAID set Node B LUN 3 Figure 25 Storage server cluster diagram Cluster terms and components Nodes The most basic parts of a cluster are the servers, referred to as nodes.
• • • • 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.
• 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 26 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.
3. Physical Disk resources are created for each basic disk inside Cluster Administrator. 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 Cluster Administrator exclusively. Hierarchy of cluster resource components Figure 26 depicts the cluster resource hierarchy as follows: • Physical Disk resources are placed in a cluster group and relate to the basic disk.
• 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.
Virtual names and addresses are the only identification used by clients on the network. Because the names and addresses are virtual, their ownership can transition from one node to the other during a failover, preserving access to the resources in the cluster group. A cluster uses at least two network connections on each node: • The private cluster interconnect or “heartbeat” crossover cable connects to one of the network ports on each cluster node.
NOTE: AppleTalk is not supported on clustered disk resources. AppleTalk requires local memory for volume indexing. On failover events, the memory map is lost and data corruption can occur. Preparing for cluster installation This section provides the steps necessary to cluster HP ProLiant Storage Servers.
2. On the left side of the window, select Add/Remove Windows Components. The Windows Components Wizard appears. 3. Select Other Network File and Print Services and click the Details button. The Other Network File and Print Services window is displayed. 4. Uncheck the Microsoft Services for NFS subcomponent. 5. Click OK, then Next, followed by Finish.
• 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.
Step Node 1 Additional Nodes Storage Comments Configuring additional nodes On On Presented Power on the next node after the first node is successfully configured. Complete this process for all cluster nodes. Post-installation On On Presented At this point all cluster nodes should be on. To configure the Cluster service on the storage server, an account must have administrative permissions on each node.
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.
Using Cluster Administrator Cluster Administrator shows information about the groups and resources on all of your clusters and specific information about the clusters themselves. A copy of Cluster Administrator is automatically installed on a cluster node when the Cluster service is installed. Using Cluster Administrator remotely For remote administration, copies of Cluster Administrator can be installed on other computers on your network.
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.
Load balancing The creation of separate cluster groups for each virtual server provides more flexibility in balancing the processing load on the cluster between the two nodes. Each cluster group can be assigned to a cluster node with the preferred owner parameter. For example, if there are two cluster groups, the cluster could be set up to have the first cluster group owned by Node A and the second cluster group owned by Node B. This allows the network load to be handled by both devices simultaneously.
NFS cluster-specific issues For convenience, all suggestions are listed below: • Back up user and group mappings. To avoid loss of complex advanced mappings in the case of a system failure, back up the mappings whenever the mappings have been edited or new mappings have been added. • Map consistently. Groups that are mapped to each other should contain the same users and the members of the groups should be properly mapped to each other to ensure proper file access. • Map properly.
The tasks described below are used to add storage to a cluster. See the online help for clustering for additional details. Creating physical disk resources A physical disk resource must reside within a cluster group. An existing cluster group can be used or a new cluster group must be created. For information on creating disk resources, see the cluster online help topic Physical Disk resource type. NOTE: • Physical disk resources usually do not have any dependencies set.
Extend a LUN in a cluster To extend a LUN on a storage array in a cluster, review the requirements and procedures from the storage array hardware provider for expanding or extending storage. For additional information associated with extending a LUN in a cluster, see the following Microsoft Knowledge Base articles: • How to extend the partition of a cluster shared disk http://support.microsoft.com/default.
Print services in a cluster The Windows Server 2003 Cluster service implementation increases availability of critical print servers. A print spooler service on a clustered print server may be hosted on any of the nodes in the cluster. As with all cluster resources, clients should access the print server by its virtual network name or virtual IP address. Creating a cluster printer spooler Printer spoolers should be created in a separate group dedicated to this purpose for ease of management.
Advanced cluster administration procedures Failing over and failing back As previously mentioned, when a node goes offline, all resources dependent on that node are automatically failed over to another node. Processing continues, but in a reduced manner, because all operations must be processed on the remaining node(s). In clusters containing more than two nodes, additional fail over rules can be applied.
Shutting down a cluster node causes all cluster resources served by that node to fail over to the other node(s). This causes any currently executing client read and write operations to fail until the cluster failover process completes. The other node(s) are placed under a heavier load by the extra work until the second node is powered up and rejoins the cluster.
Additional information and references for cluster services The following web sites provide detailed information for clustered environments for Windows Server 2003, which also applies to Windows Storager Server 2003: • Cluster services http://www.microsoft.com/windowsserver2003/technologies/clustering/default.mspx • How to: Set up a clustered print server http://support.microsoft.com/default.aspx?scid=kb;en-us;278455 • How to: Set up a print spooler on Microsoft Cluster Server http://support.microsoft.
8 Troubleshooting, servicing, and maintenance Troubleshooting the storage server The “Support and troubleshooting” task at the HP Support & Drivers web site (http://www.hp.com/ go/support) can be used to troubleshoot problems with the storage server.
Known issues and workarounds for the storage server products and the service release are addressed in release notes. To view the latest release notes, go to http://www.hp.com/support/manuals. Under the storage section, click NAS and then select your product. WEBES (Web Based Enterprise Services) WEBES is a tool suite aimed at preventing or reducing your system's down time.
Lights-Out Edition (RILOE), Remote Insight Lights-Out Edition II (RILOE II) and Integrated Lights-Out options that have firmware that can be updated. It is important to update the firmware (also called “flashing the ROM”) as part of regular server maintenance. In addition, checking for specific firmware updates in between regular updates helps to keep the server performing optimally. HP recommends checking for a firmware update before sending a part back to HP for replacement.
Troubleshooting, servicing, and maintenance
9 System recovery This chapter describes how to use the System Recovery DVD that is provided with your storage server. The System Recovery DVD The HP ProLiant Storage Server System Recovery DVD that is provided with your storage server allows you to install an image or recover from a catastrophic failure. At any later time, you may boot from the DVD and restore the server to the factory condition. This allows you to recover the system if all other means to boot the server fail.
System recovery
A Regulatory compliance and safety Federal Communications Commission notice Part 15 of the Federal Communications Commission (FCC) Rules and Regulations has established Radio Frequency (RF) emission limits to provide an interference-free radio frequency spectrum. Many electronic devices, including computers, generate RF energy incidental to their intended function and are, therefore, covered by these rules.
Declaration of conformity for products marked with the FCC logo, United States only This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. For questions regarding your product, contact: Hewlett-Packard Company P. O.
WARNING! Use of controls or adjustments or performance of procedures other than those specified herein or in the installation guide of the laser product may result in hazardous radiation exposure. To reduce the risk of exposure to hazardous radiation: • Do not try to open the module enclosure. There are no user-serviceable components inside. • Do not operate controls, make adjustments, or perform procedures to the laser device other than those specified herein.
BSMI notice Japanese notice Korean notice A&B Class A equipment Class B equipment 120 Regulatory compliance and safety
Safety Battery replacement notice WARNING! The computer contains an internal lithium manganese dioxide, a vanadium pentoxide, or an alkaline battery pack. A risk of fire and burns exists if the battery pack is not properly handled. To reduce the risk of personal injury: • Do not attempt to recharge the battery. • Do not expose the battery to temperatures higher than 60˚C (140˚F). • Do not disassemble, crush, puncture, short external contacts, or dispose of in fire or water.
Japanese power cord notice Electrostatic discharge To prevent damage to the system, be aware of the precautions you need to follow when setting up the system or handling parts. A discharge of static electricity from a finger or other conductor may damage system boards or other static-sensitive devices. This type of damage may reduce the life expectancy of the device.
Tento symbol na produktu nebo balení ozna uje výrobek, který nesmí být vyhozen spolu s ostatním domácím odpadem. Povinností uživatele je p edat takto ozna ený odpad na p edem ur ené sb rné místo pro recyklaci elektrických a elektronických za ízení. Okamžité t íd ní a recyklace odpadu pom že uchovat p írodní prost edí a zajistí takový zp sob recyklace, který ochrání zdraví a životní prost edí lov ka.
Estonian notice Seadmete jäätmete kõrvaldamine eramajapidamistes Euroopa Liidus See tootel või selle pakendil olev sümbol näitab, et kõnealust toodet ei tohi koos teiste majapidamisjäätmetega kõrvaldada. Teie kohus on oma seadmete jäätmed kõrvaldada, viies need elektri- ja elektroonikaseadmete jäätmete ringlussevõtmiseks selleks ettenähtud kogumispunkti.
garantiert eine Wiederverwertung, die die Gesundheit des Menschen und die Umwelt schützt. Informationen dazu, wo Sie Rücknahmestellen für Ihre Altgeräte finden, erhalten Sie bei Ihrer Stadtverwaltung, den örtlichen Müllentsorgungsbetrieben oder im Geschäft, in dem Sie das Gerät erworben haben.
Š ds simbols uz izstr d juma vai uz t iesai ojuma nor da, ka šo izstr d jumu nedr kst izmest kop ar citiem sadz ves atkritumiem. J s atbildat par to, lai nolietot s iek rtas tiktu nodotas speci li iek rtotos punktos, kas paredz ti izmantoto elektrisko un elektronisko iek rtu sav kšanai otrreiz jai p rstr dei.
Slovakian notice Likvidácia vyradených zariadení v domácnostiach v Európskej únii Symbol na výrobku alebo jeho balení ozna uje, že daný výrobok sa nesmie likvidova s domovým odpadom. Povinnos ou spotrebite a je odovzda vyradené zariadenie v zbernom mieste, ktoré je ur ené na recykláciu vyradených elektrických a elektronických zariadení.
och gör att avfallet återvinns på ett sätt som skyddar människors hälsa och miljön. Kontakta ditt lokala kommunkontor, din närmsta återvinningsstation för hushållsavfall eller affären där du köpte produkten för att få mer information om var du kan lämna ditt avfall för återvinning.
Index A access rights, managing, 103 ACL, defining, 52 Active Directory Lookup, 63 AppleTalk, 21 Array Configuration Utility, 26 array controller, purpose, 17 arrays, defined, 17 audience, 11 B backup, printer, 61 backup, with shadow copies, 44 basic disks, 19, 19, 20 battery replacement notice, 121 C cables, 118 cache file, shadow copies, 35 CIFS, share support, 53 Class A equipment, 117 Class B equipment, 117 cluster adding new storage, 104 analysis, 101 concepts, 92 concepts, diagram, 92 diagram, 90 d
document conventions, 11 related documentation, 11 documentation HP website, 11 providing feedback, 14 domain membership, verifying, 100 dual data paths, 96 dynamic disks clustering, 20 spanning multiple LUNs, 19 E electrostatic discharge, 122 European Union notice, 119 expanding storage Array Configuration Utility, 30 Command View EVA, 30 extending volumes Disk Management, 30 F failover automatic, 108 defined, 91 resources, 91 fault tolerance, 18 FCC notice, 117 file share permissions, managing, 103 file
NetWare adding local users, 78 enabling user accounts, 78 installing services for, 75 supervisor account, 79 network name resource, 93 network planning, 94 network requirements, cluster, 97 NFS share resource, 105 node, server, 90 RAID data striping, 17 LUNs in volumes, 19 summary of methods, 18 regulatory compliance, 117 related documentation, 11 resources, cluster, 90 S O online spares, 18 P partitions extended, 19 primary, 19 permissions file level, 45 list adding users and groups, 46 removing users
storage management elements, 15 overview, 15 process, 16 Storage Manager for SANs, 23 storage reports, 54 storage, adding to a cluster, 104 Subscriber's Choice, HP, 13 symbols in text, 12 system updates, 112 T technical support HP, 13 service locator website, 13 text symbols, 12 troubleshooting, 111 U UNIX, print services, 73 user account, setting up, 100 user-mode drivers, 60 users adding to permission list, 46 NetWare adding, 78 enabling, 78 V verifying connectivity, 99 disk access, 100 domain membersh
