Please note that we are experiencing high memory usage with nas probe version 9.39.
We downgraded to 9.38 and probe is behaving normally.
This has been identified as a defect.
A test fix is attached to this KB which should resolve the behavior.
If you are not comfortable running a test fix in production, we suggest downgrading to NAS 9.38 until the official release of NAS 9.40 which will contain this fix.
nas v9.38 is also attached to this KB Article if you prefer to use the previous GA version.
In some cases high memory usage may also be associated with the following error in the nas.log:
nas: COM Error [0x80040e2f] IDispatch error #3119 - [Microsoft OLE DB Driver for SQL Server] Violation of UNIQUE KEY constraint 'UQ__NAS_TRAN__475A76F6F35709E8'. Cannot insert duplicate key in object 'dbo.NAS_TRANSACTION_SUMMARY'. The duplicate key value is (CO34264159-83443).
This can be caused by having a secondary NAS (e.g. on the HA hub) with the NiS Bridge option enabled.
Only a single nas can write to the backend nas table at one time.
If a second nas NiS Bridge is enabled at the same time as the Primary nas is running, it will cause duplicate key errors in the nas log.
This should be deactivated on a secondary NAS and only enabled on the Primary hub.