UIM - How to reduce nas transactionlog / Nas probe down / Nas transactionlog.db very large

book

Article ID: 143781

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

Over the weekend our NAS probe crashed, after reviewing the environment further we noticed the transactionlog.db file has grown to 40GB. 

Environment

UIM 9.0.2, 9.1.0 an 9.2.0

Resolution

Implementing the steps documented in the following KB Article will resolve this issue for a period of time, however depending on the values configured for alarm retention you may face this issue again.

Nas alarm counts are not in sync between UMP USM and the Infrastructure Manager alarm subconsole
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=57377  

Moving forward, to prevent any further reoccurrences: 

1. Modifiy the NAS Transaction Summary retention values within the nas probe under the NiS Bridge (NAS GUI -> Setup -> NiS Bridge). 

a). The default in my 9.2.0 environment are: 

- Compress transactions after: 7 days 
- Keep transaction history: 30 day 
- Keep transaction summary: 90 day 

* Compress transactions after - The events (of type suppression) for alarms stored in the transaction log will be deleted after the number of days specified.

* Keep transaction history - For how long (in days) the transaction history is stored.The transaction history stores all events for each of the alarms handled by the NAS in the database.

* Keep transaction summary - For how long (in days) the transaction summary is stored.

b). Lowering these values to the below might help, depending on the volume of alarms in this environment and what's required for historical data: 

- Compress transactions after: 7 days 
- Keep transaction history: 30 day 
- Keep transaction summary: 45 day 

c). If make the above changes to the Nis Bridge rentention settings you will need to follow Steps 1 to 4 in the below technical guide to recreate the NAS tables and db files: 

Article title: Nas alarm counts are not in sync between UMP USM and the Infrastructure Manager alarm subconsole - https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=57377