Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Initialize the SCS server containers and configurations with basic defaults.

    Code Block
    scsctl init wizard -a
    1. For Site_Name, use EXACTLY the same name as the old C7 SCS server, and as recorded at the beginning of this process.

    2. For Swarm Administrator Password, use EXACTLY the same password as the old C7 SCS server, and as recorded at the beginning of this process

    3. For the Swarm network IP, you can either specify the same Swarm IP as the existing C7 SCS server or specify a new IP.
      ** If using a new IP, this must still be in the same subnet and outside of the DHCP range, and you MUST make changes to the Swarm cluster detailed later in this guide.

    4. DO NOT perform the “scsctl repo components, add -f [storage bundle file name]” step, or the “scsctl diagnostics config scan_missing” step at this time. Proceed to restore the backup file.

  2. Restore the SCS backup.

    Code Block
    scsctl backup restore /root/mig2rl8/scs_backup_full.YYYYMMDD.tgz
  3. Initialize the DHCP server using the same parameters as the old C7 SCS instance and as recorded at the beginning of this process.

    Code Block
    languagebash
    scsctl init dhcp --dhcp-reserve-lower ${EXISTING_DHCP_LOWER} --dhcp-reserve-uppper ${EXISTING_DHCP_UPPER}
  4. If required, re-enable SELinux (i.e. reverting step 3). This may take some time to complete.

    Re-enable SELinux, by editing the /etc/selinux/config file, removing the line SELINUX=disabled, and un-commenting out the line SELINUX=enforcing or SELINUX=permissive. Save the file, then reboot the server.

    Code Block
    languagebash
    vi /etc/selinux/config
    ...
    SELINUX=enforcing
    ...
    
    reboot
  5. If the system was deployed with a minimal installation, please install the Swarm support tools.

    Code Block
    cd /root
    curl -O https://support.cloud.datacore.com/tools/updateBundle.sh
    bash updateBundle.sh fresh
    rm updateBundle.sh

    If the system was deployed with the OVA, the support tools should already be installed, but please update with the command below:

    Code Block
    cd /root/dist && ./updateBundle.sh

Migrate to the (New) RL8 SCS

...

Server

At this point, the C7 SCS instance is the live server. This section of the process will finalize the process by disconnecting the C7 instance and making the RL8 server the primary instance.

...

In a production environment, there will likely be multiple gateway instances that need to be migrated. Therefore, repeat this procedure for each gateway, then test each instance thoroughly before proceeding to the next gateway instance.

...