HP StorageWorks 2000s Administration Manual

hp StorageWorks

NAS 2000s

First Edition(September 2003)

Part Number: 345650-001

Administration Guide

This guide provides information on performing the administrative tasks necessary to manage the HP
StorageWorks NAS 2000s server. Overview information as well as procedural instructions are included in this
guide.

© Copyright 2003 Hewlett-Packard Development Company, L.P.
Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied

warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for
incidental or consequential damages in connection with the furnishing, performance, or use of this material.

This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied,
reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information contained in this
document is subject to change without notice.

Compaq Computer Corporation is a wholly-owned subsidiary of Hewlett-Packard Company.
Microsoft®, MS-DOS®, MS Windows®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information is provided

“as is” without warranty of any kind and is subject to change without notice. The warranties for Hewlett-Packard Company products are
set forth in the express limited warranty statements for such products. Nothing herein should be construed as constituting an additional
warranty.

Printed in the U.S.A.

NAS 2000s Administration Guide
First Edition (September 2003)
Part Number: 345650-001

Contents

About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Text Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Equipment Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Rack Stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

HP Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

HP Storage Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

HP Authorized Reseller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Product Definition and Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Server Hardware and Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Product Manageability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Product Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Product Scalability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Environment Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Workgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

NAS 2000s Web-Based User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Menu Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Contents

3NAS 2000s Administration Guide

Contents

Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

HP Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Welcome Screen Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Rapid Startup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Set Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Take a Tour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Set Server Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Set Default Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

NAS 2000s Desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

NAS Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

NIC Team Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2 Basic Administrative Procedures and Setup Completion . . . . . . . . . . . . . . . . . . . . . .25

Basic Administrative Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Setting the System Date and Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Shutting Down or Restarting the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Viewing and Maintaining Audit Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Using Remote Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Improper Closure of Remote Desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Setting up E-mail Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Changing System Network Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Setup Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Activating the iLO Port Using the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Setting up Ethernet NIC Teams (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Installing the HP Network Teaming Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Opening the HP Network Teaming Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Adding and Configuring NICs in a Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Fault Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring the NIC Team Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Renaming the Teamed Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Showing a Connection Icon on the Taskbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Configuring the TCP/IP Protocol on the New Team . . . . . . . . . . . . . . . . . . . . . 39

Checking the Status of the Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

NIC Teaming Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4 NAS 2000s Administration Guide

Contents

Managing System Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Creating and Managing Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Creating and Managing File Shares. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3 Storage Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Storage Management Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Storage Elements Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Physical Hard Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Arrays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Logical Drives (LUNs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Fault-Tolerance Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

RAID 0—Data Striping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

RAID 1+0—Drive Mirroring and Striping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

RAID 5—Distributed Data Guarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Disadvantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

RAID ADG—Advanced Data Guarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Disadvantage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Online Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Physical Storage Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Logical Storage Elements Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Utilizing DM Storage Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Volume Shadow Copy Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

File System Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

File-Sharing Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4 Disk Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

WebUI Disks Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Storage Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Step 1: Create Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Step 2: Create Logical Disks from the Array Space. . . . . . . . . . . . . . . . . . . . . . 59

Step 3: Verify newly created logical disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

5NAS 2000s Administration Guide

Contents

Step 4: Create a Volume on the new logical disk . . . . . . . . . . . . . . . . . . . . . . . . 59

Array Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Using the ACU to Configure Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

ACU Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Managing Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Disk Management Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Disk Management Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Volumes Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Managing Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Dynamic Growth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Expanding a LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

To extend a LUN where space is available in the array: . . . . . . . . . . . . . . . 70

To extend a LUN where space is not available in the array. . . . . . . . . . . . . 70

Extending a partition on a basic disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Extending using DiskPart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Scheduling Defragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Managing Disks After Quick Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Disk Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Enabling Quota Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Setting User Quota Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

DiskPart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Example of using DiskPart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

5 Shadow Copies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Shadow Copy Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Identifying the Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Allocating Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Identifying the Storage Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Determining Creation Frequency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Shadow Copies and Drive Defragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Mounted Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Managing Shadow Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

The Shadow Copy Cache File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Enabling and Creating Shadow Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Viewing a List of Shadow Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Set Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Scheduling Shadow Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Deleting a Shadow Copy Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6 NAS 2000s Administration Guide

Contents

Viewing Shadow Copy Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Disabling Shadow Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Managing Shadow Copies from the NAS Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Shadow Copies for Shared Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

SMB Shadow Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

NFS Shadow Copies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Recovery of Files or Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Recovering a Deleted File or Folder (non-sharepoint or Windows XP/Windows 2003) 97

Recovering a Deleted File or Folder (sharepoint - Windows 2000 SP3 only). . . . . . . . . 98

Recovering an Overwritten or Corrupted File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Recovering a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Backup and Shadow Copies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

6 User and Group Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Domain Compared to Workgroup Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

User and Group Name Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Managing User Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Managing Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Workgroup User and Group Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Managing Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Adding a New User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Deleting a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Modifying a User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Modifying User Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Managing Local Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Adding a New Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Deleting a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Modifying Group Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Members Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

7 Folder, Printer, and Share Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Folder Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Navigating to a Specific Volume or Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Creating a New Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Deleting a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Modifying Folder Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Creating a New Share for a Volume or Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Managing Shares for a Volume or Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

7NAS 2000s Administration Guide

Contents

Managing File Level Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Share Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Share Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Defining Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Integrating Local File System Security into Windows Domain Environments. . . . . . . 125

Comparing Administrative (Hidden) and Standard Shares . . . . . . . . . . . . . . . . . . . . . . 125

Planning for Compatibility between File Sharing Protocols . . . . . . . . . . . . . . . . . . . . . 125

NFS Compatibility Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Managing Shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Creating a New Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Deleting a Share. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Modifying Share Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Windows Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

UNIX Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Web Sharing (HTTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Protocol Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

DFS Protocol Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Deploying DFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

DFS Administration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Accessing the DFS Namespace from other Computers . . . . . . . . . . . . . . . . . . . . . . . . . 133

Setting DFS Sharing Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Creating a Local DFS Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Deleting a Local DFS Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Publishing a New Share in DFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Publishing an Existing Share in DFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Removing a Published Share from DFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Directory Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Establishing Directory Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

File Screening. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Storage Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Print Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Configuring the Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Removing the Print Server Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Adding an Additional Printer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Adding Additional Operating System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Installing Print Services for UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

8 NAS 2000s Administration Guide

Contents

8 Microsoft Services for NFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Server for NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Authenticating User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Indicating the Computer to Use for the NFS User Mapping Server . . . . . . . . . . . . . . . 148

Logging Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Server for NFS Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Installing NFS Authentication Software on the Domain Controllers and Active Directory

Domain Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Understanding NTFS and UNIX Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

NFS File Shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Creating a New Share. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Deleting a Share. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Modifying Share Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Encoding Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

NFS Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

NFS Protocol Properties Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

NFS Async/Sync Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

NFS Locks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

NFS Client Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Adding a New Client Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Deleting a Client Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Editing Client Group Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

NFS User and Group Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Types of Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Explicit Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Simple Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Squashed Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

User Name Mapping Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Creating and Managing User and Group Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Simple Mapping Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Explicit User Mapping Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Explicit Group Mapping Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Backing up and Restoring Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Backing up User Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Restoring User Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Creating a Sample NFS File Share. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Remote Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

9NAS 2000s Administration Guide

Contents

Using Remote Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

9 NetWare File System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175

Installing Services for NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Managing File and Print Services for NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Creating and Managing NetWare Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Adding Local NetWare Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Enabling Local NetWare User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Managing NCP Volumes (Shares) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Creating a New NCP Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Modifying NCP Share Properties using the NAS Management Console . . . . . . . . 184

NOTES:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

10 Remote Access Methods and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

Web Based User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Remote Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Integrated Lights-Out Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Manage Users Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Manage Alerts Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Integrated Lights-Out Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Using the Integrated Lights-Out Port to Access the NAS 2000s. . . . . . . . . . . . . . . . . . 191

Telnet Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Enabling Telnet Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Sessions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

HP Insight Manager Version 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

10 NAS 2000s Administration Guide

About This Guide

This administration guide provides information to help administrators:

■ Plan the storage configuration

■ Setup physical storage

■ Manage users and groups

■ Manage folders and shares

■ Manage a UNIX® file system

■ Manage a NetWare file system

■ Remotely access the NAS 2000s server

About this Guide

About this Guide

“About this Guide” topics include:

■ Overview, page 12

■ Conventions, page 12

■ Rack Stability, page 14

■ Getting Help, page 15

11NAS 2000s Administration Guide

About this Guide

Overview

This section covers the following topics:

■ Intended Audience

■ Prerequisites

Intended Audience

This book is intended for use by system administrators who are experienced with setting up
and managing a network server.

Prerequisites

Before beginning, make sure you consider the items below.

■ Knowledge of Microsoft® Windows® NT® or 2000® operating system

■ Knowledge of HP hardware

■ Location of all documentation shipped with your server

Conventions

Conventions consist of the following:

■ Document Conventions

■ Text Symbols

■ Equipment Symbols

Document Conventions

The document conventions included in Tab le 1 apply in most cases.

Table 1: Document Conventions

Cross-reference links Figure 1
Key and field names, menu items, buttons, and

dialog box titles
File names, application names, and text

emphasis
User input, command and directory names,

and system responses (output and messages)

Variables <monospace, italic font>
Website addresses Sans serif font text:

Element Convention

Bold

Italics

Monospace font
COMMAND NAMES are uppercase monospace

font unless they are case sensitive

http://www.hp.com

12 NAS 2000s Administration Guide

Text Symbols

The following symbols may be found in the text of this guide. They have the following
meanings:

Note: Text set off in this manner presents commentary, sidelights, or interesting points of

information.

Equipment Symbols

About this Guide

WARNING: Text set off in this manner indicates that failure to follow directions in the

warning could result in bodily harm or death.

Caution: Text set off in this manner indicates that failure to follow directions could result in

damage to equipment or data.

The following equipment symbols may be found on hardware for which this guide pertains.
They have the following meanings:

Any enclosed surface or area of the equipment marked with these symbols indicates
the presence of electrical shock hazards. Enclosed area contains no operator
serviceable parts.

WARNING: To reduce the risk of personal injury from electrical shock hazards, do

not open this enclosure.

Any RJ-45 receptacle marked with these symbols indicates a network interface
connection.

WARNING: To reduce the risk of electrical shock, fire, or damage to the equipment,

do not plug telephone or telecommunications connectors into this receptacle.

Any surface or area of the equipment marked with these symbols indicates the
presence of a hot surface or hot component. Contact with this surface could result in
injury.

WARNING: To reduce the risk of personal injury from a hot component, allow the

surface to cool before touching.

13NAS 2000s Administration Guide

About this Guide

Rack Stability

Power supplies or systems marked with these symbols indicate the presence of
multiple sources of power.

WARNING: To reduce the risk of personal injury from electrical shock, remove

all power cords to completely disconnect power from the power supplies and
systems.

Any product or assembly marked with these symbols indicates that the component
exceeds the recommended weight for one individual to handle safely.

WARNING: To reduce the risk of personal injury or damage to the equipment,

observe local occupational health and safety requirements and guidelines for
manually handling material.

Rack stability protects personnel and equipment.

WARNING: To reduce the risk of personal injury or damage to the equipment, be sure that:

■ The leveling jacks are extended to the floor.

■ The full weight of the rack rests on the leveling jacks.

■ In single rack installations, the stabilizing feet are attached to the rack.

■ In multiple rack installations, the racks are coupled.

■ Only one rack component is extended at any time. A rack may become unstable if more

than one rack component is extended for any reason.

14 NAS 2000s Administration Guide

Getting Help

If you still have a question after reading this guide, contact an HP authorized service provider
or access our website:

HP Technical Support

Telephone numbers for worldwide technical support are listed on the following HP website:

http://www.hp.com/support/

Note: For continuous quality improvement, calls may be recorded or monitored.

Be sure to have the following information available before calling:

■ Technical support registration number (if applicable)

■ Product serial numbers

■ Product model names and numbers

■ Applicable error messages

http://www.hp.com

.

. From this website, select the country of origin.

About this Guide

■ Operating system type and revision level

■ Detailed, specific questions

HP Storage Website

The HP website has the latest information on this product, as well as the latest drivers. Access
storage at:
the appropriate product or solution.

HP Authorized Reseller

For the name of your nearest HP authorized reseller:

■ In the United States, call 1-800-345-1518

■ In Canada, call 1-800-263-5868

■ Elsewhere, see the HP website for locations and telephone numbers:

http://www.hp.com/country/us/eng/prodserv/storag e.html

. From this website, select

http://www.hp.com

.

15NAS 2000s Administration Guide

About this Guide

16 NAS 2000s Administration Guide

System Overview

The HP StorageWorks NAS 2000s server can be used in many types of computing
environments, from basic Microsoft Windows workgroups to complicated multiprotocol
domains using DFS, NFS, FTP, HTTP, and Microsoft SMB. The corresponding varieties of
clients that can be serviced include any Windows, UNIX, Linux, Novell, or Macintosh variant.

This chapter provides an overview of these environments and deployments and includes brief
descriptions of system user interfaces, applications, and options.

Product Definition and Information

The NAS 2000s is a business class NAS solution that provides reliable performance,
manageability, and fault tolerance.

Server Hardware and Software Features

Refer to the HP StorageWorks NAS 2000s Installation Guide for a listing of server hardware
and software features.

1

For specific software product recommendations, go to the HP website:

http://h18000.www1.hp.com/products/s torageworks/nas/supportedsoftware.html

Product Manageability

The NAS 2000s ships with the following utilities and features that ease the administration
tasks associated with managing the system:

■ The Rapid Startup Wizard is a user friendly configuration utility that ensures easy

configuration.

■ The WebUI is a simple, graphical user interface (GUI) that helps with administration

tasks.

■ Insight Manager is a comprehensive tool designed to be a key component in the systems

management environment. It monitors the operations of HP servers, workstations, and
clients. Insight Manager provides system administrators more control through
comprehensive fault and configuration management, and industry leading remote
management.

■ The Integrated Lights-Out feature provides remote access, sends alerts, and performs other

management functions, even if the operating system of the host server is not responding.

17NAS 2000s Administration Guide

System Overview

Product Redundancy

The NAS 2000s is specifically designed to perform file serving tasks for networks. Using
industry standard components, redundancy of power supplies, NICs, and fans ensures
reliability.

Other industry standard features, such as redundant array of independent drives (RAID) and
remote manageability, further enhance the overall dependability of the NAS 2000s.

The server contains dual 36.4 GB hard drives preconfigured with the NAS operating system so
that the active system volume is mirrored (RAID 1+0) to the second drive. If one of the
internal drives fails, the integrity of the system is preserved, because the system will use the
copy of the operating system on the remaining healthy drive. The drives in the server are
hot-pluggable, so the failed drive can be replaced while the system is running. When the failed
drive is replaced, the system automatically uses the version of the operating system on the
healthy drive to rebuild the replacement.

The NAS 2000s internal storage server also contains four 146.8 GB hard drives for data
storage. The NAS 2000s external storage server ships with four 146.8 GB hard drives in an
external storage cabinet connected to the Smart Array 6404 controller. These hard drives are
not configured, allowing customizable configuration options. These drives may be configured
to RAID levels 0, 1+0, 5, and Advanced Data Guarding (ADG).

Product Scalability

Note: RAID 1+0 requires an even number of drives.

The NAS 2000s includes dual power supplies. A power supply can be replaced while the
server is running. To ensure redundancy, it is important to connect each power supply to a
separate power source. If one power source fails, the server remains operational through the
second power source.

Through a seamless, hardware-based, graphical remote console, the Integrated Lights-Out port
provides the administrator with full control of the server from a remote location. Using a client
browser, the administrator can remotely power up, power down, and operate the console. A
built in processor makes the port independent of the server and the operating system.

The NAS 2000s offers optimized performance for a growing environment. Storage capacity
can increase as a business grows without incurring downtime or compromising performance.
The internal model ships with four 146.8 GB disk drives, providing 587.2 GB of raw storage.
The external NAS 2000s model can support up 27 TB of raw storage capacity. This maximum
capacity is achieved by connecting thirteen HP StorageWorks storage enclosures to three
Smart Array 4-port controllers and the integrated SCSI array connector. Each storage
enclosure supports up to fourteen 146.8 GB hard disks, and the NAS system has four
additional SCSI bays, for a total of 186 hard disk drives.

The external NAS 2000s model can support up 27 TB of raw storage capacity. This maximum
capacity is achieved by connecting thirteen HP StorageWorks storage enclosures to three
Smart Array 4-port controllers and the integrated SCSI array connector. Each storage
enclosure supports up to fourteen 146.8 GB hard disks, and the NAS system has four
additional internal SCSI bays, for a total of 186 hard disk drives.

Note: Each fully populated HP StorageWorks 4300/4400 Family storage enclosure can contain up

to14 hard drives.

18 NAS 2000s Administration Guide

Deployment Scenarios

Various deployment scenarios are possible. See the HP StorageWorks NAS 2000s Installation
Guide for configurations. Typical application of NAS devices include:

■ File server consolidation

As businesses continue to expand their information technology (IT) infrastructures, they
must find ways to manage larger environments without a corresponding increase in IT
staff. Consolidating many servers into a single NAS device decreases the number of points
of administration and increases the availability and flexibility of storage space.

■ Multiprotocol environments

Some businesses require several types of computing systems to accomplish various tasks.
The multiprotocol support of the NAS 2000s allows it to support many types of client
computers concurrently.

■ Protocol and platform transitions

When a transition between platforms is being planned, the ability of the NAS 2000s to
support most file sharing protocols allows companies to continue to invest in file storage
space without concerns about obsolescence. For example, an administrator planning a
future transition from Windows to Linux can deploy the NAS 2000s with confidence that
it can support both CIFS and NFS simultaneously, assuring not only a smooth transition,
but also a firm protection of their investment.

System Overview

■ Remote office deployment

Frequently, branch offices and other remote locations lack dedicated IT staff members. An
administrator located in a central location can use the WebUI of the NAS 2000s, Microsoft
Terminal Services, and other remote administration methods to configure and administer
all aspects of the NAS 2000s.

19NAS 2000s Administration Guide

System Overview

Environment Scenarios

The NAS 2000s is deployed in one of two security modes:

■ Wo rkg rou p

■ Domain (Windows NT Domain or Active Directory Domain)

The NAS 2000s uses standard Windows user and group administration methods in each of
these environments. For procedural instructions on managing users and groups, see Chapter 5
of this guide.

Regardless of the deployment, the NAS 2000s integrates easily into multiprotocol
environments, supporting a wide variety of clients. The following protocols are supported:

■ Distributed File System (DFS)

■ Network File System (NFS)

■ Hypertext Transfer Protocol (HTTP)

■ File Transfer Protocol (FTP)

■ Microsoft Server Message Block (SMB)

Workgroup

Domain

In a workgroup environment, users and groups are stored and managed separately, on each
member server of the workgroup. Workgroups are typical for very small deployments where
little or no computing environment planning is required.

When operating in a Windows NT or Active Directory domain environment, the NAS 2000s is
a member of the domain and the domain controller is the repository of all account information.
Client machines are also members of the domain and users log on to the domain through their
Windows based client machines. The domain controller also administers user accounts and
appropriate access levels to resources that are a part of the domain. Additional information
about planning for domain environments can be found at:

http://www.microsoft.com/windo ws2000/technologies/directory/ad/default.asp

The NAS 2000s obtains user account information from the domain controller when deployed
in a domain environment. The NAS 2000s itself cannot act as a domain controller, backup
domain controller, or the root of an Active Directory tree as these functions are disabled in the
operating system.

20 NAS 2000s Administration Guide

User Interfaces

There are several user interfaces that administrators can use to access and manage the NAS
2000s. Two of these interfaces are:

■ NAS 2000s WebUI

■ NAS 2000s Desktop

Each interface contains the same or similar capabilities, but presents them in a different
manner. Each of these interfaces are illustrated in the following sections.

NAS 2000s Web-Based User Interface

The WebUI provides for system administration, including user and group management, share
management, and local storage management.

Refer to the HP StorageWorks NAS 2000s Installation Guide for detailed information on using
the Rapid Startup Wizard for initial setup.

To access the WebUI, launch a Web browser and enter the following in the address field:

https://<your NAS machine name or IP Address>:3202/

The default user name is Administrator. The default password is hpinvent. Online
help for the WebUI is available by clicking the Help tab on the primary WebUI screen.

The primary screen of the WebUI is shown in Figure 1.

System Overview

Figure 1: Primary WebUI screen

As shown in Figure 1, the following areas are administered through this interface:

21NAS 2000s Administration Guide

System Overview

Menu Tabs

Status

The Status option displays alerts generated by the WebUI.

Network

The Network option contains system settings, including system identification, global settings,
interfaces settings, administration settings, Telnet settings, and SNMP settings.

Disks

Use this option to manage disks, volumes, disk quotas, and shadow copies.

Users

Use this option to manage local users and groups.

Shares

The administrator creates folders and shares to control access to files. When a share is created,
the administrator indicates the protocols that can be supported by that share as well as the
users and groups of users that have access. Protocol parameters are entered in this Shares
option. See Chapter 6 for additional information.

Maintenance

Maintenance tasks include setting date and time, performing system restarts and shutdowns,
viewing audit logs, setting up Email alerts, linking to remote management, and selecting and
configuring your UPS.

HP Utilities

Access HP system management utilities such as remote management, enable floppy boot, File
and Print Services for Netware, and the HP System Management WebUI.

Help

This option contains help information for the WebUI.

Welcome Screen Contents

Installation Overview

Use to set up and configure the NAS server. This is an online, supplemental guide. A more
comprehensive paper document is provided in the country kit that shipped with the server.

Rapid Startup Wizard

Use this utility to enter system setup and configuration information.

Set Administrator Password

Create a password for the server appliance administrator.

Take a Tour

Learn how to use the NAS server.

22 NAS 2000s Administration Guide

Set Server Name

Choose a name so that client computers can connect to the server.

Set Default Page

Choose which page the server appliance displays first.

NAS 2000s Desktop

The NAS 2000s desktop can be accessed by:

■ Directly connecting a keyboard, mouse, and monitor

■ Using the WebUI Maintenance tab and selecting Remote Desktop

■ Using the Integrated Lights-Out port

Note: When using Remote Desktop to connect to the NAS 2000s desktop do not use the window

close feature ( ). Click on Start/Log Off Administrator to exit Remote Desktop. See “Improper
Closure of Remote Desktop” in Chapter 2.

System Overview

Figure 2: NAS 2000s desktop

The following icons are available from the Desktop:

■ NAS Management Console

■ NIC Team Setup

23NAS 2000s Administration Guide

System Overview

NAS Management Console

Click this icon to access the following folders:

■ Core Operating System is used to manage local users and groups, access performance

logs and alerts, and manage the event viewer.

■ Disk System contains access to the Compaq Array Configuration Utility and local disk

management, including a volume list and a graphical view of the disks.

■ File Sharing contains modules for the configuration of file sharing exports. CIFS/SMB

(Windows) and NFS (UNIX) file shares are managed through this folder.

■ System contains system summary information.

NIC Team Setup

Click this icon to install the HP Network Teaming and Configuration utility. See Chapter 2 for
additional information on this feature.

24 NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

Basic system administration functions are discussed in this chapter.
This chapter also continues the process of setting up the system that was started using the HP

StorageWorks NAS 2000s Installation Guide by discussing additional setup procedures and
options. Further steps can also be viewed online by clicking the Installation Overview tab
from the primary WebUI screen.

Unless otherwise instructed, all procedures are performed using the NAS Web Based User
Interface (WebUI).

Note: The NAS 2000s Desktop can be accessed via a directly connected keyboard, mouse, and

monitor through Remote Desktop, or by using an Integrated Lights-Out port.

Basic Administrative Procedures

2

Basic administrative procedures include:

■ Setting the system date and time

■ Shutting down or restarting the server

■ Viewing and maintaining audit logs

■ Using Remote Desktop

■ Setting up e-mail alerts

■ Changing system network settings

These functions are performed in the Maintenance menu of the WebUI.

25NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

Figure 3: Maintenance menu

Setting the System Date and Time

To change the system date or time:

1. From the WebUI, select Maintenance and Date/Time. The Date and Time Settings

dialog box is displayed.

2. Enter the new values and then click OK. The Maintenance menu is displayed.

Figure 4: Date and Time dialog box

26 NAS 2000s Administration Guide

Shutting Down or Restarting the Server

Caution: Notify users before powering down the system. Both UNIX and Windows NT users

can be drastically affected if they are not prepared for a system power-down.

1. From the NAS 2000s WebUI, select Maintenance, Shutdown. Several options are
displayed: Restart, Shut Down, and Scheduled Shutdown.

Basic Administrative Procedures and Setup Completion

Figure 5: Shutdown menu

a. To shut down and automatically restart the server, click Restart.
b. To shut down and power off the server, click Shut Down.
c. To schedule a shutdown, click Scheduled Shutdown.

2. Regardless of the choice, a confirmation prompt is displayed. After verifying that this is
the desired action, click OK.

Note: Client computers connected to the server will receive a warning message prior to shutdown.

Clients connected via Remote Desktop do not receive any warning.

27NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

Viewing and Maintaining Audit Logs

A variety of audit logs are provided on the NAS 2000s. System events are grouped into similar
categories, representing the seven different logs.

To access the logs from the WebUI, select Maintenance, Logs. The Logs menu is displayed.

Figure 6: Logs menu

A variety of logs are available and are listed in Figure 6.
Each log has viewing, clearing, printing, and saving options.

Note: You should not use the WebUI to view log files greater than 2 MB. Select Log properties to

adjust the maximum file size, or download the file to view.

Note: NFS logging is disabled by default. Enable NFS logging using the NAS Management

Console. NFS stops logging when the log file is full.

28 NAS 2000s Administration Guide

Using Remote Desktop

Remote Desktop is provided in the WebUI to allow for additional remote system
administration and the use of approved third-party applications. Backup software and antivirus
programs are examples of approved applications.

To open a Remote Desktop session from the WebUI, select Maintenance, Remote Desktop.
A Remote Desktop session is opened. Enter the appropriate password to log on to the server.

Basic Administrative Procedures and Setup Completion

Figure 7: Remote Desktop session

Caution: Two open sessions of Remote Desktop are allowed to operate at the same time.

After completing an application do not use the window close feature ( ) to close that
session of Remote Desktop. Click Start/Log Off Administrator to exit Remote Desktop.

Improper Closure of Remote Desktop

Certain operations such as drive management via ACU can leave the utilities running if the
browser is closed versus exiting from the program via the application menu or logging off the
Remote Desktop session. In the case of ACU, the drive lights will remain blinking until one of
the following occurs:

1. The ACU is accessed again via the link under Disk in the Web User Interface and the
application is closed properly.

2. The orphaned Remote Desktop session is closed and the orphaned application is closed.
The default timeout has been set to 15 minutes but it may require up to 30 minutes for
ACU to exit. This value may be adjusted in the Terminal Services Configuration option
under Administrator Tools, accessed either through the desktop or via a Remote Desktop
session.

29NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

Other applications may become orphaned in this manner when the Remote Desktop session is
exited improperly. A maximum of two Remote Desktop sessions may be used at any given
time. Improper exit from a session can result in the sessions becoming consumed. Sessions
and processes can be terminated using the Terminal Services Manager via
Start >Programs >Administrator Tools.

Note: The Terminal Services Manager must be accessed via the iLO port or direct attached console.

Setting up E-mail Alerts

E-mail messages are limited to the alerts generated from the WebUI status bar or the WebUI
status page, as well as some event log messages. Some alerts, such as the restart of the server,
only occur if the WebUI was utilized to initiate the request. For example, a restart initiated
using the WebUI will general an e-mail message indicating a restart has occurred. Initiating a
restart using the Windows 2000 schedule or Desktop will not. Messaging in the status bar and
page is limited to the following areas:

■ WebUI Alerts

— NTBackup backup started
— NTBackup restore started
— Defrag started
— UPS power failure
— Restart pending
— Shutdown pending
— DFS not configured
— Date and time not configured
— No certificate
— Quota management alerts

■ Event Log Messages

— NTBackup Information
— UPS power failed
— UPS power restored
— UPS invalid config
— UPS system shutdown
— Quota management alerts

To activate this option:

1. From the WebUI, select Maintenance, Alert E-mail. The Set Alert E-Mail dialog box is
displayed.

2. Select Enable Alert E-mail.

30 NAS 2000s Administration Guide

3. Indicate the types of messages to be sent.

■ Critical alerts

■ Warning alerts

■ Informational alerts

4. Enter the desired e-mail address in the appropriate boxes.

5. After all settings have been entered, click OK.

Changing System Network Settings

Network properties are entered and managed from the Network menu. Most of these settings
are entered as part of the Rapid Startup process. Settings made from this menu include adding
the NAS 2000s to a domain.

Online help is available for these settings. Figure 8 is an illustration of the Network settings
menu.

Basic Administrative Procedures and Setup Completion

Figure 8: Network menu

31NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

Setup Completion

After the NAS device is physically set up and the basic configuration is established, additional
setup steps must be completed. Depending on the deployment scenario of the NAS device,
these steps may vary.

Additional setup steps may include:

■ Activating the iLO port using the license key

■ Setting up Ethernet NIC teams (optional)

■ Managing system storage

■ Creating and managing users and groups

■ Creating and managing file shares

Each of these setup steps is discussed in the following sections.

Activating the iLO Port Using the License Key

The Remote Desktop feature of the iLO port requires a license key. The key is included with
the product inside the Country Kit. Refer to the iLO Advanced License Pack for activation
instructions.

To access the iLO port, click on HP Utilities, then click Remote Management.

Setting up Ethernet NIC Teams (Optional)

The NAS 2000s is equipped with the HP Network Teaming and Configuration utility. The
utility allows administrators to configure and monitor Ethernet network interface controllers
(NIC) teams in a Windows-based operating system. These teams provide options for
increasing fault tolerance and throughput.

Fault tolerance provides automatic redundancy. If the primary NIC fails, the secondary NIC
takes over. Load Balancing provides the ability to balance transmissions across NICs.

Note: The NAS server ships with the NIC teaming utility available, however it must be installed and

configured.

Note: Installing NIC teaming requires a restart of the server.

Procedures include:

■ Installing the HP Network Teaming utility

■ Opening the HP Network Teaming utility

■ Adding and configuring NICs in a team

■ Configuring the NIC team properties

■ Checking the status of the team

■ NIC teaming troubleshooting

32 NAS 2000s Administration Guide

Installing the HP Network Teaming Utility

Before using the HP Network Teaming utility, it must be installed.

Note: Installing and configuring NIC teaming should always be performed via iLO port or the

console using a direct attached keyboard, monitor, and mouse since IP connections could be reset
during the configuration process. Do not use Remote Desktop.

To install the HP Network Teaming utility:

1. In the URL field of the Web browser, enter the IP address of the Integrated Lights-Out
port.

Note: The iLO port requires a license key. The key is included with the product inside the Country

Kit. Refer to the iLO Advanced License Pack for activation instructions.

Note: The iLO port can also be accessed from the HP Utilities tab of the WebUI by clicking the

remote management link.

Basic Administrative Procedures and Setup Completion

2. At the Integrated Lights-Out Account Login screen, supply the username and password for
the iLO and click Login.

3. Click the Remote Console tab. The Remote Console Information screen is displayed.

4. Click on the Remote Console choice in the menu on the left side of the screen.

5. Press the Ctrl-Alt-Del button to login to the console.

6. Supply an administrator username and password. The NAS server desktop is displayed.

7. Double-click the HP Network Teaming Setup icon on the desktop.
If the icon is not displayed, enter the following command after selecting Start/Run:

c:\winnt\bin\nicteam\EN\cpqsetup.exe (English)
c:\winnt\bin\nicteam\JP\cpqsetup.exe (Japanese)

8. When the following message box is displayed, click Install.

Figure 9: Installing Network Teaming

9. When the installation process is complete, the following screen is displayed. Click Close.

33NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

Figure 10: Network Teaming installation complete

10. Restart the system.

Caution: To ensure proper functioning of the software, the server must be restarted at

this time.

Opening the HP Network Teaming Utility

The HP Network Teaming utility is now accessible from the Windows toolbar at the bottom of
the NAS server desktop. To open the utility, click the HP Network Teaming utility icon.

Figure 11: HP Network Teaming utility icon

34 NAS 2000s Administration Guide

Adding and Configuring NICs in a Team

Before a NIC is teamed, verify the following:

■ The NICs must be on the same network.

■ The NICs must be DHCP enabled and the DNS server address must be left blank.

Note: The teaming utility becomes unstable if static IP addresses, subnets, and DNS addresses are

set before teaming.

■ Duplex and speed settings must be set to use the default values.

To team the NICs:

1. Open the HP Network Teaming utility. The Network Teaming and Configuration
Properties dialog box is displayed. The type of NIC and the slot and port used is shown.

Basic Administrative Procedures and Setup Completion

Figure 12: HP Network Teaming Properties dialog box

2. Highlight the NICs to team.

3. Click the Te am button. The Teaming Controls tab of the Properties dialog box is
displayed.

35NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

Figure 13: NIC Properties, Teaming Controls tab, Fault Tolerant option

4. Configure the team by choosing either Fault Tolerant or Load Balancing.
The fault tolerance and load balancing options are discussed in the following sections.

Fault Tolerance

The Fault Tolerance teaming option provides three redundancy control options:

■ Manual—This setting allows change from a Primary NIC to a Secondary NIC only when

Switch Now is clicked.

Note: The Switch Now option is disabled until Manual is selected and then OK is clicked.

■ Fail on Fault—This setting automatically switches from a primary NIC to a secondary

NIC when the primary NIC fails.

■ Smart Switch—This setting lets a member of a team be selected as the preferred Primary

Smart Switch NIC. As long as this NIC is operational, it is always the active NIC. If the
NIC fails and it is eventually restored or replaced, it automatically resumes its status as the
active NIC.

Note: Smart Switch is the recommended choice for fault tolerance.

Detailed information about configuring teams for fault tolerance can be found in the HP
Network Teaming utility help.

36 NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

Load Balancing

The Load Balancing teaming option provides four load balancing control options:

Figure 14: NIC Properties, Teaming Controls tab, Load Balancing option

Detailed information about these four load balancing teaming options can be found in the HP
Network Teaming Help.

■ Transmit Load Balancing—All transmit IP frames are load balanced among all team

members based on a Load Balancing algorithm in the teaming device driver. The Current
Primary adapter transmits all other frames, and receives all frames for the team. If a
failover event occurs, one of the non-Primary adapters assumes the role of Current
Primary adapter, and transmit IP packets are load balanced among all remaining team
members. If a failure occurs in any of the non-Primary adapters, the packets are load
balanced among all remaining team members.

■ Switch-assisted Load Balancing—All transmit packets are load balanced among all team

members based on a Load Balancing algorithm in the teaming device driver. The receive
packets are load balanced among all team members by the switch. If a failure of any team
member occurs, the packets are load balanced among the remaining adapters. There is no
primary adapter in a Switch-assisted Load Balancing team.

■ Balance with MAC Address—This feature allows load balancing of IP packets among

the teamed NICs using the last four bits of the MAC Address. (See following Note.)

■ Balance with IP Address—This feature allows load balancing of IP packets among the

teamed NICs using the last four bits of the IP Address. (See following Note.)

Note: The teaming utility can load balance IP packets among the teamed NICs installed in a server.

The primary NIC in the team receives all incoming packets. The choice is available to load balance
with the source MAC address (the address transmitted from the workstation) or the source IP address.

Using the last four bits of either source address, the teaming driver algorithm assigns this source
address to the port of one of the NICs in the team. This port is then used to transmit all packets
destined for that source address. If there are four NICs in the team, the packets are received by the
primary NIC on the team. The packets are retransmitted through one of the four ports.

37NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

5. Click OK to accept the team properties.

6. Click OK in the HP Network Teaming and Configuration Properties Screen to apply the
changes.

7. Click Ye s when prompted to apply all configuration changes. Wait while the adapters are
configured. This process could take several seconds.

8. The following screen is displayed, indicating that there are additional procedures to
perform in the NIC teaming process. Click Ye s to reboot now.

Figure 15: HP Network Teaming dialog box

Configuring the NIC Team Properties

At this point, the NICs are teamed but are not completely configured. Additional procedures
include:

■ Renaming the teamed connection

■ Selecting the option to show an icon on the taskbar

■ Configuring TCP/IP on the new team

Renaming the Teamed Connection

The assigned name for the new NIC team connection is “Local Area Connection X,” where X
represents the next available connection number generated by the system. HP recommends
changing this name to a more meaningful name, such as “NIC Team.”

To change the name of the connection:

1. From the desktop, right-click the My Network Places icon, then click Properties. The
Network and Dial up Connections screen is displayed.

2. Move the cursor over each connection icon to view the pop up box of the icon's name.
Locate HP Network Teaming Virtual Miniport.

3. Right-click the connection icon for HP Network Teaming Virtual Miniport, and select
Rename. Enter a name that is more descriptive than “Local Area Connection X,” such as
“NIC Team.”

38 NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

Showing a Connection Icon on the Taskbar

To show a connection icon:

1. In the Network and Dial up Connections screen, double-click the NIC Team
connection, and then click Properties.

2. At the bottom of the screen, select Show icon in task bar when connected, and then click
Close.

Configuring the TCP/IP Protocol on the New Team

After teaming the NICs, a new virtual network adapter for the team is automatically created.
However, by default the new adapter is set to DHCP. To manually configure the IP address,
perform the following steps.

To enter the TCP/IP address information for the team:

1. From the desktop, go to the Network and Dial up Connections screen and click
Properties. Right-click the NIC Team icon and then select Properties. A screen similar
to the following is displayed.

Figure 16: NIC Team Properties dialog box

2. Use the arrows and the scroll bar on the right of the screen to scroll through the
Components list.

39NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

3. Click Internet Protocol (TCP/IP) and then click Properties. The following screen is
displayed:

Figure 17: NIC Team TCP/IP Properties dialog box

Note: If a NIC is teamed, do not modify the TCP/IP settings for the individual NIC ports.

4. Select Use the following IP address, and enter the IP address and subnet mask. If desired,
enter the default gateway.

5. Click OK. The Ethernet Team should be working.

40 NAS 2000s Administration Guide

Checking the Status of the Team

To check the status of the Ethernet Team, open the HP Network Teaming utility. The
Configuration Properties screen is displayed, showing the teamed NICs.

Basic Administrative Procedures and Setup Completion

Figure 18: NIC Teaming status

NIC Teaming Troubleshooting

Problems with the NIC teaming feature are diagnosed by the connection icons displayed in the
HP Network Teaming and Configuration dialog box. The following table lists the error
icons for RJ 45 NICs.

Table 2: NIC Teaming Troubleshooting

RJ-45 Description

Active OK—The NIC is operating properly. The driver is installed in the registry
and is loaded. If the NIC is a member of a team, the NIC is active.

Installed inactive—The NIC is installed and is OK, but is not active.

Cable fault—The driver is installed in the registry and is loaded. The broken
cable indicator means that the cable is unplugged, loose, broken, or the switch
or hub is not operating properly. If this icon is displayed, check all network
connections and make sure the hub/switch is working properly. When the
connection is restored, this icon will change.

Inactive cable fault—A cable fault has occurred while the NIC was inactive.

41NAS 2000s Administration Guide

Basic Administrative Procedures and Setup Completion

Table 2: NIC Teaming Troubleshooting

RJ-45 Description

Hardware failure—The driver is installed in the registry and is loaded. The
driver is reporting a hardware problem with the NIC. This indicates a serious
problem. Contact your HP authorized service provider.

Unknown—The server is unable to communicate with the driver for the
installed NIC. The NIC is installed in the registry, but the driver is not. This error
occurs when the NIC has been installed but the server has not been restarted.
If this problem persists after the server has been restarted, the driver has not
been loaded or the Advanced Network Control utility is unable to
communicate with the driver.

Note: Only NICs assigned as members of a team are displayed as Unknown.

If a teamed NIC is turned off, it displays as Unknown.
Disabled—The NIC has been disabled through the Device Manager or NCPA.

For more advanced problems with NIC teaming, refer to the help section in the HP Teaming
and Configuration utility.

Managing System Storage

The NAS administrator uses the Array Configuration Utility (ACU) to manage the storage
hardware, Disk Manager to manage volumes, and Shadow Copies to manage snapshots. See
the following chapters for more detailed information on managing system storage:

■ Chapter 3 provides a storage management overview

■ Chapter 4 discusses disk management procedures

■ Chapter 5 discusses snapshot (shadow copy) management procedures.

■ Chapter 7 discusses folder and share management procedures.

Creating and Managing Users and Groups

User and group information and permissions determine whether a user can access files. If the
NAS device is deployed into a workgroup environment, this user and group information is
stored locally on the device. By contrast, if the NAS device is deployed into a domain
environment, user and group information is stored on the domain.

To enter local user and group information, see Chapter 6.

Creating and Managing File Shares

Files shares must be set up, granting and controlling file access to users and groups. See
Chapter 7 for complete information on managing file shares.

UNIX specific information is discussed in the “Microsoft Services for NFS” chapter.

42 NAS 2000s Administration Guide

Storage Management Overview

With the HP StorageWorks NAS 2000s the administrator has complete control over all storage
issues. The NAS administrator uses the Array Configuration Utility (ACU) to manage the
hardware storage, Disk Manager to manage the volume level, and Shadow Copies to manage
the shadow copies (snapshots).

The NAS 2000s is configured at the factory with default system settings and with the NAS
operating system installed. Storage, however, is not pre-configured, allowing the NAS
administrator to tailor the organization and configuration of the storage to specific
environmental needs. Refer to the “Storage Management Process” section later in this chapter
for more information.

This chapter defines and discusses physical, logical, and snapshot storage concepts on the HP
StorageWorks NAS 2000s.

Additional storage management information is included in the following chapters:

■ Chapter 4 discusses disk management procedures

■ Chapter 5 discusses snapshot (shadow copy) management procedures.

■ Chapter 7 discusses folder and share management procedures.

3

Storage Management Process

The lowest level of storage management occurs at the physical drive level. Physical drives are
grouped into arrays for better performance and fault tolerance.

The arrays are then configured with RAID fault tolerance and presented to the operating
system as logical drives or units, which are called LUNs.

At the virtual level of storage, Disk Manager is used to take the LUNs and create basic or
dynamic disks, which can then be broken down into partitions or volumes. Folders, subfolders,
and file shares are created on the resulting volumes or partitions to organize, store, and give
access to the data. The Shadow Copies utility is used to create snapshots of the data at specific
times.

For organizational and documentation purposes, this administration guide separates physical
storage from logical storage.

See Figure 19 for an illustration of these storage management elements.

43NAS 2000s Administration Guide

Storage Management Overview

Physical Disks

RAID Arrays

(ACU)

Storage
Elements

Logical Drives

(ACU)

Visible Disks

(Windows Device
Manager)

\Engineering
\Marketing

Q:

Q:

Q:

@GMT-2003.04.27-04:00:00

@GMT-2003.04.28-04:00:00

\Users
\Sales
\Marketing
\Engineering
\Snapshot.0
\Snapshot.1

R:

\Users \Sales

Figure 19: Storage Management process

Partitioning

(Win2K
Disk Manager)

NFS Volumes

(Logical Disk
Manager)

File Folders

Shadow Copies

(Snapshots)

CIFS/SMB and
NFS File Shares

Logical
Storage
Elements

File
System
Elements

Shadow Copies
Elements

File
Sharing
Elements

44 NAS 2000s Administration Guide

Storage Elements Overview

Note: Each fully populated HP StorageWorks 4300/4400 Family storage enclosure supports up to

14 hard drives.

Preliminary physical storage management tasks involve managing:

■ Physical Hard Drives

■ Arrays

■ Logical Drives (LUNs)

Drive array concepts and data protection methods, including fault tolerance options are
discussed in this section. This information will help guide decisions on how to best configure
the arrays.

Physical Hard Drives

For personal or small business use, the capacity and performance of a single hard drive is
adequate. However, larger businesses demand higher storage capacities, higher data transfer
rates, and greater security from data loss if drives fail.

Storage Management Overview

Arrays

Merely adding extra drives to the system increases the total storage capacity, but has little
effect on the system efficiency, because data can only be transferred to one hard drive at a time.

Figure 20 illustrates the read/write process with separate physical hard drives.

R/W

P1 P2 P3

Figure 20: Separate physical drive (P1, P2, P3) read/write (R/W) operations

With an array controller installed in the system, the capacity of several physical drives can be
logically combined into one or more logical units 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.

45NAS 2000s Administration Guide

Storage Management Overview

Figure 21: Configuring the physical drives into an array dramatically improves read/write
efficiency

Because the read/write heads are active simultaneously, the same amount of data is written to
each drive during any given time interval. Each unit of data is termed a block. The blocks form
a set of data stripes over all the hard drives in an array, as shown in Figure 22.

L1

P1 P2 P3

S1

S2

S3

S4

B1

B4

B7

B2

B5

B8

B11B10 B12

B3

B6

B9

Figure 22: RAID 0 (data striping) (S1-S4) of data blocks (B1-B12)

For data in the array to be readable, the data block sequence within each stripe must be the
same. This sequencing process is performed by the array controller, which sends the data
blocks to the drive write heads in the correct order.

A natural consequence of the striping process is that each hard drive in a given array will
contain the same number of data blocks.

Note: If one hard drive has a larger capacity than other hard drives in the same array, the extra

capacity is wasted because it cannot be used by the array.

46 NAS 2000s Administration Guide

Logical Drives (LUNs)

As previously stated, drive array technology distributes data across a series of individual hard
drives to unite these physical drives into one or more higher performance arrays. Distributing
the data allows for concurrent access from multiple drives in the array, yielding faster I/O rates
than non arrayed drives.

While an array is a physical grouping of hard drives, a logical drive is the configuration of the
arrays that is presented to the operating system.

When planning to allocate space on the NAS device, consider that the maximum number of
LUNs in a dynamic disk is 32 and the largest single LUN that can be utilized by the operating
system is 2 TB. It should also be noted that the largest basic disk that can exist is 2 TB and the
largest volume that can exist is 64 TB. Format of the partition or volume impacts the largest
file system that can exist as well.

HP recommends creating one logical drive from the array. After the physical drives are
grouped into arrays, they are ready to be converted into logical drives.

It is important to note that a LUN may extend over (span) all physical drives within a storage
controller subsystem, but cannot span multiple storage controller subsystems.

After a LUN has been created, it is possible to extend the size, either through the HP Array
Configuration Utility or via Disk Management. See chapter 4 for additional information.

Storage Management Overview

Note: After a LUN has been extended, you must go into Disk Manager to allocate that space.

A1

L1

L2

Figure 23: 2 arrays (A1, A2) and 5 logical drives (L1 through L5) spread over 5 physical drives

A2

L3
L4

L5

Drive failure, although rare, is potentially catastrophic. For example, in the previous figure
using simple striping, failure of any hard drive will lead to failure of all logical drives in the
same array, and hence to data loss.

To protect against data loss from hard drive failure, arrays should be configured with fault
tolerance. Several fault tolerance methods have been devised and are described in the
following sections.

47NAS 2000s Administration Guide

Storage Management Overview

Fault-Tolerance Methods

Different RAID (redundant array of independent disks) types use different methods of striping
the arrays and different ways of writing data and parity to the drives to offer a variety of fault
tolerance and capacity usage. The RAID methods supported by the NAS 2000s include:

■ RAID 0—Data Striping only, no fault tolerance

■ RAID 1+0—Drive Mirroring and striping

■ RAID 5—Distributed Data Guarding

■ RAID ADG—Advanced Data Guarding (ADG)

Further protection against data loss can be achieved by assigning an online spare to an array.
This hard drive contains no data and is contained within the same storage subsystem as the
other drives in the array. When a hard drive in the array fails, the controller can then
automatically rebuild information that was originally on the failed drive onto the online spare.
This quickly restores the system to full RAID level fault tolerance protection.

Note: The ADG feature is available only with the optional Smart Array 5304/6404 Controller

installed. RAID 1+0 support requires an even number of drives. Refer to Table 3 for more
information.

These fault tolerance methods are discussed in the following paragraphs.

RAID 0—Data Striping

This configuration provides striping of the array to improve read and write performance, but
offers no redundancy of data and therefore no protection against data loss when a drive fails.
However, RAID 0 is useful for rapid storage of large amounts of noncritical data (for printing
or image editing, for example) or when cost is the most important consideration.

When creating RAID 0 arrays, carefully consider how many drives to include in the array.
Statistically, the chance of a drive failure increases with each additional drive that is included
in an array. Based upon laboratory testing, HP recommends including no more than 7 drives in
a RAID 0 array.

See Figure 22 for an illustration of the data striping technique.

Advantages

■ Highest performance method for reads and writes

■ Lowest cost per unit of data stored

■ All drive capacity is used to store data; none is used for fault tolerance

48 NAS 2000s Administration Guide

Disadvantages

■ All data on logical drive is lost if a hard drive fails

■ Cannot use an online spare

■ Data can only be preserved by being backed up to external media

RAID 1+0—Drive Mirroring and Striping

In this configuration, information on one drive is duplicated onto a second drive, creating
identical copies of the information as shown in Figure 24. Therefore, this method provides the
best fault tolerance. RAID 1+0 requires an even number of drives and is the only method for
fault tolerance protection if only two drives are installed or selected for an array. If more than
two drives are in an array, the data is striped across all of the drives in the array.

Storage Management Overview

B1

B2

B3

B4

P1 P2

B1

B2

B3

B4

Figure 24: RAID 1+0 (drive mirroring) of P1 onto P2

This method is useful when high performance and data protection are more important than the
cost of hard drives. The operating system drives are mirrored. If one drive fails, the mirror
drive immediately takes over and normal system operations are not interrupted.

Note: HP supports a configuration that uses RAID 1+0 on the system drives in a two drive RAID

array.

Caution: If two drives being mirrored to each other both fail, data loss occurs.

Advantages

Drive mirroring offers:

■ The highest read and write performance of any fault-tolerant configuration.

■ Protection against data loss if one drive fails.

■ Data preservation in a RAID 1+0 system, when more than one drive fails, as long as none

of the failed drives are mirrored to another failed drive.

49NAS 2000s Administration Guide

Storage Management Overview

Disadvantages

Some disadvantages of drive mirroring are:

■ Increased expense—Since many drives must be used for fault tolerance and hard drives

must be added in pairs.

■ Decreased storage capacity—Only 50% of the total drive capacity is usable.

RAID 5—Distributed Data Guarding

Using this method, a block of parity data (rather than redundant data) is calculated for each
stripe from the data that is in all other blocks within that stripe. The blocks of parity data are
distributed over every hard drive within the array, as shown in the figure below. When a hard
drive fails, data on the failed drive can be rebuilt from the parity data and the user data on the
remaining drives. This rebuilt data can be written to an online spare.

This configuration is useful when cost, performance, and data availability are equally
important.

S1

S2

S3

S4

B1

B3

P5,6

B7

B2

P3,4

B5

B8

P1,2

B4

B6

P7,8

Figure 25: RAID 5 (distributed data guarding) showing parity information (P)

Spreading the parity across all the drives allows more simultaneous read operations and higher
performance than data guarding (RAID 4). If one drive fails, the controller uses the parity data
and the data on the remaining drives to reconstruct data from the failed drive. RAID 5 allows
the system to continue operating with reduced performance until the failed drive is replaced.
However, if more than one drive fails, RAID 5 also fails and all data in the array is lost.

Distributed data guarding uses the equivalent of one drive to store parity information and
requires an array with a minimum of three physical drives. In an array containing three
physical drives, distributed data guarding uses 33 percent of the total logical drive storage
capacity for fault tolerance; a 14 drive configuration uses seven percent.

Note: Given the reliability of a particular generation of hard drive technology, the probability of an

array experiencing a drive failure increases with the number of drives in an array. HP recommends
the number of drives in a RAID 5 array not exceed 14.

50 NAS 2000s Administration Guide

Advantages

Distributed data guarding offers:

■ High read and write performance

■ Protection against data loss if one drive fails

■ Increased usable storage capacity, since capacity equal to only one physical drive is used

to store parity information

Disadvantages

Some disadvantages of distributed data guarding are:

■ Lower write performance than RAID 0 or RAID 1+0

■ Possibility of data loss if a second drive fails before data from the first failed drive has

been rebuilt

RAID ADG—Advanced Data Guarding

RAID ADG is similar to RAID 5 in that parity information is generated (and stored) to protect
against data loss caused by drive failure. With RAID ADG, however, two different sets of
parity data are used. This allows data to still be preserved if two drives fail. As can be seen
from Figure 26, each set of parity data uses up a capacity equivalent to that of one of the
constituent drives, for a total parity usage of two drives of space.

This method is most useful when data loss is unacceptable, but cost must also be minimized.
The probability that data loss will occur when configured with RAID ADG is less than when
configured with RAID 5.

Storage Management Overview

Note: The ADG feature is available only with the optional Smart Array 5304/6404 Controller

installed.

B1

B3

P5,6

Q7,8

Figure 26: RAID ADG (advanced data guarding) with two sets of parity data

B2

P3,4

Q5,6

B7

P1,2

Q3,4

B5

B8

Q1,2

B4

B6

P7,8

Advanced Data Guarding technology offers the best combination of fault tolerance and usable
disk space among RAID levels.

51NAS 2000s Administration Guide

Storage Management Overview

This technology allows the safe deployment of large capacity disk drives and the creation of
very large storage volumes without expensive overhead to protect business critical data. This
technology provides more flexibility in responding to drive failures without the fear of costly
server downtime.

Advance Data Guarding protects against multiple disk failures, while requiring the capacity of
two drives in an array of up to 56 disk drives to be set aside for dual sets of distributed parity
data. It provides data protection greater than RAID 5, and also has the capacity utilization
efficiency similar to RAID 5.

Advantages

■ High read performance

■ High data availability-any two drives can fail without loss of critical data

Disadvantage

■ Relatively low write performance (lower than RAID 5), due to the need for two sets of

parity data

The table below summarizes the important features of the different kinds of RAID supported
by the Smart Array controllers. The decision chart in the following table may help determine
which option is best for different situations.

Table 3: Summary of RAID Methods

Usable drive space
formula

Minimum number of
hard drives

Maximum number of
hard drives

Tolerant of single hard
drive failure?

Tolerant of multiple
simultaneous hard drive
failure?

RAID 0

Striping (no

fault

tolerance)

nn/2(n-1)/n(n-2)/n

1234

N/A N/A 14 56

No Yes Yes Yes

No For RAID

RAID 1+0
Mirroring

1+0, if the
failed drives
are not
mirrored to
each other

RAID 5

Distributed

Data

Guarding

No Yes

(two drives
can fail)

RAID ADG

Advanced

Data

Guarding

52 NAS 2000s Administration Guide

Online Spares

Further protection against data loss can be achieved by assigning an online spare (or hot spare)
to any configuration except RAID 0. This hard drive contains no data and is contained within
the same storage sub system as the other drives in the array. When a hard drive in the array
fails, the controller can then automatically rebuild information that was originally on the failed
drive onto the online spare. This quickly restores the system to full RAID level fault tolerance
protection. However, unless RAID ADG is being used, which can support two drive failures in
an array, in the unlikely event that a third drive in the array should fail while data is being
rewritten to the spare, the logical drive will still fail.

Physical Storage Best Practices

Minimally, choosing the best disk carving strategy includes the following policies:

■ Analyze current corporate and departmental structure.

■ Analyze the current file server structure and environment.

■ Plan properly to ensure the best configuration and use of storage.

— Determine the desired priority of fault tolerance, performance, and storage capacity.
— Use the determined priority of system characteristics to determine the optimal striping

policy and RAID level.

Storage Management Overview

Logical Storage Elements Overview

Logical Storage elements consist of those components that translate the physical storage
elements to the file system elements as presented in Figure 19. The NAS 2000s utilizes the
Disk Manager (DM) to manage the various types of disk presented to the file system. DM has
two types of LUN presentation, basic disk and dynamic disk. Each of these types of disk has
special features that enable different types of management. Through the use of basic disks,
primary partitions or extended partitions may be created. Partitions can only encompass one
LUN. Through the use of dynamic disks, volumes can be created that span multiple LUNS.

DM can be used to convert disks to dynamic and back to basic, and manage the volumes
residing on dynamic disks. Other options include the ability to delete, extend, mirror, and
repair these elements.

The sections below briefly discuss each of these types of representations and the
considerations that need to be observed.

More detailed information regarding DM use can be obtained through the online help of the
tool.

Partitions

Partitions exist as either Primary Partitions or Extended Partitions and can be composed of
only one Basic disk no larger than 2 TB. Basic disks can also only contain up to four primary
partitions, or three primary partitions and one extended partition. In addition, the partitions on
them cannot be extended beyond the limits of a single LUN. Extended partitions allow the user
to create multiple logical drives. These partitions or logical disks can be assigned drive letters
or be mounted as mount points on existing disks. The use of mount points in conjunction with
NFS shares is not supported.

53NAS 2000s Administration Guide

Storage Management Overview

Volumes

When planning dynamic disks and volumes there is a limit to the amount of growth a single
volume can undergo. Volumes are limited in size and are limited to no more than 32 separate
LUNs with each LUN not exceeding 2 terabytes (TB). Volumes also cannot exceed 64 TB of
disk space.

The RAID level of the LUNs included in a volume must be considered. All of the units that
make up a volume should have the same high-availability characteristics. In other words, the
units should all be of the same RAID level. For example, it would be a bad practice to include
both a RAID 1+0 and a RAID 5 array in the same volume set. By keeping all the units the
same, the entire volume retains the same performance and high-availability characteristics,
making managing and maintaining the volume much easier. It should be noted that if a
dynamic disk goes offline, then the entire volume dependent on the one or more dynamic disks
is unavailable. There could be a potential for data loss depending on the nature of the failed
LUN.

Volumes are created out of the dynamic disks and can be expanded on the fly to extend over
multiple dynamic disks if they are spanned volumes. However, once a type of volume is
selected it cannot be altered. For example, a spanning volume cannot be altered to a mirrored
volume without deleting and recreating the volume, unless it is a simple volume. Simple
volumes can be mirrored or converted to spanned volumes. Fault tolerant disks cannot be
extended either. Therefore, selection of the volume type is important. Please note that 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. In general, HP
recommends utilizing the Array controller for the management of fault tolerance over the use
of DM since DM places an additional level of operating system overhead on volumes. If
mount points are utilized, it should be noted that Services for Unix does not support mount
points at this time.

The administrator should carefully consider how the volumes will be carved up and what
groups or applications will be using them. For example, putting several storage-intensive
applications or groups into the same dynamic disk set would not be efficient. These
applications or groups would be better served by being divided up into separate dynamic disks,
which could then grow as their space requirements increased, within the allowable growth
limits.

Utilizing DM Storage Elements

No matter which type of storage element is created in DM the last step in creating the element
is determining its drive letter or mount point and formatting the element. Each element created
can exists as a drive letter(s), assuming one is available and/or as mount points off of an
existing folder of a drive letter. Either method is supported. However, mount points can not be
utilized for shares that will be shared using Microsoft Services for Unix (NFS). They can be
setup with both but the use of the mount point in conjunction with NFS shares causes
instability with the NFS shares.

Formats consist of NTFS, FAT32, and FAT and all three types can be used on the NAS device.
However, the Volume Shadow Copy Service can only utilize volumes that are NTFS
formatted. Also, quota management is possible only on NTFS.

54 NAS 2000s Administration Guide

Volume Shadow Copy Service Overview

The Volume Shadow Copy Service (VSS) provides an infrastructure for creating point-in-time
snapshots (shadow copies) of volumes. VSS supports 64 shadow copies per volume.

Shadow Copies of Shared Folders resides within this infrastructure and helps alleviate data
loss by creating shadow copies of files or folders that are stored on network file shares at
pre-determined time intervals. In essence, a shadow copy is a previous version of the file or
folder at a specific point in time.

By using shadow copies, a NAS 2000s server can maintain a set of previous versions of all
files on the selected volumes. End users access the file or folder by using a separate client
add-on program, which enables them to view the file in Windows Explorer.

Shadow copies should not replace the current backup, archive, or business recovery system,
but they can help to simplify restore procedures. For example, shadow copies cannot protect
against data loss due to media failures, however, recovering data from shadow copies can
reduce the number of times needed to restore data from tape.

Detailed information on Shadow Copies can be found in Chapter 5 of this guide.

File System Elements

Storage Management Overview

File system elements are composed of the folders and subfolders that are created under each
Logical Storage element (partitions, logical disks, and volumes). Folders are used to further
subdivide the available file system providing another level of granularity for management of
the information space. Each of these folders can contain separate permissions and share names
that can be used for network access. Folders can be created for individual users, groups,
projects, and so on.

Detailed information on file system elements can be found in Chapter 7 of this guide.

File-Sharing Elements

The NAS 2000s supports several file sharing protocols, including DFS, NFS, FTP, HTTP, and
Microsoft SMB. On each folder or Logical Storage element, different file sharing protocols
can be enabled using specific network names for access across a network to a variety of
clients. Permissions can then be granted to those shares based on users or groups of users in
each of the file sharing protocols.

Detailed information on file-sharing elements can be found in Chapter 7 of this guide.

55NAS 2000s Administration Guide

Storage Management Overview

56 NAS 2000s Administration Guide

Disk Management

Disk Management is core to the Windows NAS product. The process of creating storage
elements and presenting them to the NAS OS is facilitated by the use of the WebUI. This
chapter documents the contents of the WebUI for disks and volume management.

WebUI Disks Tab

The online Storage Guide provides an overview of the storage management process as a
supplement to this administration guide.

The primary web page for facilitating disks and volume creation is illustrated in Figure 27.
The figure in the diagram illustrates the process of creating arrays, volumes, and shadow
copies. The diagram on the left illustrates the logical steps used to manage disks, beginning
with the ACU at the top. The process follows the diagram from top to bottom and the
selectable menu items from left to right on the page:

1. Create arrays and logical drives via ACU.

4

2. Create Windows 2003 disks via Disk Manager.

3. Create volumes via the WebUI.

57NAS 2000s Administration Guide

Disk Management

To manage disks and volumes via the WebUI, click on Disks.

Figure 27: Disks menu

The Disks tab contains the following task items for configuring the NAS device:

Table 4: Disks Tab Options

Option Task

Array Configuration Utility (ACU) Configure SCSI array controllers installed inside or

connected to the NAS system. Arrange individual physical
disks as RAID arrays, and create logical disks from those
arrays.

Disks Manage logical disks. Observe disk capacity and status,

Volumes Manage disk space usage by enabling quotas, scheduling

Shadow Copies Manage shadow copies of shared folders on the volume.

Storage Guide Provides a detailed list of the procedures required to

scan for new disks, view detailed disk properties, create new
volumes by launching the advanced Disks Management
interface.

disk defragmentation, and performing detailed volume
management using the Manage item.

Shadow copies are read-only copies of shared data that
provide users with a way to view, and, if necessary, restore
to previous versions of files.

configure and create disks and volumes on NAS devices.

58 NAS 2000s Administration Guide

Storage Configuration Overview

Physical disks can be arranged as RAID arrays for fault tolerance and enhanced performance,
then segmented into logical disks of appropriate sizes for particular storage needs. These
logical disks then become the volumes that appear as drives on the NAS server.

Step 1: Create Disk Arrays

1. Click Array Configuration Utility on the Disks tab, and log in as an administrator to the
Remote Desktop session.

The Remote Desktop session automatically runs the Array Configuration Utility.

2. Select the proper array controller in the left pane of the interface before beginning array
configuration. Some NAS systems are equipped with array controllers for both internal
and external storage.

Consult the Help available in ACU for details on creating arrays, if necessary.

Step 2: Create Logical Disks from the Array Space

Continue using the ACU from the Disks tab.

1. Select a previously created array.

2. Click Create Logical Drive from the right pane of the ACU.

3. Complete the logical drive creation wizard to designate some or all of the array space as a
logical disk.

Disk Management

Depending on how many physical disks are included in the array, several different types of
logical disks are possible. Consult the ACU Help for details on creating logical disk drives.

Step 3: Verify newly created logical disks

1. Click Disks on the Disk tab.

2. Click Rescan to scan for newly created logical disks.

3. Verify that disks matching the newly created sizes are displayed.

Step 4: Create a Volume on the new logical disk

1. Click Vo lu m es on the Disks tab.

2. Click Manage.

3. Click Create New.

4. Log into the Remote Desktop session as an administrator.
The Remote Desktop session automatically runs the Disk Management interface.

5. In Disk Management, select one of the disk items representing the logical disk created
previously with the ACU.

6. Initialize the disk as a basic or dynamic disk by right-clicking the disk item in the lower
left pane of the Disk Management interface.

7. Select the initialized disk, and right-click the unallocated space representation.

8. Click New Partition.

9. Use the New Partition Wizard to create a new volume, format a filesystem, and mount the
volume on a drive letter or subdirectory of another mounted volume.

59NAS 2000s Administration Guide

Disk Management

Array Configuration Utility

RAID arrays and LUNs are created and can be managed using the HP Array Configuration
Utility.

Features of ACU:

■ Graphical representation of drive array configurations with wizards that help optimize

array configuration

■ Online spare (hot spare) configuration

■ Separate fault tolerance configurations on a logical drive (LUN) basis

■ Easy capacity expansion of arrays

■ Online RAID level and stripe size migration

■ Manages OS and data drives

Each time the Array Configuration Utility is run, it analyzes the configuration of the Array
Controllers installed in the system. From the Main page various options are available to
change or reconfigure the controller(s). This document only covers a subset of the functions
available in the ACU. For complete documentation on ACU, refer to the comprehensive online
help found within the ACU tool.

Using the ACU to Configure Storage

To configure storage:

1. Open the WebUI and navigate to the Disks tab.

2. Click on Array Configuration Utility. A new browser window opens, displaying the
Systems Management Homepage.

Note: ACU is used to manage and configure array-based storage.

60 NAS 2000s Administration Guide

Disk Management

3. Log into the ACU utility. The default user name is administrator and the default
password is administrator.

Figure 28: Systems Management Homepage

The Array Configuration Utility is displayed.

Figure 29: Array Configuration Utility

4. Select a controller from the list on the left side to begin configuration.

■ The controller named Smart Array 5i Controller in the embedded slot is for all drives

in the server chassis, and drives contained in an external storage enclosure attached to
the Smart Array 5i on the server head if present.

61NAS 2000s Administration Guide

Disk Management

■ The controller named Smart Array 6400 Controller (if present) is used for all

externally SCSI attached storage.

Caution: On the Smart Array 5i controller there are two logical drives pre-configured

under Array A. These two logical drives are configured for the NAS operating system and
should not be altered.

5. After the controller is selected there are three ways to configure the storage:

■ Express Configuration

Select Express Configuration to be asked a few simple questions and allow the
controller to be configured automatically. The Express Configuration is the easiest
and fastest way to configure a controller and will provide the most reasonable
configuration possible.

■ Configuration Wizards

Select Configuration Wizards to configure a controller through a series of wizards,
which provides a guide through the configuration process. Choosing Configuration
Wizards is not the fastest or easiest way to configure a controller, but it does offer
more control over the configuration and provides for a more individualistic setup.

■ Standard Configuration (default)

Select Standard Configuration to quickly configure a controller. Choosing
Standard Configuration is the fastest way to configure a controller but requires an

intermediate to advanced level of knowledge concerning storage. The Standard
Configuration path offers the least amount of help or step-by-step guides and does not
provide a FAQ panel, assuming the user knows exactly what they would like to
accomplish and are very familiar with the concepts required to complete the task.

The default method is the standard configuration method. The steps that follow are for
creating an array using the standard configuration mode.

6. Click Create Array.

7. Select all of the drives to be included in the array and click OK.

8. Select the array that was just created and click on Create logical Drive at the right.

9. Select the desired Fault Tolerance, Stripe Size, and Size of the logical disk, and click OK.
The Fault tolerance level depends on the amount of disks selected when the array was

created. A minimum of two disks is required for a RAID 0+1 configuration, three disks for
a RAID 5 configuration, and four disks for a RAID 5 ADG configuration.

10. After all logical disks have been created, click Save.

11. Click Exit ACU to exit the ACU session.

62 NAS 2000s Administration Guide

ACU Guidelines

Managing Disks

Disk Management

■ Do not modify Array A off of the Smart Array 5i controller as it contains the NAS OS

■ Spanning more than 14 disks with a RAID 5 volume is not recommended

■ Designate spares for RAID sets to provide greater protection against failures

■ RAID sets cannot span controllers

■ A single array can contain multiple logical drives of varying RAID settings.

■ Extending and Expanding Arrays and Logical Drives is supported

■ RAID migration is supported

From the Disks tab of the WebUI, select Disks. The page displays the physical disks that are
associated with the NAS device and the volumes that are created on them. Multiple volumes
may appear on multiple disks depending on whether the volumes are simple, spanned, or
multi-volumes/partitions exist. The page does not display what type of disk (basic or
dynamic). To display this type of information click Advanced Disk Management.

63NAS 2000s Administration Guide

Disk Management

Figure 30: Manage Disks screen

Table 5: Manage Disks Options

Option Task

Rescan Select to detect a new disk added to the system. By default,

Create New Volume Select to open the Windows GUI Disk Management and create

Properties Select to display the properties of the selected disk.
Advanced Disk Management Select to open the Disk Management utility and perform disk

Disk Management Utility

When the Create New Volume or Advanced Disk Management button on the Manage Disks
screen is selected, the Disk Management Utility is opened.

The Disk Management tool is a system utility for managing hard disks and the volumes, or
partitions, that they contain. Disk Management is used to initialize disks, create volumes,
format volumes with the FAT, FAT32, or NTFS file systems, and create fault-tolerant disk
systems. Most disk-related tasks can be preformed in Disk Management without restarting the
system or interrupting users; most configuration changes take effect immediately. A complete
online help facility is provided with the Disk Management Utility for assistance in using the
product.

drives are dynamically recognized by the system. Occasionally
a rescan of the hardware is required. The rescan is not
synchronous and may require a browser refresh after the scan is
initiated to display the new content.

a new volume on a disk that was added to the system. This is
accomplished via Remote Desktop and the Windows GUI Disk
Management

management tasks, such as creating partitions, and changing
basic disks to dynamic disks. Please see the online Disk
Management help pages for complete documentation.

64 NAS 2000s Administration Guide

Disk Management

Figure 31: Disk Management utility

Note: When the Disk Management utility is accessed, the Remote Desktop connection assumes a

dedicated mode and can only be used to manage disks and volumes on the server. Navigating to
another page during an open session closes the session.

Note: It may take a few moments for the Remote Desktop Connection session to log off when closing

Disk Management.

Disk Management Guidelines

When managing disks and volumes:

■ Read the online Disk Manager Help found in the utility.

■ Do not alter the Operating System Disk Labeled Local Disk C:.

■ Do not alter the disk labeled “DON’T ERASE.”

■ The use of software RAID-based dynamic volumes is not recommended; use the array

controller instead, it is more efficient.

■ The largest disk that Windows 2003 Storage Server can accommodate from a storage

system is 2 TB.

■ It is not recommended to span array controllers with dynamic volumes.

■ Use meaningful volume labels with the intended drive letter embedded in the volume

label, if possible. For example, volume e: might be named “Disk E:.” Volume labels often
serve as the only means of identification.

■ Record all volume labels and drive letters in case of system Quick Restore. See

“Managing Disks After Quick Restore” later in this chapter.

65NAS 2000s Administration Guide

Disk Management

Volumes Page

■ When managing basic disks, only the last partition on the disk can be extended unless the

disk is changed to dynamic.

■ Basic disks can be converted to dynamic without bringing the system offline or loss of

data, but the volume will be unavailable during the conversion.

■ Basic disks can contain up to four primary partitions (or three primary partitions and one

extended partition).

■ Format drives with a 16 K allocation size for best support of snapshots, performance, and

defragmentation.

■ NTFS formatted drives are recommend since they provide the greatest level of support for

snapshots, encryption, and compression.

■ Only basic disks can be formatted as FAT or FAT32.

On the Volumes page, administrators can select to manage volumes, schedule
defragmentation, and set or manage quotas. The Volumes page displays all volumes that are
formatted NTFS on the system. It does not display the volume type (for example simple or
spanned) nor volumes that are FAT32 or FAT. To display these types of volumes, click the
Manage or Advanced Disk Management buttons.

See the Managed Disks page to view a list of disks, and the volumes assigned to them. The
drive letters for volumes that encompass multiple disks appear on multiple rows on the display.
For an example, see the volume labeled H: in Figure 30.

66 NAS 2000s Administration Guide

Disk Management

Figure 32: Volumes tab

Table 6: Volumes Page Object/Task Selector

Option Task

Manage... Select to display the Manage Volumes screen.
Schedule Defrag... Select to schedule defragmentation for the selected volume.
Set Default Quota Select to set quota limits to manage use of the volume. Settings on this

page apply to new users and any users for whom user quota entries
have not previously been set.

Set Quota Entries Select to show a list of user quota entries. Then create a new quota entry,

delete a quota entry, or view the properties of a quota entry.

67NAS 2000s Administration Guide

Disk Management

Managing Volumes

To manage volumes on the server:

1. On the primary navigation bar, click Disks.

2. Click Vo lu m es .

3. Select the volume to manage.

4. In the Tasks list, click Manage.

The Manage Volumes screen is displayed. The Manage Volumes page displays all volumes on
the NAS device regardless of their format (NTFS, FAT, or FAT32). Do not tamper with the
“Don’t Erase” or the Local C: volume. These are reserved volumes and must be maintained as
they exist.

Figure 33: Manage Volumes screen

Table 7: Manage Volumes Options

Option Task

Create New Select to open the Disk Utility and create a new volume.

Delete Select to delete the selected volume. This is data destructive

68 NAS 2000s Administration Guide

Create a new volume will open a remote desktop session to
the Windows Disk Manager

and there is no recovery other than from tape.

Dynamic Growth

Disk Management

Table 7: Manage Volumes Options (Continued)

Option Task

Extend Opens a page to extend a partition based on a basic disk

or it opens Windows Disk Management to extend dynamic
based volumes.

Rescan Select to detect a volume or partition added to the system or

to update the size of a volume that has undergone
expansion. The rescan is not synchronous and may require a
browser refresh after the scan is initiated to display the new
content.

Advanced Volume Management Select to open the Windows Disk Manager and perform

advanced volume management tasks.

Dynamic growth is a feature of the NAS 2000s, which provides for growth of a volume or
partition to meet expanding storage requirements without the need to take volumes offline or
incur downtime. Growth may occur in three forms:

■ Extend unallocated space from original LUNS.

■ Alter LUNs to contain additional storage.

■ Add new LUNS to the system. The additional space is then extended into through a variety

of means depending on which type of disk structure is in use.

Expanding a LUN

Expanding an existing LUN is accomplished via the Array Configuration Utility presented on
the Disk page. LUN expansion may occur in Disk Arrays where space is available. If
insufficient space is available, additional physical disks may be added to the array
dynamically.

Figure 34: Expanding a LUN

69NAS 2000s Administration Guide

Disk Management

To extend a LUN where space is available in the array:

1. Click the Disks tab.

2. Click Array Configuration Utility and log in.

3. Select the appropriate array controller and the appropriate array that the logical drive is
contained in.

4. Select the appropriate logical drive.

5. Select Extend Size.

6. Enter the total size of the logical drive in MB (not just the amount to be added) and click
OK.

7. Click Save to update the configuration.

8. Close the ACU.

To extend a LUN where space is not available in the array

1. Add an unassigned physical disk to the array using the ACU. If an unassigned physical
disk is unavailable, add a new disk to the appropriate storage device and select Refresh.

2. To add an unassigned physical disk to the array use the following steps:
a. Select the appropriate array controller and the appropriate array that the logical drive

is contained in.

b. Select Expand Array.
c. Select the appropriate physical disk and click OK. The array is expanded.

3. Follow the instructions for extending a LUN.

Extending a partition on a basic disk

Partitions can be extended using either the WebUI extend function from the Managed Volumes
page extend selection or by using the DiskPart command line utility. The Windows Disk
Manager cannot extend basic disk partitions. To extend a partition using the WebUI follow the
steps below:

1. Click the Disks tab.

2. Click the Vo lu m es tab.

3. Click Manage.

4. Select the Volume to extend and click Extend.

5. The page in Figure 35 is displayed. Enter in the amount to extend the partition.

70 NAS 2000s Administration Guide

Disk Management

Figure 35: Extending a volume

Extending a Volume on Dynamic Disks

The WebUI allows for the extension of volumes based on a dynamic disk or a set of dynamic
disks. To extend a volume perform the following steps:

1. Click the Disks tab.

2. Click the Vo lu m es tab.

3. Click Manage.

4. Select the volume to extend and select Extend. A remote session to Disk Manager is
started.

5. To extend a given volume, right-click on the desired volume and select Extend.

6. Enter the amount to extend the volume. If no more space is available on the current
dynamic disk, add an additional dynamic disk to the list of available disks and utilize
space from it.

Extending using DiskPart

DiskPart may also be used to extend a partition or volume from the CMD prompt of the NAS
operating system via Remote Desktop. Complete help is available from the Windows 2003
desktop under Start > Help and Support. To use DiskPart follow the steps below:

Connect to the box through remote desktop, login, and select the command prompt icon.

1. Type Diskpart.

2. From the Diskpart prompt type the following commands:

■ Ty pe list to display all of the volumes

■ Ty pe select [name of volume] (for example select Volume 4) to work

against a particular volume or partition.

71NAS 2000s Administration Guide

Disk Management

■ Ty pe Extend. The volume is extended to the capacity of the underlying disk. To

specify the amount to extend or to extend to another disk, type

extend [size=N] [disk=N]

Size is in MB.

■ Ty pe exit to exit the utility.

Scheduling Defragmentation

Defragmentation is the process of analyzing local volumes and consolidating fragmented files
and folders so that each occupies a single, contiguous space on the volume. This allows the
system to access files and folders and save new ones more efficiently. Because
defragmentation consolidates files and folders, it also consolidates the free space on a volume.
This reduces the likelihood that new files will be fragmented.

Defragmentation for a volume can be scheduled to occur automatically at convenient times.
Defragmentation can also be done once, or on a recurring basis.

To schedule defragmentation for a volume:

1. On the primary navigation bar, choose Disks.

2. Click the Vo lu m es tab.

3. Select the volume to schedule defragmentation.

4. In the Tasks list, choose Schedule Defrag.

5. On the Manage the defragmentation schedule for [VolumeName] page, select the
Schedule defragmentation for this volume check box.

6. Select the frequency: Once, Weekly, or Monthly.

7. Use the remaining controls to specify when defragmentation will occur. The available
controls change according to the frequency that is selected.

8. Click OK.

To disable defragmentation for a volume:

1. On the primary navigation bar, click Disks.

2. Click Vo lu m es .

3. Select the volume to disable defragmentation.

4. In the Tasks list, choose Schedule Defrag.

5. On the Manage the defragmentation schedule for [VolumeName] page, clear the
Schedule defragmentation for this volume check box.

6. Click OK.

Note: Scheduling defragmentation to run no later than a specific time prevents the defragmentation

process from running later than that time. If the defragmentation process is running when the time is
reached, the process is stopped. This setting is useful to ensure that the defragmentation process ends
before the demand for server access is likely to increase.

72 NAS 2000s Administration Guide

If defragmenting volumes on which shadow copies are enabled, use a cluster (or allocation
unit) size of 16 KB or larger during the format. Otherwise defragmentation registers as a
change by the Shadow Copy process. This increase in the number of changes forces Shadow
Copy to delete snapshots as the limit for the cache file is reached.

Caution: Allocation unit size cannot be altered without reformatting the drive. Data on a

reformatted drive cannot be recovered.

Note: NTFS compression is supported only if the cluster size is 4 KB or smaller.

Managing Disks After Quick Restore

After a Quick Restore, drive letters may be assigned to the wrong volume. Windows Storage
Server 2003 assigns drive letters after the restoration in the order of discovery. To help
maintain drive letter information, placing the drive letter into the volume label is
recommended. To change the drive letters to the appropriate ones, go into Disk Management
and perform the following steps for each volume.

1. Right-click the on the volume that needs to be changed.

Disk Management

2. Select Change Drive Letter and Paths.

3. In the Change Drive Letter and Paths dialog box, select Change.

Figure 36: Change Drive Letter and Paths dialog box

4. In the Change Drive Letter or Path dialog box, select the appropriate drive letter and then
click OK.

73NAS 2000s Administration Guide

Disk Management

Figure 37: Enter new drive letter

5. Click Ye s to confirm the drive letter change.

Figure 38: Confirm drive letter change

6. If the dialog box in Figure 39 is displayed, select Ye s to continue. If the old drive letter
needs to be reused, reboot the server after clicking Ye s .

Figure 39: Disk Management warning

74 NAS 2000s Administration Guide

Disk Quotas

Disk Management

Disk quotas track and control disk space use in volumes.

Note: To limit the size of a folder or share, see “Directory Quotas” in Chapter 7.

Configure the volumes on the server to perform the following tasks:

■ Prevent further disk space use and log an event when a user exceeds a specified disk space

limit.

■ Log an event when a user exceeds a specified disk space warning level.

When enabling disk quotas, it is possible to set both the disk quota limit and the disk quota
warning level. The disk quota limit specifies the amount of disk space a user is allowed to use.
The warning level specifies the point at which a user is nearing his or her quota limit. For
example, a user's disk quota limit can be set to 50 megabytes (MB), and the disk quota warning
level to 45 MB. In this case, the user can store no more than 50 MB on the volume. If the user
stores more than 45 MB on the volume, the disk quota system logs a system event.

In addition, it is possible to specify that users can exceed their quota limit. Enabling quotas
and not limiting disk space use is useful to still allow users access to a volume, but track disk
space use on a per-user basis. It is also possible to specify whether or not to log an event when
users exceed either their quota warning level or their quota limit.

When enabling disk quotas for a volume, volume usage is automatically tracked from that
point forward, but existing volume users have no disk quotas applied to them. Apply disk
quotas to existing volume users by adding new quota entries on the Quota Entries page.

Enabling Quota Management

When enabling disk quotas on a volume, every user’s disk volume usage is monitored and
treated differently, depending on the quota management settings for the specific user.

To enable quota management on a volume:

1. On the primary navigation bar, click Disks.

2. Click Vo lu m es .

3. Select the volume to manage.

4. In the Tasks list, click Set Default Quota.

5. On the Default Quota for volume page, select Use quota limits to manage use of the
volume.

6. If desired, select Deny disk space to users exceeding quota limit to enable that
restriction.

7. Specify the default quota limit and warning level for new users on this volume.

8. Specify which quota events should be logged.

9. Click OK.

75NAS 2000s Administration Guide

Disk Management

Note: When enabling disk quotas on a volume, any users with write access to the volume who have

not exceeded their quota limit can store data on the volume. The first time a user writes data to a
quota-enabled volume, default values for disk space limit and warning level are automatically
assigned by the quota system.

To disable quota management on a volume:

1. On the primary navigation bar, click Disks.

2. Click Vo lu m es .

3. Select the volume to manage.

4. In the Tasks list, click Set Default Quota.

5. On the Default Quota for (volume) page, clear the check box to Use quota limits to
manage use of the volume.

6. Click OK.

Setting User Quota Entries

The Set User Quotas page allows the administrator to set, delete, or change disk quotas for any
user on the server. To set or change quota entries on the server:

1. On the primary navigation bar, click Disks.

2. Click Vo lu m es .

3. Select the volume to manage.

4. From the Tasks list, click Set Quota Entries.

Figure 40: Setting user quotas

76 NAS 2000s Administration Guide

To create a new user quota entry:

1. Click New Quota Entry.

2. Select a user.

3. Set the limit.

4. Set the warning level.

5. Click OK.

Disk Management

Figure 41: Add new quota entry

To change a quota entry:

1. Select the quota to change.

2. Click Properties.

3. Change the limit.

4. Change the warning level.

5. Click OK.

To delete a quota entry:

1. Select the quota to change.

2. Click Delete.

77NAS 2000s Administration Guide

Disk Management

DiskPart

DiskPart.exe is a text-mode command interpreter that enables the administrator to manage
disks, partitions, or volumes.

When using the list commands, an asterisk (*) appears next to the object with focus. Select an
object by its number or drive letter, such as disk 0, partition 1, volume 3, or volume C.

When selecting an object, the focus remains on that object until a different object is selected.
For example, if the focus is set on disk 0 and volume 8 on disk 2 is selected, the focus shifts
from disk 0 to disk 2, volume 8. Some commands automatically change the focus. For
example, when creating a new partition, the focus automatically switches to the new partition.

Focus can only be given to a partition on the selected disk. When a partition has focus, the
related volume (if any) also has focus. When a volume has focus, the related disk and partition
also have focus if the volume maps to a single specific partition. If this is not the case, focus on
the disk and partition is lost.

Table 8: Common DiskPart Commands

Command Description

add disk

assign

convert basic

convert dynamic

create volume
simple

exit

help

list disk

list partition

list volume

rem

retain

select disk

Mirrors the simple volume with focus to the specified disk.
Assigns a drive letter or mount point to the volume with focus.
Converts an empty dynamic disk to a basic disk.
Converts a basic disk into a dynamic disk. Any existing partitions on

the disk become simple volumes.
Creates a simple volume. After creating the volume, the focus

automatically shifts to the new volume.
Exits the DiskPart command interpreter.
Displays a list of the available commands.
Displays a list of disks and information about them, such as their size,

amount of available free space, whether the disk is a basic or dynamic
disk, and whether the disk uses the master boot record (MBR) or GUID
partition table. The disk marked with an asterisk (*) has focus.

Displays the partitions listed in the partition table of the current disk.
On dynamic disks these partitions may not correspond to the dynamic
volumes on the disk. This discrepancy occurs because dynamic disks
contain entries in the partition table for the system volume or boot
volume (if present on the disk). They also contain a partition that
occupies the remainder of the disk in order to reserve the space for use
by dynamic volumes.

Displays a list of basic and dynamic volumes on all disks.
Provides a way to add comments to a script.
Prepares an existing dynamic simple volume to be used as a boot or

system volume.
Selects the specified disk and shifts the focus to it.

78 NAS 2000s Administration Guide

For a complete list of DiskPart commands, go to the Windows 2003 Desktop on the NAS
device via Remote Desktop and select Start >Help and Support, search on DiskPart.

Example of using DiskPart

The following example shows how to configure a volume on the NAS server.
In the cmd window, type:

c:\>diskpart

DISKPART>Rescan

DISKPART>select disk 2

DISKPART>convert dynamic

DISKPART>REM Create a simple volume

DISKPART>create volume simple size=4000

DISKPART> REM Assign drive letter E: to the volume

DISKPART>assign letter=E

DISKPART>list vol

DISKPART>Exit

Disk Management

79NAS 2000s Administration Guide

Disk Management

80 NAS 2000s Administration Guide

Shadow Copies

Overview

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. While the Shadow Copy mechanism is managed at the server (see the
“Managing Shadow Copy” section in this chapter), previous versions of files and folders are
only available over the network from clients and are seen on a per folder or file level and not as
an entire volume.

The Shadow Copy feature works at the block level. As changes are made to the file system, the
Shadow Copy Service copies out the original blocks to a special cache file, to maintain a
consistent view of the file at a particular point in time. Since the snapshot only contains a
subset of the original blocks, the cache file is typically smaller than the original volume. In the
snapshot’s original form, it takes up no space since blocks are not moved until an update to the
disk occurs.

By using shadow copies, a NAS 2000s server can maintain a set of previous versions of all
files on the selected volumes. End users access the file or folder by using a separate client
add-on program, which enables them to view the file in Windows Explorer. Accessing
previous versions of files, or shadow copies, enables users to:

5

■ Recover files that were accidentally deleted. Previous versions can be opened and copied

to a safe location.

■ Recover from accidentally overwriting a file. A previous version of that file can be

accessed.

■ Compare several versions of a file while working. Use previous versions to compare

changes between two versions of a file.

Shadow copies cannot replace the current backup, archive, or business recovery system, but
they can help to simplify restore procedures. Since a snapshot only contains a portion of the
original data blocks, shadow copies can not protect against data loss due to media failures.
However the strength of snapshots is the ability to instantly recover data from shadow copies,
reducing the number of times needed to restore data from tape.

81NAS 2000s Administration Guide

Shadow Copies

Shadow Copy Planning

Before setup is initiated on the server and the client interface is made available to end users,
consider the following:

■ From what volume will shadow copies be taken?

■ How much disk space should be allocated for shadow copies?

■ Will separate disks be used to store shadow copies?

■ How frequently will shadow copies be made?

Identifying the Volume

Shadow copies are taken for a complete volume, but not for a specific directory. Shadow
copies 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.

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. For example, if a user is denied permission
to read a file, that user would not be able to restore a previous version of the file, or be able to
read the file after it has been restored.

Although shadow copies are taken for an entire volume, users must use shared folders to
access shadow copies. Administrators on the local server must also specify the
\\servername\sharename path to access shadow copies. If administrators or end users want to
access a previous version of a file that does not reside in a shared folder, the administrator
must first share the folder.

Note: Shadow copies are available only on NTFS, not FAT or FAT32 volumes.

Files or folders that are recorded by using Shadow Copy appear static, even though the original
data is changing.

82 NAS 2000s Administration Guide

Allocating Disk Space

When shadow copies are enabled on a volume, the maximum amount of volume space to be
used for the shadow copies can be specified. The default limit is 10 percent of the source
volume (the volume being copied). The limit for volumes in which users frequently change
files should be increased. Also, note that setting the limit too low causes the oldest shadow
copies to be deleted frequently, which defeats the purpose of shadow copies and frustrates
users.

If the frequency of changes to each file is greater than the amount of space allocated to storing
shadow copies, then no shadow copy is created. Therefore, administrators should carefully
consider the amount of disk space they want to set aside for shadow copies, and keep in mind
user expectations of how many versions they will want to have available. End users might
expect only a single shadow copy to be available, or they might expect three days or three
weeks worth of shadow copies. The more shadow copies users expect, the more storage space
administrators must allocate for storing them.

Setting the limit too low also affects Backup and other backup programs that use shadow copy
technology because these programs are also limited to using the amount of disk space
specified by administrators.

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.

Shadow Copies

The minimum amount of storage space that can be specified is 100 megabytes (MB). The
default storage size is 10% of the source volume (the volume being copied). If the shadow
copies are stored on a separate volume, change the default to reflect the space available on the
storage volume instead of the source volume. Remember that when the storage limit is
reached, older versions of the shadow copies are deleted and cannot be restored.

When determining the amount of space to allocate for storing shadow copies, consider both
the number and size of files that are being copied, as well as the frequency of changes between
copies. For example, 100 files that only change monthly require less storage space than 10
files that change daily.

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.

When using a basic disk as a storage area for shadow copies and converting the disk into a
dynamic disk, it is important to take the following precaution to avoid data loss:

■ If the disk is a non-boot volume and is a different volume from where the original files

reside, first dismount and take offline the volume containing the original files before
converting the disk containing shadow copies to a dynamic disk.

■ The volume containing the original files must be brought back online within 20 minutes,

otherwise, the data stored in the existing shadow copies is lost.

■ If the shadow copies are located on a boot volume, the disk to can be converted to dynamic

without losing shadow copies.

83NAS 2000s Administration Guide

Shadow Copies

Note: Use the mountvol command with the /p option to dismount the volume and take it offline.

Mount the volume and bring it online using the mountvol command or the Disk Management
snap-in.

Identifying the Storage Area

To store the shadow copies of another volume on the same file server, a volume can be
dedicated on separate disks. For example, if user files are stored on H:\, another volume such
as S:\ can be used to store the shadow copies. Using a separate volume on separate disks
provides better performance and is recommended for heavily used NAS devices.

If a separate volume will be used for the storage area (where shadow copies are stored), the
maximum size should be changed to No Limit to reflect the space available on the storage area
volume instead of the source volume (where the user files are stored).

Disk space for shadow copies can be allocated on either the same volume as the source files or
a different volume. There is, however, a trade-off between ease of use and maintenance versus
performance and reliability that the system administrator must consider.

For example, by keeping the shadow copy on the same volume, although there is a potential
gain in ease of setup and maintenance, there may be a reduction in performance and reliability.

Caution: If shadow copies are stored on the same volume as the user files, note that a burst

of disk input/output (I/O) can cause all shadow copies to be deleted. If the sudden deletion
of shadow copies is unacceptable to administrators or end users, it is best to use a separate
volume on separate disks to store shadow copies.

Determining Creation Frequency

The more frequently shadow copies are created, the more likely that end users will get the
version that they want. However, with a maximum of 64 shadow copies per volume, there is a
trade-off between the frequency of making shadow copies and the amount of time that the
earlier files will be available.

By default, the NAS 2000s will create shadow copies at 0700 and 1200, Monday through
Friday when the feature is enabled for a volume. However, these settings are easily modified
by the administrator so that the shadow copy schedule can better accommodate end user needs.
To modify these schedules see the section on “Shadow Copy Schedules” documented later in
this chapter.

Note: The more shadow copies are created, the more disk space the shadow copies can consume,

especially if files change frequently.

84 NAS 2000s Administration Guide

Shadow Copies and Drive Defragmentation

When running Disk Defragmenter on a volume with shadow copies activated, all or some of
the shadow copies may be lost, starting with the oldest shadow copies.

If defragmenting volumes on which shadow copies are enabled, use a cluster (or allocation
unit) size of 16 KB or larger. Utilizing this allocation unit size reduces the number of copy outs
occurring on the snapshot. Otherwise the number of changes caused by the defragmentation
process can cause shadow copies to be deleted faster than expected. Note, however, that NTFS
compression is supported only if the cluster size is 4 KB or smaller.

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, backup 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. In addition, if a mounted drive
is shared and shadow copies are enabled on it, users cannot access the shadow copies if they
traverse from the host volume (where the mount point is stored) to the mounted drive.

For example, assume there is a folder E:\data\users, and the Users folder is a mount point for

F:\. If shadow copies are enabled on both E:\ and F:\, E:\data is shared as \\server1\data, and
E:\data\users is shared as \\server1\users. In this example, users can access previous versions
of \\server1\data and \\server1\users but not \\server1\data\users.

Shadow Copies

85NAS 2000s Administration Guide

Shadow Copies

Managing Shadow Copies

From the WebUI Welcome screen, click Disks, then Shadow Copies to display the Shadow
Copies screen.

Figure 42: Shadow Copies screen

Table 9: Shadow Copies Fields

Field Description

Volume Lists all volumes of the server on which the Shadow Copies service can be

used. Only NTFS file system data volumes that are physically located on
the server can support shadow copies. To manage shadow copies on a
volume, select the check box next to the volume name, and then choose a

task from the Tasks list.
Copies Lists the number of shadow copies on the volume.
Used Space Lists the total disk space that is used by the shadow copies on the volume.
Shares Lists the number of shared folders that reside on the volume. This

Next Run Time If the Shadow Copies service is enabled on the volume, this column lists

information can help determine whether to enable shadow copies on a

volume. A greater number of shared folders on a volume increases the

likelihood that users might need access to previous versions of their data.

the time and date the next shadow copy will be created. Otherwise, it

displays Disabled.

86 NAS 2000s Administration Guide

Table 10: Shadow Copies Tasks

Task Description

Enable Click to enable Shadow Copies on the selected volume.
Disable Click to enable Shadow Copies on the selected volume.
New Shadow Copy Click to immediately create a new shadow copy on the selected volume.
View Shadow

Copies
Set Schedule Click to set the time and frequency of shadow copies.
Properties... Click to view the shadow copy properties of the selected volume,

Manage Shares Click to go to the Shared Folders screen.

The Shadow Copy Cache File

The default shadow copy settings allocate 10% of the source volume being copied (with a
minimum of 100 MB), and store the shadow copies on the same volume as the original
volume. See Figure 43. The cache file is located in a hidden protected directory entitled
“System Volume Information” off of the root of each volume for which Shadow Copy is
enabled.

Shadow Copies

Click to view a list of shadow copies on the selected volume.

including location and size of the cache file.

E:

cache file

F:

cache file

G:

cache file

Figure 43: Shadow copies stored on source volume

As mentioned previously, the cache file location can be altered to reside on a dedicated volume
separate from the volumes containing files shares. See Figure 44.

87NAS 2000s Administration Guide

Shadow Copies

E:

F: G:

L:

cache file
cache file
cache file

Figure 44: Shadow copies stored on separate volume

The main advantage to storing shadow copies on a separate volume is ease of management and
performance. Shadow copies on a source volume must be continually monitored and can
consume space designated for file sharing. Setting the limit too high takes up valuable storage
space. Setting the limit too low can cause shadow copies to be purged too soon, or not created
at all. By storing shadow copies on a separate volume space for Shadow Copies may be
manage separately, limits can generally be set higher, or set to No Limit. See the properties tab
of the shadow copy page for a volume to alter the cache file location, covered later in this
chapter.

Caution: If the data on the separate volume L: is lost, the shadow copies cannot be

recovered.

88 NAS 2000s Administration Guide

Enabling and Creating Shadow Copies

Enabling the Shadow Copies service for a volume or creating a shadow copy can be done
directly from the Manage Shadow Copies page.

Enabling shadow copies on a volume automatically results in several actions:

■ Creates a shadow copy of the selected volume

■ Sets the maximum storage space for the shadow copies

■ Schedules shadow copies to be made at 7 A.M. and 12 noon on weekdays.

Note: Creating a shadow copy only makes one copy of the volume; it does not create a schedule.

To enable shadow copies on a volume:

1. On the primary navigation bar, click Disks.

2. Click the Shadow Copies tab.

3. On the Manage Shadow Copies page, select one or more volumes to enable the Shadow
Copies service on.

Shadow Copies

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” in this chapter.

4. Click Enable.

To create a shadow copy on a volume:

1. On the primary navigation bar, click Disks.

2. Click the Shadow Copies tab.

3. On the Manage Shadow Copies page, select one or more volumes to create the shadow
copies on.

4. Click New Shadow Copy.

Viewing a List of Shadow Copies

To view a list of shadow copies on a volume:

1. On the primary navigation bar, click Disks.

2. Click the Shadow Copies tab.

3. On the Manage Shadow Copies page, select the volume to view.

4. On the Tasks list, click View Shadow Copies.
All shadow copies are listed, sorted by the date and time they were created.

Note: It is also possible to create new shadow copies or delete shadow copies from this page.

89NAS 2000s Administration Guide

Shadow Copies

Set Schedules

Shadow Copy schedules control how frequently shadow copies of a volume are made. There
are a number of factors that can help determine the most effective shadow copy schedule for an
organization. These include the work habits and locations of the users. For example, if users do
not all live in the same time zone, or they work on different schedules, it is possible to adjust
the daily shadow-copy schedule to allow for these differences.

It is recommended that shadow copies be scheduled not more frequently than once per hour.

Scheduling Shadow Copies

When the Shadow Copies service is enabled on a volume, it automatically schedules shadow
copies to be made each weekday at 7 A.M. and 12 noon.

To add or change a shadow copy schedule for a volume:

1. On the primary navigation bar, click Disks.

2. Click Shadow Copies.

3. Select the volume.

4. In the Tasks list, click Set Schedule.

5. On the Shadow Copy Schedules page, click New.

6. Select a frequency: Once, Daily, Weekly, or Monthly.

7. Use the remaining controls to specify the recurrence pattern and the starting date and time.
The available controls change according to the frequency selected.

8. Click OK.

Deleting a Shadow Copy Schedule

To delete a shadow copy schedule on a volume:

1. On the primary navigation bar, click Disks.

2. Click the Shadow Copies tab.

3. Select the volume on which to delete a shadow copy schedule.

4. In the Tasks list, click Set Schedule.

5. On the Manage Shadow Copy Schedules screen, select the schedule to be deleted, and
click Delete.

6. Click OK to confirm the deletion or Cancel to retain the copy.

Note: When deleting a shadow copy schedule, that action has no effect on existing shadow copies.

To remove schedules and all shadow copies in one action, from the Manage Shadow Copies page,
choose Disable from the Tasks list.

Viewing Shadow Copy Properties

To view shadow copy properties on a volume:

1. On the primary navigation bar, click Disks.

2. Click the Shadow Copies tab.

90 NAS 2000s Administration Guide

Shadow Copies

3. On the Manage Shadow Copies page, select the volume on which to view shadow copy
properties.

4. On the Tasks list, click Properties.
The Shadow Copy Properties screen, as shown in Figure 45, lists the number of copies, the

date and time the most recent shadow copy was made, and the maximum size setting.
Change the maximum size limit for all shadow copies, or choose No limit.
For volumes where shadow copies do not exist currently, it is possible to change the

location of the cache file. See “The Shadow Copy Cache File” earlier in this chapter. The
list of available disks and the space available on each is presented at the bottom of the
page. Managing the cache files on a separate disk is recommended.

Note: If shadow copies have already been enabled, the cache file location is grayed out. To change

this location after shadow copies have been enabled, all shadow copies must be deleted and cannot
be recovered. Remember enabling Shadow Copies creates a Shadow Copy by default.

5. Click OK to save changes, or click Cancel to discard changes.

Figure 45: Shadow Copies properties screen

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.

91NAS 2000s Administration Guide

Shadow Copies

Disabling Shadow Copies

When shadow copies are disabled on a volume, all existing shadow copies on the volume are
deleted as well as the schedule for making new shadow copies.

To disable shadow copies on a volume:

1. On the primary navigation bar, click Disks.

2. Click the Shadow Copies tab.

3. On the Manage Shadow Copies page, select one or more volumes on which to disable
shadow copies.

4. In the Tasks list, click Disable.
The Disable Shadow Copies page identifies the volume for which shadow copies will be

disabled.

5. Click OK to delete all existing shadow copies and settings for the volume.

Caution: When the Shadow Copies service is disabled, all shadow copies on the selected

volumes are deleted. Once deleted, shadow copies cannot be restored.

Managing Shadow Copies from the NAS Desktop

As an alternative to managing Shadow Copies via the WebUI, the NAS Desktop may be
accessed via Remote Desktop.

To access Shadow Copies from the NAS Desktop:

1. From the WebUI select Remote Desktop from the Maintenance tab.

2. Click on My Computer.

3. Select the volume.

4. Right-click on the volume name and select Properties.

5. Click the Shadow Copies tab.

The user interface provides the same functionality found in the WebUI but in Win32 form. See

Figure 46.

92 NAS 2000s Administration Guide

Figure 46: Accessing shadow copies from My Computer

Shadow Copies

93NAS 2000s Administration Guide

Shadow Copies

Shadow Copies for Shared Folders

Shadow Copies are accessed over the network by supported clients and protocols. There are
two sets of supported protocols, SMB and NFS. All other protocols are not supported; this
would include HTTP, FTP, AppleTalk, and NetWare Shares. For SMB support a client side
application denoted as Shadow Copies for Shared Folders is required. The client side
application is currently only available for Windows XP and Windows 2000 SP3+. The
application is included on the HP StorageWorks NAS device from the following directory:

C:\hpnas\Components\ShadowCopyClient\XP and 2000-SP3+

No additional software is required to enable UNIX users to independently retrieve previous
versions of files stored on NFS shares.

Note: Shadow Copies for Shared Folders supports retrieval only of shadow copies of network

shares. It does not support retrieval of shadow copies of local folders.

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 on behalf of these users.

SMB Shadow Copies

Windows users can independently access previous versions of files stored on SMB shares via
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 dialog, selecting the Previous Versions tab,
and then selecting the desired shadow copy. Users can view, copy, and restore all available
shadow copies.

Shadow Copies for Shared Folders preserves the permissions set in the access control list
(ACL) of the original folders and files. Consequently, users can only access shadow copies for
shares to which they have access. In other words, if a user does not have access to a share, he
also does not have access to the share's shadow copies.

The Shadow Copies of Shared Folders client pack installs a Previous Versions tab in the
Properties dialog box of files and folders on network shares.

94 NAS 2000s Administration Guide

Shadow Copies

Users access shadow copies with Windows Explorer by selecting View, Copy, or Restore,
from the Previous Versions tab. See Figure 47. Both individual files and folders may be
restored.

Figure 47: Client GUI

When users view a network folder hosted on the NAS device for which shadow copies are
enabled, old versions (prior to the snapshot) of a file or directory are available. 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. Users can view files in the folder history, copy files from the folder history,
and so on.

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
[e-mail]-HH:MM:SS. Note that, to prevent common tools from
needlessly enumerating the pseudo-subdirectories, the name of each pseudo-subdirectory
begins with the dot character, thus rendering it hidden.

The following example shows an NFS share named “NFSShare” with three shadow copies,
taken on April 27, 28, and 29 of 2003 at 4 a.m.

NFSShare
.@GMT-2003.04.27-04:00:00
.@GMT-2003.04.28-04:00:00
.@GMT-2003.04.29-04:00:00

95NAS 2000s Administration Guide

Shadow Copies

Access to NFS shadow copy pseudo-subdirectories is governed by normal access-control
mechanisms using the permissions stored in the file system. Users can access only those
shadow copies to which they have read access at the time the shadow copy is taken. To prevent
users from modifying shadow copies, all pseudo-subdirectories are marked read-only,
regardless of the user's ownership or access rights, or the permissions set on the original files.

Server for NFS periodically polls the system for the arrival or removal of shadow copies and
updates the root directory view accordingly. Clients then capture the updated view the next
time they issue a directory read on the root of the share.

Recovery of Files or Folders

There are three common situations that may require recovery of files or folders:

■ Accidental file deletion, the most common situation.

■ Accidental file replacement, which may occur if a user selects Save instead of Save As.

■ File corruption.

It is possible to recover from all of these scenarios by accessing shadow copies. There are
separate steps for accessing a file compared to accessing a folder.

As documented previously, the use of the snapshots are from the network and are based on
shares created on the NAS server.

On Windows 2000 SP3 clients, snapshot access is not fully functional at the share point of the
network drive. At the sharepoint, a file or folder that is deleted cannot be recovered directly. It
is recommended that end user files exist under a folder below the share point to ensure easy
recovery of their contents and that the file folders not be removed. Therefore recovery is
broken out into two categories, sharepoint and non-sharepoint. This behavior is not evident in
Windows XP or Windows 2003 clients.

96 NAS 2000s Administration Guide

Shadow Copies

Recovering a Deleted File or Folder (non-sharepoint or Windows XP/Windows

2003)

To recover a deleted file or folder within a folder:

1. Navigate to the folder where the deleted file was stored.

2. Position the cursor over a blank space in the folder. If the cursor hovers over a file, that file
will be selected.

3. Right-click the mouse and select Properties from the bottom of the menu. Select the
Previous Versions tab.

4. Select the version of the folder that contains the file before it was deleted, and then click
View.

5. View the folder and select the file or folder to recover. The view may be navigated
multiple folders deep.

6. Select restore to restore the file or folder to its original location. Selecting copy will allow
the placement of the file or folder to a new location.

Figure 48: Recovering a deleted file or folder (non-sharepoint)

97NAS 2000s Administration Guide

Shadow Copies

Recovering a Deleted File or Folder (sharepoint - Windows 2000 SP3 only)

To recover a deleted file or folder at a sharepoint:

1. Navigate to the sharepoint where the deleted file or folder was stored.

2. Recreate the file or folder that was deleted with the exact same name.

3. Right-click the mouse on the newly created file or folder and select Properties from the
bottom of the menu. Select the Previous Versions tab.

4. Select the version of the folder that contains the file before it was deleted, and then click
View.

5. View the folder and select the file or folder to recover. The view may be navigated
multiple folders deep.

6. Select restore to restore the file or folder to its original location. Selecting copy will allow
the placement of the file folder to a new location.

Figure 49: Recovering a deleted file or folder (sharepoint)

In some situations, the name of the folder or file can not be recalled. In this case, if the user has
access to the root or the administrator is available, the following procedure may be followed:

1. Select Start > Run and Type in: \\name_of_server. A window will open with all of the
shares listed on the server.

2. Select the share that the file or folder is missing from.

3. Right-click the mouse on the appropriate share and select Properties from the bottom of
the menu. Select the Previous Versions tab.

4. Select the version of the folder that contains the file or folder before it was deleted, and
then click View.

5. View the folder and select the file or folder to recover. The view may be navigated
multiple folders deep.

6. Select restore to restore the file or folder to its original location. Selecting copy will allow
the placement of the file or folder to a new location.

98 NAS 2000s Administration Guide

Shadow Copies

Figure 50: Viewing root shares

Recovering an Overwritten or Corrupted File

Recovering an overwritten or corrupted file is easier than recovering a deleted file because the
file itself can be right-clicked instead of the folder. To recover an overwritten or corrupted file
use the following procedure:

1. Right-click the overwritten or corrupted file and click Properties.

2. Select Previous Versions.

3. To view the old version, click View. To copy the old version to another location, click
Copy... to replace the current version with the older version, click Restore.

99NAS 2000s Administration Guide

Shadow Copies

Recovering a Folder

To recover a folder use the following procedure:

1. Position the cursor so that it is over a blank space in the folder that will be recovered. If the
cursor hovers over a file, that file will be selected.

2. Right-click the mouse, select Properties from the bottom of the menu, then click the
Previous Versions tab.

3. Choose either Copy or Restore.

4. Choosing Restore enables the user to recover everything in that folder as well as all
subfolders. Selecting Restore will not delete any files.

Backup and Shadow Copies

As mentioned previously, 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
back up in two situations. If the backup software in question supports the use of Shadow
Copies and can communicate with underlying block device, it is supported and the previous
version of the file system will be listed in the backup application as a complete file system
snapshot. Lastly, if the built in backup application NTbackup is utilized, the backup software
forces a snapshot and then uses the snapshot as the means for backup. The user is unaware of
this activity and it is not self evident although it does address the issue of open files.

100 NAS 2000s Administration Guide