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.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FMA licensing problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Managing FMA archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure backend archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output . . . . . . . . . . . . . . . . . . . . . . Description of columns . . . . . . . . . . . CLEANUP . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . Options . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . ERASE . . . . . . . . . . . . . . . . . . . . . . . . . Synopsis . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . .
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Local Check (Level 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Remote Check (Level 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create an FMA job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule FMA commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule FMA jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defragmentation . . . . . . O & O Defrag . . . . . MS Defragmentation . IndexServer. . . . . . . . . . MS IndexServer . . . . Error codes . . . . . . . . . . . . Abstract . . . . . . . . . . . . FMA error handling . . . . FMA error codes . . . WIN32 error codes . Reporting a problem . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. ..
45 Stopping managed volumes—Not mounted status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 46 Context menu for starting unmounted volumes again . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 47 Starting unmounted volumes again—Active status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 48 Context menu for stopping managed volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 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 10 Rsa Configuration dialog—RSA-RISS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rsa Configuration dialog—RSA-RISS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replication archive (RISS) example . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . .
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.
Document conventions and symbols Document conventions Table 1 Convention Element Medium blue text: Figure 1 Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
• 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.
1 Product information HP StorageWorks File Migration Agent overview HP StorageWorks File Migration Agent (FMA) offers a technologically innovative approach to data movement by maintaining active files on high-performance primary storage while archiving inactive files to cost-effective secondary storage.
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.
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.
sparse file and the file’s data contains zero bytes. The link to the file’s data in the backend datastore is kept in the extended attributes of the file. In addition, a stubfile is marked “offline” (offline flag is set). Volume Policy A set of watermarks and retention periods that determine the automatic release strategy. Key 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.
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.
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).
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.
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.
• 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.
Product information
2 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.
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.
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.
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.
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.
The Advanced button can be used to set up a search for the user account. Figure 16 Select User (Advanced) dialog Click Finish on the Wizard Summary page to continue the installation process. Figure 17 InstallShield Wizard Completed dialog After this, the installation of the FMA software is completed. Click Finish to exit the FMA setup and reboot the system.
During this installation process, the following structure is created under the defined FMA installation directory (here C:\Program Files\Hewlett-Packard\HP FMA\). Figure 18 FMA installation directory structure FMA 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.
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.
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.
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.
3 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.
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.
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 Archive Properties dialog Setting Description Archive name: Name of the archive definition. This name is used as a reference to this archive in FMA for migration and recall operations.
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 dialog—RSA-CIFS Table 3 Rsa Configuration dialog—RSA-CIFS Setting Description Primary archive: Fully qualified NAS path where the data is migrated to and recalled from. Path names can also be specified using UNC notation. The specified path must exist.
Table 3 Rsa Configuration dialog—RSA-CIFS (continued) Setting Description Ignore system name ... : If this option is selected, the system name will not be used to generate a storage descriptor in the archive storage. If this option is off, the system name will be used to create a storage descriptor. For further information about this option, see page 45. NOTE: You should only use this option when you can be sure that the storage descriptor without the system name is unique. Ignore volume serial ...
The FMA User needs to be granted Full Control permissions. Figure 32 Permissions for data (Security) dialog 2. NTFS Folder Permissions: Click the Security tab on the folder’s property page and grant Full Control permissions to the FMA User.
RSA-FTP Figure 34 Rsa Configuration dialog—RSA-FTP Table 4 Rsa Configuration dialog—RSA-FTP Setting Description Host/IP: Hostname or IP address of the FTP server used for accessing the primary archive location. Secondary Host/IP: Hostname or IP address of the FTP server used for recalls if the primary archive instance is not available. Port: FTP port (default: 21). User: FTP user. Password: Password. Root path: Root path on the specified FTP server.
Table 4 Rsa Configuration dialog—RSA-FTP (continued) Setting Description Ignore system name ... : If this option is selected, the system name will not be used to generate a storage descriptor in the archive storage. If this option is off, the system name will be used to create a storage descriptor. For further information about this option, see page 45. NOTE: You should only use this option when you can be sure that the storage descriptor without the system name is unique. Ignore volume serial ...
Rsa Configuration dialog—RSA-RISS (continued) Table 5 Setting Description Default repository: Default repository where the data is stored. Recipients: Default recipients for FMA data. Recipients options See text in Figure 35. 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.
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: \\\. 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.
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.
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.
The symbol of the volume is changed. The status of the volume is set to Not mounted. The HSM status is Inactive. Figure 45 Stopping managed volumes—Not mounted status 3. No HSM operations (migrate, release, recall) are available now. Start an unmounted volume again 1. Right-click the corresponding volume entry to display the context menu. Figure 46 Context menu for starting unmounted volumes again 2. Select the Start item in the context menu. The symbol of the volume is changed.
3. Right-click the corresponding volume entry to display the context menu. 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.
FMA policies FMA policies can be configured by selecting Managed Volumes and double-clicking the corresponding managed volume.
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.
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.
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.
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.
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.
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).
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.
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.
Configuration
4 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).
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.
Job parameters Figure 73 Job dialog Table 9 Job dialog Setting Description Job: Job name. Descr: Description of the job. Directory: Directory that is managed by FMA. Log File: Specifies a log file. The log file must be specified with a fully qualified path. Log files are created with the following (fixed) policies: • • • Ignore Files: The default name of the log file is jobname plus the extension .log. Maximum size of a log file is 4 MB.
Migration parameters Figure 74 Migration dialog Table 10 Migration dialog Setting Description Minimum file size: Define a minimum file size for the migration operation. The value can be specified in bytes, kilobytes, megabytes, or gigabytes. Minimum time interval (modified): Define minimum time interval since the file was last modified for the migration operation to start. The value can be specified in seconds, minutes, hours, or days.
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.
Release parameters Figure 77 Release dialog Table 11 Release dialog Setting Description Release Files: If this option is active, the job contains a release operation. Retention time for migrated files: Time period (crt) that changed files stay on disk before they are released. The value can be specified in seconds, minutes, hours, or days. Retention time for recalled files: Time period (rrt) that recalled and unchanged files stay on disk before they are released.
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.
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.
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.
Following commands of the FMA command line interface (FMACLI) are supported: Table 13 command 70 Operating Supported FMACLI commands Act[ivate] Repair metadata file IDs after restore from a backup. For further information, see page 71. Arc[hive] This command is needed for the archive management. For further information, see page 73. Cle[anup] This command reorganizes FMA archives. For further information, see page 75. Era[se] This command deletes FMA metadata. For further information, see page 76.
FMACLI commands Enter FMACLI or FMACLI --help to display a list of the available FMACLI commands.
Synopsis FMACLI Act[ivate] [--help | -h] [{--logfile | -L} [--log-info-messages | -V]] [--verbose | -v] [] | [{--filelist] | -f} ] [{--recursive | -r} ] [--oem-file-format | --unicode-file-format | --ansi-file-format | --utf8-file-format] [{--minimum-file-size | -S} b|k|m|g] [{--minimum-access-time | -A} d|h|m|s] [{--minimum-write-time | -W} d|h|m|s] [--exclude-system] [--exclude-hidden] [--exclude-read-only] [--exclude-archive] [--exclude-compressed] [--off] [-F
Table 14 ACTIVATE command options (continued) Options Description --verbose Verbose mode (display informational messages) -v Specify a file name. The usage of wildcards like * or ? is possible. --filelist Specify an input file list (default: stdin). Files in the file list are separated by CR/LF. File names can be relative or fully qualified. If you plan to run scripts, use fully qualified names only.
Synopsis FMACLI Arc[hive] [--help | -h] [{--logfile | -L} [--log-info-messages | -V]] [--verbose | -v] Description The ARCHIVE command displays an archive list. Options Table 15 ARCHIVE command options Options Description --help Displays the online help for the ARCHIVE command. -h --logfile Specifies a log file. -L 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.
Table 16 Column descriptions (continued) Column Output Migrated Migrated Data (not available for FTP as Remote Storage Adapter) Description Description of the FMA Archive CLEANUP The CLEANUP command reorganizes FMA archives. Synopsis FMACLI Cle[anup] [--help | -h] [{--logfile | -L} [--log-info-messages | -V]] [--verbose | -v] [--expiration 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.
ERASE The ERASE command deletes FMA metadata from a file.
Table 18 ERASE command options (continued) Options Description Specify a file name. The usage of wildcards like * or ? is possible. --filelist Specify an input file list (default: stdin). Files in the file list are separated by CR/LF. File names can be relative or fully qualified. If you plan to run scripts, use fully qualified names only. -f --recursive Recursion into subdirectories starting at .
FIND The FIND command creates a list of files selected according to a certain filter and saves it to a specified file.
Table 19 FIND command options (continued) Options Description --minimum-access-time d|h|m|s Define minimum time (n) since file was last accessed for the specified operation. -A d|h|m|s The value can be specified in seconds (s), minutes (m), hours (h), or days (d). --minimum-write-time d|h|m|s Define minimum time (n) since file was last modified for the specified operation minimum file age. -W d|h|m|s The value can be specified in seconds (s), minutes (m), hours (h), or days (d).
Synopsis FMACLI Inf[o] [--help | -h] [{--logfile | -L} [--log-info-messages | -V]] [--verbose | -v] [] | [{--filelist] | -f} ] [{--recursive | -r} ] [--oem-file-format | --unicode-file-format | --ansi-file-format | --utf8-file-format] [{--minimum-file-size | -S} b|k|m|g] [{--minimum-access-time | -A} d|h|m|s] [{--minimum-write-time | -W} d|h|m|s] [--exclude-system] [--exclude-hidden] [--exclude-read-only] [--exclude-archive] [--exclude-compressed] [--long | -l] [-F <
Table 20 INFO command options (continued) Options Description --ansi-file-format The input file list is in ANSI format. --utf8-file-format The input file list is in UTF-8 format (default). --minimum-file-size b|k|m|g Define a minimum file size (n) for the specified operation. -S b|k|m|g The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g). --minimum-access-time d|h|m|s Define minimum time (n) since file was last accessed for the specified operation.
Description of columns Table 21 INFO command output for example 1 Column Output Last Modification: Last modification date and time. Size: File size. Attributes: File attributes: A R S H T F O Status: - Archive Read-only System Hidden Temp Sparse Offline FMA status: - 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.
MIGRATE The MIGRATE command explicitly migrates a file to the specified archive.
Table 22 MIGRATE command options (continued) Options Description --recursive Recursion into subdirectories starting at . -r --oem-file-format The input file list is in OEM format. --unicode-file-format The input file list is in Unicode format. --ansi-file-format The input file list is in ANSI format. --utf8-file-format The input file list is in UTF-8 format (default). --minimum-file-size b|k|m|g Define a minimum file size (n) for the specified operation.
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.
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 POLICY command options Options Description --help Displays the online help for the POLICY command. -h --logfile Specifies a log file. -L The log file must be specified with a fully qualified path.
Synopsis FMACLI Rec[all] [--help | -h] [{--logfile | -L} [--log-info-messages | -V]] [--verbose | -v] [] | [{--filelist] | -f} ] [{--recursive | -r} ] [--oem-file-format | --unicode-file-format | --ansi-file-format | --utf8-file-format] [{--minimum-file-size | -S} b|k|m|g] [{--minimum-access-time | -A} d|h|m|s] [{--minimum-write-time | -W} d|h|m|s] [--exclude-system] [--exclude-hidden] [--exclude-read-only] [--exclude-archive] [--exclude-compressed] [-F ] D
Table 24 RECALL command options (continued) Options Description --ansi-file-format The input file list is in ANSI format. --utf8-file-format The input file list is in UTF-8 format (default). --minimum-file-size b|k|m|g Define a minimum file size (n) for the specified operation. -S b|k|m|g The value can be specified in bytes (b), kilobytes (k), megabytes (m), or gigabytes (g). --minimum-access-time d|h|m|s Define minimum time (n) since file was last accessed for the specified operation.
Example Figure 83 RECALL command example RELEASE The RELEASE command explicitly releases data for a file.
Synopsis FMACLI Rel[ease] [--help | -h] [{--logfile | -L} [--log-info-messages | -V]] [--verbose | -v] [] | [{--filelist] | -f} ] [{--recursive | -r} ] [--oem-file-format | --unicode-file-format | --ansi-file-format | --utf8-file-format] [{--minimum-file-size | -S} b|k|m|g] [{--minimum-access-time | -A} d|h|m|s] [{--minimum-write-time | -W} d|h|m|s] [--exclude-system] [--exclude-hidden] [--exclude-read-only] [--exclude-archive] [--exclude-compressed] [{--minimum-copi
Table 25 RELEASE command options (continued) Options Description --filelist Specify an input file list (default: stdin). Files in the file list are separated by CR/LF. File names can be relative or fully qualified. If you plan to run scripts, use fully qualified names only. -f --recursive Recursion into subdirectories starting at . -r --oem-file-format The input file list is in OEM format. --unicode-file-format The input file list is in Unicode format.
Figure 84 Retention times for RELEASE command Table 26 Variable definitions for Figure 84 Variable Description crt This is the time period for migrated and changed files. All files will remain on disk for the specified time period before they become a release candidate. rrt This is the time period for recalled and unchanged files. All recalled and unchanged files will remain on disk for the specified time period before they become again a release candidate.
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} [--log-info-messages | -V]] [--verbose | -v] Description The RSA command displays the remote storage adapter status.
Options Table 27 RSA command options Options Description --help Displays the online help for the RSA command. -h --logfile Specifies a log file. -L 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.
Table 28 SYSTEM command options (continued) Options Description --logfile Specifies a log file. -L The log file must be specified with a fully qualified path. Log files are created with the following (fixed) policies: • • --log-info-message -V --verbose -v 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 -> ...
Synopsis FMACLI Ver[ify] [--help | -h] [{--logfile | -L} [--log-info-messages | -V]] [--verbose | -v] [] | [{--filelist] | -f} ] [{--recursive | -r} ] [--oem-file-format | --unicode-file-format | --ansi-file-format | --utf8-file-format] [{--minimum-file-size | -S} b|k|m|g] [{--minimum-access-time | -A} d|h|m|s] [{--minimum-write-time | -W} d|h|m|s] [--exclude-system] [--exclude-hidden] [--exclude-read-only] [--exclude-archive] [--exclude-compressed] [{--local-checks
Table 29 VERIFY command options (continued) Options Description --log-info-message Write informational messages to log file. This option is meaningful only in combination with the -L / --logfile option. (Default: only errors are written to log) -V --verbose -v Verbose mode (display informational messages) Specify a file name. The usage of wildcards like * or ? is possible. --filelist Specify an input file list (default: stdin). Files in the file list are separated by CR/LF.
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} [--log-info-messages | -V]] [--verbose | -v] Description The VERSION command displays version and build information about the installed FMA. Options Table 30 VERSION command options Options Description --help Displays the online help for the VERSION command.
Synopsis FMACLI Vol[ume] [--help | -h] [{--logfile | -L} [--log-info-messages | -V]] [--verbose | -v] Description The VOLUME command displays information about the managed volumes. Options Table 31 VOLUME command options Options Description --help Displays the online help for the VOLUME command. -h --logfile Specifies a log file. -L The log file must be specified with a fully qualified path.
Table 32 Description of columns (continued) Column Output Volume Status Possible values: • Not managed • Active • Not mounted • Error • Restricted • Cannot be managed • Need reboot HSM Status Possible values: • Active • Inactive • Unknown Label Volume label FS File system of this volume (always NTFS by managed volumes) Serial Serial number of the volume Migrated Migrated data Capacity Disk space (max.
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.
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.
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 Explorer’s detail view or on an additional property sheet called “FMA.” To add additional FMA metadata columns to Explorer’s detail view, right-click one of the column headers and select the More command from the menu.
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.
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] Options Table 34 FmaFileUtil options Option Description -v Verbose output.
Commands Table 35 FmaFileUtil commands Command Description pack | p Create a packed file (new Format) based on an NTFS file Input is an NTFS file, output is a file in the FMA Storage Format. All NTFS file information is included. unpack | u Create an NTFS file based on a packed file. Input is a packed file, output is an NTFS file. All NTFS streams saved in the packed file are written into the created NTFS file.
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.
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.
5 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.
FMA RSA-FTP Configuration dialog Figure 95 Rsa Configuration dialog—RSA-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.
• Select various options 10. Click the Save button. The new FMA archive is shown in the FMA MMC Snap-In list. 11. The creation of a new FMA archive is finished. If the backend archive is replicated outside of FMA via some replication mechanism such as the HP Continuous Access (HP CA) for the FSE Archive, the host name or IP address of the secondary system needs to be added to the entry field Secondary Host/IP.
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.
In this example, the complete path to the archive directory is /fma/hsmfs1/data1/fma. Figure 98 Rsa Configuration dialog—RSA-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.
11. The creation of a new FMA archive is finished. If the backend archive is replicated outside of FMA via some replication mechanism such as the HP CA for the FSE Archive, the host name or IP address of the secondary system needs to be added to the entry field Secondary Host/IP. Figure 99 Replication archive (Linux) example In this case recall requests are switched to the secondary system, when the primary archive is not accessible.
Note that the primary and secondary archive configuration (FTP user ID, FTP server configuration and archive directory structure) must be identical. Figure 100 Rsa Configuration dialog—RSA-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.
Example: If the share “archives” has been created on the NAS device NAS_DEVICE, subsequent archives can be set up through FMA RSA-CIFS configuration: \\NAS_DEVICE\archives\users \\NAS_DEVICE\archives\projects Figure 101 Rsa Configuration—RSA-CIFS 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.
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 FMA’s RSA-RISS configuration, a specific set of metadata about the document can be attached to the binary object.
Figure 105 Rsa Configuration dialog—RSA-RISS FMA only supports one replica site, which is built by one-way (Active/Passive) RISS remote replication services.
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.
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.
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.
Files which should always be online, can be excluded. Figure 115 Volume Properties (Exclusion) dialog 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.
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.
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.
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.
To avoid recall operations during copying of your data, it is recommended that you create a duplicate of the robocopy utility with the name NoRecRobocopy.exe and add the process name NoRecRobocopy to the list of modules for which FMA allows a physical view to the file system. Therefore, the following steps are necessary: 1. Install the robocopy.exe utility Version XP010 or higher by installing Microsoft’s Resource Kit.
5. Activate the files in the target directory. Description: Activating a file means that FMA’s metadata is synchronized to the new system file ID. This step enables the link to the archive copy. FMACLI act -r f:\homedir 6.
A 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.
Take ownership of the PartitionRoot chown -R fma:fma 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.
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.
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.
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 -g fma -s /bin/false fma Table 41 Parameters for useradd command Parameter Description -d Is the root directory of FSE (Linux). -s /bin/false Prevents a login via Telnet.
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 AllowOverwrite on RootLogin on AllowAll Allow from all # alternative host or net # Logging options # TransferLog /var/adm/proftpd.
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.
Customer information Figure 119 Customer Information dialog Install the GDS FTP-Server for anyone who uses this computer. Click the Next button to continue. Installation path In this dialog, enter the setup type. When clicking the Complete option, the GDS FTP-Server will be installed in the default directory. Figure 120 Setup Type dialog The default installation path is %ProgramPath%\Hewlett-Packard\FTPServer.
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 Example: htpasswd -c GDSFtpServerUsers FmaUser 2. Setup the configuration file. Open the configuration file ftp_server.
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.
Third-party product compatibility list Last Update: May 2006 Anti-virus FMA’s interoperability with anti-virus scanners has been successfully tested for the following products. Symantec AntiVirus Table 42 Symantec AntiVirus specifications Product name: AntiVirus Manufacturer: Symantec Version: Corporate Edition 9.0 and 10.0 Supported FMA versions: 2.x Operating system: Windows 2000, Windows 2003 Restrictions: The feature “scan files opened for backup” is not supported.
Sophos Anti-Virus Table 44 Sophos Anti-Virus specifications Product name: Sophos Anti-Virus Manufacturer: Sophos Version: 5.01, 5.1 Supported FMA versions: 2.x Operating system: Windows 2000, Windows 2003 Restrictions: The realtime scan option “on-write access” is not supported. Remark: None ServerProtect Table 45 ServerProtect specifications Product name: ServerProtect Manufacturer: TrendMicro Version: 5.58 Supported FMA versions: 2.
Table 47 TrendMicro OfficeScan specifications (continued) Restrictions: The realtime scan options “scan outgoing files” and “scan incoming and outgoing files” is not supported, when the backup application does not use VSS. Remark: Opening the property page of an offline file will trigger a file recall from remote storage. Backup/restore FMA’s interoperability with backup/restore applications has been successfully tested for file system backup/restore operations with the following products.
NetBackup Table 51 NetBackup specifications Product name: NetBackup Enterprise Server Manufacturer: Veritas Version: 5.1, 6.0 Supported FMA versions: 2.x Operating system: Windows 2000, Windows 2003 Restrictions: FMA does not support “file activation” for files that have been restored to a new location. Restoring files is only supported to their original location. Remark: None Networker Table 52 Networker specifications Product name: Networker Manufacturer: EMC Version: 7.
MS VSS Table 54 MS VSS specifications Product name: Volume Shadow Copy Services (VSS) Manufacturer: Microsoft Version: A component of Windows 2003 Supported FMA versions: 2.x Operating system: Windows 2003 Restrictions: FMA does not support “file activation” for files that have been restored to a new location. Restoring files is only supported to their original location. 1.
Galaxy Backup & Recovery Table 56 Galaxy Backup & Recovery specifications Product name: Galaxy Backup & Recovery Manufacturer: CommVault Systems Version: 6.1 Supported FMA versions: 2.x Operating system: Windows 2000, Windows 2003 Restrictions: FMA does not support “file activation” for files, which have been restored to a new location. Restoring files is only supported to their original location.
Table 59 MS Defragmentation specifications (continued) Restrictions: None Remark: None IndexServer MS IndexServer Table 60 MS IndexServer specifications Product name: IndexServer Manufacturer: Microsoft Version: Windows 2000, Windows 2003 Supported FMA versions: 2.1 Operating system: Windows 2000, Windows 2003 Restrictions: None (interoperable, no recalls) Remark: The IndexServer only keeps index informations of online files. Index informations are lost by releasing files.
FMA error: 65540 Code (hex): 0x00010004 Text: File is online. Description: The file is already online and, therefore, cannot be recalled. FMA error: 65541 Code (hex): 0x00010005 Text: Metadata not found. Description: The file does not contain FMA metadata. FMA error: 65542 Code (hex): 0x00010006 Text: File is not expired. Description: File cannot be released since the retention time has not expired. FMA error: 65543 Code (hex): 0x00010007 Text: Not enough copies.
FMA error: 65548 Code (hex): 0x0001000C Text: FMA file active. Description: - FMA error: 65549 Code (hex): 0x0001000D Text: FMA file inactive. Description: - FMA error: 65550 Code (hex): 0x0001000E Text: FMA metadata recovered. Description: - FMA error: 65551 Code (hex): 0x0001000F Text: FMA file disabled. Description: - FMA error: 65808 Code (hex): 0x00010110 Text: Archive key not found in registry. Description: The FMA archive key was not found.
FMA error: 65825 Code (hex): 0x00010121 Text: RSA-Library cannot be loaded. Description: The defined library module cannot be loaded. FMA error: 65826 Code (hex): 0x00010122 Text: Required entry point in RSA library not found. Description: A mandatory function was not found in the specified RSA library. Probable causes: • • old version of library file corrupted library file FMA error: 65841 Code (hex): 0x00010131 Text: Metadata corrupt.
FMA error: 65857 Code (hex): 0x00010141 Text: Reading metadata from import file failed. Description: - FMA error: 65858 Code (hex): 0x00010142 Text: Metadata exists on the target file, import operation aborted. Description: - FMA error: 65859 Code (hex): 0x00010143 Text: Target file exists, import operation aborted. Description: - FMA error: 65873 Code (hex): 0x00010151 Text: Directory tree for metadata copy cannot be created.
FMA error: 65891 Code (hex): 0x00010163 Text: Error when creating TMPREC file Description: - FMA error: 65904 Code (hex): 0x00010170 Text: Touch operation after release failed. Description: - FMA error: 65905 Code (hex): 0x00010171 Text: Maximum of HSM operations are reached. Description: - FMA error: 65920 Code (hex): 0x00010180 Text: Verification of file failed. Description: - FMA error: 65936 Code (hex): 0x00010190 Text: Verify, info.
FMA error: 66050 Code (hex): 0x00010202 Text: Verify, no metadata for offline file. Description: An offline file does not contain metadata. FMA error: 66051 Code (hex): 0x00010203 Text: Verify, metadata complete. Description: Parts of the metadata are incomplete. FMA error: 66052 Code (hex): 0x00010204 Text: Verify, stubfile modified. Description: A stubfile was modified without recall. FMA error: 66053 Code (hex): 0x00010205 Text: Verify, bad archive links.
FMA error: 66305 Code (hex): 0x00010301 Text: Error: Subsystem not avail. Description: Unable to connect to FMAKSS. FMA error: 66306 Code (hex): 0x00010302 Text: Error: Configuration invalid. Description: Error in FMA configuration. FMA error: 66307 Code (hex): 0x00010303 Text: Error: Volume serials are not unique. Description: - FMA error: 66308 Code (hex): 0x00010304 Text: Error: Volume not managed. Description: The volume on which the file resides is not managed.
FMA error: 66320 Code (hex): 0x00010310 Text: Error: License. Description: Generic error in licensing module. FMA error: 66321 Code (hex): 0x00010311 Text: Error: No license found. Description: No license was found. FMA error: 66322 Code (hex): 0x00010312 Text: Error: Evaluation period expired. Description: An evaluation license has expired. FMA error: 66322 Code (hex): 0x00010312 Text: Error: Evaluation period expired. Description: An evaluation license has expired.
FMA error: 66327 Code (hex): 0x00010317 Text: Error: Subsystem error. Description: Unable to connect to the subsystem. FMA error: 66328 Code (hex): 0x00010318 Text: Error: Activate no object ID. Description: No object ID for file to activate. FMA error: 66561 Code (hex): 0x00010401 Text: Error: Duplicate archive name. Description: An archive name is used more than once. FMA error: 66562 Code (hex): 0x00010402 Text: Error: Deleted archive.
FMA error: 66610 Code (hex): 0x00010432 Text: Error: Cleanup no more entries. Description: End of GC log entries reached. FMA error: 66611 Code (hex): 0x00010433 Text: Error: Cleanup EOF. Description: End of current GC log file (internally used only). FMA error: 66612 Code (hex): 0x00010434 Text: Error: Cleanup file. Description: An error occurred while reading from GC file. FMA error: 66613 Code (hex): 0x00010435 Text: Error: Storage descriptor buffer is too small.
FMA error: 66898 Code (hex): 0x00010552 Text: Error: CFGSVC protocol. Description: Error in config server protocol. FMA error: 131073 Code (hex): 0x00020001 Text: Archive Error Description: - FMA error: 131074 Code (hex): 0x00020002 Text: Error: Duplicate archive ID. Description: - FMA error: 131075 Code (hex): 0x00020003 Text: Error: Invalid archive entry.
FMA error: 131080 Code (hex): 0x00020008 Text: Error while write Windows registry Description: - FMA error: 131081 Code (hex): 0x00020009 Text: Error: Duplicate archive name Description: - FMA error: 131082 Code (hex): 0x0002000A Text: Error: Maximum of archives reached. Description: - FMA error: 131083 Code (hex): 0x0002000B Text: Error: Invalid archive name. Description: - FMA error: 131083 Code (hex): 0x0002000C Text: Archive deleted.
FMA error: 196612 Code (hex): 0x00030004 Text: Error: Volume unmount - invalid state. Description: - FMA error: 196613 Code (hex): 0x00030005 Text: Error: Volume unmount - failed. Description: - FMA error: 196614 Code (hex): 0x00030006 Text: Error: Volume filter isn’t available. Description: - FMA error: 196615 Code (hex): 0x00030007 Text: Error: Start of the volume manager failed.
FMA error: 262149 Code (hex): 0x00040005 Text: Error: Invalid header in archive storage subsystem. Description: - FMA error: 262150 Code (hex): 0x00040006 Text: Error: Invalid access mode in archive storage subsystem. Description: - FMA error: 262151 Code (hex): 0x00040007 Text: Error: Open shadow (Archive storage subsystem) Description: - FMA error: 262152 Code (hex): 0x00040008 Text: Error: Wrong number read in archive storage subsystem.
FMA error: 327937 Code (hex): 0x00050101 Text: Error: File ID doesn’t match (Metadata handling). Description: - FMA error: 327938 Code (hex): 0x00050102 Text: Error: Metadata corrupt. Description: - FMA error: 327939 Code (hex): 0x00050103 Text: Error: Metadata record not found. Description: - FMA error: 328192 Code (hex): 0x00050200 Text: Error: Unexpected verify error (Metadata handling).
FMA error: 328197 Code (hex): 0x00050205 Text: Verify: Metadata not found. Description: - FMA error: 393217 Code (hex): 0x00060001 Text: RSA Error. Description: - FMA error: 393218 Code (hex): 0x00060002 Text: Error: RSA connection Description: - FMA error: 393219 Code (hex): 0x00060003 Text: Error: RSA authentication Description: - FMA error: 393220 Code (hex): 0x00060004 Text: Error: Storage (RSA) Description: File cannot be stored (space, and so on).
FMA error: 393472 Code (hex): 0x00060100 Text: Verify error (RSA). Description: Generic error. FMA error: 393473 Code (hex): 0x00060101 Text: Error: Verify date write (RSA). Description: - FMA error: 393474 Code (hex): 0x00060102 Text: Error: Verify file size (RSA). Description: - FMA error: 393475 Code (hex): 0x00060103 Text: Error: exist (RSA). Description: - FMA error: 393505 Code (hex): 0x00060121 Text: Error: Stream format (RSA).
FMA error: 393509 Code (hex): 0x00060125 Text: Error: Adapter mismatch (RSA). Description: The specified storage descriptor does not belong to the used RSA module. FMA error: 393510 Code (hex): 0x00060126 Text: Error: Archive status info is corrupted (RSA). Description: The archive status database is corrupted. FMA error: 393511 Code (hex): 0x00060127 Text: Error: Archive status info lost (RSA). Description: The archive status database does not exist.
FMA error: 458753 Code (hex): 0x00070001 Text: Error: Create header (RSA-FTP). Description: - FMA error: 458754 Code (hex): 0x00070002 Text: Error: FTP access (RSA-FTP). Description: - FMA error: 458755 Code (hex): 0x00070003 Text: Error: FTP connect (RSA-FTP). Description: - FMA error: 458756 Code (hex): 0x00070004 Text: Error: FTP login (RSA-FTP). Description: - FMA error: 458757 Code (hex): 0x00070005 Text: Error: Invalid archive filename (RSA-FTP).
FMA error: 458761 Code (hex): 0x00070009 Text: Error while MKPATH command execution (RSA-FTP). Description: - FMA error: 458762 Code (hex): 0x0007000A Text: Error while SOCKET command execution (RSA-FTP). Description: - FMA error: 458763 Code (hex): 0x0007000B Text: Error: Server not supported (RSA-FTP). Description: - FMA error: 458764 Code (hex): 0x0007000C Text: Error: Wrong file size (RSA-FTP).
FMA error: 458769 Code (hex): 0x00070011 Text: Error while FTP DELETE command execution (RSA-FTP). Description: - FMA error: 458770 Code (hex): 0x00070012 Text: Error while FTP RMDIR command execution (RSA-FTP). Description: - FMA error: 458771 Code (hex): 0x00070013 Text: Error: Unicode conversion (RSA-FTP). Description: - FMA error: 458772 Code (hex): 0x00070014 Text: Error: Configuration (RSA-FTP).
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 to a file. • If an FMA command line operation failed, either provide the log file or a screen shot of the stdout/stderr output.
Index Symbols _IFE_FILEINFO attribute 21 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
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 fi
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 Galaxy Backup & Recovery 145 GDS FTP-Server configuring 109, 138 Customer Information dialog 136 installation path 136
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 pre
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 defragmentatio
