fma v2 administration guide

HP StorageWorksFile Migration Agent administrator guide

Part number: T4274-96105Second edition: October 2006

Legal and notice information

© Copyright 2005, 2006 by Hewlett-Packard Development Company, L.P.

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.

Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Microsoft, Windows, Windows NT, and Windows XP are U.S. registered trademarks of Microsoft Corporation.

File Migration Agent administrator guide

File Migration Agent administrator guide 3

About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15HP web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1 Product information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17HP StorageWorks File Migration Agent overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Important terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Key features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Data management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Offline marker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21File state diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Software components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23FMA command-line tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23FMACLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

FMAFileUtil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23FMA applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

FMA MMC Snap-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23FMA Policy Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23FMA Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23FMA Explorer plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24FMA Job Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Technical user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Operating system version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24First steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2 Installation, uninstall, update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Install the FMA software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Starting installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Installation path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Setup type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Define installed features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Copying the FMA software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Technical user for the File Migration Agent service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31FMA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Uninstall the FMA software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Minor updates from version 2.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35FMA License Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Enter FMA license keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Contents

4

FMA licensing problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Managing FMA archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Configure backend archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38RSA configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

RSA-CIFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40RSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43RSA-RISS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Storage descriptor creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Use system name for storage descriptor creation (Option 1 off = default) . . . . . . . . . . . . . . . . . 45Ignore system name for storage descriptor creation (Option 1 on) . . . . . . . . . . . . . . . . . . . . . . 45Use volume serial for storage descriptor creation (Option 2 off = default) . . . . . . . . . . . . . . . . . 45Ignore volume serial for storage descriptor creation (Option 2 on) . . . . . . . . . . . . . . . . . . . . . . 46

Delete an FMA archive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Managing volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Create a managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Stop a managed volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Start an unmounted volume again . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Delete a managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Volume properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50FMA policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Disk space monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Watermark parameters: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Retention time parameters: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Exclusion list:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53File policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54FMA configuration for MS Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4 Operating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61FMA Job Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Starting FMA Job Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Create a new job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Job parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Migration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Add archive for migration operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Delete an archive from the migration operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Release parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Change job settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Delete a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Run a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67About FMA Job Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Schedule FMA jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68FMA Job Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Command Line Interface (FMACLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69FMACLI syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69FMACLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

ACTIVATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

ARCHIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74


Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Description of columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

CLEANUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

ERASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

FIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

INFO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Description of columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

MIGRATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

RECALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

RSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

SYSTEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

VERIFY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

6

Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Local Check (Level 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Remote Check (Level 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

VERSION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Description of columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

FMA Explorer plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Migrating files or folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Releasing files or folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Recalling files or folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Viewing FMA metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Register/unregister the Explorer plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

FMAFileUtil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Arguments (pack command). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Arguments (unpack command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107FMA log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107FMACLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108FMA Job Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Windows event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

5 Best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Create a new HP StorageWorks File Migration Agent (FMA) archive . . . . . . . . . . . . . . . . . . . . . . . . . . 109

FMA archive configuration for a Windows archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Example of the GDS FTP-Server configuration file ftp_server.cfg file. . . . . . . . . . . . . . . . . . . . . . . 109FMA RSA-FTP Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

FMA archive configuration for an FSE/Linux archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112FMA archive configuration for a CIFS-based NAS device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115FMA archive configuration for RISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Create a new managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Create file policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Create disk usage monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Determine FMA software version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Migrate files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Release files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Recall files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Set a high-watermark for migration or releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124


Verify data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Create an FMA job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Schedule FMA commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Schedule FMA jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Backup/restore concept for FMA managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Relocating data to another FMA managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Relocating data procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Relocating a large number of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Archive store configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

FTP configuration for HP StorageWorks File System Extender (ftpd) . . . . . . . . . . . . . . . . . . . . . . . . . 129Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129General topics for using the RSA-FTP module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Minimum requirements for FTP servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Configuration of VSFTPD on SuSE Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Setting up a new group and user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Take ownership of the PartitionRoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Activation of INETD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Configuration of VSFTPD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Configuration for LogRotate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Configuration of VSFTPD on Red Hat Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Configuration of PROFTPD on Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Setting up a new group and user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Configuration of PROFTPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Using GDS FTP-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Install the GDS FTP-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Starting installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Customer information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Installation path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Copying the GDS FTP-Server software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Configure the GDS FTP-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Uninstall the GDS FTP-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

RISS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Integration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Configuring RISS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Configuring application servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Required configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Third-party product compatibility list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Anti-virus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Symantec AntiVirus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140McAfee VirusScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Sophos Anti-Virus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141ServerProtect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141eTrust AntiVirus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141TrendMicro OfficeScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Backup/restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142BackupExec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142BrightStor ArcServe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142NetBackup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Networker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143NetVault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143MS VSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Galaxy Backup & Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Quota/encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145StorageExec. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

8

Defragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145O & O Defrag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145MS Defragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

IndexServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146MS IndexServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146FMA error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

FMA error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146WIN32 error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Reporting a problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Figures1 Migration process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Migration results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Hierarchical storage management in heterogeneous networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Offline file attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 State of files managed by FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 FMA software components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 InstallShield Wizard Welcome dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 License Agreement dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Destination Folder dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2810 Setup Type dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2911 Custom Setup dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2912 Installing the HSM Explorer Extension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3013 Installing HP StorageWorks File Migration Agent dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3014 FMA Wizard (Technical user) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3115 Select User dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3116 Select User (Advanced) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3217 InstallShield Wizard Completed dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3218 FMA installation directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3319 FMA Uninstall menu item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3320 InstallShield Wizard (Remove) dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3321 Add/Remove Programs dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3422 FMA uninstallation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3423 Advanced Settings dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3624 Shortcut for starting FMA MCC Snap-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3725 FMA MCC Snap-In configuration items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3826 FMA backend archives list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3827 Context menu for defining FMA archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3928 Archive Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3929 Editing existing FMA archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4030 Rsa Configuration dialog—RSA-CIFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4031 Data Properties (Sharing) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4132 Permissions for data (Security) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4233 Data Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4234 Rsa Configuration dialog—RSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4335 Rsa Configuration dialog—RSA-RISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4436 Storage descriptor creation dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4537 Deleting FMA archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4638 Deleting Archive confirmation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4639 Managed Volumes list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4740 Creating managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4841 Context menu for creating managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4842 Creating managed volumes—Need reboot status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4843 Creating managed volumes—Active status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4844 Context menu for stopping managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48


45 Stopping managed volumes—Not mounted status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4946 Context menu for starting unmounted volumes again . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4947 Starting unmounted volumes again—Active status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4948 Context menu for stopping managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4949 Stopping managed volumes—Not mounted status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4950 Context menu for deleting managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5051 Deleting managed volumes—Not managed status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5052 Context menu for displaying volume properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5053 Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5054 Computer Management dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5155 Volume Parameters (Watermark tab) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5256 Volume Parameters (Retention tab) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5257 Volume Parameters (Exclusion tab) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5258 Scheduling dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5359 Schedule Options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5360 Policy Properties (Properties tab) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5361 Policy Properties (Filtering tab) dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5462 Policy Properties (Archives tab) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5463 FMA Wizard (Cluster setup) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5564 FMA Wizard (Technical user) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5565 FMA Wizard (Cluster setup) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5666 FMA Wizard (Cluster setup) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5667 FMA Wizard (Wizard Summary) dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5768 Activating the Ignore system name for storage description creation option . . . . . . . . . . . . . . . . . . . . 5869 Deleting the FMA Cfg Server resource from the Cluster Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5970 FMA Job Manager dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6171 Shortcut for starting FMA Job Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6272 Creating new jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6273 Job dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6374 Migration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6475 Adding archives for migration operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6576 Deleting archives from migration operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6577 Release dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6678 Retention times for release parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6679 Changing job settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6780 Deleted job confirmation dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6781 About FMA Job Manager dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6882 MIGRATE command example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8583 RECALL command example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8984 Retention times for RELEASE command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9285 RELEASE command example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9386 FMA Explorer context menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10187 Processing results dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10188 Migrating from context menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10289 Releasing from context menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10290 Release options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10291 Recalling from context menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10392 Viewing metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10493 Storing data in an FSE Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10594 Layout of FMA log file entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10895 Rsa Configuration dialog—RSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11096 Replication archive (Windows) example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11197 Rsa Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11298 Rsa Configuration dialog—RSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11399 Replication archive (Linux) example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114100 Rsa Configuration dialog—RSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115101 Rsa Configuration—RSA-CIFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116102 Rsa Configuration dialog—RSA-CIFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117103 Replication archive (Microsoft Server) example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

10

104 Rsa Configuration dialog—RSA-RISS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118105 Rsa Configuration dialog—RSA-RISS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119106 Replication archive (RISS) example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119107 New Policy - Properties (Filtering) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120108 Scheduling dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120109 Schedule Options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121110 Schedule Options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121111 Schedule Options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121112 Volume Properties (Watermarks) dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122113 Volume Properties (Retention) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122114 Volume Properties (Retention) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122115 Volume Properties (Exclusion) dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123116 Info dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123117 About FMA Job Manager dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123118 InstallShield Wizard Welcome dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135119 Customer Information dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136120 Setup Type dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136121 Installing GDS FTP-Server dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137122 InstallShield Wizard Completed dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137123 Add/Remove Programs dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Tables1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Archive Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 Rsa Configuration dialog—RSA-CIFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Rsa Configuration dialog—RSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 Rsa Configuration dialog—RSA-RISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Managed Volumes list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 Managed Volumes list status symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 FMA Job Manager dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619 Job dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6310 Migration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6411 Release dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6612 [HKEY_LOCAL_MACHINE\SOFTWARE\GDS\FMA\JobMgr] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6813 Supported FMACLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7014 ACTIVATE command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7215 ARCHIVE command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7416 Column descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7417 CLEANUP command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7518 ERASE command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7619 FIND command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7820 INFO command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8021 INFO command output for example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8222 MIGRATE command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8323 POLICY command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8624 RECALL command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8725 RELEASE command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9026 Variable definitions for Figure 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9227 RSA command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9428 SYSTEM command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9429 VERIFY command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9630 VERSION command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9831 VOLUME command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9932 Description of columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9933 Result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10034 FmaFileUtil options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10535 FmaFileUtil commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10636 FmaFileUtil command-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10637 FmaFileUtil arguments (pack command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106


38 FmaFileUtil arguments (unpack command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10639 Parameters for useradd command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12940 Parameters for LogRotate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13141 Parameters for useradd command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13342 Symantec AntiVirus specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14043 McAfee VirusScan specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14044 Sophos Anti-Virus specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14145 ServerProtect specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14146 eTrust AntiVirus specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14147 TrendMicro OfficeScan specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14148 BackupExec specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14249 BrightStor ArcServe specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14250 Data Protector specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14251 NetBackup specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14352 Networker specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14353 NetVault specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14354 MS VSS specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14455 Tivoli Storage Manager specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14456 Galaxy Backup & Recovery specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14557 StorageExec specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14558 O & O Defrag specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14559 MS Defragmentation specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14560 MS IndexServer specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146


About this guideThis guide provides information about:

• Installing HP StorageWorks File Migration Agent (FMA)• Performing typical tasks needed for operating FMA

Intended audienceThis guide is intended for system administrators who are experienced with Windows Server 2003 operating systems.

PrerequisitesPrerequisites for installing and using this product include:

• Familiarizing yourself with this guide• Meeting all minimum installation requirements• Reviewing the Readme.txt file on the CD for any last-minute announcements

Related documentationThe following documents provide related information:

• HP StorageWorks File Migration Agent Administrator Guide • HP StorageWorks File Migration Agent Release Notes• Readme.txt file

You can find these documents from the Manuals page of the HP Business Support Center web site:

http://www.hp.com/support/manuals

In the Storage section, click Archiving and active archiving and then select your product.


14

Document conventions and symbols

WARNING! Indicates that failure to follow directions could result in bodily harm or death.

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

HP technical supportTelephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/.

Collect the following information before calling:

• Technical support registration number (if applicable)• Product serial numbers• Product model names and numbers• Error messages

Table 1 Document conventions

Convention Element

Medium blue text: Figure 1 Cross-reference links and e-mail addresses

Medium blue, underlined text (http://www.hp.com)

Web site addresses

Bold font • Key names

• Text typed into a GUI element, such as into a box

• GUI elements that are clicked or selected, such as menu and list items, buttons, and check boxes

Italics font Text emphasis

Monospace font • File and directory names

• System output

• Code

• Text typed at the command-line

Monospace, italic font • Code variables

• Command-line variables

Monospace, bold font Emphasis of file and directory names, system output, code, and text typed at the command line

http://www.hp.com/support/


• Operating system type and revision level• Detailed, specific questions

For continuous quality improvement, calls may be recorded or monitored.

Subscription serviceHP recommends that you register your product at the Subscriber's Choice for Business web site: http://www.hp.com/go/e-updates.

After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources.

HP web sitesFor additional information, see the following HP web sites:

• http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator• http://www.hp.com/support/manuals

Documentation feedbackHP welcomes your feedback.

To make comments and suggestions about product documentation, please send a message to [email protected]. All submissions become the property of HP.

http://www.hp.com

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

http://www.hp.com/support/locator


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


1 Product informationHP StorageWorks File Migration Agent overview

HP StorageWorks File Migration Agent (FMA) offers a technologically innovative approach to data movement by maintaining active files on high-performance primary storage while archiving inactive files to cost-effective secondary storage.

Figure 1 Migration process overview

FMA provides support for policy-based file migration, disk space monitoring and remote storage configuration through an easy-to-use graphical user interface, which is seamlessly integrated into Microsoft’s Management Console (MMC).

The migration process itself is transparent to Windows users and applications and extends the local file system to virtually infinite storage. Data management policies can be individually defined on directory levels based on criteria such as file extension, file size and file timestamps to maintain active data on high performance disk storage and move inactive or less-frequently used data to lower-cost secondary storage devices or archival systems.

18 Product information

An application or user still has transparent access to “released” data through a stub file on the FMA managed volume, which contains the link information where the file is stored in the archives. It also contains other HSM relevant metadata such as migration and recall timestamps and file status.

When a read or write operation on the content of a released file is started, FMA is automatically triggered by its file system filter component, and the file content is retrieved from the archive to the local file system. Access to released files is the same as accessing locally stored data, except for a short delay caused by the archive retrieval process.

Figure 2 Migration results

To implement a fault-tolerant environment FMA can be used in a Windows cluster environment.

Additionally, multiple redundant archive copies on different locations are supported, which is a significant enhancement in data protection. If one archive device is not available due to maintenance reasons or a system or network failure, data will be automatically retrieved from the redundant location.

During the downtime of one archive location, data movement is still processed on the accessible archive locations.

FMA provides a simple and cost-effective solution for aggregating multiple storage locations into one virtual central archive pool.

Currently FMA supports the following archive types:

• HP StorageWorks File System Extender (FSE) Archive• HP StorageWorks Reference Information Storage System (RISS)• NAS appliances (CIFS)

The following example describes an FMA concept of a three-tier hierarchical storage management solution in heterogeneous networks:

• FMA acts as the 1st tier,• the 2nd tier is an FSE system,• and the 3rd tier is tape media where data will be migrated to by the 2nd tier.


Figure 3 Hierarchical storage management in heterogeneous networks

Important termsArchive Backend archive like an FSE Archive, any other NAS storage device, or the RISS.

Backend datastore Device that stores the data moved from the local system.

File Policy A set of rules that determines which files are to be migrated whenever the policy process runs. The rules can be any combination of file age, file size and file name. Rules may also include or exclude files from migration by name or attribute. Wildcards may be used for the file name.

File Policies may be defined per directory and are applied to all files of that directory and its subdirectories, unless a subdirectory has its own file policy defined.

HSM metadata Additional information that the HSM system needs for data management.

Inactive files (old data) Files that have not been touched for a particular period of time and, therefore, are considered inactive.

Managed volumes Volumes that are managed by the FMA. The file system of these drives must be NTFS. System drives are not supported.

Migration Creating a copy of the local file in the backend archive.

Policy Process The engine that interprets the file policies and triggers migrations and releases of files according to the policies. The policy process can be scheduled to run at any desired schedule, as often as seems appropriate.

Recall This process retrieves data from the backend archive.

Release Process that deletes the local file content after a successful migration and marks the file OFFLINE.

Remote Storage Adapter (RSA) Implements the FMA Storage interface and acts like a “driver” for different “flavors” of archive storage.

Stubfile Local “substitution file” for a file that has been released; also called “shortcut.” The stubfile is marked as a


sparse file and the file’s data contains zero bytes. The link to the file’s data in the backend datastore is kept in the extended attributes of the file. In addition, a stubfile is marked “offline” (offline flag is set).

Volume Policy A set of watermarks and retention periods that determine the automatic release strategy.

Key featuresFMA in this version supports the following features:

• FMA supports policy-based migration of files on criteria such as file age, file size, or file name. Based on the policies, FMA will automatically trigger migrations to archives at user-scheduled intervals. It is possible to exclude files from migration.

• FMA supports storage space monitoring. Based on configurable watermarks and retention time periods, files that have previously been migrated to an archive will be released from the managed volume and replaced by a stub file, through which the archived file may still be accessed seamlessly by the user or an application.

• FMA supports automatic recalls from the archive locations when files are accessed and sets the directory displays to the correct file sizes.

• Metadata can be backed up with any backup application that supports offline files. The application must open the files with the FILE_FLAG_OPEN_NO_RECALL option. For details about backup applications qualified with FMA, see ”Backup/restore” on page 142 which discusses Third-party product compatibility.

• FMA supports multiple target archives where the data is migrated to. Currently the maximum number of archives per system is 10. This means that for each file 10 copies in different archives can be managed.

• By using multiple target archives, an automatic failover for recalls is implemented. If a file cannot be recalled from the first archive, FMA tries the next archive location and so on. This will cause automatic failover if archives are temporarily unavailable during recalls.

• Data will be recalled immediately by FMA when a user or application accesses a stubfile.• FMA supports recall operations on secondary archive locations should the primary archive be

inaccessible. The replication to the secondary archive must be handled outside of FMA via some replications mechanism such as RISS replication.

• FMA is fully integrated into the management console (‘Computer Management’) of the Windows system. All definition of archives, managed volumes, and file policies are done via an FMA management console plug-in.

• FMA includes a Windows File Explorer plug-in for migrating, recalling, and releasing files as well as displaying FMA metadata.

Benefits• Transparent access to released files for users and applications without administrator intervention.• Lowering the total cost of ownership of mission-critical data by easily increasing storage space without

creating new network shares and volumes, which require further administrative effort not least because of relocating files to newly deployed storage.

• Lowering TCO by migrating inactive data to less-expensive storage media.• Less administration through automatic data management based on administrator-defined policies and

storage space monitoring.• Deployment of a fault-tolerant environment.• Less investment in file servers and storage capacity.• Reduction of storage management costs by reducing the daily backup volume due to only backing up

the metadata for inactive files.• Minimizing downtime after a disaster recovery by restoring only production files in full and only the

metadata for released files.• Easy installation and configuration.


Data managementThis section describes the lifecycle of files that are under control of the FMA.

Offline markerTo mark offline files (files with remote data), the FILE_ATTRIBUTE_OFFLINE flag is used. This file attribute is officially supported in Windows 2000 and Windows 2003 or Windows 2003/R2. Files that have this attribute set are considered offline.

Figure 4 Offline file attribute

MetadataFMA metadata is stored in an NTFS extended attribute named _IFE_FILEINFO.

File state diagramThe following diagrams show the states of files managed by FMA.

Figure 5 State of files managed by FMA


MigrationFiles are migrated to one or more archives by FMA based on policies set by the administrator. Any number of policies can be set on each volume managed by FMA. The policies are based on file name (wildcards are usable, for example, *.exe or a*.txt), file age in relation to creation, modification or last access time, or a minimum file size. Files may be excluded from migration by file name or file attributes (for example, hidden files).

Each migration policy is valid for a directory of the managed volume and all its subdirectories. A policy attached to the root directory will therefore apply to the entire volume.

Migration policies are applied by FMA through its policy process. The policy process can be freely scheduled by the administrator to run at regular intervals. The intervals can range from multiple times a day to once a year. The policy process can also be started manually.

Files may also be migrated explicitly via the FMA command line interface, or by using the Windows File Explorer plug-in.

During the archiving process files are opened exclusively to ensure that the data is consistent. Archiving does not lock files exclusively. After the file is archived, the file size and the time stamps are checked to validate the archive copy.

ReleaseFMA monitors the space available on managed volumes. The administrator must set three watermark levels (in %) for each volume: low, high, and critical. When the high watermark level is reached, FMA will release files until the low Watermark level is reached. The decision which files to release is based on the defined volume retention policies. The administrator may specify these retention policies per volume. Retention policies are related to elapsed time since last access or modification to a file.

If the critical watermark is reached, files are released independently of the retention policies.

FMA monitors the space on a volume at administrator-defined intervals.

Files may also be released explicitly via the FMA command line interface, or by using the Windows File Explorer plug-in.

Only files that have at least one valid archive copy can be released. Releasing locks files exclusively. Files that cannot be opened exclusively cannot be released and will remain online.

Files with a size of below 1024 Byte will never be released.

RecallWhenever a user or application accesses an offline file to read its data, FMA will intercept the read request and will first retrieve the file’s data from the archive. If an archive is not available FMA will try data copies in other archives if there are any.

Such copies can either be created by FMA via migration to more than one archive or by the archive itself via replication. For the latter case, FMA lets the administrator define an alternate (that is, replicated) archive from which to retrieve data.

If a file cannot be recalled from any of the archives, an FMA error code (see ”FMA error handling” on page 146) will be returned.

Files may also be recalled explicitly via the FMA command line interface, or by using the Windows File Explorer plug-in.


Software componentsThe following diagram shows the FMA software components on an abstract level:

Figure 6 FMA software components

FMA command-line toolsFMACLI

• FMACLI is the command-line interface for data management.• FMACLI contains most available FMA kernel functions.• File name input options

• Single file via command line• File list (either via file or stdin)• Processes directories recursively

• Informational output is written to stdout, errors are written to stderr. Keep this in mind when redirecting output for logging purposes.

FMAFileUtilUtility for manual data retrieval and storage with FTP-based archives.

FMA applicationsFMA MMC Snap-In

• FMA archive management.• Management for FMA-managed volumes.• Policy configuration.• Disk space watermark configuration.• Component of the Microsoft Management Console (MMC).

FMA Policy Manager• Scheduler.• Policy management.• Disk utilization monitor.

FMA Wizard• Technical user setup.• FMA/MS cluster configuration.


FMA Explorer plug-in• Context-menu extension for HSM commands (migrate, release, recall).• Property page extension for FMA metadata.

FMA Job Manager• Management of FMA jobs for migration and release operation.• Graphical user interface.

NOTE: The Job Manager is available only for upward compatibility. Its functions can be achieved via the MMC snap-in.

Job Manager tasks should be migrated to active file management policies because the job manager will be discontinued in future FMA versions.

PrerequisitesTechnical 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 datastores.

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 versionThe following operating system versions can be used for FMA:

• Microsoft Windows 2000 Server with SP4 or higher with Update Rollup for Windows 2000 SP4 (KB891861).

• Microsoft Windows 2003 Server with SP1 or higher.• Microsoft Windows Storage Server (WSS) 2003 with SP1 or later• Microsoft Windows 2003 Server R2 with SP1 or higher.• Microsoft Windows Storage Server (WSS) 2003 R2 with SP1 or later

Compatibility issuesSee ”Third-party product compatibility list” on page 140.

RestrictionsThe 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 140.)

• 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 does not support cluster quorum disks.• For restrictions on third-party applications see ”Third-party product compatibility list” on page 140.

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

1. Install the backend archive (CIFS, RISS, or FSE).2. Create a technical user for the File Migration Agent service.

Collect information about the data storage (user ID, IP address, and so on).3. Install FMA. For further information about the FMA installation, see ”Installation, uninstall, update” on

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

FMA archive management, see ”Managing FMA archives” on page 38.5. Configure the managed volumes using the FMA MMC Snap-In. For further information about the FMA

volume management, see ”Managing volumes” on page 46.6. Configure file policies and schedules on the managed volumes using the FMA Policy Manager (see

”FMA 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 ”Disk space monitoring” on page 51).


2 Installation, uninstall, updateHP StorageWorks File Migration Agent (FMA) uses Microsoft Software Installer (MSI). This section describes the installation, uninstall, update, and upgrade processes.

This chapter includes the following topics:

• Install FMA: page 27.• Uninstall FMA: page 33.• Minor update

Update FMA: page 35.

Install the FMA softwarePrerequisites

See ”Prerequisites” on page 24 for further information about what needs to be done before installing FMA.

Read the Software License Agreement that you received with the product and check the Readme.txt file on the installation media for the latest changes.

Starting installationFor installation, please start setup.exe from the installation CD-ROM. The setup program of FMA first initializes the installation files. After this, you receive information about the version and the manufacturer of the FMA software.

Figure 7 InstallShield Wizard Welcome dialog

If you still have other applications running at this time, it is strongly recommended that you close these applications before you continue with the setup of the FMA software. Click the Cancel button and finish the FMA setup. After that, close all open applications and then start the FMA setup again.

If no other application is opened, you can proceed with the installation process by clicking the Next button.

28 Installation, uninstall, update

License AgreementRead the following license contract carefully. You can turn its pages by means of the PgUp and PgDn keyboard keys or the scroll bar.

Figure 8 License Agreement dialog

If you agree with the license contract, select the option I accept the terms in the license agreement. By selecting the option I do not accept the terms in the license agreement, the installation process will be aborted. To install the FMA software, however, you have to agree with the license contract.

Installation pathIn this dialog, enter the FMA installation path.

Figure 9 Destination Folder dialog

The default installation path is C:\Program Files\Hewlett-Packard\HP FMA. When clicking the Change button, another dialog box is opened where you can specify the FMA installation path. After this step, you can proceed to the installation process with a click the Next button.


Setup typeSelect a setup type in this dialog.

Figure 10 Setup Type dialog

If the Complete setup type is selected, the FMA software will be installed completely in the defined installation path (see ”Installation path” on page 28).

In the other case (setup type is Custom), you are able to define a different installation path. (The Change button in the next dialog is active then).

Define installed featuresIf setup type Custom is selected (see ”Setup type” on page 29), this additional dialog appears.

Figure 11 Custom Setup dialog

By clicking the Change button, a further dialog box will appear giving the user the ability to select the FMA installation path. By clicking the Space button, the free space of each hard drive is displayed.


NOTE: This dialog will only appear when the setup type is Custom. By default all features are installed

Click an icon in the feature list to change how an FMA feature is installed. In this case the HSM Explorer Extension will be installed.

Figure 12 Installing the HSM Explorer Extension

Copying the FMA softwareNow the FMA setup will start unpacking and copying the FMA files to disk.

Figure 13 Installing HP StorageWorks File Migration Agent dialog

After the installation has been completed, several menu entries in the Start menu will be generated.


Technical user for the File Migration Agent serviceDuring the installation process a wizard is started for setting up the user account of the File Migration Agent service. Ensure that the selected user account has the appropriate privileges as described in ”Technical user” on page 24.

Figure 14 FMA Wizard (Technical user) dialog

To select a user from any domain of your Windows Network environment click the Browse button to launch the Select User dialog.

Figure 15 Select User dialog


The Advanced button can be used to set up a search for the user account.

Figure 16 Select User (Advanced) dialog

Click Finish on the Wizard Summary page to continue the installation process.

Figure 17 InstallShield Wizard Completed dialog

After this, the installation of the FMA software is completed. Click Finish to exit the FMA setup and reboot the system.


During this installation process, the following structure is created under the defined FMA installation directory (here C:\Program Files\Hewlett-Packard\HP FMA\).

Figure 18 FMA installation directory structure

FMA configurationAfter the FMA files have been copied to the system, you must configure the HSM. See ”Configuration” on page 37 for a description on how to configure the system.

Uninstall the FMA softwareThere are various ways to remove FMA from your system:

1. Uninstall via the FMA Uninstall menu item.

The FMA software can be uninstalled via:

Start > HP StorageWorks File Migration Agent > FMA Uninstall.

Figure 19 FMA Uninstall menu item

2. Uninstall via setup program from your installation disk.

Figure 20 InstallShield Wizard (Remove) dialog


3. Uninstall via Windows Software Manager:

Start > Control Panel > Add/Remove Programs > HP StorageWorks File Migration Agent.

Figure 21 Add/Remove Programs dialog

After starting the uninstall process, you will be asked if you want to keep the current FMA configuration or if you want to completely uninstall the FMA software.

Figure 22 FMA uninstallation dialog

IMPORTANT: If you click No for a complete uninstall of the FMA software including all configuration settings, ensure that all migrated data from each managed volume have been successfully recalled.

After the FMA uninstall process has finished a system reboot is required.

CAUTION: After a successful uninstall, it is not possible to access the released data.

NOTE: When you use the Windows Software Manager for uninstalling, there will not be created an uninstall.log.

For uninstalling the FMA on MS Cluster, see information on page 59.


Minor updates from version 2.xFMA software version 2.x can be updated (minor update) by using the Microsoft Installer (MSI) via Windows software dialogs.

To update FMA, perform the following steps:

1. Start setup.exe from the installation CD-ROM. If setup.exe finds an FMA 2.0 installation, a message appears that asks if you want to continue.

2. Confirm this dialog by clicking the Yes button.3. Follow the next instructions at the screen until the update is finished.4. Reboot the system.

NOTE: When the FMA software is updated from version 2.0, it is recommended to convert the scheduled scripts to FMA’s policies. For further information on FMA’s policy management, see ”FMA policies” on page 51.

NOTE: An update from FMA 2.x does not automatically install the Microsoft Explorer plug-in. You need to run the installation a second time after the update process in maintenance mode to install the Explorer plug-in.

FMA License KeysEnter FMA license keys

FMA includes a temporary license that allows use of the product for 60 days. Use this procedure to enter your permanent license keys.

1. Open a web browser, and enter http://www.webware.hp.com to access the HP Password delivery service website.

2. Click the Generate password(s) link in the navigation pane.3. Enter the order number from the Entitlement Certificate that you received with the product, and click

Next.4. Enter the IP address of the FMA server, and click Next.5. Enter your e-mail address and password, and click Sign-In.

NOTE: If this is the first time you are signing in to this website, you must create a password at this time.

6. Enter the appropriate contact information, and click Next.The Password Certificate appears.

7. Scroll down and copy the license key that appears near the bottom of the certificate.8. Open the C:\Program Files\Common Files\Hewlett-Packard\HPOvLic\data\

LicFile.txt file in a text editing application.9. On a new line, paste the license key that you copied from the Password Certificate.10.Save and close the LicFile.txt file.11. Restart the File Migration Agent service.12. Start FMA by selecting Start > Programs > HP StorageWorks File Migration Agent > FMA

Configuration.13. Right-click HP File Migration Agent, and select License information to verify that your permanent license

was entered successfully.

http://www.webware.hp.com


FMA licensing problemsIf your permanent license keys are not active, verify that the connection for which you have requested the license keys is on top of the connections list.

The order of the connections can be configured via right-clicking My Network Places and selecting: Properties > Network Connections > Advanced > Advanced Settings > Adapters and Bindings.

Figure 23 Advanced Settings dialog

Use the up and down arrow keys to move the connection on top of the connections list.


3 ConfigurationBefore you configure the software, please check the prerequisites on page 24.

For a successful configuration, you need to create a configuration plan. The following questions should help you to achieve this:

• Which volume (D:, E:, and so on) do you want to manage with the HP StorageWorks File Migration Agent (FMA)?

NOTE: An FMA managed volume is the volume (F:, G:, and so on) where the data that you want to migrate and release with the FMA software is stored. The FMA managed volume is the source of the data.

• Which FMA archive (target) should the data be transferred to?• Is it necessary to have the same data stored on different targets (at least on two different targets)?

This is recommended for security reasons.• Which type of archive is required?

FMA supports three different types of archives:• File system archive store (via CIFS)• FTP archive store (HP StorageWorks File System Extender (FSE))• HP StorageWorks Reference Information Storage System (RISS) store

For proper operation, the following items must be configured:

• A technical user must be provided. For further information about technical users, see ”Technical user” on page 24.

• One or more managed file systems on the local system.• One or more backend archive locations.

CAUTION: After modification in the managed file systems, please reboot the FMA system.

FMA contains a graphical user interface that is installed as a component of the Microsoft Management Console (FMA MMC Snap-In). The rest of the document will refer to this part as the FMA MMC Snap-In. This section describes how to set up the HSM system using FMA MMC Snap-In.

To start the FMA MMC Snap-In, use the shortcut:

Start > Programs > HP StorageWorks File Migration Agent > FMA Configuration

Figure 24 Shortcut for starting FMA MCC Snap-In

or use the shortcut:

Start > Control Panel > Administrative Tools > Computer Management

The FMA MMC Snap-In has various entries for the different items that need to be configured:

• Archives (configure backend archives as target).• Managed Volumes (configure managed file systems as source).

38 Configuration

Figure 25 FMA MCC Snap-In configuration items

Managing FMA archivesConfigure backend archives

First you need to configure the archive location where your data is copied to. Each remote storage adapter supports a primary and secondary archive path. The replication to the secondary archive must be handled outside of FMA via some replication mechanism, such as FSE Archive. If the primary archive location is not accessible, the secondary archive path is used for data retrieval. Migrations are only performed to the primary archive location.

FMA supports three different types of remote storage adapters (RSA) for accessing backend archives:

• RSA-CIFS uses the Common Internet File System (CIFS) protocol for attaching FMA to NTFS or Samba-based file system archive stores via network shares.

• RSA-FTP uses the File Transfer Protocol (FTP) for connecting FMA to FSE Archive systems and to non-NTFS file system archive stores. It is recommended to use RSA-FTP for Windows and Linux-based FSE Archive systems. RSA-FTP has been successfully tested in combination with the following FTP servers:• GDS FTP-Server version 2.0.3 (used on Windows FSE Archive)• vsFTPD version 1.1.0• ProFTPD version 1.2

• RSA-RISS is used for connecting FMA to the RISS.

Figure 26 FMA backend archives list

To define a new FMA archive, you have to perform the following steps:

1. Select the Archives item.


2. Right-click in the white space to display the context menu.

Figure 27 Context menu for defining FMA archives

3. Select New archive in the context menu.The Archive Properties dialog appears.

Figure 28 Archive Properties dialog

4. Enter the following values for the new archive.

NOTE: If you have changed the RSA configuration, you need to restart the File Migration Agent service to activate the new configuration.

Changing the RSA configuration may lead to inaccessible archive data.

5. Click the OK button to display the RSA configuration dialog. Each RSA module has implemented its specific configuration dialog.For further information about the RSA configuration, see page 40.

Table 2 Archive Properties dialog

Setting Description

Archive name: Name of the archive definition. This name is used as a reference to this archive in FMA for migration and recall operations.

Archive ID: Internal reference of this archive. This number is generated and has to be unique. It is not possible to change this value.

If stubfiles are to be moved between systems, the archive ID must be unique across all systems.

RSA Module: The module depends on the type of archive. The available modules are:

• RSA-CIFS (RsaCIFS.dll)• RSA-FTP (RsaFTP.dll)• RSA-RISS (RsaRISS.dll)

The module corresponds with the RSA (remote storage adapter). For further information, see ”Configure backend archives” on page 38.

Performance index: Priority for recalls. The smaller the index, the higher the priority (default: 100).

Description: Free text comment for this archive.

40 Configuration

6. Repeat these steps for each FMA archive you want to define.If you want to edit an existing FMA archive, double-click the corresponding archive entry.

Figure 29 Editing existing FMA archives

RSA configurationRSA-CIFS

Figure 30 Rsa Configuration dialog—RSA-CIFS

Table 3 Rsa Configuration dialog—RSA-CIFS

Setting Description

Primary archive: Fully qualified NAS path where the data is migrated to and recalled from. Path names can also be specified using UNC notation. The specified path must exist.

Secondary archive: Fully qualified NAS path where the data is recalled from if the primary archive is not accessible.

Ignore security on backend archive:

If this option is selected, no security information is stored in the backend archive. For security reasons, this switch should only be used in multi-domain environments.

Default: not selected

Store data stream only: If this option is selected, only the default data stream of this file is stored in the backend archive. By default all streams and EAs are stored.1


IMPORTANT: Ensure that NTFS folder permissions and share permissions are configured correctly on the shared archive folder to avoid “ACCESS_DENIED” errors.

1. Share Permissions:Click the Sharing tab on the folders property page and click the Permissions button to set permissions for the FMA user, who accesses this folder over the network.

Figure 31 Data Properties (Sharing) dialog

Ignore system name ... : If this option is selected, the system name will not be used to generate a storage descriptor in the archive storage. If this option is off, the system name will be used to create a storage descriptor.

For further information about this option, see page 45.

NOTE: You should only use this option when you can be sure that the storage descriptor without the system name is unique.

Ignore volume serial ... : If this option is selected, the volume serial number of the local file system will not be used to generate a storage descriptor in the archive storage. If this option is off, the volume serial will be used to create a storage descriptor.


NOTE: You should only use this option when you can be sure that the storage descriptor without the volume serial is unique.

NOTE: All values will be used for the primary and the secondary CIFS archive.

1. This option was introduced for SAMBA installations and is not recommended for a normal NAS device.

Table 3 Rsa Configuration dialog—RSA-CIFS (continued)

Setting Description

42 Configuration

The FMA User needs to be granted Full Control permissions.

Figure 32 Permissions for data (Security) dialog

2. NTFS Folder Permissions:Click the Security tab on the folder’s property page and grant Full Control permissions to the FMA User.

Figure 33 Data Properties dialog


RSA-FTP

Figure 34 Rsa Configuration dialog—RSA-FTP

Table 4 Rsa Configuration dialog—RSA-FTP

Setting Description

Host/IP: Hostname or IP address of the FTP server used for accessing the primary archive location.

Secondary Host/IP: Hostname or IP address of the FTP server used for recalls if the primary archive instance is not available.

Port: FTP port (default: 21).

User: FTP user.

Password: Password.

Root path: Root path on the specified FTP server.

Connection timeout (ms) Timeout for the connection to the FTP server in ms. The default value is 500 ms.

Data read timeout (ms) Read timeout for FTP data.

Default 0: Means no timeout.

This setting should not be changed unless Hewlett-Packard Co. support personnel tells you to do so.

44 Configuration

NOTE: All values will be used for the primary and the secondary FTP archive.

For further information about the FTP backend configuration, see page 129.

RSA-RISS

Figure 35 Rsa Configuration dialog—RSA-RISS

Ignore system name ... : If this option is selected, the system name will not be used to generate a storage descriptor in the archive storage. If this option is off, the system name will be used to create a storage descriptor.


NOTE: You should only use this option when you can be sure that the storage descriptor without the system name is unique.

Ignore volume serial ... : If this option is selected, the volume serial number of the local file system will not be used to generate a storage descriptor in the archive storage. If this option is off, the volume serial will be used to create a storage descriptor.


NOTE: You should only use this option when you can be sure that the storage descriptor without the volume serial is unique.

Table 5 Rsa Configuration dialog—RSA-RISS

Setting Description

Primary RISS: Hostname or IP address of the primary RISS.

Secondary RISS: Hostname or IP address of the secondary RISS.

Domain: RISS domain the data goes to.

Table 4 Rsa Configuration dialog—RSA-FTP (continued)

Setting Description


NOTE: All values will be used for the primary and the secondary RISS archive.

FMA supports only one-way (Active/Passive) RISS remote replication services. The mirror copy of a replicated RISS is available via the secondary RISS hostname.

For further information about the RISS backend configuration, see page 139.

Storage descriptor creation

Figure 36 Storage descriptor creation dialog

Use system name for storage descriptor creation (Option 1 off = default)The system name will be used to create a storage descriptor.

Structure:

Example:

Ignore system name for storage descriptor creation (Option 1 on)The system name will be used to create a storage descriptor.

Structure:

Example:

Use volume serial for storage descriptor creation (Option 2 off = default)The volume serial will be used to create a storage descriptor.

Structure:

Default repository: Default repository where the data is stored.

Recipients: Default recipients for FMA data.

Recipients options See text in Figure 35.

Table 5 Rsa Configuration dialog—RSA-RISS (continued)

Setting Description

<archive-path>\<system-name>\<vol-serial>\<local-path>\<file-name>.<generation>

D:\Archives\system03\00471100\dir1\dir2\file1.dat.0000

<archive-path>\<vol-serial>\<local-path>\<file-name>.<generation>

D:\Archives\00471100\dir1\dir2\file1.dat.0000

<archive-path>\<system-name>\<vol-serial>\<local-path>\<file-name>.<generation>

46 Configuration

Example:

Ignore volume serial for storage descriptor creation (Option 2 on)The volume serial will not be used to create a storage descriptor.

Structure:

Example:

Delete an FMA archive

CAUTION: Recall all migrated data first before deleting the FMA archive.

1. Right-click the corresponding volume entry to display the context menu.

Figure 37 Deleting FMA archives

2. Select the Delete item in the context menu.

Figure 38 Deleting Archive confirmation dialog

3. Confirm the confirmation dialog with the Yes button.

Managing volumesA managed volume is used as the primary storage resource from which files are migrated to secondary storage devices and whose storage capacity is extended by the FMA software. FMA supports only locally attached NTFS volumes, which have drive letters assigned or are mounted in an empty NTFS folder.

The following drives can not be managed by the FMA software:

• Network drives• System volumes• MS cluster quorum disks• Non-NTFS filesystem volumes

Data movement on managed volumes is primarily controlled by file policies, which are designed to individually configure the following parameters:

• Path on which the policy is active• Criteria for selecting file candidates • Archive locations

D:\Archives\system03\00471100\dir1\dir2\file1.dat.0000

<archive-path>\<system-name>\<local-path>\<file-name>.<generation>

D:\Archives\system03\dir1\dir2\file1.dat.0000


File policy processing is controlled by an internal scheduling service, which allows to setup a schedule individually for each managed volume.

Additionally a disk space monitor is available for each managed volume for releasing files based on file retention criteria and watermarks for disk utilization.

After selecting the Managed Volumes item, the following volume list is displayed.

Figure 39 Managed Volumes list

Table 6 Managed Volumes list

Column Description

Volume: Volume name together with a status symbol.

Status: See Table 7.

File system: File system of this volume (always NTFS).

Capacity: Disk space (max. available).

Free Space: Free disk space.

% Free: Free disk space in percent.

PID: HSM process ID of volume manager process.

Migrated bytes: Migrated bytes.

Table 7 Managed Volumes list status symbols

Symbol Status

Volume is not managed.

Managed volume is active.

Managed volume is inactive.

Volume is a system volume (cannot be managed).

Volume is in error status.

Managed volume needs a reboot.

48 Configuration

Create a managed volumeIn the next step, you need to define the local file systems you want to manage.

Figure 40 Creating managed volumes

1. Select the Managed Volumes item.All volumes with NTFS file system are displayed.


Figure 41 Context menu for creating managed volumes

3. Select the New item in the context menu.The symbol of the volume is changed. The status of the volume is set to Need reboot. Repeat these steps for each volume you want to manage.

Figure 42 Creating managed volumes—Need reboot status

4. Reboot the (FMA) system now.After rebooting, the symbol of the volume is changed. The status of the volume is set to Active. The HSM status is set to Active, and a PID value is set.

Figure 43 Creating managed volumes—Active status

The volume is managed via FMA now.

Stop a managed volume1. Right-click the corresponding volume entry to display the context menu.

Figure 44 Context menu for stopping managed volumes

2. Select the Stop item in the context menu.


The symbol of the volume is changed. The status of the volume is set to Not mounted. The HSM status is Inactive.

Figure 45 Stopping managed volumes—Not mounted status

3. No HSM operations (migrate, release, recall) are available now.

Start an unmounted volume again1. Right-click the corresponding volume entry to display the context menu.

Figure 46 Context menu for starting unmounted volumes again

2. Select the Start item in the context menu.The symbol of the volume is changed. The status of the volume is set to Active. The HSM status is set to Active, and a new PID value is set.

Figure 47 Starting unmounted volumes again—Active status

Delete a managed volume

CAUTION: Recall all migrated data before deleting the managed volume.


Figure 48 Context menu for stopping managed volumes

2. Select the Stop item in the context menu.The symbol of the volume is changed. The status of the volume is set to Not mounted. The HSM status is Inactive.

Figure 49 Stopping managed volumes—Not mounted status

50 Configuration


Figure 50 Context menu for deleting managed volumes

4. Select the Delete item in the context menu.The symbol of the volume is changed. The status of the volume is set to Not managed.

Figure 51 Deleting managed volumes—Not managed status

Volume properties

Figure 52 Context menu for displaying volume properties

Double-click the corresponding volume entry or select the Policies item in the context menu to display more information about the volume.

Figure 53 Properties dialog

NOTE: For further information about the other items in the context menu, refer to the Microsoft Windows manuals for the Microsoft Management Console (MMC).


FMA policiesFMA policies can be configured by selecting Managed Volumes and double-clicking the corresponding managed volume.

FMA’s policy page consists of the following four panes:

• Volume Property information• Volume serial number, mount point, and volume label• HSM status and process ID• Capacity, used, and free space

• Volume Parameters for disk space monitoring• Watermarks• Retention times• Exclusion list

• Scheduling for the file policy process• File Policy definitions

Figure 54 Computer Management dialog

Disk space monitoringFor each managed volume a disk space monitor is running, which regularly checks the disk space utilization and frees up space on the managed volume, when the high or critical watermark level is reached. This release process continues until the low watermark level is met or until no more file candidates for releasing are available.

When the disk utilization reaches the critical watermark, all files that are already copied to secondary storage (cached files) are candidates for releasing. In this case the retention time criteria are ignored.

52 Configuration

Watermark parameters:

Figure 55 Volume Parameters (Watermark tab) dialog

Retention time parameters:

Figure 56 Volume Parameters (Retention tab) dialog

An entry of a minimum time interval since a file was:

• modified: minimum time period since last modification that a migrated file is cached before it is marked as a release candidate.

• accessed:minimum time period since last access that a migrated file is cached before it is marked as a release candidate.

• recalled:minimum time period that a recalled file is cached before it is marked as a release candidate. The recall timestamp takes precedence of the modification- or access-timestamp.

Exclusion list:

Figure 57 Volume Parameters (Exclusion tab) dialog

Members in the exclusions list are ignored by the release process. An excluded directory must be specified by an absolute path.

The following wildcards are valid:

• * (none or any number of characters of any value)• ? (exactly one character of any value)

Examples:\directory1\*.doc\directory?\A???.xls\dir*\users


SchedulingFor each volume a schedule can be set up to automatically start the migration of files that are covered by any file policy. To manually start the file policy process, click the Start now button. The execution will start immediately, regardless of the schedule.

Figure 58 Scheduling dialog

Statistical information is always available for the last run of the file policy process and can be viewed by clicking the Last result button.

The schedule can be configured or changed by clicking the Change button.

If no start time is configured the file policy process is deactivated. If the max. duration check box is selected, the file policy execution time period is limited to the specified time interval.

Figure 59 Schedule Options dialog

File policyFMA automatically copies data from managed volumes to archives according to a schedule and the specified file policies.

A file policy contains the following policy parameters:

• Properties• Filtering (file selection criteria)• Archives

Figure 60 Policy Properties (Properties tab) dialog

54 Configuration

FilteringOn the Filtering tab page the following file-selection criteria can be configured:

• File age (access-, modification-, and creation timestamp).• File size.• File attributes like “Hidden,” “Archive,” and “System.”• Include and exclude rules.• Immediate release after copying the file to the archives.

Figure 61 Policy Properties (Filtering tab) dialog

The following wildcard characters are valid for included/excluded members:

• * (none or any number of characters of any value)• ? (exactly one character of any value)

Valid members of the inclusion or exclusion list are:

• Absolute path information with any of the above wildcards• File name with any of the above wildcards

If no selection criterion is specified, all files from the configured directory are migrated.

On the Archives tab page the administrator can configure up to four archive locations, where data is migrated to.

Figure 62 Policy Properties (Archives tab) dialog

FMA configuration for MS ClusterIf FMA is installed on a Microsoft Cluster system, additional configuration steps are necessary.


The following section describes the steps needed to support cluster operations.

1. Install FMA on all cluster nodes and reboot each note after finishing the installation.2. Start the FMA cluster wizard on any cluster node to create a cluster resource for the File Migration

Agent config service. Select Start > Programs > HP StorageWorks File Migration Agent > FMA Cluster Setup.

Figure 63 FMA Wizard (Cluster setup) dialog

a. Select the LocalSystem account for the File Migration Agent config service.

Figure 64 FMA Wizard (Technical user) dialog

56 Configuration

b. Assign the new cluster resource to the Cluster Group.


c. Select a name for the new cluster resource.



d. After clicking Finish the new source is automatically started by the cluster wizard.

Figure 67 FMA Wizard (Wizard Summary) dialog

3. Configure the backend archives (see page 38 for further information).

58 Configuration

NOTE: The option Ignore system name for storage descriptor creation should be activated on cluster systems.

Figure 68 Activating the Ignore system name for storage description creation option

4. Creating FMA managed volumes.The next step is the configuration of the FMA managed volumes. Please refer to ”Managing volumes” on page 46 for further information.

NOTE: An FMA managed volume must be explicitly configured on each node of the cluster.

Therefore, the cluster group, which contains the physical disk resource for the FMA managed volume, must be moved to each cluster node and marked as New in the FMA configuration (see ”Create a managed volume” on page 48).


CAUTION: Before FMA can be uninstalled from any cluster node, stop the File Migration Agent AFM service and the File Migration Agent service on all cluster nodes.

Afterwards the FMA Config Server cluster resource must be deleted from the Cluster Group to prevent the Cluster Group from failure.

Figure 69 Deleting the FMA Cfg Server resource from the Cluster Group

60 Configuration


4 OperatingThis chapter describes administrative tools that are available for the HP StorageWorks File Migration Agent (FMA).

FMA Job ManagerThe FMA Job Manager is a graphical user interface for managing migration and release jobs.

NOTE: The Job Manager functions will be replaced by FMA-MMC in one of the next versions of FMA. So we recommend to migrate Job Manager tasks to FMA policies (see page 51 for further information).

Figure 70 FMA Job Manager dialog

Table 8 FMA Job Manager dialog

Column Description

Job: Job name.

Description: Description of the job.

Path: Directory that is managed by FMA.

Archives: One or more archives when a migration operation is defined for this job.

Release: Marked with X when a release operation is defined for this job.

62 Operating

Starting FMA Job ManagerUse the shortcut Start > Programs > HP StorageWorks File Migration Agent > FMA Job Manager

Figure 71 Shortcut for starting FMA Job Manager

or start %InstallPath%\bin\JobMgr\JobMgr.exe to launch the FMA Job Manager.

Create a new jobTo create a new job, click the New button in the main dialog. The following dialog is divided into three registers:

• Job – specifies general policies for the job• Migration – migration-related policies• Release – release-related policies

Enter the required settings for the job in the following dialog and establish it by clicking the Save button.

Figure 72 Creating new jobs


Job parameters

Figure 73 Job dialog

Table 9 Job dialog

Setting Description

Job: Job name.

Descr: Description of the job.

Directory: Directory that is managed by FMA.

Log File: Specifies a log file.

The log file must be specified with a fully qualified path. Log files are created with the following (fixed) policies:

• The default name of the log file is jobname plus the extension .log.• Maximum size of a log file is 4 MB. If the files grows bigger than 4 MB, the file receives

the extension .000.• Old log files are named as JobName.nnn, where the lowest number contains the

youngest file:JobName.log -> JobName.000 -> JobName.001 -> ...

Ignore Files: Files that correspond to these descriptions are excluded from the job operations (comma separates).

Default:

• \System Volume Information • \HSM Volume Information

Verbose: Write informational messages to log file.

If the Verbose option is not selected, only error messages are written to the log file.

64 Operating

Migration parameters

Figure 74 Migration dialog

NOTE: If no archive is defined, the job contains no migration operation.

Usually files are migrated to a maximum of two FMA archives to have a automatic failover if an archive is not available.

Table 10 Migration dialog

Setting Description

Minimum file size: Define a minimum file size for the migration operation. The value can be specified in bytes, kilobytes, megabytes, or gigabytes.

Minimum time interval (modified):

Define minimum time interval since the file was last modified for the migration operation to start. The value can be specified in seconds, minutes, hours, or days.

Minimum time interval (accessed):

Define minimum time interval since the last file access for the migration operation to start. The value can be specified in seconds, minutes, hours, or days.

System: If this option is selected, no files with system attribute will be migrated.

Hidden: If this option is selected, no hidden files will be migrated.

Read Only: If this option is selected, no read-only files will be migrated.

Archive: If this option is selected, no files with active-archive bit will be migrated.

Compressed: If this option is selected, no files with active-compressed bit will be migrated.


Add archive for migration operationClick the Add button to add an archive for migration operation. After clicking, the following dialog is started.

Figure 75 Adding archives for migration operations

In the list box Archive(s), all configured archives are offered. Select the desired archive. A multiple selection is possible.

Delete an archive from the migration operation

Figure 76 Deleting archives from migration operations

To remove an archive from the list, you mark the corresponding archive and click the Delete button.

66 Operating

Release parameters

Figure 77 Release dialog

Figure 78 Retention times for release parameters

Table 11 Release dialog

Setting Description

Release Files: If this option is active, the job contains a release operation.

Retention time for migrated files:

Time period (crt) that changed files stay on disk before they are released. The value can be specified in seconds, minutes, hours, or days.

Retention time for recalled files:

Time period (rrt) that recalled and unchanged files stay on disk before they are released. The value can be specified in seconds, minutes, hours, or days.

Filesystem Watermark: Release process starts if the fill level (percentage) of the file system is reached. If the fill level is not reached, the process is immediately terminated without releasing any data.


Change job settingsTo change a job, select the job in the main dialog and click the Edit button. The following dialog appears.

Figure 79 Changing job settings

The dialog for changing a job is identical to the dialog for creating a job (see page 62), only the field Job is not editable in this case.

Delete a jobIf you want to delete a job, select this job in the main dialog and click the Delete button. After that, the following dialog appears.

Figure 80 Deleted job confirmation dialog

When clicking the OK button, the corresponding job will be removed. If you click the Cancel button, the selected job is not deleted. In the main dialog a multiple selection is possible.

Run a jobTo run a job, select the job in the main dialog and click the Run button.

After a short time, the output of the job is displayed in a DOS box. Enter Crtl-C if you want to abort a running job.

68 Operating

About FMA Job Manager

Figure 81 About FMA Job Manager dialog

Click the About button in the main dialog for more information about the FMA Job Manager.

Schedule FMA jobsThe FMA Job Manager stores the FMA jobs as CMD files (*.cmd) in the following directory:

%InstallPath%\jobs

for example:

C:\Program Files\Hewlett-Packard\HP FMA\jobs

Use the Planned Tasks utility in the Windows Control Panel to schedule these FMA jobs. Alternatively, the following command-line tools for planning FMA jobs are available on the Windows operating system:

Windows 2000

• at.exe command

Windows 2003

• at.exe command• schtasks.exe command

NOTE: See an example on page 125.

FMA Job Manager ConfigurationThe configuration of the FMA Job Manager is held in the following registry entries:

If the registry key JobPath is found by the FMA Job Manager, the associated value is used as directory, where the job scripts are stored.

This entry should be used in a cluster configuration. In this case, the JobPath should be located on a physical disk, which is configured as a cluster resource.

Table 12 [HKEY_LOCAL_MACHINE\SOFTWARE\GDS\FMA\JobMgr]

Setting Description

Height: Height of the Job Manager main dialog.

PosX: Start position (X coordinate in pixel) of the Job Manager main dialog.

PosY: Start position (Y coordinate in pixel) of the Job Manager main dialog.

DebugLevel: For internal use only.

JobPath: Path for the jobs of the FMA Job Manager.


A network name of the corresponding cluster resource must be registered. If a cluster node fails, the directory will then transfer automatically to an other node.

Command Line Interface (FMACLI)All file-based FMA commands take either a file name from the command line or a file name list (separated by CR/LF) from stdin. If no file name is specified, a file list from stdin is expected. All commands return zero on successful completion and non-zero in failure situations.

Informational output is written to stdout, error messages are written to stderr. The Command Line Interface (FMACLI) is implemented in the module FMACLI.exe. The Command Line Interface supports the following features:

Overview

• FMACLI is the command-line interface for data management.• FMACLI contains most available FMA kernel functions.• The FMACLI file name input options are:

• Single file via command line• File list (either via file or stdin)• Process directories recursively

• Informational output is written to stdout, errors are written to stderr. Keep this in mind when redirecting output for logging purposes.

FMACLI syntax

FMACLI command [global-options] [command-options]

70 Operating

Following commands of the FMA command line interface (FMACLI) are supported:

Table 13 Supported FMACLI commands

command Act[ivate] Repair metadata file IDs after restore from a backup. For further information, see page 71.

Arc[hive] This command is needed for the archive management. For further information, see page 73.

Cle[anup] This command reorganizes FMA archives. For further information, see page 75.

Era[se] This command deletes FMA metadata. For further information, see page 76.

Find This command find files and creates a file list. For further information see page 78.

Inf[o] Display FMA metadata. For further information, see page 79.

Mig[rate] Explicitly migrate a file to the specified archive. For further information, see page 83.

Pol[icy] Display or execute a file policy. For further information see page 85.

Rec[all] Explicitly recall data for a migrated file. For further information, see page 86.

Rel[ease] Explicitly release data for a file. For further information, see page 89.

RSA This command is needed for the RSA management. For further information, see page 93.

Sys[tem] This command is needed for the system management. For further information, see page 94.

Ver[ify] Display the result of the verification process. For further information, see page 95.

Vers[ion] Displays FMA version and build information. For further information see page 98.

Vol[ume] This command is needed for the volume management. For further information, see page 98.


FMACLI commandsEnter FMACLI or FMACLI --help to display a list of the available FMACLI commands.

Most commands can be shortened on the first three letters (for example: MIG, REL, REC, INF, ACT, VER, ERA, REP, ARC, RSA, SYS, VOL, CLE, POL). Only the VERSION command needs four letters (VERS) to define the short form. There is no short form for the FIND command available.

For a lot of command options (parameter of an FMACLI command) a short form is available. For example the option --help and -h are the same.

The command options of the FMACLI will be described in the next sections.

This section describes the commands that the FMACLI module supports.

ACTIVATEThe ACTIVATE command repairs metadata file IDs after restore.

FMACLI --help

usage: FMACLI <command> [command options]

commands:

---------

act[ivate] repair file-ids in metadata after restore

arc[hive] display a list of defined archives

cle[anup] remove the archived replica(s) of a deleted file

era[se] delete metadata from one or more file(s)

find find files and write found filenames to a file list

inf[o] display FMA relevant informations of one or more file(s)

mig[rate] migrate files to one or more archive(s)

pol[icy] display or execute a file policy

rec[all] recall one or more released file(s)

rel[ease] release one or more file(s)

rsa display a list of storage adapters and their status

sys[tem] display FMA relevant data and settings

ver[ify] display the result of the verification process

vers[ion] display version info

vol[ume] display a list of managed volumes

For further informations about commands please use FMACLI <command> --help

72 Operating

Synopsis

DescriptionThe ACTIVATE command sets the file ID in the metadata to fit the current ID of the file. This function needs to be called whenever the file ID of the file changes. This function is usually required after a restore of metadata.

Possible use of the ACTIVATE command is after a restore with a third-party backup software or to move FMA metadata from one computer to another.

Do not try to activate files that have an unknown status.

The ACTIVATE command with the option --off is used for disabling files. This function is required when files need to be relocated on FMA managed volumes.

Disabling files ensures that no entry is written to FMA’s garbage collection container when files are deleted. As a result, the corresponding archive copy will not be deleted during an FMA cleanup run.

Recall operations are rejected on “disabled” files.

Options

FMACLI Act[ivate] [--help | -h]

[{--logfile | -L} <logfile>

[--log-info-messages | -V]]

[--verbose | -v]

[<file>] | [{--filelist] | -f} <filelist>]

[{--recursive | -r} <path>]

[--oem-file-format | --unicode-file-format |

--ansi-file-format | --utf8-file-format]

[{--minimum-file-size | -S} <n>b|k|m|g]

[{--minimum-access-time | -A} <n>d|h|m|s]

[{--minimum-write-time | -W} <n>d|h|m|s]

[--exclude-system]

[--exclude-hidden]

[--exclude-read-only]

[--exclude-archive]

[--exclude-compressed]

[--off]

[-F <outlist>]

Table 14 ACTIVATE command options

Options Description

--help Displays the online help for the ACTIVATE command.

-h

--logfile <logfile> Specifies a log file.


• Maximum size is 4 MB. If the files grows bigger than 4 MB, the file is switched.

• Old log files are named as logfile.nnn, where the lowest number contains the youngest file:logfile.log -> logfile.000 -> logfile.001 -> ...

-L <logfile>

--log-info-message Write informational messages to log file. This option is meaningful only in combination with the -L / --logfile option. (Default: only errors are written to log)-V


To define an operation either an explicit file name or a file list that contains file names must be specified. If neither a file nor a file list is specified the FMACLI tries to read the file list from stdin.

In general you should use Unicode or UTF-8 formats only. The OEM and ANSI formats are for compatibility reasons only. OEM and ANSI cannot display all character sets.

Example

ARCHIVEThe ARCHIVE command lists the status of the FMA archives.

--verbose Verbose mode (display informational messages)

-v

<file> Specify a file name. The usage of wildcards like * or ? is possible.

--filelist <filelist> Specify an input file list (default: stdin). Files in the file list are separated by CR/LF. File names can be relative or fully qualified. If you plan to run scripts, use fully qualified names only.-f <filelist>

--recursive <path> Recursion into subdirectories starting at <path>.

-r <path>

--oem-file-format The input file list is in OEM format.

--unicode-file-format The input file list is in Unicode format.

--ansi-file-format The input file list is in ANSI format.

--utf8-file-format The input file list is in UTF-8 format (default).

--minimum-file-size <n>b|k|m|g Define a minimum file size (n) for the specified operation.

The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g).

-S <n>b|k|m|g

--minimum-access-time <n>d|h|m|s

Define minimum time (n) since file was last accessed for the specified operation.

The value can be specified in seconds (s), minutes (m), hours (h), or days (d).

-A <n>d|h|m|s

--minimum-write-time <n>d|h|m|s

Define minimum time (n) since file was last modified for the specified operation minimum file age.


-W <n>d|h|m|s

--exclude-system Exclude system files.

--exclude-hidden Exclude hidden files.

--exclude-read-only Exclude read-only files.

--exclude-archive Exclude files with an active-archive bit.

--exclude-compressed Exclude files with an active-compressed bit.

--off Disable file.

-F <outlist> Creates a file list (outlist) as output.

FMACLI Activate D:\ASC\MyFile.doc

Table 14 ACTIVATE command options (continued)

Options Description

74 Operating

Synopsis

DescriptionThe ARCHIVE command displays an archive list.

Options

Example

Output

Description of columns

FMACLI Arc[hive] [--help | -h]



[--verbose | -v]

Table 15 ARCHIVE command options

Options Description

--help Displays the online help for the ARCHIVE command.

-h





-L <logfile>



-v

FMACLI Arc

Archive List: Id Status Archive Type PI Name Migrated Description---- -------- ------------ ---- ------------------- -------------- -----------------------0001 OK RSA-FTP 90 FTP01 n/a MO-ERF Data Year 19920002 OK RSA-FTP 90 FTP02 n/a MO-ERF Data Year 19930003 OK RSA-CIFS 100 CIFS01 2.05 GB MO-ERF Data Year 19940004 OK RSA-CIFS 100 CIFS02 1.67 GB MO-ERF Data Year 1995

Table 16 Column descriptions

Column Output

Id Archive Number

Status Archive Status (currently not used)

Archive Type Type of the Remote Storage Adapter (RSA-FTP, -CIFS or -RISS)

PI Performance Index

Name Name of the FMA Archive


CLEANUPThe CLEANUP command reorganizes FMA archives.

Synopsis

DescriptionUse the CLEANUP command to reorganize FMA archives. This means you will remove copies of deleted files from the archives.

Options

Example

This command will clean up all files that were deleted more than 30 days ago.

Migrated Migrated Data (not available for FTP as Remote Storage Adapter)

Description Description of the FMA Archive

Table 16 Column descriptions (continued)

Column Output

FMACLI Cle[anup] [--help | -h]



[--verbose | -v]

[--expiration <n>d|h|m|s]

Table 17 CLEANUP command options

Options Description

--help Displays the online help for the CLEANUP command.

-h





-L <logfile>



-v

--expiration <n> Delete all files in all archives, which have been deleted more than an expiration value <n> ago.

The value <n> can be specified in seconds (s), minutes (m), hours (h), or days (d).

This option is mandatory, if the -h|--help option is not used.

FMACLI Cleanup --expiration 30d

76 Operating

ERASEThe ERASE command deletes FMA metadata from a file.

Synopsis

DescriptionThe ERASE command deletes FMA metadata from a system.

CAUTION: The command deletes data without confirmation.

Before erasing a file’s metadata, recall the file to avoid data loss.

Options

FMACLI Era[se] [--help | -h]



[--verbose | -v]








[--exclude-system]

[--exclude-hidden]


[--exclude-archive]


[[--primary-metadata | -Mp] |

[--secondary-metadata | -Ma] |

[--all-metadata | -Mb]]

[--force ]

[-F <outlist>]

Table 18 ERASE command options

Options Description

--help Displays the online help for the ERASE command.

-h





-L <logfile>



-v




Example




-r <path>







-S <n>b|k|m|g




-A <n>d|h|m|s




-W <n>d|h|m|s






--primary-metadata Deletes primary metadata (extended attributes).

-Mp

--secondary-metadata Deletes secondary metadata (alternate data stream).

-Ma

--all-metadata Deletes all metadata (default).

-Mb

--force Allows the deletion of offline files.


FMACLI Erase D:\ABC\MyFile.doc

Table 18 ERASE command options (continued)

Options Description

78 Operating

FINDThe FIND command creates a list of files selected according to a certain filter and saves it to a specified file.

Synopsis

DescriptionThe FIND command searches for files in a directory hierarchy by evaluating the given search criteria and saves the absolute path and file name of the matching files to a file specified by the -F option. The -F option is mandatory.

Options

FMACLI Find [--help | -h]



[<file>]





[--exclude-system]

[--exclude-hidden]


[--exclude-archive]


[--ignore-files <ignorefile>]

[--storage-location {offline|online}]

-F <outlist>



Table 19 FIND command options

Options Description

--help Displays the online help for the FIND command.

-h





-L <logfile>




-r <path>



-S <n>b|k|m|g


In general you should use Unicode or UTF-8 formats for output list only. The OEM and ANSI formats are for compatibility reasons only. OEM and ANSI cannot write all character sets.

Example

INFOThe INFO command displays FMA metadata.




-A <n>d|h|m|s




-W <n>d|h|m|s






--ignore-files <ignorefile> Exclude file (ignorefile). The usage of wildcards like * or ? is possible.

--storage-location online|offline

Check offline file attribute.






FMACLI Find -r D:\Data --storage-location offline -F OfflineFiles.lst

Table 19 FIND command options (continued)

Options Description

80 Operating

Synopsis

DescriptionThis command displays HSM metadata.

Options

FMACLI Inf[o] [--help | -h]



[--verbose | -v]








[--exclude-system]

[--exclude-hidden]


[--exclude-archive]


[--long | -l]

[-F <outlist>]

Table 20 INFO command options

Options Description

--help Displays the online help for the INFO command.

-h





-L <logfile>



-v




-r <path>






Example 1

Output





-S <n>b|k|m|g




-A <n>d|h|m|s




-W <n>d|h|m|s






--long Display all available information (long output). In the short version (default), only one line per file is displayed.

-l


FMACLI Info -r D:\*.*

Last Modification Size Attributes Status Name

------------------ ---------- ----------- ------- ------------------2005-02-02 17:09:28 18755 -A---O----F OFF(1) D:\ASC\EULA.rtf2006-04-21 16:00:14 1088 -A--------- MOD D:\ASC\fma.txt2005-07-27 15:42:54 4344083 -A--------- SAV(1) D:\ASC\FMAAdmGd.pdf2006-04-07 13:56:38 5482 -A--------- D:\ASC\Readme.txt2006-05-04 06:49:36 102400 -A--------- SAV(3) D:\ASC\MyFile.doc . . .12 files succeeded0 files failed0 files were processed earlier22579118080 bytes processed

Table 20 INFO command options (continued)

Options Description

82 Operating


Example 2

Output

Table 21 INFO command output for example 1

Column Output

Last Modification: Last modification date and time.

Size: File size.

Attributes: File attributes:

A - ArchiveR - Read-onlyS - SystemH - HiddenT - TempF - SparseO - Offline

Status: FMA status:

<blank> - unmanagedOFF - OfflineMOD - ModifiedSAV - MigratedINA - Inactive(n) - Number of valid copies

Name: Fully qualified file name.

FMACLI Info -r D:\*.* -l

.

.

.

File: D:\ASC\MyFile.doc

File info:

state=SAV(1), attr=-A--------F, size=102400, generations=0001

Filter file info:

SysFileID=0001000000000038, AppFileID=0000000000000000, ChgTime=2006-02-01

13:49:36,766, FileSize=104965100, CLEAN, ONLINE

File generation info:

size=104965100, last_mig=2006-02-01 13:49:36,766, last_rec=2006-05-03

15:11:04,268, attr=-A---------, locations=1

File location info:

ArchiveID=1, ArcPoolID=1, dwNumRec=1, storage_handle_descr=Id: 2 Version: 2

Filesize: 104965444 Last Write Time: 20060503130432 File name: MyFile.doc

12 files succeeded

0 files failed

0 files were processed earlier

22579118080 bytes processed


MIGRATEThe MIGRATE command explicitly migrates a file to the specified archive.

Synopsis

DescriptionThis command creates copies of file data on alternate locations. The data remains on the local hard disk.

Options

FMACLI Mig[rate] [--help | -h]



[--verbose | -v]








[--exclude-system]

[--exclude-hidden]


[--exclude-archive]


[{--archive | -a} <arc>] | [--archives <arc1,...>]

[{--maximum-copies | -n} <copies>]

[--release]

[-F <outlist>]

Table 22 MIGRATE command options

Options Description

--help Displays the online help for the MIGRATE command.

-h





-L <logfile>



-v



84 Operating




-r <path>







-S <n>b|k|m|g




-A <n>d|h|m|s




-W <n>d|h|m|s






--archive <arc> Name of the archive where the file is stored. This parameter is mandatory for the migration command.

-a <arc>

--archives <arc1, ...> Specify a list of archives with maximum 4 archives (“arc1, arc2, ... arcN”)

--maximum-copies <copies> Set the maximum number of archive copies of a file.

-n <copies>

--release Do releasing the files after a successfully migration.


Table 22 MIGRATE command options (continued)

Options Description


Examples

Figure 82 MIGRATE command example

POLICYThe POLICY command displays or executes file policies.

Synopsis

FMACLI Migrate D:\Test\file.dat -a Arc01

FMACLI Migrate -f c:\temp\miglist.dat -a Arc01

FMACLI Migrate D:\Data -A 4d --archive Arc01

FMACLI Migrate D:\Data -A --archives "Arc01, Arc02, Arc03"

FMACLI Migrate -r D:\Data --archive Arc01 --release

FMACLI Pol[icy] [--help | -h]



[--verbose | -v]

[--name <polname> | --all | --run <polname>]

86 Operating

DescriptionThis command displays or executes file policies. A policy defines the HSM operations (migrate, release) on managed volumes based on various file selection criteria (see ”File policy” on page 53).

Options

Example

RECALLThe RECALL command explicitly recalls data for a released file.

Table 23 POLICY command options

Options Description

--help Displays the online help for the POLICY command.

-h





-L <logfile>



-v

--name <polname> Display a specific policy.

--all Display all policies.

--run <polname> Execute a specific policy.

FMACLI POL --name Reports

GUID: Volume{78a17197-d505-11da-a579-806e6f6e6963}

Policy name: Reports

(Enabled)

Description: Weekly Reports

Path: \Reports2006\

List of archives: IAF01;NAS01

Filtering:

Size: 1024

Time stamp:

Release flag = TRUE

List of excludes: \System Volume Information\*;\Hsm Volume Information\*;


Synopsis

DescriptionThis command recalls a released file. A recall can also be invoked by a double-click in the Windows File Explorer or by an open to the file via an application.

Options

FMACLI Rec[all] [--help | -h]



[--verbose | -v]








[--exclude-system]

[--exclude-hidden]


[--exclude-archive]


[-F <outlist>]

Table 24 RECALL command options

Options Description

--help Displays the online help for the RECALL command.

-h





-L <logfile>



-v




-r <path>



88 Operating







-S <n>b|k|m|g




-A <n>d|h|m|s




-W <n>d|h|m|s







Table 24 RECALL command options (continued)

Options Description


Example

Figure 83 RECALL command example

RELEASEThe RELEASE command explicitly releases data for a file.

90 Operating

Synopsis

DescriptionThe RELEASE command gains space on a managed volume by converting already migrated files to stubfiles. If the command detects that not enough archived copies exist, the release operation is not performed. For releasing a file, both retention times (crt and rrt) and the number of copies (mc) must be fulfilled.

Files with a size of below 1024 Byte will never be released.

Options

FMACLI Rel[ease] [--help | -h]



[--verbose | -v]








[--exclude-system]

[--exclude-hidden]


[--exclude-archive]


[{--minimum-copies | -n} <mc>]

[{--changed-retention-time | -t} <crt>d|h|m|s]

[{--read-retention-time | -T} <rrt>d|h|m|s]

[{--low-watermark | -U} <nn>]

[{--high-watermark | -u} <nn>]

[-F <outlist>]

Table 25 RELEASE command options

Options Description

--help Displays the online help for the RELEASE command.

-h





-L <logfile>



-v





-r <path>







-S <n>b|k|m|g




-A <n>d|h|m|s




-W <n>d|h|m|s






--changed-retention-time <crt>m|h|d

Changed Retention Time (crt).

Time period in minutes (m), hours (h), or days (d) that changed files stay on disk before they are released.-t <crt>m|h|d

--read-retention-time <rrt>m|h|d

Release Retention Time (rrt).

Time period in minutes (m), hours (h), or days (d) that recalled and unchanged files stay on disk before they are released-T <rrt>m|h|d

--minimum-copies <mc> Minimum number of copies in the archive before a file can be released.

-n <mc>

--high-watermark <nn> High-Watermark value (nn).

The release process starts if the fill level (percentage) of the file system is reached. If the fill level is not reached, the process is immediately terminated without releasing any data.

-u <nn>

--low-watermark <nn> Low-Watermark value (nn)

The release process is stopped if the low-watermark (percentage) of the file system is reached.

-U <nn>


Table 25 RELEASE command options (continued)

Options Description

92 Operating

Figure 84 Retention times for RELEASE command



Examples

If the file MyFile.doc was modified, it stays 1 day on disk before it becomes a release candidate.

If the file MyFile.doc was not modified, it stays for another 10 days on disk before it becomes a release candidate.

Table 26 Variable definitions for Figure 84

Variable Description

crt This is the time period for migrated and changed files. All files will remain on disk for the specified time period before they become a release candidate.

rrt This is the time period for recalled and unchanged files. All recalled and unchanged files will remain on disk for the specified time period before they become again a release candidate.

FMACLI Release D:\ASC\MyFile.doc -t 1d -T 10d -n 2


Figure 85 RELEASE command example

In this case the file MyFile.doc will be released, when three copies are available on different archives.

RSAThe RSA command lists the status of the remote storage adapter.

Synopsis

DescriptionThe RSA command displays the remote storage adapter status.

FMACLI Rsa [--help | -h]



[--verbose | -v]

94 Operating

Options

Example

Output

SYSTEMThe SYSTEM command displays system information.

Synopsis

DescriptionThe SYSTEM command displays system information like version, license, and other FMA settings.

Options

Table 27 RSA command options

Options Description

--help Displays the online help for the RSA command.

-h





-L <logfile>



-v

FMACLI RSA

# Type Capabs Name RSA Description

- ---- -------- ---------- ---------------- ------------------------------

0 0 00000000 RSA-CIFS RsaCIFS.dll "Storage ... specifications"

1 0 00000000 RSA-FTP RsaFtp.dll "Storage on ftp server"

2 0 00000000 RSA-RISS RsaRISS.dll "Storage on HP RISS"

FMACLI Sys[tem] [--help | -h]



[--verbose | -v]

Table 28 SYSTEM command options

Options Description

--help Displays the online help for the SYSTEM command.

-h


Example

Output

VERIFYThe VERIFY command displays the result of the verification process.





-L <logfile>



-v

FMACLI Sys

HP Storage Works File Migration Agent

Version 2.1.0.1109

HP File Migration Agent command line interface

Copyright (C) 2002-2006 GRAU Data Storage

Copyright (C) 2006 Hewlett-Packard Company

Version of HP File Migration Agent kernel 2. 1. 0. 1109

System status = 0, installPath=[C:\Program Files\Hewlett-Packard\HP FMA]

HSM API Version = 2.1.0-1109 ""

License Information:

=====================

+ Base Product License Evaluation license expiration in 26 days

+ OpenStorage Option Evaluation license,capacity (avail/used) 1000 GB/0 GB.

+ Cluster Option Evaluation license.

Config:

Loglevel for eventlog: LOG_WARNING

Loglevel for logfile: LOG_INFO

Number of log files: 100

Options:=00000000

Exiting with code: 0

Table 28 SYSTEM command options (continued)

Options Description

96 Operating

Synopsis

DescriptionLocal Check (Level 1)

If verification option local is specified, the following checks are performed:

• Load primary metadata (this itself will check if the file ID matches with the metadata).• Load secondary metadata and compare with local metadata.• Check whether offline files have metadata.• Check for offline files with non-zero file size.• Check if the file is saved (backend copies are up-to-date).

Remote Check (Level 2)

If verification option remote is specified, the following checks are performed:

• Local verification.• Each link to backend data storage is verified using the RSAVerify method. The validation algorithm is

part of the remote storage adapter implementation. All copies for all available generations are checked. Locally modified files are processed the same way.

Options

FMACLI Ver[ify] [--help | -h]



[--verbose | -v]








[--exclude-system]

[--exclude-hidden]


[--exclude-archive]


[{--local-checks | -o local}]

[{--remote-checks | -o remote}]

[-F <outlist>]

Table 29 VERIFY command options

Options Description

--help Displays the online help for the VERIFY command.

-h





-L <logfile>






-v




-r <path>







-S <n>b|k|m|g




-A <n>d|h|m|s




-W <n>d|h|m|s






--local-checks Verify archive contents.

Operation level of verify operation is local (default).-o local

--remote-checks Verify archive contents.

Operation level of verify operation is remote.-o remote


Table 29 VERIFY command options (continued)

Options Description

98 Operating

Example

VERSIONThe VERSION command displays version and build information about the installed FMA.

Synopsis

DescriptionThe VERSION command displays version and build information about the installed FMA.

Options

Example

Output

VOLUMEThe VOLUME command displays a list about the managed volumes.

FMACLI Verify D:\ABC\MyFile.doc -o remote

FMACLI Vers[ion] [--help | -h]



[--verbose | -v]

Table 30 VERSION command options

Options Description

--help Displays the online help for the VERSION command.

-h





-L <logfile>



-v

FMACLI Vers


Version 2.1.0.1109





Synopsis

DescriptionThe VOLUME command displays information about the managed volumes.

Options

Example

Output


FMACLI Vol[ume] [--help | -h]



[--verbose | -v]

Table 31 VOLUME command options

Options Description

--help Displays the online help for the VOLUME command.

-h





-L <logfile>



-v

FMACLI Vol

Table 32 Description of columns

Column Output

Id Index number

M FMA status:

• <blank>: unmanaged

• X: managed

100 Operating

Result codesFMACLI returns 0 if successful. If a fatal error condition occurs, negative values are returned. Positive result codes show warning conditions.

FMA Explorer plug-inFMA provides a shell extension for the Windows Explorer. The Explorer plug-in can be used to manually migrate, release or recall file or folder objects from a managed volume on the local system.

Volume Status Possible values:

• Not managed

• Active

• Not mounted

• Error

• Restricted

• Cannot be managed

• Need reboot

HSM Status Possible values:

• Active

• Inactive

• Unknown

Label Volume label

FS File system of this volume (always NTFS by managed volumes)

Serial Serial number of the volume

Migrated Migrated data

Capacity Disk space (max. available)

Free Space Free disk space

% Free disk space in percent

PID HSM process ID of the volume manager process

GUID Global unique identifier (36 characters)

Table 32 Description of columns (continued)

Column Output

Table 33 Result codes

Return value Description

(0) No error occurred.

(1) Watermark not reached.

(2) Error occurred during operation. The command was executed successfully, but some errors occurred.

Example: Some of the files could not be processed.

(-1) A generic error occurred. Check error messages (stderr) for more information.

(-2) An invalid parameter was specified. Check error messages to determine the bad parameter.

(-3) An invalid command was specified.

(-4) FMA has found a bad configuration. This is caused by invalid archive configuration or duplicate archive IDs.


The HSM commands can be accessed through the context menu by right-clicking a file or folder in Windows Explorer. It is also possible to select many files in one directory or one or many directories.

Figure 86 FMA Explorer context menu

To perform HSM operations using the Windows Explorer, select the files or directories on the managed volume and right-click the selection and then select a command.

If an HSM command takes more than a few seconds a progress bar appears to inform the user that the operation is taking place.

After an HSM operation has been finished, a dialog window, which displays the results of the operation, appears.

Figure 87 Processing results dialog

102 Operating

Migrating files or foldersSelect the objects for migrating and right-click your selection. Then select the Migrate command on the context menu and the archive, to which FMA should copy the data.

Figure 88 Migrating from context menu

Releasing files or foldersSelect the objects for releasing and right-click your selection. Then select the Release command on the context menu.

Figure 89 Releasing from context menu

An additional dialog appears when releasing folders for configuring the release options such as the minimum number of copies in the archives, retention time periods and watermarks. The Files are immediately released without requesting release options.

Configure the release parameters according to your needs and click OK to start the release operation.

Figure 90 Release options dialog


Recalling files or foldersSelect the objects for releasing and right-click your selection. Then select the Recall command on the context menu.

Figure 91 Recalling from context menu

Viewing FMA metadataThe FMA Explorer plug-in allows the user to view metadata information on Explorer’s detail view or on an additional property sheet called “FMA.”

To add additional FMA metadata columns to Explorer’s detail view, right-click one of the column headers and select the More command from the menu. A Choose Details dialog box appears that lists the available columns for the folder and allows which columns to display.

FMA metadata columns are:

• State: Migrated, Modified.Known problem: Since Microsoft does not support to add “application specific” column information to the Explorer’s detail view for files, which are offline, no FMA specific information can be displayed, when a file has been released.

• Copies: Number of archive copies.• Last recall: Timestamp of last recall operation. • Recalls: Total number of recalls.

104 Operating

Selecting the Properties item on a file launches the property sheet, which allows to view FMA metadata information on the FMA property page.

Figure 92 Viewing metadata

The figure on the right side shows the FMA metadata information. For further information about FMA metadata see ”INFO” on page 79.

Register/unregister the Explorer plug-inThe FMA Explorer plug-in is automatically registered during the installation process. If you want to remove the plug-in from the Explorer, run the command:

To add the plug-in to the Explorer, run:

FMAFileUtilDescription

FMA stores data in the archive filer in its own internal archive format. This must be done to store all available file metadata in heterogeneous operating system environments. Otherwise meta information might be lost.

Example: Store Windows files on an FSE Archive running Linux.

regsvr32 /u hsmext.dll

regsvr32 hsmext.dll


NOTE: This only applies to files stored using RSA-FTP adapter.

This does not apply to CIFS or HP StorageWorks Reference Information Storage System (RISS) archives.

Figure 93 Storing data in an FSE Archive

The FMAFileUtil is a command-line-based program to convert NTFS files into the FMA Storage Format and vice versa.

User interfaceUsage

Options

If none of these options are used, all messages of type ERROR are written to stdout.

FmaFileUtil [options] command [command-options] <arguments>

Table 34 FmaFileUtil options

Option Description

-v Verbose output.

Write messages of type ERROR, WARNING, or INFO to stdout.

-L <Logfile> Log file output.

Write messages of type ERROR to the log file.

-V Verbose log file output.

Write messages of type ERROR, WARNING, or INFO to the log file.

-H Displays usage information for command.

106 Operating

Commands

Command options

Arguments (pack command)

Arguments (unpack command)

ExamplesPacks the file File001.dat into the file File001.dat.p:

Packs all files in directory d:\Dir001 into directory d:\tmp\Dir001.p:

Table 35 FmaFileUtil commands

Command Description

pack | p Create a packed file (new Format) based on an NTFS file

Input is an NTFS file, output is a file in the FMA Storage Format. All NTFS file information is included.

unpack | u Create an NTFS file based on a packed file.

Input is a packed file, output is an NTFS file. All NTFS streams saved in the packed file are written into the created NTFS file.

Table 36 FmaFileUtil command-options

Option Description

-f <Filelist> All files listed in Filelist will be converted.

-o Overwrite existing destination files. Default is that no files will be overwritten.

-r Recurse into directories.

-p Preserve timestamps

When unpacking a file the original creation- and modification-timestamp is restored.

If this option is used without the -o option, FmaFileUtil only resets the timestamps of the destination file (dFile) to the timestamps preserved in the source file (sFile).

Table 37 FmaFileUtil arguments (pack command)

Option Description

<sFile> <dFile>

Packs the source file (sFile) to destination file (dFile).

<sDir> <dDir> Packs all files in the source directory (sDir) to the destination directory (dDir). The new files have the same name.

Table 38 FmaFileUtil arguments (unpack command)

Option Description

<sFile> <dFile>

Unpacks the source file (sFile) to destination file (dFile).

<sDir> <dDir> Unpacks all files in the source directory (sDir) to the destination directory (dDir). The new files have the same name.

FmaFileUtil pack File001.dat File001.dat.p

FmaFileUtil pack d:\Dir001 d:\tmp\Dir001.p


Packs all files in directory d:\Dir001 and its subdirectories into directory d:\tmp\Dir001.p:

Unpacks the file File001.dat.p into the file File001.dat and restores the original timestamps. If the file File001.dat already exists, the file File001.dat will be overwritten:

Resets the timestamps of the destination file File001.dat to the timestamps preserved in the source file File001.dat.p:

Packs all files in directory d:\Dir001 into directory d:\tmp\Dir001.p. If a destination file exists, it will be overwritten:

Unpacks the file File001.dat.p into the file File001.dat:

Unpacks all files in directory d:\Dir001.p into directory d:\tmp\Dir001:

Unpacks all files in directory d:\Dir001.p and its subdirectories into directory d:\tmp\Dir001:

Unpacks all files in directory d:\Dir001.p into directory d:\tmp\Dir001. If a destination file exists, it will be overwritten:

Log filesFMA log file

The FMA writes all system messages in a log file named hsm.log. The default location of the log file is:

%InstallPath%\log\hsm.log

for example:

C:\Program Files\Hewlett-Packard\HP FMA\log\hsm.log

The FMA log file is created with the following (fixed) policies:

• Maximum size is 20 MB. If the file grows bigger than 20 MB, the file is switched.• Old log files are named hsm.nnn, where the lowest number contains the newest file:

hsm.log -> hsm.000 -> hsm.001 -> ... -> hsm.099 • A maximum of 100 old log files (hsm.000 - hsm.099) are stored.

FmaFileUtil pack -r d:\Dir001 d:\tmp\Dir001.p

FmaFileUtil unpack -p -o File001.dat.p File001.dat

FmaFileUtil unpack -p File001.dat.p File001.dat

FmaFileUtil pack -o d:\Dir001 d:\tmp\Dir001.p

FmaFileUtil unpack File001.dat.p File001.dat

FmaFileUtil unpack d:\Dir001.p d:\tmp\Dir001

FmaFileUtil unpack -r d:\Dir001.p d:\tmp\Dir001

FmaFileUtil unpack -o d:\Dir001.p d:\tmp\Dir001

108 Operating

The layout of the FMA log file entries are as follows.

Figure 94 Layout of FMA log file entries

FMACLITo configure the log file option of the FMACLI command, use the global option --Logfile. Use the --log-info-messages option for verbose log.

NOTE: The options of the FMACLI command are case-sensitive. It is highly recommended that you log all actions.

For further information about the --Logfile option in the FMACLI command, see page 71.

FMA Job ManagerTo configure the log file option of the FMA Job Manager, activate the LogFile setting in the job settings.

NOTE: For further information about the LogFile setting in the FMA Job Manager, see page 63.

Windows event logBy default, warning and error messages are recorded in the Windows application event log. By changing the log settings, informational messages can also be logged into the event log.

NOTE: Writing informational messages to the event log is not recommended.


5 Best practicesCreate a new HP StorageWorks File Migration Agent (FMA) archiveFMA archive configuration for a Windows archivePrerequisites

For archiving data to a Windows-based HP StorageWorks File System Extender (FSE) Archive, the GDS FTP-Server needs to be set up on the FSE Archive as described in ”Using GDS FTP-Server” on page 135.

The GDS FTP-Server comes with its own user management facilities. Therefore, the FTP authentication process is completely controlled by the GDS FTP-Server and no Windows domain user account needs to be created for the FTP client access.

Because the GDS FTP-Server runs as a Windows service, user access to the FTP server’s home directory can be restricted to designated administrators of the domain.

The absolute path to the archive directory is composed of the root directory, which is specified in the configuration file ftp_server.cfg of the GDS FTP-Server, and the root path set up in the FMA’s RSA-FTP configuration dialog. If a root path is defined on the client side (FMA), the administrator needs to create this subdirectory during the GDS FTP-Server configuration.

The absolute path to the archive directory in the following example should be:

c:\fsefs1\data1\fma

Example of the GDS FTP-Server configuration file ftp_server.cfg file

[default]

RootDirectory = c:\fsefs1

Port = 21

UserFile = C:\program files\Hewlett-Packard\FTPServer\GDSFtpServerUsers

LogFile = C:\program files\Hewlett-Packard\FTPServer\GDSFtpServer.log

110 Best practices

FMA RSA-FTP Configuration dialog


For archiving data directly to c:\fsefs1, the root path of the FMA RSA-FTP configuration menu needs to be left blank.

Verification of the GDS FTP-Server configuration can be done with any FTP client software.

After the FTP server side has been tested successfully, the next step is to attach FMA as an FTP client to the new archive storage location. For this, the following actions are necessary:

1. Start FMA MMC Snap-In from Windows Start menu.(Start > Programs > HP StorageWorks File Migration Agent > FMA Configuration)

2. Select the Archives item.3. Start the context menu and select the item New. A new dialog will pop up.4. Enter the name for the new archive. The archive name must be unique.5. Select RSA-FTP as RSA module.6. Enter the performance index. The smaller the index, the higher the priority.7. Enter an archive description.8. Click the OK button. A new dialog will pop up.9. Enter the following settings corresponding to your requirements:

• Host or IP address (primary and secondary host)• Port (default: 21)• User• Password• Root path• FTP server • Connection timeout in ms• Data read timeout in ms


• Select various options10.Click the Save button.

The new FMA archive is shown in the FMA MMC Snap-In list.11. The creation of a new FMA archive is finished.

If the backend archive is replicated outside of FMA via some replication mechanism such as the HP Continuous Access (HP CA) for the FSE Archive, the host name or IP address of the secondary system needs to be added to the entry field Secondary Host/IP.

Figure 96 Replication archive (Windows) example

In this case recall requests are switched to the secondary system, when the primary archive is not accessible.

112 Best practices

Note that the primary and secondary archive configuration (FTP user ID, FTP server configuration and archive directory structure) must be identical.

Figure 97 Rsa Configuration dialog

NOTE: For further information about managing FMA archives, see page 38.

FMA archive configuration for an FSE/Linux archiveFor archiving data to a Linux-based FSE Archive, the VSFTPD needs to be set up on the FSE Archive as described in ”Configuration of VSFTPD on SuSE Linux” on page 129.

The absolute path to the archive directory is composed of the FTP user’s home directory and the relative path, which is configured in the FMA RSA-FTP configuration dialog.

The first part of the absolute path to the archive is specified during the creation of the FTP user on the Linux system. The command

defines the directory /fma/hsmfs1 as the home directory for the FTP user fma. The second part of the absolute path to the archive directory is set up in the FMA RSA-FTP configuration dialog.

useradd -m -k /bin/false -d /fma/hmsfs1 -g fma -s /bin/false fma


In this example, the complete path to the archive directory is /fma/hsmfs1/data1/fma.


After the FTP server side has been tested successfully, the next step is to attach FMA as an FTP client to the new archive storage location. For this, the following actions are necessary:


2. Select the Archives item.3. Start the context menu and select the item New. A new dialog will pop up.4. Enter the name for the new archive. Info: The archive name must be unique.5. Select RSA-FTP as RSA module.6. Enter the performance index. Info: The smaller the index, the higher the priority.7. Enter an archive description.8. Click the OK button. A new dialog will pop up.9. Enter the following settings corresponding to your requirements:

• Host or IP address (primary and secondary host)• Port (default: 21)• User• Password• Root path• FTP server• Connection timeout in ms• Data read timeout in ms• Select various options

10.Click the Save button.The new FMA archive is shown in the FMA MMC Snap-In list.

114 Best practices

11. The creation of a new FMA archive is finished.

If the backend archive is replicated outside of FMA via some replication mechanism such as the HP CA for the FSE Archive, the host name or IP address of the secondary system needs to be added to the entry field Secondary Host/IP.

Figure 99 Replication archive (Linux) example

In this case recall requests are switched to the secondary system, when the primary archive is not accessible.


Note that the primary and secondary archive configuration (FTP user ID, FTP server configuration and archive directory structure) must be identical.


NOTE: For further information about managing FMA archives, see page 38.

FMA archive configuration for a CIFS-based NAS deviceFor archiving data to a CIFS-based NAS device, the archive folder on the NAS device needs to be shared on the network. FMA only supports NTFS file systems on CIFS archives.

After sharing the appropriate folder on the NAS device, the NTFS permissions on the folder must be set to FULL Control for the FMA technical user account (see ”Technical user” on page 24) or the corresponding group.

The absolute path to the archive location can be configured in FMA’s RSA-CIFS dialog.

116 Best practices

Example:

If the share “archives” has been created on the NAS device NAS_DEVICE, subsequent archives can be set up through FMA RSA-CIFS configuration:

\\NAS_DEVICE\archives\users \\NAS_DEVICE\archives\projects

Figure 101 Rsa Configuration—RSA-CIFS


If the backend archive is replicated outside of FMA via some replication mechanism the UNC path of the target location needs to be added to the entry field Secondary Archive. In this case recall requests are switched to the secondary archive location, when the primary archive is not accessible.

Figure 102 Rsa Configuration dialog—RSA-CIFS

Figure 103 Replication archive (Microsoft Server) example

118 Best practices

FMA archive configuration for RISSFMA is using the ILM Object Storage API interface for accessing the HP StorageWorks Reference Information Storage System (RISS) as a backend archive. (For further information on integration requirements, see ”Archive store configuration” on page 129.)

Any documents with a size of up to 1.58 GB can be sent from an FMA managed volume to the RISS. Depending on FMA’s RSA-RISS configuration, a specific set of metadata about the document can be attached to the binary object. The following metadata is attached by FMA:

• File modification date• MIME type of the file• Full path name in UNC notation• File security depending on FMA’s recipients options• Subject (file name without path and file extension)

FMA’s recipients options and the Recipients field entries determine which RISS repositories are granted access to the binary object. The access information is retrieved from the document’s Access Control List (ACL).


Documents will be automatically retrieved from the RISS, when a user or application accesses the document on the FMA managed volume. To search for documents, users can use the RISS Web Interface embedded in a standard RISS solution.

If a RISS is mirrored on a remote location using the RISS Replication Manager, the host name or IP address of the replica site needs to be entered to the input field Secondary RISS. In this case FMA will retrieve data from the replica site, when the primary RISS is not available. If the primary RISS site can not accept any incoming traffic, FMA does not redirect the data traffic to the replica site.



FMA only supports one replica site, which is built by one-way (Active/Passive) RISS remote replication services.

Figure 106 Replication archive (RISS) example

120 Best practices

Create a new managed volumeTo create a new managed volume:


2. Select the Managed Volumes item.All NTFS volumes will be displayed.

3. Right-click the corresponding volume entry to display the context menu.4. Select the New item in the context menu.5. Reboot the FMA system now.6. The creation of a new managed volume is finished.

NOTE: For further information about managing volumes, see page 46.

Create file policiesTo create and schedule migration rules on a managed volume:


2. Select the Managed Volumes item.3. Double-click the corresponding volume entry to display the Policy Configuration window. 4. Right-click the Policies pane to display the context menu and select New.5. Enter a policy name and policy description, and select the path, for which the policy should be

applied. 6. Set up your migration rules on the Filtering tab.

Example:• Migrate all files that have not been accessed for 180 days and release the files immediately. • Files with the extension *.tmp are excluded from migration.

Figure 107 New Policy - Properties (Filtering) dialog

7. Select the archives, where data needs to be stored, and click the OK button.


8. After all policies are configured for the managed volume, set up the schedule for policy processing by clicking the Change button in the Scheduling pane.

Figure 108 Scheduling dialog

9. Policy processing can be scheduled to be executed hourly, daily, weekly or monthly and at any point in time to suit your business needs.Examples: • Start policies every day at 10:00 p.m.


• Start policies every Saturday at 01:00 a.m.(Select Every day on Day of month, if policies should run on certain days of week.)


• Start policies on the 1st of every month.(Select Every week day, if policies should run on certain days of month.)


122 Best practices

Create disk usage monitoringTo set up the disk space monitor on a managed volume:


2. Select the Managed Volumes item.3. Double-click the corresponding volume entry to display the Policy Configuration window.4. Files will be released when the high or critical watermark threshold is reached. The policy ensures that

the monitored managed volume never causes a DISK FULL error. The release operation is based on the configured retention times and the configuration for excluded files and directories.Example:For an optimal usage of the managed volume, the following watermarks are defined:

Figure 112 Volume Properties (Watermarks) dialog

The disk space is monitored every hour and when the disk utilization reaches 85%, files which have not been accessed for 180 days will be released until the low watermark is reached. If the critical watermark is hit, the release process is no longer limited by the defined retention criteria until the high watermark is reached.

Figure 113 Volume Properties (Retention) dialog

If the retention time period is based on the modification timestamp of a file, it is recommended to specify a retention time for recalled files to avoid unnecessary recalls.

Figure 114 Volume Properties (Retention) dialog

In this example recalled files are kept online for a minimum of 7 days, although the files have not been modified for 60 days.This configuration guarantees a fast access to files for a certain time period since the files have been recalled.


Files which should always be online, can be excluded.

Figure 115 Volume Properties (Exclusion) dialog

Determine FMA software versionTo display the current version of FMA software components:

• Enter FMACLI sys in the command line. On top of the output, the current version is displayed:

• Or view the version information for (almost) each FMA file by looking at the files in the Windows File Explorer. Right-click the file, click Properties, and click the Version tab.

• Or click the About HP FMA item in the menu of the FMA MMC Snap-In.

Figure 116 Info dialog

• Or click the About button of the FMA Job Manager to obtain the FMA software version.

Figure 117 About FMA Job Manager dialog

• For further information, see the Readme.txt file. To read the Readme.txt file, use the shortcut:Start > Programs > HP StorageWorks File Migration Agent > FMA Readme


Version 2.1.0.1109




124 Best practices

Migrate filesTo migrate files:

Use the FMACLI command-line utility to migrate files.

In the following example, the testdir directory will be migrated into the myArchive archive:

To migrate a directory to more than one archives (max. 4), apply:

To migrate a directory with immediately release operation after successfully migrating of the directory, apply:

Additionally it is possible to migrate files via FMA Explorer plug-in. For further information see ”FMA Explorer plug-in” on page 100.

Release filesTo release files:

Use the FMACLI command-line utility to release files.

In the following example, the testdir directory will be released:


Recall filesTo recall files:

Use the FMACLI command-line utility to recall files.

In the following example, the testdir directory will be recalled:


Set a high-watermark for migration or releasesTo set a high-watermark for migration or release:

Use the FMACLI command-line utility. In the following example, the testdir directory will be released when the fill level of the file system (85 percent) is reached.

FMACLI migrate f:\testdir\test.* -a myArchive

FMACLI migrate -r f:\testdir -a myArchive

FMACLI migrate -r f:\testdir -a myArchive, myArchive02

FMACLI migrate -r f:\testdir -a myArchive -n1 --release

FMACLI release f:\testdir\test.* -n 1

FMACLI release -r f:\testdir -n 1

FMACLI recall f:\testdir\test.*

FMACLI recall -r f:\testdir

FMACLI release -r f:\testdir -u 85


Verify data filesTo verify FMA metadata information:

Use the FMACLI command-line utility to check whether the FMA metadata of a file object is consistent.

To check all files of a directory, apply:

To check if the link to the archive copy of a file is valid, apply:

Create an FMA jobTo create an FMA job:

1. Start FMA Job Manager.2. Click the New button.3. Enter the job settings (for more details, see page 61).4. Click the Save button.

NOTE: For further information about creating FMA jobs, see page 62.

Schedule FMA commandsTo schedule an FMA command:

Use the AT command-line utility of Windows. In the following example, an FMA release command will be started at 10 a.m.:

NOTE: For further information about the AT command-line utility, see the documentation for Microsoft Windows 2000.

You can use the Scheduled Task Wizard in the Windows Control Panel (Start > Control Panel > Scheduled Tasks) for these tasks also.

Schedule FMA jobsTo schedule FMA jobs:

The FMA Job Manager stores the FMA jobs as CMD files (*.cmd) in the following directory:

%InstallPath%\jobs

Use the Scheduled Task Wizard in the Windows Control Panel (Start > Control Panel > Planned/Scheduled Tasks) for scheduling the FMA job.

Alternatively, you can use the following command-line tools for scheduling an FMA job.

In this example, the FMA job will start every Sunday (Su) at 03:00 a.m.

FMACLI verify f:\testdir\test.dat -o local

FMACLI verify -r f:\testdir -o local

FMACLI verify f:\testdir\test.dat -o remote

at 10:00 "FMACLI release -r f:\testdir -n 2"

126 Best practices

Windows 2000:

Windows 2003:

NOTE: For further information about the AT or SCHTasks command-line utility, see the documentation for Microsoft Windows.

Backup/restore concept for FMA managed volumes FMA is a hierarchical storage management (HSM) solution and, therefore, no replacement for data backup. The major purpose for backup is to ensure recovery of data on the server if a disaster occurs. The main goal of HSM is to better manage data storage costs.

FMA migrates files to other forms of storage and creates copies of files, but does not back up files on the server. When FMA releases files, only stubs are left on the managed file system, which point FMA to the exact location in the backend storage, enabling file retrieval and user access.

To provide data protection, third-party backup applications are absolutely essential for disaster recovery. The qualified third-party backup applications (see ”Backup/restore” on page 142) are HSM-aware, which means that stubfiles are backed up without causing recalls from backend storage. Because FMA stubfiles are created as Windows sparse files, a further requirement for backup applications is the appropriate processing of sparse files to avoid heavy network traffic and to minimize the backup window.

There are two concepts for organizing the back up of FMA managed volumes.

The first one is to protect all data on the server. To accomplish this, the backup process needs to be set up to the “incremental forever” mode and the release of FMA jobs needs to be scheduled after the backup process to ensure that files are backed up before becoming a stubfile. In this case it is most likely that the capacity of the saved data will exceed the capacity of the original locations on the managed volumes. Therefore release operations will be triggered during a disaster recovery or massive restore of saved data. It is recommended to adjust the monitoring time interval (for example, 10 minutes) and watermarks accordingly.

Concept two is ideal when fast backup/restore processing is of primary importance. In this scenario, data backup needs to be configured to periodically run full backups with subsequent incremental backups. This approach reduces the backup data volume and backup/restore time period compared to a non-HSM managed filesystem with the same data capacity and number of files.

CAUTION: When backing up stubfiles, it is very important that FMA’s cleanup expiration time must be set equal to the expiration time that is configured for the backed up files. The FMA cleanup function removes the archive copies of deleted files depending on the specified cleanup expiration time. In this context, the expiration time, which is specified for the backend storage, also needs to be configured appropriately.

FMA does not support multiple references to one archive file copy. Only one stubfile can be linked to one archive copy. As a result of this restriction, restore operations of files to an alternate location are not permitted by FMA. Backed up files from FMA managed volumes can only be restored to their original location.

Relocating data to another FMA managed volumePrerequisites

Copying data to another FMA managed volume needs to be executed by the robocopy.exe command-line tool, which is available from Microsoft’s Resource Kit.

at 03:00 /every:Su "C:\Program Files\Hewlett-Packard\HP FMA\jobs\MyJob.cmd"

schtasks /create /ST 03:00 /D Su /TN "C:\Progr..\MyJob.cmd"


To avoid recall operations during copying of your data, it is recommended that you create a duplicate of the robocopy utility with the name NoRecRobocopy.exe and add the process name NoRecRobocopy to the list of modules for which FMA allows a physical view to the file system.

Therefore, the following steps are necessary:

1. Install the robocopy.exe utility Version XP010 or higher by installing Microsoft’s Resource Kit.

2. Create the NoRecRobocopy command:

3. Add the process name NoRecRobocopy to FMA’s registry key.HKEY_LOCAL_MACHINE \SOFTWARE \Hewlett-Packard \HP FMA \IgnoreModules

4. Restart the FMA services• File Migration Agent config service• File Migration Agent service

NOTE: When moving data to other server systems, ensure that the FMA archive configuration is identical on all systems.

Relocating data procedureThis section describes the steps that are needed to copy a subdirectory from an FMA managed volume to another FMA managed volume either local or remote. Assume that you want to relocate a subdirectory named e:\homedir to f:\homedir.

1. Stop sharing the subdirectory to avoid user access during the relocation process.2. Make sure that your data has been backed up.3. Disable the files in the source directory.

Description:When a “disabled” file is deleted, no entry is written to the “garbage collection” container and, therefore, the corresponding archive copy will not be deleted during an FMA cleanup run. Additionally, recall operations are rejected on “disabled” files.

(Check whether the files are set to DIS (DISABLED), use the command FMACLI info -r e:\homedir.)

4. Use the appropriate NoRecRobocopy command now.Example:

(Check that all files have been copied successfully to our target location.)

-------------------------------------------------------------

ROBOCOPY :: Robust File Copy for Windows :: Version XP010

-------------------------------------------------------------

copy <InstPath>\robocopy.exe %SYSTEMROOT%\system32\NoRecRobocopy.exe

FMACLI act --off -r e:\homedir

NoRecRobocopy e:\homedir f:\homedir /E /SEC /COPYALL

128 Best practices

5. Activate the files in the target directory.Description:Activating a file means that FMA’s metadata is synchronized to the new system file ID. This step enables the link to the archive copy.

6. Delete the source directory

Relocating a large number of filesIf the relocation process is required for a large number of files and only a short production downtime is available, the command for disabling the files could also be executed after the target directory has been enabled for user access and before deleting the source directory. In this case, the downtime is decreased by the processing time of the command for disabling the files.

This procedure is feasible under the following conditions:

• User and/or application access to the source directory must be permanently revoked before starting the relocation procedure.

• User and/or access to the target directory must be avoided until all files have been activated using the command fmacli act.

• The administrator must guarantee that the command for disabling the files in the source directory has been executed before deleting them.

Steps for relocating a large number of files:

1. Revoke access to the file systems of the source and target directories.2. Make sure that your data has been backed up.3. Copy your data using the NoRecRobocopy command and check that all files have been copied

successfully.Example:

4. Activate the files in the target location.

5. Grant access to your target location.6. Deactivate the files in the source location.

7. Delete the files in the source location.

FMACLI act -r f:\homedir

NoRecRobocopy e:\homedir f:\homedir /E /SEC /COPYALL

FMACLI act -r f:\homedir

FMACLI act --off -r e:\homedir


A AppendixArchive store configurationFTP configuration for HP StorageWorks File System Extender (ftpd)Introduction

The RSA-FTP module is one of the remote storage adapters used in the HP StorageWorks File Migration Agent (FMA) software. This chapter explains the configuration of the RSA-FTP module in general and the configuration of the supported FTP servers.

A (technical) user on a Linux (UNIX) system must be set up to use the FTP service. This section also explains how to do this on the various UNIX platforms.

General topics for using the RSA-FTP moduleMinimum requirements for FTP serversThe RSA-FTP modules uses the following FTP commands:

• STOR (Defined in RFC765)• RETR (Defined in RFC765)• MDTM (Extension)• SIZE (Extension)

These four commands must be available for supported FTP servers.

Configuration of VSFTPD on SuSE LinuxSetting up a new group and userThe following statement will add a new user group (with restricted rights) to the system. Enter at the system prompt:

To add a user with minimal rights, enter at the system prompt:

Example:

By default, the new user account is not activated. The password needs to be changed to activate the account. Enter at the system prompt:

and enter a new password. Default: fmafma

groupadd fma

useradd -m -k /bin/false -d <PartRoot> -g fma -s /bin/false fma

Table 39 Parameters for useradd command

Parameter Description

-d <PartRoot> Is the root directory of HP StorageWorks File System Extender (FSE) (Linux).

-s /bin/false Prevents a login via Telnet.

-g fma Lists the primary group of the FMA user.

useradd -m -k /bin/false -d /fse -g fma -s /bin/false/ fma

passwd fma

130 Appendix

Take ownership of the PartitionRoot

Activation of INETDTo activate inetd, start the YaST utility with the corresponding parameter:

Check whether inetd is already active. If not, activate inetd.

Configuration of VSFTPD1. Activate the FTP server vsftpd in file /etc/inetd.conf. The entry exists by default, but is not

activated.2. Create a file called /etc/vsftpd.userlist.

In this file, all users that are allowed to access the FTP server need to be added. Here the user fma is added.

3. Next the configuration file (/etc/vsftpd.conf) of the FTP server must be modified:

NOTE:• inetd must be triggered to reread its configuration file:

• To avoid problems due to transferring these configuration files from a DOS file system to a UNIX file system (LF <--> CRLF), please convert all files with the dos2unix utilty.Example:

chown -R fma:fma <PartitionRoot>

yast inetd

/etc/vsftpd.userlist

fma

/etc/vsftpd.conf

#------ Configuration used for FTPAccess of FMA

# Guenter Kruschina 07.03.05 Hewlett-Packard Co.

anonymous_enable=NO

local_enable=YES

write_enable=YES

dirmessage_enable=YES

xferlog_enable=YES

chroot_local_user=YES

userlist_enable=YES

userlist_deny=NO

userlist_file=/etc/vsftpd.userlist

local_umask=027

killall -HUP inetd

dos2unix vsftpd.conf

dos2unix vsftpd.userlist


Configuration for LogRotateLogRotate is a utility for managing log files. The VSFTPD Server is normally configured to write the log file: /var/log/vsftpd.log. To avoid an uncontrolled growth of this file, LogRotate is used. On SuSE Linux, LogRotate should be installed by default.

To setup LogRotate, the following steps must be executed:

1. Create the file: /etc/cron.daily/logrotate.

2. Make the file executable.

3. Create the file: /etc/logrotate.d/fma

Configuration of VSFTPD on Red Hat Linux1. If you have performed a Red Hat standard installation, vsftpd will probably not be installed on the

system (check whether /usr/sbin/vsftpd exists). To install vsftpd afterwards you have to mount Red Hat Installation CD #1 and change into directory RedHat/RPMS where you can find the package vsftpd-1.2.1-3.i386.rpm, which can be added to the system by performing.

2. If vsftpd installation has succeeded you can continue creating a technical user and group:Creating the group fma:

3. Creating the technical user fma_user:

/etc/cron.daily/logrotate

#!/bin/sh

/usr/sbin/logrotate /etc/logrotate.conf

chmod +x /etc/cron.daily/logrotate

/etc/logrotate.d/fma

# Configuration for logrotate

/var/log/vsftpd.log

{

compress

size=500M

rotate=5

}

Table 40 Parameters for LogRotate command


compress Old versions of log files are compressed with gzip by default.

size[=]size Log files are rotated when they grow bigger then size bytes. If size is followed by M, the size if assumed to be in megabytes. If k is used, the size is in kilobytes. Therefore, size 100, size 100k, and size 100M are all valid.

rotate[=]count Log files are rotated count times before being removed. If count is 0, old versions are removed rather than rotated.

rpm -ivh vsftpd-1.2.1-3.i386.rpm

groupadd fma

132 Appendix

• Path: Mount point of the FSE partition, for instance: /fse/fsefs01• fma_user: User fmauser belongs to group fma

4. Change the password for user fma_user:

It is recommended to take fmafma as password5. To allow user fma_user writing into the FSE partition you should change the user and group

assignment of the FSE partition by:

FSE mount point, for instance /fse/fsefs016. The installation of vsftpd creates file /etc/vsftpd.user_list, which contains all users being

allowed to access the machine via FTP.User fma_user has to be added to this file.

7. Next step is to adjust the vsftpd configuration file, which can be found under /etc/vsftpd/vsftpd.conf.You have to check and adjust at least following parameters:

8. If you do not find some of those parameters in the configuration file, you have to add them.If parameter xferlog_enable is set to YES, you also have to un-comment parameter xferlog_file=/var/log/vsftpd.log.

9. If all those steps are done, you can start the appropriate services.Restarting inetd: /etc/init.d/xinitd restartStarting vsftpd: /etc/init.d/vsftpd start

10.As already mentioned, the start/stop script will be installed into /etc/init.d/vsftpd. The installation also creates according symbolic links into the different directories for the different run levels. For instance /etc/rc2.d/K50vsftpd.Because vsftpd is dependent from module xinetd (K50xinetd), the standard installation will execute vsftpd start before xinitd start at next boot time, which will fail. Therefore, you have to delete all symbolic links and add them properly by creating an appropriate symbolic link in the different run level directories.For instance: Change into directory /etc/rc2.d, delete K50vsftpd, create new link by performing ln -s ../init.d/vsftpd S99vsftpd.

11. Now you can proceed with creating the log rotation as described in the FSE product documentation.

useradd -d Path -g fma fma_user

passwd fma_user

chown -R fma_user:fma

anonymous_enable=NO

local_enable=YES

write_enable=YES

dirmessage_enable=YES

xferlog_enable=YES

chroot_local_user=YES

userlist_enable=YES

userlist_deny=NO

userlist_file=/etc/vsftpd.user_list

local_umask=027


Configuration of PROFTPD on Sun SolarisSetting up a new group and userThe following statement will add a new user group (with restricted rights) to the system. Enter at the system prompt:

To add a user with minimal rights, enter at the system prompt:

Example:

By default, the new user account is not activated. The password needs to be changed to activate the account. Enter at the system prompt:

and enter a new password. Default: fmafma

groupadd fma

useradd -m -k /bin/false -d <PartRoot> -g fma -s /bin/false fma

Table 41 Parameters for useradd command


-d <PartRoot> Is the root directory of FSE (Linux).

-s /bin/false Prevents a login via Telnet.

-g fma Lists the primary group of the FMA user.

useradd -m -k /bin/false -d /fse -g fma -s /bin/false/ fma

passwd fma

134 Appendix

Configuration of PROFTPDModify the Proftpd-Configuration file /etc/proftpd.conf as follows:

/etc/proftpd.conf

#

ServerName "ProFTPD Default Installation"

ServerType inetd

DefaultServer on

#

# Some basic defaults

#

Port 21

Umask 002

TimeoutLogin 120

TimeoutIdle 600

TimeoutNoTransfer 900

TimeoutStalled 3600

<Global>

AllowOverwrite on

RootLogin on

</Global>

<Limit LOGIN>

AllowAll

Allow from all # alternative host or net

</Limit>

# Logging options

#

TransferLog /var/adm/proftpd.log

#

# Some logging formats

#

LogFormat default "%h %l %u %t \"%r\" %s %b"

LogFormat auth "%v [%P] %h %t \"%r\" %s"

LogFormat write "%h %l %u %t \"%r\" %s %b"

# Set the user and group that the server normally runs at.

User nobody

Group nogroup

#


Using GDS FTP-ServerInstall the GDS FTP-ServerStarting installation

For installation, please start setup.exe from the installation CD-ROM. The setup program of the GDS FTP-Server first initializes the installation files. After this, you receive information about the version and the manufacturer of the GDS FTP-Server.

Figure 118 InstallShield Wizard Welcome dialog

If you still have other applications running at this time, it is strongly recommended that you close these applications before you continue with the set up of the FTP Server. Click the Cancel button and finish the FTP Server Setup. After that, close all open applications and then start the FTP Server Setup again.

If no other application is opened, you can proceed with the installation process by clicking the Next button.

136 Appendix

Customer information

Figure 119 Customer Information dialog

Install the GDS FTP-Server for anyone who uses this computer. Click the Next button to continue.

Installation path

In this dialog, enter the setup type. When clicking the Complete option, the GDS FTP-Server will be installed in the default directory.

Figure 120 Setup Type dialog

The default installation path is %ProgramPath%\Hewlett-Packard\FTPServer. When clicking the Custom option, another dialog box is opened where you can specify the installation path of the GDS FTP-Server.

After this step, proceed to the installation process by clicking the Next button.


Copying the GDS FTP-Server software

Now the setup of the GDS FTP-Server will start unpacking and copying the program and configuration files to disk.

Figure 121 Installing GDS FTP-Server dialog

Figure 122 InstallShield Wizard Completed dialog

After this, the installation of the GDS FTP-Server is completed. Click Finish to exit the setup of the GDS FTP-Server.

138 Appendix

Configure the GDS FTP-Server1. Create an FTP user.

For creating an FTP user, open a command window and change into the installation directory of the GDS FTP-Server. Use the htpasswd command as follows:

Example:

2. Setup the configuration file.Open the configuration file ftp_server.cfg with a text editor and enter the corresponding parameters:Example:

3. Create an NT service.Define the GDS FTP-Server as a Windows NT service. Use the following command:

4. Start the FTP service.To start the FTP service, use the following command:

Uninstall the GDS FTP-Server1. Open a command window and change into the installation directory of the GDS FTP-Server.2. Stop the GDS FTP-Server with the following command:

3. Remove the FTP service with the following command:

htpasswd -c GDSFtpServerUsers <newuser>

htpasswd -c GDSFtpServerUsers FmaUser

[default]

RootDirectory = g:\FtpRoot

Port = 21

UserFile = c:\program files\Hewlett-Packard\FTPServer\GDSFtpServerUsers

LogFile = c:\program files\Hewlett-Packard\FTPServer\GDSFtpServer.log

GDSFtpServer ftp_server.cfg -i srvany.exe

net start GDSFtpServer

net stop GDSFtpServer

GDSFtpServer -r


4. Start the Windows software manager (Add/Remove Programs) to run the uninstallation.Select the HP StorageWorks GDSFtpServer and click Remove Program (see Figure 123).

Figure 123 Add/Remove Programs dialog

RISS configurationIntegration requirements

Applications integrating with HP StorageWorks Reference Information Storage System (RISS) must have TCP/IP access to port 25 and port 80. To store email, the application requires the virtual IP addresses for each storage domain. To use the ILM Object Storage API, the application can use any HTTP IP address. These attributes are defined when the RISS device is initially configured and installed in the customer’s IT environment.

Configuring RISS devicesAn application requires a RISS repository and user to view BLOBs through the API. The application might require additional separate repositories and users if end users are using the RISS Web Interface to search for documents stored through the ILM Object Storage API. At a minimum, all BLOBs should be stored in the repository for the application. Applications can make information available to the individual users who own files if those users also have accounts automatically populated on RISS from the installation’s user management LDAP server.

See the HP StorageWorks Reference Information Storage System Administrator Guide for instructions to add users, data repositories, and ACLs between users and repositories. The administrator guide is available on the documentation CD.

Configuring application serversIf data will be stored with Windows Security Descriptor information, the application server must be configured with access to the active-directory server on the customer’s network.

Required configurationThe application integrator or the application must install the RISSBIBO.LIB and RISSBIBO.DLL file in an appropriate, secure location on the application server. The application must be configured for the IP address of the RISS device that will be used for archiving.

If the RISS-specific configuration changes, the application administrator is responsible for setting configuration changes in the ILM Object Storage API.

140 Appendix

Third-party product compatibility listLast Update: May 2006

Anti-virusFMA’s interoperability with anti-virus scanners has been successfully tested for the following products.

Symantec AntiVirus

McAfee VirusScan

Table 42 Symantec AntiVirus specifications

Product name: AntiVirus

Manufacturer: Symantec

Version: Corporate Edition 9.0 and 10.0

Supported FMA versions: 2.x

Operating system: Windows 2000, Windows 2003

Restrictions: The feature “scan files opened for backup” is not supported. Therefore, the option “opened for backup” needs to be switched off in Symantec AntiVirus “Auto-Protect Advanced Options” menu.

Remark: To more efficiently scan files maintained by Hierarchical Storage Management (HSM), Symantec AntiVirus allows configuration options for on-demand or scheduled scans.

The appropriate settings for FMA are:

• Skip offline and sparse • Open files with Backup semantics

Table 43 McAfee VirusScan specifications

Product name: VirusScan

Manufacturer: McAfee

Version: Enterprise 8.0



Restrictions: None

Remark: For proper interoperability, it is recommended to not select the option:

Scan files that have been migrated to storage

The option is located in the menu:

• -> VirusScan On-Demand Scan Properties • -> Advanced properties • -> Miscellaneous


Sophos Anti-Virus

ServerProtect

eTrust AntiVirus

TrendMicro OfficeScan

Table 44 Sophos Anti-Virus specifications

Product name: Sophos Anti-Virus

Manufacturer: Sophos

Version: 5.01, 5.1



Restrictions: The realtime scan option “on-write access” is not supported.

Remark: None

Table 45 ServerProtect specifications

Product name: ServerProtect

Manufacturer: TrendMicro

Version: 5.58



Restrictions: None

Remark: Opening the property page of an offline file will trigger a file recall from remote storage.

Table 46 eTrust AntiVirus specifications

Product name: eTrust AntiVirus Scanner

Manufacturer: Computer Associates International

Version: 7.0, 8.0



Restrictions: None

Remark: Because eTrust changes the access timestamp of a file, the release operation should be based on the modification timestamp and the last recall timestamp.

Table 47 TrendMicro OfficeScan specifications

Product name: OfficeScan

Manufacturer: TrendMicro

Version: 7.0



142 Appendix

Backup/restoreFMA’s interoperability with backup/restore applications has been successfully tested for file system backup/restore operations with the following products.

Additional features, like data archiving or disk image creation, were not subject of interoperability tests.

BackupExec

BrightStor ArcServe

Data Protector

Restrictions: The realtime scan options “scan outgoing files” and “scan incoming and outgoing files” is not supported, when the backup application does not use VSS.

Remark: Opening the property page of an offline file will trigger a file recall from remote storage.

Table 47 TrendMicro OfficeScan specifications (continued)

Table 48 BackupExec specifications

Product name: BackupExec

Manufacturer: Veritas

Version: 10.0



Restrictions: 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.

Remark: None

Table 49 BrightStor ArcServe specifications

Product name: BrightStor ArcServe Backup

Manufacturer: Computer Associates

Version: 11.1, 11.5



Restrictions: None

Remark: None

Table 50 Data Protector specifications

Product name: Data Protector

Manufacturer: HP

Version: 5.50




Remark: None


NetBackup

Networker

NetVault

Table 51 NetBackup specifications

Product name: NetBackup Enterprise Server


Version: 5.1, 6.0




Remark: None

Table 52 Networker specifications

Product name: Networker

Manufacturer: EMC

Version: 7.2




Remark: None

Table 53 NetVault specifications

Product name: NetVault

Manufacturer: BakBone

Version: 7.11




Remark: None

144 Appendix

MS VSS

Tivoli Storage Manager

Table 54 MS VSS specifications

Product name: Volume Shadow Copy Services (VSS)

Manufacturer: Microsoft

Version: A component of Windows 2003


Operating system: Windows 2003


1. Restoring previous versions from VSS to the original location Offline files that were restored from snapshots must be set to a “CLEAN” state by FMA administrative tools.No restrictions exist to the restore of online files.

2. Viewing previous versions from VSS Viewing previous versions of files that were offline during the volume snapshooting is not supported.

3. Copying previous versions from VSS to a different location Copying previous versions from VSS to a different location is not supported by FMA.

Remark: Volume snapshots can be taken on FMA managed volumes; there is no negative interference between VSS and FMA.

Taking volume shadow copies will not initiate recalls of already released files. But FMA 2.0 does not provide a writer component to VSS for synchronizing volume shadow copy operations.

Therefore, a consistency of open files cannot be guaranteed when taking volume snapshots.

Table 55 Tivoli Storage Manager specifications

Product name: Tivoli Storage Manager

Manufacturer: IBM

Version: 5.3.x



Restrictions: 1. FMA does not support “file activation” for files, which have been restored to a new location. Restoring files is only supported to their original location.

2. The TSM Logical Volume Snapshot Agent is not supported in combination with FMA.

3. TSM client needs to be set up for “compress objects” mode.

(Edit > Preferences > Backup > compress objects)4. FMA does not support TSM backup in combination with Sophos Anti-Virus

realtime-scanning.

Remark: Create and set the following registry key to 1

HKEY_LOCAL_MACHINE \SOFTWARE \Hewlett-Packard\HP FMA \ADSMetadataStorage


Galaxy Backup & Recovery

Quota/encryptionStorageExec

DefragmentationO & O Defrag

MS Defragmentation

Table 56 Galaxy Backup & Recovery specifications

Product name: Galaxy Backup & Recovery

Manufacturer: CommVault Systems

Version: 6.1



Restrictions: FMA does not support “file activation” for files, which have been restored to a new location. Restoring files is only supported to their original location.

Remark: None

Table 57 StorageExec specifications

Product name: StorageExec


Version: 5.0



Restrictions: Only passive limits on FMA managed volumes are supported.

Remark: None

Table 58 O & O Defrag specifications

Product name: O & O Defrag

Manufacturer: O & O Software

Version: 8.0



Restrictions: None

Remark: None

Table 59 MS Defragmentation specifications

Product name: Defragmentation


Version: Windows 2000, Windows 2003



146 Appendix

IndexServerMS IndexServer

Error codesAbstract

This internal document describes FMA-related error messages and potential reasons and solutions (where they exist). This document is a “living” document, which means it is updated whenever new information is available.

FMA error handlingFMA modules return either a WIN32-defined error code or an FMA-defined error code. The FMA error codes starts at 0x00010000 (65536).

FMA error codes

Restrictions: None

Remark: None

Table 59 MS Defragmentation specifications (continued)

Table 60 MS IndexServer specifications

Product name: IndexServer


Version: Windows 2000, Windows 2003

Supported FMA versions: 2.1


Restrictions: None (interoperable, no recalls)

Remark: The IndexServer only keeps index informations of online files. Index informations are lost by releasing files.

FMA error: 65537

Code (hex): 0x00010001

Text: File is migrated.

Description: The file in question is already migrated. This message is for information only.

FMA error: 65538

Code (hex): 0x00010002

Text: File is not migrated.

Description: The file is not migrated and, therefore, cannot be released or recalled.

FMA error: 65539

Code (hex): 0x00010003

Text: File is released.

Description: The file is released and, therefore, cannot be migrated.


FMA error: 65540

Code (hex): 0x00010004

Text: File is online.

Description: The file is already online and, therefore, cannot be recalled.

FMA error: 65541

Code (hex): 0x00010005

Text: Metadata not found.

Description: The file does not contain FMA metadata.

FMA error: 65542

Code (hex): 0x00010006

Text: File is not expired.

Description: File cannot be released since the retention time has not expired.

FMA error: 65543

Code (hex): 0x00010007

Text: Not enough copies.

Description: A file is to be released, but not enough copies exist. The number of required copies is specified using the -n option in the release command.

FMA error: 65544

Code (hex): 0x00010008

Text: Metadata copy cannot be created.

Description: A metadata copy cannot be created.

FMA error: 65545

Code (hex): 0x00010009

Text: Recalled file was not empty, conflict file was created.

Description: A file that is recalled was not empty. The recall was done and a copy of the original file was saved.

FMA error: 65546

Code (hex): 0x0001000A

Text: HSM-operation on intermediate file was ignored.

Description: HSM operations on intermediate files (conflict and temporary recall) are ignored.

FMA error: 65547

Code (hex): 0x0001000B

Text: FMA directory was ignored.

Description: -

148 Appendix

FMA error: 65548

Code (hex): 0x0001000C

Text: FMA file active.

Description: -

FMA error: 65549

Code (hex): 0x0001000D

Text: FMA file inactive.

Description: -

FMA error: 65550

Code (hex): 0x0001000E

Text: FMA metadata recovered.

Description: -

FMA error: 65551

Code (hex): 0x0001000F

Text: FMA file disabled.

Description: -

FMA error: 65808

Code (hex): 0x00010110

Text: Archive key not found in registry.

Description: The FMA archive key was not found.

FMA error: 65809

Code (hex): 0x00010111

Text: Invalid archive configuration.

Description: (not used)

FMA error: 65810

Code (hex): 0x00010112

Text: Archive unknown.

Description: The given archive name (FMACLI option -a) is not defined in the registry. Maybe the name was misspelled or the configuration is not available.

FMA error: 65811

Code (hex): 0x00010113

Text: Duplicate archive ID.

Description: A duplicate archive ID was found in the system. This situation may lead to data loss. The error needs to be corrected before any HSM operations can be started.


FMA error: 65825

Code (hex): 0x00010121

Text: RSA-Library cannot be loaded.

Description: The defined library module cannot be loaded.

FMA error: 65826

Code (hex): 0x00010122

Text: Required entry point in RSA library not found.

Description: A mandatory function was not found in the specified RSA library.

Probable causes:

• old version of library file• corrupted library file

FMA error: 65841

Code (hex): 0x00010131

Text: Metadata corrupt.

Description: Metadata is corrupt (CRC does not match). The metadata was manually changed or modified by an application.

FMA error: 65842

Code (hex): 0x00010132

Text: Metadata error.

Description: Metadata of the file cannot be loaded.

FMA error: 65843

Code (hex): 0x00010133

Text: Metadata is invalid.

Description: (not used)

FMA error: 65844

Code (hex): 0x00010134

Text: Invalid storage handle.

Description: A new storage could not be allocated.

FMA error: 65845

Code (hex): 0x00010135

Text: Duplicate active metadata.

Description: -

150 Appendix

FMA error: 65857

Code (hex): 0x00010141

Text: Reading metadata from import file failed.

Description: -

FMA error: 65858

Code (hex): 0x00010142

Text: Metadata exists on the target file, import operation aborted.

Description: -

FMA error: 65859

Code (hex): 0x00010143

Text: Target file exists, import operation aborted.

Description: -

FMA error: 65873

Code (hex): 0x00010151

Text: Directory tree for metadata copy cannot be created.

Description: -

FMA error: 65874

Code (hex): 0x00010152

Text: Unable to create metadata copy.

Description: -

FMA error: 65888

Code (hex): 0x00010160

Text: Stubfile is not empty, recall cancelled.

Description: During recall, a non-empty stubfile was found. This situation can be caused either by a canceled recall or when a file was changed without a recall. This error should occur on IFE Versions 1.3 only. On IFE 1.4 and FMA 2.0, these situations are internally handled by the software.

FMA error: 65889

Code (hex): 0x00010161

Text: During recall an offline flag was removed.

Description: -

FMA error: 65890

Code (hex): 0x00010162

Text: Recall file modified.

Description: -


FMA error: 65891

Code (hex): 0x00010163

Text: Error when creating TMPREC file

Description: -

FMA error: 65904

Code (hex): 0x00010170

Text: Touch operation after release failed.

Description: -

FMA error: 65905

Code (hex): 0x00010171

Text: Maximum of HSM operations are reached.

Description: -

FMA error: 65920

Code (hex): 0x00010180

Text: Verification of file failed.

Description: -

FMA error: 65936

Code (hex): 0x00010190

Text: Verify, info.

Description: -

FMA error: 65937

Code (hex): 0x00010191

Text: Verify, warning.

Description: -

FMA error: 65938

Code (hex): 0x00010192

Text: Verify, error

Description: -

FMA error: 66049

Code (hex): 0x00010201

Text: Verify, stubfile not empty

Description: A stubfile contains data.

152 Appendix

FMA error: 66050

Code (hex): 0x00010202

Text: Verify, no metadata for offline file.

Description: An offline file does not contain metadata.

FMA error: 66051

Code (hex): 0x00010203

Text: Verify, metadata complete.

Description: Parts of the metadata are incomplete.

FMA error: 66052

Code (hex): 0x00010204

Text: Verify, stubfile modified.

Description: A stubfile was modified without recall.

FMA error: 66053

Code (hex): 0x00010205

Text: Verify, bad archive links.

Description: Some links of a file are invalid.

FMA error: 66054

Code (hex): 0x00010206

Text: Verify, no archive links.

Description: None of the file’s links are available.

FMA error: 66055

Code (hex): 0x00010207

Text: Verify, offline attribute is missing.

Description: -

FMA error: 66056

Code (hex): 0x00010208

Text: Verify, offline attribute is invalid.

Description: -

FMA error: 66057

Code (hex): 0x00010209

Text: Verify, dirty flag mismatch.

Description: -


FMA error: 66305

Code (hex): 0x00010301

Text: Error: Subsystem not avail.

Description: Unable to connect to FMAKSS.

FMA error: 66306

Code (hex): 0x00010302

Text: Error: Configuration invalid.

Description: Error in FMA configuration.

FMA error: 66307

Code (hex): 0x00010303

Text: Error: Volume serials are not unique.

Description: -

FMA error: 66308

Code (hex): 0x00010304

Text: Error: Volume not managed.

Description: The volume on which the file resides is not managed.

FMA error: 66309

Code (hex): 0x00010305

Text: Error: Invalid volume status.

Description: The volume status for this operation status is invalid.

FMA error: 66310

Code (hex): 0x00010306

Text: Error: Volume doesn’t match.

Description: A file is added to a list that contains files from a different volume. The volume status is invalid for this operation status.

FMA error: 66311

Code (hex): 0x00010307

Text: Error: List invalid.

Description: The specified list is not valid (not initialized, and so on).

FMA error: 66312

Code (hex): 0x00010308

Text: Error: List empty.

Description: The specified list contains no entries.

154 Appendix

FMA error: 66320

Code (hex): 0x00010310

Text: Error: License.

Description: Generic error in licensing module.

FMA error: 66321

Code (hex): 0x00010311

Text: Error: No license found.

Description: No license was found.

FMA error: 66322

Code (hex): 0x00010312

Text: Error: Evaluation period expired.

Description: An evaluation license has expired.

FMA error: 66322

Code (hex): 0x00010312

Text: Error: Evaluation period expired.

Description: An evaluation license has expired.

FMA error: 66323

Code (hex): 0x00010313

Text: Evaluation period warning.

Description: An evaluation period will expire in 10 days.

FMA error: 66324

Code (hex): 0x00010314

Text: Capacity warning.

Description: The capacity is at 90%.

FMA error: 66325

Code (hex): 0x00010315

Text: Error: Capacity expired.

Description: The capacity is expired.

FMA error: 66326

Code (hex): 0x00010316

Text: Error: Subsystem is busy.

Description: The subsystem is busy and rejected the request.


FMA error: 66327

Code (hex): 0x00010317

Text: Error: Subsystem error.

Description: Unable to connect to the subsystem.

FMA error: 66328

Code (hex): 0x00010318

Text: Error: Activate no object ID.

Description: No object ID for file to activate.

FMA error: 66561

Code (hex): 0x00010401

Text: Error: Duplicate archive name.

Description: An archive name is used more than once.

FMA error: 66562

Code (hex): 0x00010402

Text: Error: Deleted archive.

Description: The returned archive value is invalid.

FMA error: 66592

Code (hex): 0x00010420

Text: Error: Metadata import.

Description: The metadata import failed.

FMA error: 66593

Code (hex): 0x00010421

Text: Error: Metadata import too large.

Description: The metadata import is too large.

FMA error: 66608

Code (hex): 0x00010430

Text: Error: Cleanup is active.

Description: The cleanup process is already active and cannot be started twice.

FMA error: 66609

Code (hex): 0x00010431

Text: Error: Moving GC logs failed.

Description: The cleanup was unable to move GC logs to cleanup folder.

156 Appendix

FMA error: 66610

Code (hex): 0x00010432

Text: Error: Cleanup no more entries.

Description: End of GC log entries reached.

FMA error: 66611

Code (hex): 0x00010433

Text: Error: Cleanup EOF.

Description: End of current GC log file (internally used only).

FMA error: 66612

Code (hex): 0x00010434

Text: Error: Cleanup file.

Description: An error occurred while reading from GC file.

FMA error: 66613

Code (hex): 0x00010435

Text: Error: Storage descriptor buffer is too small.

Description: The storage descriptor data does not fit into the buffer.

FMA error: 66614

Code (hex): 0x00010436

Text: Error: GC log format.

Description: The GC log is not in the expected format.

FMA error: 66817

Code (hex): 0x00010501

Text: Error: RRP connect.

Description: Unable to connect to destination.

FMA error: 66818

Code (hex): 0x00010502

Text: Error: RRP protocol.

Description: Error in RRP protocol.

FMA error: 66897

Code (hex): 0x00010551

Text: Error: CFGSVC unknown function.

Description: Unknown function in config service.


FMA error: 66898

Code (hex): 0x00010552

Text: Error: CFGSVC protocol.

Description: Error in config server protocol.

FMA error: 131073

Code (hex): 0x00020001

Text: Archive Error

Description: -

FMA error: 131074

Code (hex): 0x00020002

Text: Error: Duplicate archive ID.

Description: -

FMA error: 131075

Code (hex): 0x00020003

Text: Error: Invalid archive entry.

Description: -

FMA error: 131076

Code (hex): 0x00020004

Text: Error: Unable to load RSA-DLL

Description: -

FMA error: 131077

Code (hex): 0x00020005

Text: Error: Archive key not found

Description: -

FMA error: 131078

Code (hex): 0x00020006

Text: Error: No capacity in archive pool

Description: -

FMA error: 131079

Code (hex): 0x00020007

Text: Error: Archive pool is empty

Description: -

158 Appendix

FMA error: 131080

Code (hex): 0x00020008

Text: Error while write Windows registry

Description: -

FMA error: 131081

Code (hex): 0x00020009

Text: Error: Duplicate archive name

Description: -

FMA error: 131082


Text: Error: Maximum of archives reached.

Description: -

FMA error: 131083


Text: Error: Invalid archive name.

Description: -

FMA error: 131083


Text: Archive deleted.

Description: The archive entry is deleted.

FMA error: 196609

Code (hex): 0x00030001

Text: Managed volume error.

Description: -

FMA error: 196610

Code (hex): 0x00030002

Text: Error: Maximum managed volumes exceeded.

Description: -

FMA error: 196611

Code (hex): 0x00030003

Text: Error: Volume isn’t a fixed disk.

Description: -


FMA error: 196612

Code (hex): 0x00030004

Text: Error: Volume unmount - invalid state.

Description: -

FMA error: 196613

Code (hex): 0x00030005

Text: Error: Volume unmount - failed.

Description: -

FMA error: 196614

Code (hex): 0x00030006

Text: Error: Volume filter isn’t available.

Description: -

FMA error: 196615

Code (hex): 0x00030007

Text: Error: Start of the volume manager failed.

Description: -

FMA error: 262145

Code (hex): 0x00040001

Text: Error while open target file (Archive storage subsystem).

Description: -

FMA error: 262146

Code (hex): 0x00040002

Text: Read error in archive storage subsystem.

Description: -

FMA error: 262147

Code (hex): 0x00040003

Text: Write error in archive storage subsystem.

Description: -

FMA error: 262148

Code (hex): 0x00040004

Text: Error: Read header (Archive storage subsystem).

Description: -

160 Appendix

FMA error: 262149

Code (hex): 0x00040005

Text: Error: Invalid header in archive storage subsystem.

Description: -

FMA error: 262150

Code (hex): 0x00040006

Text: Error: Invalid access mode in archive storage subsystem.

Description: -

FMA error: 262151

Code (hex): 0x00040007

Text: Error: Open shadow (Archive storage subsystem)

Description: -

FMA error: 262152

Code (hex): 0x00040008

Text: Error: Wrong number read in archive storage subsystem.

Description: -

FMA error: 262154


Text: Error: Wrong number write in archive storage subsystem.

Description: -

FMA error: 262155


Text: Error: Data corrupt in archive storage subsystem.

Description: -

FMA error: 327681

Code (hex): 0x00050001

Text: Metadata recovered.

Description: -

FMA error: 327682

Code (hex): 0x00050002

Text: No metadata found.

Description: -


FMA error: 327937

Code (hex): 0x00050101

Text: Error: File ID doesn’t match (Metadata handling).

Description: -

FMA error: 327938

Code (hex): 0x00050102

Text: Error: Metadata corrupt.

Description: -

FMA error: 327939

Code (hex): 0x00050103

Text: Error: Metadata record not found.

Description: -

FMA error: 328192

Code (hex): 0x00050200

Text: Error: Unexpected verify error (Metadata handling).

Description: -

FMA error: 328193

Code (hex): 0x00050201

Text: Verify: Size of metadata differs.

Description: -

FMA error: 328194

Code (hex): 0x00050202

Text: Verify: Metadata differs.

Description: -

FMA error: 328195

Code (hex): 0x00050203

Text: Verify: Primary metadata not found.

Description: -

FMA error: 328196

Code (hex): 0x00050204

Text: Verify: Alternate metadata not found.

Description: -

162 Appendix

FMA error: 328197

Code (hex): 0x00050205

Text: Verify: Metadata not found.

Description: -

FMA error: 393217

Code (hex): 0x00060001

Text: RSA Error.

Description: -

FMA error: 393218

Code (hex): 0x00060002

Text: Error: RSA connection

Description: -

FMA error: 393219

Code (hex): 0x00060003

Text: Error: RSA authentication

Description: -

FMA error: 393220

Code (hex): 0x00060004

Text: Error: Storage (RSA)

Description: File cannot be stored (space, and so on).

FMA error: 393221

Code (hex): 0x00060005

Text: Error: RSA configuration cancelled

Description: The configuration dialog was canceled by user.

FMA error: 393222

Code (hex): 0x00060006

Text: Error: Configuration error.

Description: Unexpected error in RSA configuration.

FMA error: 393223

Code (hex): 0x00060007

Text: Error: Storage descriptor invalid (RSA).

Description: File cannot be stored (space, and so on).


FMA error: 393472

Code (hex): 0x00060100

Text: Verify error (RSA).

Description: Generic error.

FMA error: 393473

Code (hex): 0x00060101

Text: Error: Verify date write (RSA).

Description: -

FMA error: 393474

Code (hex): 0x00060102

Text: Error: Verify file size (RSA).

Description: -

FMA error: 393475

Code (hex): 0x00060103

Text: Error: exist (RSA).

Description: -

FMA error: 393505

Code (hex): 0x00060121

Text: Error: Stream format (RSA).

Description: -

FMA error: 393506

Code (hex): 0x00060122

Text: Error: Stream format is to small (RSA).

Description: The specified stream buffer is too small. It must be larger than 20 bytes.

FMA error: 393507

Code (hex): 0x00060123

Text: Error: Stream write failed (RSA).

Description: The specified stream buffer is too small. It must be larger than 20 bytes.

FMA error: 393508

Code (hex): 0x00060124

Text: Error: Unknown storage descriptor (RSA).

Description: The specified storage descriptor is unknown.

164 Appendix

FMA error: 393509

Code (hex): 0x00060125

Text: Error: Adapter mismatch (RSA).

Description: The specified storage descriptor does not belong to the used RSA module.

FMA error: 393510

Code (hex): 0x00060126

Text: Error: Archive status info is corrupted (RSA).

Description: The archive status database is corrupted.

FMA error: 393511

Code (hex): 0x00060127

Text: Error: Archive status info lost (RSA).

Description: The archive status database does not exist.

FMA error: 393512

Code (hex): 0x00060128

Text: Error: Archive status info exists (RSA).

Description: The archive status database already exists.

FMA error: 393513

Code (hex): 0x00060129

Text: Error: Inactive archive (RSA).

Description: The archive is inactive due to a invalid configuration.

FMA error: 393520

Code (hex): 0x00060130

Text: Error: Storage meta data error (RSA).

Description: The meta data of the archive storage are corrupt.

FMA error: 393521

Code (hex): 0x00060131

Text: Error: No storage meta data (RSA).

Description: No storage meta data found.

FMA error: 393522

Code (hex): 0x00060132

Text: Error: Internal storage error (RSA)

Description: -


FMA error: 458753

Code (hex): 0x00070001

Text: Error: Create header (RSA-FTP).

Description: -

FMA error: 458754

Code (hex): 0x00070002

Text: Error: FTP access (RSA-FTP).

Description: -

FMA error: 458755

Code (hex): 0x00070003

Text: Error: FTP connect (RSA-FTP).

Description: -

FMA error: 458756

Code (hex): 0x00070004

Text: Error: FTP login (RSA-FTP).

Description: -

FMA error: 458757

Code (hex): 0x00070005

Text: Error: Invalid archive filename (RSA-FTP).

Description: -

FMA error: 458758

Code (hex): 0x00070006

Text: Error while MODDATE command execution (RSA-FTP).

Description: -

FMA error: 458759

Code (hex): 0x00070007

Text: Error while SIZE command execution (RSA-FTP).

Description: -

FMA error: 458760

Code (hex): 0x00070008

Text: Error: Storage descriptor header size.

Description: -

166 Appendix

FMA error: 458761

Code (hex): 0x00070009

Text: Error while MKPATH command execution (RSA-FTP).

Description: -

FMA error: 458762


Text: Error while SOCKET command execution (RSA-FTP).

Description: -

FMA error: 458763


Text: Error: Server not supported (RSA-FTP).

Description: -

FMA error: 458764


Text: Error: Wrong file size (RSA-FTP).

Description: -

FMA error: 458765

Code (hex): 0x0007000D

Text: Error: Archive storage subsystem (RSA-FTP).

Description: -

FMA error: 458766

Code (hex): 0x0007000E

Text: Error while FTP WRITE command execution (RSA-FTP).

Description: -

FMA error: 458767

Code (hex): 0x0007000F

Text: Error while FTP READ command execution (RSA-FTP).

Description: -

FMA error: 458768

Code (hex): 0x00070010

Text: Error while FTP AUTHENTICATION command execution

Description: -


WIN32 error codesFor getting a description of system error codes (Code No. 0 - 6118), see Microsoft error list or call the Hewlett-Packard Co. Service Center.

Reporting a problemHave the following information ready when you report an FMA problem to technical support:

• Operating system version of your file server.• FMA version and license information.

You can display this information by entering fmacli sys (see ”SYSTEM” on page 94).• Installed third-party applications on your file server.

(AntiVirus Scanners, QuotaManagement, Backup Tools, etc.)• Problem description:

• When did the problem occur?• Which activities have caused the problem?

• Logging information:• Pack all FMA log files to a zip-file (directory: %FMA_install_path%\log)• Windows application and system event log. Use the eventvwr tool and select Save Log File as to

export the event logs to file. Provide the file in the Event-Log format.• FMA configuration:

Use the regedit tool and export the following registry keys:

FMA error: 458769

Code (hex): 0x00070011

Text: Error while FTP DELETE command execution (RSA-FTP).

Description: -

FMA error: 458770

Code (hex): 0x00070012

Text: Error while FTP RMDIR command execution (RSA-FTP).

Description: -

FMA error: 458771

Code (hex): 0x00070013

Text: Error: Unicode conversion (RSA-FTP).

Description: -

FMA error: 458772

Code (hex): 0x00070014

Text: Error: Configuration (RSA-FTP).

Description: -

FMA error: 458773

Code (hex): 0x00070015

Text: Error while FTP CLOSE command execution (RSA-FTP).

Description: Closing the FTP connection failed.

168 Appendix

HKEY_LOCAL_MACHINE\Software\Hewlett-Packard\HP FMAHKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\hsmfs

• For installation/uninstallation problems:Please provide the FMA installation/uninstallation log files%temp%\FMAInst.log%temp%\FMARemove.log

• If a file cannot be opened or processed, redirect the output of the command fmacli info -l <filename> to a file.

• If an FMA command line operation failed, either provide the log file or a screen shot of the stdout/stderr output.

• If an FMA process has abnormally terminated, the Dr. Watson log file and the related user dump is needed. Run DrWtsn32.exe from a command window to find the Dr. Watson log file path and user dump location.


Index

Symbols_IFE_FILEINFO attribute 21

AACTIVATE command 71anti-virus product compatibility 140ARCHIVE command 73Archive Properties dialog 39archives

adding for migration operation 65backing up and restoring managed volumes 126CIFS-based NAS device 115CLEANUP command 75configure backend 38defined 19deleting 46error codes 157Linux 112MIGRATE command 83properties 39RECALL command 22RELEASE command 22RISS 118Windows 109

arguments, FMAFileUtil 106audience 13

Bbackend archives, configure 38backend datastore, defined 19backing up managed volumes 126backup/restore applications, compatibility 142BackupExec 142benefits 20BrightStor ArcServe 142

CCD-ROM, installation 27CIFS-based NAS device archives 115CLEANUP command 75clusters, configuring 54command-line tools 23commands

FMACLI 69FMAFileUtil 106scheduling 125

compatibility, third-party productsanti-virus 140backup/restore 142defragmentation 145IndexServer 146quota/encryption 145

components, software 23

configurationabout 37backend archives 38CIFS-based NAS device archives 115clusters 54FMA Job Manager 68GDS FTP-Server 138job parameters 63job settings 67Linux archives 112managed volumes 46, 50migration parameters 64Red Hat Linux VSFTPD 131release parameters 66RISS applications 139RISS archives 118RSA-CIFS 40RSA-FTP 43, 110, 129RSA-RISS 44Sun Solaris PROFTPD 133SuSE Linux VSFTPD 129Windows archives 109

conventionsdocument 14text symbols 14

copying software 30creating

disk usage monitoring 122file policies 120managed volumes 120

Custom Setup dialog 29

DData Protector 142defragmentation software compatibility 145deleting

archives 46jobs 67managed volumes 49metadata 76

Destination Folder dialog 28disabling files 72disk space

monitoring 51setting up monitoring 122

documentconventions 14prerequisites 13related documentation 13

documentationHP web site 13providing feedback 15

170

EERASE command 76error codes

FMA 146VOLUME command 100WIN32 167

eTrust AntiVirus 141event log, Windows 108

Ffile names, FMACLI 69file policies

creating 120overview 53

FILE_ATTRIBUTE_OFFLINE flag 21FIND command 78first use 25FMA

backend archives 38backing up and restoring managed volumes 126CIFS-based NAS device archives 115cluster configuration 54command-line tools 23components 23configuration 37copying software 30Custom Setup dialog 29deleting archives 46error codes 146features 20first steps 25installation path 28installing 27license agreement 28Linux archives 112log files 107metadata attribute 21MIGRATE command 22migration overview 17offline marker 21operating systems supported 24policies 51prerequisites 24RECALL command 22RELEASE command 22relocating data 126restrictions 24RISS archives 118scheduling commands 125Setup Type 29uninstalling 33updates 35user privileges 24version number, displaying 123Windows archives 109

FMA Explorer plug-infeatures 24migrating files 102overview 100recalling files 103registering 104releasing files 102unregistering 104viewing metadata 103

FMA Job ManagerAbout button 68archives, adding 65configuring 68deleting jobs 67dialog 61features 24job settings 67log files 108migration parameters 64new jobs, creating 62parameters 63release parameters 66running jobs 67scheduling jobs 68, 125starting 62

FMA MMC Snap-In 23, 37FMA Policy Manager

features 23FMA Wizard

features 23FMACLI

ACTIVATE command 71ARCHIVE command 73CLEANUP command 75commands 69ERASE command 76file names 69FIND command 78INFO command 79log files 108MIGRATE command 22, 83POLICY command 85RECALL command 86RELEASE command 22, 89RSA command 93syntax 69SYSTEM command 94VERIFY command 95VERSION command 98VOLUME command 98

FMAFileUtilarguments 106commands 106features 23options 105storing data 104


FTPbackend archives 38command requirements 129configuration dialog 110configuring 43error codes 165installing GDS FTP-Server 135Linux archives 112Red Hat Linux and VSFTPD configuration 131Sun Solaris and PROFTPD configuration 133SuSE Linux and VSFTPD configuration 129Windows archives 109

GGalaxy Backup & Recovery 145GDS FTP-Server

configuring 109, 138Customer Information dialog 136installation path 136installing 135Setup Type dialog 136uninstalling 138

glossary 19

Hhelp, obtaining 14high-watermark, setting 124HP

technical support 14HP StorageWorks File Migration Agent. See FMAHP StorageWorks File System Extender (FSE) 17HSM metadata, defined 19

Iinactive files, defined 19IndexServer software compatibility 146INETD activation 130INFO command 79installation path

FMA 28GDS FTP-Server 136

installing FMAcopying software 30Custom Setup dialog 29destination folder 28license agreement 28Setup Type dialog 29starting 27

installing GDS FTP-Server 135

JJob Manager. See FMA Job Manager

jobscreating new 62deleting 67parameters 63running 67scheduling 68, 125settings 67

Llicense agreement

FMA 28license keys 35Linux

archives 112RSA-FTP setup 129

Linux archives 112local checks 96locking files 22log files

FMA 107FMA Job Manager 108FMACLI 108

LogRotate configuration 131

Mmanaged volumes

backing up and restoring 126clusters 58creating 48, 120defined 19deleting 49disk space 51displaying information about 98file policies 53list 46properties 50relocating data 126scheduling 53starting unmounted 49status 46stopping 48

McAfee VirusScan 140metadata

deleting 76displaying 79error codes 146file IDSs, repairing 71storage attribute 21verification 96

Microsoft Cluster system 54Microsoft Installer (MSI), updating with 35MIGRATE command 83, 124migrating files 124migrating files, FMA Explorer plug-in 102

172

migrationcommand-line 124defined 19error codes 146high-watermark, setting 124overview 17parameters 64

minor updates 35monitoring, disk space 51MS Defragmentation 145MS IndexServer 146MS VSS 144

NNAS device archives 115NetBackup 143NetVault 143Networker 143nodes, cluster 55

OO & O Defrag 145offline files

marker 21RECALL command 22

operating systems supported 24

Pparameters

jobs 63LogRotate command 131migration 64release 66

PartitionRoot ownership 130policies 51POLICY command 85prerequisites 13privileges, users

FMA 24Red Hat Linux 131Sun Solaris 133SuSE Linux 129

PROFTPDusers, adding 133

Qquota/encryption third-party product compatibility 145

RRECALL command 22, 86, 124recall, defined 19recalling files, FMA Explorer plug-in 103Red Hat Linux VSFTPD configuration 131registering, FMA Explorer plug-in 104related documentation 13

releasedefined 19high-watermark setting 124parameters 66

RELEASE command 22, 89, 124releasing files, FMA Explorer plug-in 102relocating

data 126large number of files 128

remote checks 96remote storage adapter, defined 19removing


restoring managed volumes 126restrictions 24result codes, VOLUME command 100RISS

archives 118backend archives 38configuring 44, 139

RISS archives 118RSA command 93RSA-CIFS

backend archives 38configuring 40

RSA-FTPbackend archives 38commands supported 129configuration dialog 110configuring 43error codes 165Red Hat Linux and VSFTPD configuration 131SuSE Linux and VSFTPD configuration 129

RSA-RISSarchives 118backend archives 38configuring 44

running jobs 67

Sscheduling

FMA command 125jobs 68, 125managed volumes 53

ServerProtect 141setup program 27Setup Type dialog


softwareFMA components 23third-party compatibility 140

Sophos Anti-Virus 141status

managed volumes 46RSA 93

Storage descriptor creation dialog 45StorageExec 145


stubfile, defined 19Subscriber's Choice, HP 15Sun Solaris PROFTPD configuration 133SuSE Linux VSFTPD configuration 129Symantec AntiVirus 140symbols in text 14syntax, FMACLI 69SYSTEM command 94system requirements 24

Ttechnical support

service locator web site 15technical support, HP 14technical users

adding in Red Hat Linux 131adding in Sun Solaris 133adding in SuSE Linux 129FMA 24

terminology 19text symbols 14third-party product compatibility

anti-virus 140backup/restore 142defragmentation 145IndexServer 146quota/encryption 145

Tivoli Storage Manager 144TrendMicro OfficeScan 141troubleshooting

FMA error codes 146VOLUME command errors 100WIN32 error codes 167

Uuninstalling


unregistering, FMA Explorer plug-in 104updates, minor 35users, technical

adding in Red Hat Linux 131adding in Sun Solaris 133adding in SuSE Linux 129FMA 24

VVERIFY command 95verifying data files 125VERSION command 98version, displaying FMA 123viewing metadata, FMA Explorer plug-in 103VOLUME command 98

volumes, managedbacking up and restoring 126clusters 58creating 48, 120defined 19deleting 49displaying information about 98file policies 53list 46monitoring 51properties 50relocating data 126scheduling 53starting unmounted 49status 46stopping 48

VSFTPDconfiguration 130LogRotate 131users, adding 129, 131

VSS 144

Wwatermark, setting 124web sites

HP 15HP Subscriber's Choice for Business 15product manuals 13

WIN32 error codes 167Windows

archives 109event log 108

Windows archives 109