Linux Debian Installation

NetVizura needs dedicated server

For security reason, make sure that your server or VM doesn't have anything installed on it before NetVizura installation. Other software of services running on the same server can impact installation.

NetVizura needs correct time

Before installing NetVizura make sure to set the time on your server correctly. Time change after the installation will invalidate the license!

NetVizura installation needs internet access

NetVizura requires working connection to the internet to install required dependent software. After installation is successful you can turn off internet access for NetVizura server.

Netvizura depends on OpenJDK 8, Tomcat 8.0.14 or higher and PostgreSQL 12 or higher. NetVizura relies on 3rd-party repositories for installation of these software packages.

The installation process has been tested on Debian 10 and Debian 11. It is important that Debian is 64-bit OS.

Installation Steps

To be able to install NetVizura, you will need a root privileges.

To install NetVizura follow these steps:

Step 1: Installation of 3rd-party repositories and prerequisite software

Download and execute Debian prerequisite installation script:

su
apt update -y ; apt-get -y install sudo wget
wget https://www.netvizura.com/files/products/general/downloads/netvizura-5.2-prerequisites-debian.sh --output-document=/tmp/netvizura-prerequisites-debian.sh
bash /tmp/netvizura-prerequisites-debian.sh

Step 2: NetVizura package installation

Download NetVizura DEB package from NetVizura website to NetVizura server's /tmp directory and execute the following command:

sudo dpkg -i /tmp/downloaded_file_name.deb

Step 4: Verify installation

Now you can go to NetVizura web interface http://<netvizura_server_ip>:8080/netvizura.

Default login credentials:

Username: admin
Password: admin01

For example, if your server IP is 1.1.1.1 then point your browser to http://1.1.1.1:8080/netvizura like in the screenshot below:

NetVizura - Login Page

Post Install Steps

After installation tweaking of configuration files is required in order to utilize the installed RAM to the fullest extent. The main consumers of RAM are operating system, PostgreSQL database and Tomcat. General rule for distributing memory is to split it in ratio 2:1 between PostgreSQL and Tomcat with 1 GB or more reserved for operating system. For instance:

Installed RAM	PostgreSQL	Tomcat	OS
4 GB	2 GB	1 GB	1 GB
16 GB	10 GB	5 GB	1 GB

Tweaking PostgreSQL

Tweaking PostgreSQL for best performance is a topic on which many books were written, but the following are some common sense suggestions. For the curious ones recommended reads (among countless others) are PostgreSQL Optimization Guide and PostgreSQL Tuning Guide.

In order to apply following tweaks edit file /etc/postgresql/PG_VERSION_NUMBER/main/postgresql.conf. You will need to restart the PostgreSQL service after done editing with command: systemctl restart postgresql. Almost all of the following parameters are commented with carron character (#). Be aware that if you comment out the parameter that has been changed, PostgreSQL will revert to the default value.

In the following example it is assumed that 4 GB of RAM is allocated for PostgreSQL.

Before changing any parameters in postgresql configuration read the provided comments in the table below for more information regarding specific parameter.

parameter	recommended value	comment
`max_connections`	30	NetVizura rarely uses more than 10 connections simultaneously, but it is good to have some reserve.
`shared_buffers`	1024MB	The recommended amount is `RAM/4.`
`effective_cache_size`	2048MB	The recommended amount is `RAM/2`, possibly even `RAM * 3/4.`
`checkpoint_completion_target`	0.7	This parameter can take values between 0 and 1. Default is set to 0.5, which means that the write phase of checkpoint process will take half of the checkpoint timeout time. Increasing this value will provide more time for checkpoint write phase to finish, thus decreasing IO usage.
`work_mem`	32-64MB	The formula used is `max_connections*work_mem <= RAM/4`, but using a bit more is still fine.
`maintenance_work_mem`	256MB	Speeds up DB self clean process. Usually 4*work_mem or something in that ballpark
`wal_buffers`	16MB	Increasing `wal_buffers` is helpful for write-heavy systems. Usually this is 16MB.
`min_wal_size`	1GB	If WAL files are under this size, files will be recycled for future checkpoints.
`max_wal_size`	2GB	Maximum size of WAL files, after that CHECKPOINT command is be issued and files are written to disk.
`effective_io_concurrency`	2	Number of simultaneous request that can be handled efficiently by disk subsystem.
`full_page_writes`	off	Turning this parameter off speeds up normal operation, but might lead to either unrecoverable data corruption, or silent data corruption, after power outage, OS or HDD failure. The risks are similar to turning off `fsync`, though smaller.
`fsync`	off	Don't wait for HDD to finish previous write operation. This brings the most benefit, but if there is power outage, OS or HDD failure in exact instant when PSQL issues write command to HDD, that data will be lost and the DB itself could be corrupted. On the other hand, DB can issue several magnitude more write commands in the same time period and consider all these done, thus improving write performance immensely.
`synchronous_commit`	off	Similarly to "fsync" but with less benefit.
Parallel system optimization (PSQL => 9.6)
`max_worker_processes`	2	Number of cores
`max_parallel_workers_per_gather`	1	Number of cores/2
`(PSQL > 9.6) max_paralllel_workers`	2	Number of cores

Tomcat Memory Allocation

During installation NetVizura automatically allocates memory for Tomcat process. The amount allocated to Tomcat process is calculated according to the formula:

(RAM_total - 1GB) / 3 but no less than 1GB.

For instance:

Total RAM	Tomcat
3 GB	1 GB
4 GB	1 GB
16 GB	5 GB

However, if you need to tweak Tomcat RAM allocation differently (the example for 2048MB):

Edit file /etc/default/tomcat8 (Debian 9) or /etc/default/tomcat9 (Debian 10)
Locate JAVA_OPTS environment variable that defines memory and uncomment it if it is commented. This line looks something like the following:
JAVA_OPTS="${JAVA_OPTS} -Xmx1024m -Xms1024m +UseConcMarkSweepGC"
Modify the -Xmx parameter to allocate additional memory to Tomcat. Additionally, set parameter -Xms to the same amount. This should look something like:
JAVA_OPTS="-Djava.awt.headless=true -Xmx2048M -Xms2048M -XX:+UseConcMarkSweepGC"

Save the file and restart Tomcat: systemctl restart tomcat8 (Debian 9) systemctl restart tomcat9 (Debian 10)

Elasticsearch Memory Optimization

By default, the memory limit for Elasticsearch should be set to 30% of RAM. If you need it to be set to any other value, edit the file: /etc/elasticsearch/jvm.options, and set values -Xms and Xmx to desired size. Then, restart the Elasticsearch and Tomcat services.

On this page:

Page tree