Reports > Logs

Type of Logs	Description
StorNext Logs	Logs about each configured file system
File Manager Logs	Logs that track storage errors, etc. of the Storage Manager
Library Manager Logs	Logs that track library events and status
Server System Logs	Logs that record system messages
Web Server Logs	Various logs related to the web server
Database Logs	Logs that track changes to the internal database
Replication/Deduplication Logs	Logs that track the progress and status of data replication or data deduplication operations.
HA Logs	Logs that track activity related to the nodes in your HA system, such as whether a node is currently active, whether synchronization has completed, and so on.
Shared Firmware Upgrade Logs	Logs that track firmware upgrade status of both nodes.
Local Firmware Upgrade Logs	Logs that track firmware upgrade status of the current primary node.
Quota Logs	Logs that track quota events and status, if this feature is enabled on a given file system.
NAS	Logs that track information about your Appliance Controller. For additional details, see Manage Support Logs and View System Logs.

StorNext Storage Manager generates administrative logs for events which are worthy of notification. Such events generate e-mail notifications, while the rest are only displayed in the GUI.

There are a few notifications which are throttled, such that every occurrence does not generate a notification in order to prevent flooding you with these events repeatedly.

The default time between notification of these events is 8 hours. You can adjust the value by setting the FS_ADMINLONG_MINTIME system parameter in one of the following configuration files:

/usr/adic/TSM/config/fs_sysparm

/usr/adic/TSM/config/fs_sysparm_override

The following events are subject to throttling:

• The inability of a host to determine where to run a distributed data mover.
• A file system not being configured for distributed data movers.
• The inability to allocate a storage disk I/O stream to use for a distributed data mover.
• Encountering a duplicate entry in the database when storing a file.
• Attempts to format a media which may already be formatted and actively used.
• fsaddrelation failure due to an inconsistency with policy attributes between replication/deduplication and fspolicy.

The process is the same regardless of the type of log you are viewing.

1. On the Reports menu, click Logs. The Reports > Logs page appears.

2. On the left side of the page, select the type of log you wish to view.

3. If desired, select a file system different from the default one shown beneath the log categories. The log you selected automatically appears. If the log does not appear, click Refresh. If the log spans more than one page, use the navigation controls at the bottom of the page as described in Reports Menu Overview.