The following method describes how to migrate configuration settings from Runecast Analyzer 1.8.2.x to Runecast Analyzer 2.x
Settings that are being migrated:
- vCenter Connection
- Automatic schedule settings
- Alerting
- Licenses
- Log rotation settings
- User Profiles (Local and AD)
- Access tokens
- Filters
- Issue notes
What is not migrated:
- Enabled security profiles (PCI-DSS and DISA STIG)
- Manual answers (included in DISA STIG)
- Reconfiguration of ESXi hosts and/or VMs to send logs to Runecast Analyzer (in case new IP/DNS name is used for 2.x)
- Scan results
Prerequisities:
- Source Runecast Analyzer version 1.8.2.x
- Destination Runecast Analyzer version 2.0.0 to 2.5.2 *
- Both appliances are up and running
- The destination Runecast Analyzer is clean installation
- Connectivity on port 5432 between both appliances
* Important note: Runecast Analyzer 1.x is not supported from 15th of February 2019.
Procedure:
- Log in to Runecast Analyzer version 1.8.2.x
- Run the prepare_db_for_migration.sh script and make a note of the generated password:
sudo /opt/runecast/migrate/prepare_db_for_migration.sh - Log in to Runecast Analyzer version 2.x
- Run the migrate_from_rc18.sh script with the following parameters:
migrate_from_rc18.sh
Example:
sudo /opt/runecast/scripts/migrate/migrate_from_rc18.sh 10.1.3.7 12345678901 - Confirm the configuration were migrated to the Runecast Analyzer 2.x appliances
Note: rcuser password will be the same as it was on Runecast Analyzer 1.8.2.x - Once the data migration is confirmed, run the unprepare_db_for_migration.sh from Runecast Analyzer 1.8.2.x
sudo /opt/runecast/migrate/unprepare_db_for_migration.sh

Click to view larger image ↑

Click to view larger image ↑

Click to view larger image ↑

Click to view larger image ↑