EMC DiskXtender File System Manager for UNIX/Linux · PDF fileInitializing an existing file system ... EMC DiskXtender File System Manager for UNIX/Linux Release Version 3.5 SP1

EMC® DiskXtender®

File System Manager for UNIX/LinuxRelease 3.5 SP1

Linux/Novell OES 2 Version

Installation GuideP/N 300-012-245

REV A02

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

2

Copyright © 2004-2011 EMC Corporation. All rights reserved.

Published July, 2011

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC DiskXtender File System Manager for UNIX/Linux Release Version 3.5 SP1 Installation Guide

Contents

Preface ................................................................................................................................5

Chapter 1 IntroductionProduct description........................................................................... 10Set up roadmap ................................................................................. 11

Management domain .................................................................11Setting up management domain on single computer ...........12Setting up management domain on multiple computers .....12

Licensing............................................................................................. 14Installation requirements ................................................................. 15

Hardware .....................................................................................15Operating system ........................................................................16Software........................................................................................17File system type...........................................................................18Back-end system..........................................................................18

NFS client requirement..................................................................... 20

Chapter 2 InstallationPreinstallation task............................................................................ 22

Setting the DISPLAY ..................................................................22Installing the FSM host software .................................................... 23

Installation overview..................................................................23Installing the FSM host software ..............................................23

Installing FSM Console Client......................................................... 27Installing Console Client............................................................27

Console Client.................................................................................... 29Starting the Console Client........................................................29

Uninstalling........................................................................................ 30Uninstalling the software from UNIX and Linux ..................30Uninstalling the Console Client from UNIX and Linux........30

3EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Installation Guide

Contents

Chapter 3 UTDM File System PreparationSetting up the FSM environment.................................................... 34

Setting the FSM environment ................................................... 34File system formatting and initialization ...................................... 35

Formatting and initializing a file system ................................ 35File system formatting before initialization.................................. 37Initializing a newly formatted file system .................................... 38

The mkattrf utility ...................................................................... 38Initializing a file system for use with DMAPI........................ 39

Initializing an existing file system.................................................. 41Initializing an existing file system ........................................... 41

Mounting UTDM file systems ........................................................ 43Using the host’s file system table ............................................. 43Using the mount command ...................................................... 44

Appendix A Permanent LicensingPermanent product licensing .......................................................... 48

Appendix B File System Initialization Error MessagesDMAPI attributes filename ............................................................. 52Confirmation of more than 8 million inodes ................................ 53

Appendix C Alternate Mount Options for NFSOverview of NFS with UTDM file systems .................................. 56The retejukebox mount option........................................................ 57The dropejukebox mount option.................................................... 58

EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Installation Guide4

Preface

As part of an effort to improve and enhance the performance and capabilities of its product line, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this guide may not be supported by all revisions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this guide, please contact your EMC representative.

Audience This guide is part of the EMC DiskXtender File System Manager for UNIX/Linux (FSM), release 3.5. SP1 documentation set, and is intended for use by system administrators.

Readers of this guide are expected to be familiar with the following topics:

◆ Organization’s data archiving strategy:

• Average archived file size.

• Anticipated total number of files and total bytes to be archived.

• File access norms: frequency of access during creation, edit, and archive phases.

• Special file requirements, such as for shorter access times, multiple fail-safe copies, and optimal file stub size.

• Backup strategies for data in the file systems.

EMC DiskXtender File System Manager for UNIX/Linux Release Version 3.5 SP1 Installation Guide 5

6

Preface

◆ Network details of all computer systems and hardware devices to be used, including the following:

• IP addresses.

• TCP/IP routing information.

• Switch, router, firewall, and network-attached device configurations.

• Administration details of all involved storage targets.

Relateddocumentation

Related documents include:

◆ The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 HP-UX Version Installation Guide

◆ The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Solaris Version Installation Guide

◆ The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 AIX Version Installation Guide

◆ The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Console Client for Microsoft Windows Installation Guide

◆ The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Administrator’s Guide

◆ The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Release Notes

Conventions used inthis guide

EMC uses the following conventions for notes and cautions.

Note: A note presents information that is important, but not hazard-related.

IMPORTANT!An important notice contains information essential to operation of the software.


Preface

Typographical conventionsEMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• Names of resources, attributes, pools, Boolean expressions,

buttons, DQL statements, keywords, clauses, environment variables, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, filenames, links, groups, service keys, file systems, notifications

Bold Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs,

processes, services, applications, utilities, kernels, notifications, system calls, man pages

Used in procedures for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• What user specifically selects, clicks, presses, or types

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when

shown outside of running text

Courier bold Used for:• Specific user input (such as commands)

Courier italic Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example

EMC DiskXtender File System Manager for UNIX/Linux Release Version 3.5 SP1 Installation Guide 7

8

Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:

[email protected]


mailto:[email protected]

http://powerlink.emc.com

1

This chapter includes the following topics:

◆ Product description ........................................................................... 10◆ Set up roadmap .................................................................................. 11◆ Licensing ............................................................................................. 14◆ Installation requirements .................................................................. 15◆ NFS client requirement ..................................................................... 20

Introduction

Introduction 9

10

Introduction

Product descriptionThe EMC® DiskXtender® File System Manager (FSM) for UNIX/Linux, release 3.5 SP1 is a data management solution that uses DMAPI-enabled (Data Management API) file systems (UTDM file systems) to transparently archive data on the following back-end storage systems:

◆ The EMC Centera® Content Addressed Storage System (Centera system)

◆ Locally accessible disk resource

FSM transparently manages multiple local UTDM file systems. When necessary, it migrates and purges data from the file systems based on user-defined rules.

FSM frees up space by transferring the actual data associated with a file system object to a back-end system, while retaining the object’s metadata in the file system. This means that a migrated and purged file is fully available through the file system, but uses very little of the file system’s space.

It combines the ease-of-use of locally mounted file systems with automatic data migration and purging. FSM’s transparent migration and purging operations include the following benefits:

◆ Reduce file system space requirements.

◆ Maintain file system-level availability of data for all operations.

◆ Utilize scalable, reliable, and secure back-end systems for data storage.


Introduction

Set up roadmapTo enable UTDM file systems:

1. Evaluate and prepare the computers that host the UTDM file systems and FSM processes.

2. Install the software.

3. Initialize the file systems.

4. Configure the file systems.

5. Configure the storage target.

The file system is ready to use after these tasks are complete.

This guide provides information on the following:

◆ Procuring the product license

◆ Preinstallation requirements

◆ Overview of installation and post-installation tasks

◆ Installation information.

After successfully completing the tasks explained in this guide, the FSM software is installed, and at least one file system is set up and ready to be configured.

The final steps are to configure the UTDM file system and the storage target. The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Administrator’s Guide and the Console Client online help provide information on the configuration.

Management domainA management domain is a logical grouping of computers that host UTDM file systems (FSM hosts). In a management domain, all FSM hosts are controlled by the same FSM Console Server (Console Server).

Set up roadmap 11

12

Introduction

A management domain consists of the following essential components:

◆ Console Server

◆ FSM Console Client (Console Client)

◆ FSM host, with the following:

• FSM core processes (core processes)

• FSM Console Agent (Console Agent)

• UTDM file system

◆ Back-end system

Note: You can add multiple FSM hosts. However, you must install a permanent license on each FSM host.

You can set up a management domain entirely on one computer or on multiple computers.

Setting up management domain on single computerTo set up a management domain on a single computer:

1. Ensure that the computer meets the installation requirements.

2. Install the core processes, Console Server, and Console Agent.

3. Install the Console Client.

4. Prepare the UTDM file systems.

5. Configure the UTDM file systems.

6. Perform any necessary back-end system configuration.

Setting up management domain on multiple computersA management domain can consist of many computers. All the computers must have TCP/IP communication with the Console Server host and the Console Client host.

Console Server Console Server is a Java application that provides authentication services to the management domain. It is installed on a single computer that has TCP/IP access to all computers in the management domain.


Introduction

Console Server is installed with the core processes and the Console Agent software on one of the FSM hosts.

Console Client can be installed on the computer on which Console Server is installed.

Console Client Console Client is a Java application installed on computers with TCP/IP access to the management domain. Console Client simplifies the administrative tasks for the domain, including creation, configuration, management, and monitoring of the domain’s UTDM file systems.

Install Console Client on every computer that is used to administer UTDM file systems. It can be active on several computers at the same time.

The Console Client may run on an FSM host computer or on a separate computer.

FSM host A computer acting as an FSM host must have TCP/IP communication with the Console Server host and the Console Client host. FSM hosts need not have TCP/IP communication with other FSM hosts.

Each FSM host must have the following management domain components:

◆ Console Agent

The Console Agent is a Java application that interacts with the processes and file systems on an FSM host computer (FSM host).

◆ Core processes

◆ At least one UTDM file system

Set up roadmap 13

14

Introduction

LicensingFSM can be installed on each FSM host without a valid license. A temporary evaluation license valid for 30 days is available. After the expiry of the evaluation license, a permanent license is required on each FSM host if you intend to continue to use the product.

If available, you can provide the permanent license. Appendix A, “Permanent Licensing” provides instructions on how to apply your permanent license after installation.

When you install Console Server on a computer that is not an FSM host, it does not require a separate permanent license. Normally, Console Server is installed on one of the FSM hosts in a management domain.


Introduction

Installation requirementsThe following sections specify the mandatory requirements required for a successful installation and functioning of FSM:

◆ “Hardware” on page 15

◆ “Operating system” on page 16

◆ “Software” on page 17

◆ “File system type” on page 18

◆ “Back-end system” on page 18

HardwareThe role of a computer determines its hardware requirements. The potential roles are:

◆ Console Agent/UTDM file system host

◆ Console Server/Console Agent/UTDM file system host

◆ Console Client host

Note: The roles can be performed by a single or several computers.

Before installing the software, ensure that the host computer meets or exceeds the hardware requirements listed in Table 1 on page 15.

Table 1 Hardware requirements (page 1 of 2)

Hardware Console Server/Console Agent/UTDM file system host Console Client

Processor 500 MHz

Note: A minimum of one 500 MHz processor for every 10 million managed files is recommended.

500 MHz

RAM 512 MB

Note: A minimum of 2 GB of RAM for every 10 million managed files is recommended.

512 MB

Swap space 1. 5 times the RAM 1. 5 times the RAM

Installation requirements 15

16

Introduction

Operating systemThe following Linux operating system releases without the bigsmp kernel is supported:

◆ Redhat Enterprise Linux 5.1 for EM64T SMP




◆ SUSE Linux Enterprise Server (SLES)10 with Service pack2 for EM64T SMP

◆ SUSE Linux Enterprise Server10 with Service pack3 for EM64T SMP

◆ SUSE Linux Enterprise Server11 with Service pack1 for EM64T SMP

◆ Novell Open Enterprise Server 2 (OES2) with Service pack1 for EM64T SMP

◆ Novell Open Enterprise Server 2 (OES2) with Service pack2 for EM64T SMP

Hard drive space 500 MB

Note: 500 MB accommodates retention of the log files for a reasonable period. To provide additional room, 1 GB of hard drive space is recommended.

50 MB

Network interface 100 Mb/s

Note: 1 Gb/s is recommended.

100 Mb/s

Note: 1 Gb/s is recommended.

Monitor resolution 1024 x 768; 24 BPP 1024 x 768; 24 BPP

Table 1 Hardware requirements (page 2 of 2)

Hardware Console Server/Console Agent/UTDM file system host Console Client


Introduction

Library for hosts using Centera system back endLinux hosts that use the Centera system as a back end must have the following library installed:

◆ libstdc++.so.5

This library is installed as part of a standard Linux installation, but can be overlooked when an installation is customized. It is delivered in the following RPM:

◆ compat-libstdc++-33-3.2.3-47.3.i386.rpm

In a multiple computer management domain, the software can be installed on several different operating systems. “Related documentation” on page 6 provides information on other operating systems.

Note: The Console Client can be installed on Microsoft Windows. The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Console Client for Microsoft Windows Installation Guide describes how to install Console Client on Windows.

Library for installing 32-bit Console Client on Redhat Enterprise Linux 6.0On Redhat Enterprise Linux (RHEL) 64-bit operating system, the 32-bit compatible libraries are not installed by default. Therefore, to use the 32-bit Console Client on RHEL 6.0, you must install the following library manually:

glibc-2.12-1.7.el6.i686.rpm

This RPM is available in the installation package.

SoftwareThe following softwares must be installed on each computer to install FSM:

◆ Bourne shell (sh)

◆ Korn shell (ksh)

◆ Bourne Again shell (bash)


18

Introduction

File system typeUTDM file systems work with the following native file system types:

◆ EXT2

◆ EXT3

Back-end systemFSM integrates with the back-end system configurations described in the following sections.

Centera system You can configure a UTDM file system to use an Centera system as a back-end system on all FSM hosts.

The Centera system must meet the following requirements:

◆ CentraStar 2.3 (or later) firmware

◆ Read, write, and exist permissions to anonymous applications (the default setting) or authentication information for the FSM file systems to use

The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Administrator’s Guide provides more information about the Centera system permissions and authentication.

Centera system licensing modelsThe licensing model for Centera system affects how it applies retention periods for data migrated from a UTDM file system. Table 2 on page 19 describes the impact of the licensing models available for Centera system.


Introduction

Note: To provide enforcement of retention periods, the Centera system must use either the Governance Edition or the Compliance Edition Plus licensing model.

Locally accessibledisk resource

Configure a UTDM file system to use the NFS module with a locally accessible disk resource back end, such as any of the following:

◆ Local secondary disk

◆ Network-attached storage (NAS) disk

◆ Storage area network (SAN) disk

An FTP/SSL connection Configure a UTDM file system to use the FTP module with any back-end target that provides a standards-compliant FTP server that accepts an FTP connection or an FTP/SSL (either Auth TLS or Implicit FTPS) connection. The connection method must be in active mode.

Table 2 Centera system retention periods

Licensing model Retention settings Impact

Basic Retention Time is 0.Retention period settings of file systems are not enforced.

Data on the Centera system can be deleted and purged at any time.

Governance Edition (GE)

Retention Time is 0.Retention period settings of file systems are enforced.

Data on the Centera system cannot be deleted until its retention period has expired. After being deleted, the data can be purged.

Compliance Edition Plus (CE+)

Retention Time is infinite.Retention period settings of file systems are enforced.

Data on the Centera system cannot be deleted until its retention period has expired. Data can never be purged from the Centera system.


20

Introduction

NFS client requirementExport UTDM file systems and mount them on remote clients by using the NFS protocol. This permits remote users to access a UTDM file system without additional connection requirements. The remote clients must have NFS client software installed to utilize this protocol. The NFS client software must conform to NFS version 3 standards. When an NFS client request cannot be satisfied in 1 second or less, the UTDM file system sends an NFS3ERR_JUKEBOX message to the NFS client. This normally occurs when the data to satisfy the request must be retrieved from the file system’s storage target. NFS version 3 (and later) clients understand the NFS3ERR_JUKEBOX message and transparently repeat the request until it is satisfied.

NFS clients prior to version 3 do not understand the NFS3ERR_JUKEBOX message. The clients treat the message as an NFS server input/output (I/O) error. So, they, abandon the request and display an I/O error message.

Appendix C, “Alternate Mount Options for NFS,” provides more information about alternatives for older NFS clients.


2

This chapter describes the installation of the FSM software. It consists of the following topics:

◆ Preinstallation task............................................................................. 22◆ Installing the FSM host software ..................................................... 23◆ Installing FSM Console Client.......................................................... 27◆ Console Client .................................................................................... 29◆ Uninstalling......................................................................................... 30

Installation

Installation 21

22

Installation

Preinstallation taskBefore running the FSM installation programs, you set the DISPLAY environment variable. The DISPLAY environment variable sets the host, display number, and screen number to which the system sends bitmapped output.

You can skip this task if you do not want a bitmapped output to another system.

Setting the DISPLAYThe command to set the DISPLAY variable depends on your current shell:

◆ C shell (csh) and Turbo C shell (tcsh):

setenv DISPLAY hostname:x.y

◆ Bourne Again shell (bash):

export DISPLAY=hostname:x.y

◆ Korn shell (ksh) and Bourne shell (sh):

DISPLAY=hostname:x.yexport DISPLAY

where:

• hostname is the name or IP address of the computer to which the output is sent.

• x is the display number to which the output is sent.

• y is the screen number to which the output is sent.


Installation

Installing the FSM host softwareInstall the FSM host software by using the installation program. The installation program can be used to install the software required on each FSM host, including the Console Server host. Only one FSM host may have Console Server installed.

Installation overview◆ Displays the end-user license and service agreement (EULA) and

requests that you agree with its terms and conditions

◆ Sets the installation directory

◆ Sets the temporary directory to use during installation

◆ Determines if installation is new or an upgrade

◆ Determines if you have a software license key

◆ Offers to install Console Server and Console Agent, Console Server-only, or Console Agent-only

◆ Installs the software

Installing the FSM host software1. Obtain the installation archive file.

2. Log in as root on the host system.

3. Set the DISPLAY environment variable.

“Setting the DISPLAY” on page 22 provides more details.

4. Move the installation archive file into a temporary directory on the host.

5. Change your current working directory to the temporary directory.

6. Use the tar command to extract the installation files from the archive:

tar -xvf fsm.tar

where fsm.tar represents the name of the archive.

The command extracts the installation files into the temporary directory.

Installing the FSM host software 23

24

Installation

7. Set the installation program as executable:

chmod +x Install.fsm

8. Run the installation program:

./Install.fsm

The Setup screen appears.

Note: The Setup screen appears only if you have set the DISPLAY variable.The procedures assume that you have set the DISPLAY variable.

9. On the Setup screen, click Forward.

The License Agreement screen appears with the End User License Agreement (EULA) displayed. Read the EULA.

10. To continue the installation, on the License Agreement screen select I accept the agreement, and click Forward.

The Installation Directory screen appears.

11. On the Installation Directory screen, click Browse to open the Select File dialog box, select a directory, and click OK.

Note: If the path typed in the directory path in the text area does not exist, it is automatically created by the installer.

12. On the Installation Directory screen, click Forward.

The Temporary Directory screen appears.

13. On the Temporary Directory screen, click Browse to open the Select File dialog box, select a directory, and click OK.

Note: The temporary directory is used by the installation program to stage files during installation. It can be safely deleted after the installation is complete.

14. On the Temporary Directory screen, click Forward.

The Install/Upgrade screen appears.

On the Install/Upgrade screen, select Yes, and click Forward.


Installation

15. Selecting Yes causes the installation program to perform a new installation. The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Release Notes provide information on performing an upgrade of an existing FSM installation.

The License screen appears.

16. The License screen appears. On the License screen, select Yes if you have a valid license key, or select No if you do not, and click Forward:

• If you select No, a 30-day temporary license is installed.

• If you select Yes, a second License screen appears. Type the license key and click Forward.

The GUI Component Selection screen appears.

17. On the GUI Component Selection screen, select one of the following choices, and click Forward:

• Complete

This choice installs both Console Server and Console Agent.

• Console Server

• Console Agent

Note: “Configuration after Console Agent-only installation” on page 26 provides information about the modifications required when Console Agent is installed without Console Server.

If you did not type a valid license key, the 30 Day Evaluation License screen appears, click Forward.

The Ready to Install screen appears.

18. On the Ready to Install screen, click Forward.

The installation program installs the software. When the installation completes, the Installation Successful message appears.

19. On the Installation Successful message, click OK.

The Installation Successful text summary of the installation appears.

20. At the bottom of the Installation Successful text summary, click OK.

Installing the FSM host software 25

26

Installation

The Installation Successful text summary screen closes and the installation is complete.

Note: Depending on the resolution settings of your monitor, the OK button on the Installation Successful text summary screen may or may not be visible. If you cannot see it, use your mouse to grab (click and hold) the corner of the Installation Successful text summary screen and drag the corner in to resize it.

21. Restart the computer to load the DMAPI component of FSM.

Configuration afterConsole Agent-only

installation

After you install the software on several hosts in a management domain, only one of the hosts has Console Server installed. The other hosts determine the location of the Console Server host by using the FSMConsoleAgent.properties file.

Before using a FSM host that does not have Console Server installed, add the location of the Console Server host to its FSMConsoleAgent.properties file.

To add the location of Console Server on a host:

1. Log in as root on the host.

2. Open the FSMConsoleAgent.properties file in a plain text editor, such as vi:

vi /opt/fsm/etc/FSMConsoleAgent.properties

3. Modify the fsm.server.alias attribute:

fsm.server.alias=ConsoleServerHost

where ConsoleServerHost is the IP address of the Console Server host, or its resolvable hostname.

4. Save and close the file.

The configuration is complete.

5. Restart the computer to enable the change.


Installation

Installing FSM Console ClientThis section describes how to install and start Console Client. Console Client is FSM’s graphical administrative tool. You can install and run Console Client on several computers.

Console Client is provided as a 32-bit binary and as a 64-bit binary. For best performance on 64-bit platforms, install the 64-bit version using FSMClient_IA64.bin. The 32-bit version is provided for remote 32-bit systems being used to monitor FSM hosts. To install the 32-bit version use FSMClient.bin.

Note: This section covers installing Console Client on a Linux computer.The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Console Client for Microsoft Windows Installation Guide provides information on installing Console Client on a Windows computer.

Installing Console Client1. Log in as root on the host computer.



3. Change the current working directory to the location of the Console Client installation file.

This file may be copied to the host computer by itself or as part of the installation directory structure. When the installation directory structure is available on the computer, the file is located at:

/install-dir/installers/OS/

where:

• install-dir is the top-level of the installation directory structure.

• OS represents the operating system of the host computer.

• Use the correct installation file for the host computer:FSMClient_IA64.bin for 64-bit computers

• FSMClient.bin for 32-bit computers

4. Start the Console Client Setup Wizard:

./CC_installer

Installing FSM Console Client 27

28

Installation

where CC_installer iseither FSMClient_IA64.bin or FSMClient.bin.

The wizard starts. The Setup screen appears.

5. On the Setup screen, click Forward.

The License Agreement screen appears with the EULA displayed. Read the EULA.

6. To continue the installation, on the License Agreement screen select I accept the agreement, and click Forward.

The Installation Directory screen appears.

7. On the Installation Directory screen, click Browse to open the Select File dialog box, select a directory, and click OK.

Note: Any directory path typed in the text area is created by the installer, if it does not already exist.

8. On the Installation Directory screen, click Forward.

The Ready to Install screen appears.

9. On the Ready to Install screen, click Forward.

The wizard installs the software.

10. When the installation completes, click Forward.

The wizard closes.


Installation

Console ClientConsole Client uses an encrypted username/password combination (account) to authenticate Console Client users and determine permissions.

A default administrative account is provided with Console Client. This default account has the username "system" and the password "system". To increase the security of the management domain, the password for this account should be changed immediately. EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Administrator’s Guide provides information on changing the password.

An administrator may install Console Client on several supported operating systems. The release notes provide a complete list of the operating systems supported by Console Client.

Starting the Console Client1. Allow X Window connections:

xhost +



3. Run the Console Client application:

/opt/fsm/client/File_System_Manager_Console_Client &

The Login to DiskXtender File System Manager screen appears.

4. Type a username.

The preconfigured administrative username is system.

5. Type a password.

The preconfigured administrative password for username system is system.

Note: You should change the default password for the system account as soon as possible. The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Administrator’s Guide provides information on how to do this.

Console Client 29

30

Installation

6. Type the hostname or IP address of the management domain’s Console Server host.

7. Click OK.

The main Console Client window appears.

The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Administrator’s Guide provides information on using Console Client to configure file systems.

UninstallingThere are two separate uninstallers. One of the installers removes the following product entirely:

◆ The core processes

◆ Console Agent

◆ Console Server

◆ Console Client

The other removes only the Console Client software.

Uninstalling the software from UNIX and LinuxTo uninstall the entire product:

1. Log in to the FSM host as root.

2. Copy the uninstaller file to /tmp:

cp /opt/fsm/etc/uninstall.fsm /tmp

3. Change the current working directory to /tmp:

cd /tmp

4. Run the uninstaller:

./uninstall.fsm

The entire product is uninstalled.

Uninstalling the Console Client from UNIX and LinuxTo uninstall the Console Client software from UNIX and Linux hosts:

1. Log in to the Console Client host as root.


Installation

2. Run the uninstall script:

/opt/fsm/client/uninstall

The following prompt appears:

Do you want to uninstall File System Mnager Console Client and all of it's modules?

3. Click Yes.

Uninstalling 31

32

Installation


3

This chapter describes how to use the FSM command line tools to prepare file systems for configuration.

File system preparation consists of the following tasks:

◆ Formatting

◆ Initializing

◆ Mounting

Completely prepared UTDM file systems have the DMAPI component enabled. The DMAPI component implements an advanced set of file management extensions. These extensions include interfaces for data management and maintenance and capabilities perform the following:

◆ Monitor file events.

◆ Store extended attribute information with a file.

◆ Manage regions within a file.

◆ Control access to a file.

The file system preparation process is described in the following sections:

◆ Setting up the FSM environment ..................................................... 34◆ File system formatting and initialization ....................................... 35◆ File system formatting before initialization ................................... 37◆ Initializing a newly formatted file system...................................... 38◆ Initializing an existing file system ................................................... 41◆ Mounting UTDM file systems.......................................................... 43

UTDM File SystemPreparation

UTDM File System Preparation 33

34

UTDM File System Preparation

Setting up the FSM environmentSetting the FSM environment does the following:

◆ Provides path information that is required by the FSM utilities.

◆ Permits the FSM man pages to be read by using the standard man command.

When you install FSM, two files are created that contain the information that is required to set the environment. The files, fsm.login and fsm.profile, are placed in the etc directory at the top level of the FSM installation directory.

For a default installation, this directory path is as follows:

/opt/fsm/etc

The FSM environment is set by sourcing one of these files. The file depends upon your current command interpreter (shell):

◆ C shell (csh) and Turbo C shell (tcsh):

Use the fsm.login file.

◆ Bourne Again shell (bash), Korn shell (ksh), and Bourne shell (sh):

Use the fsm.profile file.

Setting the FSM environment1. Log in as root on the FSM host system.

2. Use the correct source command and file for the current shell:

• C shell (csh) and Turbo C shell (tcsh):

source /opt/fsm/etc/fsm.login

• Bourne Again shell (bash), Korn shell (ksh), and Bourne shell (sh):

. /opt/fsm/etc/fsm.profile



File system formatting and initializationThe utdm_mkfs utility performs the formatting and initializing tasks in one operation. The file system is then ready for mounting.

Note: “Mounting UTDM file systems” on page 43 provides information on mounting the formatted and initialized file system.

This procedure involves the following tasks:

◆ Format the file system as a native file system type.

◆ Initialize the file system.

Initialization prepares a UTDM file system. This must be done before the file system may be configured for FSM. The initialization process creates a DMAPI attributes file such as .DMATTR and .DMATTR_STAT file in the root directory of the file system. FSM stores DMAPI metadata for the file system in the .DMATTR file and stores FSM statistics for the file system in the .DMATTR_STAT file.

Formatting and initializing a file system1. Log in as root on the host that controls the new file system’s block

device.

2. Create a partition on the block device for the new file system.

Set up the FSM environment. “Setting up the FSM environment” on page 34 provides more information.

3. Run utdm_mkfs:

utdm_mkfs -t fs -n files [-o opts] blkdev mntpnt

where:

• fs is the file system type, either ext2 or ext3.

• files is the number of files the DMAPI attributes file must manage.

The size of the block device divided by the expected average file size provides a rough estimate of this number.

• opts are any file system-specific options.

• blkdev is the full path to the partition on the block device.

• mntpnt is the full path to the file system’s mount point.

File system formatting and initialization 35

36


The mount point specified must not exist when you run utdm_mkfs.

The utdm_mkfs command is designed to protect existing file systems. It stops, without performing any changes, if any one of the following conditions is true:

– Mount point specified already exists.– Mount point specified is listed in the file system table file.– Referenced device is listed in the file system table file.

4. Create the file system’s mount point:

mkdir /mntpnt

Note: This mount point must be the same as the one that you specified when utdm_mkfs was run.

The UTDM file system is formatted and initialized. The next task is to mount the file system, as described in “Mounting UTDM file systems” on page 43.



File system formatting before initializationThis section describes how to format a UTDM file system without using the utdm_mkfs utility. Use the utility as described in “File system formatting and initialization” on page 35 and skip this section.

If you follow the procedure described here, you must also complete the steps described in “Initializing a newly formatted file system” on page 38.

A UTDM file system is initially formatted as an ext2 or ext3 file system. The ext2 and ext3 file systems must be formatted with an appropriate number of inodes. The number of inodes has a significant impact on the file system’s migration and purging performance.

Formatting a file system

1. Log in as root on the system that controls the new file system’s block device.

2. Run mkfs:

mkfs -t fs -N inodes /blkdev

where:

• fs is the file system type, either ext2 or ext3.

• inodes is the appropriate number of inodes.

• blkdev is the full path to the block device.

File system formatting before initialization 37

38


Initializing a newly formatted file systemThis section describes how to initialize a UTDM file system without using the utdm_mkfs utility. Normally you should use the utility as described in “File system formatting and initialization” on page 35 and skip this section.

After the UTDM file system is formatted, it must be initialized. Initialization prepares it to be configured for FSM.

The initialization process creates a DMAPI attributes file such as .DMATTR and .DMATTR_STAT file in the root directory of the file system. FSM stores DMAPI metadata for the file system in the .DMATTR file and stores FSM statistics for the file system in the .DMATTR_STAT file.

The basic procedure to initialize a UTDM file system is the following:

1. Create a temporary directory.

2. Mount the file system’s block device on the temporary directory.

3. Write the file system’s .DMATTR file and .DMATTR_STAT file to the block device by using the FSM utility mkattrf.

4. Unmount the block device from the temporary directory.

5. Remove the temporary directory.

The .DMATTR file and .DMATTR_STAT file is written on the formatted file system by using a temporary mount point. The .DMATTR file and .DMATTR_STAT file still exists after the file system is unmounted from this temporary mount point.

Note: When the file system is mounted as type UTDM, any attempt to change or remove the .DMATTR file and .DMATTR_STAT file is prevented at the kernel level. Attempts to work around or defeat this kernel-level protection may result in data corruption and loss.

The mkattrf utilityThe mkattrf utility is the UTDM file system initialization tool. You use it to create the .DMATTR file and and .DMATTR_STAT file. This file is an integral part of an FSM file system.

For each UTDM file system, use mkattrf to create the .DMATTR file and .DMATTR_STAT file. The file must be named as .DMATTR and



.DMATTR_STAT and must be created at the top level of the file system’s block device.

The command line format for mkattrf is as follows:

mkattrf -t fs /tmp-mnt/.DMATTRmkattrf -S /tmp-mnt/.DMATTR_STAT

where:

◆ fs is the native file system type, either ext2 or ext3.

◆ tmp-mnt is the full path to the temporary mount point of the file system.

Initializing a file system for use with DMAPI1. Log in as root on the host that controls the block device that you

are using to create the new file system.

2. Create a temporary directory to use as a mount point for the initialization:

mkdir /temp-mnt

where temp-mnt is the full path to the temporary directory.


3. Type the mount command:

mount -t fs /blkdev /temp-mnt

where:

• fs is the native file system type, either ext2 or ext3.

• blkdev is the full path to the block device partition on which the file system resides.

• temp-mnt is the full path to the temporary directory.

4. Use the mkattrf utility to create the .DMATTR file and .DMATTR_STAT file:

mkattrf -t fs /temp-mnt/.DMATTRmkattrf -S /temp-mnt/.DMATTR_STAT

where:


• temp-mnt is the full path to the temporary directory.

Initializing a newly formatted file system 39

40


5. Type the umount command:

umount /temp-mnt

6. Delete the temporary directory:

rmdir /temp-mnt



Initializing an existing file systemYou can migrate an existing file system to a UTDM file system. To do this, the file system must be initialized by using utdm_initexistingfs. The utdm_initexistingfs command creates a .DMATTR file and .DMATTR_STAT file. The .DMATTR file is created for the file system and is populated with the entries for the existing data in the file system. The .DMATTR_STAT file stores the FSM file system statistics.

The utdm_initexistingfs command is designed to protect the existing file system and data. It stops without performing any changes if either of the following is true:

◆ The mount point specified is listed in the file system table file.

◆ The referenced device is listed in the file system table file.

You must comment out the file system’s listing from the file system table file in order to permit utdm_initexistingfs to migrate the file system.

IMPORTANT!Donot migrate an existing file system that contains more than 8,388,608 inodes. This inode figure represents a nominal upper limit beyond which a system administrator should carefully consider the effect of the number of inodes being supported. Surpassing this limit can eventually lead to exceeding the number of inodes that a UTDM file system can manage without performance degradation.

Initializing an existing file system1. Log in as root on the host that controls the file system’s block

device.

2. Unmount the file system.

3. Comment out the file system’s listing from the file system table (/etc/fstab).


Initializing an existing file system 41

42


4. Run utdm_initexistingfs:

utdm_initexistingfs -t fs -n files blkdev mntpnt

where:


• files is the number of files the DMAPI attributes file must manage.

Note: The size of the block device divided by the expected average file size provides a rough estimate of this number.


• mntpnt is the full path to the mount point.

The file system is initialized. The next task is to mount it. “Mounting UTDM file systems” on page 43 provides information.



Mounting UTDM file systemsMount a UTDM file system through the host’s file systems table or from the command line. Both methods use the mount command to perform the actual mount.

To mount a UTDM file system, the mount command is passed with a file system-type argument of utdm and an option that specifies the underlying native file system type.

Note: Mounting a file system by using the utdm argument ensures that the UTDM kernel module monitors the file system. The UTDM kernel module intercepts file system activity and implements interfaces that allow FSM to manage the file system. The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Administrator’s Guide provides information on advanced mount options.

Consider the following when deciding whether to mount a file system by using the host’s file systems table, or by issuing a mount command from the command line:

◆ Creating an entry in the host’s file systems table ensures that the file system is mounted every time you restart the system.

◆ Mounting the file system from the command line is a shorter procedure, but must be repeated each time you restart the system.

Note: In limited instances, the default mount settings must be overridden by passing an NFS mount option to mount. This should only be done to solve a problem caused by older NFS clients on remote hosts. Appendix C, “Alternate Mount Options for NFS,” provides more information.

To use file retention with a file system, you must enable fileretention when the file system is mounted. The EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 SP1 Administrator’s Guide provides information about setting up file retention.

Using the host’s file system tableTo mount an FSM file system by using the /etc/fstab file:

1. Log in as root on the host that controls the file system’s block device.

Mounting UTDM file systems 43

44


2. Open the /etc/fstab file in a plain text editing application, such as vi.

3. Add a new entry to the /etc/fstab file:

4. /blkdev /mntpnt utdm fstype=fs 0 2

where:




Save and close the file.

5. Run the mount command:

mount /mntpnt

Note: This step is not required when the system is restarted. The UTDM file system is automatically mounted when you restart the system.

Using the mount command1. Log in as root on the host that controls the file system’s block

device.

2. Run the mount command:

mount -t utdm -o fstype= /blkdev /mntpnt

where:




Example 1 on page 44 describes how to mount a file system from the command line.

Example 1 Mounting a UTDM file system from the command line

For this example, assume that a UTDM file system is formatted as follows:

◆ Native file system type is ext3.



◆ Full path to the partition on the block device is /dev/dsk/c0t0d0s1.

◆ Full path to the file system mount point is /mnt/fsmfs01.

The mount command is:

mount -t utdm -o fstype=ext3 /dev/dsk/c0t0d0s1 /mnt/fsmfs01

Note: In RHEL 6.0, Security Enhanced Linux (SELinux) is enabled by default. Because of this, you need to include extra parameters when mounting the file system.

The mount command is,

mount -t utdm -o fstype=ext3,context=unconfined_u:object_r:file_t:s0 /dev/sde1 /mnt/utdm_ext3/

Mounting UTDM file systems 45

46



AInvisible Body Tag

If you have installed FSM with a 30-day evaluation license, you must procure a permanent license after the evaluation or trial period is over. This appendix describes the steps to perform to procure a permanent license for FSM:

◆ Permanent product licensing ........................................................... 48

Permanent Licensing

Permanent Licensing 47

48

Permanent Licensing

Permanent product licensingTo obtain and install a permanent FSM product license:

1. Log in as root on an FSM host.

Note: You must obtain and install a permanent license on every FSM host.

2. Set up the FSM environment.

“Setting up the FSM environment” on page 34 provides information about setting up the environment for each type of shell.

3. Obtain the machine ID that is displayed when the software is installed.

If the machine ID that is displayed during the installation is not available, type the following command to obtain the alphanumeric ID of the FSM host:

testlicense -i

4. Contact licensing with the following information:

• The machine ID

• The required license capacity (in terabytes)

“Where to get help” on page 8 provides information on how to contact licensing.

5. After you receive a license string, change the current working directory:

cd /opt/fsm/etc

6. Write the license string into the existing FSM.license file:

echo "license_string"> /opt/fsm/etc/FSM.license

where license_string is the actual license string (include the quotation marks).

7. Display the contents of the FSM.license file:

cat FSM.license


Permanent Licensing

The displayed value must match the license string that you received. If it does not, repeat the previous step.

8. Stop the FSM processes:

/opt/fsm/etc/kill.fsm

9. Restart the FSM processes:

/opt/fsm/etc/rc.fsm

The FSM host is licensed.

Verifying your licenseTo verify that your license works correctly:

1. Run testlicense:

testlicense

2. When prompted, type the license string.

The value you type must match the license string that is provided by EMC:

Please enter license string:

When you type a valid license string, three lines appear with the second line showing the license size (in gigabytes):

License string is okverified for (number) GBlicense will expire: NEVER

49

50

Permanent Licensing


BInvisible Body Tag

The mkattrf utility displays messages to confirm important values and to report errors.

Messages displayed by mkattrf are described in the following sections:

◆ DMAPI attributes filename .............................................................. 52◆ Confirmation of more than 8 million inodes.................................. 53

File System InitializationError Messages

File System Initialization Error Messages 51

52

File System Initialization Error Messages

DMAPI attributes filenameThe mkattrf utility identifies the following errors during the creation of the .DMATTR and .DMATTR_STAT files:

◆ Bad new filename

Specifying any new filename other than .DMATTR and .DMATTR_STAT files causes mkattrf to display the message:

Pathname must be a directory or end with ".DMATTR".Pathname must be directory or end with ".DMATTR_STAT.

◆ No filename

If the full path to the directory that you are using for the .DMATTR file is specified without naming the .DMATTR file, the mkattrf utility appends the .DMATTR filename to the directory path. Similarly, if the full path to the directory that you are using for the .DMATTR_STAT file is specified without naming the .DMATTR_STAT file, the mkattrf utility appends the .DMATTR_STAT filename to the directory path.

◆ Filename exists

Specifying a pathname that ends in an existing file causes mkattrf to display the following message:

Specified pathname exists but is not a directory.Pathname must be directory or end with ".DMATTR".



Confirmation of more than 8 million inodesThe mkattrf utility requires confirmation before initializing a file system with more than approximately 8 million inodes. This check is performed for all file system types, irrespective of whether the -n option is used or not.

The inode figure is not a hard limit; it simply represents a nominal upper limit beyond which a system administrator should consider the effect of the number of inodes being supported. The number could eventually exceed the number that a UTDM file system could manage without performance degradation.

When mkattrf determines that the maximum number of inodes for a file system is greater than 8,388,608, the following message appears:

Large number of files (N) may result in degradedperformance.Continue (y/n):

The variable N is the number of inodes that is specified with the -n option, or reported by the file system.

Note: This message can appear even when you have not specified a number of inodes while using the mkattrf utility.

53

54



C

This appendix describes alternate mount options that you can use to resolve problems with NFS clients on remote hosts.

It addresses the following topics:

◆ Overview of NFS with UTDM file systems.................................... 56◆ The retejukebox mount option......................................................... 57◆ The dropejukebox mount option ..................................................... 58

Alternate MountOptions for NFS

Alternate Mount Options for NFS 55

56

Alternate Mount Options for NFS

Overview of NFS with UTDM file systemsWhen an NFS client sends a data request to an NFS server, the server creates a kernel thread that exists until the data is transmitted to the client. If the data is not transmitted within the NFS client’s time-out period, the client assumes the request did not reach the NFS server and sends the request again.

This behavior is acceptable when data from the exported file system can quickly be accessed and transmitted. However when exported file system must retrieve data from back-end storage, problems can occur.

During the time required to retrieve the data from back-end storage, many kernel threads can be created for one data request. The NFS server can eventually run out of kernel threads, stop responding, and lock up the exported file system.

UTDM file systems avoid this problem through the use of special mount options. The special options prevent the creation of multiple kernel threads for a single NFS data request. This prevents the NFS server from running out of resources and refusing to respond.



The retejukebox mount optionThe retejukebox option is the default mount option for UTDM file systems. It is built into the UTDM kernel and is automatically applied when a UTDM file system is mounted.

This mount option causes the NFS server to return the error code NFS3ERR_JUKEBOX whenever it cannot satisfy a request for data in 1 second or less.

NFS version 3 clients that receive this error code retry the request in 10 seconds. The kernel thread created to handle the initial request is freed as soon as NFS3ERR_JUKEBOX is returned to the NFS client.

Subsequent retries of the request result in the return of NFS3ERR_JUKEBOX, until the data is received from the back-end system.

The NFS client continues to retry the request until it is fulfilled. There is never more than one kernel thread existing for the request.

Use this default option unless trouble occurs. Always use it when the following applies:

◆ NFS version 3 clients are being used on all remote hosts.

◆ Data retrieval times average 10 seconds or longer.

◆ The exported file system is mounted by using the TCP protocol type of NFS.

57

58


The dropejukebox mount optionThe dropejukebox option can be passed to mount to override the default retejukebox option.

This option causes the NFS kernel threads to be dropped as soon as the UTDM kernel module detects that data retrieval is taking longer than 1 second. No reply is sent to the client.

The client retries the request until it is fulfilled. There is never more than one NFS server kernel thread created for the request.

When the NFS client mounts the exported file system by using the UDP protocol, the initial client reset time is 2 seconds. When the NFS client mounts the exported file system by using the TCP protocol, the initial client reset time is 180 seconds.

The reset time increases each time an NFS client repeats a request to a maximum of 10 minutes.

Use this option when the following applies:

◆ The NFS client protocol is earlier than version 3.

◆ The NFS client does not recognize NFS3ERR_JUKEBOX.

Using the dropejukebox optionTo mount a UTDM file system by using the file systems table with the dropejukebox option:


2. Open /etc/fstab in a plain text editing application, such as vi.

3. Add a new entry, all on one line:

/blkdev /mntpnt utdm fstype=fs,dropejukebox 0 2

where:




4. Save and close the file.



5. Type the mount command without rebooting:

mount /mntpnt

Note: When the system is rebooted, the UTDM file system is automatically mounted.

To mount a UTDM file system from the command line with the dropejukebox option:


2. Type the mount command:

mount -t utdm -o fstype=fs,dropejukebox /blkdev /mntpnt

where:

• fs is the native type of the file system, either ext2 or ext3.


mntpnt is the full path to the file system’s mount point.

59

Documents

EMC DiskXtender File System Manager for UNIX/Linux · PDF fileInitializing an existing file system ... EMC DiskXtender File System Manager for UNIX/Linux Release Version 3.5 SP1