docu34939 cloud tiering appliance and cloud tiering appliance ve 7.5 getting started guide

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-91031-508-435-1000www.EMC.com

EMC Cloud Tiering Appliance andCloud Tiering Appliance/VE

Version 7.5

Getting Started GuideP/N 300-005-093

REV A14

EMC Cloud Tiering Appliance and Cloud Tiering Appliance/VE Version 7.5 Getting Started Guide2

Copyright 2007 - 2011 EMC Corporation. All rights reserved.

Published August, 2011

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

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

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

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

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

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

EMC Cloud Tiering Appliance and Cloud Tiering Appliance/VE Version 7.5 Getting Started Guide 3

Preface

Chapter 1 Introduction Overview of the EMC Cloud Tiering Appliance................................................ 16

Cloud Tiering Appliance/VE (CTA/VE) ..................................................... 16High Availability for CTA and CTA/VE...................................................... 17

CTA implementation with Celerra or VNX primary storage........................... 18 CTA implementation with NetApp primary storage........................................ 20 CTA and CTA/VE tasks......................................................................................... 21 Using CTA and CTA/VE....................................................................................... 23

Chapter 2 Cloud Tiering Appliance Hardware and Port Configurations Contents of the appliance ...................................................................................... 26

Cloud Tiering Appliance types ...................................................................... 26Cloud Tiering Appliance High Availability types ...................................... 26

Cloud Tiering Appliance details........................................................................... 27 Cloud Tiering Appliance for High Availability details ..................................... 29 Appliance diagrams .............................................................................................. 31 Port details ............................................................................................................... 34

Chapter 3 Deploying the Cloud Tiering Appliance Deployment process ............................................................................................... 36 Supported platforms .............................................................................................. 37 Appliance setup ...................................................................................................... 38 Installing the virtual edition.................................................................................. 39 CTA and CTA/VE for high availability............................................................... 43

Celerra or VNX primary storage .................................................................... 43NetApp primary storage ................................................................................. 43

Configuring CTA .................................................................................................... 44Configuring the CTA network ....................................................................... 45Configuring the hostname, domain, and DNS server................................. 45Graphical user interface................................................................................... 46Command line interface .................................................................................. 46

Deploying CTA with Celerra or VNX.................................................................. 47Prerequisites for using Celerra or VNX as a file migration source or destination ........................................................................................................ 47Prerequisites for Celerra or VNX as an archive source............................... 47

Contents


Adding a Celerra or VNX to the CTA configuration................................... 48Configuring Celerra or VNX to EMC Centera or Atmos archiving on the CTA ......................................................................................................... 50Configure name resolution for archiving...................................................... 51Prerequisite tasks on the Celerra or VNX Control Station for file migration or archiving......................................................................... 52

Deploying CTA with NetApp ............................................................................... 58Prerequisites for using NetApp as a file migration source......................... 58Prerequisites for using NetApp as an archiving source ............................. 58vFiler configuration ......................................................................................... 60Configuring NetApp archiving on the CTA ................................................ 60Adding a NetApp filer to the CTA configuration........................................ 61

Deploying the CTA with a VNXe ......................................................................... 63Prerequisites for using VNXe as a file migration destination ................... 63Adding a VNXe to the CTA configuration.................................................... 63

Deploying CTA with a Windows server .............................................................. 65 Deploying CTA with Isilon.................................................................................... 66

Prerequisite tasks when using Isilon as a CIFS share destination ............. 66Prerequisite tasks when using Isilon as an NFS export destination.......... 69Adding an Isilon to the CTA configuration .................................................. 70

Deploying the CTA with a Data Domain............................................................. 71 Configuring a NAS-based repository .................................................................. 72 Deploying CTA with EMC Centera...................................................................... 73 Deploying CTA with Atmos.................................................................................. 75

Adding Atmos to the CTA configuration...................................................... 75Installing the SSL certificate on the CTA....................................................... 76

Chapter 4 Maintaining the Cloud Tiering Appliance Importing a file list archive.................................................................................... 78

Adding the primary servers ............................................................................ 78Configuring the import provider ................................................................... 79Configuring the import task............................................................................ 79Importing the file list ........................................................................................ 80Validating the import file................................................................................. 81

Backing up the configuration ................................................................................ 82Creating a backup dump ................................................................................. 83Restoring a backup dump................................................................................ 84

Maintaining the database....................................................................................... 88Checking database size and disk capacity .................................................... 88Performing database maintenance ................................................................. 88

Performing a CD clean install................................................................................ 89 Software upgrades .................................................................................................. 90

Before upgrading from FMA versions earlier than 7.3................................ 90CD full upgrade................................................................................................. 91UPG upgrade ..................................................................................................... 92

Migrating from CTA to CTA/VE.......................................................................... 93 Shutting down and restarting the appliance....................................................... 94

Chapter 5 Cloud Tiering Appliance System Settings Security hardening .................................................................................................. 96

Single security database ................................................................................... 96Disable root logins ............................................................................................ 97Strengthen passwords ...................................................................................... 98


Age passwords.................................................................................................. 98 Configuring the GUI access method.................................................................... 99 STIG hardening ....................................................................................................... 99

Enabling STIG hardening................................................................................ 99Disabling STIG hardening............................................................................. 100

LDAP client configuration .................................................................................. 101Global LDAP settings..................................................................................... 101LDAP authentication ..................................................................................... 101Configuring basic LDAP settings................................................................. 102Configuring advanced LDAP settings ........................................................ 103

RADIUS and TACACS+ ...................................................................................... 104 Certificate management ...................................................................................... 104 Appliance mail delivery settings........................................................................ 105 Log settings............................................................................................................ 106

Configuring log rotation................................................................................ 106Configuring SCP of rotated log files............................................................ 106Alerts ................................................................................................................ 108Configuring email alerts................................................................................ 112Configuring SNMP alerts .............................................................................. 113Enabling SNMP polling................................................................................. 113

System command accounting ............................................................................. 114Tracking user command history .................................................................. 115Tracking user login history ........................................................................... 115Tracking daemon command history............................................................ 115

Windows domain user ......................................................................................... 116Creating a Windows domain user ............................................................... 116Adding an admin user to the local administrator group.......................... 116Configuring Windows 2008 for NTLM ....................................................... 117

SID translator......................................................................................................... 118Installing the SID translator .......................................................................... 118Creating the SID translation file ................................................................... 119Uploading the SID translation file ............................................................... 121Deleting a SID translation file....................................................................... 121

Appendix A Network Topology Scenarios Advanced network topologies............................................................................ 124

Configuring the CTA with bonding ............................................................ 124Configuring the CTA with two subnets...................................................... 125Configuring the CTA with more than two subnets................................... 125

VLAN tagging modes for the CTA/VE............................................................. 127ESX Server virtual switch tagging ............................................................... 127ESX Server virtual guest tagging ................................................................. 128

Glossary

Index


Title Page

1 Celerra or VNX implementation ......................................................................................... 182 NetApp implementation ...................................................................................................... 203 Archived report example ..................................................................................................... 224 Rear view of Gen 7 appliance .............................................................................................. 315 Front view of Gen 7 appliance with bezel removed ........................................................ 316 Front view of the Gen 7 appliance with bezel ................................................................... 317 Rear view of Gen 5 or Gen 6 appliance .............................................................................. 328 Front view of Gen 5 or Gen 6 appliance with bezel removed ........................................ 329 Front view of the Gen 5 or Gen 6 appliance with bezel .................................................. 3210 Front view of Dell R710 for High Availability with bezel removed .............................. 3311 Front view of Dell 2950 for High Availability with bezel removed .............................. 3312 CTA-APL, CTA-APL-HA, FMA7-APL and FMA7-HA-APL port details .................... 3413 FMA6-APL, FMA6-HA-APL, and FMA5-HA-APL port details .................................... 3414 Cloud Tiering Appliance deployment process ................................................................. 3615 Example of Celerra property settings in FMA version 7.2 .............................................. 90

Figures


Figures


Title Page

1 CTA that is based on Dell R710 ........................................................................................... 272 CTA that is based on Dell 2950 ........................................................................................... 273 CTA-HA that is based on Dell R710 ................................................................................... 294 CTA-HA that is based on Dell 2950 .................................................................................... 295 Supported platform matrix for multi-tier archiving ........................................................ 376 Supported platform matrix for file migration ................................................................... 377 VMware ESX Server interoperability ................................................................................. 398 Supported SNMP traps ...................................................................................................... 1089 CTA alerts ............................................................................................................................. 108

Tables


Tables

Preface 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 This document is part of the EMC Cloud Tiering Appliance and Cloud Tiering Appliance/VE documentation set. The documentation is intended for use by:

Storage management administrators who are new to the EMC Cloud Tiering Appliance and Cloud Tiering Appliance/VE.

Existing customers who are new to version 7.5.

Relateddocumentation

Related documents include:

EMC Cloud Tiering Appliance and Cloud Tiering Appliance/VE online help Provides detailed reference information on specific product features and functions.

EMC Cloud Tiering Appliance and Cloud Tiering Appliance/VE Release Notes Provides an overview of new features and lists any limitations.

EMC CTA 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

Conventions used inthis 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 conventionsEMC uses the following type style conventions in this document:

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

fields, and menus) Names of resources, attributes, pools, Boolean expressions, buttons, DQL

statements, keywords, clauses, environment variables, functions, utilities URLs, pathnames, filenames, directory names, computer names, filenames, links,

groups, service keys, file systems, notifications

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

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

Used in procedures for: Names of interface elements (such as names of windows, dialog boxes, buttons,

fields, and menus) What user specifically selects, clicks, presses, or types

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

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

running text

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

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

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

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means or

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

... Ellipses indicate nonessential information omitted from the example

13

Preface

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

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

http://Powerlink.EMC.com

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

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

[email protected]


Preface

Introduction 15

1

This chapter includes the following sections:

Overview of the EMC Cloud Tiering Appliance ....................................................... 16 CTA implementation with Celerra or VNX primary storage .................................. 18 CTA implementation with NetApp primary storage ............................................... 20 CTA and CTA/VE tasks ................................................................................................ 21 Using CTA and CTA/VE .............................................................................................. 23

Introduction


Introduction

Overview of the EMC Cloud Tiering ApplianceThe EMC Cloud Tiering Appliance is technology that optimizes primary NAS storage by automatically moving inactive files based on policies to less expensive secondary storage. Secondary storage could be lower cost disk, such as NL-SAS or SATA drives, or to other platforms including public and private clouds. Files that are moved appear as if they are on primary storage. File tiering dramatically improves storage efficiency, and backup and restore time. File archiving onto storage with WORM functionality can support additional business requirements such as compliance and retention.

As an example, a Cloud Tiering Appliance may be configured to locate all NAS data that has not been accessed in one year, and move that data to secondary storage. For each file it moves, the appliance 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 a multi-tier policy is used, the appliance may be configured to move 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 datas new location on the tertiary storage tier.

In addition to tiering data from primary to secondary storage and leaving a stub behind on the primary server for recall later, the Cloud Tiering Appliance can also permanently migrate files from a source to a destination without leaving a stub.

The Cloud Tiering Appliance provides a full range of features including the ability to:

tier or archive and recall data

migrate files

simulate the potential effect of policies before taking action

perform orphan file management

perform stub file recovery

The Cloud Tiering Appliance software also includes a robust reporting interface that provides valuable insight into the efficacy of archiving policies.

Depending on the type of task, CTA supports a variety of platforms:

Supported platform matrix for multi-tier archiving on page 37

Supported platform matrix for file migration on page 37

The Cloud Tiering Appliance (CTA) refers to both the physical and virtual appliance, unless stated otherwise. The physical appliance is delivered preloaded with software. The virtual appliance is installed on a VMware server. One or more of each type may be deployed within a customer environment to create a complete solution.

Cloud Tiering Appliance/VE (CTA/VE)The Cloud Tiering Appliance/VE (CTA/VE) is a VMware virtual appliance installed on a VMware ESX/ESXi Server. CTA/VE is provided in an industry-standard virtual appliance distribution that consists of an Open Virtualization Format (OVF) and Virtual Machine Disk (VMDK) file.

Overview of the EMC Cloud Tiering Appliance 17

Introduction

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.

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.

High Availability for CTA and CTA/VEThe Cloud Tiering Appliance for High Availability (CTA-HA) and the Cloud Tiering Appliance/VE for High Availability (CTA/VE-HA) complement the existing CTA or CTA/VE by ensuring that tiered files can always be recalled, even in the event that the primary appliance goes down. This ensures complete transparency and nondisruptive service for clients. The high availability appliance is not 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.

The CTA-HA is a dedicated machine that runs the EMC Celerra, EMC VNX, or NetApp callback agents and is delivered preloaded with software. Installation instructions for the CTA-HA differ slightly from the CTA. The CTA/VE-HA provides the same functionality as the CTA-HA but is installed on a virtual appliance like the CTA/VE. A virtual HA can be deployed with a physical CTA and vice versa. In this way, a network with a physical CTA does not need a second piece of hardware to provide HA, it can use a CTA/VE-HA.

When a high-availability appliance is deployed alongside a CTA or CTA/VE, the underlying APIs of Celerra, VNX, and NetApp file servers are leveraged to create a highly available environment for data recall. The Celerra, VNX, and NetApp implementations differ as shown in Figure 1 on page 18 and Figure 2 on page 20.

High-availability appliances are not needed in all tiered source and destination combinations. The CTA and CTA/VE Interoperability Matrix provides more details.


Introduction

CTA implementation with Celerra or VNX primary storageFigure 1 on page 18 shows the recall architecture of CTA implementation with a Celerra or VNX.

Figure 1 Celerra or VNX implementation

Circled numbers correspond to the following steps that illustrate the recall process in the Celerra or VNX implementation:

1. Clients send read/write operations for files that have been archived. These operations are intercepted by the DHSM layer on the Celerra or VNX prior to being serviced from the filesystem.

2. If the file has been archived to EMC Centera or EMC Atmos storage, the Celerra or VNX blade resolves the fully qualified domain name (FQDN) to the IP address of the CTA or CTA-HA.

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 or VNX blade uses an alternate IP address of another appliance configured in DNS. Every

EMC Centera or Atmos

PowerEdge2950

PowerEdge2950

File System

NFSRepository

CIFSRepository

DHSM

Celerra or VNX HTTP(TCP 8000 for EMC Centera)(TCP 9000 for Atmos)

DNS

EMC CTA

EMC CTA-HANFS CIFS

Platform API

SMB overNetBIOS

(TCP 139)

SMB overTCP

(TCP 445)NFS

(RPC)HTTP

(TCP 80)FTP

(TCP 21)

CIFS R/W

/etc/hosts

CIFS R/W NFS R/W HTTP R/W FTP R/W

3

4 1

2

CNS-001622

CTA implementation with Celerra or VNX primary storage 19

Introduction

callback server (CTA, CTA-HA, CTA/VE, or CTA/VE-HA) 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 a message that the file cannot be opened if the recall fails.

Note: When Celerra or VNX data has been archived to a Celerra, VNX, VNXe, NetApp, Data Domain, Isilon, or Microsoft Windows repository, the CTA or CTA/VE is not involved in the recall process and a high availability appliance is not used.


Introduction

CTA implementation with NetApp primary storageFigure 2 on page 20 shows the recall architecture of CTA implementation with a NetApp.

Figure 2 NetApp implementation

Circled numbers correspond to the following steps that illustrate the archive and recall process in the NetApp 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 a CTA and possibly one or more CTA-HAs.

A secondary group, such as one or more physical or virtual HAs.

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 CTA/VE, the primary group of callback servers consists of virtual machines such as a CTA/VE and possibly one or more CTA/VE-HAs. The secondary group consists of one or more CTA/VE-HAs.

EMC Centera or Atmos

PowerEdge2950

PowerEdge2950

Primary

WAFL

NFSRepository

CIFSRepository

FPolicy Secondary

FPolicy APIFPolicy API

PlatformAPI

EMC CTA-HAEMC CTA

NFS CIFS/SMBover NetBIOS

SMB overNetBIOS

(TCP 139)

SMB overTCP

(TCP 445)NFS

(RPC)HTTP

(TCP 80)FTP

(TCP 21)

CIFS Recall (Writes)SMB over NetBIOS

NFS Recall (Writes)

CIFS R/W CIFS R/W NFS R/W HTTP R/W FTP R/W

3

4 1

2

CNS-001619

CTA and CTA/VE tasks 21

Introduction

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, EMC Centera, or Atmos 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 a CTA that is running version 7.5 and a CTA-HA that is running version 7.4. 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.

CTA and CTA/VE tasksThe CTA or CTA/VE may be used to run several different tasks:

Tiering or archiving

Deleting orphaned data

Auxiliary tasks, such as stub scanning, and backup

Migration tasks such as repository migration and file migration

For tiering, deleting and migrating files, the software leverages a policy engine to select the files. Users can combine and evaluate multiple rules together in a single policy. Several rule types are available.

Before running the archive, delete, or 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

Also, if an optional detailed simulation is run, a list of files that match the policy is saved on the disk for review.

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.


Introduction

A report displays results of the task. Figure 3 on page 22 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.

In addition, CTA can perform an archive task on an imported list of files.

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.

Using CTA and CTA/VE 23

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 CTA database, and maps the name and location of the archived file to its stub. The stub scanning task scans for stubs in the CTA 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 CTA configuration and database. Schedule backup tasks as part of a regular maintenance program.

Repository Migration Repository migration moves all archived data from one repository to another storage tier. Migration can be to a NAS repository, to an EMC Centera, or to an Atmos on-premise or service provider cloud. All stub files that point to this data will be updated to point to the new location.

File Migration (with policy) The file migration task moves files between two primary file servers that are defined as the source and destination in the task definition. The task evaluates both normal and stub files based on the migrate file policy with a resulting action of either migrate or dont migrate.

The CTA 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 CTA and CTA/VEOnce the appliance has been deployed on the network, the administrator can manage data through the CTA or CTA/VE graphical user interface (GUI) or command line interface (CLI). Graphical user interface on page 46 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 CTA or CTA/VE, are provided in the following chapters and appendixes:

Chapter 3, Deploying the Cloud Tiering Appliance

Chapter 4, Maintaining the Cloud Tiering Appliance

Chapter 5, Cloud Tiering Appliance System Settings

Appendix A, Network Topology Scenarios

Except where expressly stated otherwise, all sections of this guide apply to both the CTA and CTA/VE.


Introduction

Cloud Tiering Appliance Hardware and Port Configurations 25

2

This chapter contains the following sections:

Contents of the appliance.............................................................................................. 26 Cloud Tiering Appliance details .................................................................................. 27 Cloud Tiering Appliance for High Availability details ............................................ 29 Appliance diagrams....................................................................................................... 31 Port details....................................................................................................................... 34

Cloud TieringAppliance Hardware

and Port Configurations


Cloud Tiering Appliance Hardware and Port Configurations

Contents of the applianceThe CTA or CTA-HA 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 Cloud Tiering 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 the software recovery CD.

One serial cable.

Note: The following are items are not included: VGA monitor, keyboard, and mouse for a system console.

Cloud Tiering Appliance types Dell R710 Models CTA-APL and FMA7-APL ship with two enabled on-board

gigabit Ethernet copper 10/100/1000TX ports. Figure 12 on page 34 shows the port details.

Dell 2950 Models FMA6-APL and FMA5-APL ship with two on-board gigabit Ethernet copper 10/100/1000TX ports. Figure 13 on page 34 shows the port details.

Cloud Tiering Appliance High Availability types Dell R710 Models CTA-APL-HA and FMA7-HA-APL ship with two enabled

on-board gigabit Ethernet copper 10/100/1000TX ports. Figure 12 on page 34 shows the port details.

Dell 2950 Models FMA6-HA-APL and FMA5-HA-APL ship with two on-board gigabit Ethernet copper 10/100/1000TX ports. Figure 13 on page 34 shows the port details.

Cloud Tiering Appliance details 27


Cloud Tiering Appliance detailsTable 1 on page 27 lists the Gen 7 hardware configurations for the CTA that are based on the Dell R710 hardware.

Table 2 on page 27 lists the Gen 5 and Gen 6 hardware configurations for the CTA that are based on the Dell 2950 hardware.

Table 1 CTA that is based on Dell R710

Component CTA-APL, FMA7-APL

Chassis The appliance is based on Dell R710 11G hardware.

Size 2U form factor

Power Dual 570 watts

CPUs Dual, 2.0 GHz, E5504 4C/4T 80W 4MB Cache Nehalem-EP

Disks 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 31.

RAID controller PERC6/I

CD-ROM Read-only DVD that can read CD or DVD material for system upgrades. Item (a) in Figure 5 on page 31.

Memory 1066-MHz, 4 GB total (1 x 2 GB DIMM per proc/dual proc configuration)

Network interfaces Two on-board gigabit 10/100/1000TX Ethernet copper ports with RJ45 connectors. Item (e) in Figure 4 on page 31.

VGA Standard VGA video connector for a system console. Item (a) in Figure 4 on page 31.

Keyboard connector Standard USB keyboard connector for a system console. Item (d) in Figure 4 on page 31.

Mouse connector Standard USB mouse connector for a system console. Item (c) in Figure 4 on page 31.

Serial port Standard DB9 serial port for a serial-terminal system. Item (b) in Figure 4 on page 31.

Table 2 CTA that is based on Dell 2950 (page 1 of 2)

Component FMA6-APL FMA5-APL

Chassis The appliance is based on Dell 2950 hardware.

The appliance is based on Dell 2950 hardware.

Size 2U rackmount form factor with universal rails. Dimensions: 8.6 cm (h), 44.5 cm (w), 66.1 cm (d). Weight: 34 kg.

2U rackmount form factor with universal rails. Dimensions: 8.6 cm (h), 44.5 cm (w), 66.1 cm (d). Weight: 34 kg.

Power Dual redundant 750 watt hot-plug, power supplies. Total consumption: 5A at 120 V or 2.5 A at 240 V.

Dual redundant 750 watt hot-plug, power supplies. Total consumption: 5A at 120 V or 2.5 A at 240 V.

CPUs Dual Intel Xeon 3.00 GHz Quad Core processors with 1333 MHz front-side bus.

Dual Intel Xeon 3.00 GHz Dual Core processors with 1333 MHz front-side bus.



Disks Four 250 GB, SATA, 3.5-inch, 7.2K RPM hard drives in a RAID-5 configuration. Items (b) through (e) in Figure 8 on page 32.

Six 160 GB, SATA, 3.5-inch, 7.2K RPM hard drives in a RAID-1 configuration. Items (b) through (g) in Figure 8 on page 32.

RAID controller 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.

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 24x IDE CD-ROM/DVD-ROM drive for system upgrades. Item (a) in Figure 8 on page 32.

24x IDE CD-ROM drive for system upgrades. Item (a) in Figure 8 on page 32.

Memory 667 MHz, (4 x 1 GB), single-ranked DIMMs

667 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 7 on page 32.


Standard VGA video connector for a system console. Item (a) in Figure 7 on page 32.


Standard USB keyboard connector for a system console. Item (d) in Figure 7 on page 32.


Standard USB mouse connector for a system console. Item (c) in Figure 7 on page 32.


Standard DB9 serial port for a serial-terminal system. Item (b) in Figure 7 on page 32.

Table 2 CTA that is based on Dell 2950 (page 2 of 2)

Component FMA6-APL FMA5-APL

Cloud Tiering Appliance for High Availability details 29


Cloud Tiering Appliance for High Availability detailsTable 3 on page 29 lists the Gen 7 hardware configurations for the CTA-HA that are based on the Dell R710 hardware.

Table 4 on page 29 lists the Gen 5 and Gen 6 hardware configurations for the CTA-HA that are based on the Dell 2950 hardware.

Table 3 CTA-HA that is based on Dell R710

Component CTA-APL-HA, FMA7-HA-APL

Chassis The appliance is based on Dell R710 11G hardware.

Size 2U form factor

Power Dual 570 watts

CPUs Single, 2.0 GHz, E5504 4C/4T 80 W 4 MB Cache Nehalem-EP

Disks 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 33.

RAID controller SAS6/IR

CD-ROM Read-only DVD that can read CD or DVD material for system upgrades. Item (a) in Figure 10 on page 33.

Memory 1066 MHz, 4 GB total (2 x 2 GB DIMM/single proc configuration)






Table 4 CTA-HA that is based on Dell 2950 (page 1 of 2)

Component FMA6-HA-APL FMA5-HA-APL

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 2U rackmount form factor with universal rails. Dimensions: 8.6 cm (h), 44.5 cm (w), 66.1 cm (d). Weight: 34 kg.

2U rackmount form factor with universal rails. Dimensions: 8.6 cm (h), 44.5 cm (w), 66.1 cm (d). Weight: 34 kg.

Power Dual redundant 750 watt hot-plug, power supplies.

Dual redundant 750 watt hot-plug, power supplies.

CPU Single Intel Xeon 2.33 GHz Quad Core processor with 1333 MHz front-side bus.

Single Intel Xeon 1.86 GHz Dual Core processor with 1066 MHz front-side bus.



Disks 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 33.

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 33.

RAID Controller 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.

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.

CD-ROM 24x IDE CD-ROM/DVD-ROM drive for system upgrades. Item (a) in Figure 11 on page 33.

24x IDE CD-ROM drive for system upgrades. Item (a) in Figure 11 on page 33.

Memory 4 GB, 533 MHz (4x1 GB), dual-ranked DIMMs.

4 GB, 533 MHz (4x1 GB), dual-ranked DIMMs.

Network Interfaces Two on-board gigabit 10/100/1000TX Ethernet copper ports with RJ45 connectors. Item (e) in Figure 7 on page 32.

Two on-board gigabit 10/100/1000TX Ethernet copper ports with RJ45 connectors. Item (e) in Figure 7 on page 32.


Standard VGA video connector for a system console. Item (a) in Figure 7 on page 32.

Keyboard Connector Standard USB keyboard connector for a system console. Item (d) in Figure 7 on page 32.

Standard USB keyboard connector for a system console. Item (d) in Figure 7 on page 32.

Mouse Connector Standard USB mouse connector for a system console. Item (c) in Figure 7 on page 32.

Standard USB mouse connector for a system console. Item (c) in Figure 7 on page 32.


Standard DB9 serial port for a serial-terminal system. Item (b) in Figure 7 on page 32.

Table 4 CTA-HA that is based on Dell 2950 (page 2 of 2)

Component FMA6-HA-APL FMA5-HA-APL

Appliance diagrams 31


Appliance diagrams These photographs illustrate configurations of the CTA and CTA-HA.

Figure 4 Rear view of Gen 7 appliance

Figure 5 Front view of Gen 7 appliance with bezel removed

Figure 6 Front view of the Gen 7 appliance with bezel



Figure 7 Rear view of Gen 5 or Gen 6 appliance

Figure 8 Front view of Gen 5 or Gen 6 appliance with bezel removed

Figure 9 Front view of the Gen 5 or Gen 6 appliance with bezel

Appliance diagrams 33


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



Port detailsModels CTA-APL, CTA-APL-HA, FMA7-APL and FMA7-HA-APL ship with two on-board ports enabled. Figure 12 on page 34 is a rear view of the appliance with the ports labeled.

Figure 12 CTA-APL, CTA-APL-HA, FMA7-APL and FMA7-HA-APL port details

Models FMA6-APL, FMA6-HA-APL, and FMA5-HA-APL ship with two on-board ports. Figure 13 on page 34 is a rear view of the appliance with the ports labeled.

Figure 13 FMA6-APL, FMA6-HA-APL, and FMA5-HA-APL port details

eth0 eth1 Disabled Disabled

CNS-001354

CNS-001259

eth1 eth0

Deploying the Cloud Tiering Appliance 35

3

This chapter contains the following sections:

Deployment process ...................................................................................................... 36 Supported platforms...................................................................................................... 37 Appliance setup.............................................................................................................. 38 Installing the virtual edition ......................................................................................... 39 CTA and CTA/VE for high availability ...................................................................... 43 Configuring CTA............................................................................................................ 44 Deploying CTA with Celerra or VNX ......................................................................... 47 Deploying CTA with NetApp ...................................................................................... 58 Deploying the CTA with a VNXe ................................................................................ 63 Deploying CTA with a Windows server..................................................................... 65 Deploying CTA with Isilon........................................................................................... 66 Deploying the CTA with a Data Domain.................................................................... 71 Configuring a NAS-based repository.......................................................................... 72 Deploying CTA with EMC Centera............................................................................. 73 Deploying CTA with Atmos......................................................................................... 75

Deploying the CloudTiering Appliance


Deploying the Cloud Tiering Appliance

Deployment processFigure 14 on page 36 illustrates how the EMC Cloud Tiering Appliance (CTA) or Cloud Tiering Appliance/VE is deployed for archiving.

.

Figure 14 Cloud Tiering Appliance deployment process

The top of the flowchart describes deploying the CTA or CTA/VE in various environments. For Celerra or VNX to NAS configuration, NAS repositories may be Celerra, VNX, VNXe, Windows, Isilon, NetApp, or Data Domain.

Supported platforms on page 37 lists the platforms supported for archiving and migration tasks.

Appliance setup on page 38 outlines the procedure to deploy a CTA or CTA/VE.

Steps in the five boxes at the bottom of the flowchart are performed by using the CTA GUI. Online help describes these steps in detail.

1. Install the CTA/VE, if applicable.2. Configure CTA networking.

CTA Setup

Celerra or VNX to NAS Configuration

Destination Configuration

Define Policies

Create Task

Run Policy Task

1. Configure ONTAPI.2. Configure vFilers, if applicable.3. Initialize recall services.4. Configure NetApp properties.

NetApp Configuration

1. Configure NAS repositories.2. Configure non-NAS repositories.

1. Create file matching expressionsand archive destinations2. Specify policy type, retention, delayedstubbing, stub retention (as applicable)

1. Create an archive, delete, or auxiliary task2. Select source (as applicable)

Run Simulation Task (Optional)1. Select Run Simulation Now2. Collect real-time results in CTA3. Review policy efficacy againstreal-time results

1. Determine optimal task scheduling2. Select archive conditions or starttimes (as applicable)3. Monitor archiving activity for errors

1. Configure Celerra or VNX properties.2. Initialize recall services.3. Configure name resolution for recall.4. Configure FileMover API.5. Configure DHSM.

Celerra or VNX to EMC Centeraor Atmos Configuration

1. Configure Celerra or VNX properties.2. Configure FileMover API.3. Configure DHSM.

CNS-001255

Supported platforms 37


Supported platformsPlatform support varies depending on the task performed.

Table 5 on page 37 shows platform support for multi-tier archiving.

Note: Celerra, VNX, VNXe, Windows, Isilon, NetApp, and Data Domain are collectively referred to as NAS repositories as described in Configuring a NAS-based repository on page 72. Data Domain is only supported natively as an NFS NAS repository.

Table 6 on page 37 shows platform support for file migration.

Table 5 Supported platform matrix for multi-tier archiving

Primary tier Secondary tier Tertiary tier

CelerraVNX

CelerraVNXVNXeWindowsIsilonNetAppData Domain

CelerraVNXVNXeWindowsIsilonNetAppData DomainEMC CenteraAtmos

CelerraVNX

Atmos none

CelerraVNX

EMC Centera none

NetApp CelerraVNXVNXeWindowsIsilonNetAppData Domain

CelerraVNXVNXeWindowsIsilonNetAppData DomainEMC CenteraAtmos

NetApp Atmos none

NetApp EMC Centera none

Table 6 Supported platform matrix for file migration

Source Destination

CelerraVNX

CelerraVNXVNXe

NetApp CelerraVNXVNXe



Appliance setupThe appliance arrives with the software installed. Before it may be used to perform tasks, the appliance and the software must be properly configured:

If a CTA is being deployed, port details that are used to connect the appliance to the network are provided in Chapter 2, Cloud Tiering Appliance Hardware and Port Configurations.

The CTA 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 89.

Software upgrades on page 90 provides instructions to perform a CD full upgrade or UPG upgrade.

If a Cloud Tiering Appliance/VE (CTA/VE) is being deployed, follow the instructions in Installing the virtual edition on page 39.

If a Cloud Tiering Appliance for High Availability (CTA-HA) or Cloud Tiering Appliance/VE for High Availability (CTA/VE-HA) is being deployed, CTA and CTA/VE for high availability on page 43 describes configuration considerations.

To install the appliance on the network, follow instructions provided in Configuring CTA on page 44.

If the system requires security hardening or any other special configuration, Chapter 5, Cloud Tiering Appliance System Settings,provides information for all system settings.

Then proceed to configure the appliance for your environment as described in:

Deploying CTA with Celerra or VNX on page 47

Deploying CTA with NetApp on page 58

Deploying the CTA with a VNXe on page 63

Deploying CTA with Isilon on page 66

Deploying CTA with a Windows server on page 65

Deploying the CTA with a Data Domain on page 71

Configuring a NAS-based repository on page 72

Deploying CTA with EMC Centera on page 73

Deploying CTA with Atmos on page 75

Installing the virtual edition 39


Installing the virtual editionThe CTA/VE and CTA/VE-HA are installed on the VMware server. Table 7 on page 39 shows the interoperability.

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 CTA/VE or CTA/VE HA 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.

For a CTA/VE, the zip file is: fmve-.zip

For a CTA/VE HA, the zip file is: fmve-_ha.zip

2. Open the Virtual Infrastructure (VI) Client.

a. To find the appliance with the most free space, consider %CPU and %Memory.

Table 7 VMware ESX Server interoperability

Virtual Appliance VMware ESX Server Comments

CTA/VE ESX 3.5 Update 3ESXi 3.5 Update 3ESX 4.0ESXi 4.0ESX 4.1ESXi 4.1

Four virtual CPUs, 4 GB of RAM, 512 GB of disk space, 2 gigabit virtual interfaces are reserved.

CTA/VE HA ESX 3.5 Update 3ESXi 3.5 Update 3ESX 4.0ESXi 4.0ESX 4.1

Four virtual CPUs, 4 GB of RAM, 100 GB of disk space, 2 gigabit virtual interfaces are reserved.



b. Select the line with the ESX server for the installation. A summary of the CPU, memory, and data store capacities appears.

Per the requirements of Table 7 on page 39, this ESX Server has enough CPU and memory available to install the CTA/VE.

3. Import the OVF file. Instructions differ depending upon VMware version.

For ESXi 3.5 Server, from the VI Client, select File > Virtual Appliance > Import.

Installing the virtual edition 41


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.



5. After answering a few basic questions, the summary screen appears. Validate the information and click Finish.

6. The import may take 330 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 CTA/VE will be configured for archiving in either of the following deployments:

from Celerra or VNX to EMC Centera

from Celerra or VNX to Atmos

Configure the single set of credentials for recall with the FileMover Settings as described in step 3 of Adding a Celerra or VNX to the CTA configuration on page 48. Then run ccdsetup or acdsetup as described in Configuring Celerra or VNX to EMC Centera or Atmos archiving on the CTA on page 50.

CTA and CTA/VE for high availability 43


CTA and CTA/VE for high availabilityHigh availability is a feature on both CTA and CTA/VE. Both the CTA-HA and the CTA/VE-HA deliver solutions for a redundancy, which ensure that clients do not experience data unavailability due to failure of the primary appliance.

When using CTA-HA or CTA/VE-HA for recall, callback services are configured on the appliance or the virtual appliance.

CCD is used to recall files from EMC Centera to Celerra and VNX

ACD is used to recall files from Atmos to Celerra and VNX

FPolicy callback is used to recall from all secondary devices to NetApp

No callback is used for any of the NAS repository types, such as Celerra, VNX, VNXe, Windows, Isilon, NetApp, or Data Domain when the source is Celerra or VNX.

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 appliances such as CTAs, CTA-HAs, CTA/VEs, or CTA/VE-HAs.

Celerra or VNX primary storageFor Celerra or VNX primary storage archived to an EMC Centera or Atmos, Data Movers resolve an HTTP fully qualified domain name (FQDN) to the IP addresses of the 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. Deploying CTA with Celerra or VNX on page 47 provides details on configuring Celerra or VNX Data Movers.

Run ccdsetup or acdsetup on all CTA-HAs or CTA/VE-HAs that will process recall requests from the Celerra or VNX Data Movers. These scripts link multiple appliances to process recall requests from a common set of Celerra or VNX Data Movers. Configuring Celerra or VNX to EMC Centera or Atmos archiving on the CTA on page 50 provides details on ccdsetup and acdsetup.

No additional appliances are involved in recall when the CTA or CTA/VE archives data from Celerra or VNX 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 storageNetApp filers allow FPolicy clients (such as CTA, CTA-HA, CTA/VE, or CTA/VE-HA) to register for callbacks in response to user access to files with specific attributes. When using the appliances, 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.

Run fpsetup on the CTA-HAs or CTA/VE-HAs 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 appliances that will register in the primary and secondary groups. Configuring NetApp archiving on the CTA on page 60 provides details on fpsetup.

Appliances are always involved in recall when the CTA or CTA/VE archives data from NetApp primary storage to any secondary storage location. NetApp filers do not recall data directly from Celerra or VNX, EMC Centera, or NetApp storage.

Note: A single CTA-HA or CTA/VE-HA can provide redundancy for multiple CTAs or CTA/VEs. A single CTA or CTA/VE can have multiple CTA-HAs or CTA/VE-HAs registered to provide redundancy. Do not use a CTA to provide redundancy for another CTA or a CTA/VE to provide redundancy for another CTA/VE.

Configuring CTABefore 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 a CTA or CTA-HA, connect the keyboard, monitor, and mouse to the appliance. The serial cable provided with the CTA and a HyperTerminal on a PC or laptop may be used. Connect the power cord and power on the appliance.

For a CTA/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.

The Rainfinity setup tool appears. This tool performs basic setup tasks that are not available through the CTA 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 CTA 45


Configuring the CTA networkTo configure the CTA 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 serverConfigure 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 = rsDomain =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.

3. Verify that the network configuration has been saved and network connectivity can be established properly.



Graphical user interfaceTo 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 interfaceAs an alternative to the GUI, you can use a command line interface to send commands to the CTA 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 82.

rssystat Displays statistics about the CTA.

Man pages for the command line tools are stored in the software installation directory. To access the man pages, type man command_name as in, man rssystat.

Deploying CTA with Celerra or VNX 47


Deploying CTA with Celerra or VNXTo use CTA with a Celerra or VNX Data Mover, first perform configuration steps on the CTA, and then on the Celerra or VNX Control Station.

Note: Celerra supports DART versions 6.0 or earlier. VNX supports DART version 7.0 or later.

Prerequisites for using Celerra or VNX as a file migration source or destination To migrate files to or from a Celerra or VNX Data Mover, ensure that the following conditions are satisfied:

For NFS, CTA has root access with read/write permission on source and destination exports.

CIFS user has local administrator access on all source and destination shares.

If migrating files from a source that is shared and exported, CTA has root access with read/write permission to both shares and exports.

Snapsure snapshots are enabled on the source.

There is a system user for the XML API setup on the Celerra or VNX Control Station. Step 2 on page 54 describes how to set up the user.

For every server, properties are configured on the CTA for:

Control Station IP address

NDMP username and password

Adding a Celerra or VNX to the CTA configuration on page 48 provides details on configuring a Celerra or VNX server.

Prerequisites for Celerra or VNX as an archive sourceTo archive data from a Celerra or VNX Data Mover, the CTA requires access to the FileMover API (TCP port 5080).

To archive NFS data, the CTA needs the following:

Mount v3 RPC service

NFS v3 RPC service

NLM v4 RPC service

Root access with read/write export permissions for all NFS data that will be archived.

To archive CIFS data, the CTA needs SMB over NetBIOS (TCP port 139).

Direct command line access to the Celerra or VNX Control Station is not used by the CTA.



When configuring Celerra or VNX Data Mover properties on the CTA, 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) The NetBIOS name of the filer.

(For CIFS archiving only) Credentials for local administrator access through CIFS.

Adding a Celerra or VNX to the CTA configuration

Note: The VNX Properties page is not displayed. The configuration process is the same as for the Celerra. To add a VNX, follow the instructions for Celerra, substituting VNX for Celerra throughout.

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.



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 tasks on the Celerra or VNX Control Station for file migration or archiving on page 52.

4. Specify the following for the Celerra Data Mover:

Basic File Server Information Type the Celerra name. 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 Type the IP address of the Celerra Control Station. This is required for all source Celerra servers. It is not required for destination Celerra servers. In file migration transactions, it is used to create a snapshot of the source. It also allows the CTA to automatically perform some prerequisite tasks for archiving as described in Configuring automatically created DHSM connections for file migration or archiving on page 54. If this field is empty, the CTA takes no action and the prerequisite tasks 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 administrators group on the Celerra. Windows domain user on page 116 provides more information.

Note: The CIFS credential is not required if the Celerra performs only NFS archiving.

NDMP Specific Settings For file migration, type the username and password for an NDMP user on the source and destination servers. By default, the port for NDMP traffic is 10000.

To create an NDMP user on a Celerra Data Mover, log in to the Celerra Control Station as root, and type:

/nas/sbin/server_user -add -md5 -passwd

where data_mover is the name of the source or destination server, and user is the username for login. The command will prompt for a password.

Celerra as Source This option configures the CTA to archive data from the Celerra Data Mover. If multiple appliances are connected to the same Celerra Data Mover, only one appliance should be configured with the Celerra as Source. This option is required only if the Celerra is serving as a source for archiving.



CAUTION!Multiple appliances may be configured to archive data from a single Celerra Data Mover, but only one CTA or CTA/VE should 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.

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 that use scanning. Migration tasks do not scan, so this setting does not apply to file migration. The CTA ignores all system directories such as, etc, lost+found, and ckpt by default.

CAUTION!Verify that stub files are not in the excluded directories. CTA will not access the excluded directories and the stub files will become orphans.

5. Click Commit to define the Celerra file server.

Configuring Celerra or VNX to EMC Centera or Atmos archiving on the CTATo archive from a Celerra or VNX to an EMC Centera or Atmos, configure the callback service so that the CTA is in the recall path.

Configure the callback service to recall from EMC CenteraTo configure recall from the EMC Centera:

1. From the console on the CTA, log in as root.

2. Type ! to escape to the command line and type:

ccdsetup 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 a CTA-HA, 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 CTA.

If an invalid IP address is provided, the CCD.log file located in /var/log/rainfinity/filemanagement/recall 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 callback service to recall from the AtmosTo configure recall from the Atmos:

1. From the console on the CTA, log in as root.

2. Type ! to escape to the command line and type:

acdsetup 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 a CTA-HA, 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 ACD.log file located in /var/log/rainfinity/filemanagement/recall 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 name resolution for archivingWhen the Celerra or VNX 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.

Note: These instructions pertain only to configuring the hosts file on the Celerra or VNX. Do not manually edit the hosts file on the CTA as this can later result in data access problems.

To use local hostname resolution:

a. Log in to the Celerra or VNX Control Station as root and mount the Data Mover to edit the local hosts file with vi:

mount server_2:/ /mnt/sourcecd /mnt/source/.etcvi hosts

where server_2 is the name of your Celerra or VNX Data Mover.

b. Edit the hosts file to add one line for each appliance, similar to the following example:

10.0.0.1 # CCD on CTA-HA10.0.0.2 # CCD on CTA10.0.0.3 # CCD on CTA/VE10.0.0.1 # ACD on CTA-HA10.0.0.2 # ACD on CTA10.0.0.3 # ACD on CTA/VE

where:

rainccd.domain is the FQDN that will be used to create the HTTP DHSM connection described inCelerra Callback Agent Settings on page 50.

rainacd.domain is the FQDN that will be used to create the HTTP DHSM connection described in Atmos Callback Agent Settings on page 50.



c. Save the file and confirm that the Celerra or VNX Control Station is not mounted to the Data Mover:

cd ~umount /mnt/source

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.

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 or VNX FileMover supports DNS HA failover. If the DNS server resolves the callback daemon hostname to multiple IP addresses, the Celerra or VNX FileMover transparently switches to the server at the next available IP address.

Prerequisite tasks on the Celerra or VNX Control Station for file migration or archivingIf a Celerra or VNX has not been configured as a source for file migration or archiving, perform the following steps:

1. Enable filename translation on the Celerra or VNX Control Station.

The CTA, CTA-HA, or CTA/VE expects that all filenames are derived from the Celerra or VNX Network Server in UTF-8 format. To preserve filenames correctly:

a. Log in to the Celerra or VNX 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:

::::8859-1.txt: Any thing that didnt match above will be assumed to be latin-1



Add the following line immediately above the last line:

::CTA_IP_ADDR::: CTA requires no translation (UTF-8)

where CTA_IP_ADDR is the IP address of your appliance.

For example, if the IP address is 10.10.18.1, add:

::10.10.18.1::: CTA requires no translation (UTF-8)

To specify a subnet, add:

::10.10.18.0,255.255.0::: CTA requires no translation (UTF-8)

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 CTA_IP_ADDR -mover ALL

where CTA_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 or VNX Control Station CLI as root and type the command:

/nas/sbin/server_user -add -md5 -passwd

For example: /nas/sbin/server_user server_2 -add -md5 -passwd rffm

The username and password must match the FileMover settings configured on the CTA in Step 3 on page 48.

3. Allow the IP addresses of the CTA or CTA/VE to open connections to the FileMover interface. While logged in to the Celerra or VNX 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 -append dhsm -users -hosts

For example: server_http server_2 -append dhsm -users rffm -hosts 192.168.0.100,192.168.0.101,

Note: A single Celerra or VNX Data Mover can be configured as an archiving source with multiple appliances, but more than one CTA or CTA/VE should never be used to archive data from a single filesystem.

4. Enable DHSM (FileMover) for the Data Mover. To enable DHSM and keep it enabled if the Data Mover reboots, run the following command once:

server_http 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 -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 | 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 -offline_attr on

Note: Once the offline attribute is set to on, it must remain on or CTA 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

docu34939 cloud tiering appliance and cloud tiering appliance ve 7.5 getting started guide

Documents

cloud tiering appliance

appliance diagrams

appliance setup

emc software

emc powerlink

emc corporation trademarks

cta implementation

publication date