| General Operating Guidelines and Limitations |
|
|
Operating System / |
|
Affected Component | Description |
|
|
All | As a result of log rolling changes in StorNext 3.0, logs are now rolled every 6 |
| hours. For each log, 28 instances (7 days of logs) are retained. Log instances |
| are retained in the same directory as the original log. |
| All log files which are rolled are affected by this change, including TSM logs |
| (tac_00, bp_*.log, hist_01, etc.), MSM logs (tac_00, hist_01, etc.), and any other |
| components configured for rolling. The <component>/config/filelist file |
| contains roll_log entries that determine which files are rolled (where |
| <component> is /usr/adic/TSM, /usr/adic/MSM/, etc.). |
|
|
| The StorNext Library Space Used Report (accessible from the StorNext home |
| page by choosing Library Space from the Reports menu,) shows the amount |
| of nearline space used. |
| The nearline space amount does not include dead space, but does include the |
| following: |
| • All used space on all media in all libraries except vaults |
| • All space used by files that were put on a storage disk or |
| storage disk |
|
|
| The StorNext GUI does not support an isolated metadata network topology |
| with a system configured for HA failover. If the browser does not have |
| connectivity to the isolated metadata network, then it will fail to connect after |
| a failover event. If you have an isolated metadata network topology, make |
| sure the browser has connectivity to the isolated metadata network or correct |
| the network topology so the browser has connectivity to the isolated |
| metadata network. |
| For more information, contact Quantum Global Services. |
|
|
StorNext User’s Guide | 349 |
