HP File Migration Agent Administrator's Guide

HP Software

File Migration Agent (FMA

)

Installation and Administration Guide

Published: July 2009

Legal Notice

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Export of the information contained in this publication may require authorization from the U.S. Department of Commerce.

Microsoft, Windows, Internet Explorer, Notepad, and all Windows-based trademarks are either trademarks or registered trademarks of Microsoft Corporation.

Mozilla and Firefox are registered trademarks of the Mozilla Corporation.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc.

Other product and company names may be the trademarks of their respective owners.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Typographical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix

1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Cluster operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

FMA components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Creating a technical user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Configuring backup management applications to work with FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Ensuring interoperability with FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Backing up managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Backing up archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Restoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installing FMA on file servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Minimum requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Technical user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Operating system version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

First steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing FMA in a cluster configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Evicting a node from a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Adding a new node to a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configuring FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Upgrading FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Migrating a Windows 2003 cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Downgrading FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Uninstalling FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Removing the Explorer plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Enter FMA license keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

FMA licensing problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Contents | iii

4 Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Primary and secondary configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Storage descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Ignore Security and Data Stream Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Ignore System Name and Ignore Volume Serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Viewing archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Adding archives to FMA in a cluster environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Creating CIFS archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Preparing CIFS archives for FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring CIFS archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Creating FTP archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Preparing FTP archives for FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Configuring FTP archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Using FmaFileUtil to work with FTP archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Creating HP Integrated Archive Platform archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Preparing IAP archives for FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Configuring IAP archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Editing archive properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Deleting archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Removing deleted files from archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

5 Managed Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Viewing managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Creating managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Releasing files using disk space policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Setting disk space watermarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Setting retention periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Excluding files from release based on disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Migrating and releasing files using file policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Creating file policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Scheduling file policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Editing file policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Enabling and disabling file policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Deleting file policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Migrating and releasing files with the Explorer plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Recalling files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Moving files to another managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Moving a small number of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Moving a large number of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Stopping volume management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Restarting volume management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Removing volume management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

iv | Contents

6 Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Create a new HP StorageWorks File Migration Agent (FMA) archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

FMA archive configuration for a Windows FTP archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

FMA archive configuration for an Linux FTP archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

FMA archive configuration for a CIFS-based NAS device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

FMA archive configuration for IAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Create a new managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Create file policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Create disk usage monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Determine FMA software version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Migrate files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Release files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Recall files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Set a high-watermark for migration or releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Verify data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Schedule FMA commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Schedule FMA jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Backup/restore concept for FMA managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Relocating data to another FMA managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Relocating data procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Relocating a large number of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

A Command Line Interface Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

FMA commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

erase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

rsa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

verify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

B Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Accessing FMA log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

FMA log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

FMACLI log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Windows event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Troubleshooting installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Troubleshooting configuration issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Troubleshooting connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Troubleshooting common issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Troubleshooting third-party application issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Troubleshooting cluster systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Contents | v

C Third-party Product Compatibility List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Anti-virus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Symantec AntiVirus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

McAfee VirusScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Sophos Anti-Virus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

ServerProtect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

eTrust AntiVirus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

TrendMicro OfficeScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Backup/restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

BackupExec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

BrightStor ArcServe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Networker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

NetVault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

MS VSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Galaxy Backup & Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Quota/encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

StorageExec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Defragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

O & O Defrag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

MS Defragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

IndexServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

MS IndexServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

HP Storage Mirroring Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Mirroring and Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Failure monitoring and failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Supported Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Script creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

D Error Codes and Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

vi | Contents

Preface

Welcome to the File Migration Agent Installation and Administration Guide. This guide provides the

information required to install and work with File Migration Agent (FMA

FMA enables systematic migration of inactive and rarely used data on Windows file servers to Hierarchical Storage Management (HSM) systems or other Network Attached Storage (NAS) devices. Before migration is enabled, an FMA user must define the volumes to be managed and the archives where data will be stored.

About this guide

The File Migration Agent Installation and Administration Guide is designed to help you install, configure, and work with FMA. The chapters are include information about product functionality and use, planning and performing installation, creating and managing archives, managing volumes and moving files between managed volumes and archives, using the Command Line Interface (CLI), and troubleshooting.

Audience

This guide is designed for use by anyone deploying FMA. Users should be familiar with the file servers that will be managed in order to effectively create migration policies. Familiarity with system and network configuration is highly recommended.

Preface | vii

Typographical conventions

This guide uses the following typographical conventions:

Convention Description

Bold Used for file names, field names, URLs, interface elements that are

Bold Italic Represents variables within file names, command syntax, URLs, or

Italics Used for emphasis, book titles, and variables.

Monospace Used for output text, command names and arguments (syntax), code,

Monospace Italic Represents variables within command syntax, code, or command-

Blue Text Used for cross-references.

Support

For service and support assistance, contact your authorized service and support representative directly.

• For technical assistance with an evaluation version of FMA, contact your sales representative.

• For technical assistance with a registered version of FMA, contact HP Support for support of this

product.

• **ADD standard HP support contact**

Subscription service

HP strongly recommends that customers sign up online using the Subscriber's choice web site:

http://www.hp.com/go/e-updates

• Subscribing to this service provides you with e-mail updates on the latest product enhancements, newest

versions of drivers, and firmware documentation updates as well as instant access to numerous other

product resources.

• After signing up, you can quickly locate your products by selecting Business support and then Storage

under Product Category.

viii | Preface

Support

You can visit the HP Software Support web site at:

http://www.hp.com/go/hpsoftwaresupport

HP Software Support Online provides an efficient way to access interactive technical support tools. As a valued support customer, you can benefit by using the support site to:

• Search for knowledge documents of interest

• Submit and track support cases and enhancement requests

• Download software patches

• Manage support contracts

• Look up HP support contacts

• Review information about available services

• Enter into discussions with other software customers

• Research and register for software training

Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract.

To find more information about access levels, go to:

http://h20230.www2.hp.com/new_access_levels.jsp

For more information about HP Passport, go to:

http://h20229.www2.hp.com/passport-registration.html

When calling support:

Collect the following information before calling:

• Technical support registration number (if applicable)

• Product serial numbers

• Product model names and numbers

• Error messages

• Troubleshooting package (If further investigation is needed to resolve an issue. Please provide the

troubleshooting package to support. See

from your system.)

Troubleshooting on page 123 on how to obtain this package

Preface | ix

x | Preface

Overview

File Migration Agent (FMA) offers a technologically innovative approach to data management by maintaining active files on high-performance primary storage while archiving inactive files on cost-effective secondary storage. FMA does not require changes to the current directory structure and integrates seamlessly into the existing IT infrastructure. FMA only manages files on specified volumes on the file server defined as managed volumes.

FMA is a Windows-based solution that copies, or migrates, inactive or rarely used data to archive storage systems such as Content Addressed Storage (CAS) systems, Hierarchical Storage Management (HSM) systems, or Network Attached Storage (NAS) devices. Migrated files can subsequently be released so that only a stub file (a data file that stands in for the original file) remains on the file server while the full file resides on the archive storage system. FMA recalls the file from the archive whenever it is needed on the file server.

Migration, release, and recall processes are transparent to Windows users and applications, which can continue to access files as if the files were still on the file server. Migrating and releasing files manages the growth and complexity of Windows file servers, freeing space for active data.

FMA administrators define the conditions under which files on managed volumes are migrated or released. The administrator can create policies to migrate and release files based on properties such as the file extension or timestamp. The administrator can monitor the space on a managed volume and automatically release migrated files based on a retention time period when a configurable watermark is reached.

Migration

During the migration process, FMA adds FMA-specific metadata to a managed file on a file server and copies the managed file to one or more archives. FMA supports the following:

• Common Internet File System (CIFS), for Windows-based archives

• File Transfer Protocol (FTP), for Linux-based archives

• HP Integrated Archive Platform (IAP), for IAP archives

Although files can be migrated manually, FMA administrators typically create policies to define the conditions under which files are migrated. Policies can migrate files based on file name; file age in relation to creation, modification, or last access time; or a minimum file size. They can exclude files from migration based on file name or file attributes, such as hidden files. Policies can be run manually or scheduled to run at regular intervals.

Administrators can apply any number of policies to each managed volume. Policies set in the root folder apply to all files in the entire volume. Policies set at the folder level are valid for the files in that folder and its subfolders.

After migration, FMA verifies that the file size and timestamp of a file on the file server and the file on the archive are identical.

For information about migrating files, see Managed Volumes on page 45.

Release

Recall

During the release process, FMA replaces a migrated file on a file server with a stub file. FMA marks this stub file as offline, which designates files that have remote data.

Although files can be released manually, FMA administrators typically set disk space policies, which are watermark levels that monitor available disk space on managed volumes. When a managed volume reaches its high watermark, FMA evaluates the retention policies for the volume and begins releasing files that match the policy criteria. FMA stops releasing files when it reaches its low watermark. If the critical watermark is reached, files are released independently of the retention policies. Retention policies are related to elapsed time since last access or modification to a file. For information about these watermarks, see

Releasing files using disk space policies on page 48.

Before a file can be released, it must be migrated with at least one valid copy in an archive and it must be larger than 1024 bytes. Because releasing locks files exclusively, files that cannot be opened exclusively cannot be released and remain on the file server. Files can also be released according to user-set policies regarding the number of archived copies existing for each file.

For information about releasing files, see Managed Volumes on page 45.

When a user or application accesses a released file to read it or write to it, FMA intercepts the read or write request and retrieves the file data from the archive. If one archive is not available, FMA attempts to find the file in other archives where the file was also migrated. If FMA cannot recall a file from any of the archives, it returns an error.

Files can also be manually recalled explicitly by using the FMA command line interface, or by using the Window Explorer plug-in.

For information about recalling files, see Managed Volumes on page 45.

2 | Overview

Cluster operation

When running on a Microsoft Cluster Server, an instance of FMA is installed and running on each node. Two of the FMA services are concurrently active on all nodes. The Active File Management (AFMSvc) and the Volume Manager (HsmSvc) run concurrently on each node to handle file migrations and recalls on any managed volumes that might be active on those nodes. A third service, the Configuration service (HsmCfgSvc), runs only on the node currently hosting the cluster group resources. Its activation is tied to and controlled by the cluster group.

For a given volume, the policy information is stored at the root level of the volume in the “HSM Volume Information” system directory. Because this information is stored on the volume, policy information for the volume is available when the volume is moved or fails over to another node in the cluster. When this volume appears on the new node where FMA is running, a new file system filter instance is attached to the volume and an instance of the volume manager is started for this volume. The volume manager is then able to read the policy information and carry on management of the volume on the new node.

Archive configuration is considered a global resource and is controlled by the Configuration service. Although archive configuration is accessible from all nodes, the policy referencing the archive must be edited from the node where the volume is currently active. When installing or managing FMA in a Microsoft Cluster Server, be aware of the cluster-specific instructions in chapters 2-5.

FMA components

The following FMA interfaces and utilities are available:

User interface

Use the FMA user interface to perform most tasks related to managed files or volumes. The user interface is seamlessly integrated into Microsoft’s Management Console (MMC) and its use is documented throughout this guide. To access the FMA user interface, select All Programs→HP StorageWorks File Migration Agent→FMA Configuration from the Windows Start menu.

You can also access the FMA user interface from the Computer Management window or the Server Management window, depending on the operating system. For the 32-bit version of Server 2003, the File Migration Agent section is listed in the Storage section of Computer Management. For the 32-bit version of Server 2008, the File Migration Agent section is listed in the Storage section of Server Manager.

Explorer plugin

Use the Explorer plugin on the file server to manually migrate, release, and recall managed files from Windows Explorer. To view the FMA properties of a file using the Explorer plugin, rightclick on a file (in a managed volume) in Windows Explorer, select Properties, and then select the FMA tab. For more information about using the Explorer plugin, see Migrating and releasing files

with the Explorer plugin on page 56.

Command line interface

Use the FMA command line interface (FMACLI) to work with managed files. While most functions are available from the FMACLI, tasks such as creating managed volumes must be performed in the user interface.

When running HP FMA on a 64-bit Windows Operating System, the Explorer plug-in is only available for the 32-bit MS Explorer version. In order to use the FMA plug-in on a 64-bit OS, the following command must be manually run:

%windir%\syswow64\explorer /separate

For details about the FMACLI, see Command Line Interface Reference on page 81.

Overview | 3

FMAFileUtil

Use FMAFileUtil to manually retrieve and store data on FTP-based archives. For details about this utility, see Using FmaFileUtil to work with FTP archives on page 37.

4 | Overview

Installation

This chapter describes the tasks you must perform to install File Migration Agent (FMA). These tasks include the following:

1. Create the technical user required by the FMA service.

2. Configure backup management applications to ensure that data on file servers continues to be backed up

as expected.

3. Install FMA on each file server with files that you want to manage.

4. If you are installing in a Windows cluster environment, run the FMA cluster configuration wizard.

In addition, this chapter contains information about FMA license keys, upgrading FMA, downgrading FMA, uninstalling FMA, and removing the Explorer plugin.

Note To install, use the FMA components, or uninstall FMA, the login user account must have

Administrator privileges.

Note

Ensure there is no unsupported third-party applications installed on the file server.

Creating a technical user account

FMA can run processes using a technical user account. Before you begin, create a Windows user account with Full Control permissions, including permissions to start, stop, and pause services. Specifically, FMA uses the technical user to migrate data to Common Internet File System (CIFS) archives. To maintain FMA access to the files it manages, the password for this technical user account should never change or expire. If a password change is required, the password must be updated on every archive accessed by FMA.

In a cluster environment, a domain user is typically used to run FMA processes.

Configuring backup management applications to work with FMA

Managed volumes and archives must be backed up regularly. FMA is an archiving solution and does not replace the current backup solution.

Refer to the File Migration Release Notes for a list of supported backup management applications and their limitations with FMA.

Ensuring interoperability with FMA

To ensure proper interoperability with FMA, the backup management application must back up and restore the following file information:

• Unnamed data stream (actual file data)

• Proper sparse-file handling

• Access control list (file security)

• Alternate data streams

• Reparse point information

• NTFS object-id

• File attributes, such as offline and sparse

In addition, keep the following in mind when performing backups:

• The backup management application must open files using the FILE_FLAG_OPEN_NO_RECALLS

and FILE_FLAG_BACKUP_SEMANTICS options.

• The backup management application must use the WIN32 BackupRead and BackupWrite functions.

• The backup management application must not make changes to the last access timestamp of scanned or

backed up files.

• Backing up files on managed volumes using network shares triggers recalls.

Backing up managed volumes

Backup management applications use different criteria when selecting candidates for incremental backup. Changes to parameters such as file size, modification date, or file attributes can trigger a backup.

Some applications monitor the reparse attribute for a file. If this attribute has changed since the last backup, the application backs up the file again. These applications should back up files incrementally. Currently, IBM Tivoli Storage Manager is the only supported backup management application that should use only incremental backups.

Other applications monitor the modification timestamp and file size. For these applications, FMA operations are transparent. Configure these backup management applications to run a weekly full backup with daily incremental backups. As files are released, periodic full backups include stub files rather than full files. This reduces the size of backups but requires that the archive be backed up reliably.

Backing up archives

Archive files must be backed up as well. Because these are always full files, they do not have the same restrictions as the managed volume backups. However, for CIFS backups, use the following guidelines:

• Run weekly full and daily incremental backups on the managed volumes and CIFS archives at the same

time.

• For performance reasons, run incremental forever backups on the CIFS archives.

6 | Installation

• Do not migrate or release files during the backup window to ensure that the backups of the managed

volumes and CIFS archives are synchronized and consistent.

• As a best practice, create two archive copies when using CIFS archives.

• FMA archive cleanup expiration time must be greater than the backup retention time. For information

about cleanup, see

• Ensure that a replica of a file is backed up before that file is released from the managed volume.

Removing deleted files from archives on page 44.

Restoring data

If you must restore a backup of a file or folder, you should copy and paste the current file or folder to a new location and then restore the file or folder to the original location. FMA does not support file activation for files that have been restored to a new location. Restoring files is only supported to their original location.

Installing FMA on file servers

Prerequisites

Minimum requirements

• A server that meets the minimum hardware requirements shown in the HP FMA 2.5 Release Notes

document.

• An additional hard disk drive(s).

Technical user

The FMA service needs to run under a user account (for example, FMAUser) with the following privileges:

• Backup files and directories.

• Restore files and directories.

• Take ownership of files or other objects.

• Network access.

• Other things to consider about technical users:

• Password must not expire.

• Password should not be changeable by the user.

Note The user must have the appropriate access rights (“FULL CONTROL”) on the NAS devices, which

are used as backend data stores. Create the FMA technical user account before starting the installation procedure. A wizard is launched during the installation for setting up the technical user.

Operating system version

The 32 and 64-bit versions of the following operating systems are supported for file servers and for CIFSbased NAS archives:

• Microsoft Windows Server 2008 Standard, Enterprise, and Datacenter Editions

• Microsoft Windows Server 2003 SP2 Standard and Enterprise Edition

• Microsoft Windows Server 2003 R2 SP2 Standard and Enterprise Edition

• Microsoft Windows Storage Server 2003 Standard and Enterprise Edition

Installation | 7

• Microsoft Windows Storage Server 2003 R2 SP2 Standard and Enterprise Edition

• HP Windows Unified Data Storage Server (WUDSS) 2003

• Microsoft Windows Server 2003 R2 NFS server with the following restrictions:

• Windows can only handle paths with a maximum length of 260 characters.

• UNIX and Windows systems use different user and group IDs. Therefore, there needs to be a corresponding set of user and group IDs on the UNIX system to the Windows system.

• Window components “Services for Unix” and “User mapping” components is required for NFS sharing of the source volume(s)

• When files with the same name but different capitalization (such as temp1, Temp1, and TEMP1) are saved in the same directory, the Win32 subsystem recognizes only one of them. FMA and other Windows applications can only access one of these versions, and it is not possible to determine which version will be retrieved.

Compatibility issues

Before installation, please review Third-party Product Compatibility List on page 135. Software which is not on the list is not supported and needs to be removed from the FMA server before installation.

Restrictions

The following features are not part of this FMA version:

• No continuous migration and release.

• No event-driven migration and release.

• No built-in disaster recovery function. Regular backups of the managed file system are required. (See

Third-party Product Compatibility List on page 135.)

• The system volume cannot be managed by FMA.

• No support for multiple generations of files.

• No load balancing for recall between different archives.

• A monitor resolution of at least 1024 x 768 pixels is required.

• FMA can not manage a cluster quorum disks.

• For restrictions on third-party applications see Third-party Product Compatibility List on page 135.

First steps

When using the FMA for the first time, the following procedures must be executed:

1. Install the backend archive (CIFS, IAP, or FTP).

2. Create a technical user for the File Migration Agent service. Collect information about the data storage

3. Install FMA. For further information about the FMA installation, see Installing FMA on file servers on

4. Configure at least one FMA archive using the FMA MMC Snap-In. For further information about the

5. Configure the managed volumes using the FMA MMC Snap-In. For further information about the FMA

8 | Installation

(user ID, IP address, and so on).

page 7, Installing FMA in a cluster configuration on page 14, and Upgrading FMA on page 17.

FMA archive management, see

volume management, see

Archives on page 25.

Managed Volumes on page 45.

6. Configure file policies and schedules on the managed volumes using the FMA Policy Manager (see

Migrating and releasing files using file policies on page 51).

7. Configure the watermarks and retention periods for disk space monitoring of the managed volumes using the FMA Policy Manager (see

Releasing files using disk space policies on page 48).

You must install FMA on each file server to be managed. During this installation process, the following folders are created the FMA installation folder, which by default is C:\Program Files\Hewlett-Packard\HP FMA\.

• bin—Program files and binaries

• doc—Documentation

• log—FMA log files

• templates—Policy templates

If you are working in a cluster environment, see Installing FMA in a cluster configuration on page 14.

To install FMA

1. Close all applications running on the file server.

2. Run setup.exe to start the installation wizard. This file is available on the installation CD.

The Welcome dialog box is displayed:

3. On the Welcome dialog box, click Next. The License Agreement dialog box is displayed:

Installation | 9

4. On the License Agreement dialog box, read the agreement, select whether to accept it, and click Next. You cannot continue with installation unless you accept the license agreement.

The Destination Folder dialog box is displayed:

5. On the Destination Folder dialog box, choose the location where to install FMA.

• To install in the default location, click Next. This is recommended.

• To install in a different location, click Change, select a new location in the dialog box, and then

click Next in the wizard.

10 | Installation

The Setup Type dialog box is displayed:

6. On the Setup Type dialog box, choose whether to install all features or select features.

• To install all features, which is recommended, click Next.

• To install select features or if you are installing in a Windows cluster environment, select Custom

and then click Next. The Custom Setup dialog box is displayed:

Click the icon on the Custom Setup dialog box next to the files you do not want to install. To install these files in a location other than the default location, click Change and select a new location in the dialog box. Then, click Next.

Note

If you are installing in a Windows cluster environment, do not select HSM Explorer Extension. This feature (the Windows Explorer plugin) can be installed after FMA

configuration is complete.

Installation | 11

The wizard installs FMA.

Then, the Technical user dialog box is displayed:

7. On the Technical user dialog box, provide information about the technical user you set up for the FMA

12 | Installation

service. For more information about this account, see

Creating a technical user account on page 5.

If you select LocalSystem account, FMA uses the local ID named system to run processes.

To specify a technical user, complete these steps:

a. Select This account and type the name of the account.

b. In the Password and Confirm password fields, type the account password.

c. Click Next.

The Grant Permissions dialog box is displayed:

8. Click Ye s to confirm you want to grant permissions to the technical user.

9. Click Next on the Wizard Summary dialog. The completion dialog box is displayed.

10. Click Finish.

Installation | 13

Installing FMA in a cluster configuration

If you are installing FMA on a Microsoft cluster system, you must perform additional configuration steps.

FMA supports clusters based on Windows Server 2003 and 2008. Consult Microsoft documentation for help in determining the best cluster configuration for the application. The following quorum modes are supported by FMA and the installation instructions are the same for all cases:

• Server 2003

Standard Quorum—All nodes use a common disk to store the cluster information.

Majority Node Set (MNS)—All nodes store a copy of the cluster information and there is no shared disk quorum resource.

• Server 2008

Node Majority—This is similar to MNS for Server 2003.

Node and Disk Majority—This is used when there are an even number of nodes for a single site cluster and there is a single shared disk resource.

Node and File Share Majority—This is used when there are an even number of nodes and the shared disk resource is a file share that enables nodes from remote sites to access the quorum data.

No Majority—This is similar to Standard Quorum for Server 2003.

When you work with a cluster environment, consider the following:

• FMA must be installed on every node.

• All cluster nodes must be running and the cluster system must be fully operational before installing and configuring FMA. For a Server 2008 cluster, run the Validate a Configuration Wizard before installing FMA. All issues must be resolved before installation of FMA.

• When deploying FMA on an MNS multi-site cluster, ensure that the replication tool maintains exact duplicates of production disks at the recovery location.

If you want to migrate a Windows 2003 cluster that includes FMA to a Windows 2008 cluster, see Migrating

a Windows 2003 cluster on page 18.

To configure FMA in a cluster environment

The Active/Active and Active/Passive configuration have different configuration steps in the cluster environment, refer to

The following steps are for the Active/Passive cluster configuration:

1. Install FMA on each cluster node, following the steps in Installing FMA on file servers on page 7.

Note In cluster environments, the FMA configuration service runs on one node only. This service is

not started until all steps in this procedure are completed. The FMA migrator service should only run for seven minutes when the configuration service is not running. Therefore, if step 1 takes longer than seven minutes to complete for ALL nodes, HP recommends rebooting all nodes prior to completing step 2.

2. Launch the FMA cluster wizard on any cluster node to configure the FMA configuration service as a cluster resource in the default cluster group.

From the Start menu, select All Programs→HP StorageWorks File Migration Agent→FMA Cluster Setup.

3. On the Cluster Setup dialog box, click Next.

To create an Active/Active Cluster configuration on page 15 for more information.

14 | Installation

4. On the Cluster Setup dialog box, select the account to use to run processes and click Next. In a cluster environment, a domain user is typically used to run the FMA Configuration process. If you do not want to create a new user for this process, you can select Localsystem account.

5. On the Cluster Setup dialog box, select Cluster Group and click Next.

6. On the next Cluster Setup dialog box, enter a resource name and brief description and click Next.

7. On the Wizard Summary dialog box, click Finish.

8. Use the Windows cluster administration tools to view the status of the cluster group and the FMA service that was just created. The cluster group should be online and contain the FMA configuration service that was just created.

9. Move the cluster group to all nodes of the cluster and verify that it comes online in each case. Manually Start the management of managed volume(s) on each node after verifying the cluster group is online. Moving the cluster group is different depending on whether the system is based on Server 2003 or 2008.

• Server 2003

In the cluadmin application, right-click the default cluster group and select Move.

• Server 2008

Enter the following command at a command line prompt:

cluster . group "Cluster Group" /move:Node

where Node is the destination for the move.

For information about adding archives in a cluster environment, see Adding archives to FMA in a cluster

environment on page 28. See Creating managed volumes on page 47 for information about adding volumes

in a cluster environment.

To create an Active/Active Cluster configuration

The Active/Active configuration requires a few additional steps to configure compare to the Active/Passive configuration.

1. Create an Active/Passive configuration using the steps provided in To configure FMA in a cluster

environment on page 14.

2. Open the Cluster Administrator. The Cluster Administrator is a tool to enable creating and controlling cluster configurations. To open the Cluster Administrator:

• Open a new command window by clicking Start → Run. Enter cluadmin.

• Open the control panel by clicking Start → Settings → Control Panel. Open Administrative

Tools and then Cluster Administrator.

Installation | 15

3. Create a new Cluster Group for the resources to be allocated to the secondary Active node.

a. Click Add New Resources. Add the new Physical Disk to the new Cluster Group you have created.

b. Move the Cluster Group with all its resources to the appropriate active node by right clicking over

the selected group and selecting Move Group.

Note All drive letters or resource names in the cluster resources must be unique. Drive letters or

resource names cannot be used more than once. If you have identical drive letters or resources, they will not failover to the another node because it already contains the same drive letter. If the disk drive does not failover to another node during failure, it will not be managed by FMA.

4. Log on to the secondary active node and verify the resources have come online.

a. Open the control panel by clicking Start → Settings → Control Panel.

b. Open Administrative Tools and then Computer Management.

c. Expand Service and Applications, and select Services.

d. Examine the list for HP StorageWorks File Migration Agent config service. The startup type

should be Manual, and the two other FMA services should already be in Started status.

e. Right click the HP StorageWorks File Migration Agent config service and select Start to make

this an active node.

5. Bring up the FMA configuration, and manage your new volumes as described in Chapter 5, Managed

16 | Installation

Volumes. You can now configure your archives and file policies.

Note During failover, your cluster resources failover to the other active node, or to a passive node

depending on configuration.

Evicting a node from a cluster

To uninstall FMA from a node that has been evicted from a cluster, follow these steps:

1. Evict the node using Windows cluster administration tools.

2. Uninstall FMA from the evicted node. Follow the instructions (To uninstall FMA from a single file

server on page 20) for uninstalling FMA from a single server.

3. Return to a node that is still a member of the cluster and run the FMA Cluster Setup wizard. Select Ye s on the first dialog to allow the wizard to reconfigure the cluster and then click Next for the remainder of the dialogs.

Adding a new node to a cluster

If you want to add a new node to a cluster that is already running FMA, follow these steps.

1. Ensure the new node has access to all cluster disks.

2. Add the new node using Windows cluster administration tools.

3. Install FMA on the new node. The new node must already be a member of the cluster before installing FMA so that the installer completes the necessary cluster based configurations.

4. Go back to one of the other nodes in the cluster and run the FMA Cluster Setup wizard (select All

Programs

dialog and then click Next on the remaining dialogs. Verify that the wizard shows all nodes that are expected to be in the cluster on the final dialog.

→HP StorageWorks File Migration Agent→FMA Cluster Setup). Select Ye s on the first

5. Move the cluster group to the new node and verify that the FMA Configuration service comes online. Refer to the information (

6. Move all disk resources that are managed by FMA on this cluster to the new node.

7. Open the FMA configuration user interface and add the managed volumes to FMA management on the new node. Refer to

Configuring FMA

After you install FMA on file servers, you must set up the archives to store data and the managed volumes that FMA will manage. For information about archives, see managed volumes, see Managed Volumes on page 45.

To view the user interface for configuring FMA, select All Programs→HP StorageWorks File Migration

Agent

→FMA Configuration from the Windows Start menu. Also, FMA configuration information is available in the Storage section of Computer Management on Server 2003 (32 bit) and in the Server Manager section on Server 2008 (32 bit).

Upgrading FMA

The following upgrade paths are supported:

•2.1.x→2.5

To upgrade from 2.1.x, you must upgrade to 2.1.11, then upgrade to 2.2.7, and then upgrade to 2.5.

•2.2.x→2.5

To upgrade from 2.2.x, you must upgrade to 2.2.7 and then upgrade to 2.5.

Evicting a node from a cluster on page 17) on moving cluster groups.

Managed Volumes on page 45 for instructions on adding volumes.

Archives on page 25. For information about

Installation | 17

If you want to migrate a Windows 2003 cluster that includes FMA to a Windows 2008 cluster, see Migrating

a Windows 2003 cluster on page 18.

To upgrade FMA on a file server

1. Run setup.exe. This file is available on the installation CD.

2. In the confirmation dialog box, click Ye s .

3. Follow the instructions in the installation wizard.

To update a cluster

WARNING

1. Failover the cluster groups containing the managed volumes and resources of the default cluster group

to another node.

2. Update the nodes in the cluster.

a. Run setup.exe. This file is available on the installation CD.

b. When prompted, confirm to install the new version.

c. After the installation is complete, click Finish.

d. If you are upgrading from FMA 2.1, click Ye s to reboot the server. Wait until the node is active

3. Repeat steps 1 and 2 on each node of the cluster.

Use the Windows cluster administration tools to view the status of the cluster group and the FMA service that was just updated. The cluster group should be online and it should contain the FMA configuration service. Viewing the cluster group is different depending on whether the system is based on Server 2003 or 2008:

• Server 2003:

Run the cluadmin application. The default cluster group can be found under the Groups section.

• Server 2008:

Window 2003 clusters cannot be upgraded to Windows 2008 clusters directly with this method. This is because of the differing requirements of the Windows 2003 server clusters and Windows 2008 failover clusters. See Migrating a Windows 2003 cluster on page 18 to prevent data loss.

before continuing with the step

If you are updating from FMA 2.2, a reboot is not required.

Run the cluadmin.msc application. Select the cluster name and then in the center pane expand the Cluster Core Resources section.

To verify that the File Migration Agent service and File Migration Agent AFM service are running on all nodes, run services.msc from the Windows Run menu and check the status of both services. The FMA configuration service only runs on the node that is hosting the Cluster Group.

Migrating a Windows 2003 cluster

This section describes how to migrate a Windows 2003 cluster to a 2008 cluster configuration and FMA is installed in the cluster.

Before beginning this upgrade process, perform the following:

• Record the drive letter that is listed in FMA volume management.

18 | Installation

•Use the fmacli arc command to record the list of archives with their IDs. The IDs are listed in the

first column of the output of the command.

To migrate an FMA cluster to 2008

1. Uninstall FMA 2.2 on each node of the 2003 cluster. Refer to Uninstalling FMA on page 20 for more

information.

2. Migrate the cluster configuration to the Microsoft Server 2008 cluster by following the recommended

Microsoft process,

• The storage must be migrated to the same drive letters

• To prevent recalling all the managed files in the process, the storage must be moved as-is to the new cluster

3. Install FMA 2.5 on each node of the 2008 cluster and configure it as described in Installing FMA in a

cluster configuration on page 14.

4. Manage the volumes that where moved during the migration process. For more information on adding a volume to management, see

5. Recreate the archives as follows:

• Create archives in the same order in which they were created on the original cluster, to ensure that

the archive IDs are created properly. Use the list of archives that was generated by the fmacli arc command before beginning this procedure.

• When complete, run the fmacli arc command again. The output should be identical to the

output of the command for the 2003 cluster.

http://technet.microsoft.com/en-us/library/cc754506.aspx. Note the following:

Creating managed volumes on page 47.

Downgrading FMA

If you must downgrade from version 2.5 and 2.2.7 was previously installed, you must complete the following steps.

To downgrade from 2.5 to 2.2.7

1. Uninstall 2.5 as described in Uninstalling FMA on page 20.

2. When prompted to save configuration settings, select Ye s.

3. Insert the 2.5 CD.

4. Change directories to the CD drive.

5. Run the following command:

instmod RISS "\SOFTWARE\Hewlett-Packard\HP FMA\Archives"

6. Reinstall 2.2.7 as described in Installing FMA on file servers on page 7. (You can ignore the Autopass warning about the higher version.) FMA 2.5 provides a new version of Autopass which is backward compatible with 2.2.

Installation | 19

Uninstalling FMA

Use the following steps to uninstall FMA.

To uninstall FMA from a single file server

1. In the Windows Start menu, select HP StorageWorks File Migration Agent→FMA Uninstall.

2. After starting the uninstallation process, you are asked if you want to keep the current FMA configuration or if you want to completely uninstall the FMA software.

HP recommends selecting Ye s to keep the current FMA configuration. If you select No, ensure that all migrated data from each managed volume have been successfully recalled. Otherwise, you will not be able to access released files.

3. If you are uninstalling version 2.1.x or older, you must reboot after uninstalling.

To uninstall FMA from a cluster

1. Stop the File Migration Agent and File Migration Agent AFM services on every cluster node.

2. To remove the FMA configuration server cluster resource from the default cluster group, use the Windows cluster administration user interface, right-click the FMACFS resource (located in the Cluster Group by default) and click Delete. Removing this resource prevents the cluster group from failing.

3. Run the FMA uninstallation on all nodes. For more information, see To uninstall FMA from a single file

server on page 20.

4. If you are uninstalling version 2.1.x or older, you must reboot after uninstalling.

Note If you are permanently uninstalling FMA as a single file server or as a cluster, examine the

managed volumes carefully to ensure all metadata is removed. If necessary, run fmacli erase on the managed volumes to remove any remaining FMA metadata from the files.

Removing the Explorer plugin

The FMA Explorer plugin is automatically registered during the installation process.

To remove the plugin from Windows Explorer

On the command line, enter the following:

regsvr32 /u hsmext.dll

To add the plugin to Windows Explorer

On the command line, enter the following:

regsvr32 hsmext.dll

20 | Installation

+ 160 hidden pages