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.