Skip to main content
Version: 1.20.x.x RR

Migrating instances to standalone deployment


This migration guide does not apply to nevisLogRend instances managed by nevisAdmin3. Refer to the nevisAdmin3-Reference Guide chapter "Operation and Administration" to migrate nevisLogRend instances managed by nevisAdmin3.

Procedure Overview

  1. Create a new instance in standalone deployment mode.
  2. Copy the relevant configuration properties and templates from the old instance to the new instance.
  3. Test the new instance.
  4. Remove the old instance.

Detailed Migration Steps

  • Create a new nevisLogRend instance in standalone deployment mode. This instance must be bound to the same interface, using the same protocol schemes and key material as the one you would like to replace. Make sure the new instance runs on a separate unused port. Example command:

    nevislogrend inst create [newInstance] LOGREND_SERVER_URL=http://localhost:11111 DEPLOY_TYPE=standalone
  • Copy the templates used in the old instance to the new instance. Command:

    cp -r /var/opt/nevislogrend/[oldInstance]/data/* /var/opt/nevislogrend/[newInstance]/data/
  • Edit the configuration files log4j.xml and, in /var/opt/nevislogrend/[newInstance]/conf/ to reflect your previous configuration in /var/opt/nevislogrend/[oldInstance]/conf/

  • Standalone deployments do not require the file vmargs.conf to set Java options. (vmargs.conf is ignored by standalone deployments) In standalone deployments, Java options are supplied via env.conf in the following format: JAVA_OPTS="-Xmx512m -Xms512m -XX:+UseParallelGC"


    The LOGREND_DEPLOY_TYPE in env.conf must remain "standalone" for the new instance!


    Do not simply overwrite the new instance's configuration files with the configuration files of the old instance, as the new configuration files contain some mandatory settings which are not contained in the old ones. It is recommended going through the properties of the old configuration files one by one. Copy paste them to the configuration file of the new instance if desired.

  • After changing all configurations make sure that all files are owned bynvauser/nvbgroup. Example command:

    chown nvauser:nvbgroup -R /var/opt/nevislogrend/[newInstance]
  • Start the new instance with nevislogrend [newInstance] start and make sure it is running.

  • Configure nevisProxy to use the new instance, by changing the assigned port of the corresponding nevisLogRend connector to the port of the new nevisLogRend instance.

  • Test the functionality of your NEVIS setup thoroughly.

  • After successful testing, you may remove the old instance.