Migrating Enterprise Recon v1 to Enterprise Recon v2

Pre-requisites

 

Prior to performing the migration, Enterprise Recon v2 must be installed.
You must have the required Administrator access to Enterprise Recon v1 to perform the migration


Migration for ER1->ER2 requires two steps:

  1. Export from ER1 database to an intermediary export file
  2. Import from the intermediary export file into the ER2 database

Export from ER1 Database

ER v1 SQLITE Database

On Windows

Find the hub.db file

If you are using the default SQLITE based ER1 database, you will have a hub.db file located in:C:\Program Files (x86)\Ground Labs\Enterprise Recon\hub.db (or the location where Enterprise Recon is installed) 

Copy this file to the ER2 server, using the SCP command

    1. Log into the ER2 server console at the "er-master login: " prompt.  the login name will be "root" and the password will be the current Administrator password for the ER2 instance.
    2. Start the SSH service with the command "service sshd start"
    3. If on windows, use a utility such as WinSCP to copy the file to the ER2 master server.
    4. WinSCP Steps incomplete.

Export the hub.db file:

    1. Log into the ER2 server console at the "er-master login: " prompt.  the login name will be "root" and the password will be the current Administrator password for the ER2 instance
    2. Export the hub.db file using the command "er2-v1export hub.db"
    3. If the export file was successfully created by the er2-v1export utility, it should be called "erv1.exp". Verify that the erv1.exp file exists, by running the command "ls -l erv1.exp".

On Linux

Find the hub db file

If you are using the default SQLITE based ER1 database, you will have a hub.db file located in: /var/lib/erecon/hub.db (Linux)

Copy this file to the ER2 server, using the SCP command

    1. Log into the ER2 server console at the "er-master login: " prompt.  the login name will be "root" and the password will be the current Administrator password for the ER2 instance.
    2. Start the SSH service with the command "service sshd start"
    3. If running Linux, run the command "scp /var/lib/erecon/hub.db root@10.11.12.13:hub.db" (substitute 10.11.12.13 for your ER2 master server IP address)

Export the hub.db file:

    1. Log into the ER2 server console at the "er-master login: " prompt.  the login name will be "root" and the password will be the current Administrator password for the ER2 instance
    2. Export the hub.db file using the command "er2-v1export hub.db"
    3. If the export file was successfully created by the er2-v1export utility, it should be called "erv1.exp". Verify that the erv1.exp file exists, by running the command "ls -l erv1.exp".

ERv1 MySQL Database

On Windows

Find the hub.cfg file

If you are using the MySQL database backed ER1, you will need to extract the connection string from your hub.cfg file.

On windows, the hub.cfg file will be located: C:\Program Files (x86)\Ground Labs\Enterprise Recon\hub.cfg

Right-click on the filename and select "Edit".

    1. Verify that the <database_driver> field contains the value "mysql"
    2. Note the value contained in the <database_path> field.  This is the connection string.  It will be a colon separated set of fields of the form "username:password:schema:address"

Export the MySQL database:

    1. Log into the ER2 server console at the "er-master login: " prompt.  the login name will be "root" and the password will be the current Administrator password for the ER2 instance
    2. Export the MySQL database using the command "er2-v1export connectionstring mysql" and replace "connectionstring" with the connection string from the hub.cfg file(open the file), ie, "username:password:schema:address".  Note that if the MySQL address listed in the configuration was "localhost" or "127.0.0.1" then the MySQL database was running locally.  Be sure to change the address field appropriately in the er2-v1export command line and ensure that the ER2 server has permission to access the original MySQL server.
    3. If the export file was successfully created by the er2-v1export utility, it should be called "erv1.exp". Verify that the erv1.exp file exists, by running the command "ls -l erv1.exp".

On Linux

Find the hub.cfg file

On linux the file will be located in: /var/lib/erecon/hub.cfg

Right-click on the filename and select "Edit".

    1. Verify that the <database_driver> field contains the value "mysql"
    2. Note the value contained in the <database_path> field.  This is the connection string.  It will be a colon separated set of fields of the form "username:password:schema:address"

Export the MySQL database:

    1. Log into the ER2 server console at the "er-master login: " prompt.  the login name will be "root" and the password will be the current Administrator password for the ER2 instance
    2. Export the MySQL database using the command "er2-v1export connectionstring mysql" and replace "connectionstring" with the connection string from the hub.cfg file, ie, "username:password:schema:address".  Note that if the MySQL address listed in the configuration was "localhost" or "127.0.0.1" then the MySQL database was running locally.  Be sure to change the address field appropriately in the er2-v1export command line and ensure that the ER2 server has permission to access the original MySQL server.
    3. If the export file was successfully created by the er2-v1export utility, it should be called "erv1.exp". Verify that the erv1.exp file exists, by running the command "ls -l erv1.exp".

Import from export db file

If the export file was successfully created by the er2-v1export utility, it should be called "erv1.exp".

  1. If not already logged in, log into the ER2 server console at the "er-master login: " prompt.  the login name will be "root" and the password will be the current Administrator password for the ER2 instance
  2. Verify that the erv1.exp file exists, by running the command "ls -l erv1.exp"
  3. Import the file with the command "er2-v1migrate -file erv1.exp"
  4. Once the import is complete you can log into the web interface and verify that it was successful.
Note that it is possible to import and merge more than 1 db file.

Components that will be migrated

  1. Targets and Target groups
  2. Context data
  3. Users and Permissions 
  4. Statistics
  5. Reports - Summary reports, Target reports, Target detail reports 
  6. Exclusions

 

 

If you require any assistance, please send an email to support@groundlabs.com

Have more questions? Submit a request

0 Comments

Article is closed for comments.