HP File Archiving Software manual Compatibility issues, Restrictions, First steps

•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.

•Window components “Services for Unix” and “User mapping” components is required for NFS sharing of the source volume(s)

•When files with the same name but different capitalization (such as temp1, Temp1, and TEMP1) are saved in the same directory, the Win32 subsystem recognizes only one of them. FMA and other Windows applications can only access one of these versions, and it is not possible to determine which version will be retrieved.

Compatibility issues

Before installation, please review Third-party Product Compatibility List on page 135. Software which is not on the list is not supported and needs to be removed from the FMA server before installation.

Restrictions

The following features are not part of this FMA version:

•No continuous migration and release.

•No event-driven migration and release.

•No built-in disaster recovery function. Regular backups of the managed file system are required. (See Third-party Product Compatibility List on page 135.)

•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 can not manage a cluster quorum disks.

•For restrictions on third-party applications see Third-party Product Compatibility List on page 135.

First steps

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

1.Install the backend archive (CIFS, IAP, or FTP).

2.Create a technical user for the File Migration Agent service. Collect information about the data storage (user ID, IP address, and so on).

3.Install FMA. For further information about the FMA installation, see Installing FMA on file servers on page 7, Installing FMA in a cluster configuration on page 14, and Upgrading FMA on page 17.

4.Configure at least one FMA archive using the FMA MMC Snap-In. For further information about the FMA archive management, see Archives on page 25.

5.Configure the managed volumes using the FMA MMC Snap-In. For further information about the FMA volume management, see Managed Volumes on page 45.

8 Installation