Prerequisites for Adding Data Collectors

• 64-bit OS. See the APTARE StorageConsole 9.1 Certified Configurations Guide for supported operating systems.

• Reside in the same time zone as the subsystem from which data will be collected.

• For performance reasons, APTARE recommends that you do not install Data Collectors on the same server as the StorageConsole Portal. However, if you must have both on the same server, verify that the Portal and Data Collector software do not reside in the same directory.

• NetApp Systems: NetApp ONTAP version 7.3.3 or later.

• NetApp ONTAP I2P (inode to pathname) must be configured.

• NetApp User with API Privileges (see Creating a NetApp User with File Analytics API Privileges)

• When collecting from large NetApp Systems (greater than 1 PB):

When collecting CIFS shares that are located at a site that is not local to the Data Collector server, a separate Data Collector is recommended for the remote site. This mitigates access issues associated with WAN traversal.

To create a new user, with the required privileges, on a NetApp system, use the following command-line interface (CLI) steps. For the role command, do not include a space after the comma.

If api-* does not meet your security requirements, additional File Analytics privileges can be configured using the following steps:

filer> useradmin role add apifarole -a api-volume-list-info,api-nfs-exportfs-list-rules,api-cifs-share-list-iter-start,api-cifs-share-list-iter-next,api-cifs-share-list-iter-end,api-snapdiff-iter-start,api-snapdiff-iter-next,api-snapdiff-iter-end,login-http-admin

• The Data Collector must be running a Windows operating system that is at least Windows server 2003. This Data Collector can collect both Linux and Windows shares.

• The Windows LAN Manager authentication level, in the local security policy security options, must be modified to: Send LM & NTLM - use NTLMv2 session security if negotiated. This allows the Data Collector to invoke the net use command with the password supplied on the command line. Without this setting, later versions of Windows will terminate with a system error 86 (invalid password).

• Windows CIFS Shares collection requires the Windows Domain User ID. This User ID must have Administrative privileges.

• Linux CIFS Shares collection requires super-user root privileges. Access control commands, such as sudo, sesudo, and pbrun are also supported. If using any of the access control commands, verify that the User ID has sudo, sesudo, or pbrun privileges.

• Collection of owner data for Windows and CIFS is configurable via Advanced Parameters. Data collection completes faster when owner data is not collected. You can configure an Advanced Parameter (FA_RESOLVE_OWNERS=N) to disable owner collection. To access Advanced Parameters in the Portal, select Admin > Data Collector Configuration > Advanced Parameters.

• When collecting from large NetApp Systems (greater than 1 PB):

Note: File Analytics data collection is not designed to run with the Host Inventory Validate function, which only checks basic connectivity to hosts. Use the checkinstall utility to collect the data, as described in the Both Windows and Linux Servers section below.

• Windows servers: A Data Collector must be running on a Windows 2008 server. A Domain Administrator ID is required when collecting file-level data for File Analytics.

• Linux servers: Only Linux is supported (not HP-UX or AIX). Running collection with a sudo user on a Linux server requires the addition of a an access control command in the Host Inventory. Also, an advanced parameter must be created and set: FA_USE_SUDO to Y. See the APTARE StorageConsole User’s Guide for details on setting advanced parameters.

• An advanced parameter must be created and set: FA_HOST_VALIDATE to Y. See the APTARE StorageConsole User’s Guide for details on setting advanced parameters.

• Make sure that the probe is HostResourceChildThread and the task is File Analytics.