How to reduce the size of the nas's internal databases.

Document ID : KB000010006
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

Sometimes the nas internal database files can increase in size due to an alarm floods. We can use the nas Reorganize Database feature to reclaim disk space.

Background:

The nas reorganize database command will run a vacuum against the internal databases. This will free up some of the size that is being used.

Note, this assumes that the database.db and transactionlog have empty pages to free. If however, you have tens of thousands of alarms you will not see much, if any, reduction in size.

 

You can reduce the number of rows in the transaction log by modifying a few settings in the nas GUI. This would be under the Setup -> Transaction Log Tab.

The settings with the most impact will be "Keep Transaction History" and "Keep transaction summary"

These refer to the NAS_TRANSACTION_LOG and NAS_TRANSACTION_SUMMARY tables that are internal to the transactionlog.db file.

They both affect the amount of time and information you are able to see in an alarms history from within Infrastructure Manager.

 

Instructions:
  1. Open the NAS configuration GUI in Infrastructure Manager
  2. Click the Status tab.
  3. Right Click the pane containing alarm messages inside the nas GUI.
  4. Select Advanced > Reorganize Database
  5. You will see this in the  nas log
    1. Feb 14 13:37:34:799 [3088] nas: =====[ DATABASE REORGANIZE requested by Administrator from 10.130.252.246/60657
    2. The alarm enrichment and nas probes will stop processing alarms for a bit of time while the database is being reorganized. They will restart once completed.
Additional Information:

Refer to TEC000004328 for more Information on Transaction Logging/Transaction Summary and compression

Nas Release Notes