HP Software File Migration Agent (FMA®) Installation and Administration Guide Published: July 2009
© Copyright 2009 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Primary and secondary configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Storage descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Create a new HP StorageWorks File Migration Agent (FMA) archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 FMA archive configuration for a Windows FTP archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 FMA archive configuration for an Linux FTP archive . . . . . . . . . . . . . . . . . . . . .
C Third-party Product Compatibility List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Anti-virus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Symantec AntiVirus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 McAfee VirusScan . . . . . . . . . . . . . . . . . .
Preface Welcome to the File Migration Agent Installation and Administration Guide. This guide provides the information required to install and work with File Migration Agent (FMA®). FMA enables systematic migration of inactive and rarely used data on Windows file servers to Hierarchical Storage Management (HSM) systems or other Network Attached Storage (NAS) devices. Before migration is enabled, an FMA user must define the volumes to be managed and the archives where data will be stored.
Typographical conventions This guide uses the following typographical conventions: Convention Description Bold Used for file names, field names, URLs, interface elements that are clicked/selected, and information that must be used literally. Bold Italic Represents variables within file names, command syntax, URLs, or other literal text. Italics Used for emphasis, book titles, and variables.
Support You can visit the HP Software Support web site at: http://www.hp.com/go/hpsoftwaresupport HP Software Support Online provides an efficient way to access interactive technical support tools.
x | Preface
Overview File Migration Agent (FMA) offers a technologically innovative approach to data management by maintaining active files on high-performance primary storage while archiving inactive files on cost-effective secondary storage. FMA does not require changes to the current directory structure and integrates seamlessly into the existing IT infrastructure. FMA only manages files on specified volumes on the file server defined as managed volumes.
Migration During the migration process, FMA adds FMA-specific metadata to a managed file on a file server and copies the managed file to one or more archives.
Cluster operation When running on a Microsoft Cluster Server, an instance of FMA is installed and running on each node. Two of the FMA services are concurrently active on all nodes. The Active File Management (AFMSvc) and the Volume Manager (HsmSvc) run concurrently on each node to handle file migrations and recalls on any managed volumes that might be active on those nodes. A third service, the Configuration service (HsmCfgSvc), runs only on the node currently hosting the cluster group resources.
FMAFileUtil Use FMAFileUtil to manually retrieve and store data on FTP-based archives. For details about this utility, see Using FmaFileUtil to work with FTP archives on page 37.
Installation This chapter describes the tasks you must perform to install File Migration Agent (FMA). These tasks include the following: 1. Create the technical user required by the FMA service. 2. Configure backup management applications to ensure that data on file servers continues to be backed up as expected. 3. Install FMA on each file server with files that you want to manage. 4. If you are installing in a Windows cluster environment, run the FMA cluster configuration wizard.
Configuring backup management applications to work with FMA Managed volumes and archives must be backed up regularly. FMA is an archiving solution and does not replace the current backup solution. Refer to the File Migration Release Notes for a list of supported backup management applications and their limitations with FMA.
• Do not migrate or release files during the backup window to ensure that the backups of the managed volumes and CIFS archives are synchronized and consistent. • As a best practice, create two archive copies when using CIFS archives. • FMA archive cleanup expiration time must be greater than the backup retention time. For information about cleanup, see Removing deleted files from archives on page 44. • Ensure that a replica of a file is backed up before that file is released from the managed volume.
• Microsoft Windows Storage Server 2003 R2 SP2 Standard and Enterprise Edition • HP Windows Unified Data Storage Server (WUDSS) 2003 • Microsoft Windows Server 2003 R2 NFS server with the following restrictions: • Windows can only handle paths with a maximum length of 260 characters. • UNIX and Windows systems use different user and group IDs. Therefore, there needs to be a corresponding set of user and group IDs on the UNIX system to the Windows system.
6. Configure file policies and schedules on the managed volumes using the FMA Policy Manager (see Migrating and releasing files using file policies on page 51). 7. Configure the watermarks and retention periods for disk space monitoring of the managed volumes using the FMA Policy Manager (see Releasing files using disk space policies on page 48). You must install FMA on each file server to be managed.
4. On the License Agreement dialog box, read the agreement, select whether to accept it, and click Next. You cannot continue with installation unless you accept the license agreement. The Destination Folder dialog box is displayed: 5. On the Destination Folder dialog box, choose the location where to install FMA. • To install in the default location, click Next. This is recommended.
6. On the Setup Type dialog box, choose whether to install all features or select features. • To install all features, which is recommended, click Next. • To install select features or if you are installing in a Windows cluster environment, select Custom and then click Next. The Custom Setup dialog box is displayed: Click the icon on the Custom Setup dialog box next to the files you do not want to install.
The wizard installs FMA. Then, the Technical user dialog box is displayed: 7. On the Technical user dialog box, provide information about the technical user you set up for the FMA service. For more information about this account, see Creating a technical user account on page 5. If you select LocalSystem account, FMA uses the local ID named system to run processes.
To specify a technical user, complete these steps: a. Select This account and type the name of the account. b. In the Password and Confirm password fields, type the account password. c. Click Next. The Grant Permissions dialog box is displayed: 8. Click Yes to confirm you want to grant permissions to the technical user. 9. Click Next on the Wizard Summary dialog. The completion dialog box is displayed. 10. Click Finish.
Installing FMA in a cluster configuration If you are installing FMA on a Microsoft cluster system, you must perform additional configuration steps. FMA supports clusters based on Windows Server 2003 and 2008. Consult Microsoft documentation for help in determining the best cluster configuration for the application.
4. On the Cluster Setup dialog box, select the account to use to run processes and click Next. In a cluster environment, a domain user is typically used to run the FMA Configuration process. If you do not want to create a new user for this process, you can select Localsystem account. 5. On the Cluster Setup dialog box, select Cluster Group and click Next. 6. On the next Cluster Setup dialog box, enter a resource name and brief description and click Next. 7.
3. Create a new Cluster Group for the resources to be allocated to the secondary Active node. a. Click Add New Resources. Add the new Physical Disk to the new Cluster Group you have created. b. Move the Cluster Group with all its resources to the appropriate active node by right clicking over the selected group and selecting Move Group. Note 4. 5. All drive letters or resource names in the cluster resources must be unique. Drive letters or resource names cannot be used more than once.
Evicting a node from a cluster To uninstall FMA from a node that has been evicted from a cluster, follow these steps: 1. Evict the node using Windows cluster administration tools. 2. Uninstall FMA from the evicted node. Follow the instructions (To uninstall FMA from a single file server on page 20) for uninstalling FMA from a single server. 3. Return to a node that is still a member of the cluster and run the FMA Cluster Setup wizard.
If you want to migrate a Windows 2003 cluster that includes FMA to a Windows 2008 cluster, see Migrating a Windows 2003 cluster on page 18. To upgrade FMA on a file server 1. Run setup.exe. This file is available on the installation CD. 2. In the confirmation dialog box, click Yes. 3. Follow the instructions in the installation wizard. To update a cluster WARNING Window 2003 clusters cannot be upgraded to Windows 2008 clusters directly with this method.
• Use the fmacli arc command to record the list of archives with their IDs. The IDs are listed in the first column of the output of the command. To migrate an FMA cluster to 2008 1. Uninstall FMA 2.2 on each node of the 2003 cluster. Refer to Uninstalling FMA on page 20 for more information. 2. Migrate the cluster configuration to the Microsoft Server 2008 cluster by following the recommended Microsoft process, http://technet.microsoft.com/en-us/library/cc754506.aspx.
Uninstalling FMA Use the following steps to uninstall FMA. To uninstall FMA from a single file server 1. In the Windows Start menu, select HP StorageWorks File Migration Agent→FMA Uninstall. 2. After starting the uninstallation process, you are asked if you want to keep the current FMA configuration or if you want to completely uninstall the FMA software. HP recommends selecting Yes to keep the current FMA configuration.
Licensing 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.
14. Start FMA by selecting Start → Programs → HP StorageWorks File Migration Agent→ FMA Configuration. 15. Bring up the HP File Archiving software Configuration Utility, and select License information to verify that your permanent license was entered successfully. FMA License Information – Stand-alone Permanent License If you have a Cluster license or OpenStorage license, you will see Permanent license in the Optional features box. Otherwise, Not available will be shown in the status.
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 by rightclicking My Network Places and selecting: Properties → Network Connections →Advanced → Advanced Settings → Adapters and Bindings Advanced Settings dialog Use the up and down arrow keys to move the connection of the registered IP address to top of the connections list.
24 | Licensing
Archives Archives store data that FMA has migrated or released from managed volumes. FMA supports the following types of archives: • Common Internet File System (CIFS), for Windows-based archives • File Transfer Protocol (FTP), for Linux-based archives • HP Integrated Archive Platform (IAP), for IAP archives When you create an archive, you configure an FMA remote storage adapter (RSA) so that the archive can communicate with FMA.
During the creation of a CIFS or FTP archive, you are given the option to remove some of these descriptors: • Ignore system Name • Ignore Volume Serial • Ignore Security • Data Stream Only Ignore Security and Data Stream Only The process of migration is copying data from the File Migration Agent managed volume onto the selected archive target. When the Ignore Security and Data Stream Only options are selected, the information of the file is not stored into the archive.
The Ignore system name option removes the file server system name when creating the archive storage path. Similarly, Ignoring volume serial removes the volume serial number of the managed volume on the serial path. Viewing archives You can view a list of archives and information about each archive. To view the list of archives 1. Launch the FMA user interface by selecting All Programs→HP StorageWorks File Migration Agent→FMA Configuration from the Windows Start menu. 2.
Adding archives to FMA in a cluster environment If FMA is installed in a cluster environment, you must move all cluster resources, including the default cluster group, to a single node. Then, complete the steps in the following sections to create archives. After you have created the archives, redistribute the cluster resources.
5. Add the technical user account that you established during installation. Give this user Full Control permissions. For more information about the technical user account, see Creating a technical user account on page 5. 6. Click the Security tab. 7. Add the same technical user account with Full Control permissions. 8. Click OK. Configuring CIFS archives After you set up the archive share, you can configure the archive. Note You can create an archive even if it is currently unavailable.
5. Click RSA Config. The RSA Configuration dialog box is displayed. 6. In the Archive storage path area, enter the following information: 7. 30 | Archives • Primary Archive—The fully qualified NAS path to the location to which data is migrated and from which it is recalled. The specified path must exist and be specified using Universal Naming Convention (UNC) notation. Using a mapped drive is not recommended due to the limited visibility of the mapped drive for the service.
• Ignore system name—Select this option if you do not want the storage descriptors for this archive to include the system name. This option is required for cluster systems. If you use this option, you must ensure that the storage descriptor is unique without the system name. • Ignore volume serial—Select this option if you do not want to the storage descriptors for this archive to include the serial number of the local managed file system.
Configuring VSFTPD on SuSE Linux Perform the following steps to enable an FMA-compatible FTP configuration with Very Secure FTP Daemon (VSFTPD) on SuSE Linux. To set up a new group and user 1. At the system prompt, enter the following to add a new user group with restricted rights to the system: groupadd fma 2.
5. At the system prompt, enter the following to trigger inetd to reread its configuration file: killall -HUP inetd 6. Enter the following to convert all files with the dos2unix utility. This prevents problems caused by transferring these configuration files from a DOS filesystem to a UNIX filesystem. dos2unix vsftpd.conf dos2unix vsftpd.userlist To prevent uncontrolled growth of the vsftpd.log file using LogRotate 1. Create the /etc/cron.
where path is the mount point of the archive. 4. Enter the following to change the password and activate the account: passwd fma_user 5. Enter a new password. 6. Enter the following to change the user and group assignment of the archive: chown -R fma_user:fma This enables the fma_user user to write to the archive. 7. Add the fma_user user to the /etc/vsftpd.user_list, which contains all users that are allowed to access the archive using FTP. 8. In the /etc/vsftpd/vsftpd.
chmod +x 3. /etc/cron.daily/logrotate Create the /etc/cron.daily/logrotate.d/ivd file and use a text editor to add the following lines: /etc/logrotate.d/ivd # Configuration for logrotate /var/log/vsftpd.log { compress size=500M rotate=5 } where • compress ensures that old versions of log files are compressed with gzip by default. • size=size ensures that log files are rotated as they grow larger than the specified size. This size can be specified in bytes, kilobytes (k) or megabytes (M).
• RSA Module—The module required for FMA to communicate with the archive. Select RSA-FTP, which is required for FTP archives. • Performance Index—The order in which FMA recalls from this archive. The range is 0-100, and the default is 100. If a file is stored on multiple archives, FMA attempts to recall it from the archive with the smallest index number first. • Description—A description of the archive.
7. • Port—The FTP port. The default port is 21. • User—The FTP user required to access the FTP server. • Password—The password used to access the FTP server. • Root path—The root path on the specified FTP server. • Connection timeout (ms)—The number of milliseconds after which the connection to the FTP server times out. The default value is 500 ms. • Data read timeout (ms)—The number of milliseconds after which reads on FTP data times out. The default value of 0 results in no timeout.
Description Creates a packed file based on an NTFS file. Its input is an NTFS file and its output is a file in the FMA storage format. All NTFS file information is included. Options Option Description -f Filelist Converts all files listed in (Filelist). -o Overwrites existing destination files. By default, no files are overwritten. -r Recurses into directories. -p Preserves timestamps. When unpacking a file, the original creation and modification timestamp is restored.
Examples FmaFileUtil pack File001.dat File001.dat.p Packs the File001.dat file into the File001.dat.p file. FmaFileUtil pack d:\Dir001 d:\tmp\Dir001.p Packs all files in the d:\Dir001 directory into the d:\tmp\Dir001.p directory. FmaFileUtil pack –r d:\Dir001 d:\tmp\Dir001.p Packs all files in the d:\Dir001 directory and its subdirectories into the d:\tmp\Dir001.p directory. FmaFileUtil unpack –p –oFile001.dat.p File001.dat Unpacks the File001.dat.p file into the File001.
FMA’s recipients options and the Recipients field entries determine which IAP repositories are granted access to the binary object. The access information is retrieved from the document’s Access Control List (ACL). Preparing IAP archives for FMA FMA uses the ILM Object Storage API interface to access IAP archives. Before you create an IAP archive, you must configure the IAP system. Enabling integration Applications integrating with HP IAP must have TCP/IP access to port 25 and port 80.
3. In the right pane, right-click and select New archive from the context menu. 4. In the Archive Properties dialog box, enter the following information: • Archive name—The name of the archive. You cannot include a space or semi-colon character in the name. This name identifies this archive for migration and recall operations. • RSA Module—The module required for FMA to communicate with the archive. Select RSA-IAP, which is required for IAP archives.
5. Click RSA Config. The Rsa Configuration dialog is displayed: 6. In the Rsa Configuration dialog box, enter the following in the Parameters area: • Primary IAP Host name—The hostname or IP address of the IAP system to which data is migrated and from which it is recalled • Secondary IAP Host name—The hostname or IP address of the IAP system from which data is recalled when the primary archive is not accessible You must replicate files to the secondary archive outside of FMA.
7. Click Save. 8. In the Archive Properties dialog box, click OK. Editing archive properties You can edit archive properties to change the archive name, performance index, or description. You cannot change the archive ID or RSA module. While you can change the RSA configuration, you should do so with caution to ensure continued access to archive. To edit archive properties 1.
Deleting archives You can delete an archive and remove all of its data. WARNING Prior to deleting an archive, be sure to recall any released files to prevent loss of access to data. To delete an archive 1. Launch the FMA user interface by selecting All Programs→HP StorageWorks File Migration Agent→FMA Configuration from the Windows Start menu. 2. In the left pane, select Archives. 3. In the right pane, right-click the archive and select Delete from the context menu. 4.
Managed Volumes When you designate a volume as managed by FMA, its data can be migrated and released to one or more archives. You can manage any locally attached NTFS volumes with the exception of network drives, system volumes, and Microsoft cluster quorum disks. You must designate managed volumes using the FMA user interface, but you can perform other operations related to the managed volume using the FMA command line interface (FMACLI).
In the right pane, the following information is displayed for each volume: • Volume—The name of the volume and an icon that represents its current status Icon Status Description Not managed Available but not managed by FMA Active Managed by FMA Stopped or Not Mounted Managed by FMA but was stopped by a user, or the volume is not mounted. In a cluster, the volume can be mounted on another node.
• HSM process ID—The process ID of the FMA volume manager process • File system type—The type of file system (FMA only supports NTFS volumes) • Capacity—The amount of space available on the volume • Free space—The amount of free space in gigabytes and as a percentage of total space • Used space—The amount of used space in gigabytes and as a percentage of total space In addition, you can view the following information for this volume: • Disk space policies For information about setting disk space
Releasing files using disk space policies You can set disk space policies, which are watermarks and retention periods that define when files are released from a managed volume. You can also set an exclusion list of files that are not released, even if they meet the criteria in these disk space policies. FMA monitors the disk space on each managed volume and releases files when the high watermark is reached.
Note 5. The disk space policy interval counter starts running when the server is started. If the server is rebooted, the counter restarts. Click Save. Setting retention periods Use the following steps to establish retention periods during which files are not released based on the high watermark. To set retention periods 1. In the left pane of the FMA user interface, select Managed Volumes. 2. In the right pane, double-click the volume on which you want to set retention periods.
Excluding files from release based on disk space Use the following steps to specify a list of files that FMA must not release, regardless of whether they meet the criteria in the disk space policies. Note Excluded files are also excluded from statistical summaries. To exclude files from release based on disk space 1. In the left pane of the FMA user interface, select Managed Volumes. 2. In the right pane, double-click the volume on which you want to exclude files from disk space policies.
Migrating and releasing files using file policies File policies define the conditions under which files are migrated to an archive or set of archives. You can define a file policy to migrate files in a managed volume based on any combination of file age, size, or name. Files are migrated to archives according to the order specified in the policy’s archive list. By default, a file policy applies to all files in the specified folder and its subfolders, but you can include or exclude specific files.
7. Click the Filtering tab. 8. To migrate based on the age of a file, perform the following steps: a. Select File Age. b. Select one of the following from the Timestamp list: c. 9. • Access—Files that have been accessed more than this number of days ago are migrated. • Modification—Files that have been modified more than this number of days ago are migrated. • Creation—Files that were created more than this number of days ago are migrated.
begin with “\”. You can use the asterisk (*) wildcard to specify none or any number of characters of any value or the question mark (?) wildcard to specify exactly one character of any value. Note The exclusion list takes precedence over inclusion list. If multiple criteria are specified, all of them must be met in order for a file to be excluded. 13. Click the Archives tab. 14. Use the following steps to set up to four archive locations where FMA migrates data.
Scheduling file policies You can schedule a time when FMA runs all file policies for a specific volume. Note If the server is offline when a policy is scheduled to start, the policy does not run again until the next scheduled time after the server is started. To schedule file policies 1. In the left pane of the FMA user interface, select Managed Volumes. 2. In the right pane, double-click the volume on which you want to schedule file policies. 3. In the Scheduling area, click Change. 4.
Editing file policies You can modify file policies and define the files that they affect, but you cannot change the volume that they affect. To edit a file policy 1. In the left pane of the FMA user interface, select Managed Volumes. 2. In the right pane, double-click the volume that contains the policy. 3. In the right pane, right-click the policy in the Migration Policies area and select Properties. For information about fields in the Policy dialog box, see Creating file policies on page 51.
Migrating and releasing files with the Explorer plugin The Explorer plugin enables you to manually migrate, release, or recall files or folders from a managed volume on the local system. To access these commands in Windows Explorer, right-click a file or folder in a managed volume. Note The 64-bit version of Explorer is not supported.
To view FMA file properties 1. In Windows Explorer, select one or more files or a folder 2. Right-click to display the context menu and select Properties. 3. Click the FMA tab. FMA displays the following information: • Status—The current status of the file • OFF(n)—Offline • MOD(n)—Modified • SAV(n)—Migrated • INA(n)—Inactive • DIS(n)—Disabled (n) indicates the number of valid copies.
Recalling files When users select a released file on the file server, FMA automatically recalls the file. Specifically, FMA must recall files when the “system” process reads the file contents. In addition, you can recall the file manually using the Explorer plugin. If a file is migrated to multiple archives and FMA releases the file, the file is recalled from the last location to which it was migrated. The last location contains the most recent version of the file contents.
Activating a file means that the FMA metadata is synchronized to the new system file ID. This step enables the link to the archive copy and is performed from the FMACLI. For more information about the FMACLI, see Command Line Interface Reference on page 81. FMACLI act -r f:\homedir 12. Delete the source folder. 13. Restart the File Migration Agent AFM service. Moving a large number of files Use this procedure if you are relocating a large number of files and only a short production downtime is available.
FMA from managing it (remove volume management) or you want to address an issue on the volume, as directed by Technical Support. To stop managing a volume 1. In the left pane of the FMA user interface, select Managed Volumes. 2. Right-click on the volume you want to stop managing and select Stop from the context menu. The status for this volume has changed to Stopped. Restarting volume management After you stop volume management, you can restart it to restore access to the files stored on the archive.
Best Practices Create a new HP StorageWorks File Migration Agent (FMA) archive FMA archive configuration for a Windows FTP 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. The GDS FTP-Server comes with its own user management facilities.
FMA RSA-FTP Configuration dialog For archiving data directly to c:\fsefs1, the root path of the FMA RSA-FTP configuration menu needs to be left blank. Verification of the GDS FTP-Server configuration can be done with any FTP client software. After the FTP server side has been tested successfully, the next step is to attach FMA as an FTP client to the new archive storage location. For this, the following actions are necessary: 1. Start FMA MMC Snap-In from Windows Start menu.
• User • Password • Root path • FTP server • Connection timeout in ms • Data read timeout in ms • Select various options 10. Click Save. The new FMA archive is shown in the FMA MMC Snap-In list. 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. Note For further information about managing FMA archives, see Archives on page 25. FMA archive configuration for an Linux FTP archive For archiving data to a Linux-based FSE Archive, the VSFTPD needs to be set up on the FSE Archive.
In this example, the complete path to the archive directory is /fma/hsmfs1/data1/fma. After the FTP server side has been tested successfully, the next step is to attach FMA as an FTP client to the new archive storage location. For this, the following actions are necessary: 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.
• FTP server • Connection timeout in ms • Data read timeout in ms • Select various options 10. Click Save. The new FMA archive is shown in the FMA MMC Snap-In list. 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.
Note that the primary and secondary archive configuration (FTP user ID, FTP server configuration and archive directory structure) must be identical. Note For further information about managing FMA archives, see Archives on page 25.
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 Creating a technical user account on page 5) or the corresponding group.
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 IAP FMA is using the ILM Object Storage API interface for accessing the HP Integrated Archive Platform (IAP) as a backend archive. Any documents with a size of up to 1.58 GB can be sent from an FMA managed volume to the IAP. Depending on FMA’s RSA-IAP configuration, a specific set of metadata about the document can be attached to the binary object.
replica site, when the primary IAP is not available. If the primary IAP site can not accept any incoming traffic, FMA does not redirect the data traffic to the replica site. FMA only supports one replica site, which is built by one-way (Active/Passive) IAP 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 are 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.
9. Policy processing can be scheduled to be run hourly, daily, weekly or monthly and at any point in time to suit your business needs. Examples: • Start policies every day at 10:00 p.m. • Start policies every Saturday at 01:00 a.m. (Select Every day on Day of month, if policies should run on certain days of week.) • Start policies on the 1st of every month. (Select Every week day, if policies should run on certain days of month.
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 are released when the high or critical watermark threshold is reached. The policy ensures that the monitored managed volume never causes a DISK FULL error.
In this example recalled files are kept online for a minimum of 7 days, although the files have not been modified for 60 days. This configuration guarantees a fast access to files for a certain time period since the files have been recalled. Files which should always be online, can be excluded. Determine FMA software version To display the current version of FMA software components: • Enter FMACLI sys in the command line.
• 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 is migrated into the myArchive archive: FMACLI migrate -r f:\testdir -a myArchive • To migrate a directory to more than one archive (max.
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 is recalled: FMACLI recall -r f:\testdir You can also migrate files using the FMA Explorer plug-in. Set a high-watermark for migration or releases • To set a high-watermark for migration or release: Use the FMACLI command-line utility.
Schedule FMA jobs • To schedule FMA jobs, use the Scheduled Task Wizard in the Windows Control Panel (Start → Control Panel → Planned/Scheduled Tasks) for scheduling the FMA job. • Or, you can use the following command-line tools for scheduling an FMA job. In this example, the FMA job starts every Sunday (Su) at 03:00 a.m. 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.
Relocating data to another FMA managed volume Copying data to another FMA managed volume needs to be run by the robocopy.exe command-line tool, which is available from Microsoft’s Resource Kit. To avoid recall operations during copying of the data, HP recommends creating a duplicate of the robocopy utility. Name the duplicate NoRecRobocopy.exe. Add the process name NoRecRobocopy to the list of modules for which FMA enables a physical view to the file system. Therefore, the following steps are necessary: 1.
(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 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.
Command Line Interface Reference The FMA command line interface (FMACLI) provides access to most FMA functions and can be used instead of the user interface to manage data. The FMACLI is implemented in the FMACLI.exe module. It writes informational output to stdout and errors to stderr. Keep this in mind when redirecting output for logging purposes. This section uses the following typographical conventions: • Bold is used for command names and arguments in text.
Command Description ver[ify] Displays the result of the verification process vers[ion] Displays FMA version and build information vol[ume] Displays information about available volumes CLI only X Most commands can be shortened on the first three letters (for example, mig instead of migrate). Only the version command needs four letters (vers) to define the short form. There is no short form for the find command. In addition, many command parameters have a short form.
activate Sets the file ID in the metadata to the current ID of the file.
Options Option Description --help -h Displays Online Help for the activate command. --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: • • --log-info-message -V Maximum size is 10MB. If the file grows larger then 10MB, the file is switched. Old log files are named logfile.nnn, where the lowest number contains the youngest file: logfile.log logfile.000 logfile.001 ...
Option Description --minimum-access-time nd|h|m|s -A nd|h|m|s Defines the 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). --minimum-write-time nd|h|m|s -W nd|h|m|s Defines the minimum time (n) since file was last modified for the specified operation. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). --exclude-system Excludes system files.
archive Lists the status of the FMA archives. Syntax FMACLI arc[hive] [--help | -h] [{--logfile | -L} logfile] [--log-info-messages | -V]] [--verbose | -v] Description The archive command displays list of all archives. Options Option Description --help -h Displays Online Help for the archive command. --logfile logfile -L logfile Specifies a log file. The log file must be specified with a fully qualified path.
Example FMACLI arc Lists the archives. Output of the archive command is as follows: Id—The unique, internal reference number for the archive, which is generated automatically and cannot be modified. Status—The status of the archive (currently not used). State—Whether the archive is online or offline. Archive type—Type of Remote Storage Adapter (RSA-FTP for Linux archives, RSA-CIFS for Windows archives, RSA_IAP for IAP archives). pI—The order in which FMA recalls files from this archive. The range is 0-100.
cleanup Reorganizes FMA archives after files are deleted on the file server. Synopsis FMACLI cle[anup] [--help | -h] [{--logfile | -L} logfile] [--log-info-messages | -V]] [--verbose | -v] [--expiration nd|h|m|s] Description Use the cleanup command after files have been deleted on the file server to remove copies from the archive and reorganize the archive. Options Option Description --help -h Displays Online Help for the cleanup command. --logfile logfile -L logfile Specifies a log file.
erase Deletes FMA metadata from a file.
Options Option Description --help -h Displays Online Help for the erase command. --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: • • --log-info-message -V Maximum size is 10MB. If the file grows larger then 10MB, the file is switched. Old log files are named logfile.nnn, where the lowest number contains the youngest file: logfile.log logfile.000 logfile.001 ...
Option Description --minimum-access-time nd|h|m|s -A nd|h|m|s Defines the 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). --minimum-write-time nd|h|m|s -W nd|h|m|s Defines the minimum time (n) since file was last modified for the specified operation. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). --exclude-system Excludes system files.
info Displays FMA metadata.
Option Description --log-info-message -V Writes informational and debug messages to the log file (and the console). This option must be specified in combination with the -logfile | -L option. By default, only errors are written to the log. file Specifies a file name. Wildcards like * or ? can be used. --filelist filelist -f filelist Specifies an input file list (default is stdin). Files in the file list are separated by CR/LF. File names can be relative or fully qualified.
Option Description --long -l Displays all available information (long output). In the short version (default), only one line per file is displayed. -F outlist Creates a file list (outlist) as output. To define an operation, specify either an explicit file name or a file list that contains file names. If neither is specified, the FMACLI tries to read the file list from stdin. Use UNICODE or UTF8 formats whenever possible.
• Name—The fully qualified file name. Example FMACLI info -r D:\*.* -l Displays all available information for the files in the D:\*.* folder, as follows: File info Output of the info command with the -l option is as follows: Field Output state FMA status attr File attributes size File size generations Number of versions stored in the archive File generation info Filter file info (Only the latest version of a file object is supported.
File location info Field Output ArchiveID Internal reference number for the archive ArchPoolID Not used (reserved for future use) dwNumRec Total number of recalls from this location storage_handle_descr Archive link descriptor 96 | Command Line Interface Reference
migrate Explicitly migrates a file to the specified archive.
Options Option Description --help -h Displays Online Help for the migrate command. --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: • • --log-info-message -V Maximum size is 10MB. If the file grows larger then 10MB, the file is switched. Old log files are named logfile.nnn, where the lowest number contains the youngest file: logfile.log logfile.000 logfile.001 ...
Option Description --minimum-access-time nd|h|m|s -A nd|h|m|s Defines the 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). --minimum-write-time nd|h|m|s -W nd|h|m|s Defines the minimum time (n) since file was last modified for the specified operation. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). --exclude-system Excludes system files.
Examples FMACLI migrate D:\Test\file.dat -a arc01 Migrates the file D:\Test\file.dat to the archive arc01. FMACLI migrate -f c:\temp\miglist.dat -a arc01 Migrates the filelist c:\temp\miglist.dat to the archive arc01. FMACLI migrate D:\Data -A 4d --archive arc01 Migrates the file D:Data to the archive arc01 if the file has not been accessed in the last four days. FMACLI migrate D:\Data --archives "arc01, arc02, arc03" Migrates the file D:Data to the archives arc01, arc02, and arc03.
policy Displays or runs file policies. Syntax FMACLI pol[icy] [--help | -h] [{--logfile | -L} logfile] [--log-info-messages | -V]] [--verbose | -v] [--name polname | --all | --run polname] Description This command displays or runs file policies. A policy defines the conditions under which files on a managed volume are migrated and released. For more information about policies, see Migrating and releasing files using file policies on page 51.
Example FMACLI POL --name Reports Displays information about the policy named Reports, with output as follows: 102 | Command Line Interface Reference
recall Explicitly recalls data for a released file.
Option Description --log-info-message -V Writes informational and debug messages to the log file (and the console). This option must be specified in combination with the --logfile | -L option. By default, only errors are written to the log. --verbose -v Display debug information on the console (std_out). file Specifies a file name. Wildcards like * or ? can be used. --filelist filelist -f filelist Specifies an input file list (default is stdin). Files in the file list are separated by CR/LF.
Option Description --exclude-read-only Excludes read-only files. Note: The read-only attribute does not affect the behavior of policies or the Explorer plug-in. FMA will migrate, release, and recall read-only files and preserve the attribute. --exclude-archive Excludes files with an active archive bit. --exclude-compressed Excludes files with an active compressed bit. --ignore-files ignorefile Excludes file ignorefile. Wildcards like * or ? can be used.
release Explicitly releases a migrated file, leaving a stub file on the file server.
Options Option Description --help -h Displays Online Help for the release command. --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: • • --log-info-message -V Maximum size is 10MB. If the file grows larger then 10MB, the file is switched. Old log files are named logfile.nnn, where the lowest number contains the youngest file: logfile.log logfile.000 logfile.001 ...
Option Description --minimum-access-time nd|h|m|s -A nd|h|m|s Defines the 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). --minimum-write-time nd|h|m|s -W nd|h|m|s Defines the minimum time (n) since file was last modified for the specified operation. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). --exclude-system Excludes system files.
crt The time period for migrated and changed files. All files remain on disk for the specified time period before they become a release candidate. rrt The time period for recalled and unchanged files. All recalled and unchanged files remain on disk for the specified time period before they become again a release candidate. To define an operation, specify either an explicit file name or a file list that contains file names. If neither is specified, the FMACLI tries to read the file list from stdin.
rsa Lists the status of the remote storage adapter. Syntax FMACLI rsa [--help | -h] [{--logfile | -L} logfile] [--log-info-messages | -V]] [--verbose | -v] Description The rsa command displays the remote storage adapter status. Options Option Description --help -h Displays Online Help for the rsa command. --logfile logfile -L logfile Specifies a log file. The log file must be specified with a fully qualified path.
Example FMACLI rsa Lists information about the remote storage adapters, as follows: Output of the rsa command is as follows: • #—Index number • Type—Reserved for future use • Capabs—Archive capabilities (reserved for future use) • Name—RSA name • RSA—Dynamic link library of the remote storage adapter • Descr.
system Displays system information. Syntax FMACLI sys[tem] [--help | -h] [{--logfile | -L} logfile] [--log-info-messages | -V]] [--verbose | -v] Description The system command displays system information such as version, license, and other FMA settings. Options Option Description --help -h Displays Online Help for the system command. --logfile logfile -L logfile Specifies a log file. The log file must be specified with a fully qualified path.
Version of HP File Migration Agent kernel 2. 5. 0. 17 System status = 0, installPath=[C:\Program Files\Hewlett-Packard\HP FMA] HSM API Version = 2.5.0-0017 "" License Information: ===================== + Serial number S+ Base Product License Evaluation license expiration in 59 days + OpenStorage Option Evaluation license, capacity (avail/used) 1000 GB / 0 GB. + Cluster Option Evaluation license.
verify Displays the result of the verification process.
Options Option Description --help -h Displays Online Help for the verify command. --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: • • --log-info-message -V Maximum size is 10MB. If the file grows larger then 10MB, the file is switched. Old log files are named logfile.nnn, where the lowest number contains the youngest file: logfile.log logfile.000 logfile.001 ...
Option Description --minimum-access-time nd|h|m|s -A nd|h|m|s Defines the 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). --minimum-write-time nd|h|m|s -W nd|h|m|s Defines the minimum time (n) since file was last modified for the specified operation. The value can be specified in seconds (s), minutes (m), hours (h), or days (d). --exclude-system Excludes system files.
version Displays version and build information about the installed FMA. Syntax 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 Option Description --help -h Displays Online Help for the version command. --logfile logfile -L logfile Specifies a log file. The log file must be specified with a fully qualified path.
Example FMACLI vers Displays FMA version information, as follows: HP Storage Works File Migration Agent Version HP 2.5.1.0 HP File Migration Agent command line interface Copyright (C) 2007-2009 Crossroads Systems, Inc.
volume Displays a list of available volumes. Syntax FMACLI vol[ume] [--help | -h] [{--logfile | -L} logfile] [--log-info-messages | -V]] [--verbose | -v] Description The volume command displays information about the available volumes. Options Option Description --help -h Displays Online Help for the volume command. --logfile logfile -L logfile Specifies a log file. The log file must be specified with a fully qualified path.
Example FMACLI vol Displays a list of volumes in the following format: Output of the volume command is as follows: • Id—The volume index number. • M—Designates which volumes are managed. • Volume Status—The management status of the volume • • Not managed • Stopped • Active • Not mounted • Error • Restricted • Cannot be managed • Need reboot HSM Status—The status of the volume • Active • Inactive • Unknown • Label—The volume label. • FS—The file system of this volume.
Result codes FMACLI returns 0 if successful. Positive result codes show warning conditions. In the case of a fatal error condition, negative values are returned. Return Value Description (0) No error occurred. (1) Watermark not reached. (2) Error occurred during operation. The command started successfully but some errors occurred. Example: Some of the files can not be processed. (-1) A generic error occurred. Check error messages (stderr) for more information.
122 | Command Line Interface Reference
Troubleshooting This section documents the log files generated by FMA and provides steps for troubleshooting FMA. For information about contacting Support, see Support on page viii. If you must contact Support, please have the following information ready when you report an FMA issue: • Operating system version of the file server • FMA version and license information Use the FMACLI system command (page 112) to retrieve this information.
• If an FMA command line operation failed, provide the log file or a screenshot of the stdout/stderr output. • If an FMA process has terminated abnormally, provide the Dr. Watson log file and the related user dump. Run drwtsn32 from a command window to find the Dr. Watson log file path and user dump location. Accessing FMA log files FMA has several log files that you can reference when troubleshooting issues. FMA log FMA writes all FMA-related messages in a log file named hsm.log.
Layout The layout of the log file is as follows: Limits The FMA log file is created with the following limits: • Maximum size is 10MB. If the file size reaches 10MB, the file is switched. • The current log file is hsm.log. Older log files are named hsm.nnn, where the lowest number contains the youngest file: hsm.000 hsm.001 ... hsm.099 • By default, up to 100 log files (hsm.000 - hsm.099) are stored. To change the number of FMA log files saved 1.
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, although this is not recommended. To set the logging level for messages written to the Windows event log 1. In the left pane of the FMA user interface, right-click File Migration Agent. 2. Click Properties. 3.
If files are not migrated • Verify the migration policy. • Verify that the migration policy is enabled. • Check for the correct policy path. • Check include and exclude filters. Remember that the exclusion list takes precedence over the inclusion list. • Verify that a schedule is defined on the managed volume. • Verify that the archive is available. Check the FMA log files for any RSA errors. If a “disk full” error is displayed for a managed volume • Decrease the high and critical watermark.
• Set the debug mode of the RSA-FTP module: a. Open the following registry entry: HKLM\Software\Hewlett-Packard\HP FMA\Archives\ArcID\RsaConfig b. Change the debug level from 0 to 5: 5 5 c. Restart all FMA services. d. Start DbgView to capture RSA debug information. If files cannot be migrated to the CIFS archive (RSA-error: 0x006000x) • Ensure that share permissions are configured correctly.
Troubleshooting common issues If a system fault (BSOD) occurs A system fault (blue screen) occurs when Windows detects a problem or error from which it cannot recover. The contents of the memory are dumped to a file for later analysis. (By default, this file is %SystemRoot%\memory.dmp.) When this screen is displayed, deeper investigation with WinDBG and debugged version of file system filter must be initiated by Technical Support.
Tracing Archive Files • Enter the following to retrieve the storage descriptors: fmacli info –l filename The following example shows the output from this command: Gather the following file location information: • • Archive ID • storage_handle_descr On the FMA user interface, look up the RSA configuration and determine the URI. • For CIFS, the URI is the primary archive + storage_handle_descr, for example: \\NAS\arc2\W2K3EE64BIT\9C162104\openbooks\uml_tutorial.
If recall performance is poor • Check if disk caching is enabled. • Check load and performance on the archive system. If the managed volume status remains not mounted • Trigger a remount request: • For a stand-alone system, enter: fsutil volume dismount drive • For a cluster system, take the volume offline and online again. • Check whether volume is accessible. • Check for orphaned HsmVolMgr processes.
4. Click OK. If the “<<< Auto-activate metadata file 0x0000000000000000 terminated, rc=00000020” (rc=0x0020 “Sharing Violation”)” error is displayed Auto Activation is the process that takes place when managed files (stub files) are restored from a backup. Each file must be activated by a dedicated thread in the system. This error indicates that the delay time for auto activation must be increased. To increase the delay time for auto activation 1.
If Office files cannot be opened when working offline using offline folder replication Update the Windows XP client system using the following: http://support.microsoft.com/kb/936071/en-us Troubleshooting cluster systems If a managed volume cannot be activated • Check whether the volume GUID is listed in the following registry key: HKLM\System\CurrentControlSet\Services\hsmfilter\Volumes The volume GUID can be determined by using the mountvol command.
netstat –a The port can be changed in the %windir%\system32\drivers\etc\services file in the hsmconfsrv port/tcp entry.
Third-party Product Compatibility List Anti-virus FMA’s interoperability with anti-virus scanners has been successfully tested for the following products. Symantec AntiVirus Product Name: AntiVirus / EndPoint Protection Manufacturer: Symantec Version: AntiVirus 10.1, EndPoint Protection 11.0 Supported FMA Versions: 2.5 Operating System: Windows 2003, Windows 2008, Windows Unified Data Storage Server Restrictions: The feature “scan files opened for backup” is not supported.
Restrictions: None Remark: For proper interoperability, HP recommends not selecting the option: Scan files that have been migrated to storage The option is located in the menu: • • • VirusScan On-Demand Scan Properties Advanced properties Miscellaneous Sophos Anti-Virus Product Name: Sophos Anti-Virus Manufacturer: Sophos Version: 6.5, 7.x Supported FMA Versions: 2.
Restrictions: None Remark: Because eTrust changes the access timestamp of a file, the release operation should be based on the modification timestamp and the last recall timestamp. TrendMicro OfficeScan Product Name: OfficeScan Manufacturer: TrendMicro Version: 7.0, 8.0 Supported FMA Versions: 2.
Supported FMA Versions: 2.5 Operating System: Windows 2003, Windows 2008, Windows Unified Data Storage Server 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: During backup restore, CA ArcServe does not overwrite a migrated file with a stub file. This appears in the CA activity log as “Skip file Migrated”.
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: When using the Veritas AOFO option, you must select the Microsoft VSS service. Networker Product Name: Networker Manufacturer: EMC Version: 7.2, 7.4 Supported FMA Versions: 2.
Operating System: Windows 2003, Windows 2008, Windows Unified Data Storage Server Restrictions: See the FMA Readme.txt file for the latest updates. To access the Readme.txt file, select All Programs→HP StorageWorks File Migration Agent→FMA Readme. Remark: Volume snapshots can be taken on FMA managed volumes; there is no negative interference between VSS and FMA. Taking volume shadow copies does not initiate recalls of already released files.
Restrictions: FMA does not support “file activation” for files, which have been restored to a new location. Restoring files is only supported to their original location. Remark: VSS can be used on a server, with volumes managed by FMA. Note: Volume snapshots can be taken on FMA managed volumes; there is no negative interference between VSS and FMA. Taking volume shadow copies does not initiate recalls of already released files.
Version: 8.0 Supported FMA Versions: 2.5 Operating System: Windows 2003, Windows 2008, Windows Unified Data Storage Server Restrictions: None Remark: None MS Defragmentation Product Name: Defragmentation Manufacturer: Microsoft Version: Windows 2003, Windows 2008, Windows Unified Data Storage Server Supported FMA Versions: 2.
HP Storage Mirroring Interoperability File Migration Agent 2.5 supports the following features of HP Storage Mirroring 5.1.1.
Failure monitoring and failover Failover is the process in which a target stands in for a failed source. As a result, user and application requests that are directed to the failed source are routed to the target. Storage Mirroring monitors the source status by tracking network requests and responses exchanged between the source and target. When a monitored source misses a user-defined number of requests, Storage Mirroring assumes that the server has failed.
Supported Configuration Configuration 1 This configuration utilizes the HP Storage Mirroring features, but does not utilize the failover features of HP Storage Mirroring: • Mirroring • Replication • Restoration The failover feature is not used because the Source server is part of a Microsoft cluster configuration. In this case, only the Source server has the File Migration Agent installed, but HP Storage Mirroring is required for both source and target.
Configuration 2 These are the types of failover that HP Storage Mirroring provides: • Partial Failover • Full Server Failover This configuration is most likely to be used if no clustering is available. The HP Storage Mirroring failover wizard allows failover for the following elements: • IP address • Server Name • Share(s) When choosing the partial failover, only the share(s) are failover to the target server. The term failover is different than what is used in a cluster.
Script creation It is necessary to create a script to reactivate the file stubs during restoration and failover/failback. To create a script open a text editor, such as Notepad, on your Windows server. The reactivation command is fmacli act –r . The drive letters are the managed volumes of your FMA server.
148 | Third-party Product Compatibility List
Error Codes and Messages This appendix contains information about FMA-related messages and their descriptions. FMA returns a WIN32 defined error code or an FMA defined information or error code. For a description of system error codes (Code No. 0 - 6118), see the Microsoft error list or contact Technical Support. Error Code Error Text Description Recommended Action 0x00010001 File is migrated. Informational: The file in question has been migrated.
Error Code Error Text Description Recommended Action 0x0001000A FMA operation on internal control file was ignored Warning: FMA operations on internal files are ignored when a user tries to manage a file that is in the HSM Volume Information directory. This directory is a hidden system folder located at the root level of the managed volume. Files in the HSM Volume Information directory cannot be managed. 0x0001000B Directory ignored.
Error Code Error Text Description Recommended Action 0x00010013 File has foreign reparse point attached. File cannot be released. Warning: Another application has attached a reparse point to the file; only one reparse point can be attached to a file. FMA attaches a reparse point when releasing a file that has been migrated. To avoid conflicts with other applications, FMA does not migrate files with unknown reparse points attached.
Error Code Error Text Description Recommended Action 0x00010017 Modification timestamp has been changed on offline file Error: During migration, processing an offline file has been encountered that has a modification date that is newer than the date of the file at the time that it was migrated. Identify the application that could change the modified date without causing a recall. Attempt a repair operation using fmacli verify -repair filename. See page 114.
Error Code Error Text Description Recommended Action 0x00010104 Recall failed, no valid archive found. Error: FMA was not able to identify the archive referenced by the file's metadata. This occurs when trying to recall a file and the archive cannot be found. Check archive definitions. The FMA properties tab of the file indicates the ID of the archive that holds the file. Verify that the named ID is still present.
Error Code Error Text Description Recommended Action 0x00010135 Unable to activate file, duplicate metadata Error: A file cannot be activated because another file already has a valid reference to the requested archive object. This error occurs if a stub file is restored to an alternate location and the original file still exists. This error can also occur if a file is deleted and it goes to the recycle bin.
Error Code Error Text Description Recommended Action 0x00010201 Stub file is not empty. Error: A stub file contained data.This occurs during recall or a deliberate verify operation and file is offline but contains data. The file may need to be restored from the disaster recovery archive. Investigate third party applications that might modify stub file contents. 0x00010203 Metadata incomplete. Warning: The file generation information of the metadata could not be read.
Error Code Error Text Description Recommended Action 0x00010302 Configuration is invalid. Error: The install path defined in the FMA registry did not resolve to FMA binary or logging directories. This occurs when FMA tries to obtain the installation directory. Check the FMA installation directory. Reinstallation can be necessary if the path is corrupt. 0x00010303 Volume serial not unique. Warning: Two or more disk volumes attached to the system have the same volume serial number.
Error Code Error Text Description Recommended Action 0x00010307 File list is invalid. Error: The specified list was not valid, such as if it was not initialized. This can occur when a list of files is submitted to the volume manager for processing. Typically, the list comes from a fmacli command or the AFM policy service. Retry the operation. If the problem persists, restart the FMA services. If this continues to be an issue, contact HP Support.
Error Code Error Text Description Recommended Action 0x00010316 The HSM subsystem is busy and rejected the request. Error: An internal communication channel was busy and the file operation was rejected. A file processing request from the AFM policy service, the FMA command line utility, or the Explorer plug-in was rejected. Wait and try again. If the error occurs often, contact HP Support. 0x00010317 Generic error connecting to hsm subsystem.
Error Code Error Text Description Recommended Action 0x00010433 Garbage Collection: end of current logfile reached Informational: No entries exist in the current garbage collection file. None. 0x00010434 An error occurred reading from garbage collection file Error: The garbage collection file could not be read. This occurs during cleanup or when files are deleted or replaced in a managed volume. Restart FMA services and contact HP Support if the problem persists.
Error Code Error Text Description Recommended Action 0x00010551 Configuration server: unknown function Error: The FMA configuration service received a request that does not match an available operation. This can occur if internal FMA modules in the install directory are replaced with incompatible modules from another release version. Check the FMA installation and perform a repair install if needed. If there is no reason for this to occur, contact HP Support.
Error Code Error Text Description Recommended Action 0x00020007 Archive pool is empty Warning: Activate archive error occurred. This occurs when system tries to activate the next archive in a sequence but the archive pool is empty. None. 0x00020008 Unable to write to registry Error: FMA could not write to the Windows registry. Examine the log to find the reason of an error. 0x0002000A Maximum number of archives reached.
Error Code Error Text Description Recommended Action 0x00030007 The volume manager process was started, but failed. Error: The volume manager process was started but then stopped immediately. This can occur during FMA startup or HsmSvc service startup. Restart FMA services or reboot the server. Set management status for needed volumes. The FMA installation can be corrupt. Try to reinstall FMA. Contact HP Support if the problem persists.
Error Code Error Text Description Recommended Action 0x0004000A Wrong number of bytes written Error: An Archive Storage System write request returned the wrong number of bytes written confirmation. This error is produced by the FmaFileUtil application if it tries to write data and the return confirmation does not match the request. Contact HP Support. 0x0004000B Data is corrupt Error: An Archive Storage System write or read request did not pass validation checks. The data may be corrupt.
Error Code Error Text Description Recommended Action 0x00050101 File ID does not match with metadata Error: The FMA metadata contains a copy of the file ID. If a file is restored from backup or copied into a managed volume, the system file ID may no longer match the ID in the metadata. This error occurs when a user tried to recall or migrate the file. The file must be activated in order to resynchronize the file ID. Files are normally autoactivated when restored by a support backup application.
Error Code Error Text Description Recommended Action 0x00050203 Verify: primary metadata not found Error: The system compares the primary and secondary copies of the metadata as part of the activate and verify commands. The content of the primary copy of the metadata can not be read. FMA keeps a secondary copy of the metadata in an Extended Attribute. The metadata must be erased from this file. See the fmacli erase command.
Error Code Error Text Description Recommended Action 0x00060003 Authentication at storage archive storage system failed. Check supported credentials Error: The system can connect to the remote archive system, but the designated user did not have sufficient credentials to read from or write to it. This can occur during most operations that require reading or writing to the remote archive. Check archive settings in the RSA configuration.
Error Code Error Text Description Recommended Action 0x00060102 Verification failed (file size) Error: During fmacli verify or activate commands, some portions of the operation are RSA specific. This error occurs if the managed file has a different size from the copy in the archive. If the managed file is currently a stub file, it must be repaired using the fmacli verify command.
Error Code Error Text Description Recommended Action 0x00060129 Archive is inactive due to invalid configuration. Error: During system startup, the archive configuration list is scanned and if an archive has an invalid name or IP address, it is marked as invalid. This error occurs when a file's metadata references one of these archives. Check the archive configuration. If the archive path looks correct, restart the system and check again. If the problem persists, contact HP Support.
Error Code Error Text Description Recommended Action 0x00070006 Ftp: error modifying date Error: Unable to read the date of the remote file. This occurs when the system tries to read the date of the file in the FTP archive. Check the configuration of the FTP archive. 0x00070007 Ftp: error size Error: Unable to read the size of the remote file. This occurs when the system tries to read the size of the file in the FTP archive. Check the configuration of the FTP archive.
Error Code Error Text Description Recommended Action 0x0007000F FTP: read failure Error: Preparation for or recall of a file from the FTP archive has failed. Retry the operation and check the stability of the FTP server and network connections between the FMA server and the archive. 0x00070010 Ftp: authentication failed Error: While establishing a connection with the FTP server, the server returned an authentication error response.
Error Code Error Text Description Recommended Action 0x000A0002 File not migrated because file size exceeds IAP limit of 1,579,024,383 bytes. Error: The HP IAP archive has a maximum file size limitation of 1,579,024,383 bytes. This occurs if the system tries to migrate a file that is larger than the maximum allowed size. Files larger than the limit cannot be managed using an IAP archive. 0x00090001 Not enough memory to allocate buffer.
Error Code Error Text Description Recommended Action 0x00090008 Error accessing registry Error: The FMA filter driver components can not access the system registry when a volume was added or removed from FMA management. Restart the system or try to remove and add the volume to FMA management again. If the problem persists, contact HP Support. 0x00090009 Error accessing attributes.
Error Code Error Text Description Recommended Action 0x0009000E Error writing data Error: During a recall, the FMA filter driver can not write the file contents to the local managed file system. Ensure the file system is not full and that no other application has the target file open. Retry the operation. If the problem persists, contact HP Support. 0x0009000F Error occurred while waiting for filter event.
174 | Error Codes and Messages
Index A accessing FMA Explorer plugin 3 accessing FMA user interface 3 activate command 83 activating managed files 83 Active/Active 15 Active/Passive 14 archive command 86 archives backing up 6 cleaning up 88 configuring CIFS 29 FTP 35 RISS 40 creating CIFS 28 FTP 31 RISS 39 deleting 44 editing 43 listing 86 overview 25 preparing CIFS 28 Linux-based FTP 31 RISS 40 removing deleted files 44 types 25 viewing 27 audience vii Auto Activate Delay 132 Auto Activate List Size 131 B backing up archives 6 managed
D deactivating managed files 83 deleting archives 44 file policies 55 FMA metadata 89 disabling file policies 55 disk space policies 48 excluding files 50 setting retention periods 49 watermarks 48 documentation library viii E editing archives 43 file policies 55 enabling file policies 55 erase command 89 excluding files from disk space policies 50 Explorer plugin accessing 3 migrating files 57 overview 3 recalling 58 registering 20 releasing files 57 F Failover 144 file policies about 51 deleting 55 disa
L R Last recall 56 licensing 21 logs FMA log 124 FMACLI log 125 Windows event log 126 low watermark 48 recall command 103 recalling overview 2 using recall command 103 using the Explorer plugin 58 Recalls 56 registering the Explorer plugin 20 release command 106 Release Notes viii releasing overview 2 using disk space policies 48 using file policies 51 using migrate command 97 using release command 106 using the Explorer plugin 57 using watermarks 48 removing deleted files from archives 44 volume managem
Subscriber’s choice, HP viii support viii syntax for FmaFileUtil 37 system command 112 T technical support viii technical user account creating 5 overview 5 typographical conventions viii U uninstalling FMA in cluster 20 on file servers 20 updating FMA in cluster 18 on file servers 18 V verify command 114 version command 117 viewing archives 27 FMA metadata 92 FMA version information 117 managed volume information 119 managed volumes 45 system information 112 volume command 119 VSFTPD, configuring on Red
