FMA V2 Administration Guide

HP StorageWorks File Migration Agent administrator guide
Part number: T4274-96105 Second 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.21 and 12.212, Commercial 1 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
Contents
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 13 13 14 14 15 15 15
1 Product information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
HP StorageWorks File Migration Agent overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Offline marker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File state diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA command-line tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMACLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMAFileUtil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA MMC Snap-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA Policy Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA Explorer plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA Job Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating system version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the FMA software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define installed features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying the FMA software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical user for the File Migration Agent service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstall the FMA software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minor updates from version 2.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA License Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enter FMA license keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17 19 20 20 21 21 21 21 22 22 22 23 23 23 23 23 23 23 23 24 24 24 24 24 24 24 25 27 27 27 28 28 29 29 30 31 33 33 35 35 35
2 Installation, uninstall, update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
FMA licensing problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Managing FMA archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure backend archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSA-CIFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSA-RISS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage descriptor creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use system name for storage descriptor creation (Option 1 off = default) . . . . . . . . . . . . . . . . . Ignore system name for storage descriptor creation (Option 1 on) . . . . . . . . . . . . . . . . . . . . . . Use volume serial for storage descriptor creation (Option 2 off = default) . . . . . . . . . . . . . . . . . Ignore volume serial for storage descriptor creation (Option 2 on) . . . . . . . . . . . . . . . . . . . . . . Delete an FMA archive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stop a managed volume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start an unmounted volume again . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete a managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Volume properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk space monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Watermark parameters: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Retention time parameters: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exclusion list:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA configuration for MS Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38 38 40 40 43 44 45 45 45 45 46 46 46 48 48 49 49 50 51 51 52 52 52 53 53 54 54 61 62 62 63 64 65 65 66 67 67 67 68 68 68 69 69 71 71 72 72 72 73 73 74 74 74 74
4 Operating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
FMA Job Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting FMA Job Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a new job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add archive for migration operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete an archive from the migration operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change job settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About FMA Job Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule FMA jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA Job Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Line Interface (FMACLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMACLI syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMACLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACTIVATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ARCHIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output . . . . . . . . . . . . . . . . . . . . . . Description of columns . . . . . . . . . . . CLEANUP . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . ERASE . . . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . FIND . . . . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . INFO. . . . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Example 1 . . . . . . . . . . . . . . . . . . . Output . . . . . . . . . . . . . . . . . . . . . . Description of columns . . . . . . . . . . . Example 2 . . . . . . . . . . . . . . . . . . . Output . . . . . . . . . . . . . . . . . . . . . . MIGRATE. . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Examples . . . . . . . . . . . . . . . . . . . . POLICY . . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . RECALL . . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . RELEASE . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Examples . . . . . . . . . . . . . . . . . . . . RSA . . . . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . Output . . . . . . . . . . . . . . . . . . . . . . SYSTEM. . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . Output . . . . . . . . . . . . . . . . . . . . . . VERIFY. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ......
74 74 75 75 75 75 75 76 76 76 76 77 78 78 78 78 79 79 80 80 80 81 81 82 82 82 83 83 83 83 85 85 85 86 86 86 86 87 87 87 89 89 90 90 90 92 93 93 93 94 94 94 94 94 94 94 95 95 95
5
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Local Check (Level 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Remote Check (Level 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 VERSION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Description of columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 FMA Explorer plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Migrating files or folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Releasing files or folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Recalling files or folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Viewing FMA metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Register/unregister the Explorer plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 FMAFileUtil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Arguments (pack command). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Arguments (unpack command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 FMA log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 FMACLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 FMA Job Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Windows event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5 Best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Create a new HP StorageWorks File Migration Agent (FMA) archive . . . . . . . . . . . . . . . . . . . . . . . . . . FMA archive configuration for a Windows archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of the GDS FTP-Server configuration file ftp_server.cfg file. . . . . . . . . . . . . . . . . . . . . . . FMA RSA-FTP Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA archive configuration for an FSE/Linux archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA archive configuration for a CIFS-based NAS device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA archive configuration for RISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a new managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create file policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create disk usage monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine FMA software version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recall files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set a high-watermark for migration or releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
109 109 109 109 110 112 115 118 120 120 122 123 124 124 124 124
Verify data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create an FMA job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule FMA commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule FMA jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup/restore concept for FMA managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relocating data to another FMA managed volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relocating data procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relocating a large number of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archive store configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FTP configuration for HP StorageWorks File System Extender (ftpd) . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General topics for using the RSA-FTP module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum requirements for FTP servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of VSFTPD on SuSE Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a new group and user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Take ownership of the PartitionRoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activation of INETD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of VSFTPD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration for LogRotate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of VSFTPD on Red Hat Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of PROFTPD on Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a new group and user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of PROFTPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using GDS FTP-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the GDS FTP-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying the GDS FTP-Server software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure the GDS FTP-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstall the GDS FTP-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RISS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring RISS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring application servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Third-party product compatibility list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Anti-virus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symantec AntiVirus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . McAfee VirusScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sophos Anti-Virus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ServerProtect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . eTrust AntiVirus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TrendMicro OfficeScan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup/restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BackupExec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BrightStor ArcServe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Networker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NetVault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS VSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Galaxy Backup & Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quota/encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . StorageExec. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
125 125 125 125 126 126 126 127 128 129 129 129 129 129 129 129 130 130 130 131 131 133 133 134 135 135 135 136 136 137 138 138 139 139 139 139 139 140 140 140 140 141 141 141 141 142 142 142 142 143 143 143 144 144 145 145 145
A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Defragmentation . . . . . . O & O Defrag . . . . . MS Defragmentation . IndexServer. . . . . . . . . . MS IndexServer . . . . Error codes . . . . . . . . . . . . Abstract . . . . . . . . . . . . FMA error handling . . . . FMA error codes . . . WIN32 error codes . Reporting a problem . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........
145 145 145 146 146 146 146 146 146 167 167
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Figures

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 Migration process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migration results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hierarchical storage management in heterogeneous networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Offline file attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State of files managed by FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA software components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InstallShield Wizard Welcome dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . License Agreement dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Destination Folder dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup Type dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Setup dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the HSM Explorer Extension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing HP StorageWorks File Migration Agent dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA Wizard (Technical user) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select User dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select User (Advanced) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InstallShield Wizard Completed dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA installation directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA Uninstall menu item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InstallShield Wizard (Remove) dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add/Remove Programs dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA uninstallation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Settings dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shortcut for starting FMA MCC Snap-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA MCC Snap-In configuration items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMA backend archives list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Context menu for defining FMA archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archive Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing existing FMA archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rsa Configuration dialogRSA-CIFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Properties (Sharing) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Permissions for data (Security) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rsa Configuration dialogRSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rsa Configuration dialogRSA-RISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage descriptor creation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting FMA archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Archive confirmation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managed Volumes list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Context menu for creating managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating managed volumesNeed reboot status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating managed volumesActive status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Context menu for stopping managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 18 19 21 21 23 27 28 28 29 29 30 30 31 31 32 32 33 33 33 34 34 36 37 38 38 39 39 40 40 41 42 42 43 44 45 46 46 47 48 48 48 48 48
45 Stopping managed volumesNot mounted status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 46 Context menu for starting unmounted volumes again . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 47 Starting unmounted volumes againActive status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 48 Context menu for stopping managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 49 Stopping managed volumesNot mounted status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 50 Context menu for deleting managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 51 Deleting managed volumesNot managed status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 52 Context menu for displaying volume properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 53 Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 54 Computer Management dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 55 Volume Parameters (Watermark tab) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 56 Volume Parameters (Retention tab) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 57 Volume Parameters (Exclusion tab) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 58 Scheduling dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 59 Schedule Options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 60 Policy Properties (Properties tab) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 61 Policy Properties (Filtering tab) dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 62 Policy Properties (Archives tab) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 63 FMA Wizard (Cluster setup) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 64 FMA Wizard (Technical user) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 65 FMA Wizard (Cluster setup) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 66 FMA Wizard (Cluster setup) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 67 FMA Wizard (Wizard Summary) dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 68 Activating the Ignore system name for storage description creation option . . . . . . . . . . . . . . . . . . . . 58 69 Deleting the FMA Cfg Server resource from the Cluster Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 70 FMA Job Manager dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 71 Shortcut for starting FMA Job Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 72 Creating new jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 73 Job dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 74 Migration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 75 Adding archives for migration operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 76 Deleting archives from migration operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 77 Release dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 78 Retention times for release parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 79 Changing job settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 80 Deleted job confirmation dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 81 About FMA Job Manager dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 82 MIGRATE command example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 83 RECALL command example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 84 Retention times for RELEASE command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 85 RELEASE command example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 86 FMA Explorer context menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 87 Processing results dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 88 Migrating from context menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 89 Releasing from context menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 90 Release options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 91 Recalling from context menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 92 Viewing metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 93 Storing data in an FSE Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 94 Layout of FMA log file entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 95 Rsa Configuration dialogRSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 96 Replication archive (Windows) example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 97 Rsa Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 98 Rsa Configuration dialogRSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 99 Replication archive (Linux) example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 100 Rsa Configuration dialogRSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 101 Rsa ConfigurationRSA-CIFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 102 Rsa Configuration dialogRSA-CIFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 103 Replication archive (Microsoft Server) example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
File Migration Agent administrator guide 9
104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123
Rsa Configuration dialogRSA-RISS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rsa Configuration dialogRSA-RISS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replication archive (RISS) example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Policy - Properties (Filtering) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule Options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule Options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule Options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Volume Properties (Watermarks) dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Volume Properties (Retention) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Volume Properties (Retention) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Volume Properties (Exclusion) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Info dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About FMA Job Manager dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InstallShield Wizard Welcome dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer Information dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup Type dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing GDS FTP-Server dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InstallShield Wizard Completed dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add/Remove Programs dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
118 119 119 120 120 121 121 121 122 122 122 123 123 123 135 136 136 137 137 139
Tables
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Archive Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Rsa Configuration dialogRSA-CIFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Rsa Configuration dialogRSA-FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Rsa Configuration dialogRSA-RISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Managed Volumes list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Managed Volumes list status symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 FMA Job Manager dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Job dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Migration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Release dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 [HKEY_LOCAL_MACHINE\SOFTWARE\GDS\FMA\JobMgr] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Supported FMACLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 ACTIVATE command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 ARCHIVE command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Column descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 CLEANUP command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 ERASE command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 FIND command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 INFO command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 INFO command output for example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 MIGRATE command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 POLICY command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 RECALL command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 RELEASE command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Variable definitions for Figure 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 RSA command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 SYSTEM command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 VERIFY command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 VERSION command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 VOLUME command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Description of columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 FmaFileUtil options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 FmaFileUtil commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 FmaFileUtil command-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 FmaFileUtil arguments (pack command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
10
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
FmaFileUtil arguments (unpack command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Parameters for useradd command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Parameters for LogRotate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Parameters for useradd command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Symantec AntiVirus specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 McAfee VirusScan specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Sophos Anti-Virus specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 ServerProtect specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 eTrust AntiVirus specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 TrendMicro OfficeScan specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 BackupExec specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 BrightStor ArcServe specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Data Protector specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 NetBackup specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Networker specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 NetVault specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 MS VSS specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Tivoli Storage Manager specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Galaxy Backup & Recovery specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 StorageExec specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 O & O Defrag specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 MS Defragmentation specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 MS IndexServer specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
11
12
About this guide

This guide provides information about: Installing HP StorageWorks File Migration Agent (FMA) Performing typical tasks needed for operating FMA
Intended audience
This guide is intended for system administrators who are experienced with Windows Server 2003 operating systems.
Prerequisites
Prerequisites 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 documentation
The 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.
13
Document conventions and symbols

Table 1 Document conventions Element
Cross-reference links and e-mail addresses Web site addresses Italics font Monospace 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
Convention
Medium blue text: Figure 1 Medium blue, underlined text (http://www.hp.com) Bold font
Text emphasis File and directory names System output Code Text typed at the command-line Code variables Command-line variables
Monospace, italic font
Monospace, bold font
Emphasis of file and directory names, system output, code, and text typed at the command line
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 support
Telephone 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
14
Operating system type and revision level Detailed, specific questions For continuous quality improvement, calls may be recorded or monitored.
Subscription service
HP 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 sites
For 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 feedback
HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to storagedocs.feedback@hp.com. All submissions become the property of HP.
15
16
Product information
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.
HP StorageWorks File Migration Agent overview
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 Microsofts 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.
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.
18
Product information
Figure 3 Hierarchical storage management in heterogeneous networks
Important terms
Archive 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
19
sparse file and the files data contains zero bytes. The link to the files 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 features
FMA 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.
20
Product information
Data management
This section describes the lifecycle of files that are under control of the FMA.
Offline marker
To 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
Metadata
FMA metadata is stored in an NTFS extended attribute named _IFE_FILEINFO.
File state diagram

The following diagrams show the states of files managed by FMA.
Figure 5 State of files managed by FMA

Migration
Files 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.
Release
FMA 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.
Recall
Whenever a user or application accesses an offline file to read its data, FMA will intercept the read request and will first retrieve the files 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.
22
Product information
Software components
The following diagram shows the FMA software components on an abstract level:
Figure 6 FMA software components
FMA command-line tools FMACLI

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.
FMAFileUtil
Utility for manual data retrieval and storage with FTP-based archives.
FMA applications
FMA 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.
Prerequisites
Technical user
The FMA service needs to run under a user account (for example, FMAUser) with the following privileges: Backup files and directories. Restore files and directories. Take ownership of files or other objects. Network access. Other things to consider about technical users: Password must not expire. Password should not be changeable by the user. NOTE: The user must have the appropriate access rights (FULL CONTROL) on the NAS devices, which are used as backend 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 version

The 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 issues
See Third-party product compatibility list on page 140.
Restrictions
The following features are not part of this FMA version: No continuous migration and release. No event-driven migration and release.
24 Product information
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 steps
When 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).
25
26
Product information
Installation, uninstall, update

HP 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 software

Prerequisites
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 installation
For 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.
27
License Agreement
Read 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 path
In 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.
28
Setup type
Select 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 features

If setup type Custom is selected (see Setup type on page 29), this additional dialog appears.
Figure 1 Custom Setup dialog 1 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.
29
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 software

Now 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.
30
Technical user for the File Migration Agent service

During 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
31
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.
32
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 configuration
After 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 software

There 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
33
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.
34
Minor updates from version 2.x

FMA 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 FMAs policies. For further information on FMAs 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 Keys

Enter 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. 1 Restart the File Migration Agent service. 1. 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.
35
FMA licensing problems

If 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.
36
Configuration
Before 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).
37
Figure 25 FMA MCC Snap-In configuration items
Managing FMA archives

Configure 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.
38
Configuration
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. Table 2 Setting
Archive name: Archive ID:
Archive Properties dialog Description

Name of the archive definition. This name is used as a reference to this archive in FMA for migration and recall operations. 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: Description: Priority for recalls. The smaller the index, the higher the priority (default: 100). Free text comment for this 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.
39
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 configuration
RSA-CIFS
Figure 30 Rsa Configuration dialogRSA-CIFS Table 3 Setting

Primary archive:
Rsa Configuration dialogRSA-CIFS Description

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. Fully qualified NAS path where the data is recalled from if the primary archive is not accessible. 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 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
Secondary archive: Ignore security on backend archive:
Store data stream only:
40
Configuration
Table 3 Setting
Rsa Configuration dialogRSA-CIFS (continued) Description

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 system name ... :
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. 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 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.
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
41
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 folders property page and grant Full Control permissions to the FMA User.
Figure 33 Data Properties dialog
42
Configuration
RSA-FTP
Figure 34 Rsa Configuration dialogRSA-FTP Table 4 Setting

Host/IP: Secondary Host/IP: Port: User: Password: Root path: Connection timeout (ms) Data read timeout (ms)
Rsa Configuration dialogRSA-FTP Description

Hostname or IP address of the FTP server used for accessing the primary archive location. Hostname or IP address of the FTP server used for recalls if the primary archive instance is not available. FTP port (default: 21). FTP user. Password. Root path on the specified FTP server. Timeout for the connection to the FTP server in ms. The default value is 500 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.
43
Table 4 Setting
Rsa Configuration dialogRSA-FTP (continued) Description

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 system name ... :
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. 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 volume serial is unique.
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 dialogRSA-RISS Table 5 Setting

Primary RISS: Secondary RISS: Domain: 44 Configuration
Rsa Configuration dialogRSA-RISS Description

Hostname or IP address of the primary RISS. Hostname or IP address of the secondary RISS. RISS domain the data goes to.
Table 5 Setting
Rsa Configuration dialogRSA-RISS (continued) Description

Default repository where the data is stored. Default recipients for FMA data. See text in Figure 35.
Default repository: Recipients: Recipients options
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:
<archive-path>\<system-name>\<vol-serial>\<local-path>\<file-name>.<generation>
Example:
D:\Archives\system03\00471100\dir1\dir2\file1.dat.0000
Ignore system name for storage descriptor creation (Option 1 on)

The system name will be used to create a storage descriptor. Structure:
<archive-path>\<vol-serial>\<local-path>\<file-name>.<generation>
Example:
D:\Archives\00471100\dir1\dir2\file1.dat.0000
Use volume serial for storage descriptor creation (Option 2 off = default)
The volume serial will be used to create a storage descriptor. Structure:
<archive-path>\<system-name>\<vol-serial>\<local-path>\<file-name>.<generation>
45
Example:
D:\Archives\system03\00471100\dir1\dir2\file1.dat.0000
Ignore volume serial for storage descriptor creation (Option 2 on)

The volume serial will not be used to create a storage descriptor. Structure:
<archive-path>\<system-name>\<local-path>\<file-name>.<generation>
Example:
D:\Archives\system03\dir1\dir2\file1.dat.0000
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 volumes
A 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
46
Configuration
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 Column

Volume: Status: File system: Capacity: Free Space: % Free: PID: Migrated bytes:
Managed Volumes list Description

Volume name together with a status symbol. See Table 7. File system of this volume (always NTFS). Disk space (max. available). Free disk space. Free disk space in percent. HSM process ID of volume manager process. Migrated bytes.
Table 7 Symbol
Managed Volumes list status symbols 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.
47
Create a managed volume

In 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. 2. Right-click the corresponding volume entry to display the context menu.
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 volumesNeed 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 volumesActive status The volume is managed via FMA now.
Stop a managed volume

Figure 44 Context menu for stopping managed volumes 2. Select the Stop item in the context menu.
48 Configuration
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 volumesNot mounted status 3. No HSM operations (migrate, release, recall) are available now.
Start an unmounted volume again

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 againActive 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 volumesNot mounted status
49
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 volumesNot 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).
50
Configuration
FMA policies
FMA policies can be configured by selecting Managed Volumes and double-clicking the corresponding managed volume. FMAs 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 monitoring

For 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.
51
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
52 Configuration
Scheduling
For 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 policy
FMA 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

Filtering
On 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 Cluster

If FMA is installed on a Microsoft Cluster system, additional configuration steps are necessary.
54 Configuration
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
55
b. Assign the new cluster resource to the Cluster Group.
Figure 65 FMA Wizard (Cluster setup) dialog c. Select a name for the new cluster resource.
Figure 66 FMA Wizard (Cluster setup) dialog
56
Configuration
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).
57
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).
58
Configuration
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
59
60
Configuration
Operating
This chapter describes administrative tools that are available for the HP StorageWorks File Migration Agent (FMA).
FMA Job Manager

The 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 Column

Job: Description: Path: Archives: Release:
FMA Job Manager dialog Description

Job name. Description of the job. Directory that is managed by FMA. One or more archives when a migration operation is defined for this job. Marked with X when a release operation is defined for this job.
61
Starting FMA Job Manager

Use 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 job

To 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
62
Operating
Job parameters
Figure 73 Job dialog Table 9 Setting

Job: Descr: Directory: Log File:
Job dialog Description

Job name. Description of the job. Directory that is managed by FMA. 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.
63
Migration parameters
Figure 74 Migration dialog Table 10 Setting

Minimum file size: Minimum time interval (modified): Minimum time interval (accessed): System: Hidden: Read Only: Archive: Compressed:
Migration dialog Description

Define a minimum file size for the migration operation. The value can be specified in bytes, kilobytes, megabytes, or gigabytes. 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. 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. If this option is selected, no files with system attribute will be migrated. If this option is selected, no hidden files will be migrated. If this option is selected, no read-only files will be migrated. If this option is selected, no files with active-archive bit will be migrated. If this option is selected, no files with active-compressed bit will be migrated.
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.
64
Operating
Add archive for migration operation

Click 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.
65
Release parameters
Figure 77 Release dialog Table 1 1 Setting

Release Files: Retention time for migrated files: Retention time for recalled files: Filesystem Watermark:
Release dialog Description

If this option is active, the job contains a release operation. Time period (crt) that changed files stay on disk before they are released. The value can be specified in seconds, minutes, hours, or days. 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. 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.
Figure 78 Retention times for release parameters
66
Operating
Change job settings

To 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 job
If 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 job
To 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.
67
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 jobs

The 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 Configuration

The configuration of the FMA Job Manager is held in the following registry entries: Table 12 [HKEY_LOCAL_MACHINE\SOFTWARE\GDS\FMA\JobMgr] Setting
Height: PosX: PosY: DebugLevel: JobPath:
Description
Height of the Job Manager main dialog. Start position (X coordinate in pixel) of the Job Manager main dialog. Start position (Y coordinate in pixel) of the Job Manager main dialog. For internal use only. Path for the jobs of the FMA Job Manager.
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.
68
Operating
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]
69
Following commands of the FMA command line interface (FMACLI) are supported: Table 13
command
Supported FMACLI commands

Act[ivate] Arc[hive] Cle[anup] Era[se] Find Inf[o] Mig[rate] Pol[icy] Rec[all] Rel[ease] RSA Sys[tem] Ver[ify] Vers[ion] Vol[ume] Repair metadata file IDs after restore from a backup. For further information, see page 71. This command is needed for the archive management. For further information, see page 73. This command reorganizes FMA archives. For further information, see page 75. This command deletes FMA metadata. For further information, see page 76. This command find files and creates a file list. For further information see page 78. Display FMA metadata. For further information, see page 79. Explicitly migrate a file to the specified archive. For further information, see page 83. Display or execute a file policy. For further information see page 85. Explicitly recall data for a migrated file. For further information, see page 86. Explicitly release data for a file. For further information, see page 89. This command is needed for the RSA management. For further information, see page 93. This command is needed for the system management. For further information, see page 94. Display the result of the verification process. For further information, see page 95. Displays FMA version and build information. For further information see page 98. This command is needed for the volume management. For further information, see page 98.
70
Operating
FMACLI commands
Enter FMACLI or FMACLI --help to display a list of the available FMACLI commands.
FMACLI --help usage: FMACLI <command> [command options] commands: --------act[ivate] arc[hive] cle[anup] era[se] find inf[o] mig[rate] pol[icy] rec[all] rel[ease] rsa sys[tem] ver[ify] vers[ion] vol[ume]
repair file-ids in metadata after restore display a list of defined archives remove the archived replica(s) of a deleted file delete metadata from one or more file(s) find files and write found filenames to a file list display FMA relevant informations of one or more file(s) migrate files to one or more archive(s) display or execute a file policy recall one or more released file(s) release one or more file(s) display a list of storage adapters and their status display FMA relevant data and settings display the result of the verification process display version info display a list of managed volumes
For further informations about commands please use FMACLI <command> --help
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.
ACTIVATE
The ACTIVATE command repairs metadata file IDs after restore.
71
Synopsis
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>]
Description
The 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 FMAs 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
Table 14 Options
--help -h --logfile <logfile> -L <logfile> Specifies a log file. The log file must be specified with a fully qualified path. Log files are created with the following (fixed) policies: 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 -> ...
ACTIVATE command options Description

Displays the online help for the ACTIVATE command.
--log-info-message -V
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)
72
Operating
Table 14 Options
ACTIVATE command options (continued) Description

Verbose mode (display informational messages) Specify a file name. The usage of wildcards like * or ? is possible. 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. Recursion into subdirectories starting at <path>.
--verbose -v <file> --filelist <filelist> -f <filelist> --recursive <path> -r <path> --oem-file-format --unicode-file-format --ansi-file-format --utf8-file-format
The input file list is in OEM format. The input file list is in Unicode format. The input file list is in ANSI format. The input file list is in UTF-8 format (default). The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g). 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). Define minimum time (n) since file was last modified for the specified operation minimum file age. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). Exclude system files. Exclude hidden files. Exclude read-only files. Exclude files with an active-archive bit. Exclude files with an active-compressed bit. Disable file. Creates a file list (outlist) as output.
--minimum-file-size <n>b|k|m|g Define a minimum file size (n) for the specified operation. -S <n>b|k|m|g --minimum-access-time <n>d|h|m|s -A <n>d|h|m|s --minimum-write-time <n>d|h|m|s -W <n>d|h|m|s --exclude-system --exclude-hidden --exclude-read-only --exclude-archive --exclude-compressed --off -F <outlist>
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
FMACLI Activate D:\ASC\MyFile.doc
ARCHIVE
The ARCHIVE command lists the status of the FMA archives.
73
Synopsis
FMACLI Arc[hive] [--help | -h] [{--logfile | -L} <logfile> [--log-info-messages | -V]] [--verbose | -v]
Description
The ARCHIVE command displays an archive list.
Options
Table 15 Options
ARCHIVE command options Description

Displays the online help for the ARCHIVE command.
--log-info-message -V --verbose -v
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) Verbose mode (display informational messages)
Example
FMACLI Arc
Output
Archive List: Id Status Archive Type PI Name Migrated Description ---- -------- ------------ ---- ------------------- -------------- ----------------------0001 OK RSA-FTP 90 FTP01 n/a MO-ERF Data Year 1992 0002 OK RSA-FTP 90 FTP02 n/a MO-ERF Data Year 1993 0003 OK RSA-CIFS 100 CIFS01 2.05 GB MO-ERF Data Year 1994 0004 OK RSA-CIFS 100 CIFS02 1.67 GB MO-ERF Data Year 1995
Description of columns
Table 16 Column
Id Status Archive Type PI Name 74 Operating
Column descriptions Output

Archive Number Archive Status (currently not used) Type of the Remote Storage Adapter (RSA-FTP, -CIFS or -RISS) Performance Index Name of the FMA Archive
Table 16 Column
Migrated
Column descriptions (continued) Output

Migrated Data (not available for FTP as Remote Storage Adapter) Description of the FMA Archive
Description
CLEANUP
The CLEANUP command reorganizes FMA archives.
Synopsis
FMACLI Cle[anup] [--help | -h] [{--logfile | -L} <logfile> [--log-info-messages | -V]] [--verbose | -v] [--expiration <n>d|h|m|s]
Description
Use the CLEANUP command to reorganize FMA archives. This means you will remove copies of deleted files from the archives.
Options
Table 17 Options
CLEANUP command options Description

Displays the online help for the CLEANUP command.
--log-info-message -V --verbose -v --expiration <n>
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) Verbose mode (display informational messages) 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.
Example
FMACLI Cleanup --expiration 30d
This command will clean up all files that were deleted more than 30 days ago.
75
ERASE
The ERASE command deletes FMA metadata from a file.
Synopsis
FMACLI Era[se] [--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] [[--primary-metadata | -Mp] | [--secondary-metadata | -Ma] | [--all-metadata | -Mb]] [--force ] [-F <outlist>]
Description
The ERASE command deletes FMA metadata from a system. CAUTION: The command deletes data without confirmation.
Before erasing a files metadata, recall the file to avoid data loss.
Options
Table 18 Options
ERASE command options Description

Displays the online help for the ERASE command.
--log-info-message -V --verbose -v 76 Operating
Table 18 Options
<file>
ERASE command options (continued) Description

Specify a file name. The usage of wildcards like * or ? is possible. 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. Recursion into subdirectories starting at <path>.
--filelist <filelist> -f <filelist> --recursive <path> -r <path> --oem-file-format --unicode-file-format --ansi-file-format --utf8-file-format
The input file list is in OEM format. The input file list is in Unicode format. The input file list is in ANSI format. The input file list is in UTF-8 format (default). The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g). 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). Define minimum time (n) since file was last modified for the specified operation minimum file age. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). Exclude system files. Exclude hidden files. Exclude read-only files. Exclude files with an active-archive bit. Exclude files with an active-compressed bit. Deletes primary metadata (extended attributes).
--minimum-file-size <n>b|k|m|g Define a minimum file size (n) for the specified operation. -S <n>b|k|m|g --minimum-access-time <n>d|h|m|s -A <n>d|h|m|s --minimum-write-time <n>d|h|m|s -W <n>d|h|m|s --exclude-system --exclude-hidden --exclude-read-only --exclude-archive --exclude-compressed --primary-metadata -Mp --secondary-metadata -Ma --all-metadata -Mb --force -F <outlist> Allows the deletion of offline files. Creates a file list (outlist) as output. Deletes all metadata (default). Deletes secondary metadata (alternate data stream).
Example
FMACLI Erase D:\ABC\MyFile.doc
77
FIND
The FIND command creates a list of files selected according to a certain filter and saves it to a specified file.
Synopsis
FMACLI Find [--help | -h] [{--logfile | -L} <logfile> [--log-info-messages | -V]] [<file>] [{--recursive | -r} <path>] [{--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] [--ignore-files <ignorefile>] [--storage-location {offline|online}] -F <outlist> [--oem-file-format | --unicode-file-format | --ansi-file-format | --utf8-file-format]
Description
The 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
Table 19 Options
FIND command options Description

Displays the online help for the FIND command.
--log-info-message -V <file> --recursive <path> -r <path>
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) Specify a file name. The usage of wildcards like * or ? is possible. Recursion into subdirectories starting at <path>.
--minimum-file-size <n>b|k|m|g Define a minimum file size (n) for the specified operation. -S <n>b|k|m|g The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g).
78
Operating
Table 19 Options
FIND command options (continued) Description

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). Define minimum time (n) since file was last modified for the specified operation minimum file age. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). Exclude system files. Exclude hidden files. Exclude read-only files. Exclude files with an active-archive bit. Exclude files with an active-compressed bit.
--minimum-access-time <n>d|h|m|s -A <n>d|h|m|s --minimum-write-time <n>d|h|m|s -W <n>d|h|m|s --exclude-system --exclude-hidden --exclude-read-only --exclude-archive --exclude-compressed
--ignore-files <ignorefile> Exclude file (ignorefile). The usage of wildcards like * or ? is possible. --storage-location online|offline
-F <outlist> --oem-file-format --unicode-file-format --ansi-file-format --utf8-file-format
Check offline file attribute.

Creates a file list (outlist) as output. The input file list is in OEM format. The input file list is in Unicode format. The input file list is in ANSI format. The input file list is in UTF-8 format (default).
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
FMACLI Find -r D:\Data --storage-location offline -F OfflineFiles.lst
INFO
The INFO command displays FMA metadata.
79
Synopsis
FMACLI Inf[o] [--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] [--long | -l] [-F <outlist>]
Description
This command displays HSM metadata.
Options
Table 20 Options
INFO command options Description

Displays the online help for the INFO command.
--log-info-message -V --verbose -v <file> --filelist <filelist> -f <filelist> --recursive <path> -r <path> --oem-file-format --unicode-file-format
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) Verbose mode (display informational messages) Specify a file name. The usage of wildcards like * or ? is possible. 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. Recursion into subdirectories starting at <path>.
The input file list is in OEM format. The input file list is in Unicode format.
80
Operating
Table 20 Options
INFO command options (continued) Description

The input file list is in ANSI format. The input file list is in UTF-8 format (default). The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g). 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). Define minimum time (n) since file was last modified for the specified operation minimum file age. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). Exclude system files. Exclude hidden files. Exclude read-only files. Exclude files with an active-archive bit. Exclude files with an active-compressed bit. Display all available information (long output). In the short version (default), only one line per file is displayed. Creates a file list (outlist) as output.
--ansi-file-format --utf8-file-format
--minimum-file-size <n>b|k|m|g Define a minimum file size (n) for the specified operation. -S <n>b|k|m|g --minimum-access-time <n>d|h|m|s -A <n>d|h|m|s --minimum-write-time <n>d|h|m|s -W <n>d|h|m|s --exclude-system --exclude-hidden --exclude-read-only --exclude-archive --exclude-compressed --long -l -F <outlist>
Example 1
FMACLI Info -r D:\*.*
Output
Last Modification Size Attributes Status Name ------------------ ---------- ----------- ------- -----------------2005-02-02 17:09:28 18755 -A---O----F 2006-04-21 16:00:14 1088 -A--------2005-07-27 15:42:54 4344083 -A--------2006-04-07 13:56:38 5482 -A--------2006-05-04 06:49:36 102400 -A--------. . . 12 files succeeded 0 files failed 0 files were processed earlier 22579118080 bytes processed OFF(1) MOD SAV(1) SAV(3) D:\ASC\EULA.rtf D:\ASC\fma.txt D:\ASC\FMAAdmGd.pdf D:\ASC\Readme.txt D:\ASC\MyFile.doc
81
Table 21 INFO command output for example 1 Column
Last Modification: Size: Attributes:
Output
Last modification date and time. File size. File attributes: A R S H T F O Archive Read-only System Hidden Temp Sparse Offline
Status:
FMA status: <blank> - unmanaged OFF - Offline MOD - Modified SAV - Migrated INA - Inactive (n) - Number of valid copies
Name:
Fully qualified file name.
Example 2
FMACLI Info -r D:\*.* -l
Output
. . . 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
82
Operating
MIGRATE
The MIGRATE command explicitly migrates a file to the specified archive.
Synopsis
FMACLI Mig[rate] [--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] [{--archive | -a} <arc>] | [--archives <arc1,...>] [{--maximum-copies | -n} <copies>] [--release] [-F <outlist>]
Description
This command creates copies of file data on alternate locations. The data remains on the local hard disk.
Options
Table 22 Options
MIGRATE command options Description

Displays the online help for the MIGRATE command.
--log-info-message -V --verbose -v <file> --filelist <filelist> -f <filelist>
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) Verbose mode (display informational messages) Specify a file name. The usage of wildcards like * or ? is possible. 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.
83
Table 22 Options
MIGRATE command options (continued) Description

Recursion into subdirectories starting at <path>.
--recursive <path> -r <path> --oem-file-format --unicode-file-format --ansi-file-format --utf8-file-format
The input file list is in OEM format. The input file list is in Unicode format. The input file list is in ANSI format. The input file list is in UTF-8 format (default). The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g). 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). Define minimum time (n) since file was last modified for the specified operation minimum file age. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). Exclude system files. Exclude hidden files. Exclude read-only files. Exclude files with an active-archive bit. Exclude files with an active-compressed bit. Name of the archive where the file is stored. This parameter is mandatory for the migration command. Specify a list of archives with maximum 4 archives (arc1, arc2, ... arcN) Set the maximum number of archive copies of a file.
--minimum-file-size <n>b|k|m|g Define a minimum file size (n) for the specified operation. -S <n>b|k|m|g --minimum-access-time <n>d|h|m|s -A <n>d|h|m|s --minimum-write-time <n>d|h|m|s -W <n>d|h|m|s --exclude-system --exclude-hidden --exclude-read-only --exclude-archive --exclude-compressed --archive <arc> -a <arc>
--archives <arc1, ...> --maximum-copies <copies> -n <copies> --release

-F <outlist>
Do releasing the files after a successfully migration. Creates a file list (outlist) as output.
84
Operating
Examples
FMACLI FMACLI FMACLI FMACLI FMACLI Migrate Migrate Migrate Migrate Migrate D:\Test\file.dat -a Arc01 -f c:\temp\miglist.dat -a Arc01 D:\Data -A 4d --archive Arc01 D:\Data -A --archives "Arc01, Arc02, Arc03" -r D:\Data --archive Arc01 --release
Figure 82 MIGRATE command example
POLICY
The POLICY command displays or executes file policies.
Synopsis
FMACLI Pol[icy] [--help | -h] [{--logfile | -L} <logfile> [--log-info-messages | -V]] [--verbose | -v] [--name <polname> | --all | --run <polname>]
85
Description
This 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
Table 23 Options
POLICY command options Description

Displays the online help for the POLICY command.
--log-info-message -V --verbose -v --name <polname> --all --run <polname>
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) Verbose mode (display informational messages) Display a specific policy. Display all policies. Execute a specific policy.
Example
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\*;
RECALL
The RECALL command explicitly recalls data for a released file.
86
Operating
Synopsis
FMACLI Rec[all] [--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] [-F <outlist>]
Description
This 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
Table 24 Options
RECALL command options Description

Displays the online help for the RECALL command.
--log-info-message -V --verbose -v <file> --filelist <filelist> -f <filelist> --recursive <path> -r <path> --oem-file-format --unicode-file-format
The input file list is in OEM format. The input file list is in Unicode format.
87
Table 24 Options
RECALL command options (continued) Description

The input file list is in ANSI format. The input file list is in UTF-8 format (default). The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g). 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). Define minimum time (n) since file was last modified for the specified operation minimum file age. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). Exclude system files. Exclude hidden files. Exclude read-only files. Exclude files with an active-archive bit. Exclude files with an active-compressed bit. Creates a file list (outlist) as output.
--ansi-file-format --utf8-file-format
--minimum-file-size <n>b|k|m|g Define a minimum file size (n) for the specified operation. -S <n>b|k|m|g --minimum-access-time <n>d|h|m|s -A <n>d|h|m|s --minimum-write-time <n>d|h|m|s -W <n>d|h|m|s --exclude-system --exclude-hidden --exclude-read-only --exclude-archive --exclude-compressed -F <outlist>
88
Operating
Example
Figure 83 RECALL command example
RELEASE
The RELEASE command explicitly releases data for a file.
89
Synopsis
FMACLI Rel[ease] [--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] [{--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>]
Description
The 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
Table 25 Options
RELEASE command options Description

Displays the online help for the RELEASE command.
--log-info-message -V --verbose -v <file>
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) Verbose mode (display informational messages) Specify a file name. The usage of wildcards like * or ? is possible.
90
Operating
Table 25 Options
RELEASE command options (continued) Description

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. Recursion into subdirectories starting at <path>.
--filelist <filelist> -f <filelist> --recursive <path> -r <path> --oem-file-format --unicode-file-format --ansi-file-format --utf8-file-format
The input file list is in OEM format. The input file list is in Unicode format. The input file list is in ANSI format. The input file list is in UTF-8 format (default). The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g). 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). Define minimum time (n) since file was last modified for the specified operation minimum file age. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). Exclude system files. Exclude hidden files. Exclude read-only files. Exclude files with an active-archive bit. Exclude files with an active-compressed bit. Changed Retention Time (crt). Time period in minutes (m), hours (h), or days (d) that changed files stay on disk before they are released. 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 Minimum number of copies in the archive before a file can be released.
--minimum-file-size <n>b|k|m|g Define a minimum file size (n) for the specified operation. -S <n>b|k|m|g --minimum-access-time <n>d|h|m|s -A <n>d|h|m|s --minimum-write-time <n>d|h|m|s -W <n>d|h|m|s --exclude-system --exclude-hidden --exclude-read-only --exclude-archive --exclude-compressed --changed-retention-time <crt>m|h|d -t <crt>m|h|d --read-retention-time <rrt>m|h|d -T <rrt>m|h|d --minimum-copies <mc>
-n <mc>
--high-watermark <nn> -u <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. Low-Watermark value (nn) The release process is stopped if the low-watermark (percentage) of the file system is reached. Creates a file list (outlist) as output.
--low-watermark <nn> -U <nn> -F <outlist>
91
Figure 84 Retention times for RELEASE command Table 26 Variable

crt rrt
Variable definitions for Figure 84 Description

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. 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.
Examples
FMACLI Release D:\ASC\MyFile.doc -t 1d -T 10d -n 2
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.
92
Operating
Figure 85 RELEASE command example In this case the file MyFile.doc will be released, when three copies are available on different archives.
RSA
The RSA command lists the status of the remote storage adapter.
Synopsis
FMACLI Rsa [--help | -h] [{--logfile | -L} <logfile> [--log-info-messages | -V]] [--verbose | -v]
Description
The RSA command displays the remote storage adapter status.
93
Options
Table 27 Options
RSA command options Description

Displays the online help for the RSA command.
Example
FMACLI RSA
Output
# 0 1 2 Type ---0 0 0 Capabs -------00000000 00000000 00000000 Name ---------RSA-CIFS RSA-FTP RSA-RISS RSA ---------------RsaCIFS.dll RsaFtp.dll RsaRISS.dll Description -----------------------------"Storage ... specifications" "Storage on ftp server" "Storage on HP RISS"
SYSTEM
The SYSTEM command displays system information.
Synopsis
FMACLI Sys[tem] [--help | -h] [{--logfile | -L} <logfile> [--log-info-messages | -V]] [--verbose | -v]
Description
The SYSTEM command displays system information like version, license, and other FMA settings.
Options
Table 28 Options
--help -h
SYSTEM command options Description

Displays the online help for the SYSTEM command.
94
Operating
Table 28 Options
SYSTEM command options (continued) Description

Specifies a log file. The log file must be specified with a fully qualified path. Log files are created with the following (fixed) policies: 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 -> ...
--logfile <logfile> -L <logfile>
Example
FMACLI Sys
Output
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
VERIFY
The VERIFY command displays the result of the verification process.
95
Synopsis
FMACLI Ver[ify] [--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] [{--local-checks | -o local}] [{--remote-checks | -o remote}] [-F <outlist>]
Description
Local 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
Table 29 Options
VERIFY command options Description

Displays the online help for the VERIFY command.
96
Operating
Table 29 Options
VERIFY command options (continued) Description

--log-info-message -V --verbose -v <file> --filelist <filelist> -f <filelist> --recursive <path> -r <path> --oem-file-format --unicode-file-format --ansi-file-format --utf8-file-format
The input file list is in OEM format. The input file list is in Unicode format. The input file list is in ANSI format. The input file list is in UTF-8 format (default). The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g). 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). Define minimum time (n) since file was last modified for the specified operation minimum file age. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). Exclude system files. Exclude hidden files. Exclude read-only files. Exclude files with an active-archive bit. Exclude files with an active-compressed bit. Verify archive contents. Operation level of verify operation is local (default). Verify archive contents. Operation level of verify operation is remote. Creates a file list (outlist) as output.
--minimum-file-size <n>b|k|m|g Define a minimum file size (n) for the specified operation. -S <n>b|k|m|g --minimum-access-time <n>d|h|m|s -A <n>d|h|m|s --minimum-write-time <n>d|h|m|s -W <n>d|h|m|s --exclude-system --exclude-hidden --exclude-read-only --exclude-archive --exclude-compressed --local-checks -o local --remote-checks -o remote -F <outlist>
97
Example
FMACLI Verify D:\ABC\MyFile.doc -o remote
VERSION
The VERSION command displays version and build information about the installed FMA.
Synopsis
FMACLI Vers[ion] [--help | -h] [{--logfile | -L} <logfile> [--log-info-messages | -V]] [--verbose | -v]
Description
The VERSION command displays version and build information about the installed FMA.
Options
Table 30 Options
VERSION command options Description

Displays the online help for the VERSION command.
Example
FMACLI Vers
Output
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
VOLUME
The VOLUME command displays a list about the managed volumes.
98
Operating
Synopsis
FMACLI Vol[ume] [--help | -h] [{--logfile | -L} <logfile> [--log-info-messages | -V]] [--verbose | -v]
Description
The VOLUME command displays information about the managed volumes.
Options
Table 31 Options
VOLUME command options Description

Displays the online help for the VOLUME command.
Example
FMACLI Vol
Output
Table 32 Column
Id M
Description of columns Output

Index number FMA status:
<blank>: unmanaged X: managed
99
Table 32 Column
Description of columns (continued) Output

Possible values:
Volume Status
Not managed Active Not mounted Error Restricted Cannot be managed Need reboot
HSM Status Possible values:
Active Inactive Unknown

Label FS Serial Migrated Capacity Free Space % PID GUID Volume label File system of this volume (always NTFS by managed volumes) Serial number of the volume Migrated data Disk space (max. available) Free disk space Free disk space in percent HSM process ID of the volume manager process Global unique identifier (36 characters)
Result codes
FMACLI returns 0 if successful. If a fatal error condition occurs, negative values are returned. Positive result codes show warning conditions. Table 33 Result codes Description
No error occurred. Watermark not reached. Error occurred during operation. The command was executed successfully, but some errors occurred. Example: Some of the files could not be processed. (-1) (-2) (-3) (-4) A generic error occurred. Check error messages (stderr) for more information. An invalid parameter was specified. Check error messages to determine the bad parameter. An invalid command was specified. FMA has found a bad configuration. This is caused by invalid archive configuration or duplicate archive IDs.
Return value
(0) (1) (2)
FMA Explorer plug-in

FMA 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.
100 Operating
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
Migrating files or folders

Select 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 folders

Select 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
102 Operating
Recalling files or folders

Select 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 metadata

The FMA Explorer plug-in allows the user to view metadata information on Explorers detail view or on an additional property sheet called FMA. To add additional FMA metadata columns to Explorers 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 Explorers 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.
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-in

The 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:
regsvr32 /u hsmext.dll
To add the plug-in to the Explorer, run:

regsvr32 hsmext.dll
FMAFileUtil
Description
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.
104 Operating
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 interface
Usage
FmaFileUtil [options] command [command-options] <arguments>
Options
Table 34 Option
-v
FmaFileUtil options Description

Verbose output. Write messages of type ERROR, WARNING, or INFO to stdout. <Logfile> Log file output. Write messages of type ERROR to the log file. Verbose log file output. Write messages of type ERROR, WARNING, or INFO to the log file. Displays usage information for command.
-L
-V
-H
If none of these options are used, all messages of type ERROR are written to stdout.
Commands
Table 35 FmaFileUtil commands Description
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.
Command
pack | p
Command options
Table 36 Option
-f <Filelist> -o -r -p
FmaFileUtil command-options Description

All files listed in Filelist will be converted. Overwrite existing destination files. Default is that no files will be overwritten. Recurse into directories. 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).
Arguments (pack command)

Table 37 Option
<sFile> <dFile> <sDir> <dDir>
FmaFileUtil arguments (pack command) Description

Packs the source file (sFile) to destination file (dFile). Packs all files in the source directory (sDir) to the destination directory (dDir). The new files have the same name.
Arguments (unpack command)

Table 38 Option
<sFile> <dFile> <sDir> <dDir>
FmaFileUtil arguments (unpack command) Description

Unpacks the source file (sFile) to destination file (dFile). Unpacks all files in the source directory (sDir) to the destination directory (dDir). The new files have the same name.
Examples
Packs the file File001.dat into the file File001.dat.p:
FmaFileUtil pack File001.dat File001.dat.p
Packs all files in directory d:\Dir001 into directory d:\tmp\Dir001.p:

FmaFileUtil pack d:\Dir001 d:\tmp\Dir001.p
106 Operating
Packs all files in directory d:\Dir001 and its subdirectories into directory d:\tmp\Dir001.p:
FmaFileUtil pack -r d:\Dir001 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:
FmaFileUtil unpack -p -o File001.dat.p File001.dat
Resets the timestamps of the destination file File001.dat to the timestamps preserved in the source file File001.dat.p:
FmaFileUtil unpack -p File001.dat.p File001.dat
Packs all files in directory d:\Dir001 into directory d:\tmp\Dir001.p. If a destination file exists, it will be overwritten:
FmaFileUtil pack -o d:\Dir001 d:\tmp\Dir001.p
Unpacks the file File001.dat.p into the file File001.dat:

FmaFileUtil unpack File001.dat.p File001.dat
Unpacks all files in directory d:\Dir001.p into directory d:\tmp\Dir001:

FmaFileUtil unpack d:\Dir001.p d:\tmp\Dir001
Unpacks all files in directory d:\Dir001.p and its subdirectories into directory d:\tmp\Dir001:
FmaFileUtil unpack -r d:\Dir001.p 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:
FmaFileUtil unpack -o d:\Dir001.p d:\tmp\Dir001
Log files
FMA 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.
The layout of the FMA log file entries are as follows.
Figure 94 Layout of FMA log file entries
FMACLI
To 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 Manager

To 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 log

By 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.
108 Operating
Best practices
Create a new HP StorageWorks File Migration Agent (FMA) archive

FMA archive configuration for a Windows archive
Prerequisites
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 servers 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 FMAs 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 Port UserFile LogFile = = = = c:\fsefs1 21 C:\program files\Hewlett-Packard\FTPServer\GDSFtpServerUsers C:\program files\Hewlett-Packard\FTPServer\GDSFtpServer.log
FMA RSA-FTP Configuration dialog
Figure 95 Rsa Configuration dialogRSA-FTP 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
110 Best practices
Select various options 10. Click the Save button. The new FMA archive is shown in the FMA MMC Snap-In list. 1 The creation of a new FMA archive is finished. 1. 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.
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 archive

For 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 users 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
useradd -m -k /bin/false -d /fma/hmsfs1 -g fma -s /bin/false fma
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.
112 Best practices
In this example, the complete path to the archive directory is /fma/hsmfs1/data1/fma.
Figure 98 Rsa Configuration dialogRSA-FTP 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. 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.
1 The creation of a new FMA archive is finished. 1. 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.
114 Best practices
Note that the primary and secondary archive configuration (FTP user ID, FTP server configuration and archive directory structure) must be identical.
Figure 100 Rsa Configuration dialogRSA-FTP NOTE: For further information about managing FMA archives, see page 38.
FMA archive configuration for a CIFS-based NAS device

For 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 FMAs RSA-CIFS dialog.
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 ConfigurationRSA-CIFS
116 Best practices
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 dialogRSA-CIFS
Figure 103 Replication archive (Microsoft Server) example

FMA archive configuration for RISS

FMA 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 FMAs 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 FMAs recipients options Subject (file name without path and file extension) FMAs 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 documents Access Control List (ACL).
Figure 104 Rsa Configuration dialogRSA-RISS 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.
118 Best practices
Figure 105 Rsa Configuration dialogRSA-RISS FMA only supports one replica site, which is built by one-way (Active/Passive) RISS remote replication services.
Figure 106 Replication archive (RISS) example
Create a new managed volume

To create a new managed volume: 1. Start FMA MMC Snap-In from Windows Start menu. (Start > Programs > HP StorageWorks File Migration Agent > FMA Configuration) 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 policies

To create and schedule migration rules on a managed volume: 1. Start FMA MMC Snap-In from Windows Start menu. (Start > Programs > HP StorageWorks File Migration Agent > FMA Configuration) 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.
120 Best practices
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.
Figure 109 Schedule Options dialog 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.)
Figure 1 Schedule Options dialog 10 Start policies on the 1st of every month. (Select Every week day, if policies should run on certain days of month.)
Figure 1 1 Schedule Options dialog 1

Create disk usage monitoring

To set up the disk space monitor on a managed volume: 1. Start FMA MMC Snap-In from Windows Start menu. (Start > Programs > HP StorageWorks File Migration Agent > FMA Configuration) 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 1 Volume Properties (Watermarks) dialog 12 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 1 Volume Properties (Retention) dialog 13 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 1 Volume Properties (Retention) dialog 14 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.
122 Best practices
Files which should always be online, can be excluded.
Figure 1 Volume Properties (Exclusion) dialog 15
Determine FMA software version

To 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:
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
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 1 Info dialog 16 Or click the About button of the FMA Job Manager to obtain the FMA software version.
Figure 1 About FMA Job Manager dialog 17 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
Migrate files
To migrate files: Use the FMACLI command-line utility to migrate files.
FMACLI migrate f:\testdir\test.* -a myArchive
In the following example, the testdir directory will be migrated into the myArchive archive:
FMACLI migrate -r f:\testdir -a myArchive
To migrate a directory to more than one archives (max. 4), apply:

FMACLI migrate -r f:\testdir -a myArchive, myArchive02
To migrate a directory with immediately release operation after successfully migrating of the directory, apply:
FMACLI migrate -r f:\testdir -a myArchive -n1 --release
Additionally it is possible to migrate files via FMA Explorer plug-in. For further information see FMA Explorer plug-in on page 100.
Release files
To release files: Use the FMACLI command-line utility to release files.
FMACLI release f:\testdir\test.* -n 1
In the following example, the testdir directory will be released:

FMACLI release -r f:\testdir -n 1
Recall files
To recall files: Use the FMACLI command-line utility to recall files.
FMACLI recall f:\testdir\test.*
In the following example, the testdir directory will be recalled:

FMACLI recall -r f:\testdir
Set a high-watermark for migration or releases

To 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 release -r f:\testdir -u 85
124 Best practices
Verify data files

To verify FMA metadata information: Use the FMACLI command-line utility to check whether the FMA metadata of a file object is consistent.
FMACLI verify f:\testdir\test.dat -o local
To check all files of a directory, apply:

FMACLI verify -r f:\testdir -o local
To check if the link to the archive copy of a file is valid, apply:

FMACLI verify f:\testdir\test.dat -o remote
Create an FMA job

To 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 commands

To 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.:
at 10:00 "FMACLI release -r f:\testdir -n 2"
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 jobs

To 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.
Windows 2000:
at 03:00 /every:Su "C:\Program Files\Hewlett-Packard\HP FMA\jobs\MyJob.cmd"
Windows 2003:
schtasks /create /ST 03:00 /D Su /TN "C:\Progr..\MyJob.cmd"
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 FMAs 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 volume

Prerequisites
Copying data to another FMA managed volume needs to be executed by the robocopy.exe command-line tool, which is available from Microsofts Resource Kit.
126 Best practices
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 Microsofts Resource Kit.
------------------------------------------------------------ROBOCOPY :: Robust File Copy for Windows :: Version XP010 -------------------------------------------------------------
2. Create the NoRecRobocopy command:

copy <InstPath>\robocopy.exe %SYSTEMROOT%\system32\NoRecRobocopy.exe
3. Add the process name NoRecRobocopy to FMAs 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 procedure

This 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.
FMACLI act --off -r e:\homedir
(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:
NoRecRobocopy e:\homedir f:\homedir /E /SEC /COPYALL
(Check that all files have been copied successfully to our target location.)
5. Activate the files in the target directory. Description: Activating a file means that FMAs metadata is synchronized to the new system file ID. This step enables the link to the archive copy.
FMACLI act -r f:\homedir
6. Delete the source directory
Relocating a large number of files

If 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:
NoRecRobocopy e:\homedir f:\homedir /E /SEC /COPYALL
4. Activate the files in the target location.

FMACLI act -r f:\homedir
5. Grant access to your target location. 6. Deactivate the files in the source location.
FMACLI act --off -r e:\homedir
7. Delete the files in the source location.
128 Best practices
Appendix
Archive store configuration

FTP 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 module

Minimum requirements for FTP servers
The 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 Linux

Setting up a new group and user
The following statement will add a new user group (with restricted rights) to the system. Enter at the system prompt:
groupadd fma
To add a user with minimal rights, enter at the system prompt:

useradd -m -k /bin/false -d <PartRoot> -g fma -s /bin/false fma
Table 39
Parameters for useradd command Description

Is the root directory of HP StorageWorks File System Extender (FSE) (Linux). Prevents a login via Telnet. Lists the primary group of the FMA user.
Parameter
-d <PartRoot> -s /bin/false -g fma
Example:
useradd -m -k /bin/false -d /fse -g fma -s /bin/false/ fma
By default, the new user account is not activated. The password needs to be changed to activate the account. Enter at the system prompt:
passwd fma
and enter a new password. Default: fmafma
Take ownership of the PartitionRoot

chown -R fma:fma <PartitionRoot>
Activation of INETD
To activate inetd, start the YaST utility with the corresponding parameter:
yast inetd
Check whether inetd is already active. If not, activate inetd.
Configuration of VSFTPD
1. 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.
/etc/vsftpd.userlist
fma
3. Next the configuration file (/etc/vsftpd.conf) of the FTP server must be modified:
/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
NOTE: inetd must be triggered to reread its configuration file:

killall -HUP inetd
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:
dos2unix vsftpd.conf dos2unix vsftpd.userlist
130 Appendix
Configuration for LogRotate

LogRotate 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.
/etc/cron.daily/logrotate
#!/bin/sh /usr/sbin/logrotate /etc/logrotate.conf
2. Make the file executable.

chmod +x /etc/cron.daily/logrotate
3. Create the file: /etc/logrotate.d/fma

/etc/logrotate.d/fma
# Configuration for logrotate /var/log/vsftpd.log { compress size=500M rotate=5 }
Table 40
Parameters for LogRotate command Description

Old versions of log files are compressed with gzip by default. 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. Log files are rotated count times before being removed. If count is 0, old versions are removed rather than rotated.
Parameter
compress size[=]size
rotate[=]count
Configuration of VSFTPD on Red Hat Linux

1. 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.
rpm -ivh vsftpd-1.2.1-3.i386.rpm
2. If vsftpd installation has succeeded you can continue creating a technical user and group: Creating the group fma:
groupadd fma
3. Creating the technical user fma_user:

useradd -d Path -g fma fma_user
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:
passwd fma_user
It is recommended to take fmafma as password 5. To allow user fma_user writing into the FSE partition you should change the user and group assignment of the FSE partition by:
chown -R fma_user:fma
FSE mount point, for instance /fse/fsefs01 6. 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:
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
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 restart Starting 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. 1 Now you can proceed with creating the log rotation as described in the FSE product documentation. 1.
132 Appendix
Configuration of PROFTPD on Sun Solaris

Setting up a new group and user
The following statement will add a new user group (with restricted rights) to the system. Enter at the system prompt:
groupadd fma
To add a user with minimal rights, enter at the system prompt:

useradd -m -k /bin/false -d <PartRoot> -g fma -s /bin/false fma
Table 41
Parameters for useradd command Description

Is the root directory of FSE (Linux). Prevents a login via Telnet. Lists the primary group of the FMA user.
Parameter
-d <PartRoot> -s /bin/false -g fma
Example:
useradd -m -k /bin/false -d /fse -g fma -s /bin/false/ fma
By default, the new user account is not activated. The password needs to be changed to activate the account. Enter at the system prompt:
passwd fma
and enter a new password. Default: fmafma
Configuration of PROFTPD
Modify 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 #
134 Appendix
Using GDS FTP-Server

Install the GDS FTP-Server
Starting 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 1 InstallShield Wizard Welcome dialog 18 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.
Customer information
Figure 1 Customer Information dialog 19 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.
136 Appendix
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.
Configure the GDS FTP-Server

1. 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:
htpasswd -c GDSFtpServerUsers <newuser>
Example:
htpasswd -c GDSFtpServerUsers FmaUser
2. Setup the configuration file. Open the configuration file ftp_server.cfg with a text editor and enter the corresponding parameters: Example:
[default] RootDirectory = g:\FtpRoot Port = 21 UserFile = c:\program files\Hewlett-Packard\FTPServer\GDSFtpServerUsers LogFile = c:\program files\Hewlett-Packard\FTPServer\GDSFtpServer.log
3. Create an NT service. Define the GDS FTP-Server as a Windows NT service. Use the following command:
GDSFtpServer ftp_server.cfg -i srvany.exe
4. Start the FTP service. To start the FTP service, use the following command:
net start GDSFtpServer
Uninstall the GDS FTP-Server

1. 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:
net stop GDSFtpServer
3. Remove the FTP service with the following command:

GDSFtpServer -r
138 Appendix
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 configuration
Integration 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 customers IT environment.
Configuring RISS devices

An 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 installations 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 servers

If data will be stored with Windows Security Descriptor information, the application server must be configured with access to the active-directory server on the customers network.
Required configuration
The 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.
Third-party product compatibility list

Last Update: May 2006
Anti-virus
FMAs interoperability with anti-virus scanners has been successfully tested for the following products.
Symantec AntiVirus
Table 42 Symantec AntiVirus specifications
AntiVirus Symantec Corporate Edition 9.0 and 10.0 2.x Windows 2000, Windows 2003 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. 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 Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions:
Remark:
McAfee VirusScan
Table 43 McAfee VirusScan specifications
VirusScan McAfee Enterprise 8.0 2.x Windows 2000, Windows 2003 None 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 Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
140 Appendix
Sophos Anti-Virus
Table 44 Sophos Anti-Virus specifications
Sophos Anti-Virus Sophos 5.01, 5.1 2.x Windows 2000, Windows 2003 The realtime scan option on-write access is not supported. None Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
ServerProtect
Table 45 ServerProtect specifications
ServerProtect TrendMicro 5.58 2.x Windows 2000, Windows 2003 None Opening the property page of an offline file will trigger a file recall from remote storage. Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
eTrust AntiVirus
Table 46 eTrust AntiVirus specifications eTrust AntiVirus Scanner
Computer Associates International 7.0, 8.0 2.x Windows 2000, Windows 2003 None Because eTrust changes the access timestamp of a file, the release operation should be based on the modification timestamp and the last recall timestamp. Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
TrendMicro OfficeScan
Table 47 TrendMicro OfficeScan specifications OfficeScan
TrendMicro 7.0 2.x Windows 2000, Windows 2003 Product name: Manufacturer: Version: Supported FMA versions: Operating system:
Table 47
TrendMicro OfficeScan specifications (continued)

The realtime scan options scan outgoing files and scan incoming and outgoing files is not supported, when the backup application does not use VSS. Opening the property page of an offline file will trigger a file recall from remote storage.
Restrictions:
Remark:
Backup/restore
FMAs 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
Table 48 BackupExec specifications
BackupExec Veritas 10.0 2.x Windows 2000, Windows 2003 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. None Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
BrightStor ArcServe
Table 49 BrightStor ArcServe specifications
BrightStor ArcServe Backup Computer Associates 1 1 1.1, 1.5 2.x Windows 2000, Windows 2003 None None Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
Data Protector
Table 50 Data Protector specifications
Data Protector HP 5.50 2.x Windows 2000, Windows 2003 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. None Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
142 Appendix
NetBackup
Table 51 NetBackup specifications
Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark: NetBackup Enterprise Server Veritas 5.1, 6.0 2.x Windows 2000, Windows 2003 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. None
Networker
Table 52 Networker specifications
Networker EMC 7.2 2.x Windows 2000, Windows 2003 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. None Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
NetVault
Table 53 NetVault specifications
NetVault BakBone 7.1 1 2.x Windows 2000, Windows 2003 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. None Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
MS VSS
Table 54 MS VSS specifications
Volume Shadow Copy Services (VSS) Microsoft A component of Windows 2003 2.x Windows 2003 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. 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. Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions:
Tivoli Storage Manager

Table 55 Tivoli Storage Manager specifications
Tivoli Storage Manager IBM 5.3.x 2.x Windows 2000, Windows 2003 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 144 Appendix Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions:
Galaxy Backup & Recovery

Table 56 Galaxy Backup & Recovery specifications
Galaxy Backup & Recovery CommVault Systems 6.1 2.x Windows 2000, Windows 2003 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. None Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
Quota/encryption
StorageExec
Table 57 StorageExec specifications
StorageExec Veritas 5.0 2.x Windows 2000, Windows 2003 Only passive limits on FMA managed volumes are supported. None Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
Defragmentation
O & O Defrag
Table 58 O & O Defrag specifications
O & O Defrag O & O Software 8.0 2.x Windows 2000, Windows 2003 None None Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
MS Defragmentation
Table 59 MS Defragmentation specifications
Defragmentation Microsoft Windows 2000, Windows 2003 2.x Windows 2000, Windows 2003 File Migration Agent administrator guide 145 Product name: Manufacturer: Version: Supported FMA versions: Operating system:
Table 59
MS Defragmentation specifications (continued)

None None
Restrictions: Remark:
IndexServer
MS IndexServer
Table 60 MS IndexServer specifications
IndexServer Microsoft Windows 2000, Windows 2003 2.1 Windows 2000, Windows 2003 None (interoperable, no recalls) The IndexServer only keeps index informations of online files. Index informations are lost by releasing files. Product name: Manufacturer: Version: Supported FMA versions: Operating system: Restrictions: Remark:
Error codes
Abstract
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 handling

FMA 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

FMA error: 65537 Code (hex): Text: Description: FMA error: 65538 Code (hex): Text: Description: FMA error: 65539 Code (hex): Text: Description: 0x00010003 File is released. The file is released and, therefore, cannot be migrated. 0x00010002 File is not migrated. The file is not migrated and, therefore, cannot be released or recalled. 0x00010001 File is migrated. The file in question is already migrated. This message is for information only.
146 Appendix
FMA error: 65540 Code (hex): Text: Description: FMA error: 65541 Code (hex): Text: Description: FMA error: 65542 Code (hex): Text: Description: FMA error: 65543 Code (hex): Text: Description: 0x00010007 Not enough copies. 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. 0x00010006 File is not expired. File cannot be released since the retention time has not expired. 0x00010005 Metadata not found. The file does not contain FMA metadata. 0x00010004 File is online. The file is already online and, therefore, cannot be recalled.
FMA error: 65544 Code (hex): Text: Description: FMA error: 65545 Code (hex): Text: Description: 0x00010009 Recalled file was not empty, conflict file was created. A file that is recalled was not empty. The recall was done and a copy of the original file was saved. 0x00010008 Metadata copy cannot be created. A metadata copy cannot be created.
FMA error: 65546 Code (hex): Text: Description: FMA error: 65547 Code (hex): Text: Description: 0x0001000B FMA directory was ignored. 0x0001000A HSM-operation on intermediate file was ignored. HSM operations on intermediate files (conflict and temporary recall) are ignored.
FMA error: 65548 Code (hex): Text: Description: FMA error: 65549 Code (hex): Text: Description: FMA error: 65550 Code (hex): Text: Description: FMA error: 65551 Code (hex): Text: Description: FMA error: 65808 Code (hex): Text: Description: FMA error: 65809 Code (hex): Text: Description: FMA error: 65810 Code (hex): Text: Description: 0x000101 12 Archive unknown. The given archive name (FMACLI option -a) is not defined in the registry. Maybe the name was misspelled or the configuration is not available. 0x000101 1 1 Invalid archive configuration. (not used) 0x000101 10 Archive key not found in registry. The FMA archive key was not found. 0x0001000F FMA file disabled. 0x0001000E FMA metadata recovered. 0x0001000D FMA file inactive. 0x0001000C FMA file active. -
FMA error: 6581 1 Code (hex): Text: Description: 0x000101 13 Duplicate archive ID. 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.
148 Appendix
FMA error: 65825 Code (hex): Text: Description: FMA error: 65826 Code (hex): Text: Description: 0x00010122 Required entry point in RSA library not found. A mandatory function was not found in the specified RSA library. Probable causes: FMA error: 65841 Code (hex): Text: Description: 0x00010131 Metadata corrupt. Metadata is corrupt (CRC does not match). The metadata was manually changed or modified by an application. old version of library file corrupted library file 0x00010121 RSA-Library cannot be loaded. The defined library module cannot be loaded.
FMA error: 65842 Code (hex): Text: Description: FMA error: 65843 Code (hex): Text: Description: FMA error: 65844 Code (hex): Text: Description: FMA error: 65845 Code (hex): Text: Description: 0x00010135 Duplicate active metadata. 0x00010134 Invalid storage handle. A new storage could not be allocated. 0x00010133 Metadata is invalid. (not used) 0x00010132 Metadata error. Metadata of the file cannot be loaded.
FMA error: 65857 Code (hex): Text: Description: FMA error: 65858 Code (hex): Text: Description: FMA error: 65859 Code (hex): Text: Description: FMA error: 65873 Code (hex): Text: Description: FMA error: 65874 Code (hex): Text: Description: FMA error: 65888 Code (hex): Text: Description: 0x00010160 Stubfile is not empty, recall cancelled. 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. 0x00010152 Unable to create metadata copy. 0x00010151 Directory tree for metadata copy cannot be created. 0x00010143 Target file exists, import operation aborted. 0x00010142 Metadata exists on the target file, import operation aborted. 0x00010141 Reading metadata from import file failed. -
FMA error: 65889 Code (hex): Text: Description: FMA error: 65890 Code (hex): Text: Description: 0x00010162 Recall file modified. 0x00010161 During recall an offline flag was removed. -
150 Appendix
FMA error: 65891 Code (hex): Text: Description: FMA error: 65904 Code (hex): Text: Description: FMA error: 65905 Code (hex): Text: Description: FMA error: 65920 Code (hex): Text: Description: FMA error: 65936 Code (hex): Text: Description: FMA error: 65937 Code (hex): Text: Description: FMA error: 65938 Code (hex): Text: Description: FMA error: 66049 Code (hex): Text: Description: 0x00010201 Verify, stubfile not empty A stubfile contains data. 0x00010192 Verify, error 0x00010191 Verify, warning. 0x00010190 Verify, info. 0x00010180 Verification of file failed. 0x00010171 Maximum of HSM operations are reached. 0x00010170 Touch operation after release failed. 0x00010163 Error when creating TMPREC file -
FMA error: 66050 Code (hex): Text: Description: FMA error: 66051 Code (hex): Text: Description: FMA error: 66052 Code (hex): Text: Description: FMA error: 66053 Code (hex): Text: Description: FMA error: 66054 Code (hex): Text: Description: FMA error: 66055 Code (hex): Text: Description: FMA error: 66056 Code (hex): Text: Description: FMA error: 66057 Code (hex): Text: Description: 0x00010209 Verify, dirty flag mismatch. 0x00010208 Verify, offline attribute is invalid. 0x00010207 Verify, offline attribute is missing. 0x00010206 Verify, no archive links. None of the files links are available. 0x00010205 Verify, bad archive links. Some links of a file are invalid. 0x00010204 Verify, stubfile modified. A stubfile was modified without recall. 0x00010203 Verify, metadata complete. Parts of the metadata are incomplete. 0x00010202 Verify, no metadata for offline file. An offline file does not contain metadata.
152 Appendix
FMA error: 66305 Code (hex): Text: Description: FMA error: 66306 Code (hex): Text: Description: FMA error: 66307 Code (hex): Text: Description: FMA error: 66308 Code (hex): Text: Description: FMA error: 66309 Code (hex): Text: Description: FMA error: 66310 Code (hex): Text: Description: 0x00010306 Error: Volume doesnt match. A file is added to a list that contains files from a different volume. The volume status is invalid for this operation status. 0x00010305 Error: Invalid volume status. The volume status for this operation status is invalid. 0x00010304 Error: Volume not managed. The volume on which the file resides is not managed. 0x00010303 Error: Volume serials are not unique. 0x00010302 Error: Configuration invalid. Error in FMA configuration. 0x00010301 Error: Subsystem not avail. Unable to connect to FMAKSS.
FMA error: 6631 1 Code (hex): Text: Description: FMA error: 66312 Code (hex): Text: Description: 0x00010308 Error: List empty. The specified list contains no entries. 0x00010307 Error: List invalid. The specified list is not valid (not initialized, and so on).
FMA error: 66320 Code (hex): Text: Description: FMA error: 66321 Code (hex): Text: Description: FMA error: 66322 Code (hex): Text: Description: FMA error: 66322 Code (hex): Text: Description: FMA error: 66323 Code (hex): Text: Description: FMA error: 66324 Code (hex): Text: Description: FMA error: 66325 Code (hex): Text: Description: FMA error: 66326 Code (hex): Text: Description: 0x00010316 Error: Subsystem is busy. The subsystem is busy and rejected the request. 0x00010315 Error: Capacity expired. The capacity is expired. 0x00010314 Capacity warning. The capacity is at 90%. 0x00010313 Evaluation period warning. An evaluation period will expire in 10 days. 0x00010312 Error: Evaluation period expired. An evaluation license has expired. 0x00010312 Error: Evaluation period expired. An evaluation license has expired. 0x0001031 1 Error: No license found. No license was found. 0x00010310 Error: License. Generic error in licensing module.
154 Appendix
FMA error: 66327 Code (hex): Text: Description: FMA error: 66328 Code (hex): Text: Description: FMA error: 66561 Code (hex): Text: Description: FMA error: 66562 Code (hex): Text: Description: FMA error: 66592 Code (hex): Text: Description: FMA error: 66593 Code (hex): Text: Description: FMA error: 66608 Code (hex): Text: Description: FMA error: 66609 Code (hex): Text: Description: 0x00010431 Error: Moving GC logs failed. The cleanup was unable to move GC logs to cleanup folder. 0x00010430 Error: Cleanup is active. The cleanup process is already active and cannot be started twice. 0x00010421 Error: Metadata import too large. The metadata import is too large. 0x00010420 Error: Metadata import. The metadata import failed. 0x00010402 Error: Deleted archive. The returned archive value is invalid. 0x00010401 Error: Duplicate archive name. An archive name is used more than once. 0x00010318 Error: Activate no object ID. No object ID for file to activate. 0x00010317 Error: Subsystem error. Unable to connect to the subsystem.
FMA error: 66610 Code (hex): Text: Description: FMA error: 6661 1 Code (hex): Text: Description: FMA error: 66612 Code (hex): Text: Description: FMA error: 66613 Code (hex): Text: Description: FMA error: 66614 Code (hex): Text: Description: FMA error: 66817 Code (hex): Text: Description: FMA error: 66818 Code (hex): Text: Description: FMA error: 66897 Code (hex): Text: Description: 0x00010551 Error: CFGSVC unknown function. Unknown function in config service. 0x00010502 Error: RRP protocol. Error in RRP protocol. 0x00010501 Error: RRP connect. Unable to connect to destination. 0x00010436 Error: GC log format. The GC log is not in the expected format. 0x00010435 Error: Storage descriptor buffer is too small. The storage descriptor data does not fit into the buffer. 0x00010434 Error: Cleanup file. An error occurred while reading from GC file. 0x00010433 Error: Cleanup EOF. End of current GC log file (internally used only). 0x00010432 Error: Cleanup no more entries. End of GC log entries reached.
156 Appendix
FMA error: 66898 Code (hex): Text: Description: FMA error: 131073 Code (hex): Text: Description: FMA error: 131074 Code (hex): Text: Description: FMA error: 131075 Code (hex): Text: Description: FMA error: 131076 Code (hex): Text: Description: FMA error: 131077 Code (hex): Text: Description: FMA error: 131078 Code (hex): Text: Description: FMA error: 131079 Code (hex): Text: Description: 0x00020007 Error: Archive pool is empty 0x00020006 Error: No capacity in archive pool 0x00020005 Error: Archive key not found 0x00020004 Error: Unable to load RSA-DLL 0x00020003 Error: Invalid archive entry. 0x00020002 Error: Duplicate archive ID. 0x00020001 Archive Error 0x00010552 Error: CFGSVC protocol. Error in config server protocol.
FMA error: 131080 Code (hex): Text: Description: FMA error: 131081 Code (hex): Text: Description: FMA error: 131082 Code (hex): Text: Description: FMA error: 131083 Code (hex): Text: Description: FMA error: 131083 Code (hex): Text: Description: FMA error: 196609 Code (hex): Text: Description: FMA error: 196610 Code (hex): Text: Description: FMA error: 19661 1 Code (hex): Text: Description: 0x00030003 Error: Volume isnt a fixed disk. 0x00030002 Error: Maximum managed volumes exceeded. 0x00030001 Managed volume error. 0x0002000C Archive deleted. The archive entry is deleted. 0x0002000B Error: Invalid archive name. 0x0002000A Error: Maximum of archives reached. 0x00020009 Error: Duplicate archive name 0x00020008 Error while write Windows registry -
158 Appendix
FMA error: 196612 Code (hex): Text: Description: FMA error: 196613 Code (hex): Text: Description: FMA error: 196614 Code (hex): Text: Description: FMA error: 196615 Code (hex): Text: Description: FMA error: 262145 Code (hex): Text: Description: FMA error: 262146 Code (hex): Text: Description: FMA error: 262147 Code (hex): Text: Description: FMA error: 262148 Code (hex): Text: Description: 0x00040004 Error: Read header (Archive storage subsystem). 0x00040003 Write error in archive storage subsystem. 0x00040002 Read error in archive storage subsystem. 0x00040001 Error while open target file (Archive storage subsystem). 0x00030007 Error: Start of the volume manager failed. 0x00030006 Error: Volume filter isnt available. 0x00030005 Error: Volume unmount - failed. 0x00030004 Error: Volume unmount - invalid state. -
FMA error: 262149 Code (hex): Text: Description: FMA error: 262150 Code (hex): Text: Description: FMA error: 262151 Code (hex): Text: Description: FMA error: 262152 Code (hex): Text: Description: FMA error: 262154 Code (hex): Text: Description: FMA error: 262155 Code (hex): Text: Description: FMA error: 327681 Code (hex): Text: Description: FMA error: 327682 Code (hex): Text: Description: 0x00050002 No metadata found. 0x00050001 Metadata recovered. 0x0004000B Error: Data corrupt in archive storage subsystem. 0x0004000A Error: Wrong number write in archive storage subsystem. 0x00040008 Error: Wrong number read in archive storage subsystem. 0x00040007 Error: Open shadow (Archive storage subsystem) 0x00040006 Error: Invalid access mode in archive storage subsystem. 0x00040005 Error: Invalid header in archive storage subsystem. -
160 Appendix
FMA error: 327937 Code (hex): Text: Description: FMA error: 327938 Code (hex): Text: Description: FMA error: 327939 Code (hex): Text: Description: FMA error: 328192 Code (hex): Text: Description: FMA error: 328193 Code (hex): Text: Description: FMA error: 328194 Code (hex): Text: Description: FMA error: 328195 Code (hex): Text: Description: FMA error: 328196 Code (hex): Text: Description: 0x00050204 Verify: Alternate metadata not found. 0x00050203 Verify: Primary metadata not found. 0x00050202 Verify: Metadata differs. 0x00050201 Verify: Size of metadata differs. 0x00050200 Error: Unexpected verify error (Metadata handling). 0x00050103 Error: Metadata record not found. 0x00050102 Error: Metadata corrupt. 0x00050101 Error: File ID doesnt match (Metadata handling). -
FMA error: 328197 Code (hex): Text: Description: FMA error: 393217 Code (hex): Text: Description: FMA error: 393218 Code (hex): Text: Description: FMA error: 393219 Code (hex): Text: Description: FMA error: 393220 Code (hex): Text: Description: FMA error: 393221 Code (hex): Text: Description: FMA error: 393222 Code (hex): Text: Description: FMA error: 393223 Code (hex): Text: Description: 0x00060007 Error: Storage descriptor invalid (RSA). File cannot be stored (space, and so on). 0x00060006 Error: Configuration error. Unexpected error in RSA configuration. 0x00060005 Error: RSA configuration cancelled The configuration dialog was canceled by user. 0x00060004 Error: Storage (RSA) File cannot be stored (space, and so on). 0x00060003 Error: RSA authentication 0x00060002 Error: RSA connection 0x00060001 RSA Error. 0x00050205 Verify: Metadata not found. -
162 Appendix
FMA error: 393472 Code (hex): Text: Description: FMA error: 393473 Code (hex): Text: Description: FMA error: 393474 Code (hex): Text: Description: FMA error: 393475 Code (hex): Text: Description: FMA error: 393505 Code (hex): Text: Description: FMA error: 393506 Code (hex): Text: Description: FMA error: 393507 Code (hex): Text: Description: FMA error: 393508 Code (hex): Text: Description: 0x00060124 Error: Unknown storage descriptor (RSA). The specified storage descriptor is unknown. 0x00060123 Error: Stream write failed (RSA). The specified stream buffer is too small. It must be larger than 20 bytes. 0x00060122 Error: Stream format is to small (RSA). The specified stream buffer is too small. It must be larger than 20 bytes. 0x00060121 Error: Stream format (RSA). 0x00060103 Error: exist (RSA). 0x00060102 Error: Verify file size (RSA). 0x00060101 Error: Verify date write (RSA). 0x00060100 Verify error (RSA). Generic error.
FMA error: 393509 Code (hex): Text: Description: FMA error: 393510 Code (hex): Text: Description: FMA error: 39351 1 Code (hex): Text: Description: FMA error: 393512 Code (hex): Text: Description: FMA error: 393513 Code (hex): Text: Description: FMA error: 393520 Code (hex): Text: Description: FMA error: 393521 Code (hex): Text: Description: FMA error: 393522 Code (hex): Text: Description: 0x00060132 Error: Internal storage error (RSA) 0x00060131 Error: No storage meta data (RSA). No storage meta data found. 0x00060130 Error: Storage meta data error (RSA). The meta data of the archive storage are corrupt. 0x00060129 Error: Inactive archive (RSA). The archive is inactive due to a invalid configuration. 0x00060128 Error: Archive status info exists (RSA). The archive status database already exists. 0x00060127 Error: Archive status info lost (RSA). The archive status database does not exist. 0x00060126 Error: Archive status info is corrupted (RSA). The archive status database is corrupted. 0x00060125 Error: Adapter mismatch (RSA). The specified storage descriptor does not belong to the used RSA module.
164 Appendix
FMA error: 458753 Code (hex): Text: Description: FMA error: 458754 Code (hex): Text: Description: FMA error: 458755 Code (hex): Text: Description: FMA error: 458756 Code (hex): Text: Description: FMA error: 458757 Code (hex): Text: Description: FMA error: 458758 Code (hex): Text: Description: FMA error: 458759 Code (hex): Text: Description: FMA error: 458760 Code (hex): Text: Description: 0x00070008 Error: Storage descriptor header size. 0x00070007 Error while SIZE command execution (RSA-FTP). 0x00070006 Error while MODDATE command execution (RSA-FTP). 0x00070005 Error: Invalid archive filename (RSA-FTP). 0x00070004 Error: FTP login (RSA-FTP). 0x00070003 Error: FTP connect (RSA-FTP). 0x00070002 Error: FTP access (RSA-FTP). 0x00070001 Error: Create header (RSA-FTP). -
FMA error: 458761 Code (hex): Text: Description: FMA error: 458762 Code (hex): Text: Description: FMA error: 458763 Code (hex): Text: Description: FMA error: 458764 Code (hex): Text: Description: FMA error: 458765 Code (hex): Text: Description: FMA error: 458766 Code (hex): Text: Description: FMA error: 458767 Code (hex): Text: Description: FMA error: 458768 Code (hex): Text: Description: 0x00070010 Error while FTP AUTHENTICATION command execution 0x0007000F Error while FTP READ command execution (RSA-FTP). 0x0007000E Error while FTP WRITE command execution (RSA-FTP). 0x0007000D Error: Archive storage subsystem (RSA-FTP). 0x0007000C Error: Wrong file size (RSA-FTP). 0x0007000B Error: Server not supported (RSA-FTP). 0x0007000A Error while SOCKET command execution (RSA-FTP). 0x00070009 Error while MKPATH command execution (RSA-FTP). -
166 Appendix
FMA error: 458769 Code (hex): Text: Description: FMA error: 458770 Code (hex): Text: Description: FMA error: 458771 Code (hex): Text: Description: FMA error: 458772 Code (hex): Text: Description: FMA error: 458773 Code (hex): Text: Description: 0x00070015 Error while FTP CLOSE command execution (RSA-FTP). Closing the FTP connection failed. 0x00070014 Error: Configuration (RSA-FTP). 0x00070013 Error: Unicode conversion (RSA-FTP). 0x00070012 Error while FTP RMDIR command execution (RSA-FTP). 0x0007001 1 Error while FTP DELETE command execution (RSA-FTP). -
WIN32 error codes

For getting a description of system error codes (Code No. 0 - 61 18), see Microsoft error list or call the Hewlett-Packard Co. Service Center.
Reporting a problem
Have 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:
HKEY_LOCAL_MACHINE\Software\Hewlett-Packard\HP FMA HKEY_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.
168 Appendix
Index
Symbols
_IFE_FILEINFO attribute 21 configuration about 37 backend archives 38 CIFS-based NAS device archives 115 clusters 54 FMA Job Manager 68 GDS FTP-Server 138 job parameters 63 job settings 67 Linux archives 112 managed volumes 46, 50 migration parameters 64 Red Hat Linux VSFTPD 131 release parameters 66 RISS applications 139 RISS archives 118 RSA-CIFS 40 RSA-FTP 43, 110, 129 RSA-RISS 44 Sun Solaris PROFTPD 133 SuSE Linux VSFTPD 129 Windows archives 109 conventions document 14 text symbols 14 copying software 30 creating disk usage monitoring 122 file policies 120 managed volumes 120 Custom Setup dialog 29
A
ACTIVATE command 71 anti-virus product compatibility 140 ARCHIVE command 73 Archive Properties dialog 39 archives adding for migration operation 65 backing up and restoring managed volumes 126 CIFS-based NAS device 115 CLEANUP command 75 configure backend 38 defined 19 deleting 46 error codes 157 Linux 112 MIGRATE command 83 properties 39 RECALL command 22 RELEASE command 22 RISS 118 Windows 109 arguments, FMAFileUtil 106 audience 13
B
backend archives, configure 38 backend datastore, defined 19 backing up managed volumes 126 backup/restore applications, compatibility 142 BackupExec 142 benefits 20 BrightStor ArcServe 142
D
Data Protector 142 defragmentation software compatibility 145 deleting archives 46 jobs 67 managed volumes 49 metadata 76 Destination Folder dialog 28 disabling files 72 disk space monitoring 51 setting up monitoring 122 document conventions 14 prerequisites 13 related documentation 13 documentation HP web site 13 providing feedback 15
C
CD-ROM, installation 27 CIFS-based NAS device archives 115 CLEANUP command 75 clusters, configuring 54 command-line tools 23 commands FMACLI 69 FMAFileUtil 106 scheduling 125 compatibility, third-party products anti-virus 140 backup/restore 142 defragmentation 145 IndexServer 146 quota/encryption 145 components, software 23
E
ERASE command 76 error codes FMA 146 VOLUME command 100 WIN32 167 eTrust AntiVirus 141 event log, Windows 108
F
file names, FMACLI 69 file policies creating 120 overview 53 FILE_ATTRIBUTE_OFFLINE flag 21 FIND command 78 first use 25 FMA backend archives 38 backing up and restoring managed volumes 126 CIFS-based NAS device archives 115 cluster configuration 54 command-line tools 23 components 23 configuration 37 copying software 30 Custom Setup dialog 29 deleting archives 46 error codes 146 features 20 first steps 25 installation path 28 installing 27 license agreement 28 Linux archives 112 log files 107 metadata attribute 21 MIGRATE command 22 migration overview 17 offline marker 21 operating systems supported 24 policies 51 prerequisites 24 RECALL command 22 RELEASE command 22 relocating data 126 restrictions 24 RISS archives 118 scheduling commands 125 Setup Type 29 uninstalling 33 updates 35 user privileges 24 version number, displaying 123 Windows archives 109
FMA Explorer plug-in features 24 migrating files 102 overview 100 recalling files 103 registering 104 releasing files 102 unregistering 104 viewing metadata 103 FMA Job Manager About button 68 archives, adding 65 configuring 68 deleting jobs 67 dialog 61 features 24 job settings 67 log files 108 migration parameters 64 new jobs, creating 62 parameters 63 release parameters 66 running jobs 67 scheduling jobs 68, 125 starting 62 FMA MMC Snap-In 23, 37 FMA Policy Manager features 23 FMA Wizard features 23 FMACLI ACTIVATE command 71 ARCHIVE command 73 CLEANUP command 75 commands 69 ERASE command 76 file names 69 FIND command 78 INFO command 79 log files 108 MIGRATE command 22, 83 POLICY command 85 RECALL command 86 RELEASE command 22, 89 RSA command 93 syntax 69 SYSTEM command 94 VERIFY command 95 VERSION command 98 VOLUME command 98 FMAFileUtil arguments 106 commands 106 features 23 options 105 storing data 104
170
FTP backend archives 38 command requirements 129 configuration dialog 110 configuring 43 error codes 165 installing GDS FTP-Server 135 Linux archives 112 Red Hat Linux and VSFTPD configuration 131 Sun Solaris and PROFTPD configuration 133 SuSE Linux and VSFTPD configuration 129 Windows archives 109
jobs creating new 62 deleting 67 parameters 63 running 67 scheduling 68, 125 settings 67
L
license agreement FMA 28 license keys 35 Linux archives 112 RSA-FTP setup 129 Linux archives 112 local checks 96 locking files 22 log files FMA 107 FMA Job Manager 108 FMACLI 108 LogRotate configuration 131
G
Galaxy Backup & Recovery 145 GDS FTP-Server configuring 109, 138 Customer Information dialog 136 installation path 136 installing 135 Setup Type dialog 136 uninstalling 138 glossary 19
H
help, obtaining 14 high-watermark, setting 124 HP technical support 14 HP StorageWorks File Migration Agent. See FMA HP StorageWorks File System Extender (FSE) 17 HSM metadata, defined 19
M
managed volumes backing up and restoring 126 clusters 58 creating 48, 120 defined 19 deleting 49 disk space 51 displaying information about 98 file policies 53 list 46 properties 50 relocating data 126 scheduling 53 starting unmounted 49 status 46 stopping 48 McAfee VirusScan 140 metadata deleting 76 displaying 79 error codes 146 file IDSs, repairing 71 storage attribute 21 verification 96 Microsoft Cluster system 54 Microsoft Installer (MSI), updating with 35 MIGRATE command 83, 124 migrating files 124 migrating files, FMA Explorer plug-in 102
I
inactive files, defined 19 IndexServer software compatibility 146 INETD activation 130 INFO command 79 installation path FMA 28 GDS FTP-Server 136 installing FMA copying software 30 Custom Setup dialog 29 destination folder 28 license agreement 28 Setup Type dialog 29 starting 27 installing GDS FTP-Server 135
J
Job Manager. See FMA Job Manager
migration command-line 124 defined 19 error codes 146 high-watermark, setting 124 overview 17 parameters 64 minor updates 35 monitoring, disk space 51 MS Defragmentation 145 MS IndexServer 146 MS VSS 144
N
NAS device archives 115 NetBackup 143 NetVault 143 Networker 143 nodes, cluster 55
O
O & O Defrag 145 offline files marker 21 RECALL command 22 operating systems supported 24
P
parameters jobs 63 LogRotate command 131 migration 64 release 66 PartitionRoot ownership 130 policies 51 POLICY command 85 prerequisites 13 privileges, users FMA 24 Red Hat Linux 131 Sun Solaris 133 SuSE Linux 129 PROFTPD users, adding 133
release defined 19 high-watermark setting 124 parameters 66 RELEASE command 22, 89, 124 releasing files, FMA Explorer plug-in 102 relocating data 126 large number of files 128 remote checks 96 remote storage adapter, defined 19 removing FMA 33 GDS FTP-Server 138 restoring managed volumes 126 restrictions 24 result codes, VOLUME command 100 RISS archives 118 backend archives 38 configuring 44, 139 RISS archives 118 RSA command 93 RSA-CIFS backend archives 38 configuring 40 RSA-FTP backend archives 38 commands supported 129 configuration dialog 110 configuring 43 error codes 165 Red Hat Linux and VSFTPD configuration 131 SuSE Linux and VSFTPD configuration 129 RSA-RISS archives 118 backend archives 38 configuring 44 running jobs 67
S
scheduling FMA command 125 jobs 68, 125 managed volumes 53 ServerProtect 141 setup program 27 Setup Type dialog FMA 29 GDS FTP-Server 136 software FMA components 23 third-party compatibility 140 Sophos Anti-Virus 141 status managed volumes 46 RSA 93 Storage descriptor creation dialog 45 StorageExec 145
Q
quota/encryption third-party product compatibility 145
R
RECALL command 22, 86, 124 recall, defined 19 recalling files, FMA Explorer plug-in 103 Red Hat Linux VSFTPD configuration 131 registering, FMA Explorer plug-in 104 related documentation 13
172
stubfile, defined 19 Subscriber's Choice, HP 15 Sun Solaris PROFTPD configuration 133 SuSE Linux VSFTPD configuration 129 Symantec AntiVirus 140 symbols in text 14 syntax, FMACLI 69 SYSTEM command 94 system requirements 24
T
technical support service locator web site 15 technical support, HP 14 technical users adding in Red Hat Linux 131 adding in Sun Solaris 133 adding in SuSE Linux 129 FMA 24 terminology 19 text symbols 14 third-party product compatibility anti-virus 140 backup/restore 142 defragmentation 145 IndexServer 146 quota/encryption 145 Tivoli Storage Manager 144 TrendMicro OfficeScan 141 troubleshooting FMA error codes 146 VOLUME command errors 100 WIN32 error codes 167
volumes, managed backing up and restoring 126 clusters 58 creating 48, 120 defined 19 deleting 49 displaying information about 98 file policies 53 list 46 monitoring 51 properties 50 relocating data 126 scheduling 53 starting unmounted 49 status 46 stopping 48 VSFTPD configuration 130 LogRotate 131 users, adding 129, 131 VSS 144
W
watermark, setting 124 web sites HP 15 HP Subscriber's Choice for Business 15 product manuals 13 WIN32 error codes 167 Windows archives 109 event log 108 Windows archives 109
U
uninstalling FMA 33 GDS FTP-Server 138 unregistering, FMA Explorer plug-in 104 updates, minor 35 users, technical adding in Red Hat Linux 131 adding in Sun Solaris 133 adding in SuSE Linux 129 FMA 24
V
VERIFY command 95 verifying data files 125 VERSION command 98 version, displaying FMA 123 viewing metadata, FMA Explorer plug-in 103 VOLUME command 98
174

FMA V2 Administration Guide

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

FMA V2 Administration Guide

Hochgeladen von

Copyright:

Verfügbare Formate

HP StorageWorks File Migration Agent administrator guide

Part number: T4274-96105 Second edition: October 2006

File Migration Agent administrator guide

2 Installation, uninstall, update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

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

File Migration Agent administrator guide

5 Best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

File Migration Agent administrator guide

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Figures

File Migration Agent administrator guide

About this guide

File Migration Agent administrator guide

Document conventions and symbols

Monospace, italic font

Monospace, bold font

Provides clarifying information or specific instructions.

Provides additional information.

Provides helpful hints and shortcuts.

File Migration Agent administrator guide

HP StorageWorks File Migration Agent overview

Figure 3 Hierarchical storage management in heterogeneous networks

File Migration Agent administrator guide

Figure 4 Offline file attribute

File state diagram

Figure 5 State of files managed by FMA

Figure 6 FMA software components

FMA command-line tools FMACLI

FMA Policy Manager

FMA Explorer plug-in

FMA Job Manager

Operating system version

File Migration Agent administrator guide

Installation, uninstall, update

Install the FMA software

File Migration Agent administrator guide

Installation, uninstall, update

Define installed features

File Migration Agent administrator guide

Figure 12 Installing the HSM Explorer Extension

Copying the FMA software

Installation, uninstall, update

Technical user for the File Migration Agent service

Figure 15 Select User dialog

File Migration Agent administrator guide

Installation, uninstall, update

Figure 18 FMA installation directory structure

Uninstall the FMA software

Figure 20 InstallShield Wizard (Remove) dialog

File Migration Agent administrator guide

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

Installation, uninstall, update

Minor updates from version 2.x

FMA License Keys

File Migration Agent administrator guide

FMA licensing problems

Installation, uninstall, update

File Migration Agent administrator guide

Figure 25 FMA MCC Snap-In configuration items

Managing FMA archives

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

Archive Properties dialog Description

File Migration Agent administrator guide

Figure 29 Editing existing FMA archives