Preparing to Rehome

Rehoming involves turning up new virtual machines (target installation) that will be used to import the database configuration of the previous installation (source installation). This requires, at a minimum, the deployment of the virtual machine, the configuration of its hostname, IP addresses, NTP time sources (highly recommended) and selection of its deployment profile.

For redundant environments, two new Skylight orchestrator virtual machines will be required and for hot standby environments, the need for three interfaces per machine on distinct subnets remains.

These procedures are written assuming the target installation will be hosted in a new environment with net new IP addresses. It is expected that new firewall implementations will be required to ensure the application can connect to the network and that end users can access the application interfaces.

The installation of these new virtual machines is beyond the scope of this document. These procedures are already captured in Virtual Machine Installation and should be used in preparation of your rehoming activity. The important point to consider while installing your Skylight orchestrator 20.05 virtual machines is the deployment profile. The software ships with three deployment profiles:

• 5K profile (default)
• 30K profile
• 60K profile.

The profiles reference the number of network elements the system can manage. Larger profiles have larger memory, CPU and disk requirements. The selection of the profile is dictated by the current number of network elements in your source installation. The following general rules apply:

• Single node source installations will work with the 5K profile.
• Clustered source installations will need the 30K profile.

Please consult with your Accedian sales engineer if you need guidance on the profile to choose for your virtual machines. The deployment profile can be changed (during a maintenance window) at any time, but when doing so, adequate memory, CPU and disk resources need to be assigned to the virtual machine. Once the virtual machines are in place, with IP addresses assigned, deployment profile selected and networking rules in place, the high-level process of rehoming entails the following tasks:

1. Taking a database backup of your source installation

2. Stopping the software on your source installation

3. Transferring the performance session data to your target installation

4. Importing the database backup into the target installation

5. Upgrading the database to the 20.05 schema

6. Running a network element rebalance procedure

7. Starting up the software on your target installation.

If the user rehomes from the system using Rsync method, the user needs to generate and import an SSH key for Rsync destination on the Target Installation (refer to Administrative Operations subcategory)