SAN Management Software
HyperFS Administrator
Setup Guide
This guide provides step-by-step instructions for setup, configuration, and management of the
Rorke Data HyperFS SAN Management Software
Ver 2.1
May 11, 2012
This page left blank intentionally
This manual applies to Hyper FS SAN Management Software for the use of HyperFS User
Management
Released
January 1, 2012
Copyright 2012
This edition first published 2012. All rights reserved. This publication may not be reproduced, transmitted,
transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by
any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written
consent of Rorke Data, Inc.
Disclaimer
Rorke Data makes no representations or warranties with respect to the contents hereof and specifically disclaims any
implied warranties of merchantability or fitness for any particular purpose. Furthermore, Rorke Data reserves the right to
revise this publication and to make changes from time to time in the content hereof without obligation to notify any person
of such revisions or changes. Product specifications are also subject to change without prior notice.
Trademarks
Rorke Data and the Rorke Data logo are registered trademarks of Rorke Data, Inc. Rorke Data are trademarks of
Rorke Data, Inc. in the United States, other countries, or both.
Third-party software is copyrighted and licensed from Rorke suppliers. Windows® and Microsoft® are trademarks
of Microsoft Corporation in the United States, other countries, or both.
All other names, brands, products or services are trademarks or registered trademarks of their respective owners.
Naming conventions
For ease of identification purposes, the Rorke Data Hyper FS software can be referred to as the “HyperFS” or ‘the
San Software” in the following manual.
Changes
This Administrators’ Guide is for information only, and is subject to change without notice. Rorke Data reserves the right to
revise this publication, software and product design and to make changes in content from time to time without obligation on
the part of Rorke Data to provide notification of such revisions or changes.
Contents
Introduction
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Concepts and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
About this user guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Installation
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Installation file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Install HyperFS server software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
License the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Verify installed components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Next steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Getting Started
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
First steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
HyperFS Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Launch the console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Log in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
HyperFS Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
File System Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Navigation pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Command buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Service status area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Start/stop file system services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Change administrator password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Application language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
File System Management
Add a file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Launch the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Step 1: Choose file system operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Step 2: Configure file system attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Step 3: Configure volume group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Step 4: Configure volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Volume name/Volume prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Volume type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
HyperFS User Guide
Add batch volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Add data volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Add metadata volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Step 5: Format and start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Manage volume group data placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Assign a data placement policy to a directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Query the data placement policy for a directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Delete policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Policy history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Back up/restore the file system configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Back up the configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Restore the configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Format file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Start and stop a file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Start a file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Stop a file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Manage file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Add a file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Modify a file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Delete a file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Manage volume groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Add a volume group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Modify volume group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Delete volume group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Manage volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Add volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Move data volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Delete volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Modify an unformatted file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Use the wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Expand data capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Mount an external file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Add an external file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Manage external file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Mount and unmount a file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Modify a file system mount entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Delete a file system mount entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Configure the iSCSI Initiator node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . 59
iSCSI service control . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
iSCSI Initiator advanced configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
iSCSI Initiator name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Session timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
HA Management
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
New installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Existing system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
HyperFS User Guide
ii
Configure the HA cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Start HA services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Create or restart a file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Confirm HA configuration on the secondary node . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Manage the HA cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Cluster status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Start HA services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Stop HA services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Migrate file system services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Delete HA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Refresh HA status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Rebuild member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Quota Management
Add a user or group quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Modify a quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Delete a quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Copy a quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Check quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Configure quota-check events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
HyperFS Clients
Manage export paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Create an export path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Manage export paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Modify export path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Delete export path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
System Management
View the action log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
View system events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Configure email alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Perform system diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
View system log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Display log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Download log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Command Line
Using the command line utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Common arguments . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
bwlun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .89
bwadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
HyperFS User Guide
0
bwlicstat
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
bwvg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
bwvol
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
bwmkfs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
bwpolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
bwexportentry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
bwdefrag ……. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
HyperFS User Guide
0
Introduction
The HyperFS® solution is an innovative file system that simplifies management of
and access to multiple types of large files, providing concurrent high-speed file
access and data sharing for file and application servers in a cluster environment.
The HyperFS server handles all metadata requests from HyperFS clients. An
environment will include either a single storage server on which HyperFS is
installed, or a high-availability (HA), active/passive cluster with two nodes.
HyperFS client software, installed on all client machines, allows client machines to
access file systems directly over iSCSI or Fibre Channel connections.
A HyperFS system includes the following components:
The HyperFS solution provides the following benefits:
Massive
scalability
Supports up to 144 PB of storage and tens of billions of files in a single file system,
together with hundreds of clients. Storage capacity can be added rapidly and
dynamically. HyperFS supports up to 16 file systems.
Heterogeneous
application
support
Can integrate with any business and IT environment. The solution is currently widely
used in fields such as video surveillance and post processing, petroleum exploration
processing, information retrieving and processing, rich/digital media, remote
sensing, and high energy physics research. HyperFS connects with application
servers and storage subsystems via high-speed Ethernet.
HyperFS User Guide
1
Introduction
Intelligent
data/file
handling
Provides a modular storage platform with a full range of data services across
heterogeneous storage protocols and hardware for structured and unstructured data
platforms and applications.
Global name
space
All HyperFS clients share a single global name space. Administrators can expand,
move, rebalance, and configure storage without affecting how users view and
access it, and without downtime. Data changes are automatically updated in the
name space.
High
availability
A high-availability (HA) cluster can be configured to maximize data availability and
operational efficiency.
High
performance
Multiple
operating
system
support
Offers high-performance data transmission and sharing services by overcoming the
data transmission bottlenecks of traditional distributed file systems. Data is
transmitted over Fibre Channel (FC), infiniband, or iSCSI for maximum data services
performance. This makes HyperFS an ideal platform for HPC or video streaming
applications.
Runs on a wide variety of operating systems. Built-in NAS support enables users to
share data easily and seamlessly using industry-standard NFS and CIFS. HyperFS
supports Microsoft Windows, Linux, and Mac OS X clients.
HyperFS User Guide
2
Introduction
Features
HyperFS features are available in a dedicated, browser-based console:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Add, remove, and modify file systems.
Start and stop file system services on the HyperFS server.
Mount a file system to a specific directory on the HyperFS server.
Define a volume group and volumes on previously provisioned storage.
Create a binding relationship between the directories in your file system and
volume groups.
Define import paths from external file systems.
Define export paths between individual clients and a file system, allowing
clients to read, write, and delete data in the associated directory.
Configure high availability by identifying the primary and secondary servers
and the configuration LUN that they share.
Set up email alerts to identify email addresses that should receive
notification of system events; specify the level of alerts the address should
receive.
Define the size of files that can be stored on specific volumes and volume
groups.
Display and download diagnostics for the file system hardware
environment.
Display and download log files of file system operations, events, and
console activity.
Protect the HyperFS configuration file by backing up to a local machine
Manage the licensing for all standard and high availability HyperFS clients
HyperFS User Guide
3
Introduction
Concepts and components
HyperFS
server
HyperFS
Management
Console
HyperFS SAN
Clients
The HyperFS Metadata Server (MDS) software module (referred to as the HyperFS
server) is installed on the storage server. The HyperFS server processes file system
metadata, organizes the directory tree, maintains file properties, records file
operations, and authorizes file access. By providing dedicated metadata processing
and splitting its path from the primary data path, HyperFS ensures high performance
and low latency for demanding workflow applications. In the HyperFS Management
Console, connections to the HyperFS server are sometimes expressed as
connections to the Metadata Controller (MDC).
The console is installed on the storage server and accessed in a browser. The
console lets the administrator administer file systems, synchronize key operations,
and monitor system operation.
The file, application, database, or mail servers whose data is managed by the file
system connect to the HyperFS server over the existing IP network.
The HyperFS client utility, installed on client machines, allows them to access the
HyperFS server and associated data export paths.
Network
Nodes in the system are connected via a high-speed switched network such as
Gigabit Ethernet, 10Gigabit Ethernet, or InfiniBand, which takes full advantage of the
existing computing and network environment of the enterprise and reduces the cost
of storage subsystem setup and maintenance.
High
Availability
HyperFS HA configuration, based on Linux HA, allows you to configure primary and
secondary HyperFS servers for active/passive (asymmetric) failover. HA is
configured in the HyperFS Management Console.
About this user guide
This guide describes how to use the HyperFS Management Console or a command
line interface to configure and manage file systems.
HyperFS User Guide
4
Installation
This section of the user guide describes how to install HyperFS software on the
storage server that will function as the metadata controller.
Prerequisites
Complete the following steps before beginning installation:
1. Install 64-bit CentOS, OEL, or RHEL Linux 5.2 or 5.3 on the server on which you
plan to install HyperFS.
2. Ensure that the server is running the default kernel that came with the original
OS distribution. Do not patch or update the original distribution.
3. Disable SE Linux:
a. Edit the SE Linux config file:
vi /etc/selinux/config
b. Mark SE Linux as disabled:
SELINUX=disabled
4. Disable the Linux firewall:
a. Stop the firewall:
/etc/init.d/iptables stop
b. Delete iptables from the config file:
chkconfig --del iptables
5. Disable CTRL+ALT+DEL:
a. Edit the initab file:
vi /etc/initab
b. Comment out (#) the shutdown script:
#ca::ctrlaltdel:/sbin/shutdown -t3 -r now
c. If this is the final change you need to make to system files, reboot the system
and review prerequisites before continuing.
6. Make sure that all network and SAN connections are up and running.
7. If you plan to deploy HA, configure the power control. You can use IPMI or
another service; however, IPMI most commonly used.
8. Verify that at least three SAN resources (LUNs) are visible and available to the
operating system on the server that will be running HyperFS:
• Metadata LUN (200 GB advised)
HyperFS User Guide
5
Installation
•
•
Data LUN (depends on the amount of data projected for the file system)
Configuration LUN (1 or 2 GB advised)
Note: This Configuration LUN is not required if you plan to configure a
single MDS. This Configuration LUN is required if you plan to configure a
HA MDS system.
9. Make sure that all prospective client machines will be able to access to the LUNs
you intend to identify as data LUNs (following installation).
If you made any additional changes to the system since the previous reboot, reboot
the server again. Verify that you have completed all prerequisites.
Installation file
The HyperFS installation file consists of a single .tar file whose name is in the format
HyperFS_[Version-build].tar.gz.
The installation file includes all rpms required for HyperFS server installation.
Install HyperFS server software
If you plan to install an HA system, perform these steps on both storage
servers.
1. Expand the tar file:
tar xvf HyperFS_[Version-build].tar
2. Change to the installation directory:
cd ./hyperfs_install_package
3. Run the Installation package shell script:
./ install_HyperFS.sh
HyperFS User Guide
6
Installation
License the software
Preparing the license file for use:
Copy the Lic XXXX.rar or .dat file from the license email onto the desktop of a client that is on the same
network as your HyperFS MDS. Note you will need to know your MDS IP address to license it. Get that
information from your site IT administrator.
Unzip the .rar on a Windows system by doing the following procedure:
• Decompress the license file on Windows using 7-Zip
Once you’ve downloaded and installed 7-Zip from their web site http://7-zip.org/, you can rightclick on the LicXXXX.rar file and easily choose to extract the files from the menu and un-compress the
file. This creates a license.txt file that will be used in the following procedure.
Decompress the .rar file Apple OSX system by doing the following procedure:
• Decompressing the licence file on MAC OSX using Unarchiver
Apple OSX doesn’t provide many choices like the Windows platform, however there are still a few
choices, like the free app “The Unarchiver“ http://wakaba.c3.cx/s/apps/unarchiver.html , which has great
support for multi-part archive files.
HyperFS User Guide
7
Installation
Once installed, you can launch the app to associate file types with the app:
Place the Lic XXXX.rar on the desktop of the MAC and launch the Unarchiver app. Then simply doubleclick on the desktop file. The Unarchiver will create a folder with the same name as the archive and
extract its contents into the folder. This creates a license.txt file that will be used in the following
procedure.
Licensing the HyperFS
Using the system that you are logged into that now has the license.txt or .dat file on its desktop, use a
standard internet browser to log into the MDS with this procedure. In the browsers url location field enter:
http://mds_ip_address:82 where mds_ip_address is the ip address of your MDS ie 10.200.19.2
following initial page will display:
The
Enter the user and password that you have used or the defaults
username: fsadmin
default password: password
HyperFS User Guide
8
Installation
This window will open showing you that the MDS is not licensed.
Use the menu on the left side, click on the License entry under Configuration. The following window will
bring up the license window.
HyperFS User Guide
9
Installation
Click on the Import button. The following window will bring up the license import window.
Click on the Browse button and browse to the license.txt or .dat file on your desktop.
Click on the file and click the Open button to open the file.
Click on the Evaluate button to load the license.txt or .dat file and its attributes as shown in the next
window.
HyperFS User Guide
10
Installation
Note that your attributes may be different based on your license requirements.
The license file will populate the information on the Import License File page and will be indicated by
displaying Official version in the License type field. An example of the window displayed is below. Note
your window may be different based on the type of License you have purchased.
Click on the Import button. The HyperFS license activation process will begin by giving you the
following message.
The Import message window displays like the one above.
Click on the OK button and your HyperFS MDS license is now loaded and activated.
HyperFS User Guide
11
Installation
Verify installed components
To view the status of all components installed for your HyperFS system, enter the
following command:
bwlicstat -l
A list of installed components is displayed. Make sure that they all have been
enabled.
Next steps
HyperFS server software installation is now complete.
Complete the following preparations in your environment:
•
•
•
Create at least two SAN Resources (LUNs) for exclusive use by Hyper File
Systems:
• Metadata LUN (200 GB advised, minimum 50 GB)
• One or more data LUNs. LUN size depends on the amount of data in the
file system.
• If you will be configuring a High Availability cluster, create a
Configuration LUN (also known as a system resource device).
Recommended size is between 1 and 5 GB
If you plan to set limits on the amount of file system space that can be used
by users and/or user groups, create users/groups and configure access to
the data LUNs.
Identify/create the clients (application/file/media servers) that will use
HyperFS. Assign the Data LUNs to clients and make sure clients have
Read/Write access over the network.
• Install the HyperFS Client Utility on each client, as described in the
HyperFS Client Utility User Guide.
You are now ready to launch the HyperFS Management Console and configure
HyperFS.
HyperFS User Guide
12
f
Getting Started
This section of the user guide introduces the browser-based HyperFS Management
Console, which enables you to manage file systems and client access to file system
data.
Before you begin
Make sure these preparations have been completed:
•
Create at least two SAN Resources (LUNs) for exclusive use by HyperFS:
• Metadata LUN (200 GB advised, minimum 50 GB)
• One or more Data LUNs. LUN size depends on the amount of data in
the file system.
• If you will be configuring a High Availability cluster, reserve a device that
can be accessed by both nodes in the cluster. This Configuration LUN
will store HA configuration and storage resource information.
Recommended size is between 1 and 5 GB.
Note: In an HA configuration, the metadata and data volumes are also shared
devices, enabling access by either node in the cluster.
•
•
If you plan to set limits on the amount of file system space that can be used
by users and/or user groups, create users/groups and configure access to
the data LUNs.
Clients (application/file/media servers) that will use HyperFS have been
identified; data LUNs have been assigned to them and clients have Read/
Write access to these LUNs.
• The HyperFS Client Utility has been installed on all clients.
First steps
Launch the HyperFS Management console and log in.
If you are configuring a standalone (one server) HyperFS system, do the following:
•
•
•
Start file system services (refer to ‘Start/stop file system services’)
Create and start a file system (refer to ‘Add a file system’
Configure export paths for clients (refer to ‘HyperFS Clients’)
If you are configuring a High Availability (HA) cluster (active/passive, asymmetric
model), do the following:
•
•
Configure the HA cluster and start HA services (refer to ‘Configure the HA
cluster’)
On the primary server, create and start a file system (‘Add a file system’)
HyperFS User Guide
13
Getting Started
•
On the primary server, configure export paths for clients (refer to ‘HyperFS
Clients’).
HyperFS Management Console
The HyperFS Management Console enables you to manage file systems, define
relationships between volume groups and directories/files, define import/export
paths between clients and file systems, set up email alerts, run system diagnostics,
review system and event logs, and safeguard the HyperFS file system configuration
file.
Requirements
The computer from which you run the console must be on the same network as the
HyperFS server and clients.
The console supports Safari, Internet Explorer versions 6.0 and above and Mozilla
FireFox versions 2.0 and above. To ensure proper display, enable pop-ups and set
your monitor to a minimum resolution of 1072 x 768.
Launch the console
To launch the console, enter the IP address of the HyperFS server followed by :82,
for example: http://10.0.0.2:82/.
Once the login window is displayed, you can save the IP address as a Favorite or
Bookmark.
Log in
To log in, enter the administrator username (default fsadmin) and password (default
password) and then click Log In. The console Home Page is displayed.
HyperFS User Guide
14
Getting Started
HyperFS Home Page
The Home Page is displayed whenever you log into the HyperFS console.
If you are logging into the console for the first time or if file system services were
stopped when you last logged off, the Home Page will display a warning message
as shown below. The “module” referred to in the message represents file system
services and the Start and Stop Services text is a link to the File System Services
screen.
If you are configuring a standalone (one server) HyperFS system, you can start file
system services now (refer to ‘Start/stop file system services’) and then create a file
system (refer to ‘Add a file system’).
However if you are configuring a High Availability (HA) cluster, you must configure
the cluster before you can create a file system (refer to ‘Configure the HA cluster’).
If file system services are running when you log into the console, the File System
Monitor is displayed on the Home Page.
HyperFS User Guide
15
Getting Started
In the console, HyperFS features are listed in the navigation pane on the left side of
the screen. To navigate, use these feature links and the browser Back and Forward
buttons. The HyperFS product name in the title bar is a clickable link to the Home
Page.
The Home Page includes:
•
•
•
•
File System Monitor
Navigation pane
Command Buttons
Service Status area
File System Monitor
The File System Monitor summarizes status information for each file system,
including storage capacity used/available and current status.
Status – Indicates whether or not the file system is running.
File system name – The name used to identify the file system in the console.
Capacity – Indicates the total file system storage capacity, amount used, and
amount available. This is expressed in the format xxx.yyy, where xxx is the number
of GB and yyy is the number of MB. For example, 6200.581 GB represents 6200
GB plus 581 MB.
HyperFS User Guide
16
Getting Started
Details – click the Details icon
file system.
to display additional information about each
Navigation pane
The Navigation Pane at the left side of the console lists HyperFS features.
File System Menu
•
•
•
•
•
•
•
•
•
Configure Wizard - Add or modify a file system.
File System Management - Manage file systems from a screen that
includes links to all file system attributes.
Volume and Volume Group Management - Manage volumes and volume
groups.
File System Format - Format a file system.
File System Start and Stop - Start and stop a file system.
Data Placement - Associate file system directories with volumes.
Export Management - Manage export paths between a file system and
clients and between external file systems and the HyperFS server.
Quota Management - Assign storage capacity quotas to users and user
groups.
Mount File System - Manage automatic mount entries that enable you to
mount an external file system.
HyperFS User Guide
17
Getting Started
Configuration
•
•
•
•
•
•
Application Language - Specify the language displayed in the console.
Administrator Password - Change the administrator password.
Email Alerts - Set up email alerts as the result of system diagnostics and
events.
HA Management - Configure and manage a High Availability cluster
iSCSI Initiator - Configure iSCSI targets
License
Maintenance
•
•
•
•
Configuration File Management - Back up and restore file system
configuration.
System Log Files - View and download System Log files.
Event Log - View the Event Log.
System Diagnostics - View information about system activity.
Action Log – Display system events filtered by time frame.
Command buttons
Command buttons at the top of the screen are always available:
•
•
•
Home – Displays the Home Page.
About – Displays version information for the file system, management
control platform, and server operating system.
Log out – Closes the console.
Service status area
This object is always visible and displays the status of file system services, which
monitor your file systems and enable communication with storage LUNs. Three
status conditions are possible:
- all services are running.
- at least one service is not running.
- all file system services have stopped; management console functions
are disabled.
Start/stop file
system
services
To do this:
1. Click the Service Status area status text or button (in the bottom right corner of
the screen); or the Status link in the File System Monitor display; or the Start and
Stop Services link in the module warning message.
HyperFS User Guide
18
Getting Started
The System Status screen is displayed.
2. Click the Start or Stop button.
A message is displayed with success or failure information.
Starting file system services does not start file systems. File system services
communicate with the LUNs designated for use with HyperFS, making it
possible for you to create and manage file systems.
To have HyperFS file system services start automatically when the HyperFS
server boots up, select Yes.
Note: If you will be configuring a High Availability cluster, do not select this
option. If an HA node reboots and file system services start automatically, a
“split-brain” condition - where file system services are running on both nodes may occur. The HA Services function is used to control file system services
for an HA cluster.
3. Click Save to save options.
HyperFS User Guide
19
Getting Started
Change administrator password
After initial setup, you should change the default password.
1. Select Administrator Password in the Configuration menu.
2. Type the original password (password).
3. Type the new password in the New password field. The password must be
between 1 and 16 characters and is case-sensitive.
4. Type the new password again in the Retype password field.
5. Click Change Password.
If you entered the current password incorrectly or if the new and confirmed
passwords do not match, an error message is displayed and all fields are
cleared. Re-enter password information and click Change Password again.
A success message will be displayed when the password has been changed.
HyperFS User Guide
20
Getting Started
Application language
The HyperFS management console supports two languages, with English used by
default. To change the language being used:
1. Click Application Language in the Configuration menu.
2. Select the language in the drop-down list and then click Change.
When the language settings have been changed, the console is refreshed and
displays the Home Page.
HyperFS User Guide
21
File System Management
File System Management
The File System menu includes the functions you need to create and manage file
systems.
Add a file system
The File System Configuration Wizard, which allows you to add, format, and start a
file system, is the best way to create a file system.
Prerequisites
If you have a standalone (one server) HyperFS system, make sure you have started
file system services (refer to ‘Start/stop file system services’).
If you have a HyperFS HA cluster, make sure you have started HA services on both
nodes in the cluster (refer to ‘Start HA services’).
If you do not start these services before launching the wizard, an error message will
be displayed on the initial wizard screen and you will not be able to continue.
Launch the wizard
Select Configure Wizard from the File System menu.
The initial wizard screen displays the steps you will complete:
HyperFS User Guide
22
File System Management
Step 1: Choose whether you wish to add a new file system. (You can also modify an
existing, unformatted file system; refer to ‘Modify an unformatted file system’.)
Step 2: Provide attributes such as file system name, mount point, data block size,
and inode (file) size.
Step 3: Configure volume groups.
Step 4: Configure at least one data volume and one metadata volume.
Step 5: Format and start the file system.
Click Next to continue.
Step 1: Choose file system operation
This screen lets you configure a new file system or change the attributes for an
unformatted file system.
1. To create a new file system, select Add a new file system.
2. Click Next to continue
HyperFS User Guide
23
File System Management
Step 2: Configure file system attributes
Complete all items in this screen.
File system
name
File system
mount point
Enter a name for the new file system. The name can include from 1 to 31 characters
consisting of letters, numbers, and underscores. The name is not case-sensitive.
Select a mount point for the file system. To do this:
1. Click Browse, which displays the file system root directory.
HyperFS User Guide
24
File System Management
2. Select an existing directory and click OK or click Create Directory to create a
new directory.
If you choose Create Directory, enter a name for the directory in the displayed
dialog and click OK. The new directory is displayed in the list.
Note: We recommend that you use a variation of the file system name for the
directory name.
3. Click OK again to exit from the directory display and return to the Step 2 screen.
Data block
size
Select a data block size from the Data block size drop-down list. Available data block
sizes range from 4 KB to 16 MB; use the default (256 KB).
HyperFS file system performance depends on choosing the appropriate block size.
•
•
Inode ratio:
Use a larger block size if you are storing large files;
Use a smaller block size if you are storing a large number of small files;
Select an inode ratio for your file system. The Inode ratio specifies the ratio between
the inode (file) size and other metadata.
In the drop-down list, choose from the available inode ratios that range from 1:7 to
1:63. The default is 1:7.
Disk quotas
Choose whether to activate quota management on your file system. The Disk
Quotas option allows you specify limits for either disk space used or number of files
stored for individual users and user groups (refer to ‘Quota Management’). The
default is off.
Selecting on to turn on quotas for your file system.
When you are done, click Next to continue.
HyperFS User Guide
25
File System Management
Step 3: Configure volume group
A volume group is a collection of data LUNs that store file system data. A file system
must have at least one volume group. The name of the file system you are creating
is displayed by default.
Complete all items in this screen.
Volume group
name
The default is vg1. You can enter a name for the volume group. The name can
include from 1 to 31 characters consisting of letters, numbers, and underscores. The
name is not case-sensitive.
Allocation size
Choose the allocation size for your files. Allocation size is the minimum amount of
disk space that can be allocated to a file. Choose a value that is 1, 2, or 4 times the
data block size you selected for the file system. The default is 4 times the data block
size.
Exclusion
attribute
Choose the exclusion attribute, which specifies how the volume group will be used.
Choose Exclusive if you intend to set a data placement policy that binds this volume
group to certain files or all files in a specific directory (refer to ‘Manage volume group
data placement’). Only policy-bound data will be stored in the volume group.
Choose Nonexclusive (the default) to allow any type of data to be stored in this
volume group. Overflow from a volume group can be placed in any non-exclusive
volume group.
Storage usage
Choose a storage usage option from the drop-down list. Three types are available:
•
Fill (the default) – LUNs in the volume group will be filled in sequential
order.
HyperFS User Guide
26
File System Management
•
•
Stripe – A file will be striped across all LUNs in the volume group. If you
choose this option, you must also choose Stripe Size, which specifies the
amount of data that is placed on each LUN.
Flfi - All files written will be scattered across all available data volumes in
the group. If at all possible, each file will be stored in its entirety on a single
volume, in round-robin fashion.
Note: If you will be storing many small files, it is recommended that you
choose the Flfi layout, since small files are not large enough to fill a single
stripe. This can degrade performance.
Stripe size
When you choose Stripe as the Storage Usage type, the Stripe Size area is enabled.
Use the drop-down lists to select the stripe size. The stripe size value must be
greater than the allocation size.
Operation
The command button in the Operation column is either Add (to add the volume
group you have just defined) or Delete (to delete an existing volume group).
When you have completed all fields for this volume group, click Add. A new row is
displayed in case you want to add another volume group.
When you are done, click Next to continue.
Step 4: Configure volumes
A volume is a physical or logical block device used to store data. If you are creating
a new file system, create at least one metadata volume and one data volume. The
name of the file system you are building is displayed by default and the default
values are based on a data volume.
Volume name/
Volume prefix
Volume type
Volume group
name
The default name corresponds to the volume type. You can enter a name that
includes between 1 and 31 characters (letters, numbers, and underscores). The
volume name is not case-sensitive.
A drop-down list includes all volume types. The volume type you choose populates
the Volume name/Volume prefix field with a default name.
The Volume group name list allows you to associate a volume group with a data
volume.
This field is not available when you create a metadata volume.
Add batch
volume
The Add batch volume field allows you add multiple data LUNs to the volume group.
This option is available only for data volumes.
Device
The Device drop-down list includes all the available devices on the HyperFS server.
These are named according to their path at the OS level. (For more information, log
into the server root and enter fdisk -l to show all devices.)
HyperFS User Guide
27
File System Management
When you hover over a device in the list, a pop-up (the SCSI inquiry string) helps
you identify individual LUNs. Select the device that is appropriate for the type of
volume you are creating.
Add data
volume(s)
The data volume stores all types of data. You can create up to 4096 data volumes,
limited only by the size of the data LUNs allocated to the HyperFS server.
1. Data volume is the default in the Volume type drop-down list. The default data
volume name appears in the Volume name/Volume name prefix column.
2. Enter a unique name for the data volume.
3. Select the volume group that will “own the data volume (Volume group name
drop-down list).
4. Select yes in the Add batch column if you want to add multiple data LUNs to the
volume group.
5. Select the device this volume will use (Device drop-down list, minimum capacity
50 GB).
6. Click Add when you are done. A row for an additional data volume is added
below the new volume.
If you prepared more than one data LUN, you can add another data volume. If
not, create the metadata volume.
Add the
metadata
volume
The metadata volume stores bitmaps, inodes, attributes, etc. You can create only
one metadata volume.
1. Select Metadata volume from the Volume Type list.
The Volume Name/Volume Prefix text box is populated with a default name.
HyperFS User Guide
28
File System Management
2. Enter a name for the metadata volume.
3. From the Device drop-down list, select the device that this volume will use. The
minimum capacity is 2 GB.
4. Click Add when you are done. A new row is added to let you add additional
volumes but you do not need it at this time.
At this point, the Configure Volumes screen should resemble this example:
5. Click Next when you are done.
Step 5: Format and start
The final screen of the configuration wizard summarizes file system details and
offers two options:
•
•
Format file system – Initializes the storage space assigned to the file
system. This option does not start the file system.
Start file system – Mounts the file system and begins the network file
system service.
You do not have to format or start the file system at this time. An unformatted file
system is labeled in all displays as “Unformatted.” You cannot use a file system until
you start it. Refer to ‘Start and stop a file system’ and ‘Format file system’ for
information about doing this outside of the wizard.
Select or de-select options and click Done.
HyperFS User Guide
29
File System Management
Processing steps are displayed in the next screen as they occur. Click Close when processing is complete.
HyperFS User Guide
30
File System Management
Manage volume group data placement
After you have formatted and started a file system, you can define policies that
create a binding association between a directory or file in the file system and a
volume group.
To manage data placement policies, select Data Placement in the File System
menu. Four related procedures are available:
•
•
•
•
Assign a directory to a volume group.
Query a directory or file to display the properties of the bound volume group.
Delete the policy that binds a selected directory to a volume group.
Display records of policy operations that have occurred since the last format
operation.
Assign a data placement policy to a directory
This procedure binds a selected directory to a selected volume group. As a result, all
new files and subdirectories under this directory will be part of the binding volume
group. To assign a data placement policy to a directory
1. Select Data Placement in the File System menu. The Assign tab is selected by
default.
2. Select a running file system from the drop-down list.
HyperFS User Guide
31
File System Management
3. Click Browse to locate an existing directory; alternatively, click Create Directory
to create a new directory. If you create a directory, select it in the list once it
appears.
4. Click OK to return to the Data Placement screen.
5. Select the volume group.
If the group you have selected is exclusive, all files in the selected directory will
be saved to this volume group; when the data volumes in that group are full,
overflow will be saved to a non-exclusive volume group, if one exists. If all
volume groups are exclusive, there is no overflow.
6. Click Assign Policy.
A success message will be displayed when the policy has been assigned.
The volume group now has a colored background and the option button cannot
be deselected.
HyperFS User Guide
32
File System Management
Query the data placement policy for a directory
This procedure displays the properties of the volume group that is bound to a
selected directory or file.
1. Select Data Placement in the File System menu.
2. Select a running file system in the drop-down list.
3. Select the Query tab.
4. Select the Browse button to locate the directory or file, then select it.
5. Click OK.
6. Click Query Policy.
7. The query result shows the directory path and the properties of the bound
volume group.
HyperFS User Guide
33
File System Management
Data Placement
Step 1:Add, modify or delete file system
Step 2:Manage volume groups andvolumes
Step 4:Format file system
Step 4: Start or stop file system
Step 5:Manage data placement policies
A policy represents the binding relationship between a volume group and a directory or a file.If a directory is boundto a volume group, all new files and
subdirectories under this directory will inherit its policy.Deleting the policy for a directory would not change the policy for its existing subdirectories andfiles.
File system: FileSystem1(Running)
li til·•*·iiill &i.fflffiMII1111illl·ll·iil
Display the properties of volume group which directory or file was bound to.
Choose a
directory or a file:
I
I
/fsmnUFileSystem1 /abc
Browse...
ClicK Browse to choose a directory or a file.
The maximum length of the directory or file is 250.It cannot include semicolons, hyphens, bacK slashes, asterisKs, spaces,
single Quotes, double Quotes, or bacK Quotes.
Directory or
file:
Volume group
name:
Allocation
Query result:
size:
I
/fsmnUFileSystem1/abc
vg1
1024KB
Exclusion:
Nonexclusive
Storage
usage:
Flfi
Query Policy
I
HyperFS User Guide
34
.
File System Management
Delete policy
This procedure deletes the data placement policy that binds a selected directory to a
volume group.
1. Select Data Placement in the File System menu.
2. Select a running file system from the drop-down list.
3. Select the Delete tab.
4. Select the Browse button to locate the directory then select the directory.
5. Click OK.
6. Click Delete Policy and confirm that you want to delete the policy.
A success message will be displayed when the policy has been deleted.
HyperFS User Guide
35
File System Management
Policy history
This procedure displays a list of policy operations that have occurred since the last
format operation.
1. Select Data Placement from the File System menu.
2. Select a running file system from the File System drop-down menu.
3. Select the History tab.
Each item includes the date and time, operation, and the associated directory
and volume group.
HyperFS User Guide
36
File System Management
Back up/restore the file system configuration file
File system configuration information is stored in a single file. Use the Configuration
File Management feature to back up the file from the HyperFS server to a local
machine via a browser after you add a file system or after you modify a file system or
volume group.
If the configuration file damaged or lost or it becomes necessary to rebuild the
server, you can recover file system configuration details. If such a scenario occurs,
contact Rorke Data Technical Support for assistance in restoring the file.
Back up the configuration file
1. Select Configuration File Management in the Maintenance menu.
The Backup tab is selected by default.
2. Click Backup.
3. When prompted by the browser pop-up, save the configuration file in
compressed format. Close the browser pop-up when the file has been saved.
Restore the configuration file
1. Select Configuration File Management in the Maintenance menu.
1. Select the Restore tab.
2. Click Browse and locate the saved configuration file.
HyperFS User Guide
37
File System Management
3. Click Restore.
Note: You cannot restore the configuration file if you have made changes to the
file since the last time you backed it up. You must back up the configuration file
after making any change to file system configuration.
Format file system
If you did not format the file system in step 5 of the configuration wizard, you must
do so before you can use the file system.
Formatting a file system initializes the storage space assigned to the file system and
permanently erases all stored data on the data volume(s). Before you can format a
file system, you must have at least one volume group, a data volume, and a
metadata volume.
To format a file system:
1. Select File System Format in the File System menu.
2. Select an unformatted file system in the list.
3. Enter yes in the textbox to confirm that you want to format the selected file
system.
4. Click Format.
5. Click OK in the confirmation dialog.
A success message will be displayed when the file system has been formatted.
HyperFS User Guide
38
File System Management
Start and stop a file system
If you did not start the file system in step 5 of the configuration wizard or if you have
formatted a file system but did not start it, you must do so before you can use the file
system.
Select Start and Stop File System in the File System menu. From here, you can start
and stop any file system.
Start a file system
To start/mount a file system:
1. Select Start and Stop File System in the File System menu.
2. Select a stopped file system in the Stopped File Systems list.
3. Click Start. This will mount and start the selected file system.
HyperFS User Guide
39
File System Management
The file system name will appear in the Running File Systems list. A success
message will be displayed when the file system has started.
Stop a file system
To stop/unmount a file system:
1. Select Start and Stop File System in the File System menu.
2. Select the file system you wish to stop from the Running File Systems list.
3. Click Stop.
4. Click OK in the confirmation dialog if you understand that all clients of this file
system will be disconnected if you continue.
The file system name will appear in the Stopped File Systems list.
A success message will be displayed when the file system has stopped.
HyperFS User Guide
40
File System Management
Manage file systems
The File System Management main screen allows you to add or remove a file
system and includes links to procedures that can be initiated directly from the
navigation pane. Unlike the procedures in the Configuration Wizard, these
procedures are independent of each other and not sequential.
Select File System Management in the File System menu.
HyperFS User Guide
41
File System Management
Add a file system
Click Add at the bottom of the File System Management screen.
Define file system attributes in the Add File System screen (refer to ‘Step 2:
Configure file system attributes’ for details).
You can create up to 16 file systems.
Completing a file system requires the following additional steps, which are all
available from the File System Management screen:
1. Configure at least one volume group (refer to ‘Manage volume groups’.)
2. Configure at least one metadata volume and one data volume (refer to ‘Manage
volumes’.)
3. Format and start the file system (refer to ‘Format file system’ and ‘Start and stop
a file system’).
You must also back up the file system configuration file (refer to ‘Back up/restore the
file system configuration file’).
HyperFS User Guide
42
File System Management
Modify a file system
To do this:
1. Stop the file system you want to modify (refer to ‘Start and stop a file system’).
2. Select File System Management in the File System menu to display the File
System Management screen.
3. Select the file system and click Modify (the Modify button is disabled if the file
system is running).
Change file system attributes (refer to ‘Step 2: Configure file system attributes’
for details).
Note: Whenever you change file system configuration, you must back up the
configuration file when you are done (refer to ‘Back up/restore the file system
configuration file’).
HyperFS User Guide
43
File System Management
Delete a file system
You must remove all volumes and volume groups from a file system before you can
delete it.
To delete a file system:
1. Stop the file system you want to delete (refer to ‘Start and stop a file system’).
2. Delete the volumes associated with the file system (refer to ‘Delete volume’).
3. Delete the volume groups associated with the file system (refer to ‘Delete
volume group’).
4. Select File System Management in the File System menu to display the File
System Management screen.
5. Select the file system you want to delete.
Note: If the file system includes volumes, the Force Delete check box is
available. Select this to forcibly delete all volumes and volume groups. All
data on these volumes will be lost.
6. Click Delete (the Delete button is disabled if the file system is running).
A success message will be displayed when the file system has been deleted.
Note: Whenever you change file system configuration, you must back up the
configuration file when you are done (refer to ‘Back up/restore the file system
configuration file’).
HyperFS User Guide
44
File System Management
Manage volume groups
To manage the volume groups associated with a file system, select Volume and
Volume Group Management in the File System menu. The management screen
provides tabbed access to configuration screens for volumes and volume groups.
File system status can be running, stopped, or unformatted.
1. Select the file system from the drop-down list.
2. Select the Volume group configuration tab. You can perform these functions:
• Add a new volume group;
• Modify an existing volume group;
• Delete an existing volume group.
HyperFS User Guide
45
File System Management
Add a volume
group
A volume group is a collection of data volumes that store file data. A file system
must have at least one volume group.
1. Click Add in the Volume Group Configuration screen. Complete all attributes in
the Add Volume Group screen (refer to ‘Step 3: Configure volume group’ for
details).
2. Click Save when you are done. A success message will be displayed when the
volume group has been created.
3. Use your browser’s Back button to return to the Volume and Volume Group
Management screen – the new volume group appears in the list.
Modify volume
group
You can modify the attributes of an existing volume group.
1. Select a file system in the drop-down list and stop it (refer to ‘Start and stop a file
system’).
2. Click the checkbox for the volume group you want to change, then click Modify.
3. In the Modify Volume Group screen, you can change the settings for Exclusion,
Storage usage, and Stripe size.
4. Click Modify when you are done. Your changes are reflected in the Volume and
Volume Group Management screen.
HyperFS User Guide
46
File System Management
Delete volume
group
You can delete a volume group.
1. Stop the file system from which you want to remove a volume group (refer to
‘Start and stop a file system’).
2. Remove all volumes from the volume group you want to delete (refer to ‘Delete
volume’).
3. Select Volume and Volume Group Management in the File System menu to
display the Volume and Volume Group Management screen.
4. Select the associated file system in the drop-down list.
5. Click the checkbox for the volume group you want to remove, then click Delete.
A message is displayed when the volume group has been removed.
Manage volumes
To manage the volumes associated with a file system, select Volume and Volume
Group Management in the File System menu. In order to work with volumes, at least
one file system and one volume group must exist. File system status can be running,
stopped, or unformatted.
To begin, choose a file system from the drop-down list.
Next, select the Volume Configuration tab. You can perform these functions:
•
•
•
•
Add a new volume;
Move an existing volume;
Delete an existing volume
Expand the capacity of the data volume.
HyperFS User Guide
47
File System Management
Volume and Volume Group Management
Step 1:Add, modify or delete file system
Step 2:Manage volume groups andvolumes
Step 3:Format file system
Step 4: Start or stop file system
Step 5:Manage data placement policies
The table lists existing volume groups andvolumes, depending on the tab you select.
If you are adding a new file system, add atleast one volume group andthen add one metadata volume and atleast one data volume. Click Add to begin.Add
volume group andvolume attributes in the secondary screen.
If you are modifying or deleting volumes andlor volume groups,first select the file system, andthen stop itfrom running. Select the appropria te tab,then select
the checkbox for the item in the table. To select or deselect all items in the table, click the button at the top of the checkbox column.
File system: FileSystem1(Running) •
Select Ali i Deselect All
I
Volume
name
Volume type
Device
state
Volume group
name
Cl
vol_meta
Metadata
volume
Active
NIA
l devsl dc
Cl
vol_data
Data volume
Active
vg1
Move
Total capacity
Available capacity
(GB)
(GB)
Use
(%)
49.492
43.236
12.64
l devsl db 49.395
41.566
15.85
Device
Details
0
0
II Delete I D Force Delete- The volumes will be deleted even if the device cannot be found or the label of the device cannot be
erased. or there is user data in the volumes.
HyperFS User Guide
48
File System Management
Add volume
A volume is a physical or logical block device provided by the disk array and used to
store data. A file system must have at least one metadata volume and one data
volume. The name of the file system you are building is displayed by default.
Before you add a volume to a storage disk, be aware of the following:
•
•
Before you create a volume, the storage device you plan to use must exist
(must already have been prepared on the storage server) and must be
available. If you have added data capacity (refer to ‘Expand data capacity’),
be sure this has been done before you attempt to create a volume.
Do not create a duplicate of a volume that is currently being used by a file
system, as this will cause data loss on the original volume.
To add a volume:
1. Select the Volume Configuration tab and click Add (refer to ‘Step 4: Configure
volumes’ for details on fields in the Add Volume screen).
2. Select the type of volume you want to create.
3. Complete all items in the Add Volume screen.
4. Click Save when you are done. A success message will be displayed when the
volume has been created.
5. Use your browser’s Back button to return to the Volume and Volume Group
Management screen – the new volume appears in the list and an empty row (for
an additional volume) has been added.
HyperFS User Guide
49
File System Management
Volume details
In the Volume Configuration tab, click the Details link to display details about the
selected volume, including its name, type, state, SCSI_ID, capacity and available
capacity, volume group owner, and information about the device on which the
volume was created.
Volume deta1ls
X
Volume name:
vol_meta
Volume type:
Metadata volume
Device state:
ACTIVE
Device:
/dev/sdc
SCSI_ID:
36842b2b00985d9001541c1eb0c7fc49f
Device
capacity (GB):
49.512
Available
capacity (GB):
43.236
Volume group
name:
N/A
SCSIbus:
)0:2:2:0)
Vendor:
DELL
Product name:
PERC 6/i
Version:
1.22
HyperFS User Guide
50
File System Management
Move data
volume
This feature allows you to move or reassign a data LUN from one volume group to
another. If you are migrating to new storage, you need to create a new volume group
first and then move your data volumes to that group. A volume group “owns” the
associated data volumes.
1. Modify the file system to create a new volume group (refer to ‘Add a volume
group’).
2. Stop the file system (refer to ‘Start and stop a file system’).
3. In the Volume and Volume Group Management screen, select the file system
from the drop-down list.
4. Click the checkbox for a data volume and then click Move.
5. In the Move Volume screen, select the destination volume group name from the
drop-down list.
6. Click Move when you are done. Wait until the “loading” message has
disappeared and the result message is displayed before continuing.
7. Click Cancel to return to the Volume Configuration screen.
Delete volume
If a file system has changed or if you need to recreate a file system, you can delete
volumes. The following rules apply:
•
•
•
•
•
•
You can delete an empty data volume while file system status is running.
If a data volume is not empty, stop the file system before removing the data
volume. Please note that this will cause all data to be lost on the LUN.
If you want to delete a metadata volume, stop the file system.
You can delete a metadata volume from a file system that is not formatted.
If the file system has been formatted and you delete a volume, all data will
be lost and you will have to reformat the file system.
You can delete all volumes at the same time if file system status is stopped
or not formatted.
HyperFS User Guide
51
File System Management
•
If you delete all volumes for a stopped file system, file system status will
change to not formatted.
1. After you have identified the dependencies that affect you, select the file system
in the drop-down list in the Volume and Volume Group Management screen.
2. To delete a volume, click its checkbox and then click Delete.
To remove all volumes, click all volume checkboxes or the select all link and then
click Delete.
If a file system device is in an abnormal situation, for instance if the device
cannot be found or if the label on the device cannot be erased, you can forcibly
remove a volume. In such a case, select the Force Delete checkbox before you
click Delete.
HyperFS User Guide
52
File System Management
Modify an unformatted file system
If you created a file system but did not format it, you can modify its attributes from
the File System Management screen or by using individual features from the File
System menu, or you can use the configuration wizard.
Use the wizard
Select Configuration Wizard in the System menu and click Next in the first screen.
1. Select Modify an unformatted file system.
2. Select a file system with the label Not Formatted.
3. Click Next to skip to any step in the wizard and modify file system components.
Refer to ‘Add a file system’ for details on wizard screens.
4. Click Done when you are finished.
HyperFS User Guide
53
File System Management
Expand data capacity
You can expand file system data capacity whether file system status is running or
stopped. To do this:
1. Connect additional physical storage and perform any configuration required by
the storage vendor.
2. In the HyperFS console, add a new data volume (refer to ‘Add volume’). If you
have more than one volume group, make sure you add the new volume to the
correct group.
When you return to the Volume Group Configuration screen after creating the
new data volume, it will be displayed in the list.
Mount an external file system
You can mount a HyperFS file system that is part of another HyperFS system in
order to make it accessible to clients who access file systems on your HyperFS
server.
Prerequisites
1. Configure the external server as an iSCSI target of your HyperFS server (refer to
‘Configure the iSCSI Initiator node’).
2. Create an export path for the data (refer to ‘Manage export paths’). Note the IP
address, file system address, and file system type for the file system you plan to
mount.
Add an external file system
The procedure to add an external file system creates an automatic mount point for
that file system. To do this:
1. Select Mount File System in the File System menu.
2. Click Add.
HyperFS User Guide
54
File System Management
3. Complete properties in the Add Automatic Mount Entry screen.
File system
type
Server IP
Export Path
Select a file system type from the drop-down menu. (Currently, only the BWFS
file system protocol is supported.)
Enter the server IP address for the external file system.
Click Query Export Path to display a list of existing export paths to the target
server. Select the one you want to use, which will display it in the export path
field.
HyperFS User Guide
55
File System Management
Mount point
Enter a file system mount point or click Browse to select an existing directory or
to create a directory that will be a dedicated mount point.
Click OK when you are done.
The remaining options in this screen define the conditions for mounting the file
system:
Automount on
boot
Access type
Specify whether or not the file system should mount automatically when the
system starts. The default is Yes.
Set the access type as Read and write (the default) or Read only.
Owner
permission
Set owner permissions for the external file system. The default allows the setuser-identifier and set-group-identifier bits to take effect.
Async write
requests
Specify whether to emphasize write performance (the default) or data
consistency in write requests.
Execute
binary file
Indicate whether or not execution of binary files on the mounted file system is
permitted. The default is Yes.
Lock type
Specify whether to set a distributed lock in the server or a non-distributed lock on
the client (the default) for the file system.
Mount at once
Indicate whether you want to mount the external file system automatically when
you save this screen. The default is Yes.
Auxiliary
parameters
Define optional parameters. For instance, to add dev and user=bin parameters,
enter -o dev,user=bin.
4. Click Save.
A success message will be displayed when the automatic mount entry has been
added. If the Mount at once option is set to yes, the file system will be accessed
and mounted.
HyperFS User Guide
56
File System Management
Once the external file system has been mounted, you can define export paths
between the file system and clients. The client display for an export path to a
mounted external file system is the same as for any mounted export path:
Manage external file systems
To view which file systems are currently mounted, select Mount File System from the
File system menu.
In addition to adding file system mount entries, you can mount, unmount, modify,
and delete existing entries.
The following information is displayed for each external file system:
File system type – File system protocol.
Server IP – Server IP address for the external file system.
Export path – The export path defined for the file system.
Mount point - Mount point directory.
Status – Mounted or unmounted.
Mount and
unmount a file
system
Before you unmount the file system, make sure that all clients have unmounted any
export path to the target server and disconnected from the target server.
Click the checkbox for the file system mount entry and then select either Mount or
Unmount.
HyperFS User Guide
57
File System Management
Modify a file
system mount
entry
Before you modify a file system mount entry, make sure that all clients have
unmounted any export path to the target server and disconnected from the target
server.
1. Click the checkbox for the mount entry that you want to modify.
2. If the file system is mounted, click Unmount. Note that this will disconnect all
connected clients.
3. Click Modify.
In the Modify Automatic Mount Entry screen (see ‘Add an external file system’),
you can change the settings related to the conditions under which the file system
is mounted; other options are disabled.
4. Click Modify when you are done.
A success message will be displayed when the changes are completed.
Delete a file
system mount
entry
Before you delete a file system mount entry, make sure that all clients have
unmounted any export path to the target server and disconnected from the target
server.
1. Click the checkbox for the mount entry that you want to delete.
2. If the file system is mounted, click Unmount. Note that this will disconnect all
connected clients.
3. Click Delete.
4. Click OK in the confirmation dialog.
A success message will be displayed when the entry has been deleted.
HyperFS User Guide
58
File System Management
Configure the iSCSI Initiator node
Before you can mount an external HyperFS file system, you must configure the
external server as an iSCSI target of the server on which the file system will be
mounted, allowing the iSCSI initiator to see the file system on the external server.
The iSCSI Initiator feature identifies the external server as the target server, and
discovers the target, making it possible to display it in the HyperFS console. You can
also modify the Initiator node name, view information about the target LUNs, and
control the iSCSI Initiator service.
If you have a HyperFS HA cluster, complete this procedure on the primary and
secondary nodes.
1. Select iSCSI Initiator in the Configuration menu. The iSCSI Target Server tab is
selected by default.
2. Click Add.
3. In the Add iSCSI Target Server dialog, enter the external storage server IP
address and click Add.
HyperFS User Guide
59
File System Management
4. The server IP address is displayed in the iSCSI target server tab. Select the
server checkbox and then select Discover Target. A success message will
display when the target server has been discovered.
5. Select the iSCSI Target tab. At this point, target status is Disconnected and the
Details link is inactive.
To connect to the target, select the server checkbox and click Connect.
A message will be displayed when the target connection is successful. If you
lose connection to the target, you can click Rescan to reconnect.
HyperFS User Guide
60
File System Management
Click the Details icon to see information about the LUNs on the target server; the
data LUN is highlighted.
You can now mount the external file system.
iSCSI service control
The Service Control tab displays information about the iSCSI Initiator utility and
allows you to stop iSCSI services if necessary for debugging purposes or if you do
not want iSCSI services running.
HyperFS User Guide
61
File System Management
iSCSI Initiator advanced configuration
The Advanced Configuration tab displays the iSCSI initiator name and the session
timeout setting.
iSCSI Initiator
name
Session
timeout
Although you can change the iSCSI initiator name, this is not recommended, as
initiator names must be unique within the HyperFS system.
A default Session timeout value of 300 seconds is set in order to sustain the disk for
five minutes during failover so that applications will not be disrupted by temporary
network problems. You should change this value only on advice from Technical
Support.
Save any changes when you are done.
If you have an HA configuration, repeat any changes on the secondary node.
HyperFS User Guide
62
HA Management
You can configure a High Availability cluster when you first set up your HyperFS
system, or you can install HyperFS on a second server later on and then configure
the cluster.
In an HA cluster, the metadata and data volumes are shared devices, enabling
access by either node in the cluster. Another shared device - the Configuration LUN
- stores all cluster configuration and storage resource information and makes it
possible to rebuild the cluster after a failed node is restored.
The layout of a typical HA cluster is shown below.
HA software resources, including the bwfsmmd and bwfs services, run on the
primary node, which is also assigned a floating IP address. The bwfsmmd service
mounts the system resource device on the primary node (default mount path /usr/
local/hr/share). The bwfs service can then start the file system on the primary
server. Clients machines access the file system via the floating IP. If the primary node
fails, all resources fail over to the secondary node.
The HA Management feature allows you to create and manage a High Availability,
active/passive (asymmetrical) failover cluster. In the event of a disk failure on the
primary or secondary node, it is possible to reconfigure the cluster by executing the
Rebuild command from the HA Management screen after the hardware has been
repaired.
HyperFS User Guide
63
HA Management
Prerequisites
New installation
Note: Do not start file system services; HA services are used in the cluster. Do not
create a file system until you have completed HA configuration.
1. Install HyperFS server software on the two storage servers you plan to
designate as the primary and secondary HyperFS server (identified as MDC in
the HA Configuration screen).
2. Verify that both servers are on the same network and make a note of their IP
addresses.
3. Ensure that the same LUNs are visible from both servers.
4. Reserve a device that will function as the Configuration LUN (recommended size
is between 1 and 5 GB). This shared device (also known as a system resource
device) will store HA configuration and storage resource information for both
nodes in the cluster and make it possible to rebuild the cluster after failover.
5. Implement some form of power control on each server and note the power
control IP addresses.(A power control device is used to reset the HyperFS
server during failover.)
6. Enable and configure other options such as a network monitor or an HBA
connect monitor and note their IP addresses.
7. Reserve 4-7 IP addresses for the cluster.
8. Determine which node you want as the primary. Perform HA configuration using
the console on this node.
Existing system
1. If you have already created a file system, your existing HyperFS server will serve
as the primary server in the cluster. Stop file system services on the primary
server: click the Service Status link at the bottom of the screen; in the Services
Status screen, click the Stop button.
2. Install HyperFS server software on the storage server that will serve as the
secondary node in the cluster.
3. Verify that the secondary node is on the same network as the primary and make
a note of its IP address.
4. Ensure that the existing LUNs are visible from the secondary node.
HyperFS User Guide
64
HA Management
5. Reserve a device that will function as the Configuration LUN (recommended size
is between 1 and 5 GB). This shared device (also known as a system resource
device) will store HA configuration and storage resource information for both
nodes in the cluster and make it possible to rebuild the cluster after failover.
6. Implement some form of power control on each server and note the power
control IP addresses.
7. Enable and configure other options such as a network monitor or an HBA
connect monitor and note their IP addresses.
8. Reserve 4-7 IP addresses for the cluster.
Important: After you configure the HA cluster, never select the option in the
System Status screen to start file system services automatically when the MDS
(HyperFS server) is started (refer to ‘Start/stop file system services’). If an HA
node reboots and file system services start automatically, a “split-brain” condition
- where file system services are running on both nodes - may occur. The HA
Services function is used to control file system services for an HA cluster.
HyperFS User Guide
65
HA Management
Configure the HA cluster
1. Select HA Management in the Configuration menu. The settings you enter in this
screen will be saved in the cluster configuration file on the configuration LUN.
Primary MDC
Secondary
MDC
Server IP
Power Control
Type the IP address of the primary HyperFS server.
Type the IP address of the secondary HyperFS server.
Type the IP address that clients will use to access the cluster.
Select the power control option you used during hardware installation. The
power control enables the system to monitor failover conditions. Choices are
IPMI, ILO, and None.
If you selected IPMI or ILO, type the IP address, username, and password for
the power control on each node and enable the power control.
You can also disable the power control.
HyperFS User Guide
66
HA Management
If you select None, no other options are available.
Heartbeat
Heartbeat settings allow servers in the cluster to monitor each other. Select
network interface ports and Mcast IP addresses.The multicast IP address
defines the communication path between the nodes.
If you have more than one cluster, each cluster must have a unique multicast IP
address.
Network
Monitor
Enable this option and enter the health IP address if you want the cluster to
monitor the network state.
The health monitor IP is typically the IP address of a known stable system, such
as the IP Gateway.
The Network Monitor continuously sends an ICMP message (ping) to the health
monitor IP. As long as the network monitor detects an ICMP response, it
assumes the network connection is functioning normally. If the network monitor
cannot communicate with this address, a failover condition occurs and file
system services migrate automatically to the secondary node.
HBA Connect
Monitor
System
Resource
Device
Enable this option if you want the cluster to monitor the state of the HBA adapter.
The HBA Connect Monitor continuously queries the state of the HBA adapter to
ensure that the access to storage is clear. (The QLogic HBA adapter connection
monitor is currently supported.)
Select the device path of the Configuration LUN, which stores the cluster
configuration and is accessed by both nodes in the cluster. Enter the label
assigned when the disk was prepared.
The Rebuild process uses the information in the cluster configuration file to
rebuild the HA configuration on the failed node.
Service
Resource
Click Enable to automount the file system when the HA cluster starts.
2. Click Configure.
The HA Management screen is displayed; the HA Configuration screen is no
longer available.
HyperFS User Guide
67
HA Management
Start HA services
The HA Management screen displays the status of all components in the cluster.
At this point, HA services are not yet running. The status of both nodes is Service
Stopped. You must start HA services on both nodes in the cluster.
To do this, click the Start button at the bottom of the screen. Wait while the system
performs the following operations:
• Sends a “Start HA services” command to both HyperFS servers;
• Joins the nodes at a cluster;
• Starts the system resource device, file system services, and server IP on
the primary node.
When this is done, displayed status will change to Service running for the primary
node and Service waiting for the secondary node.
Important: After you configure the HA cluster, never select the option in the
System Status screen to start file system services automatically when the MDS
(HyperFS server) is started (refer to ‘Start/stop file system services’). If an HA
node reboots and file system services start automatically, a “split-brain” condition
- where file system services are running on both nodes - may occur. The HA
Services function is used to control file system services for an HA cluster.
HyperFS User Guide
68
HA Management
Create or restart a file system
If this is a new installation, you are ready to create a file system (refer to ‘Add a file
system’). Launch the Management Console on the primary node; create all file
systems on the primary node.
If you have reconfigured an existing system for HA, restart any existing file system
(refer to ‘Start a file system’).
After you have configured the HyperFS high-availability cluster, select HA
Management in the Configuration menu from the primary node (the node on which
file system services are running) to manage the cluster and to check for/manage
failover events.
Confirm HA configuration on the secondary node
Log into the HyperFS Management console on the secondary node and make sure
the settings on the HA Management screen are the same as for the primary node.
Manage the HA cluster
To monitor cluster status after the cluster is operational, select HA Management in
the Configuration menu. The HA Management screen displays information about all
components in the cluster.
HyperFS User Guide
69
HA Management
Cluster status
Possible conditions include:
Running – Both nodes are performing satisfactorily: the status of one is Services
running and the status of the other is Service waiting.
Warning – File system services are being supplied by one node but the other is not
OK. This is a failover condition.
Abnormal – File system services cannot be supplied by either node, although HA
services are running.
Stopped – HA services have stopped on both nodes.
Unknown – HA system status cannot be displayed.
Refer to ‘Configure the HA cluster’ for information about other components.HBA
Connect Monitor
Management functions
Command buttons at the bottom of the HA Management screen control
management functions.
Start HA
services
1. Select Configuration --> HA Management in the navigation tree.
2. Click the Start button at the bottom of the screen. HyperFS will perform the
following steps:
a. Remotely send a “Start HA services” command to both nodes;
b. Connect the two nodes as a cluster;
c. Start the Shared Configuration LUN, file system services, and server IP on
the primary node.
Stop HA
services
1. Select Configuration --> HA Management in the navigation tree.
2. Click the Stop button at the bottom of the screen. HyperFS will perform the
following steps:
a. Remotely send a “Stop HA services” command to both nodes.
b. Stop the Shared Configuration LUN, file system services, and server IP on
the primary node.
Migrate file
system
services
Perform this procedure only as part of planned activities such as maintenance or
testing. Manual migration is not part of a response to a failover event.
To do this:
1. Select Configuration --> HA Management in the navigation tree.
HyperFS User Guide
70
HA Management
2. Click the Migrate button at the bottom of the HA Management screen. If you
continue, HA services will be stopped on both nodes.
3. A confirmation message states the IP address of the node to which file system
services will be migrated. Click OK if you want to continue.
A confirmation message will be displayed when migration is done.
After testing or maintenance is complete, repeat this procedure to migrate services
back to the primary node.
Delete HA
configuration
You can remove HA configuration only when both nodes have a status of Stopped,
To do this:
1. Select HA Management in the Configuration menu.
2. Stop HA services (refer to ‘Stop HA services’).
3. Click the Delete button at the bottom of the HA Management screen. HyperFS
will do the following:
a. Delete the HA configuration file on both nodes.
b. Move all files from the Shared Configuration LUN to the local disk, and then
deletes them.
c. Removes the label from the Shared Configuration LUN.
You can now use the former primary node as a standalone HyperFS system.
Refresh HA
status
Click Refresh to collect and display current status for both nodes.
You can also set automatic refresh frequency. To do this, select 30 seconds, 1
minute, or 5 minutes in the drop-down list.
Rebuild member
When failover has occurred, it may be necessary to make repairs on the failed node
such as system disk change, operating system reinstallation, etc. After this, the
cluster cannot manage the node because information related to HA configuration
has changed.
After a node has recovered/operational, you can recover HA configuration
information by clicking the Rebuild Member link for the affected server in the HA
Management screen. This rebuilds the cluster configuration from information stored
on the Configuration LUN.
The Rebuild operation is complete when you see Service running on the primary
node and Service waiting on the secondary node.
HyperFS User Guide
71
Quota Management
If you enabled quota management when you created a file system, you can control
the amount of space used on the file system by individual users and user
groups.The Quota Management feature lets you add quotas for users and user
groups, specifying either how much data or how many files each one can store on a
data volume. Information on space used and space available is displayed. You can
also modify and delete quotas and copy quota information from one user or group to
another.
Prerequisites
Before you create quotas, do the following:
•
•
Activate Linux quotas.
Configure access to the file system for users and user groups. The user and
group names you provide for quota management must already have
permission to access the file system.
A user name or group name can contain 1-31 characters and cannot include
the space, colon, pound, or Chinese characters; it cannot be the user “root”.
•
•
Make sure the file system for which you want to set quotas is running.
Make sure the Disk Quotas option has been turned on for the file system.
If this option has not been turned on, you can modify the file system (refer
to‘Modify a file system’).
Add a user or group quota
1. Select Quota Management in the File System menu.
Users is the default tab; select Groups if you want to set a group quota. No
quotas is displayed if none have been defined. (The Users tab display is shown
below.).
HyperFS User Guide
72
Quota Management
2. Select the file system from the drop-down list.
3. Click Add.
4. The Add Quota screen displays disk and file information and lets you specify a a
limit for one or both categories. (Except for the User name/Group name field,
Add Quota screen is the same for both.).
User Name (or Group Name) – Type the user name or group name.
Information of disk – This is the amount of space (total and free) on the LUNs
reserved for the file system.
Disk hard limit – Type a value, in units of GB or MB, to specify the amount of
space you want to allocate. The maximum amount of space is the amount of free
space on the disk. Type 0 (zero) if you do not want to set a space limitation. If
you do this, you must set a file limitation.
Information of file – This is the number of inodes (total and free) on the file
system.
Files hard limit – Type a value to specify the maximum number of files you want
the user or group to be able to store on the file system. The maximum number of
files is the number of free inodes. Type 0 (zero) if you do not want to set a file
limitation. If you do this, you must set a disk space limitation.Click Save.
HyperFS User Guide
73
Quota Management
The new quota is displayed. An example of a group quota is shown below:
Modify a quota
To modify a user or group quota:
1. Select Quota Management in the File System menu.
2. Select a file system from the drop-down list.
3. Select the Users or Groups tab.
4. Click the checkbox for the quota you want to modify and click Modify.
5. In the Modify Quota screen, you can change the values for Disk hard limit and
Files hard limit. You cannot set both values to 0 (zero).
6. Click Modify when you are done.
Delete a quota
When you remove the quota for a user or group, there is no limit to the amount of
space that user or group can occupy on the file system.
To delete a quota:
1. Select Quota Management in the File System menu.
2. Select a file system from the drop-down list.
3. Select the Users or Groups tab.
4. Click the checkbox for the quota you want to delete and click Delete.
5. Click OK in the confirmation message.
HyperFS User Guide
74
Quota Management
6. A message will be displayed when the quota has been removed.
Copy a quota
You can copy a user or group quota to another user or group, respectively.
1. Select Quota Management in the File System menu
2. Select a file system from the drop-down list.
3. Select the Users or Groups tab.
4. Click the checkbox for the quota you want to copy.
5. Click Copy Quota.
6. The selected user or group name is displayed in the user name/group name
field.
7. Type a destination user or group name. The selected quota values will be copied
to that user or group.
8. Click Copy Quota.
A success message will be displayed when the quota has been copied.
Check quotas
If a quota check message is displayed as shown in the example below. perform the
Check Quotas operation. This will scan the file system for disk usage and quotas
and will make repairs to quota files if possible.
This procedure may take a long time if the file system is very large; during this time
the file system status will be changed to Readonly.
To check file system quotas:
1. Select Quota Management in the File System menu.
2. Select a file system from the file system drop-down menu.
HyperFS User Guide
75
Quota Management
3. Select the Check Quotas tab.
4. Enter yes in the check quotas field and click Check Quotas.
A confirmation message will be display when the operation is complete.
Configure quota-check events
You can indicate how often quotas are checked and specify a percentage of disk
usage that will trigger a warning email to all affected users and groups when the
threshold is reached.
To configure the quota-check events:
1. Select Quota Management in the File System menu.
2. Select a file system from the drop-down list.
3. Select the Event Configuration tab.
4. To define the time interval between quota checks, type a value between 1 and 7
days or 1 and 24 hours, using the text box and drop-down list.
HyperFS User Guide
76
Quota Management
Based on this interval, a quota-check reminder message will be displayed in the
Quota Management screen. Before executing the quota-check, the administrator
must notify client users that the file system will be Readonly during this process.
5. To set a disk-space-usage threshold, enter a percentage between 1 and 100 in
the Warn when usage reaches: textbox.
When occupied disk space exceeds this threshold, the system will send an email
to all affected users (refer to “Configure email alerts”.)
HyperFS User Guide
77
HyperFS Clients
Manage export paths
An export path allows a HyperFS client to access data in a specified directory on a
file system. When you create an export association for a HyperFS client, the client
can mount the directory to read, write, and delete data. A single file system can have
many export paths.
Create an export path
You can add an export path to a running file system:
1. Select Export Management in the File System menu.
2. Select a file system in the drop-down-down list (the file system status must be
running) and click Add.
3. Complete all items in the Add Export screen.
HyperFS User Guide
78
HyperFS Clients
Directory to
export
Click Browse to display the file system directory.
Select the directory you wish to export or click Create Directory to create a new
directory, then click OK. Select the new directory when it appears in the list.
Click OK again to exit from the directory display and return to Add Export screen.
Exports to
Specify the export destination, which is the client IP address or domain name.
Click the Format help links to display examples of correct IP address or domain
name format.
Access type
The default is read-write; you can also choose read-only.
Root access
control
Select the type of root access control you want for this export path:
• no root – The HyperFS client root user is treated as root in the exported
directory.
• root (the default) – The client root user is treated as an anonymous user in
the exported directory.
• all – Any client user is treated as an anonymous user in the exported
directory.
Anonymous
user
This specifies the Anonymous user mapping logging from Windows clients.
• fsnobody – The user has read/write/execute permissions for the directory
and its contents.
• fsuser (the default) – The user is a root owner user of the file system.
Async write
requests
• yes (the default) – Data is written to the memory cache first and then to disk
when necessary, improving write performance. It is possible to lose data if
there is an abnormal shutdown and the data is not flushed.
• no – Data is written to the memory cache and to disk synchronously,
ensuring data consistency.
HyperFS User Guide
79
HyperFS Clients
Support nfs
export
Select yes to change the default no. Selecting yes makes the export available
via NFS protocols.
4. Click Save when you are done. A success message will be displayed when the
export path has been created.
Manage export paths
To view existing export paths, select Export Management in the File System menu.
Modify export path
This procedure modifies an export path for a running file system. To do this:
1. Select a running file system from the drop-down list.
2. Click the checkbox for the export path and then click Modify.
HyperFS User Guide
80
HyperFS Clients
You can modify all export path properties except the directory being exported
and the target client.
3. Click Modify when you are done.
4. Use the browser’s Back button to return to the Export Management screen.
Delete export path
Deleting an export path removes the client’s access permission(s) to the
corresponding directory. To do this:
1. Select one or more checkboxes to mark the export path(s) you want to delete.
2. Click Delete.
3. Click OK in the confirmation dialog. A success message will be displayed when
the selected export path(s) have been deleted.
HyperFS User Guide
81
System Management
The features listed in the Configuration and Maintenance menus allow you to
perform system diagnostics in order to review system activity, view and download
system log files, and set up email alerts related to system events.
View the action log
The action log displays a list of operations that have been performed using the
HyperFS console and allows you to filter the display to various time frames: the
current day, the past three days, the past week, and all actions.
The system module, user, host, and date/time are displayed for each action.
To display the log, click Action Log at the bottom of the Navigation Pane. The current
day’s actions are displayed by default.
To display actions:
Choose a time frame in the drop-down list and click Search.
HyperFS User Guide
82
System Management
View system events
The Event Log procedures let you query the HyperFS system for various levels of
events during a specified period of time. You can also download the event log files.
To view system events, click Event Log in the Maintenance menu. The default
display lists all events in the file system environment.
To filter the display:
1. Enter the hostname.
2. Select an event level: error, warning and higher level, or info and higher level.
3. Enter an optional key word to limit the search.
4. To restrict the event display to a period of time, click the From and To calendars
and click a date in each one.
5. Click Query.
To review details for an event, click Details.
To delete events from the display, click the checkbox for the event and then click
Delete.
To download the displayed events and view as a text file, click Download.
HyperFS User Guide
83
System Management
Configure email alerts
This feature allows you to supply email addresses that should receive notification of
system events. For each address, you can specify the level of alerts the address
should receive. To configure email alerts, select Email Alerts in the Configuration
menu.
1. Enter the Name or IP of the SMTP server.
2. Indicate whether the server requires a password (select Password) or not (select
None), in order to authenticate email addresses.
3. If you select Password, enter the required username and password.
4. Enter the email address of the HyperFS administrator.
5. Enter the email address that should receive event notifications.
6. Choose the level of events to be sent: info and higher (the default); warning and
higher; or error. The selected event level includes all levels below it in the list.
7. Click Add when you are done.
8. Add additional receivers as needed
9. When you are done, click Configure Email.
HyperFS User Guide
84
System Management
Perform system diagnostics
System Diagnostics are used to check the file system hardware environment and
display the results. To run system diagnostics and display the results screen, select
System Diagnostics in the Maintenance menu.
•
•
•
•
Analyze
diagnostics
Diagnosis – System components being monitored.
Status – An icon indicates the status of each component:
•
- the component is operating properly.
•
- warning that the component may not be available
•
- the component has not been configured.
•
- faulty - the component is not functioning.
Summary – high-level summary of component status.
Details – detailed information about component status.
•
- details are available.
•
- details most recently reviewed.
To view suggestions for resolving system problems, click Analyze. Suggestions are
displayed in a popup dialog.
HyperFS User Guide
85
System Management
Download
system
configuration
information
You can download system configuration information in compressed .tgz format. To
do this:
1. Click Download to display the Download System Configuration Information
dialog.
2. Select one or more system modules and click Download.
3. Indicate whether you want to open or save the file.
The diagnosis file name includes the current date and time.
HyperFS User Guide
86
System Management
View system log files
System log files record information needed to review file system operations and
diagnose and fix system errors. To display the list of downloadable system log files,
select System Log in the Maintenance menu. The following log files are available:
•
•
•
•
bwutils.log – file system function information
bwweb.log – user operations in the file system management console
dmesg_file.log – system-wide log
message_file.log – generic linux common log repository
Display log files
To display a log file, click Query for that file. The 20 most recent log entries are
displayed by default.
•
•
•
To display all log entries that contain a specific string, enter that string in the
Match string field and click Query.
To display the latest n entries, enter that number (from 1 to 5000) in the
Query the last field and click Query.
You can also search within the results of either of these two options.
To return to the System Log screen from a log file display, click Return to System
Log or use your browser’s Back button.
Download log files
To download all log files in compressed .tgz format, click Download Log and indicate
whether you want to open or save the file. The logs file name includes the current
date and time.
Two additional log files are included in the download:
•
•
action.log – records the user’s actions in the HyperFS console.
miniserv_error.log – records web server activity.
Downloaded files can be provided to Technical Support.
HyperFS User Guide
87
Command Line
HyperFS provides a simple utility that allows you to perform HyperFS system
functions at a command line instead of through the HyperFS console.
The CLI is installed under this path: /usr/local/hr/bin/.
Using the command line utility
All commands can be perform under any path. Each command must be combined
with the appropriate long or short arguments.(ex. Long: -- start file system
Short: -s file system).
If you type the command name (for example, bwadmin --help), a list of
arguments will be displayed for that command.
Commands
Below is a list of commands you can use to perform HyperFS functions from the
command line. You should be aware of the following as you enter commands:
•
•
•
•
•
•
•
•
Type each command on a single line, separating arguments with a space.
You can use either the short or long arguments (as described above).
Variables are listed in {} after each argument.
Arguments listed in brackets [ ] are optional.
The order of the arguments is irrelevant.
Arguments separated by | are choices. Only one can be selected.
For a value entered as a literal, it is necessary to enclose the value in
Quotes (double or single) if it contains special characters such as *, <, >, |,
%, $, or space. Otherwise, the system will interpret the characters with a
special meaning before it is passed to the command.
Literals cannot contain leading or trailing spaces. Leading or trailing spaces
enclosed in quotes will be removed before the command is processed.
HyperFS User Guide
88
Command Line
Common arguments
Short Argument
Long Argument
Value/Description
-s
--server-name
Server Name (hostname or IP
address)
-u
--server-username
Server Username
-p
--server-password
Server User Password
-c
--client-name
Client Name
-v
--vdevid
Virtual Device ID
bwlun
bwlun --list
bwlun --help
bwlun --version
Description:
This command is used to manage devices. Available arguments:
-l, --list
List device properties
-h, --help
Display this help and exit
-v, --version
Output version information and exit
bwadmin
Description:
This command is used to manage the file system: add, remove, start, or stop a file system; set file system
properties, display file system status, or list all file systems. Available arguments:
-l, --list
List all file systems
-a, --add
Add a file system
-s, --start
Start a file system
-t, --stop
Stop a file system
-d, --status
Display file system status
-m, --modify
Modify file system properties
-e, --set
Set file system properties
HyperFS User Guide
89
Command Line
-r, --del
Remove a file system
-o, --othervg={on,off}
Set the use other volume group flag on or off for a file system
-M, --dmapi={on,off}
Set the data manager interface flag on or off for a file system
-A, --acl={on,off}
Set the access control list flag on or off for a file system
-p, --mntpoint=POINT
Set the mount point of a file system to POINT
-b, --datablocksize=SIZE
Set the data block size of a file system. The size can be: 4KB, 8KB, 16KB, 32KB,
64KB, 128KB, 256KB, 512KB, 1MB, 2MB, 4MB, 8MB, 16MB. The default is 256KB.
-F, --non-interactive
Execute this command in non-interactive mode
-h, --help
Display this help and exit
-v, --version
Output version information and exit
Add a file system
bwadmin --add [ --datablocksize SIZE] [ --mntpoint POINT] fsname
Examples:
bwadmin --add filesystem1
bwadmin --add --datablocksize 1MB
Start a file system
bwadmin --start fsname
Example:
bwadmin --start filesystem1
Stop a file system
bwadmin --stop [ --non-interactive ] fsname
Example:
bwadmin --stop
--non-interactive filesystem1
Display file system status
bwadmin --status fsname
Example:
bwadmin --status filesystem1
HyperFS User Guide
90
Command Line
List all file systems
Example: bwadmin –
list Remove a file
system
bwadmin --del [ --non-interactive ] fsname
Example:
bwadmin --del filesystem1
Set file system properties
bwadmin --set --othervg on|off fsname
Example:
bwadmin --set --othervg on filesystem1
Modify file system properties
bwadmin --modify --dmapi on|off --acl on|off filesystem1
Example:
bwadmin --modify --dmapi on --acl on filesystem1
Display help
bwadmin --help
Display version information
bwadmin --version
bwlicstat
bwlicstat --list
bwlicstat --reload
bwlicstat --help
Description:
This command is used to display and reload the values of the licensed features. Available arguments:
-l, --list
Show all the values of the licensed features.
-r, --reload
Reload all the values of the licensed features.
-h, --help
Display this help information.
HyperFS User Guide
91
Command Line
bwvg
Description:
This command is used to manage volume groups: add a volume group to a file system, remove a volume group
from a file system, modify a volume group in a file system; list properties of all volume groups in a file system.
Available arguments:
-a, --add
Add a volume group to a file system
-d, --del
Remove a volume group from a file system
-l, --list
List the properties of all volume groups in a file system
-m, --modify
Modify the attribute of a volume group in a file system
-n, --fsname=FSNAME Specify an existing file system name which you want to operate on
-D, --desc=DESCRIPTION Specify a description for the volume group. The description must be enclosed in
matched single (') or double (") quotes if it contains any blanks. The description can be up to 255 characters in
length. The default is an empty string
-c, --allocsize=ALLOCSIZE Specify the allocation size. The allocation size can be set to 4KB, 8KB, 16KB, 32KB,
64KB,128KB, 256KB, 512KB, 1MB, 2MB, 4MB, 8MB, 16MB, 32MB, or 64MB. Note: the allocation size must be
equal to or double of or quadruple the data blocksize the file system. The default size is quadruple the data block
size of the file system. Restriction: You can't change the allocation size after it is set.
-u, --storusage={stripe,fill,flfi}Set the storage usage to the volume group. The default is flfi.
-s, --stripesize=STRIPESIZESpecify the stripe size. The stripe size can be set to 256KB, 512KB, 1MB, 2MB, 4MB,
8MB, 16MB 32MB, 64MB, 128MB, 256MB, 512MB, 1GB, 2GB, 4GB 8GB, 16GB, 32GB, 64GB, 128GB, 256GB or
512GB. Note: The storusage must be specified to stripe before use this option. The stripe size must be greater
than or equal to the allocation size you specified for the volume group.
-e, --exclusive={on,off
Set the volume group to exclusive or nonexclusive. The default is off.
-h, --help
Display this help and exit
-v, --version
Output version information and exit
Add a volume group
bwvg --add --fsname FSNAME [--storusage stripe|fill|flfi][--desc DESCRIPTION]
[--allocsize ALLOCSIZE][--stripesize STRIPESIZE] [--exclusive on|off] vgname
Example:
bwvg --add --fsname fs1 --storusage fill --allocsize 256KB vg1
HyperFS User Guide
92
Command Line
Remove a volume group
bwvg --del --fsname FSNAME vgname
Example:
bwvg --del --fsname fs1 vg1
List the properties of all volume groups
bwvg --list --fsname FSNAME
Example:
bwvg --list --fsname fs1
Modify volume group attributes
bwvg --modify --fsname FSNAME [--storusage stripe|fill|flfi] [--stripesize STRIPESIZE]
[--exclusive on|off] [--desc DESCRIPTION] vgname
Example:
bwvg --modify --fsname fs1 --exclusive=off --storusage=stripe --stripesize=128MB vg1 bwvg
--modify --fsname fs1 --storusage=flfi --desc="change to media" vg1
Display this help
bwvg --help
Output version information
bwvg --version
bwvol
Description:
This command is used to manage volumes: add a volume to a file system, remove a volume from a file system,
move a volume to another volume group in a file system; list the properties of all volumes in a file system. Available
arguments:
-a, --add
Add a volume to a file system
-d, --del
Remove a volume from a file system
-l, --list
List the properties of all volumes in a file system
-m, --move
Move a volume to another volume group in a file system
-n, --fsname=FS_NAME
Specify the file system name which you want to operate on
-D, --device=DEVICE_NAME
Write label to the device DEVICE_NAME
-t, --type={meta,data,}
Specify a volume type for the volume
HyperFS User Guide
93
Command Line
-g, --group=VOL_GROUP
volume
Add volume to volume group VOL_GROUP, only specified when you add a data
-s, --desc=DESCRIPTION Specify a description for the volume. The description must be enclosed in matched
single (') or double (") quotes if it contains any blanks. This description can be up to 255 characters in length. The
default is an empty string.
-f, --force
Force to create volume even if the device is being used by other system when creating
volume. Or force to remove volume even if the physical device can't be found.
-F, --non-interactive
confirmation prompts.
Execute the bwvol command in non-interactive mode. The user does not receive
-h, --help
Display this help and exit
-v, --version
Output version information and exit
Add a volume to a file system
bwvol --add --fsname FSNAME --device DEVICE_NAME [--force] --type meta|data [--group
VOL_GROUP] [--desc DESCRIPTION] volume_name
Example:
bwvol --add --fsname fs1 --device /dev/sda --type data --group vg1 vol1 bwvol --add -fsname fs1 --device /dev/vd1 --type meta vol2
Remove a volume from a file system
bwvol --del --fsname FSNAME [--force] [--non-interactive] volume_name
Example:
bwvol --del --fsname fs1 vol1
List the properties of all volumes in a file system
bwvol --list --fsname FSNAME
Example:
bwvol --list --fsname fs1
Move a volume to another volume group
bwvol --move --fsname FSNAME --group VOL_GROUP volume_name
Example:
bwvol --move --fsname fs1 --group vg2 vol1
Display this help
bwvol --help
HyperFS User Guide
94
Command Line
Output version information
bwvol --version
bwmkfs
Description:
This command is used to format a file system. Available arguments:
-F, --non-interactive
Execute the bwmkfs command in non-interactive mode. The user does not receive
confirmation prompts. WARNING: Executing the 'bwmkfs' command without prompts results in an irreversible reinitialization of the file system. Use extreme caution when invoking this option.
-h, --help
Display this help and exit
-v, --version
Output version information and exit
Format a file system
bwmkfs [--non-interactive] fsname
Examples:
bwmkfs fs1
bwmkfs -F fs1
bwmkfs -F -c 16MB fs1
Output version information
bwmkfs --version
Display this help
bwmkfs --help
bwpolicy
Description:
This command is used to manage the file system policy: add or remove a binding between the directory and
volume group in a file system; display volume group properties for the selected directory or file in a file system.
Available arguments:
-n, --fsname=FSNAME Specify the file system name which you want to operate on
-a, --add
Add a binding between the directory and a certain volume group
-d, --del
Remove the binding between the directory and the volume group
-l, --list
Query the binding properties of a directory or a file
HyperFS User Guide
95
Command Line
-g, --vg=VG_NAME
Specify the binding volume group name
-h, --help
Display this help and exit
-v, --version
Output version information and exit
Add a binding relationship policy
bwpolicy --add --fsname FSNAME --vg VG_NAME directory
Example:
bwpolicy --add
--fsname fs1 --vg vg1 /bwfs/workspaces
Remove the binding relationship policy
bwpolicy --del --fsname FSNAME directory
Example:
bwpolicy --del
--fsname fs1 /bwfs/workspace
Query the binding relationship policy
bwpolicy --list --fsname FSNAME directory|file
Example:
bwpolicy --list --fsname fs1 /bwfs/workspace
Output version information
bwpolicy --version
Display this help
bwpolicy
--help
bwexportentry
Description:
This command is used to manage export entries: add an export entry to a file system, delete an export entry from a
file system, list, modify, and delete export entries in a file system. Available arguments:
-l, --list
Query export entries
-a, --add
Add an export entry to a file system
-d, --del
Delete an export entry from a file system
-m, --mod
Modify an export entry in a file system
-f, --fsname
Specify the file system name which you want to operate on
HyperFS User Guide
96
Command Line
-A, --all
All the export entries on the storage server will be accessed
-D, --dir
Indicates the export directory of a file system, MUST lead at'/'
-C, --clients
Indicates the clients who can access EXPORTDIR
-o, --options
The method used by those clients for accessing the EXPORTDIR
-L, --oneline
All the information of an export entry will be showed in one line
-F, --force
Will modify the export entries of a file system even if running
-V, --verbose
Display more detailed information during this CLI running
-v, --version
Output version information and exit
-h, --help
Display this help and exit
Option details:
-C, --clients
*
: anonymous users
@mygroup : a netgroup named "mygroup"
hname_*
: any hostname with fore 6 bytes matched "hname_"
10.10.2.0/24: a subnetwork
10.10.99.123: an IPv4 address
o, --options
readonly=yes|no
insecport=yes|no
squash=root|all|no_root
async=yes|no
nfsexport=yes|no
Add an export entry
bwexportentry --fsname="FSNAME" --add --dir="EXPORTDIR" --clients="a.b.c.d" -options="readonly=yes,squash=all,..."
Example:
bwexportentry --fsname=fs1 --add --dir=/bwfs/workspaces --clients=10.10.99.123 -options="readonly=yes,insecport=yes,squash=all,async=yes,nfsexport=no"
HyperFS User Guide
97
Command Line
Delete an export entry
bwexportentry --fsname="FSNAME" --del --dir="EXPORTDIR" --clients="a.b.c.d"
Example:
bwexportentry --fsname=fs1 --del --dir=/bwfs/workspaces --clients=10.10.99.123
Modify an export entry
bwexportentry --fsname="FSNAME" --mod --dir="EXPORTDIR" --clients="a.b.c.d" -options="readonly=no,squash=no_root,..."
Example:
bwexportentry --fsname=fs1 --mod --dir=/bwfs/workspaces --clients=10.10.99.123 -options="readonly=yes,squash=root"
Query file system export entries
bwexportentry --fsname="FSNAME" --list
Example:
bwexportentry --fsname=fs1 –list
Query export entries for all file systems
bwexportentry [--all] --list
Example:
bwexportentry --all –list
Output version information
bwexportentry --version
Display help
bwexportentry –help
bwdefrag
Description− HyperFS File System Defrag Utility
Description
bwdefrag is a utility for fragmentation analysis and defragmenting of file(s) in BWFS file system.Fragmentation level
of a file is evaluated according to an internal algorithm, which take into consideration the number and length of file
extents, the number and length of gap between extents. File(s) are online defragmented by relocating the live data
to take up less number of, and more continuous extents, thus speeding up sequential read performance. With stripe
configuration, it can be used to grow stripe sets and optimize the data across more striped data LUNs.
HyperFS User Guide
98
Command Line
OPTIONS
-d Doing defrag. By default, bwdefrag will print the fragmentation info about file only, without defragmenting it.
-r Processing the file under specified directory recursively.
-v Print more detailed fragmentation info.
-w Do not print warning message.
-h Print help message.
EXAMPLES
Print basic fragmentation information.
bwdefrag /path/to/file
Print verbose fragmentation information.
bwdefrag -v /path/to/file
Defrag a file.
bwdefrag -d /path/to/file
Defrag all file under a directory.
bwdefrag -dr /path/to/dir
Synopsis
bwdefrag [-drvwh] PATH...
Fragmentation Info
The fragmentation info about a file consist of following fields:
level
fragmentation level. May be none, low, medium, high.
Index
fragmentation index. Quantification of the file’s fragmentation level. A file with higher index is more fragmental.
Extent
Number of extents.
BWFS 5.4.1 March 2012 1
BWDEFRAG(8) BWDEFRAG(8)
breaks
Number of gap between logical adjacent extents in same volume.
dist
Value describing approximately average length of extent gap.
list of dist
Length of all extents gap.
HyperFS User Guide
99
Command Line
list of extent
Length of all extents.
NOTES
bwdefrag run only on MDS, do not use it on a client path. During defragmenting, bwdefrag will skip some file which
is considered not fragmental (fragmentation level is none). When there is no space large enough or more
continuous in the file system for some file, bwdefrag will abort the defrag of this file. Space larger then the file to be
defragmented is most important requirement. Only the superuser is allowed to defragment a file. Only the regular
file will be defragmented. special file, directory, or symbolic link will be bypassed. Symbolic links is not followed.
SEE ALSO
bwfsck
HyperFS User Guide
100
Index
A
Action log 79
Add
Client 75
Export path 75
External file system 51
File system 19, 39
Alerts, email 81
C
Change Password (admin) 17
CLI 85
Add a data placement policy 93
Add export path 94
Add file system 87
Add volume 91
Add volume group 89
Arguments 86
bwadmin
Manage file system 86
bwexportentry
Manage export paths 93
bwlicstat 88
Display and reload licensed features 88
bwlun
Manage devices 86
bwmkfs
Format file system 92
bwpolicy
Manage data placement policies 92
bwvg
Manage volume groups 89
bwvol
Manage volumes 90
Delete export path 95
Display data placement policy help 93
Display export path help 95
Display file system admin help 88
Display file system status 87
Display format file system help 92
Display version information 88
Display volume group help 90
Display volume help 91
Format file system 92
List all volume properties 91
List file systems 88
List volume group properties 90
Modify export path 95
Modify file system properties 88
Modify volume group attributes 90
Move volume 91
Output export path version information 95
Output policy version information 93
Output version information 90, 92
Query a data placement policy 93
Query export paths for all file systems 95
Query export paths for file system 95
Reload licensed features 88
Remove a data placement policy 93
Remove file system 88
Remove volume 91
Remove volume group 90
Set file system properties 88
Start file system 87
Stop file system 87
Clients
Export path 75
Configuration file
Backup 34
Restore 34
Configuration Wizard 19
Add file system 19
Volume 24
Volume group 23
Console 11
Command buttons 15
File system services status 15
Language 18
Launch 11
Log in 11
Navigation pane 14
Requirements 11
Service status area 15
D
Data block size 22
Data placement 28
Assign policy 28
Delete policy 32
HyperFS User Guide
101
Policy history 33
Query policy 30
Data volume 25
Delete 48
Move 48
Delete
Data volume 48
Export path 78
File system 41
Metadata volume 48
Volume group 44
Diagnostics, system 82
Analyze 82
Disk quotas 22
Modify 40
Modify unformatted file system 50
Mount 36
Mount point 21
Start 36
Start and stop 36
Stop 37
File System Monitor 13
File system services
Start/stop 15
Status 15
Fill 23
Flfi 24
Format and start file system 26
Format file system 35, 92
E
Email alerts 81
Event log 80
Delete event 80
Download 80
Filter 80
Export paths 75
Create 75
Delete 78
Modify 77
External file system
Add 51
Delete mount entry 55
Manage 54
Modify 55
Mount 54
Unmount 54
F
Failover
Rebuild 68
File system
Add 19, 39
Configuration file
Backup 34
Restore 34
Data block size 22
Delete 41
Expand data capacity 51
External
Add 51
Format 35
Format and start 26
Menu 19
G
Group quota
Add 69
Copy 72
Delete 71
Modify 71
H
HA cluster 60
HA configuration 63
Create file system 66
Delete 68
New 61
Start HA services 65
Upgrade from single-server system 61
HA management 66
Cluster status 67
Delete HA configuration 68
High Availability cluster 60
Migrate file system services 67
Rebuild member 68
Refresh HA status 68
Start HA services 67
Stop HA services 67
HA services 65, 67
Start 67
Stop 67
HyperFS
Clients 75
Command Line Utility 85
Components 4
Solution 1
HyperFS User Guide
102
I
Inode ratio 22
Installation 6
Filename 6
License 7
Next steps 8
Offline registration 8
Online registration 8
Prerequisites 5
Register license 7
Verify installed components 8
Verify license 7
L
Language
Change 18
Login 11
M
Management Console 11
Metadata Controller (MDC)
See HyperFS Server 4
Metadata Server (MDS)
See HyperFS Server 4
Metadata volume
Add 25
Delete 48
Modify
Export path 77
File system mount entry 55
Modify file system 40
Mount
External file system 54
File system 36
Events 73
Configure 73
Disk-space-usage threshold 74
Quota check interval 73
Modify quota 71
Quotacheck 72
R
Rebuild 68
S
Start file system 36
Stop file system 37
Stripe 24
System configuration
Download 83
System diagnostics 82
Analyze 82
System log 84
Display 84
Download 84
U
Unformatted file system
Modify 50
Unmount
External file system 54
File system 37
User quota
Add 69
Copy 72
Delete 71
Modify 71
V
N
Network 4
P
Password
Change 17
Q
Quota management 22
Add quota 69
Check 72
Copy quota 72
Delete quota 71
Email alerts 73
Volume
Add 46
Configure 24
Data 25
Delete 48
Metadata 25
Move data volume 48
Volume group
Add 43
Configure 23
Data placement 28
Assign policy 28
Delete policy 32
Policy history 33
HyperFS User Guide
103
Query policy 30
Delete 44
Fill 23
Flfi 24
Manage 42
Modify 43
Stripe 24
Volumes
Manage 44
HyperFS User Guide
104