Post-installation
In the post-installation steps, you should fulfill the business requirements and perform your planned maintenance tasks as previously detailed in the Nodinite Planning Guide.
Monitor Disk Usage
The most severe incidents in our support are usually the result of systems running out of disk space. When you run out of disk space, Nodinite is no longer operational.
Make sure to monitor your disk usage. Nodinite has the following helpful Monitoring agents with disk usage-related monitoring:
Backup your SQL Server Databases
Make sure your IT organization, among many other things, performs a regular backup of your Nodinite installation.
It will help if you use the Nodinite Database Monitoring Agent to ensure that backups of the databases are regular. Regardless of who is responsible, if the backups fail, or are not created, in the end, if the IT department fails to back up your environment and data gets lost, it will be your problem!
Create a Full Database Backup - Microsoft documentation
You need to make sure you are performing timely backups according to your policy of the following Nodinite databases:
- Configuration Database
- Log Databases
Info
There can be more than one.
- Agent Databases
Info
There can be more than one.
Remove the backups of the databases (retention) according to your company policy. We recommend at least 4 days to manage a long weekend.
Boost SQL Server Performance
- Please review the following trace flags 1117, 1118 and 2371 (startup parameters) for SQL Server instances < 2016.
- Ensure there is at least one TEMPDB file with 128 MB in fixed size per CPU core (up to 8), and at least one that is allowed to grow beyond the fixed size limit.
- Bump the Database compatibility level to match the SQL Server version in use.
Nodinite ships with low numbers to support older versions of SQL Server.
- Compress the backup if possible.
- If you have SQL maintenance plans, please disable the Nodinite 'DatabaseMaintenance' system parameter if these are competing.
- Please tune the recovery interval according to your policy. We recommend the following settings:
- Standalone, 60.
- High availability (AOAG), 0 - (default).
Hardening your environment
IIS - Use HTTPS
It is possible to encrypt the communication between end-users and the Nodinite Web Client and other Nodinite Core Services using HTTPS. For details, please follow the instructions in the How to perform hardening on your Nodinite installation user guide.
SMB / NFS
If you have SMB file shares on untrusted networks, it is possible to apply SMB Encryption. For Windows Servers; This is detailed in the "SMB Security enhancements" user guide.
If you have NFS file shares, the way to encrypt traffic depends on the type of NFS Service. Please review the documentation for each such service.
SQL Server
You can encrypt the SQL Server database connections. Please review the "Enable encrypted connections to the Database Engine" user guide for the details.
Windows Server / IPSec
Some Nodinite customers may opt to use IPSec to encrypt ALL network communication. This is an advanced topic. For details, please review the following "What is IPSec?" user guide.
Stay up-to-date
We constantly develop new features and fine-tune the product with better performance; Make sure to stay up to date.
Tip
As technology and platforms advance, we also add security-related features to help keep you safe.