The nas probe's local database.db and transactionlog.db are growing to gigabit sizes.
This can be caused by nas Auto Operators that use Action Type "assign" and Action Mode "On message arrival". This can cause a loop in which alarms replicate before nas has been able to acknowledge the previous alarm.
To resolve this, change these "assign" Auto Operators fromAction Mode from "On message arrival" to "On overdue age" with a time of 10s.
Was this information helpful?