EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Solaris Version

Transcription

1 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Solaris Version Installation Guide P/N REV. A01 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright 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. 2 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Solaris Version Installation Guide

3 Contents Preface...5 Chapter 1 Chapter 2 Introduction Product description Set up roadmap Management domain...11 Licensing Installation requirements Hardware Operating system Software File system type Back-end system NFS client requirement Installation Setting the DISPLAY Installing the FSM host software How to install the FSM host software...23 Installing FSM Console Client How to install Console Client...27 Starting Console Client How to start Console Client...29 Uninstalling 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 Solaris Version Installation Guide 3

4 Chapter 3 Appendix A Appendix B Appendix C UTDM File System Preparation Setting up the FSM environment How to set the FSM environment File system formatting and initialization How to format and initialize a file system File system formatting before initialization Formatting a UFS file system for FSM Formatting a VxFS file system How to format a VxFS file system Initializing a newly formatted file system Setting the maximum files for a VxFS file system The mkattrf utility How to initialize a file system for use with DMAPI Initializing an existing file system How to initialize an existing file system Mounting UTDM file systems Using the host s file systems table How to use the mount command Using the delaylog mount option Permanent Licensing Permanent product licensing Verifying your license File System Initialization Error Messages DMAPI attributes filename Using the -n option on UFS file systems Confirmation of nondefault number of inodes Confirmation of more than eight million inodes Alternate Mount Options for NFS Overview of NFS with UTDM file systems The retejukebox mount option The dropejukebox mount option How to use the dropejukebox option

5 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. Backup strategies for data in the file systems. The network details of all computer systems and hardware devices to be used, including: Preface 5

6 Preface IP addresses. TCP/IP routing information. Switch, router, firewall, and network-attached device configurations. The administration details of all involved storage targets. Organization Related documentation Conventions used in this guide 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. Appendix C, Alternate Mount Options for NFS, describes the mount options you can use to correct problems caused by older NFS clients. Related documents include: Installation guides for these supported operating systems: AIX HP-UX Solaris Linux/Novell OES version 2 Installation guide for the Microsoft Windows version of Console Client Administrator s guide EMC uses the following conventions for notes and cautions. Note: A note presents information that is important, but not hazard-related. 6 Preface

7 Preface! IMPORTANT An important notice contains information essential to operation of the software. 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 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Solaris Version Installation Guide 7

8 Preface 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. 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: 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: SSGdocumentation@emc.com 8 Preface

9 1 Introduction This chapter includes: Product description Product description Licensing Installation requirements NFS client requirement Introduction 9

10 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 Solaris Version Installation Guide

11 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

12 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 Multiple computers 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. 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 Solaris Version Installation Guide

13 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

14 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 Solaris Version Installation Guide

15 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 17 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 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 Table 1 Hardware requirements (page 2 of 2) Hardware Console Server/Console Agent/UTDM file system host Console Client 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 Operating system This release is supported on the following Solaris operating system (OS) releases: Solaris 9 for 64-bit SPARC Solaris 10 for 64-bit SPARC You can install this release in a Solaris 10 zone, either local or global. The administrator s guide provides more information about how to run FSM in a Solaris zone. 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. Semaphore undo requirements When a Solaris 9 or 10 FSM host manages 30 file systems or more the host can run out of semaphore undo structures. To avoid this resource issue add the following line to /etc/system: set semsys:seminfo_semmnu= EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Solaris Version Installation Guide

17 Introduction This setting has minimal impact on system resources. Stacksize requirements To provide an adequate stacksize for FSM on both Solaris 9 and 10, the following lines are added automatically to /etc/system by the installation program: set lwp_default_stksize=0x8000 set rpcmod:svc_default_stksize=0x8000 Software To successfully install this release, the following software must be installed on each computer: Bourne shell (sh) Korn shell (ksh) Bourne Again shell (bash) The shared object /usr/lib/libz.so.1 File system type UTDM file systems work with the following native file system types: UNIX file system (UFS) VxFS 4.1 (Solaris 10 only) VxFS 5.0 Back-end system EMC Centera This release is designed to integrate with the back-end system configurations described in the following sections. 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. Installation requirements 17

18 Introduction 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. 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 EMC Centera can be deleted and purged at any time. Governance Edition (GE) Compliance Edition Plus (CE+) Retention Time is 0. Retention period settings of file systems are enforced. Retention Time is infinite. Retention period settings of file systems are enforced. Data on the EMC Centera cannot be deleted until its retention period has expired. After being deleted, the data can be purged. Data on the EMC Centera cannot be deleted until its retention period has 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 Solaris Version Installation Guide

19 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

20 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. Appendix C, Alternate Mount Options for NFS, provides more information about alternatives for older NFS clients. 20 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Solaris Version Installation Guide

21 2 Installation This chapter describes the installation of the FSM software. It addresses the following topics: Setting the DISPLAY Installing the FSM host software Installing FSM Console Client Starting Console Client Uninstalling Installation 21

22 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 Solaris Version Installation Guide

23 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

24 Installation 7. Set the installation program as executable: chmod +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 Solaris Version Installation Guide

25 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

26 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 Solaris Version Installation Guide

27 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 a Solaris 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

28 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 Solaris Version Installation Guide

29 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

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. 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 Solaris Version Installation Guide

31 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

32 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 File system formatting and initialization File system formatting before initialization Initializing a newly formatted file system Initializing an existing file system Mounting UTDM file systems UTDM File System Preparation 33

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 environment To set the FSM 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 Solaris Version Installation Guide

34 UTDM File System Preparation File system formatting and initialization The 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 45 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 (.DMATTR) in the root directory of the file system. FSM stores DMAPI metadata for the file system in the.dmattr file. How to format and initialize a file system To format and initialize a file system: 1. 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. 3. Set up the FSM environment. This is described in Setting up the FSM environment on page Run utdm_mkfs: utdm_mkfs -t fs -n files [-o opts] blkdev chardev mntpnt where: fs is the file system type, either ufs or vxfs. 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. File system formatting and initialization 35

35 UTDM File System Preparation To specify a non-default VxFS disk layout, you use the -o argument. For example, to use a version 4 disk layout, the -o argument is: -o version= 4 Note: You do not need to add the largefiles option that is required for VxFS version 4 layouts. The utdm_mkfs command applies that option automatically. blkdev is the full path to the partition on the block device. chardev is the full path to the partition on the character device. mntpnt is the full path to the file system s mount point. 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. 5. 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 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Solaris Version Installation Guide

36 UTDM File System Preparation File system formatting before initialization This section describes how to format a UTDM file system without using the utdm_mkfs utility. Normally you should use the utility in the manner 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 40. A UTDM file system is formatted first as a UFS or VxFS file system using specific formatting guidelines. The guidelines for these file system types are the following: UFS file systems must be formatted to create an appropriate number of inodes. VxFS file systems using a version 4 disk layout must be formatted with the largefiles option. Formatting a UFS file system for FSM A UFS file system must be formatted with an appropriate number of bytes per inode (nbpi) in order to obtain the correct number of inodes for the file system. The number of inodes that are created for a UFS file system has a significant impact on migration and purging performance. Note: UFS file systems have a limit on the nbpi value. This value cannot be set above Computing a file system s number of bytes per inode The default value for nbpi on a UFS file system is 2,048. This value can cause too many inodes to be created. For instance, formatting a 100 GB file system with the default value creates over 58 million inodes. FSM stores 32 bytes of information in its DMAPI attributes file (the.dmattr file) for every inode. The.DMATTR file for a 100 GB file system, formatted with the default nbpi value, contains over 1.5 GB of inode information. This inode information must be scanned every time a migration or purge occurs. By setting the nbpi to a higher value that is 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 before initialization 37

37 UTDM File System Preparation To compute an appropriate nbpi value for a UTDM file system, use the 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. For an example of this, see Example 1. Example 1 Computing a File System s nbpi Value A maximum of 100,000 files is expected in a UTDM file system and 100 GB (107,374,182,400 bytes) is allocated to the file system: ( ) 2 = The nbpi value is 536,871. Formatting the file system by using this value results in 200,000 inodes and a.dmattr file that is 6.1 MB. How to format a UFS file system 1. Compute the file system s nbpi value. Computing a file system s number of bytes per inode on page 37 provides information on this. 2. Log in as root on the host that controls the new file system s block device. 3. Create a partition on the block device for the new file system. 4. Type the newfs command: newfs -i nbpi /chardev where: nbpi is the appropriate number of bytes per inode. chardev is the full path to the new partition s character device. 5. Create the file system s mount point: mkdir /mntpnt where mntpnt is the full path to the mount point you will use for the file system. Formatting a VxFS file system To format a VxFS file system you specify file system type vxfs. Disk layout versions are specified using the -o option version=n. Disk layout version 4 must also include the -o option largefiles. 38 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Solaris Version Installation Guide

38 UTDM File System Preparation The largefiles option removes a limit of 2 GB on the size of the.dmattr file. This allows a file system to continue to grow, even after the.dmattr file reaches 2 GB. The.DMATTR file stores 32 bytes for every inode and 1,024 bytes for every file that is migrated. Without the largefiles option, the.dmattr file cannot exceed 2 GB. When that limit is reached, the file system cannot accept any more files and cannot perform migrations. Formatting the file system with the largefiles option removes this limitation. Note: The VxFS file system dynamically creates inodes, which eliminates the requirement of computing the number of bytes per inode. However, dynamic inode creation raises a different consideration during the initialization of the file system, as described in Setting the maximum files for a VxFS file system on page 40. How to format a VxFS file system To format a VxFS file system: 1. 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. 3. Type the mkfs command: mkfs -F vxfs -o version= n[,largefiles] /chardev where: n is the disk layout version The option argument largefiles is only included for a version 4 disk layout Note: The largefiles argument is only applicable to a version 4 disk layout. The brackets surrounding the argument indicate that it is optional. The brackets are not part of the command and should not be included when mkfs is run. When included, the argument is separated from other -o arguments by a comma. chardev is the full path to the new partition s character device 4. Create the file system s mount point: mkdir /mntpnt where mntpnt is the full path to the mount point you will use for the file system. File system formatting before initialization 39

39 UTDM File System Preparation Initializing a newly formatted file system This 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 (.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. Setting the maximum files for a VxFS file system The FSM utility, mkattrf, uses the number of inodes allocated to a file system to determine how much inode storage space to create in the.dmattr file. Once the.dmattr file is created, this amount is fixed. VxFS file systems create inodes as needed. This means that the number of inodes initially allocated to a VxFS file system will not normally reflect the file system s final inode use. For such file systems, the mkattrf utility uses a default value to determine the 40 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Solaris Version Installation Guide

40 UTDM File System Preparation.DMATTR file inode storage space. The default value is based on the maximum number of inodes reported by the file system. For VxFS file systems that report an insufficient number of inodes to handle anticipated usage, you should use the -n option of mkattrf. This option does the following: Specifies the anticipated number of required inodes. Forces the appropriate allocation of inode storage space in the.dmattr file. Note: The suggested number of inodes to specify with the -n option is twice the anticipated maximum number of files to be placed into the UTDM file system. 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 ufs or vxfs. inodes is the inode value to provide for in the.dmattr file. The -n option with the inodes argument is only applicable to VxFS 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 file system for use with DMAPI To initialize a formatted 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. Initializing a newly formatted file system 41

41 UTDM File System Preparation 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 Type the mount command: mount -F fs /blkdev /temp-mnt where: fs is the native file system type, either ufs or vxfs. 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. 5. 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 ufs or vxfs. 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 VxFS file systems. temp-mnt is the full path to the temporary directory. 6. Type the umount command: umount /temp-mnt 7. Delete the temporary directory: rmdir /temp-mnt 42 EMC DiskXtender File System Manager for UNIX/Linux Release 3.5 Solaris Version Installation Guide

42 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 existing file system To initialize an 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/vfstab). 4. Set up the FSM environment. This is described in Setting up the FSM environment on page 34. Initializing an existing file system 43