Administration Guide hp StorageWorks NAS 4000s and 9000s First Edition (November 2003) Part Number: 352405-001 This guide provides information on performing the administrative tasks necessary to manage the HP StorageWorks NAS 4000s or 9000s server. Overview information as well as procedural instructions are included in this guide.
© Copyright 2003 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Contents About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NAS Server Web-Based User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Menu Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network.
Contents Fault Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the NIC Team Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming the Teamed Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Showing a Connection Icon on the Taskbar . . . . . . . . . . .
Contents Volume Shadow Copy Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File System Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File-Sharing Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clustered Server Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Shadow Copy Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Identifying the Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Allocating Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Identifying the Storage Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Deleting a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Group Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Members Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directory Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Establishing Directory Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File Screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Squashed Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Name Mapping Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating and Managing User and Group Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simple Mapping Tab . . . . . . . . . . . . . . . . .
Contents Protocol Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for Cluster Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before Beginning Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP StorageWorks NAS Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Creating NFS Share Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Permissions for an NFS Share. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating IP Address Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Network Name Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Cluster Administration Procedures. . . . . . .
About This Guide About this Guide This administration guide provides information to help administrators: ■ Plan the storage configuration About this Guide ■ Set up physical storage ■ Manage users and groups ■ Manage folders and shares ■ Manage a UNIX® file system ■ Manage a NetWare file system ■ Remotely access the NAS server “About this Guide” topics include: ■ Overview, page 14 ■ Conventions, page 15 ■ Rack Stability, page 17 ■ Getting Help, page 17 NAS 4000s and 9000s Administrati
About this Guide Overview This section covers the following topics: ■ Intended Audience ■ Prerequisites Intended Audience This book is intended for use by system administrators who are experienced with setting up and managing a network server. Prerequisites Before beginning, make sure you consider the items below.
About this Guide Conventions Conventions consist of the following: ■ Document Conventions ■ Text Symbols ■ Equipment Symbols Document Conventions The document conventions included in Table 1 apply in most cases.
About this Guide Equipment Symbols The following equipment symbols may be found on hardware for which this guide pertains. They have the following meanings: Any enclosed surface or area of the equipment marked with these symbols indicates the presence of electrical shock hazards. Enclosed area contains no operator serviceable parts. WARNING: To reduce the risk of personal injury from electrical shock hazards, do not open this enclosure.
About this Guide Rack Stability Rack stability protects personnel and equipment. WARNING: To reduce the risk of personal injury or damage to the equipment, be sure that: ■ The leveling jacks are extended to the floor. ■ The full weight of the rack rests on the leveling jacks. ■ In single rack installations, the stabilizing feet are attached to the rack. ■ In multiple rack installations, the racks are coupled. ■ Only one rack component is extended at any time.
About this Guide 18 NAS 4000s and 9000s Administration Guide
System Overview 1 The HP StorageWorks NAS server can be used in many types of computing environments, from basic Microsoft Windows workgroups to complicated multiprotocol domains using DFS, NFS, FTP, HTTP, and Microsoft SMB. The corresponding varieties of clients that can be serviced include any Windows, UNIX, Linux, Novell, or Macintosh variant. This chapter provides an overview of these environments and deployments and includes brief descriptions of system user interfaces, applications, and options.
System Overview ■ Insight Manager is a comprehensive tool designed to be a key component in the systems management environment. It monitors the operations of HP servers, workstations, and clients. Insight Manager provides system administrators more control through comprehensive fault and configuration management, and industry leading remote management.
System Overview Deployment Scenarios Various deployment scenarios are possible. Typical application of NAS devices include: ■ File server consolidation As businesses continue to expand their information technology (IT) infrastructures, they must find ways to manage larger environments without a corresponding increase in IT staff. Consolidating many servers into a single NAS device decreases the number of points of administration and increases the availability and flexibility of storage space.
System Overview NAS Server as a Single Device In the single NAS device configuration, a NAS server is attached to a SAN via a single or pair of fiber channel host bus adapters (HBAs) and one or more SAN switches. In Figure 1, the dual HBA approach is illustrated. Each HBA should be connected to a separate switch that has access to the same controller pairs. This connection method allows redundant paths to the same storage subsystem.
System Overview NAS Server as a Clustered Pair In the clustered configuration, two NAS devices are linked via a private network and have access to shared storage as illustrated in Figure 2. In clustered deployments, it is recommended that each NAS device be attached to the SAN via a pair of fiber channel HBAs. Dual HBAs per NAS device is recommended but not required for cluster deployments, since dual HBAs allow for path failure without causing node failover in the cluster.
System Overview NAS Server Single Device Deployment In a single device deployment, network connections are divided into two categories: client data segments and management segments. The default shipping configuration contains a two-port network interface controller (NIC) 10/100/100 that provides one port for management and one port for client data. The management port is intended for use with the 3202 port of the device to enable use of the WebUI that accompanies the product.
System Overview NAS Server Cluster Deployment In a clustered deployment, network connections are divided into three categories: cluster maintenance segments, client data segments, and management segments. The default shipping configuration contains a two-port 10/100/1000 NIC that together provide one port for the cluster maintenance and one port for management and client data. An additional management port for remote console and diagnostics is provided off of the iLO port.
System Overview Environment Scenarios The NAS server is deployed in one of two security modes: ■ Workgroup ■ Domain (Windows NT Domain or Active Directory Domain) The NAS server uses standard Windows user and group administration methods in each of these environments. For procedural instructions on managing users and groups, see Chapter 6 of this guide. Regardless of the deployment, the NAS server integrates easily into multiprotocol environments, supporting a wide variety of clients.
System Overview User Interfaces There are several user interfaces that administrators can use to access and manage the NAS server. Two of these interfaces are: ■ NAS server WebUI ■ NAS server Desktop Each interface contains the same or similar capabilities, but presents them in a different manner. Each of these interfaces are illustrated in the following sections.
System Overview Network The Network option contains system settings, including system identification, global settings, interfaces settings, administration settings, Telnet settings, and SNMP settings. Disks Use this option to manage disks, volumes, disk quotas, and shadow copies. Users Use this option to manage local users and groups. Shares The administrator creates folders and shares to control access to files.
System Overview Set Server Name Choose a name so that client computers can connect to the server. Set Default Page Choose which page the server appliance displays first. NAS Server Desktop The NAS server desktop can be accessed by: ■ Directly connecting a keyboard, mouse, and monitor ■ Using the WebUI Maintenance tab and selecting Remote Desktop ■ Using the Integrated Lights-Out port Note: When using Remote Desktop to connect to the NAS desktop do not use the window close feature ( ).
System Overview NAS Management Console Click this icon to access the following folders: ■ Core Operating System is used to manage local users and groups, access performance logs and alerts, and manage the event viewer. ■ Disk System contains access to the HP Array Configuration Utility and local disk management, including a volume list and a graphical view of the disks. ■ File Sharing contains modules for the configuration of file sharing exports.
Basic Administrative Procedures and Setup Completion 2 Basic system administration functions are discussed in this chapter. This chapter also continues the process of setting up the system that was started using the HP StorageWorks NAS 4000s/9000s Installation Guide by discussing additional setup procedures and options. Further steps can also be viewed online by clicking the Installation Overview tab from the primary WebUI screen.
Basic Administrative Procedures and Setup Completion Figure 7: Maintenance menu Setting the System Date and Time To change the system date or time: 1. From the WebUI, select Maintenance and Date/Time. The Date and Time Settings dialog box is displayed. 2. Enter the new values and then click OK. The Maintenance menu is displayed.
Basic Administrative Procedures and Setup Completion Shutting Down or Restarting the Server Caution: Notify users before powering down the system. Both UNIX and Windows NT users can be drastically affected if they are not prepared for a system power-down. 1. From the NAS server WebUI, select Maintenance, Shutdown. Several options are displayed: Restart, Shut Down, and Scheduled Shutdown. Figure 9: Shutdown menu a. To shut down and automatically restart the server, click Restart. b.
Basic Administrative Procedures and Setup Completion Viewing and Maintaining Audit Logs A variety of audit logs are provided on the NAS server. System events are grouped into similar categories, representing the seven different logs. To access the logs from the WebUI, select Maintenance, Logs. The Logs menu is displayed. Figure 10: Logs menu A variety of logs are available and are listed in Figure 10. Each log has viewing, clearing, printing, and saving options.
Basic Administrative Procedures and Setup Completion Using Remote Desktop Remote Desktop is provided in the WebUI to allow for additional remote system administration and the use of approved third-party applications. Backup software and antivirus programs are examples of approved applications. In addition, Remote Desktop is used to access the NAS Management Console of the NAS device. To open a Remote Desktop session from the WebUI, select Maintenance, Remote Desktop. A Remote Desktop session is opened.
Basic Administrative Procedures and Setup Completion Setting up E-mail Alerts E-mail messages are limited to the alerts generated from the WebUI status bar or the WebUI status page, as well as some event log messages. Some alerts, such as the restart of the server, only occur if the WebUI was utilized to initiate the request. For example, a restart initiated using the WebUI will general an e-mail message indicating a restart has occurred.
Basic Administrative Procedures and Setup Completion 3. Indicate the types of messages to be sent. ■ Critical alerts ■ Warning alerts ■ Informational alerts 4. Enter the desired e-mail address in the appropriate boxes. 5. After all settings have been entered, click OK. Changing System Network Settings Network properties are entered and managed from the Network menu. Most of these settings are entered as part of the Rapid Startup process.
Basic Administrative Procedures and Setup Completion Setup Completion After the NAS device is physically set up and the basic configuration is established, additional setup steps must be completed. Depending on the deployment scenario of the NAS device, these steps may vary.
Basic Administrative Procedures and Setup Completion Installing the HP Network Teaming Utility Before using the HP Network Teaming utility, it must be installed. Note: Installing and configuring NIC teaming should always be performed via iLO port or the console using a direct attached keyboard, monitor, and mouse since IP connections could be reset during the configuration process. Do not use Remote Desktop. To install the HP Network Teaming utility: 1.
Basic Administrative Procedures and Setup Completion Figure 14: Network Teaming installation complete 10. Restart the system. Caution: To ensure proper functioning of the software, the server must be restarted at this time. Opening the HP Network Teaming Utility The HP Network Teaming utility is now accessible from the Windows toolbar at the bottom of the NAS server desktop. To open the utility, click the HP Network Teaming utility icon.
Basic Administrative Procedures and Setup Completion Adding and Configuring NICs in a Team Before a NIC is teamed, verify the following: ■ The NICs must be on the same network. ■ The NICs must be DHCP enabled and the DNS server address must be left blank. Note: The teaming utility becomes unstable if static IP addresses, subnets, and DNS addresses are set before teaming. ■ Duplex and speed settings must be set to use the default values. To team the NICs: 1. Open the HP Network Teaming utility.
Basic Administrative Procedures and Setup Completion Figure 17: NIC Properties, Teaming Controls tab, Fault Tolerant option 4. Configure the team by choosing either Fault Tolerant or Load Balancing. The fault tolerance and load balancing options are discussed in the following sections. Fault Tolerance The Fault Tolerance teaming option provides three redundancy control options: ■ Manual—This setting allows change from a Primary NIC to a Secondary NIC only when Switch Now is clicked.
Basic Administrative Procedures and Setup Completion Figure 18: NIC Properties, Teaming Controls tab, Load Balancing option Detailed information about these four load balancing teaming options can be found in the HP Network Teaming Help. ■ Transmit Load Balancing—All transmit IP frames are load balanced among all team members based on a Load Balancing algorithm in the teaming device driver. The Current Primary adapter transmits all other frames, and receives all frames for the team.
Basic Administrative Procedures and Setup Completion 6. Click OK in the HP Network Teaming and Configuration Properties Screen to apply the changes. 7. Click Yes when prompted to apply all configuration changes. Wait while the adapters are configured. This process could take several seconds. 8. The following screen is displayed, indicating that there are additional procedures to perform in the NIC teaming process. Click Yes to reboot now.
Basic Administrative Procedures and Setup Completion Showing a Connection Icon on the Taskbar To show a connection icon: 1. In the Network and Dial up Connections screen, double-click the NIC Team connection, and then click Properties. 2. At the bottom of the screen, select Show icon in task bar when connected, and then click Close. Configuring the TCP/IP Protocol on the New Team After teaming the NICs, a new virtual network adapter for the team is automatically created.
Basic Administrative Procedures and Setup Completion Figure 21: NIC Team TCP/IP Properties dialog box Note: If a NIC is teamed, do not modify the TCP/IP settings for the individual NIC ports. 4. Select Use the following IP address, and enter the IP address and subnet mask. If desired, enter the default gateway. 5. Click OK. The Ethernet Team should be working.
Basic Administrative Procedures and Setup Completion Checking the Status of the Team To check the status of the Ethernet Team, open the HP Network Teaming utility. The Configuration Properties screen is displayed, showing the teamed NICs.
Basic Administrative Procedures and Setup Completion NIC Teaming Troubleshooting Problems with the NIC teaming feature are diagnosed by the connection icons displayed in the HP Network Teaming and Configuration dialog box. The following table lists the error icons for RJ 45 NICs. Table 2: NIC Teaming Troubleshooting RJ-45 Description Active OK—The NIC is operating properly. The driver is installed in the registry and is loaded. If the NIC is a member of a team, the NIC is active.
Basic Administrative Procedures and Setup Completion Clustering the NAS Server Many aspects of configuring a NAS device in a clustered configuration are unique to that environment. The cluster administration chapter later in this guide provides the details behind this specific configuration and the steps necessary to form a cluster. Throughout the remaining chapters, references to the cluster administration chapter are made when special considerations must be applied when utilizing a cluster configuration.
Basic Administrative Procedures and Setup Completion 50 NAS 4000s and 9000s Administration Guide
Storage Management Overview 3 The NAS server is configured at the factory with default system settings and with the NAS operating system installed. No external addressable storage is included with the NAS device. Storage is based on the SAN infrastructure and is configured using the appropriate tools for the particular SAN storage arrays in use. This chapter defines and discusses physical, logical, and snapshot storage concepts on the HP StorageWorks NAS server.
Storage Management Overview Physical Disks Single Server Cluster Implementation RAID Arrays (ACU - MSA1000 only) Storage Elements Logical Drives (ACU - MSA1000 only) Selective Storage Presentaion (ACU- MSA1000 only) Visible Disks (Windows Device Manager) Partitioning (WebUI) Q: \Engineering \Marketing S: R: \Users \Sales \Engineering \Marketing \Users T: \Sales Q: from 02/10/03 09:30 \snapshot.0 R: from 02/10/03 09:30 \snapshot.0 Q: from 02/10/03 11:30 \snapshot.
Storage Management Overview Storage Elements Overview The NAS server offers optimized performance for a growing environment. Storage capacity can increase as a business grows without downtime or compromised performance. Storage limitations are based on the type of SAN the NAS server is connected to. See the individual SAN documentation for limitations of Windows Storage Server 2003.
Storage Management Overview L1 P1 P2 P3 Figure 25: Configuring the physical drives into an array dramatically improves read/write efficiency Because the read/write heads are active simultaneously, the same amount of data is written to each drive during any given time interval. Each unit of data is termed a block. The blocks form a set of data stripes over all the hard drives in an array, as shown in Figure 26.
Storage Management Overview Logical Drives (LUNs) As previously stated, drive array technology distributes data across a series of individual hard drives to unite these physical drives into one or more higher performance arrays. Distributing the data allows for concurrent access from multiple drives in the array, yielding faster I/O rates than non arrayed drives.
Storage Management Overview Fault-Tolerance Methods Different RAID (redundant array of independent disks) types use different methods of striping the arrays and different ways of writing data and parity to the drives to offer a variety of fault tolerance and capacity usage.
Storage Management Overview RAID 1+0—Drive Mirroring and Striping In this configuration, information on one drive is duplicated onto a second drive, creating identical copies of the information as shown in Figure 28. Therefore, this method provides the best fault tolerance. RAID 1+0 requires an even number of drives and is the only method for fault tolerance protection if only two drives are installed or selected for an array.
Storage Management Overview RAID 5—Distributed Data Guarding Using this method, a block of parity data (rather than redundant data) is calculated for each stripe from the data that is in all other blocks within that stripe. The blocks of parity data are distributed over every hard drive within the array, as shown in the figure below. When a hard drive fails, data on the failed drive can be rebuilt from the parity data and the user data on the remaining drives.
Storage Management Overview Disadvantages Some disadvantages of distributed data guarding are: ■ Lower write performance than RAID 0 or RAID 1+0. ■ Possibility of data loss if a second drive fails before data from the first failed drive has been rebuilt. RAID ADG—Advanced Data Guarding and RAID 5DP—Double Parity RAID ADG and RAID 5DP are similar to RAID 5 in that parity information is generated (and stored) to protect against data loss caused by drive failure.
Storage Management Overview Advantages ■ High read performance. ■ High data availability-any two drives can fail without loss of critical data. Disadvantages ■ Relatively low write performance (lower than RAID 5), due to the need for two sets of parity data. 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 may help determine which option is best for different situations.
Storage Management Overview 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 sub system 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.
Storage Management Overview or be mounted as mount points on existing disks. If mount points are utilized, it should be noted that Services for UNIX does not support mount points at this time. The use of mount points in conjunction with NFS shares is not supported. Volumes 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 are limited to no more than 32 separate LUNs with each LUN not exceeding 2 terabytes (TB).
Storage Management Overview can not be utilized for shares that will be shared using Microsoft Services for Unix (NFS). They can be setup 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 and all three types can be used on the NAS device. However, the Volume Shadow Copy Service can only utilize volumes that are NTFS formatted. Also, quota management is possible only on NTFS.
Storage Management Overview Clustered Server Elements The HP StorageWorks NAS 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, nor will they failover during a node failure.
Disk Management 4 Disk Management is core to the Windows NAS product. The process of creating storage elements and presenting them to the NAS OS is facilitated by the use of the WebUI. This chapter documents the contents of the WebUI for disks and volume management. WebUI Disks Tab The online Storage Guide provides an overview of the storage management process as a supplement to this administration guide. The primary web page for facilitating disks and volume creation is illustrated in Figure 31.
Disk Management To manage disks and volumes via the WebUI, click on Disks. Figure 31: Disks menu The Disks tab contains the following task items for configuring the NAS device: Table 4: Disks Tab Options Option 66 Task Array Management Open the Array Management screen to access the ACU and links to other storage array management elements. Disks Manage logical disks. Observe disk capacity and status, scan for new disks, view detailed disk properties, and create new volumes.
Disk Management Storage Configuration Overview Physical disks can be arranged as RAID arrays for fault tolerance and enhanced performance, 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 NAS server. Note: This type of configuration may not apply to all supported SANs and serves only as an example. The following steps are an example of a storage configuration using an HP StorageWorks MSA1000.
Disk Management Step 4: Create a Volume on the new logical disk 1. Click Create New Volume. 2. Enter the volume size. 3. Select a drive letter. 4. Enter a mount point, if desired. 5. Select to format the volume, if desired. 6. Click OK. 7. Select whether or not to quick format the volume. 8. Enter a volume label. 9. Enter the allocation unit size. 10. Click OK.
Disk Management Array Configuration Utility (MSA1000 and internal OS drives only) RAID arrays and LUNs are created and can be managed using the HP Array Configuration Utility.
Disk Management Note: ACU is used to manage and configure array-based storage. 4. Log in to the ACU utility. The default user name is administrator and the default password is administrator. Figure 33: Systems Management Homepage The Array Configuration Utility is displayed. Figure 34: Array Configuration Utility 5. Select a controller from the list on the left side to begin configuration.
Disk Management ■ The controller named Smart Array 5i Controller in the embedded slot is for all drives in the server chassis, and drives contained in an external storage enclosure attached to the Smart Array 5i on the server head if present. ■ Additional controllers (if present) are used for all externally SCSI attached storage. Caution: On the Smart Array 5i controller there are two logical drives pre-configured under Array A.
Disk Management ACU Guidelines 72 ■ Do not modify Array A off of the Smart Array 5i controller as it contains the NAS OS ■ 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.
Disk Management Managing Disks From the Disks tab of the WebUI, select Disks. The page displays the physical disks that are associated with the NAS device and the volumes that are created on them. Multiple volumes may appear on multiple disks depending on whether the volumes are simple, spanned, or multi-volumes/partitions exist. The page also displays the type of disk (basic or dynamic).
Disk Management Creating a New Volume via the WebUI To create a new volume via the WebUI: 1. Click the Disks tab, then click Disks. 2. Select the Disk to create the new volume on. 3. Click Create New Volume. Figure 36: Creating a new volume, page 1 4. Enter the volume size. 5. Select a drive letter. 6. Enter a mount point, if desired. 7. Select to format the volume, if desired. 8. Click OK.
Disk Management Figure 37: Creating a new volume, page 2 9. Select whether or not to quick format the volume. 10. Enter a volume label. 11. Enter the allocation unit size. 12. Click OK. The Manage Disks page is displayed. Advanced Disk Management When the Advanced Disk Management button on the Manage Disks screen is selected, the Disk Management Utility is opened in a remote desktop session.
Disk Management Figure 38: Disk Management utility Note: When the Disk Management utility is accessed, the Remote Desktop connection assumes a dedicated mode and can only be used to manage disks and volumes on the server. Navigating to another page during an open session closes the session. Note: It may take a few moments for the Remote Desktop Connection session to log off when closing Disk Management.
Disk Management ■ 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 without bringing the system offline or loss of data, but the volume will be unavailable during the conversion. ■ Basic disks can contain up to four primary partitions (or three primary partitions and one extended partition).
Disk Management Figure 39: Volumes tab Table 6: Volumes Page Object/Task Selector Option 78 Task Manage... Select to display the Manage Volumes screen. Schedule Defrag... Select to schedule defragmentation for the selected volume. Set Default Quota Select to set quota limits to manage use of the volume. Settings on this page apply to new users and any users for whom user quota entries have not previously been set. Set Quota Entries Select to show a list of user quota entries.
Disk Management Managing Volumes To manage volumes on the server: 1. On the primary navigation bar, click Disks. 2. Click Volumes. 3. In the Tasks list, click Manage. The Manage Volumes screen is displayed. The Manage Volumes page displays all volumes on the NAS device regardless of their format (NTFS, FAT, or FAT32). Do not tamper with the “Don’t Erase” or the Local C: volume. These are reserved volumes and must be maintained as they exist.
Disk Management Dynamic Growth Dynamic growth is a feature of the NAS server, which provides for growth of a volume or partition to meet expanding storage requirements without the need to take volumes offline or incur downtime. Growth may occur in three forms: ■ Extend unallocated space from original LUNS. ■ Alter LUNs to contain additional storage. ■ Add new LUNS to the system. The additional space is then extended into through a variety of means depending on which type of disk structure is in use.
Disk Management 8. Click Save to update the configuration. 9. Close the ACU. To extend a LUN where space is not available in the array (MSA1000 only): 1. Add an unassigned physical disk to the array using the ACU. If an unassigned physical disk is unavailable, add a new disk to the appropriate storage device and select Refresh. 2. To add an unassigned physical disk to the array use the following steps: a.
Disk Management Figure 42: Extending a volume (basic disk) 6. Click OK. Extending a Volume on Dynamic Disks (non-clustered systems only) The WebUI allows for the extension of volumes based on a dynamic disk or a set of dynamic disks. To extend a volume perform the following steps: 1. Click the Disks tab. 2. Click the Volumes tab. 3. Click Manage. 4. Select the volume to extend and select Extend.
Disk Management Figure 43: Extending a volume (dynamic disk) 5. Enter the amount to extend the volume. If no more space is available on the current dynamic disk, add an additional dynamic disk to the list of available disks and utilize space from it. 6. Click OK. Extending using DiskPart DiskPart may also be used to extend a partition or volume from the CMD prompt of the NAS operating system via Remote Desktop.
Disk Management 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 allows the system to access files and folders and save new ones more efficiently. Because defragmentation consolidates files and folders, it also consolidates the free space on a volume. This reduces the likelihood that new files will be fragmented.
Disk Management Note: NTFS compression is supported only if the cluster size is 4 KB or smaller. Managing Disks After Quick Restore After a Quick Restore, drive letters may be assigned to the wrong volume. Windows Storage Server 2003 assigns drive letters after the restoration in the order of discovery. To help maintain drive letter information, placing the drive letter into the volume label is recommended.
Disk Management 5. Click Yes to confirm the drive letter change. Figure 46: Confirm drive letter change 6. If the dialog box in Figure 47 is displayed, select Yes to continue. If the old drive letter needs to be reused, reboot the server after clicking Yes.
Disk Management Disk Quotas Disk quotas track and control disk space use in volumes. Note: To limit the size of a folder or share, see “Directory Quotas” in Chapter 7. 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.
Disk Management 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. To disable quota management on a volume: 1. On the primary navigation bar, click Disks. 2. Click Volumes. 3. Select the volume to manage. 4.
Disk Management To create a new user quota entry: 1. Click New Quota Entry. 2. Select a user. 3. Set the limit. 4. Set the warning level. 5. Click OK. Figure 49: Add new quota entry To change a quota entry: 1. Select the quota to change. 2. Click Properties. 3. Change the limit. 4. Change the warning level. 5. Click OK. To delete a quota entry: 1. Select the quota to change. 2. Click Delete.
Disk Management DiskPart DiskPart.exe is a text-mode command interpreter that enables the administrator to manage disks, partitions, or volumes. When using the list commands, an asterisk (*) appears next to the object with focus. Select an object by its number or drive letter, such as disk 0, partition 1, volume 3, or volume C. When selecting an object, the focus remains on that object until a different object is selected.
Disk Management For a complete list of DiskPart commands, go to the Windows Storage Server 2003 Desktop on the NAS device via Remote Desktop and select Start >Help and Support, search on DiskPart. Example of using DiskPart The following example shows how to configure a volume on the NAS server.
Disk Management 92 NAS 4000s and 9000s Administration Guide
Shadow Copies 5 Overview Note: The NAS 4000s and 9000s servers can be deployed in a clustered as well as a non-clustered configuration. This chapters discusses using Shadow Copies in a non-clustered environment. Please review the Cluster Administration chapter of this guide for additional information regarding Shadow Copies in a cluster. The Volume Shadow Copy Service provides an infrastructure for creating point-in-time snapshots (shadow copies) of volumes.
Shadow Copies Shadow Copy Planning Before setup is initiated on the server and the client interface is made available to end users, consider the following: ■ From what volume will shadow copies be taken? ■ How much disk space should be allocated for shadow copies? ■ Will separate disks be used to store shadow copies? ■ How frequently will shadow copies be made? Identifying the Volume Shadow copies are taken for a complete volume, but not for a specific directory.
Shadow Copies user expectations of how many versions they will want to have available. End users might expect only a single shadow copy to be available, or they might expect three days or three weeks worth of shadow copies. The more shadow copies users expect, the more storage space administrators must allocate for storing them.
Shadow Copies Identifying the Storage Area To store the shadow copies of another volume on the same file server, a volume can be dedicated on separate disks. For example, if user files are stored on H:\, another volume such as S:\ can be used to store the shadow copies. Using a separate volume on separate disks provides better performance and is recommended for heavily used NAS devices.
Shadow Copies Shadow Copies and Drive Defragmentation When running Disk Defragmenter on a volume with shadow copies activated, all or some of the shadow copies may be lost, starting with the oldest shadow copies. If defragmenting volumes on which shadow copies are enabled, use a cluster (or allocation unit) size of 16 KB or larger. Utilizing this allocation unit size reduces the number of copy outs occurring on the snapshot.
Shadow Copies Managing Shadow Copies From the WebUI Welcome screen, click Disks, then Shadow Copies to display the Shadow Copies screen. Figure 50: Shadow Copies screen Table 9: Shadow Copies Fields Field 98 Description Volume Lists all volumes of the server on which the Shadow Copies service can be used. Only NTFS file system data volumes that are physically located on the server can support shadow copies.
Shadow Copies Table 10: Shadow Copies Tasks Task Description Enable Click to enable Shadow Copies on the selected volume. Disable Click to enable Shadow Copies on the selected volume. New Shadow Copy Click to immediately create a new shadow copy on the selected volume. View Shadow Copies Click to view a list of shadow copies on the selected volume. Set Schedule Click to set the time and frequency of shadow copies. Properties...
Shadow Copies E: F: G: L: cache file cache file cache file Figure 52: Shadow copies stored on 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.
Shadow Copies Enabling and Creating Shadow Copies Enabling the Shadow Copies service for a volume or creating a shadow copy can be done directly from the Manage Shadow Copies page. Enabling shadow copies on a volume automatically results in several actions: ■ Creates a shadow copy of the selected volume ■ Sets the maximum storage space for the shadow copies ■ Schedules shadow copies to be made at 7 A.M. and 12 noon on weekdays.
Shadow Copies Set Schedules Shadow Copy schedules control how frequently shadow copies of a volume are made. There are a number of factors that can help determine the most effective shadow copy schedule for an organization. These include the work habits and locations of the users. For example, if users do not all live in the same time zone, or they work on different schedules, it is possible to adjust the daily shadow-copy schedule to allow for these differences.
Shadow Copies 3. On the Manage Shadow Copies page, select the volume on which to view shadow copy properties. 4. On the Tasks list, click Properties. The Shadow Copy Properties screen, as shown in Figure 53, lists the number of copies, the date and time the most recent shadow copy was made, and the maximum size setting. Change the maximum size limit for all shadow copies, or choose No limit. For volumes where shadow copies do not exist currently, it is possible to change the location of the cache file.
Shadow Copies Disabling Shadow Copies When shadow copies are disabled on a volume, all existing shadow copies on the volume are deleted as well as the schedule for making new shadow copies. To disable shadow copies on a volume: 1. On the primary navigation bar, click Disks. 2. Click the Shadow Copies tab. 3. On the Manage Shadow Copies page, select one or more volumes on which to disable shadow copies. 4. In the Tasks list, click Disable.
Shadow Copies Managing Shadow Copies from the NAS Desktop As an alternative to managing Shadow Copies via the WebUI, the NAS Desktop may be accessed via Remote Desktop. To access Shadow Copies from the NAS Desktop: 1. From the WebUI select Remote Desktop from the Maintenance tab. 2. Click My Computer. 3. Select the volume. 4. Right-click the volume name and select Properties. 5. Click the Shadow Copies tab. The user interface provides the same functionality found in the WebUI but in Win32 form.
Shadow Copies Shadow Copies for Shared Folders Shadow Copies are accessed over the network by supported clients and protocols. There are two sets of supported protocols, SMB and NFS. All other protocols are not supported; this would include HTTP, FTP, AppleTalk, and NetWare Shares. For SMB support a client side application denoted as Shadow Copies for Shared Folders is required. The client side application is currently only available for Windows XP and Windows 2000 SP3+.
Shadow Copies Users access shadow copies with Windows Explorer by selecting View, Copy, or Restore, from the Previous Versions tab. See Figure 55. Both individual files and folders may be restored. Figure 55: Client GUI When users view a network folder hosted on the NAS device for which shadow copies are enabled, old versions (prior to the snapshot) of a file or directory are available.
Shadow Copies 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.
Shadow Copies Recovering a Deleted File or Folder To recover a deleted file or folder within a folder: 1. Navigate to the folder where the deleted file was stored. 2. Position the cursor over a blank space in the folder. If the cursor hovers over a file, that file will be selected. 3. Right-click the mouse and select Properties from the bottom of the menu. Select the Previous Versions tab. 4. Select the version of the folder that contains the file before it was deleted, and then click View. 5.
Shadow Copies 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 use the following procedure: 1. Right-click the overwritten or corrupted file and click Properties. 2. Select Previous Versions. 3. To view the old version, click View. To copy the old version to another location, click Copy...
User and Group Management 6 There are two system environments for users and groups: workgroup and domain. Because users and groups in a domain environment are managed through standard Windows NT or Windows Storage Server 2003 domain administration methods, this document discusses only local users and groups, which are stored and managed on the NAS device. For information on managing users and groups on a domain, refer to the domain documentation available on the Microsoft website.
User and Group Management The configuration of the domain controller is reflected on the NAS server because it obtains user account information from the domain controller when deployed in a domain environment. As mentioned previously, the server cannot act as a domain controller itself. User and Group Name Planning Effective user and group management is dependent upon how well the user and group names are organized.
User and Group Management Using tags is a helpful convention that indicates the specific access that a particular user has to a network resource. For example, if there is a data share on the device, the network administrator can create a “Data Users ROnly” group and a “Data Users RWrite” group to contain users that have read only or read write access on the share, respectively. Workgroup User and Group Management Note: In a clustered environment, users and groups should not be managed locally.
User and Group Management Figure 57: Local Users dialog box All available options include: New, Delete, Set a Password, and Properties. When the Local Users dialog box is initially displayed, only the New option is available. After an existing user is selected, the additional actions are displayed. Each of these options is discussed in the following paragraphs.
User and Group Management Figure 58: Create New User dialog box 2. Enter the user information and then click OK. The user is added and the Local Users dialog box is displayed again. Deleting a User To delete a user: 1. In the Local Users dialog box, select the user to delete, and then click Delete. The Delete User dialog box is displayed, including a warning note about deleting users. 2. To delete the user, click OK. The user is deleted and the Local Users dialog box is displayed again.
User and Group Management Modifying a User Password Follow these steps to modify a user password: 1. In the Local Users dialog box, select the user whose password needs to be changed. Then, click Set a Password. The Set Password dialog box is displayed. 2. Enter the password and click OK. The Local Users dialog box is displayed again. Modifying User Properties To modify other user properties: 1. From the Local Users dialog box, select the user whose record needs to be modified. Then, click Properties.
User and Group Management Managing Local Groups Managing groups includes the following tasks: ■ Adding a new group ■ Deleting a group ■ Modifying group properties, including user memberships Local groups in a workgroup environment are managed through the Users option in the WebUI. In the WebUI, under Users, Local Groups is the Local Groups on Server dialog box. All workgroup group administration tasks are performed in the Local Groups on Server Appliance dialog box.
User and Group Management Adding a New Group To add a group: 1. In the Local Groups dialog box, click New. The Create New Group dialog box is displayed. Figure 61: Create New Group dialog box, General tab 2. Enter the group name and description. 3. To indicate the user members of this group, click Members. See “Modifying Group Properties” for procedural instructions on entering group members. 4. After all group information is entered, click OK.
User and Group Management Modifying Group Properties To modify other group properties: 1. From the Local Groups dialog box, select the desired group and then click Properties. The Properties dialog box is displayed. Figure 62: Group Properties dialog box, General tab Within the Properties dialog box are two tabs: ■ General tab ■ Members tab Each of these tabs is discussed in the following paragraphs. 2. Enter the desired changes in each of the tabs. Then, click OK.
User and Group Management ■ To add an existing local user to a group: 1. Select the desired user from the Add user or group box 2. Click the Add button. 3. Click OK to save the changes. ■ To remove an existing local user from a group: 1. Select the desired user from the Members box. 2. Click Remove. 3. Click OK to save the changes. ■ To add a user or group from a domain to this group, the scroll bar at the right of the screen may need to be used to scroll up the screen display: 1.
Folder, Printer, and Share Management 7 The HP StorageWorks NAS server supports several file sharing protocols, including DFS, NFS, FTP, HTTP, and Microsoft SMB. This chapter discusses overview information as well as procedural instructions for the setup and management of the file shares for the supported protocols. In addition, discussions on security at the file level and at the share level are included in this chapter.
Folder, Printer, and Share Management ■ Modifying folder properties ■ Creating a new share for a volume or folder ■ Managing shares for a volume or folder ■ Managing file level permissions Navigating to a Specific Volume or Folder When you work with volumes and folders, the first task is to gain access to the desired volume or folder. The steps are the same, whether navigating to a volume or a folder: 1. To navigate to a specific volume or folder, from the WebUI, select Shares and then Folders.
Folder, Printer, and Share Management Figure 65: Folders dialog box After accessing the desired folder, the following actions can be performed: ■ Creating a new folder ■ Deleting a folder ■ Modifying folder properties ■ Creating a new share for the volume or folder ■ Managing shares for the volume or folder Creating a New Folder To create a new folder: 1. From the Shares directory, navigate to the Folders menu and then select New. The Create New Folder dialog box is displayed.
Folder, Printer, and Share Management Figure 66: Create a New Folder dialog box, General tab 3. In the Compress tab, indicate whether and how this folder and its contents are to be compressed. 4. After all information for the new folder is entered, click OK. Deleting a Folder To delete a folder: 1. From the Shares directory, navigate to the folder to delete. Select the folder and then click Delete. The Delete Folder dialog box is displayed. Summary information about the deletion is displayed.
Folder, Printer, and Share Management Figure 67: Folder Properties dialog box, General tab 2. In the General tab, enter the new information for the folder, which may include: ■ Folder Name ■ Folder Attributes 3. In the Compress tab, indicate whether and how this folder and its contents are to be compressed. 4. After all changes have been completed, click OK. The Folders dialog box is displayed again.
Folder, Printer, and Share Management 2. Click New. The Create New Share dialog box is displayed. Figure 68: Create New Share dialog box, General tab 3. Enter the information for the share, including the name of the share, the allowed protocols, and corresponding permissions. Note: The Share path is the path of the previously selected volume or folder. This field is automatically completed by the system. 4. Select the appropriate tab to enter protocol specific information.
Folder, Printer, and Share Management Note: This section discusses managing shares from the Folders menu, and is an overview of the procedures. Complete details on the process of managing shares are included in the discussion that documents creating shares through the Shares menu. See the “Managing Shares” section later in this chapter for these details. To create, delete, and manage shares for a particular volume or folder while in the Folders menu: 1.
Folder, Printer, and Share Management Figure 69: Security Properties dialog box Several options are available in the Security tab dialog box: 128 ■ To add users and groups to the permissions list, click Add. Then 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 provides a listing of permission levels.
Folder, Printer, and Share Management Figure 70: Advanced security settings To modify specific permissions assigned to a particular user or group for a selected file or folder in the Advanced screen: 1. Select the desired user or group. 2. Click Edit. 3. Check all the permissions that you want to enable, and clear the permissions that you want to disable. Enable or disable permissions by selecting the Allow box to enable permission or the Deny box to disable permission.
Folder, Printer, and Share Management Figure 71: User or Group Permission Entry dialog box Other functionality available in the Advanced Security Settings tab is illustrated in Figure 70 and includes: ■ Add a new user or group. Click Add, and then follow the dialog box instructions. ■ Remove a user or group. Click Remove. ■ Replace permission entries on all child objects with entries shown here that apply to child objects.
Folder, Printer, and Share Management Figure 72: Advanced Security Settings, Auditing tab dialog box 4. Click Add to display the Select User or Group dialog box. Figure 73: Select User or Group dialog box Note: Click Advanced to search for users or groups. 5. Select the user or group. 6. Click OK. Figure 74 illustrates the Auditing Entry screen that is displayed.
Folder, Printer, and Share Management Figure 74: Auditing Entry dialog box for folder name NTSF Test 7. Select the desired Successful and Failed audits for the user or group as shown in Figure 74. 8. Click OK. Note: Auditing must be enabled to configure this information. Use the local Computer Policy Editor to configure the audit policy on the NAS server. The Owner tab allows for taking ownership of files.
Folder, Printer, and Share Management Figure 75: Advanced Security Settings, Owner tab dialog box The current owner of the file or folder is listed at the top of the screen. To take ownership: 1. Select the appropriate user or group from 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 to execute the commands.
Folder, Printer, and Share Management Share Management There are several ways to set up and manage shares. The WebUI provides screens for setting up and managing shares. Additional methods include using a command line interface, Windows Explorer, or NAS Management Console. This guide demonstrates using the WebUI to set up and manage shares. Note: The NAS 4000s and 9000s servers can be deployed in a clustered as well as a non-clustered configuration.
Folder, Printer, and Share Management Integrating Local File System Security into Windows Domain Environments ACLs include properties specific to users and groups from a particular workgroup server or domain environment. In a multidomain environment, user and group permissions from several domains can apply to files stored on the same device. Users and groups local to the NAS server can be given access permissions to shares managed by the device.
Folder, Printer, and Share Management NFS Compatibility Issues When planning to manage CIFS and NFS shares, consider two specific requirements. Note: Further information, including details about the NFS Service and the User Mapping service, is available in the “Microsoft Services for NFS” chapter. ■ NFS service does not support spaces in the names for NFS file shares. NFS translates any spaces in an export into an underscore character. Additional translations can be set up for files.
Folder, Printer, and Share Management Figure 76: Create a New Share dialog box, General tab 2. Enter the following information: ■ Share name ■ Share path ■ Client protocol types To create a folder for the new share, check the indicated box and the system will create the folder at the same time it creates the share. Protocol specific tabs are available to enter sharing and permissions information for each sharing type. See “Modifying Share Properties” for detailed information on these tabs. 3.
Folder, Printer, and Share Management Modifying Share Properties To change share settings: 1. From the Shares menu, select the share to modify and then click Properties. The General tab of the Share Properties dialog box is displayed. Figure 77: Share Properties dialog box, General tab The name and path of the selected share is displayed. 2. To enter or change client protocol information, check the appropriate boxes and then click the corresponding tabs.
Folder, Printer, and Share Management Figure 78: Share Properties dialog box, Windows Sharing tab 2. Select Offline settings. 3. Set the permissions. The Permissions box lists the currently approved users for this share. ■ To add a new user or group, either select a user or group from the box at the bottom right of the screen or manually enter the user or group name in the Add a user or group box and then click Add. That user or group is added to the Permissions box.
Folder, Printer, and Share Management Figure 79: Share Properties dialog box, UNIX Sharing tab 2. Indicate the access permissions. Select the machine from the main user display box and then select the appropriate access method from the Access permissions drop down box. The types of access are: ■ Read-only—Use this permission to restrict write access to the share. ■ Read-write—Use this permission to allow clients to read or write to the share.
Folder, Printer, and Share Management Protocol Parameter Settings As previously mentioned, the NAS server supports the following protocols: ■ DFS ■ NFS ■ FTP ■ HTTP ■ Microsoft SMB This section discusses the parameter settings for each protocol type. Note: See the protocol section of the Cluster Administration chapter for information about protocol selection and management in a cluster. To access and enter protocol parameter settings: 1. From the Shares menu, select Sharing Protocols.
Folder, Printer, and Share Management DFS Protocol Settings With Distributed File System (DFS) and the Windows SMB protocol, files can be distributed across multiple servers and appear to users as if they reside in one place on the network. A configuration containing multiple shares is known as a virtual namespace. Using Distributed File System (DFS), system administrators can make it easy for users to access and manage files that are physically distributed across a network.
Folder, Printer, and Share Management Figure 81: DFS Win32 GUI DFS Administration Tool The DFS Administration Tool provides extended functionality not found in the WebUI.
Folder, Printer, and Share Management Setting DFS Sharing Defaults The We UI can be used to set the default DFS settings provided when creating a shared folder. When a new shared folder is create, the DFS defaults may be overridden. To set DFS sharing defaults: 1. On the primary navigation bar, choose Shares. 2. Choose Sharing Protocols. 3. Select DFS, and then choose Properties. Figure 82: DFS properties, general tab 4.
Folder, Printer, and Share Management 3. Select DFS, and then choose Properties. Figure 83: Local DFS Root tab 4. On the Local DFS Root tab, type the name of the DFS root in the Root name box. 5. In the Folder path box, type the path of the folder that corresponds to the root. Click Create folder if the folder does not exist. 6. Choose Create DFS Root, and then choose OK. Deleting a Local DFS Root The WebUI enables the deletion of a local stand-alone DFS root on the server only.
Folder, Printer, and Share Management Publishing a New Share in DFS Once a root has been established either on the local machine or one in the network, shares can be published in order to extend the virtual name space. For example, several shares can be created for a DFS root labeled “Engineering.” The shares might be titled “Documentation,” “Technical Specs,” and “Project Info.
Folder, Printer, and Share Management Figure 85: DFS share example, mapped drive In this case, Documentation exists on G:\documentation, Technical Specs exists on G:\technical specs and Project Info exists on C:\project info on the local machine but they are all accessible via \\DOCNASBOX\engineering. Publishing an Existing Share in DFS To enable an existing shares for DFS, perform the following steps: 1. Select Shares from the WebUI. 2. Select the target share from the table and select Publish in DFS.
Folder, Printer, and Share Management Storage Management The storage management features built into the NAS server are composed of three main features and are applicable at the directory level of a share. These features include: ■ Directory Quotas ■ File Screening ■ Storage Reports Each of these feature sets are describe below. For procedures and methods, refer to the online help available within the web UI via the ? in the right hand corner of each accompanying feature management page.
Folder, Printer, and Share Management The Directory Quota feature includes the following components: ■ Active and passive space limits on directories ■ Best practice storage resource management policies ■ A severe alarm threshold ■ A warning alarm threshold ■ Auto discovery of drives ■ Customized messages ■ Alarms sent to the event log ■ Alarms sent to the user ■ Storage reports that can be sent to an intranet Web site ■ Custom script support The directory quota set on the system partit
Folder, Printer, and Share Management Each of these policies provides an example of a particular policy type. Custom policies should be created to meet the needs of the environment.
Folder, Printer, and Share Management Within each policy, there are a number of configuration screens that are presented in the form of a wizard. The wizard collects the following information to create a policy: ■ Name of Policy ■ Disk space limit and Unit of measurement ■ Passive limit (If selected the limit will issue warnings but will not prevent access.
Folder, Printer, and Share Management Use caution when placing screening parameters on the system partition. If certain classes of files are screened from the system partition, the operating system may not have the access to save temporary working files. It is a good idea to exclude systems directories from screening. Another option is to create a passive screening policy that allows files to be saved but the file activity to be logged.
Folder, Printer, and Share Management Print Services Printer services are a new feature added to the NAS server that has not been available previously. The new service supports network printers only and is not intended for use with locally attached printers (USB or Parallel port connected). Note: See the Cluster Administration chapter for information on clustering a print spooler.
Folder, Printer, and Share Management Note: While the “All Windows” support may be selected at this step, it is more efficient to add the alternative operating systems on each printer after the wizards are complete. See section below on “Adding Additional Operating System Support”. 6. Click Next on the Summary page and an Add Printer Wizard will start. 7. Select Local Printer and uncheck “automatically detect install my plug and play printers” click Next.
Folder, Printer, and Share Management Removing the Print Server Role To remove the print server role: 1. Click Start > Settings > Control Panel, double-click Administrative Tools, and then double-click Manage Your Server. 2. Click on Add or Remove a Roll. 3. A wizard will start. Click Next. 4. Select Printer Server from the list of Server Roles and click Next. 5. Select the checkbox Remove the printer role, click Next. 6. The Printer role will be removed, click Finish.
Folder, Printer, and Share Management 10. Enter a Share Name for the printer that will used on the network, click Next. 11. Enter a location description and a comment, click Next. 12. Select Print a test page and click Next. 13. Click Finish. A test page prints. Click OK if the page printed otherwise select Troubleshoot. Adding Additional Operating System Support By default, support is added for Windows 2000 and Windows XP.
Microsoft Services for NFS 8 Microsoft Services for NFS is a comprehensive software package designed to provide complete UNIX environment integration into a Windows NT, Windows 2000, Windows Storage Server 2003, or Active Directory domain file server. Services for NFS manages tasks on both Windows and UNIX platforms. Tasks include creating NFS exports from Windows and administering user name mappings.
Microsoft Services for NFS Permissions are granted on a per-export basis; each export has its own permissions, independent of other exports on the system. For example, file system a can be exported to allow only the Accounting department access, and file system m can be exported allowing only the Management department access. If a user in Management needs access to the Accounting information, the A export permissions can be modified to let that one user's client machine have access.
Microsoft Services for NFS Note: If the authentication software is not installed on all domain controllers that have user name mappings, including Primary Domain Controllers, Backup Domain Controllers, and Active Directory Domains, then domain user name mappings will not work correctly. Figure 88: Microsoft Services for NFS screen, Settings tab Logging Events Various levels of auditing are available. Auditing sends Services for NFS events to a file for later review and establishes log-setting behavior.
Microsoft Services for NFS Figure 89: Server for NFS screen, Logging tab Server for NFS Server Settings The NAS server has new features for Services for NFS included in the Services for NFS administration GUI. The new features include settings that affect performance, such as toggling between TCP and UDP NFS versions 2 and 3. Other Server for NFS server settings include those that affect how file names are presented to NFS clients, such as allowing hidden files and allowing case sensitive lookups.
Microsoft Services for NFS Figure 90: Server for NFS screen, Server Settings tab NAS 4000s and 9000s Administration Guide 161
Microsoft Services for NFS Installing NFS Authentication Software on the Domain Controllers and Active Directory Domain Controllers The NFS Authentication software must be installed on all Primary Domain Controllers (PDCs) and backup domain controllers (BDCs) that have Windows users mapped to UNIX users. This includes Active Directory domains. For instructions on setting up user mappings, see “NFS User and Group Mappings.
Microsoft Services for NFS Microsoft Services for Unix 3.0 CD has been included with the NAS server and is needed for the following procedure. To install the Authentication software on the domain controllers (CD Method): 1. Insert the Microsoft Windows Services for UNIX compact disc into the CD-ROM drive of the domain controller. 2. In the Microsoft Windows Services for UNIX Setup Wizard dialog box, click Next. 3. In the User name box, type your name.
Microsoft Services for NFS Understanding NTFS and UNIX Permissions When creating a NFS export, make sure that the NTFS permissions on the share allows the correct permissions that you want assigned for users/groups.
Microsoft Services for NFS Figure 91: Create a New Share dialog box, General tab 2. In the General tab, enter the share name and path. Check the Unix (NFS) client protocol check box. Note: Uncheck the Microsoft SMB option if you do not want to allow SMB access to the share. Note: NFS service does not support the use of spaces in the names for NFS file shares. NFS translates any spaces in an export into an underscore character.
Microsoft Services for NFS Deleting a Share Caution: Before deleting a share, warn all users to exit that share. Then confirm that no one is using the share. To delete a share: 1. From the Shares menu, select the share to be deleted, and then click Delete. 2. Verify that this is the correct share, and then click OK. Modifying Share Properties To change share settings: 1. From the Shares menu, select the share to modify and then click Properties.
Microsoft Services for NFS Figure 93: UNIX Sharing tab 3. From the UNIX Sharing tab of the Share Properties dialog box, a. Indicate the allowed clients. Select the machine to include in the Select a group box or manually enter the NFS client computer name or IP address. Then click Add. b. Indicate the access permissions. Select the machine from the main user display box and then select the appropriate access method from the Access permissions drop down box.
Microsoft Services for NFS Anonymous Access to an NFS Share It may be desirable to add anonymous access to a share. An instance would be when it is not desirable or possible to create and map a UNIX account for every Windows user. A UNIX user whose account is not mapped to a Windows account is treated by Server for NFS as an anonymous user. By default, the user indentifier (UID) and group identifier (GID) is -2.
Microsoft Services for NFS Encoding Types Encoding types can be selected using the WebUI. These include the default ANSI as well as EUC-JP. Other encoding types include: ■ ANSI (default) ■ BIG5 (Chinese) ■ EUC-JP (Japanese) ■ EUC-KR (Korean) ■ EUC-TW (Chinese) ■ GB2312-80 (Simplified Chinese) ■ KSC5601 (Korean) ■ SHIFT-JIS (Japanese) If the option is set to ANSI on systems configured for non-English locales, the encoding scheme is set to the default encoding scheme for the locale.
Microsoft Services for NFS Figure 94: NFS Sharing Protocols menu NFS properties include: ■ Async/Sync Settings ■ NFS Locks ■ Client Groups ■ User and Group Mappings Settings for asynchronous/synchronous writes and service locks are discussed together in the following paragraphs of this chapter. Client groups and user and group mappings are each discussed in separate sections later in this chapter.
Microsoft Services for NFS Note: Using synchronous writes allows for greater data integrity. Asynchronous writes will increase performance but will reduce data integrity as the data is cached before being written to disk. Changing the write state causes the NFS service to be restarted. Notify users before toggling this setting. Figure 95: NFS Async/Sync Settings dialog box NFS Locks NFS supports the ability to lock files.
Microsoft Services for NFS To enter locking parameters: 1. From the WebUI, access the NFS Protocol Properties menu by selecting Shares, Sharing Protocols. Select NFS Protocol and then click Properties. The NFS Properties menu is displayed. 2. In the NFS Properties menu, select NFS Locks. The NFS Locks dialog box is displayed. Figure 96 is an illustration of the NFS Locks dialog box. All clients that have locks on system files are listed in the Clients that hold locks box. 3.
Microsoft Services for NFS NFS Client Groups The Client Groups feature gives administrators a method of assigning access permissions to a set of clients. The administrator creates a client group, gives it a name, and then inserts clients into the group by client name or IP address. After the client group is created, the administrator adds or removes permissions for the entire group, instead of allowing or denying access for each individual client machine.
Microsoft Services for NFS Adding a New Client Group To add a new client group: 1. From the NFS Client Groups dialog box, click New. The New NFS Client Group dialog box is displayed. Figure 98: New NFS Client Group dialog box 2. Enter the name of the new group. 3. Enter the client name or their IP address. 4. Click Add. The system adds the client to the displayed list of members. 5. To remove a client from the group, select the client from the Members box and then click Remove. 6.
Microsoft Services for NFS Editing Client Group Information To modify the members of an existing client group: 1. From the NFS Client Groups dialog box, select the group to modify, and click Edit. The Edit NFS Client Group dialog box is displayed. Current members of the group are listed in the Members box. Figure 99: Edit NFS Client Groups dialog box 2. To add a client to the group, enter the client name or IP address in the Client name box, and then click Add.
Microsoft Services for NFS NFS User and Group Mappings When a fileserver exports files within a homogeneous environment, there are no problems with authentication. It is a simple matter of making a direct comparison to determine whether the user should be allowed access to the file, and what level of access to allow. However, when a fileserver works in a heterogeneous environment, some method of translating user access is required.
Microsoft Services for NFS Squashed Mappings If the NFS server does not have a corresponding UID or GID or if the administrator has set other conditions to filter out the user, a process called squashing takes effect. Squashing is the conversion of an unmapped or filtered user to an anonymous user. This anonymous user has very restricted permissions on the system.
Microsoft Services for NFS — Make sure that the Windows Group1 is mapped to the corresponding UNIX Group1. — Make sure that User1 is a member of Group1 on both Windows and UNIX. ■ Map properly — Valid UNIX users should be mapped to valid Windows users. — Valid UNIX groups should be mapped to valid Windows groups. — The mapped Windows user must have the Access this computer from the Network privilege, or the mapping will be squashed.
Microsoft Services for NFS Figure 101: User and Group Mappings dialog box, General tab From the General tab of the User and Group Mappings dialog box: 1. If an NIS server is being used: a. Select Use NIS server. b. Enter the NIS domain name. c. Enter the NIS server name. This field is optional, but recommended. In the Hours and Minutes fields, indicate how often the system will connect to the NIS domain to update the user list. 2. If custom password and group files are being used: a.
Microsoft Services for NFS Figure 102: User and Group Mappings dialog box, Simple Mapping tab Explicit User Mapping Tab Explicit (or advanced) mappings allow the administrator to map any user or group manually to any other user and group. Advanced mappings override simple mappings, giving administrators the capability of using simple mapping for most users and then using advanced mappings for the users with unique names on the different systems.
Microsoft Services for NFS Figure 103: User and Group Mappings dialog box, Explicit User Mapping tab To create explicit user mappings: 1. Click the List UNIX Users button to populate the UNIX users box. 2. To map a local Windows user to a UNIX user, highlight the Windows user in the Windows local users box and highlight the UNIX user that you want to map, and then click Add. The Explicitly mapped users box at the bottom of the screen is populated with the new mappings.
Microsoft Services for NFS Figure 104: User and Group Mappings dialog box, Explicit Group Mapping tab To create explicit group mappings: 1. Click the List UNIX Groups button to populate the UNIX Groups box. 2. To map a local Windows group to a UNIX group, highlight the Windows group in the Windows local groups box and highlight the UNIX group to map, and then click Add. The Explicitly mapped groups box at the bottom of the screen is populated with the new mappings.
Microsoft Services for NFS Backing up and Restoring Mappings The user name-mapping server has the capability to save and retrieve mappings from files. This capability is useful for backing up mapping settings prior to making changes and for exporting the mapping file from one server to others, using the same mapping information. The user name-mapping server can save existing mappings to a file or load them from a file and populate the mapping server.
Microsoft Services for NFS 2. Type the path and name of the file in the File path and name field or click Browse to locate the file. 3. After locating the file, click Restore. Creating a Sample NFS File Share HP recommends performing the following tests to verify that the setup of the shares, user mappings, and permissions grant the desired access to the NFS shares. 1. Create an NFS share. NFS Shares are All Machines, read-only by default.
Microsoft Services for NFS d. Create the file as the mapped user (example: file1). 8. Verify that the same permissions are set up for the user on both the UNIX side and the Windows side. a. List the permissions on the UNIX side: ls -l /mount-point/file1 (Example screen display: -r--r----- unixuser1 unixgroup1) b.
Microsoft Services for NFS Remote Desktop In addition to the WebUI, Remote Desktop is available for remote administration of Services for UNIX. This service let users connect to machines, log on, and obtain command prompts remotely. See Table 12 for a list of commonly used commands. Using Remote Desktop Microsoft Remote Desktop can be used to remotely access the NAS server desktop. This provides the administrator flexibility to automate setups and other tasks.
NetWare File System Management 9 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. Customers using NetWare as the platform to host their file and print services have become accustomed to its interface from both a user and an administrator point of view and have built up an investment in NetWare file and print services.
NetWare File System Management Installing Services for NetWare The installation of FPNW on the NAS server allows for a smooth integration with existing Novell servers. FPNW allows a Windows Storage Server 2003-based server to emulate a NetWare file and print server to users, clients, and administrators. This emulation allows authentication from Novell clients, the use of Novel logon scripts, the creation of Novell volumes (shares), the use of Novell file attributes, and many other Novell features.
NetWare File System Management 6. Select File and Print Services for NetWare and click OK. Figure 107: Select network service 7. Click OK. Figure 108: Install File and Print Services for NetWare 8. Select or change items as necessary. 9. Click OK. The system must be rebooted for the changes to take effect.
NetWare File System Management Managing File and Print Services for NetWare To access FPNW: 1. From the desktop of the NAS server, click Start > Settings > Control Panel > Administrative Tools > Server Manager. 2. Select FPNW, then Properties. Figure 109: File and Print Services for NetWare screen 3. Enter an FPNW Server Name and Description. This name must be different from the server name used by Windows or LAN Manager-based clients to refer to the server.
NetWare File System Management 4. Indicate a Home directory root path. This path is relative to where the Sysvol volume has been installed. This will be the root location for the individual home directories. If the directory specified does not already exist, it must first be created. 5. Click Users to: See connected users, disconnect users, send broadcast messages to all users connected to the server, and to send a message to a specific user. 6.
NetWare File System Management Enabling Local NetWare User Accounts 1. In the Users folder (NMC, Core Operating System, Local Users and Groups), right-click an NCP client listed in the right pane of the screen and then click Properties. 2. Select the NetWare Services tab. Figure 111: NetWare Services tab 3. Select Maintain NetWare compatible login. 4. Set other NetWare options for the user and click OK.
NetWare File System Management Managing NCP Volumes (Shares) NCP file shares are created in the same manner as other file shares; however, there are some unique settings. NCP shares can be created and managed using the NAS Management Console. Note: NCP shares can be created only after Microsoft Services for NetWare is installed. See the previous section “Installing Services for NetWare” for instructions on installing SFN. Creating a New NCP Share To create a new file share: 1.
NetWare File System Management Figure 113: Share permissions dialog box 6. Click Add to add additional users and groups, and to set their permissions. Figure 114: Add Users and Groups dialog box 7. Highlight the desired user or group, then click Add. 8. Select the Type of Access from the drop down list. Note: Type of Access can also be set from the Access Through Share Permissions dialog box.
NetWare File System Management 9. Click OK when all users and groups have been added. 10. Click OK on the Create Volume dialog box. 11. Click Close. Modifying NCP Share Properties To modify a file share: 1. From the NAS server desktop, choose Start > Settings > Control Panel > Administrative Tools > Server Manager. 2. Choose FPNW > Shared Volumes. 3. Highlight the volume to modify. 4. Click Properties.
NetWare File System Management 196 NAS 4000s and 9000s Administration Guide
Cluster Administration 10 One important feature of the HP StorageWorks NAS server is that it can operate as a single node or as a cluster. This chapter discusses cluster installation and cluster management issues. Some of these topics are discussed or mentioned elsewhere in this guide. The discussion in this chapter is more detailed than other references and addresses the unique administration procedures for operating in a clustered environment.
Cluster Administration 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 115: NAS server cluster diagram Cluster Terms and Components This section provides brief definitions of clustering terms.
Cluster Administration Virtual Servers A virtual server is a cluster group that consists of a static IP Address resource and a Network Name resource. Several virtual servers can be created. By assigning ownership of the virtual servers to the different server nodes, the processing load on the NAS devices can be distributed between the nodes of a cluster. The creation of a virtual server allows resources dependant on the virtual server to fail over and fail back between the cluster nodes.
Cluster Administration Cluster Concepts Microsoft cluster concepts are rather straight forward when explained through a diagram. Figure 116 illustrates a typical cluster configuration with the corresponding storage elements. The diagram progresses from the physical disks to the file shares, showing the relationship between both the cluster elements and the physical devices underlying them. While the diagram only illustrates two nodes, the same concepts apply for multi node deployments.
Cluster Administration FS1 Cluster Node 1 5 Node 2 Cluster Group FS1Eng Cluster Resource : Disk E Cluster Resource : Network Name Fileserver1 Cluster Resource : File Share Eng1 E:\eng1 E:\eng1 E:\eng2 E:\eng3 4 3 Cluster Resource : IP Address 172.18.1.99 Basic Disk E: Cluster Resource : Network Name Fileserver2 Cluster Resource : File Share Mar4 G:\Mar4 Cluster Resource Physical Disk F Basic Disk F Raidsets 1-3 Cluster Resource : IP Address 172.18.1.
Cluster Administration Hierarchy of Cluster Resource Components The cluster components are referred to as resources and are placed together in groups. Groups are the basic unit of failover between nodes. Resources do not failover individually, rather they failover with the group in which they are contained. In Figure 116 it is depicted as follows: ■ Physical Disk resources are placed in a group and relate to the basic disk created through the WebUI.
Cluster Administration For example, if from a client a network share map F: was established and assigned to \\Node1\Eng1 instead of \\Fileserver1\Eng1, when Node1 fails and Node2 assumes ownership, the map will become invalid because the reference in the map is to \\Node1. If the map were created to the virtual name and Node1 were to fail, the map would still exist when the group associated with Eng1 failed over to Node2.
Cluster Administration In preparing for the cluster installation: ■ All software components listed in the SAN connection tool must be installed and the fiber cables attached to the HBA(s) before the cluster installation is started. ■ All shared disks, including the quorum disk, must be accessible from both nodes. When testing connectivity between server and LUN, only one server should be given access to the LUN at a time or the non-testing server should be powered off.
Cluster Administration Protocol Planning The NAS 4000s and 9000s both support many file sharing protocols, including sharing protocols for Windows, UNIX, Linux, Novell, Macintosh, Web, and FTP clients. However, not all of these protocols can take advantage of clustering. If a protocol does not support clustering, the share will not be available to the clients until the owner cluster node is brought back online. HP recommends placing cluster aware and non cluster aware protocols on different file shares.
Cluster Administration Preparing for Cluster Installation This section provides the steps necessary to cluster HP StorageWorks NAS servers. Before Beginning Installation Confirm that the following specifications have been met before proceeding: ■ The SAN connection tool must be completed and all the necessary software components for connecting to the desired storage must be installed before the configuration of cluster services.
Cluster Administration After cluster installation has been completed, run the cluster update tool located in the Cluster Installation Guide in the WebUI. The Cluster Installation Guide is located under the Cluster tab. This must be done after the cluster installation is complete. It is necessary to run this tool on all cluster nodes. Checklists for Cluster Server Installation These checklists assist in preparing for installation. Step-by-step instructions begin after the checklists.
Cluster Administration Cluster Installation During the installation process, nodes will be shut down and rebooted. These steps are necessary to guarantee that the data on disks that are attached to the shared storage bus is not lost or corrupted. This can happen when multiple nodes try to simultaneously write to the same disk that is not yet protected by the cluster software. Use Table 14 to determine which nodes and storage devices should be presented during each step.
Cluster Administration Configure the Private Network Adapter The following procedures are Best Practices provided by Microsoft and should be configured on the private network adapter.
Cluster Administration ■ Create a small partition [A minimum of 50 megabytes (MB) to be used as a quorum disk. HP recommends a quorum disk to be 500 MB.] ■ Dedicate a separate disk resource for a quorum disk. As the failure of the quorum disk would cause the entire cluster to fail, it is strongly recommended that the disk resource be a RAID 1 configuration. During the Cluster service installation, a drive letter must be provided for the quorum disk. HP recommends the drive letter Q for the quorum disk.
Cluster Administration Install Cluster Service Software Clustering is installed by default. It is necessary to configure the cluster by launching Cluster Administrator. Follow the steps in the next section to configure the cluster. It is possible to add seven additional cluster nodes for an eight node cluster. Refer to the associated Storage Array documentation to determine the number of cluster nodes that are supported by the specific array in use under Windows Storage Server 2003.
Cluster Administration The next step runs a pre-configuration analysis. This procedure analyzes and verifies the hardware and software configuration and identifies potential problems. A comprehensive and easy-to-read report will be created listing any potential configuration issues before the cluster is created. 1. Select the details tab to see a list of the items analyzed and any potential issues there may be with the cluster configuration. 2.
Cluster Administration 2. Ensure that the additional node has access to only the quorum LUN utilized as the cluster quorum disk. Caution: Presenting other LUNs to the non-clustered system could lead to data corruption. 3. Click Add New Node. 4. Enter the name of the node and specify the password for the cluster service account. Select OK to continue. Figure 119: Adding a new node 5. In the Add Nodes Wizard window, click Next. 6. Specify the domain and select Next. 7.
Cluster Administration 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 VLAN connection with latency of 500 milliseconds or less ensures that cluster consistency can be maintained.
Cluster Administration Creating and managing these resources and groups must be managed through Cluster Administrator, available from the Cluster tab of the WebUI. Complete online help for creating the various cluster objects is available in the Cluster Administrator tool. Cluster Group Overview A default cluster group is automatically created when the cluster is first created.
Cluster Administration Cluster Resource Overview Hardware and software components that are managed by the cluster service are called cluster resources. Resources represent individual system components. These resources are then organized into groups and managed as a group. Some resources are created automatically by the system and other resources must be set up manually.
Cluster Administration 4. Create the file share resources. In a clustered environment, file shares are created as a type of cluster resource. Creating cluster resources and file shares is documented later in this chapter. 5. Assign ownership of the file share resources to the resource groups. a. Divide ownership of the file share resource between the resource groups, which are in turn distributed between the virtual servers, for effective load balancing. b.
Cluster Administration ■ In a clustered deployment, if PCNFS password and group files are being used to provide user and group information, these files must be located on each node of the system. Example: If the password and group files are located at c:\maps on node 1, then they must also be at c:\maps on node 2. The contents of the password and group files must be the same on both nodes as well.
Cluster Administration Adding New Storage to a Cluster Present the new storage to one node in the cluster. This can be accomplished through selective storage presentation or through SAN switch zoning. Open the WebUI and navigate to the Disks tab. Select the Disks link under the disks tab. Select the disk which needs to be configured from the list of available disks and select Create New Volume. Follow the steps in the wizard to create the new volume.
Cluster Administration 4. Specify a name for the cluster resource and enter a description for the resource. 5. Select the Cluster group the physical disk will reside in. 6. Select Physical Disk as the resource type and select Next. 7. Select the Possible Owners and select Next. 8. Set the dependencies and select Next. Note: Physical disk resources usually do not have any dependencies set. 9. Specify the available disk resource and select Next. 10.
Cluster Administration Creating File Share Resources To create a file share resource: 1. Open the WebUI to the Cluster tab and select Cluster Resources. 2. Click Create. 3. Select Next to proceed with the wizard. 4. Specify the Share name, description, the cluster group the share will reside in and the resource type. The resource type should be File Share. Note: A file share resource must reside in the same cluster group as the physical disk resource it will reside on.
Cluster Administration 9. Review the configuration and click Finish to create the share. 10. After the resource is created it is necessary to bring it online. In the Cluster Resources page, select the resource and select Bring Online. 11. Click OK on the Bring a Resource Online page to bring the new file share resource online. Setting Permissions for a SMB File Share When a share resource is created via the WebUI and brought online, the default permission is set to: Everyone=Read-Only.
Cluster Administration Figure 125: Set resource permissions 7. Set the permissions, then click OK. Creating NFS Share Resources To create an NFS share resource: 1. Open the WebUI to the Cluster tab and select Cluster Resources. 2. Click Create. 3. Select Next to proceed with the wizard. 4. Specify the name, description, the cluster group the share will reside in and the resource type. The resource type should be NFS Share. 5. Click Next. 6. Select the possible owners and click Next to continue. 7.
Cluster Administration Setting Permissions for an NFS Share When a share resource is created via the WebUI and brought online, the default permission is set to: Everyone=Read-Only. To change the default permissions: 1. From the Cluster tab, click Advanced Cluster Management. 2. Log into Remote Desktop. 3. Click the group. 4. Right-click the resource, then click Properties. Figure 126: NFS Share Resource parameters 5. Click the Parameters tab. 6. Click Permissions.
Cluster Administration Figure 127: Set NFS Share resource permissions 7. Set the permissions, then click OK.
Cluster Administration Creating IP Address Resources 1. Open the WebUI to the Cluster tab and select Cluster Resources. 2. Click Create. 3. Select Next to proceed with the wizard. 4. Specify the name, description, the cluster group the resource will reside in and the resource type. The resource type should be IP Address. 5. Click Next. 6. Select the possible owners and click Next to continue. 7. Specify the dependencies and click Next to continue. 8.
Cluster Administration Creating Network Name Resources 1. Open the WebUI to the Cluster tab and select Cluster Resources. 2. Click Create. 3. Select Next to proceed with the wizard. 4. Specify the name, description, the cluster group the resource will reside in and the resource type. The resource type should be Network Name. 5. Click Next. 6. Select the possible owners and click Next to continue. 7. Specify the dependencies and click Next to continue. Figure 129: Network Name Parameters 8.
Cluster Administration Basic Cluster Administration Procedures ■ Failing over and failing back ■ Restarting one cluster node ■ Shutting down one cluster node ■ Powering down all cluster nodes ■ Powering up all cluster nodes Failing Over and Failing Back As previously mentioned, when a node goes offline, all of the resources dependent on that node are automatically failed over to another node.
Cluster Administration Shutting Down One Cluster Node Caution: Shutting down a cluster node must be done only after confirming that the other node(s) in the cluster are functioning normally. Adequate warning should be given to users connected to resources of the node being shutdown. Shutting down a cluster node causes file shares served by that node to fail over to the other node(s).
Cluster Administration Powering Up the Cluster The power up process for the NAS cluster is more complex than it is for a single node because extra care must be taken with the storage subsystem. The sequence of the power up steps is critical. Improper power up procedures can cause corruption and loss of data. Caution: Do not power up the cluster nodes without first powering up the storage subsystem, and verifying it is operating normally.
Cluster Administration Shadow Copies in a Clustered Environment The creation and management of clustered Shadow Copy resources in a cluster should be performed using the WebUIs by selecting Disk, Shadow Copy or from the file system by right-clicking on the volume and selecting Shadow Copy. Assuming the underlying disk is part of a cluster, both methods will generate a cluster resource on the cluster that is viewable from Cluster Administrator and the Cluster Resource tab of the WebUI.
Cluster Administration g. Select the folder to place the spooler temporary contents and click Finish. h. Close Cluster Administrator. 6. To connect to the Virtual Server Name or IP address created in the steps above: a. Select Start > Run > then type: \\"virtual_server_name or ip address" from the local menu b. A session will open to the virtual server. 7. To add a printer to the virtual server: a. Double-click the printers and faxes icon. b. Right-click the new screen and select add printer.
Remote Access Methods and Monitoring 11 The HP StorageWorks NAS server comes from the factory with full remote manageability.
Remote Access Methods and Monitoring Web Based User Interface The NAS server includes a Web based user interface (WebUI) for the administrator to remotely manage the machine. Of all of the remote access methods, the WebUI is the most intuitive and easiest to learn and use. The WebUI permits complete system management, including system configuration, user and group management, shares management, Microsoft Services for NFS, and storage management. To access the WebUI: 1. Launch a Web browser. 2.
Remote Access Methods and Monitoring Features The Integrated Lights-Out port provides the following features: Note: The remote client console must have a direct browser connection to the Integrated Lights-Out port without passing through a proxy server or firewall. ■ Hardware based graphical remote console access ■ Remote restart ■ Server failure alerting ■ Integration with Insight Manager ■ Local Area Network (LAN) access through onboard NIC ■ Browser support for Internet Explorer 5.
Remote Access Methods and Monitoring Manage Alerts Feature The Manage Alerts feature allows the user to: ■ Select alert types received ■ Generate a global test alert ■ Generate an individual test alert ■ Clear pending alerts ■ Enable alerts Refer to the Integrated Lights-Out Port User Guide for more information about the Integrated Lights-Out port features and functionality.
Remote Access Methods and Monitoring Using the Integrated Lights-Out Port to Access the NAS Server Using the Web interface of a client machine is the recommended procedure for remotely accessing the server: 1. In the URL field of the Web browser, enter the IP address of the Integrated Lights-Out port. Note: The iLO port can also be accessed from the HP Utilities tab of the WebUI by clicking the remote management link. 2.
Remote Access Methods and Monitoring Telnet Server Telnet Server is a utility that lets users connect to machines, log on, and obtain a command prompt remotely. Telnet Server is preinstalled on the NAS server, but must be activated before use. Caution: For security reasons, the Telnet Server service must be restarted each time the server is restarted. Enabling Telnet Server Telnet Server can be enabled in two ways.
Index A backup mappings 183 with shadow copies 110 basic disk 61 C cache file, shadow copies 99 CIFS administration 112 share support 135 client groups adding NFS 174 deleting NFS 174 editing NFS 175 managing NFS 173 cluster NAS 4000s and 9000s Administration Guide Index B Index access rights, managing 217 ACL defined 134 translating 177 ADG (Advanced Data Guarding) 59 alerts, e-mail, setting up 36 array controller purpose 54 arrays defined 53 audience 14 Authentication software, installing 162 autho
Index setting up user account 209 shared disk requirements 207 terms and components 198 configuring private network adapter 209 configuring shared disks 210 connectivity, verifying 209 conventions document 15 equipment symbols 16 text symbols 15 creating NFS file shares 164 configuring 42 configuring properties 44 configuring TCP/IP 45 renaming the connection 44 setting up 38 showing connection icon 45 troubleshooting 48 events, Services for NFS, logging 159 explicit group mapping 181 explicit mappings 17
Index managing shares for 126 modifying properties 124 navigating to 122 FPNW accessing 190 described 187 installing 188 G getting help 17 group names examples 112 managing 112 group, cluster cluster group 202 groups adding from a domain 120 adding local users 119 adding to permissions list 128 local, adding 118 local, deleting 118 local, managing 117 local, modifying properties 119 properties, general tab 119 properties, members tab 119 removing local users 120 H hard drives best practices 61 online spa
Index presenting to cluster node 213 M management, storage 51 managing system storage 49 mappings backup and restore 183 best practices 177 creating 178 data stored 178 explicit 176, 180 NFS 176 simple 176, 179 squashed 177 mount points creating 62 not supported with NFS 62 mounted drives and shadow copies 97 N NAS servers defined 19 desktop 29 restarting 33 shutting down 33 supported fault tolerance methods 56 using iLO to access 237 utilities 19 NCP creating new share 193, 195 NetWare adding local user
Index adding users and groups 128 removing users and groups 128 modifying 128 resetting 130 physical disk resources 202, 219 physical storage best practices 61 planning cluster 203 network 204 protocol 205 storage 203 prerequisites 14 printer spooler, creating in a cluster 231 private network adapter, configuring 209 protocols NFS properties settings 169 non cluster aware 218 parameter settings 141 planning 205 planning for compatibility 135 supported 26, 141 public network adapter, configuring configuring
Index completing 38 e-mail alerts 36 Ethernet NIC teams 38 shadow copies accessing 98 backups 110 cache file 99 client access 106 creating 101 defragmentation 97 deleting schedule 102 described 93 disabling 104 enabling 101 file or folder recovery 108 in a cluster 231 managing 98 mounted drives 97 NAS Desktop 105 on NFS shares 107 on SMB shares 106 planning 94 properties, viewing 102 scheduling 102 uses 93 viewing list 101 shared disk requirements 207 shared disks, configuring 210 shares administrative 135
Index permissions 164 sharing 139 user ID 158 user access, authenticating 157 user account, setting up 209 user credentials 158 user interfaces 27 user permissions for NFS 158 users adding to permission list 128 local adding 114 deleting 115 managing 113 modifying properties 116 names, managing 112 NetWare adding 191 enabling 192 V verifying connectivity 209 disk access 210 domain membership 209 name resolution 209 NAS 4000s and 9000s Administration Guide virtual server 202 virtual server, defined 199 v
Index 246 NAS 4000s and 9000s Administration Guide
