EMC File Management Appliance and File Management Appliance/VE Version 7.3.2

Transcription

1 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide P/N REV A11 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright EMC Corporation. All rights reserved. Published July, 2010 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 2 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

3 Contents Preface Chapter 1 Chapter 2 Chapter 3 Introduction Overview of EMC File Management Appliance File Management High Availability (FMHA) File Management Appliance/VE (FMA/VE) File Management Appliances File Management with Celerra implementation File Mangement with NetApp implementation File Management tasks Using File Management File Management Appliance Hardware and Port Configurations Contents of the appliance File Management Appliance types File Management High Availability appliance types File Management Appliance details File Management High Availability appliance details Appliance diagrams Port details for FMA-7, FMHA-7, FMA-6, FMHA-6, FMA-5, and FMHA Port detail for FMA Deploying File Management The File Management Appliance deployment process Appliance setup File Management High Availability Celerra primary storage NetApp primary storage Installing the virtual appliance Configuring the File Management Appliance Configuring the FMA network Configuring the hostname, domain, and DNS server Graphical user interface Command line interface Using the FMA with the Celerra Data Mover as a source Adding a Celerra to the File Management configuration Configuring Celerra to EMC Centera or Atmos archiving on the FMA.. 47 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide 3

4 Configure name resolution Prerequisites for using Celerra as an archiving source Prerequisite on the Celerra Control Station Using the FMA with the NetApp filer as a source Prerequisites for using NetApp as an archiving source vfiler configuration Configuring NetApp archiving on the FMA Adding a NetApp filer to the File Management configuration Adding a Windows server to the FMA configuration Configuring a NAS-based repository Using FMA with EMC Centera Using the FMA with an Atmos server Using the FMA with a Data Domain server Backing up the configuration Creating a backup dump Restoring a backup dump Maintaining the database Performing a CD clean install Software upgrades Before upgrading FMA to version 7.3 or later CD full upgrade UPG upgrade Migrating from FMA to FMA/VE Shutting down and restarting the appliance Chapter 4 File Management System Settings Security hardening Single security database Disable root logins Strengthen passwords Age passwords Configuring the GUI access method STIG hardening Enabling STIG hardening Disabling STIG hardening LDAP client configuration Global LDAP settings LDAP authentication Configuring basic LDAP settings Configuring advanced LDAP settings RADIUS and TACACS Certificate management Appliance mail delivery settings Log settings Configuring log rotation Configuring SCP of rotated log files Alerts Configuring alerts Configuring SNMP alerts Enabling SNMP polling System command accounting Tracking user command history Tracking user login history Tracking daemon command history EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

5 Windows domain user Creating a Windows domain user Adding an admin user to the local administrator group Configuring Windows 2008 for NTLM Appendix A Network Topology Scenarios Advanced network topologies Configuring the FMA with bonding Configuring the FMA with two subnets Configuring the FMA with more than two subnets VLAN tagging modes for the FMA/VE ESX Server virtual switch tagging ESX Server virtual guest tagging Glossary Index EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide 5

6 6 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

7 Figures Title Page 1 Celerra implementation NetApp FPolicy implementation Archived report example Rear view of Dell R Front view of Dell R710 with bezel removed Rear view of Dell Front view of Dell 2950 with bezel removed Rear view of HP ProLiant Front view of HP ProLiant Front view of Dell R710 for High Availability with bezel removed Front view of Dell 2950 for High Availability with bezel removed FMA-7 and FMHA-7 port detail FMA-6, FMHA-6, and FMHA-5 port detail FMA-4 port detail File Management process Example of Celerra property settings in FMA version EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide 7

8 Figures 8 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

9 Tables Title Page 1 FMA that is based on Dell R FMA that is based on Dell FMA that is based on HP ProLiant FMHA appliance that is based on Dell R FMHA appliance that is based on Dell VMware ESX Server interoperability with FMA/VE Supported SNMP traps File Management alerts EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide 9

10 Tables 10 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

11 Preface As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions 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 document, please contact your EMC representative. Audience Related documentation This document is part of the EMC File Management Appliance documentation set. The documentation is intended for use by: Storage management administrators who are new to the EMC File Management Appliance. Existing customers who are new to version Related documents include: EMC File Management Appliance online help Provides detailed reference information on specific product features and functions. EMC File Managment Appliance Release Notes Provides an overview of new features and lists any limitations. EMC File Management man pages Provide detailed command-line help, as well as overview information. A good starting point is: man rffm. PDFs of all man pages are available from: /opt/rainfinity/filemanagement/doc Preface 11

12 Preface Conventions used in this document EMC uses the following conventions for special notices. Note: A note presents information that is important, but not hazard-related.! CAUTION A caution contains information essential to avoid data loss or damage to the system or equipment.! 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 Courier bold Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text 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 12 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

13 Preface Where to get help Your comments 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 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: techpubcomments@emc.com 13

14 Preface 14 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

15 1 Introduction This chapter includes the following sections: Overview of EMC File Management Appliance File Management Appliances File Management tasks Using File Management Introduction 15

16 Introduction Overview of EMC File Management Appliance The EMC File Management Appliance (FMA) is data archival technology that optimizes primary NAS storage by automatically moving inactive files based on policies to less expensive secondary storage. Files that are moved appear as if they are on primary storage. File archiving dramatically improves storage efficiency, and backup and restore time, while supporting additional business requirements such as compliance and retention. As an example, an FMA may be configured to locate all NAS data that has not been accessed in one year, and archive that data to secondary storage. For each file it archives, the FMA will leave behind a small space-saving stub file that points to the real data on the secondary storage device. When a user tries to access the data in its original location on the primary NAS, the user will be transparently provided with the actual data that the stub points to, from secondary storage. If multi-tier archiving is used, the FMA may be configured to move archived files from a secondary storage device tier to a tertiary storage device tier. This can be particularly useful in cases where the secondary storage device represents a tier that is smaller, faster, and more expensive to maintain than a larger, slower, and cheaper storage used in the tertiary tier. Once the files are moved, the space-saving stub file on the primary NAS tier would be updated to point to the data s new location on the tertiary storage tier. File Management High Availability (FMHA) The File Management High Availability (FMHA) appliance is a dedicated machine that runs the NetApp and EMC Celerra callback agents and provides high availability for stub file recalls, in case callback agents on the primary FMA are not available. This ensures complete transparency and nondisruptive service for clients. Note: The FMHA dedicated appliance has installation instructions that differ slightly from the FMA. File Management Appliance/VE (FMA/VE) The File Management Appliance/VE (FMA/VE) is a VMware virtual appliance installed on a VMware ESX/ESXi Server. FMA/VE is provided in an industry-standard virtual appliance distribution that consists of an Open Virtualization Format (OVF) and Virtual Machine Disk (VMDK) file. 16 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

17 Introduction File Management Appliances The EMC File Management Appliance includes two types of physical appliances and one type of virtual appliance. The capabilities and features available on the appliances differ. One or more of each type may be deployed within a customer environment to create a complete solution. File Management Appliance (FMA) Is the foundation of every file archiving deployment. It provides a full range of features including the ability to: archive and recall data perform policy simulations perform orphan file management perform stub file recovery It features a robust reporting interface that provides valuable insight into the efficacy of archiving policies. An FMA is delivered preloaded with software. File Management High Availability (FMHA) Appliance Complements an existing FMA by adding high-availability and load-balancing capabilities when recalling archived data to primary storage. FMHA cannot be used for any purpose other than recall. For example, it does not perform archiving or orphan file management, nor does it have a graphical user interface. An FMHA appliance is delivered preloaded with FMHA software. When FMHA appliances are deployed alongside an FMA, the underlying APIs of Celerra and NetApp file servers are leveraged to create a highly available and load-balanced environment for data recall. The Celerra and NetApp implementations differ as shown in Figure 1 on page 18 and Figure 2 on page 19. File Management Appliance/VE (FMA/VE) Runs on a virtual appliance. Virtual appliances are prebuilt software solutions, comprised of one or more virtual machines that are packaged, updated, maintained, and managed as a unit. Unlike a traditional hardware appliance, these software appliances allow customers to acquire, deploy, and manage preintegrated solution stacks more quickly and easily. VMware High Availability (HA) provides high availability for FMA/VE across a virtualized environment. With the failover protection against hardware and operating system failures that VMware HA delivers, FMA/VE can offer a disaster recovery solution. Depending on the environment, VMware HA features require: Virtual Center 2.5 for ESX 3.5 vcenter Server 4.0 for ESX 4.0 Information on configuring the VMware HA is provided in the VMware documentation. File Management Appliances 17

18 PowerEdge 2950 PowerEdge 2950 Introduction File Management with Celerra implementation Figure 1 on page 18 shows the recall architecture of a Celerra implementation. 4 1 CIFS R/W CIFS R/W NFS R/W HTTP R/W FTP R/W SMB over NetBIOS (TCP 139) SMB over TCP (TCP 445) NFS (RPC) HTTP (TCP 80) FTP (TCP 21) DHSM Celerra File System /etc/hosts 3 FileMover API 2 DNS EMC FMA NFS CIFS EMC FMHA Platform API NFS Repository CIFS Repository Centera or Atmos CNS Figure 1 Celerra implementation Circled numbers correspond to the following steps that illustrate the archive and recall process in the Celerra implementation: 1. Clients send read/write operations for files that have been archived. These operations are intercepted by the DHSM layer on the Celerra prior to being serviced from the filesystem. 2. If the file has been archived to EMC Centera or EMC Atmos storage, the Celerra blade resolves the fully qualified domain name (FQDN) to one of the following: In an FMA environment, it resolves the FQDN to the IP address of the FMA or FMHA appliance. In an FMA/VE environment, it resolves the FQDN to the IP address of the FMA/VE. 18 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

19 PowerEdge 2950 PowerEdge 2950 Introduction The blade then uses HTTP to read the archived data from the appliance, which in turn reads it from EMC Centera or Atmos by using the platform API. If an appliance does not respond to the HTTP read requests, the Celerra blade uses an alternate IP address of another appliance configured in DNS. Every callback server (FMA, FMHA, or FMA/VE) has its IP address associated with a single hostname in DNS. The FQDN uses that hostname, which may have multiple IP addresses associated with it. 3. If the file has been archived to an NFS or CIFS repository, the blade opens a connection to the repository and reads back the data. 4. The blade responds to the client operation as usual if the recall was successful, or the client receives an "access denied" message if the recall fails. Note: When Celerra data has been archived to a Celerra, NetApp, or Microsoft Windows repository, the FMA is not involved at all in the recall process. In such an environment, the FMHA appliance is not necessary. File Management with NetApp implementation Figure 2 on page 19 shows the recall architecture of NetApp FPolicy implementation. 4 1 CIFS Recall (Writes) SMB over NetBIOS CIFS R/W CIFS R/W NFS R/W HTTP R/W FTP R/W NFS Recall (Writes) SMB over NetBIOS (TCP 139) SMB over TCP (TCP 445) NFS (RPC) HTTP (TCP 80) FTP (TCP 21) FPolicy Primary Secondary 2 WAFL FPolicy API FPolicy API EMC FMA EMC FMHA 3 NFS CIFS/SMB over NetBIOS Platform API NFS Repository CIFS Repository Centera or Atmos CNS Figure 2 NetApp FPolicy implementation File Management Appliances 19

20 Introduction Circled numbers correspond to the following steps that illustrate the archive and recall process in the NetApp FPolicy implementation: 1. Clients send read/write operations for files that have been archived. These operations are intercepted by the FPolicy layer on the NetApp prior to being serviced from the Write Anywhere File Layout (WAFL) filesystem. 2. The NetApp is configured with the following groups: A primary group of callback servers, such as an FMA and possibly one or more FMHA appliances. A secondary group, such as one or more FMHA appliances. The NetApp will send FPolicy callbacks to servers registered in the primary group in round-robin fashion. If a server does not reply to the callback, it is removed from its group. If there are no servers in the primary group, the callbacks are distributed in a round-robin fashion among the servers in the secondary group. For FMA/VE, the primary group of callback servers consists of one or more virtual machines that are clustered using VMware. 3. The appliance connects to the filer by using CIFS to read the contents of the stub file. The stub file points to where the file data is stored. The appliance then connects to the NFS repository, CIFS repository, or EMC Centera cluster where the data was archived. It then reads the data by using the native protocol and the file data is written back to the NetApp. 4. The filer responds to the client operation as usual if the recall was successful, or with an "access denied" message if the recall failed. Note: It is a requirement that the software versions of all the appliances match. For example, do not deploy a configuration with an FMA that is running version 7.3b2 and an FMHA that is running version 7.3b3. While the software does not perform any explicit checks to ensure the versions are compatible, the running of different software versions has not been tested and may result in unexpected behavior. File Management tasks File Management may be used to run several different tasks: Archiving Deleting Auxiliary tasks, such as stub scanning, backup, and NAS migration For archiving and deleting, the software leverages a policy engine to define which files should be archived or deleted. Users can combine and evaluate multiple rules together in a single policy. Several rule types for archiving and deleting are included. Before running the archive, delete, or NAS migration task, the running of a simulation allows administrators to review real-time results without executing the task. The results will return: Aggregated summary of total files matched Total bytes potentially archived Optional list of files stored on the disk. 20 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

21 Introduction Run a simulation to gain insight into the efficiency of a task before running the task. This practice is notably important for the delete tasks, since these tasks remove data. A report displays results of the task. Figure 3 on page 21 is an example of an archived report. Figure 3 Archived report example Archive tasks may be one of three types: Archive (with policy) Archives all regular (non-stub) files. Files are selected for archiving based on the archive policy. Multi-tier (with policy) For this archiving task, all regular and stub files are evaluated with the multi-tier policy. If a regular file matches the policy, it is archived. If a stub file matches the policy, archived data is moved to a different repository and the stub is updated to point to the new location. Multi-tier stub (with policy) For this archiving task, only stub files are evaluated with the multi-tier stub policy. If a stub file matches the policy, archived data is moved to a different repository and the stub is updated to point to the new location. Otherwise, the archived data remains in the current repository. Delete tasks may be one of two types: Delete orphan with policy Deletes orphans on secondary storage that match the delete orphans policy. Delete stub with policy The delete stub task deletes stubs that match the delete stubs policy. Stubs on primary storage and files on the second tier that are no longer under retention or that were defined without any retention period are automatically deleted. File Management tasks 21

22 Introduction Auxiliary tasks are: Scan stubs When a file is archived, a stub file remains on the source and an entry is added to the FMA database, and maps the name and location of the archived file to its stub. The stub scanning task scans for stubs in the FMA database that are no longer present on the source. When a stub has not been detected for 30 or more days, the archived file is designated as an orphan. Backup The backup task performs periodic backups of the FMA configuration and database. Schedule backup tasks as part of a regular maintenance program. NAS Migration NAS migration moves all archived data from one NAS repository to a new repository, which may be a NAS repository, an EMC Centera, or an Atmos. All stub files that point to this data will be updated to point to the new location. The File Management software also has the capability to recover stub files accidentally deleted by client systems. It can even recover prior versions of files archived to any secondary storage destination. Using File Management Once the appliance has been deployed on the network, the adminstrator can manage data through the File Management graphical user interface (GUI) or command line interface (CLI). Graphical user interface on page 44 explains how to invoke the GUI. Online help documents all GUI pages. Technical system details that are not related to the GUI, but are required to configure the FMA, are provided in the following chapters and appendixes: Chapter 3, Deploying File Management Chapter 4, File Management System Settings Appendix A, Network Topology Scenarios If the FMA is not installed on the network, administrators should refer to the sections in this book to configure the FMA properly before its use. 22 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

23 2 File Management Appliance Hardware and Port Configurations This chapter contains the following sections: Contents of the appliance File Management Appliance details File Management High Availability appliance details Appliance diagrams Port details for FMA-7, FMHA-7, FMA-6, FMHA-6, FMA-5, and FMHA Port detail for FMA File Management Appliance Hardware and Port Configurations 23

24 File Management Appliance Hardware and Port Contents of the appliance FMA or FMHA ships with robust, fault-tolerant hardware consistent with the mission-critical application for which it is used. The following items are included in the appliance package: A 2U 19-inch rackmountable File Management Appliance. Two universal rails for mounting the appliance on a 19-inch rack. Two sets of power cords. Copper patch cables for the number of ports on your appliance. Media kit with documentation CD and the software recovery CD. One serial cable. Note: The following are items are not included: VGA monitor, keyboard, and mouse for a system console. File Management Appliance types Dell R710 Model FMA-7 ships with two enabled on-board gigabit Ethernet copper 10/100/1000TX ports. Figure 12 on page 33 shows the port details. Dell 2950 Model FMA-6 and FMA-5 ships with two on-board gigabit Ethernet copper 10/100/1000TX ports. Figure 13 on page 33 shows the port details. HP ProLiant Model FMA-4 ships with two on-board gigabit Ethernet copper 10/100/1000TX ports and four copper ports. Figure 14 on page 34 shows the port details. File Management High Availability appliance types Dell R710 Model FMHA-7 ships with two enabled on-board gigabit Ethernet copper 10/100/1000TX ports. Figure 12 on page 33 shows the port details. Dell 2950 Model FMHA-6 and FMHA-5 ships with two on-board gigabit Ethernet copper 10/100/1000TX ports. Figure 13 on page 33 shows the port details. 24 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

25 File Management Appliance Hardware and Port File Management Appliance details Table 1 on page 25 lists the configurations for the FMA that is based on the Dell R710 hardware. Table 1 FMA that is based on Dell R710 Component Chassis Size Power CPUs Disks RAID controller CD-ROM Memory Network interfaces VGA Keyboard connector Mouse connector Serial port FMA-7 The appliance is based on Dell R710 11G hardware. 2U form factor Dual 570 watts Dual, 2.0 GHz, E5540 4C/4T 80W 4MB Cache Nehalem-EP Four 1 TB, SATA, 3.5-inch, 7.2 K RPM hard drives in a RAID-1 configuration with two hot spares. Items (b) through (e) in Figure 5 on page 30. SAS6/IR Read-only DVD that can read CD or DVD material for system upgrades. Item (a) in Figure 5 on page MHz, (2 x 2 GB), dual-ranked RDIMMs Two on-board gigabit 10/100/1000TX Ethernet copper ports with RJ45 connectors. Item (e) in Figure 4 on page 30. Standard VGA video connector for a system console. Item (a) in Figure 4 on page 30. Standard USB keyboard connector for a system console. Item (d) in Figure 4 on page 30. Standard USB mouse connector for a system console. Item (c) in Figure 4 on page 30. Standard DB9 serial port for a serial-terminal system. Item (b) in Figure 4 on page 30. Table 2 on page 25 lists the configurations for the FMA that is based on the Dell 2950 hardware. Table 2 FMA that is based on Dell 2950 (page 1 of 2) Component FMA-6 FMA-5 Chassis The appliance is based on Dell 2950 hardware. The appliance is based on Dell 2950 hardware. Size Power CPUs 2U rackmount form factor with universal rails. Dimensions: 8.6 cm (h), 44.5 cm (w), 66.1 cm (d). Weight: 34 kg. Dual redundant 750 watt hot-plug, power supplies. Total consumption: 5A at 120 V or 2.5 A at 240 V. Dual Intel Xeon 3.00 GHz Quad Core processors with 1333 MHz front-side bus. 2U rackmount form factor with universal rails. Dimensions: 8.6 cm (h), 44.5 cm (w), 66.1 cm (d). Weight: 34 kg. Dual redundant 750 watt hot-plug, power supplies. Total consumption: 5A at 120 V or 2.5 A at 240 V. Dual Intel Xeon 3.00 GHz Dual Core processors with 1333 MHz front-side bus. File Management Appliance details 25

26 File Management Appliance Hardware and Port Table 2 FMA that is based on Dell 2950 (page 2 of 2) Component FMA-6 FMA-5 Disks RAID controller Four 250 GB, SATA, 3.5-inch, 7.2K RPM hard drives in a RAID-5 configuration. Items (b) through (e) in Figure 7 on page 31. PERC 6/I integrated controller card with 256 MB of battery-backed write cache. The storage controller buffers all writes to disk so that in the event of a critical full-system failure. Important state information is saved even during abrupt disk or power failure. Six 160 GB, SATA, 3.5-inch, 7.2K RPM hard drives in a RAID-1 configuration. Items (b) through (g) in Figure 7 on page 31. PERC 5/I integrated controller card with 256 MB of battery-backed write cache. The storage controller buffers all writes to disk so that in the event of a critical full-system failure. Important state information is saved even during abrupt disk or power failure. Remote management Dell DRAC Card. Dell DRAC Card. CD-ROM Memory Network interfaces VGA Keyboard connector Mouse connector Serial port 24x IDE CD-ROM/DVD-ROM drive for system upgrades. Item (a) in Figure 7 on page MHz, (4 x 1 GB), single-ranked DIMMs Two on-board gigabit 10/100/1000TX Ethernet copper ports with RJ45 connectors. Item (e) in Figure 6 on page 30. Standard VGA video connector for a system console. Item (a) in Figure 6 on page 30. Standard USB keyboard connector for a system console. Item (d) in Figure 6 on page 30. Standard USB mouse connector for a system console. Item (c) in Figure 6 on page 30. Standard DB9 serial port for a serial-terminal system. Item (b) in Figure 6 on page x IDE CD-ROM drive for system upgrades. Item (a) in Figure 7 on page MHz, (8 x 512 MB), single-ranked DIMMs Two on-board gigabit 10/100/1000TX Ethernet copper ports with RJ45 connectors. Item (e) in Figure 6 on page 30. Standard VGA video connector for a system console. Item (a) in Figure 6 on page 30. Standard USB keyboard connector for a system console. Item (d) in Figure 6 on page 30. Standard USB mouse connector for a system console. Item (c) in Figure 6 on page 30. Standard DB9 serial port for a serial-terminal system. Item (b) in Figure 6 on page 30. Table 3 on page 26 lists the configuration for the FMA that is based on the HP ProLiant hardware. Table 3 FMA that is based on HP ProLiant (page 1 of 2) Component Chassis Size Power CPUs Disks FMA-4 The appliance is based on the HP ProLiant DL380 G4 hardware. 2U rackmount form factor with universal rails. Dimensions: 8.6 cm (h), 44.5 cm (w), 66.1 cm (d). Weight: kg. Dual redundant 575 watt, hot-plug, power supplies. Total consumption: 5A at 120V or 2.5A at 240 V. Item (a) in Figure 8 on page 31. Dual Intel Xeon processors 3.6 GHz with 800 MHz front-side bus. Six GB, SCSI, 3.5 inch 10K RPM drives in a RAID 5 configuration. Items (b) and (c) in Figure 9 on page EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

27 File Management Appliance Hardware and Port Table 3 FMA that is based on HP ProLiant (page 2 of 2) Component RAID controller Remote management FMA-4 SmartArray 6i storage controller. The storage controller buffers all writes to disk so that in the event of a critical full-system failure. Important state information is saved even during abrupt disk or power failure. Not applicable. CD-ROM CD-ROM drive for system upgrades. Item (a) in Figure 9 on page 31. Memory Network interfaces VGA 400 MHz, (4 x 1 GB), single-ranked DIMMs Two on-board gigabit 10/100/1000TX Ethernet copper ports with RJ45 connectors. Item (e) in Figure 8 on page 31. In addition, connectivity to the network is made through four copper ports. Item (f) in Figure 8 on page 31. Standard VGA video connector for a system console. Item (g) in Figure 8 on page 31. Keyboard connector Standard PS/2 keyboard for a system console. Item (d) in Figure 8 on page 31. Mouse connector Serial port Standard PS/2 keyboard connector for a system console. Item (c) in Figure 8 on page 31. Standard DB9 serial port for a serial-terminal system. Item (b) in Figure 8 on page 31. File Management Appliance details 27

28 File Management Appliance Hardware and Port File Management High Availability appliance details Table 4 on page 28 lists the hardware configurations for the File Management High Availability appliance that is based on the Dell R710 hardware. Table 4 FMHA appliance that is based on Dell R710 Component Chassis Size Power CPUs Disks RAID controller CD-ROM Memory Network interfaces VGA Keyboard connector Mouse connector Serial port FMHA-7 The appliance is based on Dell R710 11G hardware. 2U form factor Dual 570 watts Single, 2.0 GHz, E5540 4C/4T 80 W 4 MB Cache Nehalem-EP Two 1 TB, SATA, 3.5-inch, 7.2K RPM hard drives in a RAID-1 (SW) configuration. Items (b) and (c) in Figure 10 on page 32. None. Read-only DVD that can read CD or DVD material for system upgrades. Item (a) in Figure 10 on page MHz, (2 x 2 GB), dual-ranked RDIMMs Two on-board gigabit 10/100/1000TX Ethernet copper ports with RJ45 connectors. Item (e) in Figure 4 on page 30. Standard VGA video connector for a system console. Item (a) in Figure 4 on page 30. Standard USB keyboard connector for a system console. Item (d) in Figure 4 on page 30. Standard USB mouse connector for a system console. Item (c) in Figure 4 on page 30. Standard DB9 serial port for a serial-terminal system. Item (b) in Figure 4 on page 30. Table 5 on page 28 lists the hardware configurations for the File Management High Availability appliance that is based on the Dell 2950 hardware. Table 5 FMHA appliance that is based on Dell 2950 (page 1 of 2) Component FMHA-6 FMHA-5 Chassis The appliance is based on Dell 2950 hardware. It is a 2U rackmount form factor with universal rails. The appliance is based on Dell 2950 hardware. It is a 2U rackmount form factor with universal rails. Size Power CPU 2U rackmount form factor with universal rails. Dimensions: 8.6 cm (h), 44.5 cm (w), 66.1 cm (d). Weight: 34 kg. Dual redundant 750 watt hot-plug, power supplies. Single Intel Xeon 2.33 GHz Quad Core processor with 1333 MHz front-side bus. 2U rackmount form factor with universal rails. Dimensions: 8.6 cm (h), 44.5 cm (w), 66.1 cm (d). Weight: 34 kg. Dual redundant 750 watt hot-plug, power supplies. Single Intel Xeon 1.86 GHz Dual Core processor with 1066 MHz front-side bus. 28 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

29 File Management Appliance Hardware and Port Table 5 FMHA appliance that is based on Dell 2950 (page 2 of 2) Component FMHA-6 FMHA-5 Disks RAID Controller CD-ROM Memory Network Interfaces VGA Keyboard Connector Mouse Connector Serial port Two 250 GB, SATA, 3.5-inch, 7.2K RPM hard drives in a RAID 1 configuration. Items (b) and (c) in Figure 11 on page 32. PERC 6/I integrated controller card with 256 MB of battery-backed write cache. The storage controller buffers all writes to disk so that in the event of a critical full-system failure. Important state information is saved even during abrupt disk or power failure. 24x IDE CD-ROM/DVD-ROM drive for system upgrades. Item (a) in Figure 11 on page GB, 533 MHz (4x1 GB), dual-ranked DIMMs. Two on-board gigabit 10/100/1000TX Ethernet copper ports with RJ45 connectors. Item (e) in Figure 6 on page 30. Standard VGA video connector for a system console. Item (a) in Figure 6 on page 30. Standard USB keyboard connector for a system console. Item (d) in Figure 6 on page 30. Standard USB mouse connector for a system console. Item (c) in Figure 6 on page 30. Standard DB9 serial port for a serial-terminal system. Item (b) in Figure 6 on page 30. Two 160 GB, SATA, 3.5-inch, 7.2K RPM hard drives in a RAID 1 configuration. Items (b) and (c) in Figure 11 on page 32. PERC 5/I integrated controller card with 256 MB of battery-backed write cache. The storage controller buffers all writes to disk so that in the event of a critical full-system failure. Important state information is saved even during abrupt disk or power failure. 24x IDE CD-ROM drive for system upgrades. Item (a) in Figure 11 on page GB, 533 MHz (4x1 GB), dual-ranked DIMMs. Two on-board gigabit 10/100/1000TX Ethernet copper ports with RJ45 connectors. Item (e) in Figure 6 on page 30. Standard VGA video connector for a system console. Item (a) in Figure 6 on page 30. Standard USB keyboard connector for a system console. Item (d) in Figure 6 on page 30. Standard USB mouse connector for a system console. Item (c) in Figure 6 on page 30. Standard DB9 serial port for a serial-terminal system. Item (b) in Figure 6 on page 30. File Management High Availability appliance details 29

30 File Management Appliance Hardware and Port Appliance diagrams These photographs illustrate configurations of the FMA and FMHA based on the Dell and HP hardware. Figure 4 Rear view of Dell R710 Figure 5 Front view of Dell R710 with bezel removed Figure 6 Rear view of Dell EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

31 File Management Appliance Hardware and Port Figure 7 Front view of Dell 2950 with bezel removed Figure 8 Rear view of HP ProLiant Figure 9 Front view of HP ProLiant Appliance diagrams 31

32 File Management Appliance Hardware and Port Figure 10 Front view of Dell R710 for High Availability with bezel removed Figure 11 Front view of Dell 2950 for High Availability with bezel removed 32 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

33 File Management Appliance Hardware and Port Port details for FMA-7, FMHA-7, FMA-6, FMHA-6, FMA-5, and FMHA-5 Models FMA-7 and FMHA-7 ship with two on-board ports enabled. Figure 12 on page 33 is a rear view of the appliance with the ports labeled. eth0 eth1 Disabled Disabled CNS Figure 12 FMA-7 and FMHA-7 port detail Models FMA-6, FMHA-6, and FMHA-5 ship with two on-board ports. Figure 13 on page 33 is a rear view of the appliance with the ports labeled. eth1 eth0 CNS Figure 13 FMA-6, FMHA-6, and FMHA-5 port detail Port details for FMA-7, FMHA-7, FMA-6, FMHA-6, FMA-5, and FMHA-5 33

34 File Management Appliance Hardware and Port Port detail for FMA-4 Model FM-4 ships with six copper ports. Figure 14 on page 34 is a rear view of the appliance with the ports labeled. To help identify the ports in the schematic, note that: eth0, eth1, eth2, and eth3 are on slot 1. eth4 and eth5 are the onboard NICs. eth0 eth1 eth2 eth3 eth5 eth4 CNS Figure 14 FMA-4 port detail 34 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

35 3 Deploying File Management This chapter contains the following sections: The File Management Appliance deployment process Appliance setup File Management High Availability Installing the virtual appliance Configuring the File Management Appliance Using the FMA with the Celerra Data Mover as a source Using the FMA with the NetApp filer as a source Adding a Windows server to the FMA configuration Configuring a NAS-based repository Using FMA with EMC Centera Using the FMA with an Atmos server Using the FMA with a Data Domain server Backing up the configuration Maintaining the database Performing a CD clean install Software upgrades Migrating from FMA to FMA/VE Shutting down and restarting the appliance Deploying File Management 35

36 Deploying File Management The File Management Appliance deployment process Figure 15 on page 36 illustrates the EMC File Management Appliance deployment process. File Management Setup 1. Configure FMA networking 2. For NetApp archiving and Celerra-EMC Centera or Celerra-Atmos archiving, initialize recall services Celerra to EMC Centera or Atmos Configuration 1. Configure FileMover API 2. Configure name resolution for recall 3. Configure DHSM Celerra to NAS Configuration 1. Configure FIleMover API 2. Configure DHSM NetApp Configuration 1. Configure NetApp options 2. Configure ONTAPI 3. Configure FPolicy (vfilers only) File Management Configuration 1. Configure primary NAS 2a. Configure NAS repositories 2b. Configure non-nas repositories Define Policies 1. Create file matching expressions and archive destinations 2. Specify policy type, retention, delayed stubbing, stub retention (as applicable) Create Task 1. Create an archive, delete, or auxiliary task 2. Select source (as applicable) Run Simulation Task (Optional) 1. Select Run Simulation Now 2. Collect real-time results in FMA 3. Review policy efficacy against real-time results Run Policy Task 1. Determine optimal task scheduling 2. Select archive conditions or start times (as applicable) 3. Monitor archiving activity for errors CNS Figure 15 File Management process The top of the flowchart describes deploying the FMA in various environments. Appliance setup on page 37 outlines this process. In a Celerra to NAS configuration, the NAS repositories may be a Celerra Data Mover, NetApp filer, Windows server, or Data Domain server. Steps in the five boxes at the bottom of the flowchart are performed by using the FMA GUI. Online help describes these steps in more detail. 36 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

37 Deploying File Management Appliance setup The appliance arrives with the software installed. Before it may be used to perform tasks, the appliance and the software must be properly configured: If an FMA is being deployed, port details that are used to connect the appliance to the network are provided in Chapter 2, File Management Appliance Hardware and Port Configurations. The File Management software is preinstalled on every new appliance. If the software must be reinstalled without preserving any previous information or data, follow the instructions provided in Performing a CD clean install on page 70. Software upgrades on page 71 provides instructions to perform a CD full upgrade or UPG upgrade. If a File Management High Availability (FMHA) appliance is being deployed, File Management High Availability on page 38 describes configuration considerations. If an FMA/VE is being deployed, follow the instructions in Installing the virtual appliance on page 39. To install the appliance on the network, follow instructions provided in Configuring the File Management Appliance on page 42. If the system requires security hardening or any other special configuration, Chapter 4, File Management System Settings, provides information for all system settings. Then proceed to configure the appliance for your environment as described in: Using the FMA with the Celerra Data Mover as a source on page 45 Using the FMA with the NetApp filer as a source on page 55 Adding a Windows server to the FMA configuration on page 58 Configuring a NAS-based repository on page 60 Using FMA with EMC Centera on page 61 Using the FMA with a Data Domain server on page 63 Appliance setup 37

38 Deploying File Management File Management High Availability File Management delivers a solution for a redundancy, which ensures that clients do not experience data unavailability due to failure of an appliance. When using File Management High Availability (FMHA) for recall, NetApp and Celerra callback services are configured on the FMHA appliance. These services handle file recall from secondary storage such as EMC Centera, Atmos, Microsoft Windows, or Data Domain servers to primary storage, such as NetApp or Celerra. This configuration eliminates a single point of failure for the primary callback service and ensures transparent client access to archived data. To fulfill requirements for high availability, recall operations can be handled by a group of File Management or FMHA appliances. High availability does not apply to the FMA/VE. Celerra primary storage For Celerra primary storage archived to an EMC Centera or Atmos, Data Movers resolve an HTTP fully qualified domain name (FQDN) to the IP addresses of File Management and FMHA appliances. If a Data Mover identifies multiple IP addresses mapped to the same FQDN, it will select the first address it finds and attempt to send the recall request. If the IP address is not responsive, the Data Mover will select subsequent addresses for the FQDN and attempt to send the recall requests to those addresses. All recall requests generated by a Data Mover when resolving the FQDN are sent to a single appliance even if multiple IP addresses are found. Each Data Mover can be configured to send recall requests to a preferred appliance which provides coarse-grained load balancing of recall requests at the Data Mover level. Using the FMA with the Celerra Data Mover as a source on page 45 provides details on configuring Celerra Data Movers. Run ccdsetup or acdsetup on all FMHA appliances that will process recall requests from the Celerra Data Movers. These scripts link multiple appliances to process recall requests from a common set of Celerra Data Movers. Configuring Celerra to EMC Centera or Atmos archiving on the FMA on page 47 provides details on ccdsetup and acdsetup. No additional appliances are involved in recall when the FMA archives data from Celerra primary storage to NAS repositories serving as secondary storage. The Data Movers use the CIFS and NFS protocols to recall data directly from secondary storage. NetApp primary storage NetApp filers allow FPolicy clients (such as FMA or FMHA) to register for callbacks in response to user access to files with specific attributes. When using File Management, a callback will be generated when a read/write operation occurs to a file with the CIFS offline bit set. For NetApp primary storage, multiple appliances can register in the primary or secondary FPolicy groups of the filer. In the event that a registered server becomes unresponsive, it is removed from its group. Recall requests will be sent by the filer in a round-robin fashion to the IP addresses registered in the primary group. If there are no responsive IP addresses in the primary group, then the requests are load-balanced across the servers in the secondary group. 38 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

39 Deploying File Management Run fpsetup on the FMHA appliances that will process recall requests. Use this script to link together multiple appliances that will process recall requests that are sent from a common set of NetApp Filers. Later, when configuring NetApp filers, you will have the option to select specific FM and FMHA appliances that will register in the primary and secondary groups. Configuring NetApp archiving on the FMA on page 56 provides details on fpsetup. Appliances are always involved in recall when the FMA archives data from NetApp primary storage to any secondary storage location. NetApp filers do not recall data directly from Celerra, EMC Centera, or NetApp storage. Note: A single FMHA appliance can provide redundancy for multiple FMAs. A single FMA can have multiple FMHA appliances registered to provide redundancy. Do not use an FMA to provide redundancy for another FMA. Installing the virtual appliance FMA/VE is installed on the VMware server. Table 6 on page 39 shows the interoperability. Table 6 VMware ESX Server interoperability with FMA/VE VMware ESX Server ESX 3.5 Update 3 ESXi 3.5 Update 3 ESX 4.0 ESXi 4.0 Comments Four virtual CPUs, 4 GB of RAM, 512 GB of disk space, 2 gigabit virtual interfaces are reserved. Hardware and firmware requirements for 64-bit guest operating systems are listed at the VMware web site. The following example shows the steps to install the FMA/VE virtual appliance on an ESX 3.5 Server host: 1. Unzip the file to create the directory for your virtual appliance. The Zip file contains the.ovf file and.vmdk file. 2. Open the Virtual Infrastructure (VI) Client. Installing the virtual appliance 39

40 Deploying File Management a. To find the appliance with the most free space, consider %CPU and %Memory. b. Select the line for the ESX Server: A summary of the CPU, memory, and data store capacities appears. This ESX Server has enough CPU and memory available to install the FMA/VE. 3. Import the OVF file. Instructions differ depending upon VMware version. 40 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

41 Deploying File Management For ESXi 3.5 Server, from the VI Client, select File > Virtual Appliance > Import. For ESX 4.0 Server, from the VI Client, select File > Deploy OVF Template. 4. Using the Import from file selection, type the path to the OVF file or click Browse to locate the file. Installing the virtual appliance 41

42 Deploying File Management 5. After answering a few basic questions, the summary screen appears. Validate the information and click Finish. 6. The import may take 3 30 minutes depending on the network connection between the VI Client and the VMware ESX Server. Approximately 600 MB will initially be transferred across the network. If the FMA/VE will be configured for Celerra to EMC Centera archiving, use FileMover Settings as described in step 3 of Adding a Celerra to the File Management configuration on page 45 to configure the single set of credentials for recall. Then run ccdsetup.sh or acdsetup.sh as described in Configuring Celerra to EMC Centera or Atmos archiving on the FMA on page 47. Configuring the File Management Appliance Before proceeding with the setup, ensure that you have the following information for each appliance: IP address Subnet mask Hostname Default gateway IP DNS server IP (optional) 1. Set up the appliance: For an FMA or FMHA appliance, connect the keyboard, monitor, and mouse to the appliance. The serial cable provided with the FMA and a HyperTerminal on a PC or laptop may be used. Connect the power cord and power on the appliance. For an FMA/VE, power on the appliance. 2. Log in to the appliance by using the local keyboard and monitor. Type root as the login name. Type rain as the password. 42 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

43 Deploying File Management The Rainfinity setup tool appears. This tool performs basic setup tasks that are not available through the File Management GUI. 3. Select Change File Management Appliance Password, and change the password. 4. Select Configure Date and Time to set the time zone and date for the appliance. 5. Select Configure File Management Networking. The network configuration menu appears. Use the menu to change interface settings or set global settings such as hostname, domain, and DNS servers. Configuring the FMA network To configure the FMA network: 1. Select option 1 from the Network Configuration menu. The File Management Network Setup, Main Menu appears. On the list of available physical interfaces on the appliance, eth0 appears highlighted. To highlight a different interface, use the up arrow and down arrow keys. 2. With eth0 highlighted, press Enter. The configuration menu for the eth0 interface appears: Use the up arrow and down arrow keys to highlight the IP address field. Press Enter and type a new IP address value into the New Value column. Press Enter. Repeat the process to provide the subnet mask, gateway, and MTU settings. 3. When the configuration for this interface is complete, press the left arrow key to exit the eth0 interface configuration. 4. To save the interface configuration, select Yes and press Enter. Note that the changes are saved, but will not be implemented until the File Management Network Setup menu is exited. 5. Press the left arrow key to exit from the File Management Network Setup, Main Menu. When prompted, select Yes to save your changes. Configuring the hostname, domain, and DNS server Configure the hostname, domain, and DNS servers: 1. Select option 2 from the network configuration menu. The following menu appears: EMC Rainfinity Setup Tool (Configure Hostname, Domain and DNS Server(s)) Hostname = rs Domain = DNS Server = Do you want to change the configuration [Y/N]? 2. Type Y. Use the menu to configure the hostname, domain, and DNS servers. The new hostname, domain, and DNS server information is summarized after all the changes are entered, and you are given the ability to accept or make further changes to these settings. To keep the new settings and return to the network configuration menu, press Enter. Configuring the File Management Appliance 43

44 Deploying File Management 3. Verify that the network configuration has been saved and network connectivity can be established properly. Graphical user interface To access the graphical user interface from a web browser: 1. In the navigation field of the web browser, type the IP address of the appliance. 2. Type the username and password for the default account which are: Username: admin Password: rain Tabs appear as follows: Schedule Displays a list of scheduled tasks that are currently being processed and the status of each task. Archived Files Displays an archived file report. Also provides a search option to find archived files, recover stub files, and delete orphan files. Policies Provides options that apply to creating and managing policies, including: A list of policies, file matching expressions, and NAS destinations. Create new policy. Create new file matching expression. Create new NAS destination. Configuration Provides configuration of users, passwords, logging, primary servers, and secondary destination servers. Command line interface As an alternative to the GUI, you can use a command line interface to send commands to the File Management daemon. To log in to the CLI by using SSH, the default username and password are: Username: root Password: rain The most commonly used commands are: fmsupportdump Creates a dump of the appliance's current state for technical support. rffm Configures the appliance and issues all commands that the GUI interface supports. To see a list of all commands available, type rffm --help or to view the man page for more detailed help, type man rffm. fmbackup/fmrestore Backs up and restores the configuration as described in Backing up the configuration on page EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

45 Deploying File Management rssystat Displays statistics about the FMA. Man pages for the command line tools are stored in the software installation directory. To accesss the man pages, type man command_name as in, man rssystat. Using the FMA with the Celerra Data Mover as a source To use the FMA with a Celerra Data Mover, first perform configuration steps on the appliance, and then on the Celerra Control Station. Adding a Celerra to the File Management configuration 1. Click the File Servers link on the Configuration tab. The File Server List appears. Click New. 2. On the File Server Properties page that appears, select Celerra from the Type list box. 3. Click FileMover Settings. The FileMover Settings page appears. Using the FMA with the Celerra Data Mover as a source 45

46 Deploying File Management Type the username and password for FileMover API authentication and callback HTTP authentication. The system uses this username and password to create an HTTP connection by using XML API. This same username and password are used when creating the FileMover API user in step 2 of Prerequisite on the Celerra Control Station on page Specify the following for the Celerra FileMover: Basic File Server Information Type the Celerra name and select the DART version from the list. If the Data Mover will be involved in CIFS archiving, the NetBIOS name of the CIFS server must be used. Do not use the fully qualified domain name (FQDN) or IP address. Note: To identify the Celerra as a Virtual Data Mover, select the checkbox. Virtual Data Movers support only the CIFS protocol. IP Addresses Type the Celerra Data Mover IP address: When editing an existing server, click Update to retrieve the IP address from the DNS that is based on the server name. To specify an additional IP address, click Add. To delete an existing IP address, select an IP and click Delete. Control Station For DART 5.6, type the IP address of the Celerra Control Station. This allows File Management to automatically perform some preconfiguration steps for archiving. If this field is empty, the FMA takes no action. The preconfiguration steps must be performed manually. CIFS Specific Settings This is the Windows domain user to be used by the appliance. The domain user must be a member of the local administrator s group on the Celerra. Windows domain user on page 95 provides more information. Note: The CIFS credential is not required if the Celerra performs only NFS archiving. Celerra as Source This option configures File Management to archive data from the Celerra Data Mover. If more than one appliance is connected to the same Celerra Data Mover, configure only one appliance with this option. This option is required only if the Celerra is serving as a source for archiving. It is not required if the Celerra will be used only for NFS archiving.! CAUTION Multiple appliances may be configured to archive data from a single Celerra Data Mover, but more than one FMA or FMA/VE should never be used to archive data from a single filesystem. Celerra Callback Agent Settings This option is required if archiving to an EMC Centera. For the CCD DNS name, type the FQDN of the Celerra Callback DNS entry. Note that the FQDN is case-sensitive. Atmos Callback Agent Settings This option is required if archiving to an Atmos server. For the ACD DNS name, type the FQDN of the Atmos Callback DNS entry. Note that the FQDN is case-sensitive. 46 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

47 Deploying File Management Note: The DNS names for the Celerra Callback agent and Atmos Callback agent must be distinct. They cannot be the same. Directory Exclusion List These are the directories to exclude for all tasks. File Management ignores all system directories such as, etc, lost+found, and ckpt by default. 5. Click Commit to define the Celerra FileMover. Configuring Celerra to EMC Centera or Atmos archiving on the FMA To archive from a Celerra to an EMC Centera or Atmos, configure the Celerra Callback Service so that the FMA is in the recall path. Configure the Celerra Callback Service to recall from EMC Centera To configure recall from the EMC Centera: 1. From the console on the appliance which is the primary callback agent, log in as root. 2. Type! to escape to the command line and type: /opt/rainfinity/filemanagement/bin/ccdsetup.sh init_rffm 3. Type n when the following message appears: By default the Celerra Callback Daemon will connect to the File Management service on the local machine. Do you wish to configure another File Management Machine? (y/n) 4. If there is a secondary callback agent such as an FMHA appliance, log in on that agent as root, and repeat step 2 and step 3. In step 3, type y to provide the IP address and the root password of the primary callback agent. If an invalid IP address is provided, the CelerraCallbackDaemon.stdout file located in /var/log/rainfinity/filemanagement will fill with errors to indicate that there was no response from the primary agent. To correct the problem, repeat step 2 through step 4 of this procedure. Configure the Celerra Callback Service to recall from the Atmos To configure recall from the Atmos: 1. From the console on the appliance which is the primary callback agent, log in as root. 2. Type! to escape to the command line and type: /opt/rainfinity/filemanagement/bin/acdsetup.sh init_rffm 3. Type n when the following message appears: By default the Atmos Callback Daemon will connect to the File Management service on the local machine. Do you wish to configure another File Management Machine? (y/n) 4. If there is a secondary callback agent such as an FMHA appliance, log in on that agent as root, and repeat step 2 and step 3. In step 3, type y to provide the IP address and root password of the primary callback agent. If an invalid IP address is provided, the AtmosCallbackDaemon.stdout file located in /var/log/rainfinity/filemanagement will fill with errors to indicate that there was no response from the primary agent. To correct the problem, repeat step 2 through step 4 of this procedure. Using the FMA with the Celerra Data Mover as a source 47

48 Deploying File Management Configure name resolution When the Celerra Data Mover needs to establish a connection to the appliance to recall data from an EMC Centera or Atmos, it tries to resolve the FQDN from the HTTP DHSM connection in its local hosts file. If it cannot be resolved locally, the Data Mover will use DNS. To use local hostname resolution: a. Log in to the Celerra Control station as root and mount the Data Mover to edit the local hosts file with vi: mount server_2:/ /mnt/source cd /mnt/source/.etc vi hosts where server_2 is the name of your Celerra Data Mover. b. Edit the host file to add one line for each appliance, similar to the following example: <rainccd.domain> # CCD on FMHA <rainccd.domain> # CCD on FMA <rainccd.domain> # CCD on FMA/VE <rainacd.domain> # ACD on FMHA <rainacd.domain> # ACD on FMA <rainacd.domain> # ACD on FMA/VE where: rainccd.domain is the FQDN that will be used to create the HTTP DHSM connection described in Celerra Callback Agent Settings on page 46. rainacd.domain is the FQDN that will be used to create the HTTP DHSM connection described in Atmos Callback Agent Settings on page 46. c. Save the file and confirm that the Celerra Control Station is not mounted to the Data Mover: cd ~ umount /mnt/source Note: A bug in versions of DART 5.5 prior to will prevent the Data Movers from properly resolving hostnames that use the local hosts file. Upgrade to the latest version of DART 5.5 if local hostname resolution will be used to identify the CCD. To use DNS: a. Create a DNS entry for the callback daemon that points to the appliance. b. Create multiple entries by the same name for each callback appliance. 48 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

49 Deploying File Management c. For each entry that is created, select the checkbox for Create associated pointer (PTR) record to ensure that it will be included in the Reverse Lookup Zones list. Note: The Celerra FileMover supports DNS HA failover. If the DNS server resolves the callback daemon hostname to multiple IP addresses, the Celerra FileMover transparently switches to the server at the next available IP address. Prerequisites for using Celerra as an archiving source To archive data from a Celerra Data Mover, the appliance requires access to the FileMover API (TCP port 5080). To archive NFS data, the appliance needs the following: Mount v3 RPC service NFS v3 RPC service NLM v4 RPC service Root and read/write export permissions for all NFS data that will be archived To archive CIFS data, the appliance needs SMB over NetBIOS (TCP port 139). Direct command line access to the Celerra Control Station is not used by the appliance. Using the FMA with the Celerra Data Mover as a source 49

50 Deploying File Management When configuring a Celerra Data Mover on the appliance, plan to provide: Credentials for a FileMover API user. This single set of credentials is used for both archive and recall. (For CIFS archiving only) Credentials for local administrator access through CIFS. (For CIFS archiving only) The NetBIOS name of the filer. Prerequisite on the Celerra Control Station If a Celerra has not been configured as a source for archiving, perform the following steps: 1. Enable filename translation on the Celerra Control Station. The FMA, FMHA, or FMA/VE expects that all filenames are derived from the Celerra Network Server in UTF-8 format. To preserve filenames correctly: a. Log in to the Celerra Control Station as nasadmin. b. Use a text editor to open the file: /nas/site/locale/xlt.cfg. c. Locate the last line of the file. Typically the last line appears as: :::: txt: Any thing that didn t match above will be assumed to be latin-1 Add the following line immediately above the last line: ::FMA_IP_ADDR::: FMA requires no translation (UTF-8) where FMA_IP_ADDR is the IP address of your appliance. d. To update the configuration, type: /nas/sbin/uc_config -update xlt.cfg e. To verify the new configuration, type: /nas/sbin/uc_config -verify FMA_IP_ADDR -mover ALL where FMA_IP_ADDR is the IP address of your appliance. Output will appear in the format: server_name : FMA_IP_ADDR is UTF-8 2. Create the FileMover API user. Log in to the Celerra Control Station CLI as root and type the command: /nas/sbin/server_user <data_mover> -add -md5 -passwd <user> For example: /nas/sbin/server_user server_2 -add -md5 -passwd rffm 3. Allow the IP addresses of the FMA, FMHA, or FMA/VE to open connections to the FileMover interface. While logged in to the Celerra Control Station as an administrator (such as nasadmin ), run the following command for all IP addresses of all appliances that will perform archiving or service recall requests for the Data Mover: server_http <data_mover> -append dhsm -users <user> -hosts <ip_address> For example: server_http server_2 -append dhsm -users rffm -hosts , , <FMA_IP_address> 50 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

51 Deploying File Management Note: A single Celerra Data Mover can be configured as an archiving source with multiple appliances, but more than one FMA or FMA/VE should never be used to archive data from a single filesystem. 4. Enable DHSM (FileMover) for the Data Mover. DHSM was disabled by default with Celerra DART 5.6 and later. To enable DHSM and keep it enabled if the Data Mover reboots, run the following command once: server_http <data_mover> service dhsm start 5. Enable DHSM for specific filesystems that will be used as archiving sources. To enable DHSM and keep it enabled if the Data Mover reboots, run the following command once per filesystem. fs_dhsm -modify <primary_fs> -state enabled For example: fs_dhsm -modify filesystem1 -state enabled 6. Ensure that the DHSM offline attribute is enabled for filesystems that will be used for archiving. To verify that the offline attribute is on, run the command: fs_dhsm -i <fs_name> grep offline attr If the offline attribute is on, the following line will appear: offline attr = on If the offline attribute is off, turn it on with the command: fs_dhsm -m <fs_name> -offline_attr on Note: Once the offline attribute is set to on, it must remain on or File Management archiving will not work. Create one or more connections from the Data Mover to the secondary storage locations for each filesystem that will be archived. Each CIFS or NFS repository used to store archived data needs to be configured as a DHSM connection for the Celerra filesystem. If data will be archived to an EMC Centera or an Atmos cluster, a DHSM connection that uses the HTTP protocol needs to be configured for the filesystem. Configuring automatically created DHSM connections FMA, FMHA, or FMA/VE can automatically create DHSM connections for Celerra systems that run DART 5.6. To configure this feature, perform the following steps on the Celerra and the appliance: 1. Check to see if the XML API server is running. As root user on the Celerra, type: ps -ef grep start_xml_api_server grep -v grep The following example shows a server that is already running: [root@celerra01 sbin]# ps -ef grep start_xml_api_server grep -v grep root :41? 00:00:00 /bin/sh /nas/sbin/start_xml_api_server If it is running, restart the server by typing: /nas/sbin/hup_api If it is not running, start the server by typing: /nas/sbin/start_xml_api_server Using the FMA with the Celerra Data Mover as a source 51

52 Deploying File Management If the server fails to start or restart: a. Delete the file /nas/api/exit_now. b. Delete the file /nas/api/api_retry. c. Repeat the process to check if the server is running and to start it. If the XML API server still fails to start, contact Celerra support. 2. Start the DHSM HTTP server on the Celerra: server_http <data_mover_name> -service dhsm -start 3. Create a new system user for the XML API and FileMover API operations. Use the API GUI on the Celerra Control Station: a. Log in as root and select: Security > Administrators > Users > New. The New User screen appears. b. Define a new system user: In the root group. With client access option XML API v2 allowed. This is the user for FileMover API settings on the FMA, FMHA, or FMA/VE. Use the same username and password that was defined for the FileMover API user in in step 2 of Prerequisite on the Celerra Control Station on page 50. If the user cannot be added to the root group, use the filemover group instead. Password Expiration appears blank, but DART 5.6 may fix a number of days. If the password expires, the FMA will be unable to connect to the Data Mover to automatically create DHSM connections. When a user password is updated or changed on the Celerra Control Station, update the FileMover settings for the 52 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

53 Deploying File Management Celerra Properties on the appliance as in step 3 of Adding a Celerra to the File Management configuration on page 45 and update the DHSM connection password with the command: fs_dhsm -connection <primary_fs> -modify <cid> -password <new_password> 4. Define Celerra Data Mover properties on the FMA or FMA/VE. Adding a Celerra to the File Management configuration on page 45 describes the following properties in greater detail: For Control Station, provide the Control Station IPs for DART 5.6. For FileMover Settings, type the username and password that were created for the new system user. If DHSM connections do not exist, the FMA automatically creates the connections before running each archiving task. Configuring manually created DHSM connections DHSM connections must be created manually if any of the following conditions apply: DART 5.6 is not being used. DART 5.6 is being used, but with an NFS-exported filesystem on a VDM. File Management is not being used to automatically create DHSM connections. Commands to create the connection for different archiving scenarios are provided as follows: When archiving CIFS data to NAS, you archive to a CIFS repository configured on the appliance. Create a connection to each CIFS repository that will hold archived data. This setting applies to any repository that is part of a multi-tier destination. Log in to the CLI of the Celerra Control Station and type the command: fs_dhsm -connection <primary_fs> -create -type cifs admin <fqdn>\<domain_administrator> secondary \\<fqdn_of_secondary_server>\<repository_path> -local_server <local_cifs_server> For example: fs_dhsm -connection filesystem1 -create -type cifs -admin 'mydomain.prv\administrator' -secondary '\\oldserver.mydomain.prv\fma\' -local_server ns80dm1 Note: Use the apostrophe instead of quotation marks to encapsulate the CIFS administrative username and UNC path of the secondary storage location. When archiving NFS data to NAS, you archive to an NFS repository configured on the appliance. Create a connection to each NFS repository that will hold archived data. Log in to the CLI of the Celerra Control Station, and type the command: fs_dhsm -connection <primary_fs> -create -type nfsv3 secondary <fqdn_of_secondary_server>:/<repository_path> -proto TCP userootcred True For example: fs_dhsm -connection filesystem1 -create -type nfsv3 secondary oldserver.mydomain.prv:/fma -proto TCP userootcred True Using the FMA with the Celerra Data Mover as a source 53

54 Deploying File Management When archiving any type of data to an EMC Centera CAS or Atmos server, recall requests will flow from the Data Mover to FMA, FMHA, or FMA/VE. To create the connection for an EMC Centera, log in to the CLI of the Celerra Control Station, and type the command: fs_dhsm -connection <primary_fs> -create -type http secondary ' for CCD>/fmroot' -httpport cgi n -user <user> For example: fs_dhsm -connection filesystem1 -create -type http secondary ' -httpport cgi n -user rffm When prompted, type a password for the rffm user. To create the connection for an Atmos server, log in to the CLI of the Celerra Control Station and type the command: fs_dhsm -connection <primary_fs> -create -type http secondary ' for ACD>/fmroot' -httpport cgi n -user <user> For example: fs_dhsm -connection filesystem1 -create -type http secondary ' -httpport cgi n -user rffm When prompted, type a password for the rffm user. These same settings are used in Adding a Celerra to the File Management configuration on page 45. The FQDN for the callback daemon is used for Celerra Callback Agent Settings on page 46 or Atmos Callback Agent Settings on page 46. The FQDN must be distinct even if the the Celerra and Atmos callback daemons are running on the same appliance. The same user and password credentials are used for FileMover Settings in step 3. Regardless of the type of connection (CIFS, NFS, or HTTP), the target of a connection should be specified as a hostname or FQDN in the command: fs_dhsm -connection <primary_fs> -create When a Celerra Data Mover needs to establish a connection to secondary storage, it first attempts to resolve the hostname in the local hosts file. If the name cannot be resolved locally, the Data Mover then issues a DNS query. When archiving to NAS from Celerra, a DNS record is required to resolve the FQDN of the secondary storage server to IP addresses if the local hostname resolution of the Celerra is not going to be used. A PTR record (reverse DNS) is also required to map the IP addresses of the secondary storage server to the FQDN. Note: The Celerra File Level Retention (FLR) enabled filesystems cannot be used as an archiving source. 54 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

55 Deploying File Management Using the FMA with the NetApp filer as a source To use File Management with a NetApp filer, first configure the filer, and then configure the appliance. Prerequisites for using NetApp as an archiving source To archive any data from a NetApp filer, the FMA, FMHA appliance, or FMA/VE requires access to: SMB over NetBIOS (TCP port 139) ONTAPI (TCP port 80) In addition, to archive NFS data, the FMA, FMHA appliance, or FMA/VE will require the following: Portmap v2 RPC service (TCP port 111) Mount v3 RPC service NFS v3 RPC service NLM v4 RPC service Root and read/write export permissions for all NFS data that will be archived inode to pathname mapping is enabled for NFS clients that will access stub files When configuring a NetApp filer on the FMA or FMA/VE, plan to provide: All IP addresses that are used by the filer Credentials for local administrator access through both CIFS and ONTAPI The NetBIOS name of the filer Note: If a NetApp filer leverages its vscan interface for virus scanning, the IP addresses of the vscan servers must be configured on the appliance as excluded clients on the NetApp FPolicy Special Clients configuration page in the GUI. This allows the virus scanner to scan the stub file upon a recall event. Failure to configure excluded clients properly will lead to recall failures when vscan is used in conjunction with FPolicy. Direct command line access through Telnet or SSH is not used by the appliance. However, ONTAPI access is used to send a variety of API calls and hence the requirement for a local administrator s credentials. If a user other than root is specified, then the following option must be set: options httpd.admin.hostsequiv.enable on Ensure that the appliance hostname: Can be resolved to its IP addresses in the local /etc/hosts file of the NetApp filer. Maps to a user with privileges to access the ONTAPI interface in the /etc/hosts.equiv file on the filer. Additional configuration prerequisites vary, depending upon the existing network environment: For NetApp filers that run Data ONTAP 7.2 or later, disable duplicate session detection by setting: options cifs.client.dup-detection off Using the FMA with the NetApp filer as a source 55

56 Deploying File Management To properly support stub files, NetApp FPolicy requires a particular CIFS offline bit attribute on the stub files: The CIFS protocol must be enabled on the NetApp filer to archive either CIFS or NFS datasets. An active CIFS license must be installed on all file servers that are archive sources. NFS-only exports must be shared as well. To properly recall stub files, FPolicy must be enabled (options fpolicy.enable on) and rfpolicy must be the only screen policy registered for reads and writes. If a policy that monitors stub files on the NetApp filer was previously installed, manually delete it. To configure NFS archiving, perform the following steps on the NFS-only source directories: 1. Create a share at the qtree or volume level for qtree sources. 2. Create a share at the volume level for non-qtree sources, that is, those not part of any qtree. 3. Add access to only the File Management user. Note: File Management does not support name clashes on qtrees. For example, QTREE1 against qtree1. vfiler configuration Additional configuration prerequisites apply to vfiler support for NetApp filers that run ONTAP 7.1: Manually create rfpolicy configuration on the vfiler with the commands: fpolicy create rfpolicy screen fpolicy enable rfpolicy fpolicy options rfpolicy required on Manually configure secondary FPolicy servers with the command: fpolicy options rfpolicy secondary_servers ip,ip To use NetApp vfilers with File Management, ensure that: The FMA can access to both the vfiler and the hosting NetApp filer. vfilers and main filers are in IP spaces that can reach each other. Configuring NetApp archiving on the FMA To archive from the NetApp filer, configure the FPolicy callback service on the FMA, FMHA appliance, or FMA/VE. 1. Type the following: /opt/rainfinity/filemanagement/bin/fpsetup.sh init_rffm 2. At the prompt that appears, select the interface on which the FPolicy callback daemon should listen for callbacks from NetApp filers. If there is only one interface, it will be selected automatically: If this is the primary callback agent in the environment, type n. 56 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

57 Deploying File Management If this machine is being configured as the secondary callback agent, type y. When prompted, type the IP address and the root password of the primary agent. Adding a NetApp filer to the File Management configuration 1. Click the File Server link on the Configuration tab. The File Server Properties dialog box appears. Select NetApp from the Type list box. 2. Specify the following for the NetApp file server: Name Type the NetApp filer NetBIOS name. IP Addresses Type the NetApp filer IP address. When editing an existing server, click Update to retrieve the IP address from the DNS that is based on the server name. To specify an additional IP address, click Add. The IP address is added to the list. To delete an existing IP address, select an IP and click Delete. Vfiler Host IP If using a vfiler, type the IP address of the hosting NetApp filer. CIFS Specific Settings This is the Windows domain user to be used by the appliance. To avoid permission issues during archiving and recall, add this user as a member of the domain administrator group with backup operator privileges. If this user cannot be added to the domain administrator group, add it to the file server's local Administrators group with backup privileges. Windows domain user on page 95 provides more information on administering domain users. Note: For NetBIOS Domain, use the NetBIOS domain name and not the FQDN. For example, use emc and not emc.com. Using the FMA with the NetApp filer as a source 57

58 Deploying File Management NetApp as Source This option configures the FMA to archive data from the NetApp filer. If more than one FMA is connected to the same NetApp filer, configure only one FMA with this option. These options are not required if this NetApp is used as a destination.! CAUTION If more than one FMA is configured to archive data from a single NetApp filer, data loss may occur. NetApp Local Admin Type the username and password of a user on the NetApp filer. The user must be a member of the NetApp local administrator s group. Directory Exclusion List These are the directories to exclude for all tasks. File Management ignores all system directories such as etc, lost+found,.snapshot by default. NetApp FPolicy callback agents The primary agent recalls all files when it is registered with the NetApp. A secondary agent recalls files when the primary is unavailable. If the FPolicy callback agent is not explicitly configured as a secondary agent, then it is a primary agent and the NetApp file server will load balance between the registered primary agents. If no primary agents respond, then the NetApp filer will contact any of the registered secondary agents. When one of the primary agents is responsive again, the NetApp filer will automatically fail back to the primary agent. For the primary agent, select the agent that is on the same subnet as the NetApp machine. For the secondary agent, select another agent on the same subnet. If no such agent exists, select an agent on the next physically closest subnet. Up to two secondaries are supported. Secondary agents may include FMHA appliances. 3. Click Commit to define the NetApp filer. Adding a Windows server to the FMA configuration Windows 2003 and 2008 servers are supported as CIFS NAS destinations. Configure the FMA to archive to a Windows server. 1. Click the File Servers link on the Configuration tab. The File Server List appears. 2. Click New. The File Server Properties page appears. 58 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

59 Deploying File Management 3. Select Windows from the Type list box. The Windows Properties page appears: 4. Specify the following for the Windows server: Name Type a name to identify the Windows server. IP Addresses Specify the IP address of the Windows server. When editing an existing server, click Update to retrieve the IP address from the DNS that is based on the server name. To specify an additional IP address, click Add. The IP address is added to the list. To delete an existing IP address, choose an address and click Delete. CIFS Specific Settings This is the Windows domain user to be used by the appliance. The domain user must be a member of the local administrator s group on the Celerra. Windows domain user on page 95 provides more information. 5. Click Commit to define the Windows server. Adding a Windows server to the FMA configuration 59

60 Deploying File Management Configuring a NAS-based repository Any Celerra Data Mover, NetApp filer, Windows, or Data Domain server can be configured as a NAS-based repository. Note: The appliance must have read/write access to any share or export that may be used as an archive source or destination. In addition, the appliance must have read/write permission for any file that it may archive. 1. Click NAS Repository and NAS group on the Configuration tab. The NAS Repository List and NAS Group List page appears. 2. For Create NAS Repository, click New. The Create New NAS Repository dialog box appears. 3. Specify the following for the NAS repository: File Server Select a file server from the list. Note: The file server must have a proper DNS entry defined that links the file server name with the IP address. Protocol Select NFS or CIFS. The source and repository protocol types must match. If the source protocol is CIFS, the NAS repository protocol must be CIFS. If the source protocol is NFS, the NAS repository protocol must be NFS. If the CIFS protocol is selected, use the CIFS user in the filesystem CIFS DHSM connection string for CIFS specific settings when configuring the primary storage on the appliance: Adding a Celerra to the File Management configuration on page 45 provides details on configuring this setting for Celerra NAS. Adding a NetApp filer to the File Management configuration on page 57 provides details on configuring this setting for NetApp. Adding a Windows server to the FMA configuration on page 58 provides details on configuring this setting for Windows. Path Click Browse to select an existing path. Once the path is specified, a name in the form of Repository at <path> appears in the Name field. 60 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

61 Deploying File Management Maximum limit of disk usage Type a percentage value for disk usage. Default value is 90%. 4. Click Save Repository. The NAS Repository List reappears with the new NAS repository listed. Using FMA with EMC Centera 1. Click the File Servers link on the Configuration tab. The File Server List appears. 2. Click New. The File Server Properties page appears. 3. Select Centera from the Type list box. The Centera Properties page appears: 4. Specify the following for EMC Centera: Name Type a name to identify the EMC Centera. Using FMA with EMC Centera 61

62 Deploying File Management Access Node IP Specify the IP address of the EMC Centera access node: To specify an additional access node IP, click Add. The IP address is added both to the list and as an entry in the Access Node String field. If an EMC Centera cluster is being used, a hostname can be used in place of an IP address. To delete an existing node, select a node IP and click Delete. Access Node String This is automatically generated when the Access Node IP address is added or deleted. You cannot type data directly into the field. Authentication Select from one of the three choices: Anonymous If selected, no security is used to authenticate with EMC Centera. User profile If selected, type the username and password of the EMC Centera profile that is to be used for archiving. PEA file This option requires that a profile and pool entry authorization (PEA) file was created to access EMC Centera, and that a copy of the PEA file resides on the File Management Appliance. If selected, the PEA file is used to authenticate the File Management connection with EMC Centera. Type the path to the file on the local machine or browse for the file. A copy of the file will be stored with the File Management configuration. 5. Click Commit to define EMC Centera. Using the FMA with an Atmos server The Atmos cloud-optimized storage product is supported as an archiving destination. Configure the FMA to archive to an Atmos. 1. Click the File Servers link on the Configuration tab. The File Server List appears. 2. Click New. The File Server Properties page appears. 3. Select Atmos from the Type list box. The Atmos Properties page appears. 62 EMC File Management Appliance and File Management Appliance/VE Version Getting Started Guide

63 Deploying File Management 4. Specify the following for the Atmos: Name Type a name to identify the Atmos. DNS Name Specify the name used to resolve the IP addresses in the Atmos cluster. Port The GUI access method. HTTPS is the default and is typically used when the Atmos is deployed remotely. Select HTTPS or HTTP to specify the communication protocol. Type the port number through which HTTPS or HTTP connects. Username Type the name that corresponds to a user ID with access to storage on the cluster. This username is created on the Atmos first. Password Type the password or shared secret that was generated when the username was created on the Atmos. 5. Click Commit to define the Atmos. Using the FMA with a Data Domain server The EMC Data Domain storage product is supported as an archiving destination. Configure the FMA to archive to Data Domain server. 1. Click the File Servers link on the Configuration tab. The File Server List appears. 2. Click New. The File Server Properties page appears. 3. Select Data Domain from the Type list box. The Data Domain Properties page appears. Using the FMA with a Data Domain server 63