HP StorageWorks X3000 G2 Network Storage System User Guide SWX image version 2.00.
Legal and notice information © Copyright 2010, 2010 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 1 Installing and configuring the storage system ....................................... 13 Setup overview ......................................................................................................................... Check kit contents .............................................................................................................. Determine an access method ...............................................................................................
Storage management elements ................................................................................................... Storage management example ............................................................................................. Physical storage elements .................................................................................................... Arrays ........................................................................................................................
Redirecting shadow copies to an alternate volume ........................................................... Disabling shadow copies .............................................................................................. Managing shadow copies from the storage system desktop ..................................................... Shadow Copies for Shared Folders ....................................................................................... SMB shadow copies ....................................
Configuring the private network adapter ......................................................................... 97 Configuring the public network adapter .......................................................................... 98 Renaming the local area connection icons ...................................................................... 98 Verifying connectivity and name resolution ...................................................................... 98 Verifying domain membership ..................
Create a System Recovery USB Flash Drive .......................................................................... 114 Use the USB Flash Drive for System Recovery ....................................................................... 115 Managing disks after a restoration ............................................................................................ 116 9 Support and other resources ............................................................ 117 Contacting HP ..............................
Greek recycling notice ...................................................................................................... Hungarian recycling notice ................................................................................................ Italian recycling notice ...................................................................................................... Latvian recycling notice .....................................................................................................
Figures 1 HP X3400 G2 front panel components ...................................................................... 21 2 HP X3400 G2 front panel LEDs ................................................................................ 22 3 HP X3400 G2 rear panel components ....................................................................... 22 4 HP X3400 G2 rear panel LEDs ................................................................................. 23 5 HP X3800 G2 front panel components ...............
32 Client GUI ............................................................................................................. 73 33 Recovering a deleted file or folder ............................................................................. 75 34 Properties dialog box, Security tab ............................................................................ 78 35 Advanced Security settings dialog box, Permissions tab ...............................................
Tables 1 Storage system RAID configurations ........................................................................... 20 2 HP X3400 G2 front panel LED descriptions ................................................................ 22 3 HP X3400 G2 rear panel LED descriptions ................................................................. 23 4 HP X3800 G2 front panel LED and button descriptions ................................................ 25 5 HP X3800 G2 rear panel LED and button descriptions ........
1 Installing and configuring the storage system Setup overview The HP StorageWorks X3000 G2 Network Storage System comes preinstalled with the Microsoft Windows® Storage Server™ 2008 R2 Enterprise Edition x64operating system with Microsoft iSCSI Software Target and a Microsoft Cluster Service (MSCS) license included.
The type of access you select is determined by whether or not the network has a Dynamic Host Configuration Protocol (DHCP) server. If the network has a DHCP server, you can install the storage system through the direct attachment or remote management methods. If your network does not have a DHCP server, you must access the storage system through the direct attachment method. The direct attachment method requires a display, keyboard, and mouse. These components are not provided with the storage system.
IMPORTANT: Only the direct attach and remote management access methods can be used to install the storage system. After the storage system installation process is complete and the system's IP address has been assigned, you can then additionally use the remote browser and remote desktop methods to access the storage system. • Direct attach — Connect the following cables to the back panel of the storage system in the following sequence: keyboard, mouse, network cable, monitor cable, and power cable.
1. Power on the system by pushing the power button on the front panel. If using iLO, click Momentary Press on the Power Management page to power on the server, then click Launch on the Status Summary page to open the iLO Integrated Remote Console and complete the installation process. The storage system starts and displays an HP Network Storage System installation screen. The storage system installation process takes approximately 10–15 minutes.
2. Record the product key located on the Certificate of Authenticity. 3. In Control Panel, double-click System. 4. Under Windows Activation, click Activate Windows Now. 5. Follow the on-screen instructions. Be sure to choose the Type a different product key option when prompted for a product key. Microsoft Windows Storage Server 2008 R2 cannot be fully activated online. During the activation process, you will be provided with a telephone number to call to complete the process.
Additional access methods After the storage system installation process is complete and the system's IP address has been assigned, you can then additionally use the remote browser, Remote Desktop, and Telnet methods to access the storage system. Using the remote browser method The storage system ships with DHCP enabled on the network port. If the server is placed on a DHCP-enabled network and the IP address or server name is known, the server can be accessed through a client running Internet Explorer 5.
allows only two concurrent sessions. Leaving a session running takes up one license and can affect other users. If two sessions are running, additional users will be denied access. To connect the storage system to a network using the Remote Desktop method 1. On the PC client, select Start > Run. At Open, type mstsc, then click OK. 2. Enter the IP address of the storage system in the Computer box and click Connect. 3. Log on to the storage system with the administrator user name and password.
If the Operating System volume is customized and the System Recovery DVD is run at a later time, the System Recovery process will maintain the custom settings as long as the above criteria are met (RAID level other than RAID 0 and OS logical drive size of 60 GB or higher) and the OS volume is labeled System. If the storage system arrays are deleted and the System Recovery DVD is run, the System Recovery process will configure the storage system using the factory default settings listed in the table below.
2 Storage system component identification This chapter provides illustrations of the storage system hardware components. NOTE: The keyboard, mouse, and monitor are used only for the direct attached method of accessing the server. They are not provided with your storage system. HP X3400 G2 Network Storage Gateway hardware components The following figures show components and LEDs located on the front and rear panels of the X3400 G2 Network Storage Gateway. Figure 1 HP X3400 G2 front panel components . 1.
Figure 2 HP X3400 G2 front panel LEDs . Table 2 HP X3400 G2 front panel LED descriptions Item / Description Status Green = System health is normal. 1. Internal health LED Amber = System health is degraded. Red = System health is critical. Off = System health is normal (when in standby mode). 2. NIC 1 link/activity LED 3. NIC 2 link/activity LED 4. Drive activity LED Green = Network link exists. Flashing green = Network link and activity exist. Off = No network link exists.
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. Power cord connector Mouse connector 10/100/1000 NIC 1 connector/shared iLO 2 management port 10/100/1000 NIC 2 connector Serial connector Low profile PCIe slot cover (x16 slot open) Full-sized PCIe slot (occupied by Smart Array P212 controller) Dedicated iLO 2 management port (this port is optional and must be purchased separately) Video connector USB connectors (2) Keyboard connector Figure 4 HP X3400 G2 rear panel LEDs .
Figure 5 HP X3800 G2 front panel components . 1. 2. Quick release levers (2) Systems Insight Display NOTE: See “Systems Insight Display LEDs” on page 30 and “Systems Insight Display LED combinations” on page 31 for LED status information. 3. Eight (8) 2.5” SFF SAS / SATA hot plug hard drive bays NOTE: See “SAS and SATA hard drive LED combinations” on page 29 for HDD LED status descriptions. 4. 5. 6.
Figure 6 HP X3800 G2 front panel LEDs and buttons . Table 4 HP X3800 G2 front panel LED and button descriptions Item / Description Status Blue = Activated 1. UID LED and button Flashing blue = System being remotely managed Off = Deactivated Green = Normal 2. System health LED Amber = System degraded Red = System critical To identify components in degraded or critical state, see 3.
2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. PCIe slot 6 PCIe slot 4 (occupied by P812 Smart Array controller) PCIe slot 2 PCIe slot 3 (SAS Expander) PCIe slot 1 Power supply 2 (standard) Power supply 1 (standard) USB connectors (2) Video connector NIC 1 connector NIC 2 connector Mouse connector Keyboard connector Serial connector iLO 3 connector NIC 3 connector 18. NIC 4 connector Figure 8 HP X3800 G2 rear panel LEDs and buttons .
Item / Description Status Green = Network activity 3. NIC/iLO 3 activity LED Flashing green = Network activity Off = No network activity 4. NIC/iLO 3 link LED Green = Network link Off = No network link HP X3800sb G2 Network Storage Gateway Blade hardware components The following figures show components and LEDs located on the front panel of the X3800sb G2 Network Storage Gateway. Figure 9 HP X3800sb G2 front panel components . 1. 2. SUV connector Serial label pull tab 3. 4. 5. 6. 7.
Figure 10 HP X3800sb G2 front panel LEDs . Table 6 HP X3800sb G2 front panel LED descriptions Item / Description Status Blue = Identified 1. UID LED Blue flashing = Active remote management Off = No active remote management Green = Normal 2. Health LED Flashing = Booting Amber = Degraded condition Red = Critical condition Green = Network linked 3. Flex-10 NIC 1 LED Green flashing = Network activity Off = No link or activity Green = Network linked 4.
Figure 11 SAS/SATA hard drive LEDs . Table 7 SAS and SATA hard drive LED combinations 1. Fault/UID LED (amber/blue) 2. Online/activity LED (green) Alternating amber and blue On, off, or flashing The drive has failed, or a predictive failure alert has been received for this drive; it also has been selected by a management application. Steadily blue On, off, or flashing The drive is operating normally, and it has been selected by a management application.
1. Fault/UID LED (amber/blue) 2. Online/activity LED (green) Status Amber, flashing regularly (1 Hz) Off A predictive failure alert has been received for this drive. Replace the drive as soon as possible. Off Off The drive is offline, a spare, or not configured as part of an array. Systems Insight Display LEDs The HP Systems Insight Display LEDs represent the system board layout. The display enables diagnosis with the access panel installed. Figure 12 Systems Insight Display LEDs .
Item / Description Status Green = AMP mode enabled Amber = Failover 3. AMP status Flashing amber = invalid configuration Off = AMP modes disabled Off = Normal Amber =Failure All other LEDs For detailed information on the activation of these LEDs, see “Systems Insight Display LED combinations” on page 31. Systems Insight Display LED combinations When the internal health LED on the front panel illuminates either amber or red, the server is experiencing a health event.
Systems Insight Display LED and color Internal health LED color Status Online spare memory (flashing amber) Red Invalid online spare memory configuration. Online spare memory (green) Green Online spare memory enabled and not failed. Mirrored memory (amber) Amber Bank(s) X failed over to the mirrored memory bank(s). Mirrored memory (flashing (amber) Red Invalid mirrored memory configuration. Mirrored memory (green) Green Mirrored memory enabled and not failed.
3 Administration tools HP StorageWorks X3000 G2 Network Storage Systems include several administration tools to simplify storage system management tasks. Microsoft Windows Storage Server 2008 R2 administration tools Microsoft® Windows® Storage Server 2008 R2 operating systems provide a user interface for initial server configuration, unified storage system management, simplified setup and management of storage and shared folders, and support for Microsoft iSCSI Software Target.
NOTE: You must have a VDS Hardware Provider that is appropriate for your storage system installed in order to provision storage on an iSCSI target. If you have Microsoft iSCSI Software Target running on a Windows Storage Server 2008 R2 storage system, install the Microsoft iSCSI Software Target VDS Hardware Provider on the client computer. • Provision a Shared Folder Wizard for creating and configuring shared folders that can be accessed by using either the server message block (SMB) or NFS protocol.
• The backup software used must support SIS-enabled volumes. • The SIS volume, SIS Common Store folder, and reparse points (links) to the files must be restored to a Windows 2000 NTFS version 5.0 (or later) file system or partition that supports reparse points or junction points. • The Single Instance Storage Filter must be installed or enabled to access the data in the SIS volume.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID= 5f4c294c-8692-4235-8236-8ea809ae71f7 . Configuring AD LDS To simplify AD LDS mapped user access, HP provides the scripts that Microsoft describes in the NFS Account Mapping in Windows Server 2008 R2 whitepaper. The whitepaper describes two phases of scripts. Phase 1 scripts are used to install and prepare your system for NFS account mapping. Phase 2 scripts are used to configure specific users and groups for NFS account mapping.
Figure 13 AD LDS Role and Instance . To verify the installation of the Services for Network File System (NFS) Role, in Server Manager, under Roles, click File Services. In the System Services table, Server for NFS is listed. Phase 2 scripts Phase 2 scripts are located in the c:\hpnas\components\ADLDS folder. You create NFS mappings for users and groups by running the nfs-adlds-config.js script. This script takes as inputs a standard UNIX password file and a standard UNIX group file.
Each line of a standard UNIX group file follows this format: group:password:GID:group list All fields are required, but only the group, GID, and group list fields are used. The GID field value must match the GID field value in the password file for those users that belong to the group. NOTE: If you create the group and password files, you must have corresponding users and groups on the UNIX system.
Figure 14 AD LDS script execution help screen . As a best practice, specify all of the above parameters so that Windows accounts and NFS mappings are created; however, you can provide finer control as follows. If you omit the /ldf option, the script creates Windows accounts but not NFS mappings. Likewise, omitting the /usercmd option creates NFS mappings but not Windows accounts. The /execute option controls whether Windows accounts and NFS mappings are actually made to the system.
The newly-created NFS mappings are stored as Active Directory objects and can be verified as follows: 1. Click Start > Administrative Tools > ADSI Edit. 2. On the Action menu, select Connect to.... 3. In the Connection Settings dialog box, under Computer, select the radio button labeled Select or type a domain or server: (Server|Domain[:port]). 4. In the Select or type a domain or server: (Server|Domain[:port]) field, type localhost:389 and then click OK.
Figure 16 NFS-mapped users and groups in ADSI Edit . Because the imported users and groups are now Windows users and groups as well as UNIX users and groups, you can use NFS sharing so that volumes, folders and files are visible in both the Windows file system and the UNIX file system. When you set ownership or permissions in the Windows file system, the proper ownership and permissions are set on the UNIX side.
Step 1 If you have not already run the Phase 1 script factory-setup-adlds.cmd, do so now. The script is located in the c:\hpnas\components\postinstaller\adlds folder.
Figure 17 NFS Advanced Sharing dialog box . Click the Permissions button. In the Type of access list, select Read-Write. Check the Allow root access check box. Figure 18 NFS Share Permissions dialog box . Click OK twice to return to the NfsTest Properties dialog box.
Step 5 In the NfsTest Properties dialog box, select the Security tab. This tab shows the current security settings for the folder. The following steps will add permissions for Everyone to have access to the NfsTest folder. To do this, click Edit… and then click Add…. Under Group or user names: type Everyone and then click OK. In the Permissions for NfsTest dialog box, check the Allow check box for Full control under Permissions for Everyone. Figure 19 Permissions for NfsTest dialog box .
check the Owner check box and then click OK. Note that root is part of the owner name. This verifies that NFS mapping is functional for the root user. Step 8 On the Windows system as Administrator, create a file file.txt in C:\NfsTest. Windows Explorer now displays its properties: On the UNIX system, issue a listing of the /mnt/nfstest directory. This listing displays the following information. Note that file permissions on your system may be different than those shown here.
Step 10 On the UNIX system, issue a listing of the /mnt/nfstest directory. Because you changed the owner of file.txt on the Windows system to user1, the owner of the file on the UNIX side is also user1. Because user1 is in the allusers group on the Windows system, the group ownership of file.txt is allusers on the UNIX side. If the group for file.txt is listed as nfsnobody, you must enable Microsoft hotfix 2222746 and restart the storage system as described in “Shared access example” on page 41.
Figure 22 Replace owner on subcontainers and objects . Click OK four times to dismiss the Properties dialog box. Return to the Properties dialog box, select the Security tab, and then click Edit. Select Everyone in the list of groups and user names and then click Remove. Next, click Add and add user1. Select full control for its permissions. Figure 23 Permissions for NfsTest dialog box . Click OK twice to dismiss the NfsTest Permissionsand Properties dialog boxes.
Administration tools
4 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 24 depicts many of the storage elements that one would find on a storage device.
Figure 24 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 25. 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 26, 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 27 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.
dynamic disks is unavailable. There could be a potential for data loss depending on the nature of the failed LUN. Volumes are created out of the dynamic disks, and can be expanded on the fly to extend over multiple dynamic disks if they are spanned volumes. However, after a type of volume is selected, it cannot be altered. For example, a spanning volume cannot be altered to a mirrored volume without deleting and recreating the volume, unless it is a simple volume.
Shadow copies should not replace the current backup, archive, or business recovery system, but they can help to simplify restore procedures. For example, shadow copies cannot protect against data loss due to media failures; however, recovering data from shadow copies can reduce the number of times needed to restore data from tape. Using storage elements The last step in creating the element is determining its drive letter or mount point and formatting the element.
For additional information, refer to the Management CD in the HP ProLiant Essentials Foundation Pack or the HP SIM website (http://www.hp.com/go/hpsim). Management Agents Management Agents provide the information to enable fault, performance, and configuration management. The agents allow easy manageability of the server through HP SIM software, and thirdparty SNMP management platforms. Management Agents are installed with every SmartStart assisted installation or can be installed through the HP PSP.
5 File server management This chapter begins by identifying file services in Windows Storage Server 2008 R2. The remainder of the chapter describes the many tasks and utilities that play a role in file server management. File services features in Windows Storage Server 2008 R2 Storage Manager for SANs The Storage Manager for SANs (also called Simple SAN) snap-in enables you to create and manage the LUNs that are used to allocate space on storage arrays.
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 X3000 G2 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.
• A single array can contain multiple logical drives of varying RAID settings. • Extending and expanding arrays and logical drives is supported. The HP Array Configuration Utility User Guide is available for download at http://www.hp.com/ support/manuals. Disk Management utility The Disk Management tool is a system utility for managing hard disks and the volumes, or partitions, that they contain.
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.
• Improve performance by increasing the number of spindles in a logical drive volume • Change fault-tolerance (RAID) configurations For more information about RAID levels, see the Smart Array Controller User Guide, or the document titled Assessing RAID ADG vs. RAID 5 vs. RAID 1+0. Both are available at the Smart Array controller web page or at http://h18000.www1.hp.com/products/servers/proliantstorage/arraycontrollers/ documentation.html.
Volume shadow copies NOTE: Select storage systems can be deployed in a clustered as well as a non-clustered configuration. This chapter discusses using shadow copies in a non-clustered environment. The Volume Shadow Copy Service provides an infrastructure for creating point-in-time snapshots (shadow copies) of volumes. Shadow Copy supports 64 shadow copies per volume. A shadow copy contains previous versions of the files or folders contained on a volume at a specific point in time.
NOTE: Shadow copies should not be used to provide access to previous versions of application or e-mail databases. Shadow copies are designed for volumes that store user data such as home directories and My Documents folders that are redirected by using Group Policy or other shared folders in which users store data. Shadow copies work with compressed or encrypted files and retain whatever permissions were set on the files when the shadow copies were taken.
CAUTION: To change the storage volume, shadow copies must be deleted. The existing file change history that is kept on the original storage volume is lost. To avoid this problem, verify that the storage volume that is initially selected is large enough. Identifying the storage area To store the shadow copies of another volume on the same file server, a volume can be dedicated on separate disks. For example, if user files are stored on H:\, another volume such as S:\can be used to store the shadow copies.
NOTE: To check the cluster size of a volume, use the fsutil fsinfo ntfsinfo command. To change the cluster size on a volume that contains data, back up the data on the volume, reformat it using the new cluster size, and then restore the data. Mounted drives A mounted drive is a local volume attached to an empty folder (called a mount point) on an NTFS volume. When enabling shadow copies on a volume that contains mounted drives, the mounted drives are not included when shadow copies are taken.
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 29). 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 29 Shadow copies stored on a source 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. By storing shadow copies on a separate volume space, limits can generally be set higher, or set to No Limit.
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.
6. Click Settings. 7. In the Located on this volume field, select an available alternate volume from the list. NOTE: To change the default shadow copy schedule settings, click Schedule. 8. Click OK. 9. On the Shadow Copies tab, ensure that the volume is selected, and then click Enable. Shadow copies are now scheduled to be made on the alternate volume.
3. Click the Shadow Copies tab. See Figure 31. Figure 31 Accessing shadow copies from My Computer . 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 includes HTTP, FTP, AppleTalk, and NetWare Shares. For SMB support, a client-side application denoted as Shadow Copies for Shared Folders is required.
SMB shadow copies Windows users can independently access previous versions of files stored on SMB shares by using the Shadow Copies for Shared Folders client. After the Shadow Copies for Shared Folders client is installed on the user's computer, the user can access shadow copies for a share by right-clicking on the share to open its Properties window, clicking the Previous Versions tab, and then selecting the desired shadow copy. Users can view, copy, and restore all available shadow copies.
NFS shadow copies UNIX users can independently access previous versions of files stored on NFS shares via the NFS client; no additional software is required. Server for NFS exposes each of a share's available shadow copies as a pseudo-subdirectory of the share. Each of these pseudo-subdirectories is displayed in exactly the same way as a regular subdirectory is displayed. The name of each pseudo-subdirectory reflects the creation time of the shadow copy, using the format .@GMT-YYYY.MM.DD-HH:MM:SS.
6. Click Restore to restore the file or folder to its original location. Click Copy... to allow the placement of the file or folder to a new location. Figure 33 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.
3. Click either Copy... or Restore. Clicking Restore enables the user to recover everything in that folder as well as all subfolders. Clicking Restore does not delete any files. 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.
management of the file shares for the supported protocols. Security at the file level and at the share level is also discussed. 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 34 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 35 illustrates the properties available on the Advanced Security Settings dialog box. Figure 35 Advanced Security settings dialog box, Permissions tab . Other functionality available in the Advanced Security Settings dialog box is illustrated in Figure 35 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 36 illustrates the Edit screen and some of the permissions. Figure 36 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 37 Advanced Security Settings dialog box, Auditing tab . 5. Click Add to display the Select User or Group dialog box. Figure 38 Select User or Group dialog box . NOTE: Click Advanced to search for users or groups. 6. Select the user or group.
7. Click OK. The Auditing Entry dialog box is displayed. Figure 39 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 40 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.
File server management
6 Cluster administration One important feature of HP StorageWorks X3000 G2 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 A failover cluster is a group of independent computers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software.
Figure 41 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 42 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 Failover Cluster Management. 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 Failover Cluster Management exclusively. Hierarchy of cluster resource components Figure 42 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.
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. (500 MB is recommended.) Additional LUNs may also be presented for use as shared disk resources. • Cluster configurations should be deployed with dual data paths for high availability. Dual data paths from each node enable a path failure to occur that does not force the failover of the node.
• All partitions on the disks must be formatted as NTFS. Cluster installation During the installation process, nodes are shut down and rebooted. These steps 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 13 to determine which nodes and storage devices should be presented during each step.
Configuring the public network adapter While the public network adapter's IP address can be automatically obtained if a DHCP server is available, this is not recommended for cluster nodes. HP strongly recommends setting static IP addresses for all network adapters in the cluster, both private and public. If IP addresses are obtained though DHCP, access to cluster nodes could become unavailable if the DHCP server goes down.
Configuring shared disks Use the Windows Disk Management utility to configure additional shared disk resources. Verify that all shared disks are formatted as NTFS and are designated as Basic. Additional shared disk resources are automatically added into the cluster as physical disk resources during the installation of cluster services. Verifying disk access and functionality Write a file to each shared disk resource to verify functionality.
CAUTION: Presenting other LUNs to the non-clustered system could lead to data corruption. Geographically dispersed clusters Cluster nodes can be geographically dispersed to provide an additional layer of fault tolerance. Geographically dispersed clusters are also referred to as stretched clusters. The following rules must be followed with geographically dispersed clusters: • A network connection with latency of 500 milliseconds or less ensures that cluster consistency can be maintained.
Node-based cluster groups Creating only one resource group and one virtual server for each node facilitates group and resource administration. This setup allows administrators to include all file share resources under one group. Clients access all of the resources owned by one node through a virtual server name. In node-based cluster groups, each group has its own network name and IP address. The administrator decides on which node to place each physical disk resource.
4. Assign ownership of the file share resources to the resource groups. a. b. c. Divide ownership of the file share resource between the resource groups, which are in turn distributed between the virtual servers, for effective load balancing. Verify that the physical disk resource for this file share is also included in this group. Verify that the resources are dependent on the virtual servers and physical disk resources from which the file share was created.
Non cluster aware file sharing protocols Services for Macintosh (SFM), File and Print Services for NetWare, HTTP file sharing protocols are not cluster aware and will experience service interruption if installed on a clustered resource during failover events of the resource. Service interruptions will be similar to those experienced during a server outage. Data that has not been saved to disk prior to the outage will experience data loss.
Creating NFS share resources To create an NFS share resource, see “MSNFS administration on a server cluster” on page 104. 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. In this case, a physical disk resource for the cache file disk should be created in the same cluster group as the intended Shadow Copy resource and the volume for which snapshots will be enabled.
• • • • • • • • • • • Use the appropriate tool to manage Network File System (NFS) share cluster resources. Avoid conflicting share names. Ensure the availability of audit logs. Move file shares or take them offline before stopping Server for NFS. Take resources offline before modifying. Administer Server for NFS only from computers in a trusted domain. Restart the Server for NFS service after the cluster service restarts. Choose the appropriate sharing mode.
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.
7 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.
tower models, the COA label is located toward the rear of the top panel of the server. On blade models, the COA label is located on top of the server blade. Workarounds for common issues The following list documents common issues related to HP StorageWorks X3000 G2 Network Storage Systems and their recommended workarounds. For issues and workarounds specific to a particular product release, see the HP StorageWorks X3000 G2 Network Storage System Release Notes for your product version.
Issue: Adding the hardware ID in MPIO properties results in losing access to MPIO LUNs In rare cases, configuring MPIO when connected to an MSA array will result in losing access to the MPIO LUNs. The correct MPIO configuration can be determined by opening device manager and confirming that the LUNs presented from the MSA array are enumerated as a "Multi-path Disk Device". If incorrectly configured, the LUNs are not present in the device manager or are enumerated twice.
8 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.
3. Click Restore Factory Image. The upgrade process completes with little user intervention required. The server automatically reboots more than once. IMPORTANT: Do not interrupt the upgrade process. When the upgrade process nears completion, the Windows Storage Server 2008 R2 desktop displays the following message: The user's password must be changed before logging on the first time. Log on to the storage system by establishing an Administrator password: 4. Click OK. 5.
11. Enter format fs=fat32 quick. NOTE: If your USB Flash Drive does not support the FAT32 file system, format the drive as NTFS instead. Omitting the quick parameter lengthens the format time considerably. 12. Enter active to mark the partition as active. 13. Enter assign letter= to assign a drive letter to the USB drive. For example, assign letter=U. 14. Insert the System Recovery DVD provided with the system. 15.
5. Type an Administrator password in the New password box. 6. Re-type the Administrator password in the Confirm password box. 7. Click the blue arrow next to the Confirm password box. 8. Click OK. After the Administrator password has been set, the storage system completes the recovery process. 9. Remove the USB Flash drive from the X Series system or client PC.
9 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
WARNING! Indicates that failure to follow directions could result in bodily harm or death. CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: Provides clarifying information or specific instructions. NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Rack stability Rack stability protects personnel and equipment.
http://www.hp.com/go/selfrepair HP Insight Remote Support software HP strongly recommends that you install HP Insight Remote Support software to complete the installation or upgrade of your product and to enable enhanced delivery of your HP Warranty, HP Care Pack Service or HP contractual support agreement.
Support and other resources
A Regulatory compliance notices This section contains regulatory notices for the HP ______________________. 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.
Japanese power cord statement Korean notices Class A equipment Class B equipment Taiwanese notices BSMI Class A notice 124 Regulatory compliance notices
Taiwan battery recycle statement Turkish recycling notice Türkiye Cumhuriyeti: EEE Yönetmeliğine Uygundur X3000 G2 Network Storage System User Guide 125
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 X3000 G2 Network Storage System User Guide 127
Japanese laser notice Spanish laser notice Recycling notices English recycling notice Disposal of waste equipment by users in private household in the European Union This symbol means do not dispose of your product with your other household waste. Instead, you should protect human health and the environment by handing over your waste equipment to a designated collection point for the recycling of waste electrical and electronic equipment.
Bulgarian recycling notice Този символ върху продукта или опаковката му показва, че продуктът не трябва да се изхвърля заедно с другите битови отпадъци. Вместо това, трябва да предпазите човешкото здраве и околната среда, като предадете отпадъчното оборудване в предназначен за събирането му пункт за рециклиране на неизползваемо електрическо и електронно борудване. За допълнителна информация се свържете с фирмата по чистота, чиито услуги използвате.
Estonian recycling notice Äravisatavate seadmete likvideerimine Euroopa Liidu eramajapidamistes See märk näitab, et seadet ei tohi visata olmeprügi hulka. Inimeste tervise ja keskkonna säästmise nimel tuleb äravisatav toode tuua elektriliste ja elektrooniliste seadmete käitlemisega egelevasse kogumispunkti. Küsimuste korral pöörduge kohaliku prügikäitlusettevõtte poole.
Greek recycling notice μ Αυτό το σύμβολο σημαίνει ότι δεν πρέπει να απορρίψετε το προϊόν με τα λοιπά οικιακά απορρίμματα. Αντίθετα, πρέπει να προστατέψετε την ανθρώπινη υγεία και το περιβάλλον παραδίδοντας τον άχρηστο εξοπλισμό σας σε εξουσιοδοτημένο σημείο συλλογής για την ανακύκλωση άχρηστου ηλεκτρικού και ηλεκτρονικού εξοπλισμού. Για περισσότερες πληροφορίες, επικοινωνήστε με την υπηρεσία απόρριψης απορριμμάτων της περιοχής σας.
Lithuanian recycling notice Nolietotu iek rtu izn cin šanas noteikumi lietot jiem Eiropas Savien bas priv taj s m jsaimniec b s Šis simbols norāda, ka ierīci nedrīkst utilizēt kopā ar citiem mājsaimniecības atkritumiem. Jums jārūpējas par cilvēku veselības un vides aizsardzību, nododot lietoto aprīkojumu otrreizējai pārstrādei īpašā lietotu elektrisko un elektronisko ierīču savākšanas punktā. Lai iegūtu plašāku informāciju, lūdzu, sazinieties ar savu mājsaimniecības atkritumu likvidēšanas dienestu.
Slovak recycling notice Likvidácia vyradených zariadení používate mi v domácnostiach v Európskej únii Tento symbol znamená, že tento produkt sa nemá likvidovať s ostatným domovým odpadom. Namiesto toho by ste mali chrániť ľudské zdravie a životné prostredie odovzdaním odpadového zariadenia na zbernom mieste, ktoré je určené na recykláciu odpadových elektrických a elektronických zariadení. Ďalšie informácie získate od spoločnosti zaoberajúcej sa likvidáciou domového odpadu.
Battery replacement notices Dutch battery notice 134 Regulatory compliance notices
French battery notice German battery notice X3000 G2 Network Storage System User Guide 135
Italian battery notice Japanese battery notice 136 Regulatory compliance notices
Spanish battery notice X3000 G2 Network Storage System User Guide 137
Regulatory compliance notices
Glossary The following glossary terms and definitions are provided as a reference for storage products. ACL Access control list. ADS Active Directory Service. array A synonym of storage array, storage system, and virtual array. A group of disks in one or more disk enclosures combined with controller software that presents disk storage capacity as one or more virtual disks. backups A read-only copy of data copied to media, such as hard drives or magnetic tape, for data protection.
computer (such as a server that hosts Exchange or SQL Server) and a target device (such as the HP All-in-One Storage System). By carrying SCSI commands over IP networks, iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. HDD Hard disk drive. iLO Integrated Lights-Out. LAN Local area network.
Index A access rights, managing, 102 Accessing the storage system Remote Desktop method, 18 Accessing the storage system remote browser method, 18 ACL, defining, 84 Active Directory® Lightweight Directory Services (AD LDS), 36 ActiveX enabling, 18 Array Configuration Utility, 59 array controller, purpose, 51 arrays, defined, 51 B backup, with shadow copies, 76 basic disks, 53, 54 basic disks, 53, 54 battery replacement notices, 134 boot sequence, 20 C cache file, shadow copies, 68 Canadian notice, 122 Cer
Declaration of Conformity, 122 default storage settings, 19 disk access, verifying, 99 Disk Management extending volumes, 63 Disposal of waste equipment, European Union, 128 document conventions, 117 domain membership, verifying, 98 dual data paths, 96 dynamic disks clustering, 54 dynamic disks spanning multiple LUNs, 53 E End User License Aggreement (EULA), 14 European Union notice, 123 expanding storage Array Configuration Utility, 63 Command View EVA, 63 extending volumes Disk Management, 63 F factory
network planning, 94 network requirements, cluster, 96 NFS share resource, 104 node, server, 90 O online spares, 52 P partitions extended, 53 primary, 53 permissions file level, 77 list adding users and groups, 78 removing users and groups, 78 modifying, 79 resetting, 79 physical disk resources, 93, 103 physical configuration, 19 physical storage elements, 50 planning network, 94 network access method, 13 protocol, 95 storage, 94 power on server, 15 Print Management, 35 printer spooler, creating in a clus
shadow copies, 54 backups, 76 cache file, 68 defragmentation, 66 described, 64 disabling, 71 file or folder recovery, 74 managing, 67 mounted drives, 67 on NFS shares, 74 on SMB shares, 73 planning, 64 redirecting, 70 scheduling, 70 viewing list, 69 Shadow Copies for Shared Folders, 72 Share and Storage Management, 33 share management, 83 shared disks, configuring, 99 shares administrative, 85 managing, 83 standard, 85 Single Instance Storage, 57 Single Instance Storage (SIS), 34 storage configurations, 19
