HP StorageWorks X1800sb and X3800sb Network Storage Blade user guide Part number: 572092-001 First edition: June 2009
Legal and notice information © Copyright 1999, 2009 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents About this guide ................................................................................. 11 Intended audience .................................................................................................................... Related documentation .............................................................................................................. Document conventions and symbols .............................................................................................
Single Instance Storage ....................................................................................................... File Server Resource Manager .............................................................................................. Windows SharePoint Services .............................................................................................. File services management ..........................................................................................................
Other Windows disk and data management tools ......................................................................... Additional information and references for file services .................................................................... Backup ............................................................................................................................. HP StorageWorks Library and Tape Tools .............................................................................. Antivirus .......
Creating physical disk resources .................................................................................... Creating file share resources ......................................................................................... Creating NFS share resources ....................................................................................... Shadow copies in a cluster .................................................................................................. Extend a LUN in a cluster .....
Taiwan battery recycle statement .......................................................................................... Laser compliance notices ........................................................................................................... English laser notice ............................................................................................................. Dutch laser notice .........................................................................................................
Figures 1 Storage management process example ...................................................................... 20 2 Configuring arrays from physical drives ...................................................................... 21 3 RAID 0 (data striping) (S1-S4) of data blocks (B1-B12) ................................................ 21 4 Two arrays (A1, A2) and five logical drives (L1 through L5) spread over five physical drives .........................................................................
Tables 1 Document conventions ............................................................................................. 11 2 Summary of RAID methods ....................................................................................... 22 3 Tasks and utilities needed for storage system configuration ........................................... 28 4 Sharing protocol cluster support ................................................................................
About this guide This guide provides information about the following HP StorageWorks Network Storage Systems: • HP StorageWorks X1800sb Network Storage Blade • HP StorageWorks X3800sb Network Storage Gateway Blade The HP StorageWorks X1800sb Network Storage Blade and HP StorageWorks X3800sb Network Storage Gateway Blade are based on HP ProLiant BL460c G6 Server Blade hardware.
Convention Element • Keys that are pressed • Text typed into a GUI element, such as a box Bold text • GUI elements that are clicked or selected, such as menu and list items, buttons, tabs, and check boxes Italic text Text emphasis • File and directory names • System output Monospace text • Code • Commands, their arguments, and argument values Monospace, italic Monospace, bold text text • Code variables • Command variables Emphasized monospace text WARNING! Indicates that failure to follow direc
WARNING! To reduce the risk of personal injury or damage to equipment: • Extend leveling jacks to the floor. • Ensure that the full weight of the rack rests on the leveling jacks. • Install stabilizing feet on the rack. • In multiple-rack installations, fasten racks together securely. • Extend only one rack component at a time. Racks can become unstable if more than one component is extended. HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
• • • • http://www.hp.com/go/storage http://www.hp.com/service_locator http://www.hp.com/support/manuals http://www.hp.com/support/downloads Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to storagedocsFeedback@hp.com. All submissions become the property of HP.
1 Administration tools HP StorageWorks X1000 and X3000 Network Storage Systems include several administration tools to simplify storage system management tasks. HP StorageWorks X1000 Network Storage Systems include the HP X1000 Automated Storage Manager (ASM) in addition to HP storage utilities and Microsoft® Windows® Storage Server 2008 administration tools.
Remote Desktop for Administration does not require the purchase of special licenses for client computers that access the server. It is not necessary to install Terminal Server Licensing when using Remote Desktop for Administration. You can use Remote Desktop for Administration to log on to the server remotely with any of the following features: • Remote Desktop Connection • Remote Web Administration • Windows Server Remote Administration Applet For more information, see the Windows Storage Server 2008 Help.
Mapping Setup Wizard. After completing the initial Microsoft Services for NFS configuration, you can use the Microsoft Services for NFS console for ongoing maintenance and administration. If you are using Windows Storage Server 2008 in an environment that does not include an Active Directory directory service domain, you can install Active Directory Application Mode (ADAM) on your storage system to provide user name mapping for NFS.
Print Management Print Management is an MMC snap-in that you can use to view and manage printers and print servers in your organization. You can use Print Management from any computer running Windows Storage Server 2008, and you can manage all network printers on print servers running Windows 2000 Server, Windows Server 2003, Windows Storage Server 2003, Windows Storage Server 2003 R2, or Windows Storage Server 2008.
2 Storage management overview This chapter provides an overview of some of the components that make up the storage structure of the storage system. Storage management elements Storage is divided into four major divisions: • • • • Physical storage elements Logical storage elements File system elements File sharing elements Each of these elements is composed of the previous level's elements. Storage management example Figure 1 depicts many of the storage elements that one would find on a storage device.
Figure 1 Storage management process example Physical storage elements The lowest level of storage management occurs at the physical drive level. Minimally, choosing the best disk carving strategy includes the following policies: • Analyze current corporate and departmental structure. • Analyze the current file server structure and environment. • Plan properly to ensure the best configuration and use of storage. • Determine the desired priority of fault tolerance, performance, and storage capacity.
• Include the appropriate number of physical drives in the arrays to create logical storage elements of desired sizes. Arrays See Figure 2. With an array controller installed in the system, the capacity of several physical drives (P1–P3) can be logically combined into one or more logical units (L1) called arrays. When this is done, the read/write heads of all the constituent physical drives are active simultaneously, dramatically reducing the overall time required for data transfer.
Fault tolerance Drive failure, although rare, is potentially catastrophic. For example, using simple striping as shown in Figure 3, failure of any hard drive leads to failure of all logical drives in the same array, and hence to data loss. To protect against data loss from hard drive failure, storage systems should be configured with fault tolerance. HP recommends adhering to RAID 5 configurations.
It is important to note that a LUN may span all physical drives within a storage controller subsystem, but cannot span multiple storage controller subsystems. Figure 4 Two arrays (A1, A2) and five logical drives (L1 through L5) spread over five physical drives NOTE: This type of configuration may not apply to all storage systems and serves only as an example. Through the use of basic disks, you can create primary partitions or extended partitions. Partitions can only encompass one LUN.
is important. The same performance characteristics on numbers of reads and writes apply when using fault-tolerant configurations, as is the case with controller-based RAID. These volumes can also be assigned drive letters or be mounted as mount points off existing drive letters. The administrator should carefully consider how the volumes will be carved up and what groups or applications will be using them.
Using storage elements The last step in creating the element is determining its drive letter or mount point and formatting the element. Each element created can exist as a drive letter, assuming one is available, and/or as mount points on an existing folder or drive letter. Either method is supported. However, mount points cannot be used for shares that will be shared using Microsoft Services for Unix.
Management Agents Management Agents provide the information to enable fault, performance, and configuration management. The agents allow easy manageability of the server through HP SIM software, and thirdparty SNMP management platforms. Management Agents are installed with every SmartStart assisted installation or can be installed through the HP PSP. The Systems Management homepage provides status and direct access to in-depth subsystem information by accessing data reported through the Management Agents.
3 File server management This chapter begins by identifying file services in Windows Storage Server 2008. The remainder of the chapter describes the many tasks and utilities that play a role in file server management. File services features in Windows Storage Server 2008 Storage Manager for SANs The Storage Manager for SANs (also called Simple SAN) snap-in enables you to create and manage the LUNs that are used to allocate space on storage arrays.
File services management Information about the storage system in a SAN environment is provided in the HP StorageWorks SAN Manuals page located on the HP web site at www.hp.com/go/SDGManuals. Configuring data storage HP StorageWorks X1000 and X3000 Network Storage Systems are configured only for the operating system. The administrator must configure data storage for the storage system. Configuring additional data storage involves creating arrays, logical disks, and volumes.
Array management utilities Storage devices for RAID arrays and LUNs are created and managed using the array management utilities mentioned previously. For HP Smart Arrays use the ACU. NOTE: The ACU is used to configure and manage array-based storage. Software RAID-based storage systems use Microsoft Disk Manager to manage storage. You need administrator or root privileges to run the ACU.
• Extending and expanding arrays and logical drives is supported. The HP Array Configuration Utility User Guide is available for download at http://www.hp.com/ support/manuals. Disk Management utility The Disk Management tool is a system utility for managing hard disks and the volumes, or partitions, that they contain. Disk Management is used to initialize disks, create volumes, format volumes with the FAT, FAT32, or NTFS file systems, and create fault-tolerant disk systems.
Scheduling defragmentation Defragmentation is the process of analyzing local volumes and consolidating fragmented files and folders so that each occupies a single, contiguous space on the volume. This improves file system performance. Because defragmentation consolidates files and folders, it also consolidates the free space on a volume. This reduces the likelihood that new files will be fragmented. Defragmentation for a volume can be scheduled to occur automatically at convenient times.
per-user basis. It is also possible to specify whether or not to log an event when users exceed either their quota warning level or their quota limit. When enabling disk quotas for a volume, volume usage is automatically tracked from that point forward, but existing volume users have no disk quotas applied to them. Apply disk quotas to existing volume users by adding new quota entries on the Quota Entries page.
Extending storage using Windows Storage Utilities Volume extension grows the storage space of a logical drive. During this process, the administrator adds new storage space to an existing logical drive on the same array, usually after the array has been expanded. An administrator may have gained this new storage space by either expansion or by deleting another logical drive on the same array. Unlike drive expansion, the operating system must be aware of changes to the logical drive size.
Expand logical drive This option in the ACU increases the storage capacity of a logical drive by adding unused space on an array to the logical drive on the same array. The unused space is obtained either by expanding an array or by deleting another logical drive on the same array.
• How frequently will shadow copies be made? Identifying the volume Shadow copies are taken for a complete volume, but not for a specific directory. Shadow copies work best when the server stores user files, such as documents, spreadsheets, presentations, graphics, or database files. NOTE: Shadow copies should not be used to provide access to previous versions of application or e-mail databases.
NOTE: Regardless of the volume space that is allocated for shadow copies, there is a maximum of 64 shadow copies for any volume. When the 65th shadow copy is taken, the oldest shadow copy is purged. The minimum amount of storage space that can be specified is 350 megabytes (MB). The default storage size is 10 percent of the source volume (the volume being copied).
Shadow copies and drive defragmentation When running Disk Defragmenter on a volume with shadow copies activated, all or some of the shadow copies may be lost, starting with the oldest shadow copies. If defragmenting volumes on which shadow copies are enabled, use a cluster (or allocation unit) size of 16 KB or larger. Using this allocation unit size reduces the number of copy outs occurring on the snapshot.
Figure 5 System administrator view of Shadow Copies for Shared Folders The shadow copy cache file The default shadow copy settings allocate 10 percent of the source volume being copied (with a minimum of 350 MB), and store the shadow copies on the same volume as the original volume. (See Figure 6). The cache file is located in a hidden protected directory titled “System Volume Information” off of the root of each volume for which shadow copy is enabled.
Figure 7 Shadow copies stored on a separate volume The main advantage to storing shadow copies on a separate volume is ease of management and performance. Shadow copies on a source volume must be continually monitored and can consume space designated for file sharing. Setting the limit too high takes up valuable storage space. Setting the limit too low can cause shadow copies to be purged too soon, or not created at all.
NOTE: After the first shadow copy is created, it cannot be relocated. Relocate the cache file by altering the cache file location under Properties prior to enabling shadow copy. See “Viewing shadow copy properties” on page 40. Viewing a list of shadow copies To view a list of shadow copies on a volume: 1. Access Disk Management. 2. Select the volume or logical drive, then right-click on it. 3. Select Properties. 4. Select Shadow Copies tab.
CAUTION: Use caution when reducing the size limit for all shadow copies. When the size is set to less than the total size currently used for all shadow copies, enough shadow copies are deleted to reduce the total size to the new limit. A shadow copy cannot be recovered after it has been deleted. Redirecting shadow copies to an alternate volume IMPORTANT: Shadow copies must be initially disabled on the volume before redirecting to an alternate volume.
Managing shadow copies from the storage system desktop To access shadow copies from the storage system desktop: The storage system desktop can be accessed by using Remote Desktop to manage shadow copies. 1. On the storage system desktop, double-click My Computer. 2. Right-click the volume name, and select Properties. 3. Click the Shadow Copies tab. See Figure 8.
NOTE: Shadow Copies for Shared Folders clients are not available for HTTP, FTP, AppleTalk, or NetWare shares. Consequently, users of these protocols cannot use Shadow Copies for Shared Folders to independently retrieve previous versions of their files. However, administrators can take advantage of Shadow Copies for Shared Folders to restore files for these users.
Figure 9 Client GUI When users view a network folder hosted on the storage system for which shadow copies are enabled, old versions (prior to the snapshot) of a file or directory are available. Viewing the properties of the file or folder presents users with the folder or file history—a list of read-only, point-in-time copies of the file or folder contents that users can then open and explore like any other file or folder.
Access to NFS shadow copy pseudo-subdirectories is governed by normal access-control mechanisms using the permissions stored in the file system. Users can access only those shadow copies to which they have read access at the time the shadow copy is taken. To prevent users from modifying shadow copies, all pseudo-subdirectories are marked read-only, regardless of the user's ownership or access rights, or the permissions set on the original files.
Figure 10 Recovering a deleted file or folder Recovering an overwritten or corrupted file Recovering an overwritten or corrupted file is easier than recovering a deleted file because the file itself can be right-clicked instead of the folder. To recover an overwritten or corrupted file: 1. Right-click the overwritten or corrupted file, and then click Properties. 2. Click Previous Versions. 3. To view the old version, click View. To copy the old version to another location, click Copy...
Backup and shadow copies Shadow copies are only available on the network via the client application, and only at a file or folder level as opposed to the entire volume. Hence, the standard backup associated with a volume backup will not work to back up the previous versions of the file system. To answer this particular issue, shadow copies are available for backup in two situations.
NOTE: Select servers can be deployed in a clustered or non-clustered configuration. This section discusses share setup for a non-clustered deployment. Folder management Volumes and folders on any system are used to organize data. Regardless of system size, systematic structuring and naming conventions of volumes and folders eases the administrative burden.
2. Click Properties, and then click the Security tab. Figure 11 Properties dialog box, Security tab Several options are available on the Security tab: • To add users and groups to the permissions list, click Add. Follow the dialog box instructions. • To remove users and groups from the permissions list, highlight the desired user or group, and then click Remove. • The center section of the Security tab lists permission levels.
3. To modify ownership of files, or to modify individual file access level permissions, click Advanced. Figure 12 illustrates the properties available on the Advanced Security Settings dialog box. Figure 12 Advanced Security settings dialog box, Permissions tab Other functionality available in the Advanced Security Settings dialog box is illustrated in Figure 12 and includes: • Add a new user or group—Click Add, and then follow the dialog box instructions. • Remove a user or group— Click Remove.
4. Enable or disable permissions by selecting the Allow box to enable permission or the Deny box to disable permission. If neither box is selected, permission is automatically disabled. Figure 13 illustrates the Edit screen and some of the permissions. Figure 13 User or group Permission Entry dialog box Another area of the Advanced Security Settings is the Auditing tab. Auditing allows you to set rules for the auditing of access, or attempted access, to files or folders.
Figure 14 Advanced Security Settings dialog box, Auditing tab 5. Click Add to display the Select User or Group dialog box. Figure 15 Select User or Group dialog box NOTE: Click Advanced to search for users or groups. 6. 52 Select the user or group.
7. Click OK. The Auditing Entry dialog box is displayed. Figure 16 Auditing Entry dialog box for folder name NTFS Test 8. Select the desired Successful and Failed audits for the user or group. 9. Click OK. NOTE: Auditing must be enabled to configure this information. Use the local Computer Policy Editor to configure the audit policy on the storage system. The Owner tab allows taking ownership of files.
Figure 17 Advanced Security Settings dialog box, Owner tab The current owner of the file or folder is listed at the top of the screen. To take ownership: 1. Click the appropriate user or group in the Change owner to list. 2. If it is also necessary to take ownership of subfolders and files, enable the Replace owner on subcontainers and objects box. 3. Click OK. Share management There are several ways to set up and manage shares.
The content of shares should be carefully chosen to avoid two common pitfalls: either having too many shares of a very specific nature, or of having very few shares of a generic nature. For example, shares for general use are easier to set up in the beginning, but can cause problems later. Frequently, a better approach is to create separate shares with a specific purpose or group of users in mind. However, creating too many shares also has its drawbacks.
• Standard shares are shares that do not end in a $ character. Standard shares are listed whenever a CIFS client browses for available shares on a CIFS server. The storage system supports both administrative and standard CIFS shares. To create an administrative share, end the share name with the $ character when setting up the share. Do not type a $ character at the end of the share name when creating a standard share. Managing shares Shares can be managed using Server Manager.
File screening management On the File Screening Management node of the File Server Resource Manager snap-in, you can perform the following tasks: • Create file screens to control the types of files that users can save and to send notifications when users attempt to save blocked files. • Define file screening templates that can be easily applied to new volumes or folders and that can be used across an organization. • Create file screening exceptions that extend the flexibility of the file screening rules.
For more information, and to download the utility, see the StorageWorks L&TT web site at http:// h18006.www1.hp.com/products/storageworks/ltt. Antivirus The server should be secured by installing the appropriate antivirus software.
4 Cluster administration HP StorageWorks X3000 Network Storage Systems support clustering; HP StorageWorks X1000 Network Storage Systems do not. One important feature of HP StorageWorks X3000 Network Storage System models is that they can operate as a single node or as a cluster. This chapter discusses cluster installation and cluster management issues. Cluster overview Up to eight server nodes can be connected to each other and deployed as a no single point of failure (NSPOF) cluster.
Figure 18 Storage system cluster diagram Cluster terms and components Nodes The most basic parts of a cluster are the servers, referred to as nodes. A server node is any individual server in a cluster, or a member of the cluster. Resources Hardware and software components that are managed by the cluster service are called cluster resources. Cluster resources have three defining characteristics: • They can be brought online and taken offline. • They can be managed in a cluster.
• • • • CIFS file share resources NFS file share resources FTP file share resources iSCSI resources Cluster groups Cluster resources are placed together in cluster groups. Groups are the basic unit of failover between nodes. Resources do not fail over individually; they fail over with the group in which they are contained. Virtual servers A virtual server is a cluster group that consists of a static IP Address resource and a Network Name resource. Several virtual servers can be created.
• Storing the most current version of the cluster database • Guaranteeing that only one set of active communicating nodes is allowed to operate as a cluster Cluster concepts Figure 19 illustrates a typical cluster configuration with the corresponding storage elements. The diagram progresses from the physical disks to the file shares, showing the relationship between both the cluster elements and the physical devices underlying them.
3. Physical Disk resources are created for each basic disk inside Cluster Administrator. 4. Directories and folders are created on assigned drives. 5. Cluster components (virtual servers, file shares) are created, organized in groups, and placed within the folders using Cluster Administrator exclusively. Hierarchy of cluster resource components Figure 19 depicts the cluster resource hierarchy as follows: • Physical Disk resources are placed in a cluster group and relate to the basic disk.
• Storage planning • Network planning • Protocol planning Storage planning For clustering, a basic disk must be designated for the cluster and configured as the Quorum disk. Additional basic disks are presented to each cluster node for data storage as physical disk resources. The physical disk resources are required for the basic disks to successfully work in a cluster environment, protecting it from simultaneous access from each node.
• The private cluster interconnect or “heartbeat” crossover cable connects to one of the network ports on each cluster node. In more than two node deployments, a private VLAN on a switch or hub is required for the cluster interconnect. • The public client network subnet connects to the remaining network ports on each cluster node. The cluster node names and virtual server names have IP addresses residing on these subnets.
NOTE: AppleTalk is not supported on clustered disk resources. AppleTalk requires local memory for volume indexing. On failover events, the memory map is lost and data corruption can occur. Preparing for cluster installation This section provides the steps necessary to cluster HP StorageWorks X3000 Network Storage Systems. Before beginning installation Confirm that the following specifications have been met before proceeding: • The Quorum disk has been created from shared storage and is at least 50 MB.
Shared disk requirements NOTE: Do not allow more than one node access the shared storage devices at the same time until Cluster service is installed on at least one node and that node is online. This can be accomplished through selective storage presentation, SAN zoning, or having only one node online at all times. • All shared disks, including the Quorum disk, must be accessible from all nodes.
Setting up networks Verify that all network connections are correct, with private network adapters connected to other private network adapters only, and public network adapters connected to the public network. Configuring the private network adapter The following procedures are best practices provided by Microsoft and should be configured on the private network adapter. • On the General tab of the private network adapter, ensure that only TCP/IP is selected.
• Dedicate a separate disk resource for a Quorum disk. Because the failure of the Quorum disk would cause the entire cluster to fail, HP strongly recommends that the disk resource be a RAID 1 configuration. • Create a partition with a minimum of 50 megabytes (MB) to be used as a Quorum disk. HP recommends a Quorum disk be 500 MB. HP recommends assigning the drive letter Q for the Quorum disk. It is also helpful to label the volume Quorum.
• Use of DHCP addresses for network connections. All Network adapters must be configured with static IP addresses in a cluster configuration. • File Services for Macintosh and Service for NetWare are not supported in a cluster configuration. • Dynamic Disks are not supported in a cluster configuration. • Errors appear on a network adapter that is not configured or does not have an active link. If the network adapter is not going to be used it should be disabled.
When creating groups, the administrator's first priority is to gain an understanding of how to manage the groups and their resources. Administrators may choose to create a resource group and a virtual server for each node that will contain all resources owned by that node, or the administrator may choose to create a resource group and virtual server for each physical disk resource.
2. For NFS environments, configure the NFS server. NFS specific procedures include entering audit and file lock information as well as setting up client groups and user name mappings. These procedures are not unique to a clustered deployment and are detailed in the Microsoft Services for NFS section within the “Other network file and print services” chapter. Changes to NFS setup information are automatically replicated to all nodes in a cluster. 3. Create the file share resources. 4.
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. These password and group files on each server node must be updated periodically to maintain consistency and prevent users or groups from being inadvertently squashed.
NOTE: • A file share resource must reside in the same cluster group as the physical disk resource it will reside on. • The physical disk resource specified in this step must reside in the same cluster group as specified in the beginning of this wizard. Creating NFS share resources To create an NFS share resource, see “MSNFS administration on a server cluster” on page 74. Shadow copies in a cluster It is recommended that the location of the cache file be placed on a separate disk from the original data.
• Configuring User Name Mapping on a server cluster For further details, see the online help for Microsoft Services for Network File System. Best practices for running Server for NFS in a server cluster • • • • • • • • • • • • • Stop Server for NFS before stopping the server cluster. Ensure share availability when a node fails. Use the appropriate tool to manage Network File System (NFS) share cluster resources. Avoid conflicting share names. Ensure the availability of audit logs.
6. To add a printer to the virtual server: a. b. c. d. e. f. g. h. i. j. k. l. Double-click the printers and faxes icon. Right-click the new screen, and then click add printer. A wizard starts. Click create a new port, and then click Next. Enter the IP address of the network printer. Update the Port Name if desired, click Next, and then click Finish. Select the appropriate driver, and then click Next. If presented with a dialog to replace the driver present, click keep the driver, and then click Next.
Restarting one cluster node CAUTION: Restarting a cluster node should 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 restarted. Attached connections can be viewed through Server Manager on the storage system Desktop using Terminal Services. From Server Manager, select File Sharing > Shared Folders > Sessions.
Powering up the cluster The power up process for the storage system 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.
5 Troubleshooting, servicing, and maintenance Troubleshooting the storage system The “Support and troubleshooting” task at the HP Support & Drivers web site (http://www.hp.com/ go/support) can be used to troubleshoot problems with the storage system.
• CCAT (Computer Crash Analysis Tool) • SEA (System Event Analyzer) If you have a warranty or service contract with HP you are entitled to these tools free of charge. You must, however, upgrade the tools at least once a year because the software expires after one year. For more information about WEBES, see http://h18023.www1.hp.com/support/svctools/webes/. To install WEBES on your storage system, run the setup executable located in the C:\hpnas\Components\WEBES folder.
6 System recovery This chapter describes how to use the System Recovery DVD that is provided with your storage system. The System Recovery DVD The HP StorageWorks Storage System Recovery DVD that is provided with your storage system allows you to install an image or recover from a catastrophic failure. At any later time, you may boot from the DVD and restore the server to the factory condition. This allows you to recover the system if all other means to boot the server fail.
4. Select the appropriate drive letter, then click OK. 5. Click Yes to confirm the drive letter change. 6. Click Yes to continue. If the old drive letter needs to be re-used, reboot the server after clicking Yes.
A Regulatory compliance notices This section contains regulatory notices for the HP StorageWorks family of products. Regulatory compliance identification numbers For the purpose of regulatory compliance certifications and identification, this product has been assigned a unique regulatory model number. The regulatory model number can be found on the product nameplate label, along with all required approval markings and information.
of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at personal expense. Class B equipment This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation.
Class B equipment This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la class B respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. European Union notice Products bearing the CE marking comply with the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of the European Community.
Korean notices Class A equipment Class B equipment Taiwanese notices BSMI Class A notice Taiwan battery recycle statement Recovery mark: • Four-in-one recycling symbol 86 Regulatory compliance notices Recovery text: • “Please recycle waste batteries”
Laser compliance notices English laser notice This device may contain a laser that is classified as a Class 1 Laser Product in accordance with U.S. FDA regulations and the IEC 60825-1. The product does not emit hazardous laser radiation. WARNING! Use of controls or adjustments or performance of procedures other than those specified herein or in the laser product's installation guide may result in hazardous radiation exposure.
French laser notice German laser notice Italian laser notice 88 Regulatory compliance notices
Japanese laser notice Spanish laser notice Recycling notices English notice X1800sb and X3800sb Network Storage Blade 89
Bulgarian notice Czech notice Danish notice Dutch notice 90 Regulatory compliance notices
Estonian notice Finnish notice French notice German notice X1800sb and X3800sb Network Storage Blade 91
Greek notice Hungarian notice Italian notice Latvian notice 92 Regulatory compliance notices
Lithuanian notice Polish notice Portuguese notice Romanian notice X1800sb and X3800sb Network Storage Blade 93
Slovak notice Spanish notice Swedish notice Turkish notice Türkiye Cumhuriyeti: EEE Yönetmeli ine Uygundur 94 Regulatory compliance notices
Battery replacement notices Dutch battery notice X1800sb and X3800sb Network Storage Blade 95
French battery notice German battery notice 96 Regulatory compliance notices
Italian battery notice Japanese battery notice X1800sb and X3800sb Network Storage Blade 97
Spanish battery notice 98 Regulatory compliance notices
Index A access rights, managing, 72 ACL, defining, 55 Array Configuration Utility, 29 array controller, purpose, 21 arrays, defined, 21 audience, 11 B backup, with shadow copies, 47 basic disks, 23 basic disks, 23, 24 battery replacement notices, 95 C cache file, shadow copies, 38 Canadian notice, 84 CIFS, share support, 56 cluster adding new storage, 73 analysis, 69 concepts, 62 concepts, diagram, 62 diagram, 60 dual data paths, 66 geographically dispersed, 70 group, 70 groups, node-based, 71 installati
Disk Management extending volumes, 33 document conventions, 11 related documentation, 11 documentation HP website, 11 providing feedback, 14 domain membership, verifying, 68 dual data paths, 66 dynamic disks clustering, 24 dynamic disks spanning multiple LUNs, 23 H E Japanese notices, 85 European Union notice, 85 expanding storage Array Configuration Utility, 33 Command View EVA, 33 extending volumes Disk Management, 33 F failover automatic, 76 defined, 61 resources, 61 fault tolerance, 22 Federal Comm
P partitions extended, 23 primary, 23 permissions file level, 48 list adding users and groups, 49 removing users and groups, 49 modifying, 50 resetting, 50 physical disk resources, 63, 73 physical storage elements, 20 planning network, 64 protocol, 65 storage, 64 printer spooler, creating in a cluster, 75 private network adapter, configuring, 68 protocols non cluster aware, 73 planning, 65 public network adapter, configuring, 68 Q Quorum disk defined, 61 recommendations, 68 quota management, 56 R rack sta
U user account, setting up, 68 users adding to permission list, 49 V verifying connectivity, 68 disk access, 69 domain membership, 68 name resolution, 68 virtual server, defined, 61 Volume Shadow Copy Service, 34 volumes planning, 23 vssadmin tool, 37 W warning rack stability, 12 WEBES (Web Based Enterprise Services, 79 websites customer self repair, 13 HP , 13 HP Subscriber's Choice for Business, 13 product manuals, 11 102 Index
