EMC® DiskXtender® Manager for UNIX/ Release 3.5 AIX Version

Installation Guide P/N 300-009-574 REV. A01

EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.EMC.com Copyright © 2004-2009 EMC Corporation. All rights reserved. Published October 2009 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 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 3.5 AIX Version Installation Guide 2 Contents

Preface...... 5

Chapter 1 Introduction Product description ...... 10 Set up roadmap ...... 11 Management domain ...... 11 Licensing ...... 14 Installation requirements...... 15 Hardware ...... 15 ...... 16 Software ...... 16 File system type...... 17 Back-end system ...... 17 NFS client requirement ...... 20

Chapter 2 Installation Setting the DISPLAY ...... 22 Installing the FSM host software ...... 23 How to install the FSM host software...... 23 Installing FSM Console Client...... 27 How to install Console Client ...... 27 Starting Console Client ...... 29 How to start Console Client...... 29 Uninstalling ...... 31 Uninstalling the software from UNIX and Linux ...... 31 Uninstalling Console Client from UNIX and Linux...... 31

EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide 3 Chapter 3 UTDM File System Preparation Setting up the FSM environment...... 34 How to set the FSM environment ...... 34 File system formatting ...... 35 Formatting a JFS file system...... 35 Initializing a newly formatted file system ...... 39 The mkattrf utility ...... 39 How to initialize a file system for use with DMAPI ...... 40 Initializing an existing file system...... 42 How to initialize an existing file system ...... 42 Mounting UTDM file systems ...... 44 Using the host’s file systems table ...... 44 How to use the mount command...... 47

Appendix A Permanent Licensing Permanent product licensing...... 50 Verifying your license...... 51

Appendix B File System Initialization Error Messages DMAPI attributes filename ...... 54 Confirmation of nondefault number of ...... 55 Confirmation of more than eight million inodes ...... 56

4 Preface

As part of an effort to improve and enhance the performance and capabilities of its product line, EMC from time to time 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 documentation set, and is intended for use by system administrators. Readers of this guide are expected to be familiar with the following topics:

◆ Their organization’s data archiving strategy, in particular: • 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. • strategies for data in the file systems. ◆ The network details of all computer systems and hardware devices to be used, including:

Preface 5 Preface

• IP addresses. • TCP/IP routing information. • Switch, router, firewall, and network-attached device configurations. ◆ The administration details of all involved storage targets.

Organization This guide is organized as follows: ◆ Chapter 1, “Introduction,” provides an overview of the installation process. ◆ Chapter 2, “Installation,” describes how to install the software. ◆ Chapter 3, “UTDM File System Preparation,” explains how to perform the file system preparation tasks of formatting, initializing, and mounting. ◆ Appendix A, “Permanent Licensing,” describes how to apply a permanent license to an FSM host. ◆ Appendix B, “File System Initialization Error Messages,” provides helpful information about error messages that sometimes occur during initialization of a file system.

Related Related documents include: documentation ◆ Installation guides for these supported operating systems: • HP-UX • Linux • Solaris • Linux/Novell OES version 2 ◆ Installation guide for the Microsoft Windows version of Console Client ◆ Administrator’s guide

Conventions used in EMC uses the following conventions for notes and cautions. this guide Note: A note presents information that is important, but not hazard-related.

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

6 Preface Preface

Typographical conventions EMC 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

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

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

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]

8 Preface 1

Introduction

This chapter includes: ◆ Product description ...... 10 ◆ Product description ...... 10 ◆ Licensing ...... 14 ◆ Installation requirements...... 15 ◆ NFS client requirement ...... 20

Introduction 9 Introduction

Product description EMC® DiskXtender® File System Manager for UNIX/Linux (FSM), release 3.5 is a data management solution that uses DMAPI-enabled file systems (UTDM file systems) to transparently archive data on the following back-end storage systems: ◆ EMC Centera® Content Addressed Storage System (EMC Centera) ◆ 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: ◆ 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.

10 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide Introduction

Set up roadmap To enable UTDM file systems, you perform a series of sequential tasks: 1. Evaluate and prepare the computers that are to 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. After these tasks are complete, the file system is ready to use. This guide contains licensing, preinstallation requirements, and installation information for FSM. After completing the steps in this guide, the software is installed, and at least one file system is set up and ready to be configured for FSM. The final steps are to configure the UTDM file system and the storage target. These steps are described in the administrator's guide, and in the Console Client online help.

Management domain A 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). A management domain consists of the following essential pieces: ◆ 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

Set up roadmap 11 Introduction

Note: You may add more than one FSM host. This release requires that you install a permanent license on each FSM host.

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

Single computer To set up a management domain on a single computer, perform the following installation tasks: ◆ Ensure that the computer meets the installation requirements. ◆ Install the core processes, Console Server, and Console Agent. ◆ Install the Console Client. ◆ Prepare the UTDM file systems. ◆ Configure the UTDM file systems. ◆ Perform any necessary back-end system configuration.

Multiple computers A management domain can consist of many computers. All of 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. Console Server is installed with the core processes and Console Agent software on one of the FSM hosts. The computer on which Console Server is installed may also have Console Client installed. Console Client Console Client is a Java application that you install 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. You install Console Client on every computer that is used to administer UTDM file systems. It may be active on several computers at the same time.

12 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide Introduction

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 Introduction

Licensing FSM installs on each FSM host without a license. In that state, it is fully functional for 30 days. A permanent license is required on each FSM host if you intend to continue to use the product after the 30-day trial period. If available, your permanent license may be applied during installation. Appendix A, “Permanent Licensing” provides instructions on how to apply your permanent license after installation. Console Server, when installed on a computer that is not an FSM host, does not require a separate permanent license. Normally, Console Server is installed on one of the FSM hosts in a management domain.

14 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide Introduction

Installation requirements To ensure a successful installation, certain requirements must be met. The requirements are described in the following sections: ◆ “Hardware” on page 15 ◆ “Operating system” on page 16 ◆ “Software” on page 16 ◆ “File system type” on page 17 ◆ “Back-end system” on page 17

Hardware The 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 500 MHz

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

RAM 512 MB 512 MB

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

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

Installation requirements 15 Introduction

Table 1 Hardware requirements (page 2 of 2)

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

Hard drive space 500 MB 50 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.

Network interface 100 Mb/s 100 Mb/s

Note: 1 Gb/s is recommended. Note: 1 Gb/s is recommended.

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

Operating system This release is supported on AIX release 5.3 on RS/6000 computers. In a multiple computer management domain, the software may be installed on several different operating systems. “Related documentation” on page 6 provides information on other operating systems.

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

64 Bit mode This release requires that the operating system run in 64-bit mode.

Fsize limit The fsize attribute in /etc/security/limits must be set to -1 before using the mkattrf file system initialization tool. This setting removes file system size limits in order to allow the DMAPI attribute file to expand as needed. After changing the fsize attribute, quit and restart the shell. Restarting causes the OS to read the new setting from the limits file, and must be done before using the mkattrf tool.

Software To successfully install this release, the following software must be installed on each computer:

16 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide Introduction

◆ Bourne shell (sh) ◆ Korn shell (ksh) ◆ Bourne Again shell (bash)

File system type UTDM file systems work with the following native file system types: ◆ Journaled File System (JFS), formatted with the largefiles option ◆ JFS2

Back-end system This release is designed to integrate with the back-end system configurations described in the following sections.

EMC Centera You may configure a UTDM file system to use an EMC Centera as a back-end system on all FSM hosts. The EMC Centera must meet the following requirements: ◆ Use the CentraStar 2.3 (or later) firmware. ◆ Provide read, write, and exist permissions to anonymous applications (the default setting) or provide authentication information for the FSM file systems to use. The administrator’s guide provides more information about EMC Centera permissions and authentication. EMC Centera licensing models The licensing model for an EMC Centera affects how it applies retention periods for data migrated from a UTDM file system. The impact of the licensing models available for an EMC Centera is described in Table 2 on page 18.

Installation requirements 17 Introduction

Table 2 Centera system retention periods

Licensing model Retention settings Impact

Basic Retention Time is 0. Data on the EMC Centera can be Retention period settings of deleted and purged at any time. file systems are not enforced.

Governance Retention Time is 0. Data on the EMC Centera cannot be Edition (GE) Retention period settings of deleted until its retention period has file systems are enforced. expired. After being deleted, the data can be purged.

Compliance Edition Retention Time is infinite. Data on the EMC Centera cannot be Plus (CE+) Retention period settings of deleted until its retention period has file systems are enforced. expired. Data can never be purged from the EMC Centera.

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

18 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide Introduction

Locally accessible disk resource You may 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

FTP server You may 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 active mode.

Installation requirements 19 Introduction

NFS client requirement You can export 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 in order 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. Earlier NFS clients do not understand the NFS3ERR_JUKEBOX message. Those clients treat the message as an NFS server input/output (I/O) error, abandon the request, and display an I/O error message.

20 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide 2

Installation

This chapter describes the installation of the FSM software. It addresses the following topics: ◆ Setting the DISPLAY ...... 22 ◆ Installing the FSM host software ...... 23 ◆ Installing FSM Console Client...... 27 ◆ Starting Console Client...... 29 ◆ Uninstalling...... 31

Installation 21 Installation

Setting the DISPLAY Before 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. The command you use 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.y export 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.

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

Installing the FSM host software You install the FSM host software by using its 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. The installation program does the following: ◆ 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

How to install the FSM host software To install the FSM host software: 1. 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 describes how to do this. 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 Installation

7. Set the installation program as executable: +x Install.fsm 8. Run the installation program: ./Install.fsm The Setup screen appears. 9. On the Setup screen, click Next. The License Agreement screen appears with the EULA displayed. Scroll through the EULA to read it. 10. To continue the installation, on the License Agreement screen select I accept the agreement, and click Next. The Installation Directory screen appears. 11. On the Installation Directory screen, click the browse button 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.

12. On the Installation Directory screen, click Next. The Temporary Directory screen appears. 13. On the Temporary Directory screen, click the browse button 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 Next. The Install/Upgrade screen appears. 15. On the Install/Upgrade screen, select Yes, and click Next. Selecting Yes causes the installation program to perform a new installation. The release notes provide information on performing an upgrade of an existing FSM installation. The License screen appears.

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

16. On the License screen, select Yes if you have a valid license key, or select No if you do not, and click Next: • 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 Next. The GUI Component Selection screen appears. 17. On the GUI Component Selection screen, select one of the following choices, and click Next: • 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 that are 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 Next. The Ready to Install screen appears. 18. On the Ready to Install screen, click Next. 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. The Installation Successful text summary screen closes and the installation is complete.

Installing the FSM host software 25 Installation

Note: Depending on the resolution settings of your monitor, the OK button on the Installation Successful text summary screen 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 after Console Agent-only installation When you install this software on several hosts in a management domain, only one of those 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. Reboot the computer to enable the change.

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

Installing FSM Console Client This section describes how to install and start Console Client. Console Client is FSM’s graphical administrative tool. You may install and run Console Client on several computers. Console Client is provided as a 32-bit binary . 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 an AIX computer. EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Console Client for Microsoft Windows Installation Guide provides information on installing Console Client on a Windows computer.

How to install Console Client To install Console Client: 1. Log in as root on the host computer. 2. Set the DISPLAY environment variable. “Setting the DISPLAY” on page 22 describes how to do this. 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.bin for 32-bit computers 4. Start the Console Client Setup Wizard: ./CC_installer where CC_installer is FSMClient.bin.

Installing FSM Console Client 27 Installation

The wizard starts. The Setup screen appears. 5. On the Setup screen, click Next. The License Agreement screen appears with the EULA displayed. Scroll through the EULA to read it. 6. To continue the installation, on the License Agreement screen select I accept the agreement, and click Next. The Installation Directory screen appears. 7. On the Installation Directory screen, click the browse button 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 Next. The Ready to Install screen appears. 9. On the Ready to Install screen, click Next. The wizard installs the software. 10. When the installation completes, click Next. The wizard closes.

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

Starting Console Client Console 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 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.

How to start Console Client To start Console Client: 1. Allow X Window connections: xhost + 2. Set the DISPLAY environment variable. “Setting the DISPLAY” on page 22 describes how to do this. 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. EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Administrator’s Guide provides information on how to do this.

Starting Console Client 29 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. EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Administrator’s Guide provides information on using Console Client to configure file systems.

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

Uninstalling This release has two separate uninstallers: ◆ One removes the entire product: • The core processes • Console Agent • Console Server • Console Client ◆ The other removes only the Console Client software.

Uninstalling the software from UNIX and Linux To 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 Console Client from UNIX and Linux To uninstall the Console Client software from UNIX and Linux hosts: 1. Log in to the Console Client host as root. 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 3

UTDM File System Preparation

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 to: ◆ 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...... 35 ◆ Initializing a newly formatted file system...... 39 ◆ Initializing an existing file system ...... 42 ◆ Mounting UTDM file systems...... 44

UTDM File System Preparation 33 UTDM File System Preparation

Setting up the FSM environment Setting 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 you should use 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.

How to set the FSM To set the FSM environment: environment 1. 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

34 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide UTDM File System Preparation

File system formatting A UTDM file system is initially formatted as a JFS or JFS2 file system. When a JFS file system is used, it must use the Large File Enabled Journaled File System option and have an appropriate number of bytes per (nbpi).

Note: JFS2 file systems dynamically allocate inodes and do not need to have the nbpi determined when they are created. JFS2 file systems are also Large File-enabled by default.

Formatting a JFS file JFS file systems must be formatted with both of the following: system ◆ Nondefault nbpi ◆ Large File Enabled Journaled File System option JFS2 file systems do not require these formatting steps. JFS2 file systems automatically allocate inodes, and enable large files by default. To use a JFS2 file system with FSM, format it normally and then initialize it. “Initializing a newly formatted file system” on page 39 and “Initializing an existing file system” on page 42 provide information on how to initialize both JFS and JFS2 file systems.

Determining a file The default value for nbpi on a JFS file system is 4,096. Formatting a system’s number of 100 GB device with the default value creates over 26 million inodes. bytes per inode value FSM stores 32 bytes of information in its DMAPI attributes file (.DMATTR) for every inode. The .DMATTR file for a 100 GB device, formatted with the default nbpi value, contains over 800 MB of inode information. This inode information is scanned every time a migration or purge occurs which can increase the time required to perform those tasks. By setting the nbpi to a higher value, more in keeping with the average size of the files, the time required to complete automatic migration and purge activity is significantly reduced.

File system formatting 35 UTDM File System Preparation

On a JFS file system, the nbpi value is selected from the following choices: ◆ 512 ◆ 1,024 ◆ 2,048 ◆ 4,096 ◆ 8,192 ◆ 16,384 ◆ 32,768 ◆ 65,536 ◆ 131,072 To determine which choice is best, compute the nbpi value for the file system by using the following formula: ()allocatedsize÷ numberfiles ÷ 2 = nbpi Divide the allocated size of the new file system, in bytes, by the maximum number of files that are expected to be in the file system. Divide the result by 2 to derive the nbpi. Select the available choice that is closest to the suggested value.

Example 1 Computing a file system’s nbpi value.

A maximum of 100,000 files is expected in a UTDM file system. A 100 GB (107,374,182,400 bytes) block device is allocated to the file system: ()107374182400÷ 100000 ÷ 2 = 536871 The nbpi value is 536,871. The closest nbpi choice is 131,072. When this value is used to format the file system, 819,200 inodes are allocated to the file system and the inode information portion of the .DMATTR file is 25 MB.

Enabling the Large File To properly format a JFS file system for FSM, enable the Large File option Enabled Journaled File System option. Specifying this option removes a limit of 2 GB on the size of the .DMATTR file. This allows the file system to continue to grow, even when the .DMATTR file is 2 GB or larger. The .DMATTR file stores 32 bytes for every inode and 1,024 bytes for every file that is migrated. Without the Large File Enabled Journaled File System option, the .DMATTR file cannot exceed 2 GB. When that

36 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide UTDM File System Preparation

limit is reached, the file system cannot accept any more files and cannot perform migrations. Formatting the file system with the Large File Enabled Journaled File System option removes this limitation.

How to format a JFS To format a JFS (not JFS2) file system: file system 1. Decide on the following parameters for the file system: • Volume group • Mount point • Size in bytes • Size in 512-byte blocks • nbpi value “Determining a file system’s number of bytes per inode value” on page 35 provides information on computing the nbpi value. 2. Log in as root on a system with control over the new file system’s volume group. 3. Start the System Management Interface Tool (smit). 4. Select System Storage Management (Physical & Logical Storage). The System Storage Management (Physical & Logical Storage) window appears. 5. Select File Systems. The File Systems window appears. 6. Select Add/Change/Show/Delete File Systems. The Add/Change/Show/Delete File Systems window appears. 7. Select Journaled File Systems. The Journaled File Systems window appears. 8. Select Add a Journaled File System. The Add a Journaled File System window appears. 9. Select Add a Large File Enabled Journaled File System. The Single Select List appears. 10. In Volume Group Name, select the volume group. 11. Click OK.

File system formatting 37 UTDM File System Preparation

The Add a Large File Enabled Journaled File System window appears. 12. In Unit Size, type a unit size to use in measuring the file system’s size. Use the unit size typed here in the next step. 13. In Number of Units (Num.), type the number of units in the file system. For example, if the unit size is MB and the file system is 1 GB, you type 1024 here. 14. In Mount Point, type the full path to the file system’s mount point, with a leading forward slash and no trailing forward slash. 15. In Mount Automatically, select Yes. 16. In PERMISSIONS, leave the default value (read/write). 17. In Mount Options, leave the field blank. 18. In Start Disk Accounting, select Yes or No.

Note: Disk accounting provides useful information with a slight, usually negligible, performance loss.

19. In Number of Bytes Per Inode, type the number of bytes per inode for the file system. Normally you should set this at 131072. The appropriate value is determined in step 1. 20. In Size (MBytes), select an appropriate value. Normally the default value of 64 MB is appropriate. 21. Click OK. The new file system is created and formatted. 22. Click Exit to close smit.

38 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide UTDM File System Preparation

Initializing a newly formatted file system 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 (.DMATTR) in the root directory of the file system. FSM stores DMAPI metadata for the file system in the .DMATTR file. The basic procedure you use 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 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 is written on the formatted file system by using a temporary mount point. The .DMATTR 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 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 utility The mkattrf utility is the UTDM file system initialization tool. You use it to create the .DMATTR file. This file is an integral part of an FSM file system. For each UTDM file system, use mkattrf to create the .DMATTR file. The file must be named .DMATTR 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 [-n inodes]/tmp-mnt/.DMATTR where: ◆ fs is the native file system type, either jfs or jfs2. ◆ inodes is the inode value to provide for in the .DMATTR file.

Initializing a newly formatted file system 39 UTDM File System Preparation

The -n option with the inodes argument is only applicable to JFS file systems. The brackets surrounding -n inodes indicate that the option and argument are not required. The brackets are not part of the command and should not be included when mkattrf is run. ◆ tmp-mnt is the full path to the temporary mount point of the file system.

How to initialize a To initialize a formatted file system for use with DMAPI: file system for use with DMAPI 1. 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. Set up the FSM environment. This is described in “Setting up the FSM environment” on page 34. 4. Type the lsfs command to list the formatted JFS file system’s logical volume path: lsfs /mnt-pnt where /mnt-pnt is the file system’s mount point. Two lines are returned. The first line is a set of column headers. The second line is the file system’s information for each column. The full path to the file system’s logical volume appears in the Name column. In Figure 1 on page 40, the logical volume’s path is /dev/lv07.

Name Nodename Mount Pt VFS Size Options Auto Accounting /dev/lv07 -- /mnt/utdm5 jfs 17301504 rw,log=/dev/loglv01 yes no

Figure 1 File system information returned from the lsfs command

5. Type the mount command: mount -V fs -o log=/logicalvol-log /logicalvol /temp-mnt where:

40 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide UTDM File System Preparation

• fs is the native file system type, either jfs or jfs2. • logicalvol-log is the logical volume log file that is generated. • logicalvol is the full path to the file system’s logical volume. • temp-mnt is the full path to the temporary directory.

6. Use the mkattrf utility to create the .DMATTR file: mkattrf -t fs [-n inodes]/temp-mnt/.DMATTR where: • fs is the native file system type, either jfs or jfs2. • inodes is the inode value to provide for in the .DMATTR file. The brackets surrounding -n inodes indicate that the option and argument are not required. The brackets are not part of the command and should not be included when mkattrf is run. This option is only used with JFS file systems. • temp-mnt is the full path to the temporary directory. 7. Type the umount command: umount /temp-mnt 8. Delete the temporary directory: rmdir /temp-mnt

Initializing a newly formatted file system 41 UTDM File System Preparation

Initializing an existing file system You 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 for the file system and populates the file with entries for the existing data in the file system. 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 It is not recommended that you 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.

How to initialize an To initialize an existing file system: existing file system 1. 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/filesystems). 4. Set up the FSM environment. This is described in “Setting up the FSM environment” on page 34.

42 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide UTDM File System Preparation

5. Run utdm_initexistingfs: utdm_initexistingfs -t fs -n files -o log=/logicalvol-log blkdev mntpnt where: • fs is the native file system type, either jfs or jfs2. • 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.

• logicalvol-log is the logical volume log file that is generated. • blkdev is the full path to the block device partition on which the file system resides. • 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 44 provides information about how to do this.

Initializing an existing file system 43 UTDM File System Preparation

Mounting UTDM file systems You can mount 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 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 administrator’s guide provides information on advanced mount options.

In 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, consider the following: ◆ Creating an entry in the host’s file systems table ensures that the file system is mounted every time the system is rebooted. ◆ Mounting the file system from the command line is a shorter procedure, but must be repeated each time the system is rebooted. To use file retention with a file system, you must enable it when the file system is mounted. The administrator’s guide provides information about setting up file retention.

Using the host’s file systems table To mount a UTDM file system by using the file systems table: 1. Log in as root on the system that controls the file system’s volume group. 2. Open /etc/filesystems in a plain text editing application, such as vi. Find the entry for the file system that was previously created with smit, as described in “Formatting a JFS file system” on page 35. 3. Edit the entry so that it is mounted as a UTDM file system.

44 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide UTDM File System Preparation

The initial entry is similar to Figure 2 on page 45, where: • /mntpnt is the full path to the file system’s mount point. • logicalvol is the logical volume name that is generated. • logicalvol-log is the logical volume log file that is generated. • fs is the native type of the file system, either jfs or jfs2.

/mntpnt: dev = /dev/logicalvol vfs = fs log = /dev/logicalvol-log mount = true options = rw account = false

Figure 2 The entry before editing for FSM

Note: In filesystems file entries, the parameters are on the left of the equals sign and the arguments are on the right.

Change the entry as follows: • For the vfs parameter, substitute utdm for the fs argument. • For the options parameter, add the following arguments after the rw argument (the arguments must be separated by commas): – fstype=fs where fs is the native type of the file system, either jfs or jfs2. – log=/dev/logicalvol-log where the logicalvol-log value is not changed. After editing, the entry looks similar to Figure 3 on page 46.

Mounting UTDM file systems 45 UTDM File System Preparation

/mntpnt: dev = /dev/logicalvol vfs = utdm log = /dev/logicalvol-log mount = true options = rw,fstype=fs,log=/dev/logicalvol-log account = false

Figure 3 The entry after editing for FSM

4. Save and close the file. 5. To mount the file system without rebooting, type the mount command: mount /mntpnt

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

Example 2 Mounting a UTDM file system by using the file systems table

For this example, assume that a file system is formatted for use as a UTDM file system with the following characteristics: ◆ Volume name is lv01. ◆ Native file system type is jfs2. ◆ Full path to the logical volume log is /dev/lv01log. ◆ Full path to the file system’s mount point is /mnt/fsmfs01. To correctly mount the UTDM file system, the /etc/filesystems file is edited so that the entry for the file system appears as follows: /mnt/fsmfs01: dev = /dev/lv01 vfs = utdm log = /dev/lv01log mount = true options = rw,fstype=jfs2,log=/dev/lv01log account = true check = false

46 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide UTDM File System Preparation

How to use the To mount a UTDM file system by using the mount command: mount command 1. Log in as root on the host that controls the file system’s block device. 2. Run the mount command: mount -V utdm -o fstype=fs,log=/dev/logicalvol-log /dev/logicalvol /mntpnt where: • fs is the native file system type, either jfs or jfs2. • logicalvol is the logical volume name that is generated. • logicalvol-log is the logical volume log file that is generated. • mntpnt is the full path to the file system’s mount point. Example 3 on page 47 describes how to mount a file system from the command line.

Example 3 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 jfs2. ◆ Full path to the file system mount point is /mnt/fsmfs01. ◆ Full path to the logical volume is /dev/lv01. ◆ Full path to the logical volume log is /dev/lv01log. The mount command is: mount -V utdm -o fstype=jfs2,log= /dev/lv01log /dev/lv01log /mnt/fsmfs01

Mounting UTDM file systems 47 Invisible Body Tag A

Permanent Licensing

To enable a permanent license for FSM, perform the steps described in the following section: ◆ Permanent product licensing ...... 50

Permanent Licensing 49 Permanent Licensing

Permanent product licensing To obtain and install a permanent FSM product license: 1. Log in as root on an FSM host.

Note: a This release requires that you 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 7 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

50 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide 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 license To 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 ok verified for (number)GB license will expire: NEVER

51 Invisible Body Tag B

File System Initialization Error Messages

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...... 54 ◆ Confirmation of nondefault number of inodes ...... 55 ◆ Confirmation of more than eight million inodes...... 56

File System Initialization Error Messages 53 File System Initialization Error Messages

DMAPI attributes filename The mkattrf utility catches the following errors during the creation of the .DMATTR file: ◆ Bad new filename Specifying any new filename other than .DMATTR causes mkattrf to display the message: Pathname must be a directory or end with ".DMATTR".

◆ 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. ◆ 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".

54 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 AIX Version Installation Guide File System Initialization Error Messages

Confirmation of nondefault number of inodes When you use the -n option to specify a nondefault number of inodes on a JFS2 file system, the mkattrf utility requires confirmation that the specified number of inodes is correct. The following message appears: Will create DM attribute file with N maximum files. Please ensure that this value is correct before continuing. Continue (y/n):

where N represents the number of inodes specified with the -n option.

Note: This issue only applies to the JFS2 file system. The JFS file system does not dynamically allocate inodes, so the -n option is not used.

55 File System Initialization Error Messages

Confirmation of more than eight million inodes The 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, whether or not the -n option is used. 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 degraded performance. 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.

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