Skip to main content

Transfer data to AVIX version 5.1.6


AVIX 5.1.6 includes an overhaul of how more centralized data such as the configuration (admin template) and the access control are handled. 

In previous versions, including 5.1.5, possible setups were:

Storage type Configuration Access control
AVIX file (.avx5)

As per user preference : 

  •  .avx5t file(s) and/ or
  • DB storage (enterprise)

Storage-centric: 

  • Local (inside .avx5 file) or
  • DB storage 
AVIX DB storage Same as above Same as above, but most likely another "DB storage"




Regardless if we are setting out to work with a pure file-based AVIX 5.1.6, or full-fledged server setup, there is a need to "export" or extract these various data sets from an AVIX 5.1.5 (or earlier) storage: 

  • the normal AVIX data
  • the access control data (be it "local" or existing in a separate DB storage)
  • the configuration data

Above exports will store the data in a JSON file format (along with possible binary data in a separate folder). Having done the 5.1.5 export(s), an import can be done using AVIX 5.1.6.

The following sections will describe the 5.1.5 exports and the 5.1.6 imports in turn, using some examples.

EXportExport from 5.1.5

We

will

Exporting define two tasks: one that will bring the server down, and one that will start the server again. Let's also leaveusing a bitfile of space in-between, say 10 minutes, to give the server a chance to shutdown gracefully. 

Preparations before DEFINING "stop" and "start" tasksstorage

    • OpenExport theAccess Windowscontrol Services Management Console by typing "services.msc" in the run box.

      1. image.png

      data
    • LocateExport thenormal AVIX Server service and open its properties.data
    • TakeExport noteconfiguration ofdata
      • the Service name for future use:

    1. image.png

  1. Open the Task Scheduler by typing Task in the Windows search box:

    1. image.png

  2. Create a dedicated folder named "AVIXTasks", where we will define our tasks:

    1. image.png



Exporting

Define "Stop" Task

  1. Select Createusing a Basicdb Task from the Actions list on the right:
    1. storage

      image.png

      Requires
      2. having
    a
    2. 5.1.5
  2. Nameserver, theand taskrunning Stopan AVIX Server:5.1.5
      application
    1. to

      image.png

  3. Click Nextconnect and select Weekly Trigger:

    1. image.png

  4. Pick time(s) when there will be little activity/usage. We select 01:00 AM, two days/week here:

    1. image.png

  5. Click Next and for the Action select Start a program:

    1. image.png

  6. For the Program/Script type NET and add the arguments  Stop "SolmeAviXServer" (i.e. the service name):

    1. image.png

  7. Before Finishing, select the Open the Properties dialog option:

    1. image.png

  8. In the General tab select Run whether user is logged in or not and Run with highest privileges:

    1. image.png

The task we have now defined will stop the AVIX Server service, twice weekly at a chosen time.


Define "start" Task

We will start AVIX Server 10 minutes later, to give the Windows Service some time to close all pending tasks before restarting.

  1. Select Create a Basic Task from the Actions list on the right.
  2. Name the task Start AVIX Server:

    1. image.png

  3. Set the Trigger to start Weekly at 10 minutes after the stop time set previously:

    1. image.png

  4. Click Next and for the Action select Start a program.
  5. For the Program/Script type NET and add the arguments  Start "SolmeAviXServer" (i.e. the service name):

    1. image.png

  6. Before Finishing, select the Open the Properties dialog option as before.
  7. In the General tab, select Run whether user is logged in or not and Run with highest privileges.


Summary

You have now created two scheduled tasks,open one will stop the AVIX Server service and the other will start it again 10 minutes later. The overview of the tasksDB look like this:storages.

image.png

  • Export Access control data
  • Export normal data
  • Export configuration data


      addendum 1

      It has been observed that scheduled tasks fail to execute, should the password be changed for the user account who is running them.  In the screenshots above, the user is "EXUWNP". 

      Instead, a better approach could be to run the task with the "Administrators" group or similar: 

      image.png

      This can be specified by: Clicking on "Change User or Group...", and then clicking on "Advanced". Then, click on "Find Now" in the Common Queries section, and select the appropriate group.

      addendum 2

      While the "Administrators" group approach is an improvement, there are still problems with it. Should the machine be re-started, it is likely that no user belonging to the "Administrators" group is logged on. Hence, the service will not execute after a restart. 

      Instead, make sure to run as "SYSTEM" instead:

      Click on "Change User or Group...", and then clicking on "Advanced". Then, click on "Find Now" in the Common Queries section. Locate SYSTEM, and click OK: 

      image.png

      Notice the "Run whether user is logged on or not" (it was reset to this value automatically when I saved my setup): 

      This should be the end result:

      image.png


      Back to top