HP StorageWorks File Migration Agent 2.2.7 release notes

You must have administrative privileges to perform administrative tasks. These privileges are
granted only if you are either locally logged into the system as Administrator (recommended) or
using remote access software that supports logging in with the real Administrator account. When
using the Windows native Remote Desktop, ensure that “-console” is added to your shortcut after
mstsc.exe with a space, for example: “%SystemRoot%\system32\mstsc.exe –console”. If this is
not done, Remote Desktop tool will be unsuitable for these tasks, because it uses a different
Administrator account when logging in remotely.
After the software is successfully installed, configure File Migration Agent (FMA) resources, such
as migration policies and target archives.
Related Documentation
The following documents provide related information:
 HP StorageWorks File Migration Agent Administrator Guide
 Readme.txt file
You can find these documents from the manual page of the HP Business Support Center
website:
http://h18006.www1.hp.com/products/storage/software/fma/index.html
Select “Support for your product” and “Manuals” to download the documents.
Revision History from FMA 2.2.0
This section provides information about changes that were made between this patch and FMA
2.2.0. The FMA 2.2.7 patch contains several fixes to known issues in the FMA 2.2.0 release.
These issues are listed below in no particular order:
1. When recalling files in a cluster environment, a “blue screen” occurs when an attempt is
made to access a pageble address at an interrupt request level (IRQL) that is too high.
2. FMA triggers a system crash when a recall or release operation is performed on
compressed file objects or on a compress drive.
3. When recalling files on a compressed volume, a system crash occurs if “DISK FULL”
status is reached.
4. During FMA IAP archive configuration, if more than one recipient is entered into the
recipients list and FMA operation is executed afterwards, an application crash occurs.
5. When using the „fmacli info‟ command to display information about a file, a file with a
UNICODE name is not displayed correctly.
6. When a file is marked for release, the value “minimum number of copies in the archive” is
derived from the number of archives, which are defined in the file migration policy for that
file. If a file is not covered by any migration policy, the value is set to 2.
This value was constantly set to 2 and was not derived from an existing file migration
policy, in case the policy is defined on the root directory of an FMA managed volume.