System Tools

System Tools contains powerful tools which modify the core system of a GWAVA server. These tools are not to be used on a regular basis, and should not be used unless instructed to do so by GWAVA support. Editing the database, removing objects and modifying Servers in the GWAVA network may render the GWAVA system inoperative. Only proceed with such operations if you fully understand the process and possible repercussions and on instructions by GWAVA support. The System Tools section will be added to as necessity requires, and new menu items will be self-documented within the system.

Network, server & DB Tools

Replication Manager

The replication manager is a tool to push settings found in the current GWAVA system to other servers in a GWAVA network. The connection between two GWAVA servers is created during server activation. Instead of setting up the GWAVA server as a ‘new server’, select the new server to become part of an existing GWAVA network. If chosen to do so, the manager will assist in replicating the existing configuration database and settings across multiple servers.

Database Editor

The database editor allows both the viewing and the editing of the GWAVA configuration database. This can be used in coordination with GWAVA support. Do not use the database editor without explicit instruction and aid from GWAVA support.

The editor prompts you to spawn a new window and then offers the option to open the selected table in either viewing only, (default setting), or in the editing mode, which allows changes to be committed to the database. The editor also includes a search function which passes queries to the database and allows the response to be limited to a desired level of results. Changes to the database in the editor are immediate. To exit the editor, simply close the window.

Server Maintenance

Standard core functions for GWAVA maintenance are listed here. Removing and renaming a GWAVA server from the GWAVA networks correctly severs or renames a connection between two GWAVA servers. Removing a connected server from a network should be done prior to uninstalling the GWAVA server in order to avoid connection issues with the remaining GWAVA server(s).

Due to updates and changes in the GWAVA interface, it may be necessary to rebuild the system Menu’s. Selecting this option causes the GWAVA system to discard the current menu tree and system in the GWAVA interface, and recreated them from the current system files. If a new item has been installed or downloaded to the GWAVA system during an update and a menu rebuild is appropriate, you will be notified on the default GWAVA home page, under the system status window. The notice will be a link which initiates a menu rebuild. Utilization of this option under the system tools should not be necessary under normal operation.

Database Migration

The Database Migration tool migrates the internal SQLite database to an external Postgres database. Migration is a relatively simple process which is automated by GWAVA, however, database migration may take some time, and may take quite a long time depending on the size of the internal database. During database migration GWAVA services and scanning will be unavailable.

All maintenance, installation, tuning, and administration of the Postgres system is the responsibility of the system administrator. GWAVA offers no technical support for third party programs.

The Database Migration itself has detailed instructions in place. Read all of them before proceeding with the database migration. The migration process consists of several steps and pre-requisites which must be completed before continuing. Once all steps are completed, the migration can continue.

Shutting down all peripheral programs to gwava, except the ‘gwavaman’ process will leave the administration interface functional and accessible for the migration process. It is critical that all peripheral GWAVA process be shut down before the migration is started.

The migration itself may take quite some time depending on the size of the SQLite database, and during this time GWAVA will not scan mail and messages will not be passed through the system.

Enter the connection information to a pre-created, blank, Postgres database, and select the ‘Start Migration’ button to begin the migration. Once the migration has been completed, the peripheral GWAVA processes need to be started to initiate the quarantine and statistics data migrations. Once those have completed, the entire GWAVA system needs to be restarted in order to complete the migration. Once restarted, GWAVA will be functioning from the Postgres database.

Diagnostics & repair

The diagnostics section of the GWAVA management interface is designed for troubleshooting use and works in conjunction with the base components of the system. These tools should not be played with or used without full understanding of the effects. Use of these tools without the guidance of support may cause serious issues with the GWAVA system and network.

Master Event Duplication Check

This page will check the system to make sure there are not duplicate entries in the database.

Version Stamp Repair

That page allows you to reset version for a server or the online update versions.

Object Resync

This page will sync up settings between servers.

Object Removal

This page will remove entries from the GWAVAMAN database.

Policy Consistency Check

This page will ensure that the Policy manager is correct.

Interface Server Link Check

This page will make sure that Interfaces are assigned to specific servers.