Hitachi NAS Platform F1000 Series

Transcription

1 Hitachi NAS Platform F1000 Series Single Node Administrator's Guide Product Version Getting Help Contents MK-92NAS089-05

2 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users. Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries. Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation. AIX, AS/400, DB2, Domino, DS8000, Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM, Lotus, OS/390, RS6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/os, z9, zseries, z/vm, z/ VSE are registered trademarks and DS6000, MVS, and z10 are trademarks of International Business Machines Corporation. All other trademarks, service marks, and company names in this document or website are properties of their respective owners. Microsoft product screen shots are reprinted with permission from Microsoft Corporation. ii

3 Contents Preface...xi Intended audience...xii Product version...xii Release notes...xii Organization of HNAS F manuals...xii Abbreviation conventions...xiii Document conventions...xv Convention for storage capacity values...xv Getting help...xvi Comments...xvi 1 Logging on Logging on to the system Managing system administrator accounts Changing an account password Changing account security settings Managing shared directories Creating a shared directory Sharing HCP data migrated from HNAS F as read-only Changing the policy and schedule for migrating data to HCP Setting conditions for preventing certain files from turning into stub files Expanding the capacity of a file system Limiting the capacity used per file share Limiting the capacity used by a user or group Expanding the capacity used for snapshots Importing data from another file server Importing data from another file server by using the CIFS protocol Importing data from another file server by using the NFS protocol Setting up the access environment from clients Setting up the access environment from CIFS clients Joining a node to an Active Directory domain iii

4 Rejoining an Active Directory domain Joining a node to an NT domain Configuring a workgroup Identifying users by user mapping Collecting CIFS client access logs Setting up the access environment from NFS clients Showing previous data Changing snapshot schedules and other settings Showing previous data on HCP Managing disk capacity Increasing the number of disks Adding internal hard disks to a node Adding LUs to a running storage system Changing the use of disks Deleting a volume group Deleting LUs that are not being used by file systems from a volume group Protecting user data Setting up virus scanning Backing up data to a tape device Restoring data from a tape device Backing up data to a remote site Setting up an environment for Hitachi File Remote Replicator Before setting up the operation environment Setting up the operation environment Setting up an environment for making the latest differential-data snapshot at the secondary site visible Preparations for file share creation at the remote site When all of the conditions are satisfied When the conditions are not satisfied Manually backing up data to the remote site Expanding the capacity of file systems in Hitachi File Remote Replicator Terminating data backup to the remote site Switching operation to a remote site Switching to a remote site during planned outages Planned outages for the primary site Restarting operation after a planned outage at the primary site Switching to a remote site during outages due to failure Unplanned primary site outages Restarting the operation at the primary site after unplanned outages (if you did not delete the HFRR pair at the primary site for failure recovery) Restarting operation at the primary site after unplanned outages (if you deleted the HFRR pair at the primary site for failure recovery) Operation required when changing the settings Backing up system configuration Manually backing up the system configuration Regularly backing up system configuration iv

5 9 Changing the network configuration Changing the IP address of a node Changing the host name of a node Adding and deleting routing information Adding routing information Deleting routing information Changing the negotiation mode Changing the negotiation mode (for a non-cascaded trunk port) Changing the negotiation mode (for a cascaded trunk port) Setting up redundant link configuration Setting link aggregation Setting link alternation Combining link aggregation and link alternation (cascaded trunking) Performing manual link alternation Setting up a VLAN Monitoring the system Using SNMPv Using SNMPv Using error notifications Setting up an environment for command and GUI operations Setting up the SSH environment to use commands Setting up a public key certificate Performing an update installation Updating software Updating software (using the installation file registered in an HCP system) Updating software (using an installation media) A Operations provided by the GUI...A-1 List of operations...a-2 B Basic GUI operation...b-1 Window configuration...b-2 Notes on using the GUI...B-5 C GUI reference...c-1 Task Management dialog box...c-4 Task List page...c-4 Setup Schedule page...c-7 Edit Policy page...c-8 Summary page...c-11 Details (success-list) page...c-15 Details (failure-list) page...c-15 Details (history) page...c-16 System Configuration Wizard...C-17 Service Configuration Wizard...C-19 v

6 Download Chargeback Report dialog box...c-21 Import Files dialog box...c-21 Configure Proxy Server dialog box...c-29 Change User Password dialog box...c-30 Login Security dialog box...c-30 Check for Errors dialog box...c-32 List of RAS Information page...c-32 List of RAS Information page (for List of messages)...c-32 List of RAS Information page (for List of system logs)...c-34 List of RAS Information page (for List of other log files)...c-34 List of RAS Information page (for Batch-download)...C-35 List of RAS Information page (for List of core files)...c-36 List of RAS Information page (for Server check)...c-37 Transfer All Files page...c-37 Dashboard tab...c-37 System Information panel...c-38 Capacity Usage panel...c-39 Namespace Information panel...c-40 Tasks panel...c-41 Panel Configuration dialog box...c-43 host-name window...c-44 Shares window...c-46 File Systems window...c-48 File Systems tab...c-49 Cache Resident tab...c-53 file-system-name window...c-54 Properties tab...c-55 Shares tab...c-56 File Snapshots tab...c-58 Namespace tab...c-64 Monitor tab...c-66 Cache Resident Policy tab...c-67 Volume Groups window...c-67 Hardware window...c-69 Hardware tab...c-72 Network tab...c-74 Memory tab...c-76 tenant-name window...c-76 Namespaces tab...c-77 Properties tab...c-78 Import Files window...c-78 Restart Node dialog box...c-81 System Software Installation dialog box...c-82 Local Users dialog box...c-82 List of Users / Groups page...c-82 Change Password page...c-84 Edit User page...c-84 Add User page...c-85 Batch Operation page...c-86 CSV file format...c-87 Execution results file format...c-89 Edit Group page...c-92 vi

7 Add Group page...c-93 Backup Configuration dialog box...c-94 Save System Settings Menu page...c-95 Save All System Settings page...c-95 Schedule Settings for Saving All System Settings page...c-98 List of Mounted File Systems page...c-99 Upload Saved Data page...c-99 Network & System Configuration dialog box...c-100 System Setup Menu page...c-100 List of Data Ports page...c-102 Negotiation Mode Setup page...c-104 List of Trunking Configurations page...c-107 Link Aggregation Setup page...c-109 Link Alternation Setup page...c-110 List of Interfaces page...c-110 Edit Interface page...c-111 Add Interface page...c-112 DNS, NIS, LDAP Setup page...c-113 List of Routings page...c-115 Add Routing page...c-116 Time Setup page...c-118 Syslog Setup page...c-119 Edit Syslog Setup page...c-120 Add Syslog Setup page...c-120 Log File Capacity Setup page...c-120 Edit File Capacity page...c-121 Core File Auto. Deletion Setup page...c-121 Edit System File page...c-122 Performance Tuning page...c-126 List of SNMPs page...c-127 Edit SNMP page...c-127 Add SNMP page...c-128 Access Protocol Configuration dialog box...c-129 List of Services page...c-129 CIFS Service Management (Basic) page...c-131 CIFS Service Management (User mapping) page...c-133 CIFS Service Management (Security) page...c-140 CIFS Service Management (Performance) page...c-143 CIFS Service Management (Administration) page...c-146 Select Authentication Mode page...c-146 Local Authentication page...c-148 NT Server Authentication page...c-148 NT Domain Authentication page...c-149 Active Directory Authentication page...c-150 Setting Events Logged to the CIFS Access Log page...c-152 FTP Service Management page...c-153 List of Mounted File Systems page...c-157 Select FTP Users page...c-157 NFS Service Management page...c-158 SFTP Service Management page...c-161 Select SFTP Users page...c-164 Public Key List page...c-166 vii

8 Add Public Key page...c-166 CIFS Service Maintenance page...c-167 Virus Scan Server Configuration dialog box...c-175 List of Scanner Servers page...c-176 Edit Scanner Server page...c-178 Add Scanner Server page...c-179 Scan Conditions page...c-179 Scanning software page...c-185 CIFS Protocol Settings dialog box...c-186 NFS Protocol Settings dialog box...c-186 Edit Share dialog box...c-187 Release Share(s) dialog box...c-191 Edit CIFS Share Host or Network dialog box...c-192 Add CIFS Share Host or Network dialog box...c-193 Edit NFS Share Host or Network dialog box...c-193 Add NFS Share Host or Network dialog box...c-195 Add Share dialog box...c-195 Create File System dialog box...c-202 Edit File System dialog box...c-216 Delete File System dialog box...c-224 Custom Schedule Settings dialog box...c-224 Advanced ACL Settings dialog box...c-225 Add Cache Resident Policy dialog box...c-227 Edit Cache Resident Policy dialog box...c-228 Delete Cache Resident Policy dialog box...c-228 Release File Snapshots dialog box...c-229 Delete Snapshot(s) dialog box...c-229 Purge All Snapshots dialog box...c-230 D Operation performed by end users...d-1 List of operations...d-2 Logging on...d-2 Basic GUI operations...d-2 GUI layout...d-2 Notes about using the GUI...D-3 GUI reference...d-3 List of File Shares page (for List of NFS file shares)...d-3 List of File Shares page (for List of CIFS File Shares)...D-4 Display Quota page (for User Quota Info.)...D-4 Display Quota page (for Group Quota Info.)...D-6 Password Setup page...d-8 User Info. Setup page...d-8 E Backing up and restoring quota information...e-1 Backing up quota information...e-2 Output location for files storing quota information when the mount point for a file system is specified as the backup target...e-2 Output location for files storing quota information when a directory under the mount point is specified as the backup target...e-4 Cautions when backing up quota information...e-7 Restoring quota information...e-9 viii

9 Restoring quota information at the file system level...e-9 Restoring quota information at the directory level...e-11 Cautions for restoring quota information...e-12 F Reserved words... F-1 List of reserved words... F-2 G MIB objects...g-1 List of MIB objects...g-2 MIB objects for responding to SNMP get requests...g-3 MIB objects used for SNMP traps...g-71 H Operation reference information...h-1 List of reference information...h-2 I Node maintenance...i-1 Starting and forcibly stopping a node OS...I-2 Starting an OS...I-2 Forcibly Stopping an OS...I-2 Replacing the internal RAID battery...i-2 Managing the RAID card...i-3 J Terminology used in messages and related documents...j-1 Viewing messages and related documents... J-2 K Acronyms...K-1 Acronyms used in the HNAS F manuals...k-2 Glossary Index ix

10 x

11 Preface This manual explains how to operate a Hitachi NAS Platform F (HNAS F) in a single-node configuration. Notice: The use of Hitachi NAS Platform F and all other Hitachi Data Systems products is governed by the terms of your agreement(s) with Hitachi Data Systems. This preface includes the following information: Intended audience Product version Release notes Organization of HNAS F manuals Abbreviation conventions Document conventions Convention for storage capacity values Getting help Comments Preface xi

12 Intended audience This manual is intended for system administrators who operate and manage HNAS F systems in a single-node configuration. Also, the user must have: A basic knowledge of networks A basic knowledge of file sharing services A basic knowledge of CIFS A basic knowledge of NFS A basic knowledge of Windows A basic knowledge of Web browsers In addition to the above, the user must have a basic knowledge of Hitachi Content Platform (HCP) if an HCP system is linked to. If a storage system is connected to, the user must have a basic knowledge of the storage system. Product version This document revision applies to Hitachi NAS Platform F version or later. Release notes Release notes can be found on the documentation CD. Release notes contain requirements and more recent product information that may not be fully described in this manual. Be sure to review the release notes before installation. Organization of HNAS F manuals HNAS F manuals are organized as shown below. Note that whether HNAS F nodes can be set up in a redundant configuration depends on the HNAS F model. A configuration where nodes are made redundant is called a cluster configuration, and a configuration where a node is not made redundant with another node is called a single-node configuration. Which manuals you need to read depends on which configuration you are going to use. Manual name Hitachi NAS Platform F1000 Series Installation and Configuration Guide, MK-92NAS061 You must read this manual first to use an HNAS F system. This manual contains the information that you must be aware of before starting HNAS F system operation, as well as the environment settings for an external server. xii Preface

13 Manual name Hitachi NAS Platform F1000 Series Cluster Getting Started Guide, MK-92NAS076 Hitachi NAS Platform F1000 Series Cluster Getting Started Guide for Virtual NAS, MK-92NAS073 Hitachi NAS Platform F1000 Series Cluster Administrator's Guide, MK-92NAS084 Hitachi NAS Platform F1000 Series Cluster Troubleshooting Guide, MK-92NAS066 Hitachi NAS Platform F1000 Series Single Node Getting Started Guide, MK-92NAS079 Hitachi NAS Platform F1000 Series Single Node Administrator's Guide (This manual) Hitachi NAS Platform F1000 Series Single Node Troubleshooting Guide, MK-92NAS078 Hitachi NAS Platform F1000 Series CLI Administrator's Guide, MK-92NAS085 Hitachi NAS Platform F1000 Series API References, MK-92NAS064 Hitachi NAS Platform F1000 Series Error Codes, MK-92NAS065 Hitachi NAS Platform F1000 Series File System Protocols (CIFS/NFS) Administrator's Guide, MK-92NAS086 This manual explains how to set up an HNAS F system in a cluster configuration. To operate HNAS F on a virtual server, see the Cluster Getting Started Guide for Virtual NAS. This manual explains how to set up virtual servers for HNAS F systems in a cluster configuration. This manual provides procedures for using HNAS F systems in a cluster configuration, as well as provides GUI references. This manual provides troubleshooting information for HNAS F systems in a cluster configuration. This manual explains how to set up an HNAS F system in a single-node configuration. This manual explains the procedures for using HNAS F systems in a single-node configuration, as well as provides GUI references. This manual provides troubleshooting information for HNAS F systems in a single-node configuration. This manual describes the syntax of the commands that can be used for HNAS F systems in a cluster configuration or a single-node configuration. This manual explains how to use the API for HNAS F systems in a cluster configuration or a single-node configuration. This manual contains messages for HNAS F systems in a cluster configuration or a singlenode configuration. This manual contains the things to keep in mind before using the CIFS or NFS service of an HNAS F system in a cluster configuration or a singlenode configuration from a CIFS or NFS client. The Cluster Administrator's Guide and the Single Node Administrator's Guide are available in HTML and PDF formats. All other manuals are available in only PDF format. Abbreviation conventions This manual uses the following abbreviations for product names: Preface xiii

14 Abbreviation Active Directory Dynamic Provisioning Dynamic Tiering HCP HNAS F Internet Explorer Windows Windows NT Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2012 Active Directory(R) Full name or meaning Hitachi Dynamic Provisioning Hitachi Dynamic Tiering Hitachi Content Platform Hitachi NAS Platform F Windows(R) Internet Explorer(R) Microsoft(R) Windows(R) Operating System Microsoft(R) Windows NT(R) Server Network Operating System A generic name for the following: Microsoft(R) Windows Server(R) 2003, Standard Edition Operating System Microsoft(R) Windows Server(R) 2003, Enterprise Edition Operating System Microsoft(R) Windows Server(R) 2003, Datacenter Edition Operating System Microsoft(R) Windows Server(R) 2003, Web Edition Operating System A generic name for the following: Microsoft(R) Windows Server(R) 2003 R2, Standard Edition Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition Microsoft(R) Windows Server(R) 2003 R2, Datacenter Edition A generic name for the following: Microsoft(R) Windows Server(R) 2008 Enterprise Microsoft(R) Windows Server(R) 2008 Enterprise 32-bit Microsoft(R) Windows Server(R) 2008 Standard Microsoft(R) Windows Server(R) 2008 Standard 32- bit Microsoft(R) Windows Server(R) 2008 R2 Enterprise Microsoft(R) Windows Server(R) 2008 R2 Standard A generic name for the following: Microsoft(R) Windows Server(R) 2012 Datacenter Microsoft(R) Windows Server(R) 2012 Essentials Microsoft(R) Windows Server(R) 2012 Foundation Microsoft(R) Windows Server(R) 2012 Standard Microsoft(R) Windows Server(R) 2012 R2 Datacenter Microsoft(R) Windows Server(R) 2012 R2 Essentials xiv Preface

15 Abbreviation Full name or meaning Microsoft(R) Windows Server(R) 2012 R2 Foundation Microsoft(R) Windows Server(R) 2012 R2 Standard Note that this manual may abbreviate Hitachi File Remote Replicator as HFRR when referring to processing specific to Hitachi File Remote Replicator. Document conventions This document uses the following typographic conventions: Convention Bold Italic screen/code Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK. Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file Note: Angled brackets (< >) are also used to indicate variables. Indicates text that is displayed on screen or entered by the user. Example: # pairdisplay -g oradb < > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: # pairdisplay -g <group> Note: Italic font is also used to indicate variables. [ ] square brackets Indicates optional values. Example: [ a b ] indicates that you can choose a, b, or nothing. This document uses the following icons to draw attention to information: Icon Label Note Calls attention to important and/or additional information. Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Convention for storage capacity values Storage capacity values (e.g., drive capacity) are calculated based on the following values: Preface xv

16 Capacity Unit Physical Value Logical Value 1 KB 1,000 bytes 1,024 (2 10 ) bytes 1 MB 1,000 KB or 1,000 2 bytes 1,024 KB or 1,024 2 bytes 1 GB 1,000 MB or 1,000 3 bytes 1,024 MB or 1,024 3 bytes 1 TB 1,000 GB or 1,000 4 bytes 1,024 GB or 1,024 4 bytes 1 PB 1,000 TB or 1,000 5 bytes 1,024 TB or 1,024 5 bytes 1 EB 1,000 PB or 1,000 6 bytes 1,024 PB or 1,024 6 bytes 1 block bytes Getting help The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week. If you need technical support, log on to the Hitachi Data Systems Portal for contact information: Comments Please send us your comments on this document: doc.comments@hds.com. Include the document title, number, and revision, and refer to specific section(s) and paragraph(s) whenever possible. Thank you! (All comments become the property of Hitachi Data Systems Corporation.) xvi Preface

17 1 Logging on This chapter describes how to log on the system. Logging on to the system Logging on 1-1

18 Logging on to the system A system administrator can operate and manage a Hitachi NAS Platform F (HNAS F) system from a Web browser by logging on to the system. To log on to the system 1. Enter the URL in your web browser's address bar, in the following format: F-IP-address-or-host-name/admin/ The Login window appears. 2. Specify a user ID and the password in the Login window, and then click Login. The main window is displayed. Note: If you are accessing the GUI for the first time, use the following account to log on. User ID: admin Password: chang3me! (default) When you access the GUI for the first time, the Change User Password dialog box is displayed (Change User Password dialog box on page C-30). Be sure to change the password to prevent unpermitted access. The user ID and password here are shared with the HNAS F API administrator account. If the password is changed from the API, use the new password. 1-2 Logging on

19 2 Managing system administrator accounts This chapter describes how to manage system administrator accounts. Changing an account password Changing account security settings Managing system administrator accounts 2-1

20 Changing an account password A system administrator can change his or her own password. GUI used for this operation Change User Password dialog box on page C-30 To change an account password 1. In the top-left corner of the GUI, select Action, select Change Password, and then select Change User Password. 2. In the Change User Password dialog box, specify the required information, and then click OK. 3. Make sure that the processing results are correct, and then click Close. Note: Specify a new password that meets the conditions set in the Login Security dialog box, such as the minimum number of characters and the combination of the characters that can be used as a password. The password set here is required for the operation and management of the HNAS F system. Be sure not to forget this password. The password is shared with the HNAS F API administrator account. If the password is changed from the GUI, use the new password in the API. If the current password is lost, use the adminpasswd command to reset the password and then specify a new password. Changing account security settings You can change the session timeout time and the automatic account lockout settings. You can also change the conditions for specifying the system administrator's password to prevent discovery by a third party. These conditions include the minimum number of characters and the combination of the characters that can be specified for the system administrator's password. GUI used for this operation Login Security dialog box on page C-30 To change the account security settings 1. In the top-left corner of the GUI, select Action, and then Login Security. 2. In the Login Security dialog box, specify the required information, and then click OK. 3. Make sure that the processing results are correct, and then click Close. 2-2 Managing system administrator accounts

21 3 Managing shared directories This chapter describes how to manage shared directories. Creating a shared directory Sharing HCP data migrated from HNAS F as read-only Changing the policy and schedule for migrating data to HCP Setting conditions for preventing certain files from turning into stub files Expanding the capacity of a file system Limiting the capacity used per file share Limiting the capacity used by a user or group Expanding the capacity used for snapshots Importing data from another file server Managing shared directories 3-1

22 Creating a shared directory This section explains how to create a shared directory. GUI used for this operation Create File System dialog box on page C-202 To create a shared directory 1. In the top-left corner of the GUI, choose the Resources tab. 2. In the General Tasks area, click Create File System. 3. In the Create File System dialog box, specify a file system name, how to link to the HCP system, the access protocols to be used (CIFS, NFS, or both), the capacity, and other options. To migrate data to the HCP system, specify File system or Subtree for Namespace type, and then specify how to share the HCP data for Content sharing. If you are only migrating data to the HCP system and you are not using HCP data migrated from other HNAS F systems, select Off for Content sharing. If you specify File system for Namespace type, also specify the quota to be allocated to the migration-destination namespace. To share the HCP data with end users of other HNAS F systems (by creating a home-directory-roaming file system), select Home directory for Content sharing, and then specify the information about the migration-destination namespace. When you create a homedirectory-roaming file system, you must specify File system for Namespace type and specify CIFS for the access protocol. Note: If a file system is linked to the HCP system at the share level, you cannot use the Create File System dialog box to create a share or allocate the namespace. After creating the file system, use the Add Share dialog box to add the file share directly below the mount point, and then allocate the namespace to the file share. To periodically acquire the snapshots of a shared directory so that clients can view the past data in the.snaps directory, which is immediately under the shared directory, enable Enable file snapshots. When this item is enabled, you can specify the capacity to be allocated to the differential-data storage device and snapshot acquisition schedules. However, if you specify Home directory for Content sharing, you cannot acquire snapshots. You can also enable single instancing to eliminate duplicate data and save capacity. Single instancing can be enabled by clicking the Enable single instancing. By default, single instancing is enabled on files that are more than 128 KB in size and have not been changed for one week or more. After creating the shared directory, change the setting as necessary in the Task Management dialog box (see Task Management dialog box on page C-4). If execution of the single instancing task takes too much time after system operation starts, use the arcfilterpolicyset command to set the conditions for excluding files from the single 3-2 Managing shared directories

23 instancing targets (filtering policy). However, if you specify Home directory for Content sharing, you cannot enable single instancing. Enable Enable the WORM function if you want to apply WORM which keeps files from being deleted for a specific period of time and automatically sets files that are not accessed for a specific period of time as read-only. However, if you specify Home directory for Content sharing, you cannot enable the WORM functionality. To use version management and allow clients to view the past data as of the time the data was migrated to the HCP system, enable Use file version restore and specify the period of time during which the past data is to be retained. To use CIFS bypass traverse checking, enable CIFS bypass traverse checking. However, if you specify Home directory for Content sharing, you cannot enable CIFS bypass traverse checking. 4. Click OK. 5. Verify the information displayed in the confirmation dialog box, and then click Apply. 6. Make sure that the processing results are correct, and then click Close. Sharing HCP data migrated from HNAS F as read-only This section describes sharing HCP data migrated from HNAS F as read-only. GUI used for this operation Create File System dialog box on page C-202 To share HCP data migrated from HNAS F as read-only 1. In the top-left corner of the GUI, choose the Resources tab. 2. In the General Tasks area, click Create File System. 3. In the Create File System dialog box, specify a file system name, how to link to the HCP system, the access protocols to be used (CIFS, NFS, or both), and the capacity. Note: If a file system is linked to the HCP system at the share level, you cannot use the Create File System dialog box to create a share or allocate the namespace. After creating the file system, use the Add Share dialog box to add the file share directly below the mount point, and then allocate the namespace to the file share. 4. Select On for Content sharing. 5. If you select File System for Namespace type, specify the HCP namespace information that refers to the data. Specify the system information for the HCP namespace whose data you want to show and specify a namespace-access account. If you are using the replication functionality in the HCP system, also specify the system information for the replica HCP system. Managing shared directories 3-3

24 Click Test Connection to check whether you can connect to the HCP. 6. Click OK. 7. Verify the information displayed in the confirmation dialog box, and then click Apply. 8. Make sure that the processing results are correct, and then click Close. Changing the policy and schedule for migrating data to HCP This section explains how to change the policy and schedule for migrating data to the HCP system. GUI used for this operation Task Management dialog box on page C-4 To change a migration policy 1. In the top-left corner of the GUI, select Action, and then Manage Tasks and Policies. 2. In the Task List page in the Task Management dialog box, click (Edit) for a task. 3. In 1. Policy Name in the Edit Policy page in the Task Management dialog box, change the policy description as necessary, and click Next. 4. Change the migration condition in 2. Criteria in the Edit Policy page, as necessary. 5. Click Confirm. To change a migration schedule 1. In the top-left corner of the GUI, select Action, and then Manage Tasks and Policies. 2. In the Task List page in the Task Management dialog box, click (Start) for a task. 3. On the Setup Schedule page in the Task Management dialog box, specify the required information. 4. Click Confirm. Setting conditions for preventing certain files from turning into stub files This section explains how to set conditions (cache resident policies) so that certain files are not turned into stub files when the data in the file system is migrated to the HCP system. 3-4 Managing shared directories

25 After you set conditions for preventing certain files from turning into stub files, file data that satisfies the conditions is always retained in the HNAS F system (cache residency). This causes the access time for these files to be shorter than for stub files. GUI used for this operation file-system-name window on page C-54 Add Cache Resident Policy dialog box on page C-227 To set conditions for preventing certain files from turning into stub files 1. In the top-left corner of the GUI, choose the Resources tab. 2. In a tree on the left side of the GUI, select the triangle icon to the left of the host-name. 3. In a tree on the left side of the GUI, select the triangle icon to the left of File Systems, and then click a file system name. 4. In the file-system-name window, click the Cache Resident Policy tab. 5. In the Cache Resident Policy tab, click the Add. 6. In the Add Cache Resident Policy dialog box, specify the necessary information. Tip: Only files that meet all the conditions set for a policy are prevented from being turned into stub files. If multiple policies are set up, a file is not turned into a stub file if all the conditions in at least one of the policies are met. 7. Click OK. 8. Verify the information displayed in the confirmation dialog box, and then click Apply. 9. Make sure that the processing results are correct, and then click Close. After cache resident policies are set up, tasks for suppressing or recalling stub files are executed everyday at midnight to prevent the files that satisfy the specified conditions from turning into stub files. Expanding the capacity of a file system This section explains how to expand the capacity of a file system in which a shared directory was created. If you want to expand the capacity of a volume group used by a file system, you need to increase the number of disks. For details about how to increase the number of disks, see Increasing the number of disks on page 6-2. GUI used for this operation File Systems window on page C-48 Managing shared directories 3-5

26 Edit File System dialog box on page C-216 To expand the capacity of a file system 1. In the top-left corner of the GUI, choose the Resources tab. 2. In a tree on the left side of the GUI, select the triangle icon to the left of the host-name, and then click File Systems. 3. In the File Systems window, select the file system, and then click Edit. 4. In the Edit File System dialog box, specify the size in Allocate capacity. 5. Click OK. 6. Verify the information displayed in the confirmation dialog box, and then click Apply. 7. Make sure that the processing results are correct, and then click Close. Limiting the capacity used per file share This section explains how to limit the capacity used per file share directly below the mount point when quota is enabled. Before limiting the capacity used per file share Make sure that the file system meets both of the following conditions: Data is not migrated to the HCP system. Single instancing is not enabled. The execution of commands is required for this operation. See Setting up the SSH environment to use commands on page 11-2 to set up a proper environment. To limit the capacity used per file shares 1. Execute the fslist command, and then make sure that the file system is mounted with quotas enabled. Make sure that on is displayed for Quota. If off is displayed for Quota, unmount the file system. Then, execute the fsmount command to enable quotas. 2. Execute the stquotaset command to set a quota for the shared directory. 3. Execute the stquota command to make sure that the quota is properly set for the shared directory. 3-6 Managing shared directories

27 Limiting the capacity used by a user or group This section explains how to limit the capacity used by a user or group when quota is enabled. Before limiting the capacity used by a user or group Make sure that the file system meets both of the following conditions: Data is not migrated to the HCP system. Single instancing is not enabled. The execution of commands is required for this operation. See Setting up the SSH environment to use commands on page 11-2 to set up a proper environment. To limit the capacity used by a user or group 1. Execute the fslist command, and then make sure that the file system is mounted with quotas enabled. Make sure that on is displayed for Quota. If off is displayed for Quota, unmount the file system. Then, execute the fsmount to enable quotas. 2. Execute the quotaset command to set a quota for the user or group. 3. Execute the quotaget command to make sure that the quota is properly set for the user or group. Tip: By using the quotaset command, you can set the default quota to use for users and groups for which a quota is not specifically set. You can also set up quota monitoring, which notifies you when a user or a group has exceeded their soft limit or grace period. Expanding the capacity used for snapshots This section explains how to expand the capacity that is used for snapshots when the storage runs low on space. GUI used for this operation File Systems window on page C-48 Edit File System dialog box on page C-216 To expand capacity that is used for snapshots 1. In the top-left corner of the GUI, choose the Resources tab. 2. In a tree on the left side of the GUI, select the triangle icon to the left of the host-name, and then click File Systems. 3. In the File Systems window, select the file system, and then click Edit. Managing shared directories 3-7

28 4. In File snapshots settings of the Edit File System dialog box, specify the snapshot storage capacity. 5. Click OK. 6. Verify the information displayed in the confirmation dialog box, and then click Apply. 7. Make sure that the processing results are correct, and then click Close. Importing data from another file server This section describes how to use GUIs to import file shares data that is used in another file server to the HNAS F system. You can import data from multiple file servers at the same time. A maximum of 20 file shares can be imported at the same time per HNAS F system. The way of importing data depends on the protocol being used. If you use the CIFS protocol, see Importing data from another file server by using the CIFS protocol on page 3-8. If you use the NFS protocol, see Importing data from another file server by using the NFS protocol on page If the share type of the importsource file server differs from the protocol used for importing data, information including the attribute might not be imported correctly. Use the same protocol as the share type when importing data. Note: To set capacity limitations for each file share, user, or group, command settings are required when an importation starts. Therefore, we recommend you to use commands for importing data if you want to set capacity limitation. For details about how to use commands for importing data from another file server, see the Cluster Administrator's Guide. Importing data from another file server by using the CIFS protocol This section describes how to import data from another file server by using the CIFS protocol. Before importing data, you must set the configuration definitions of the CIFS service. Only files that are in non-worm file system and are accessed by CIFS clients can be imported. The directory path of each file must be no more than 4,095 bytes including the file name. The following information and objects are not imported: File system attributes such as quota and share settings Symbolic links SACL (System ACL) and quota information for files and directories Encryption, compression, and non-indexed attributes for files and directories (The settings are removed.) Accounts that are not registered on the domain controller and accounts other than Everyone, CREATOR_OWNER, or CREATOR_GROUP (when domain authentication is used) 3-8 Managing shared directories

29 The directories and files of the following names:.history,.snaps,.arc,.system_gi,.system_reorganize,.bac kupdates,.temp_backupdates, lost+found,.lost+found System directories that are used by the server and that are in the importsource CIFS shares sometimes fail to be imported. If this happens, revise the owner accounts as well as any other accounts for which file access permissions for the directories that failed to be imported are set, and then perform the importation again. No more than 700 ACEs set for files and directories can be imported. The imported files have archive attributes as DOS attributes. Also, the attributes for NTFS ACL are converted into the corresponding attributes for Advanced ACL. For details about correspondence between NTFS ACL and Advanced ACL attributes, see the File System Protocols (CIFS/NFS) Administrator's Guide. You might not be able to access some differential-data snapshots until importation finishes. Before importation, download the Microsoft Visual C Redistributable Package (x86) from Microsoft Download Center, and then install it on the import-source file server. For details about the user mapping method used when data is imported, see Identifying users by user mapping on page 4-8. GUI used for this operation Import Files dialog box on page C-21 List of RAS Information page on page C-32 Shares window on page C-46 Local Users dialog box on page C-82 DNS, NIS, LDAP Setup page on page C-113 Create File System dialog box on page C-202 To import data from another file server by using the CIFS protocol 1. Create a data access account for importation. Create an account for accessing shared data in an external authentication server. Set up an account so that the account can access all data in the shares to be imported. Specify the account name using no more than 256 characters and the password using no more than 128 characters. You can use alphanumeric characters, sign characters except backslashes (\), and multi-byte characters that are encoded in UTF If some of the import-source files are owned by local accounts, on the import-source file server, verify the local accounts, and then create a mapping file for using the accounts in the HNAS F system. For Microsoft(R) Windows Server(R), use the mapping generation tool (sidlist.exe) to create a mapping file. The mapping generation tool is stored at the following location on the HNAS F installation media. Managing shared directories 3-9

30 installation-media-drive:\tool\sidlist Copy sidlist.exe to a desired directory on the import-source file server, and then run it by specifying the absolute path of sidlist.exe and the mapping file. Example for when sidlist.exe is stored in the tool directory on the D drive: D:\>d:\tool\sidlist.exe >d:\tool\mappingfile.txt Verify the character encoding of the mapping file, and then save the file in the UTF-8 format. The entries are output to a mapping file as follows: [MAPDEF] SID=account-SID SRC_NAME=import-source-account-name KIND=account-type (u (user) or g (group)) DST_NAME=import-target-account-name If you want to use different account names in the HNAS F system than the ones that have been used on the import-source file server, edit the DST_NAME for those accounts. If you use domain accounts, specify the names in domain-name\account-name format. For servers other than Microsoft(R) Windows Server(R), manually create a mapping file containing the above entries for each local account. Verify the character encoding of the mapping file (use UTF-8). 3. Connect the HNAS F system to the network in which the HNAS F system can access the import-source file server. 4. Perform the necessary settings depending on how the import-source files will be accessed. When domain authentication is used Set the same DNS, NIS, and LDAP information for the HNAS F system as the one set for the import-source file server. Set the information so that the name resolution and user authentication work when clients access the HNAS F system in the same way as when clients access the import-source file server. Also set up user and group mapping by the external authentication server. When local authentication is used Register the local accounts that were used on the import-source file server to the HNAS F system. Register the users and groups by using the names for DST_NAME in step 2 and specifying desired UIDs and GIDs. When both domain authentication and local authentication are used Perform the settings necessary for both domain authentication and local authentication. 5. Create and share the import-target file system in the HNAS F system. Note that this step is unnecessary if the import-target file system and file share have already been created Managing shared directories

31 Create a non-worm file system. If you do not want to migrate data to the HCP system, the size of the file system must be at least the same size as the import-source file system. When determining what size to set for the file system, in addition to the size of the files to be imported, consider the size of files that might be created and the decompressed size of compressed files to be imported. If you want to migrate data in the import-target file system to an HCP, set information about the namespace and a migration schedule. Content sharing must be set to off. If you want to migrate data that is stored in the file system and updated during an importation to an HCP, configure settings to periodically migrate the data. However, if data migration starts during an importation, importation of all data is temporarily stopped, and then the importation method is changed to on-demand. This increases the time needed for importing data. To reduce the time needed for importing data, set a migration schedule in step 18 after the importation is completed. Do not create any files or directories in the import-target file system until a importation is started in step 14. If a file or directory path is the same as one in the import-source file system, the file or directory corresponding to that path in the import-source file system is not imported. 6. In the Shares window, select the shared directory created in step 5, and then click Import Files. 7. In the Import Files dialog box, specify the necessary information, and then click Show Plan. 8. Make sure that the information displayed in the confirmation dialog box is correct, and then click Start Scan. Make sure that verification of the import-source files has started, and, if necessary, click Close. 9. In the top-left corner of the GUI, select the Tasks tab. The Import Files window appears. 10. In the Import Files window, check the status of the defined tasks. Make sure that Status is Scan finished. If the Caution icon ( ) is displayed, an error occurred during verification, or some files could not be recognized as verification targets. Click the task name, and display the Import Files dialog box. In the dialog box, click Display Scan Failure List or Display Read Failure List, and check the details about the error. Also, take any necessary action. 11. Notify clients who are using the import-source file server of the importation schedule. 12. Set shares in the import-source file server as read-only. If an import-source file or directory is updated after the import starts, the file or directory might not be properly imported. 13. Use MMC (Microsoft Management Console) (or some other similar tool) to disconnect the session connected to the import-source file server. For details about how to disconnect sessions, see the documentation for the import-source file server. Managing shared directories 3-11

32 14. In the Import Files window, select a task, and then click Start Import. 15. Make sure that the information displayed in the confirmation dialog box is correct, and then click Apply. 16. Inform clients that they can start accessing shares in the HNAS F system. Clients can access the shares in the HNAS F system during data importation. To check the progress of the import, from the Tasks tab, check the Import Files window. In the Import Files window, Import finished is displayed for Status if the import is completed. 17. In the Import Files window, check the results of the import. If the Caution icon ( ) is displayed, an error occurred during the import, or some files could not be recognized as import sources. Click the task name, and display the Import Files dialog box. In the dialog box, click Display Import Failure List or Display Read Failure List, and check the details about the error. If files or directories are moved while a importation is being performed, those files might not have been imported. Confirm that all the files were imported. If importation failed for some files, take action according to the recovery procedure described in the Single Node Troubleshooting Guide. If no files failed, but the number of import-source files differs from the number of files that were successfully imported, redo this procedure from step 14. The files that were not imported will be imported. If a node failure occurs or the file system capacity is insufficient while importing data from another file server, the import process might fail. If this happens, a message is still output to prompt users to import data again even after an all-file import is performed again. Run the datamigratestatus command with the --incompletionlist option to verify that the displayed files are all imported. If the files have been imported, no action is necessary. If some files have not been imported, take action by, for example, manually copying the files one-by-one. 18. To migrate the data of the import-source file system to an HCP, set a migration schedule. Configure this setting if the schedule is not set in step 5. If a migration schedule is set in step 5 and migration has never been performed, execute the arcmodectl command with the --init-migration enable option specified to enable the initial mode. If 1,000,000 or more files are to be imported, execute the arcmodectl command with the --initmigration enable and -t repeat options specified to enable initial mode every time a task is executed. If you specify the -t repeat option, when the number of files to be migrated drops below 1,000,000, disable initial mode. 19. Remove the import-source file server. If a failure occurred during data importation, take action according to the recovery procedure described in the Single Node Troubleshooting Guide Managing shared directories