RackWare RMM Migration Getting Started for Oracle Marketplace (BYOL)

August 2021

Storage Considerations

Data Transfer options

Passthrough:

Most Migration projects use the Passthrough method for data transfer. RMM does not store a copy of the used data from source hosts. The RMM acts as a passthrough proxy to sync the source workload data through itself and onto the target DR instances. No additional storage is necessary on the RMM.

Store and forward:

The store and forward method is typically used if you want to seed the target network with the data from the source servers but not ready to deploy actual resources that consume cpu and memory. All used data from source hosts is stored in block storage on the RMM. You will need to add and configure the additional necessary block storage to maintain this. If you wish to use store and forward method please contact [email protected] for guidance.

Cpu/Memory requirements

Every 3 Ocpu’s requires at least 16gb Ram

Example:

1-3 Ocpu/16gb Ram

4-7 Ocpu/32gb Ram

8-12 Ocpu/48gb Ram

The RMM server requires at least 1 Ocpu for every 2 parallel operations.

Each Ocpu = 2 virtual cpu’s

Each host sync operation consumes one virtual CPU thread.

Example:

If you require to sync 8 hosts in parallel this would require 4 Ocpu’s

GETTING STARTED

Deploy and configure the RMM into your compartment

1. Deploy RMM instance from the Marketplace listing.

a. Deploy RackWare RMM from Oracle Marketplace

b. For every 2 parallel sync operations the RMM instance will require 1 OCPU

i. Minimum deployment of 4 OCPU and 16gb ram is required.

2. Configure you OCI Security list for access to RMM appliance.

a. Open TCP ports 22, 443 ingress to the RMM

b. Open TCP port 445 ingress from RMM to target subnet

c. From instance view click on the link to the subnet

d. Click the link to the security list for your subnet

e. Add a stateful Ingress rule from the IP or network where you will access the RMM

i. Click on Edit all rules

ii. Add the ingress rules to your RMM from the host you will access it from

3. Configure RMM instance

a. Login through ssh to your RMM Instance

i. Connect with user opc and ssh key supplied when you deployed the instance.

b. Elevate opc user to root

i. All RMM operations must be executed as root.

ii. $sudo su -

c. Create the admin GUI user account

i. # useradd admin

ii. Set the password, use a strong password

iii. #passwd admin

d. Generate new ssh key

i. # ssh-keygen -t rsa

ii. accept defaults and leave passphrase empty

Enter file in which to save the key (/root/.ssh/id_rsa):

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in /root/.ssh/id_rsa.

Your public key has been saved in /root/.ssh/id_rsa.pub.

4. License your RackWare server.

a. If you wish to use the 2 free trial licenses that come with the deployment, follow next steps

i. # rwadm relicense

ii. send the pre-install license file that is generate to [email protected]

b. If you have or wish to purchase production licenses then contact your sales representative at [email protected] or if you have your purchase invoice send the license pre-install file generated in the steps below along with your purchase information to [email protected]

c. Generate license pre-install file

i. #rwadm relicense

WARNING: This command will generate a new preinstall file, but will also INVALIDATE the existing license on next RMM restart.

If you wish to continue using RMM till you get the new license, DO NOT STOP RMM after running this command.

Do you wish to continue? (Y/N)  [N]: Y

PreInstall file generated at /etc/rackware/rwlicense_preinstall_1234567890. Please email this file to [email protected] to get the license.

ii. DO NOT REBOOT until you install your license file

d. If you can't generate the license using the specified methods in this Marketplace documentation then please reach out to RackWare team to procure two free trial licenses at [email protected] with following details e.g Contact / Email ID, Company Name, OCI Tenancy Name, Region etc.

5. Login to the RackWare RMM GUI

a. Open a Chrome or Firefox browser.

i. https://<rmm_ip>

ii. Username: admin

iii. Password: <this password you created from step 2c

6. Prepare your Linux source hosts

a. TCP port 22 should be open in any firewalls between source and RMM

b. Login to your Source linux host through SSH

c. Create user "rackware" on Source linux hosts

i. # sudo useradd -m -s /bin/bash rackware

d. Login to RMM and copy sudoers file information

i. rmm> #sudo cat /opt/rackware/docs/sudo-config.txt

e. Edit sudoer file on source host

i. source> #sudo visudo

ii. copy sudo-config.txt from RMM to bottom of sudoers file on source hosts

f. Create .ssh directory and authorized_key file for rackware user on source host

i. $ sudo su - rackware

ii. $ mkdir -p /home/rackware/ .ssh

iii. $ touch /home/rackware/.ssh/authorized_keys

iv. $ chmod 700 ~/.ssh/

v. $ chmod 600 ~/.ssh/authorized_keys

g. Copy RMM SSH key to source host

i. FROM RMM

ii. rmm> # sudo cat ~/.ssh/id_rsa.pub

h. Paste ssh key into source host authorized_keys file

i. $ vi /home/rackware/.ssh/authorized_keys

ii. $ sudo restorecon /home/rackware/ -v

i. Test connectivity between your RMM and your linux source host

i. rmm> #sudo ssh rackware@<my_source_ip>

ii. You should connect without any password prompt.

7. Prepare your windows source hosts.

a. TCP port 22 should be open in any firewalls between source and RMM

i. Open TCP 22 on the windows host. Enter netsh command in elevated powershell command (run as administrator).

1. netsh.exe advfirewall firewall add rule name=rw-tcp22-in dir=in action=allow protocol=TCP localport=22

b. Download the Rackware SSH Client installer package to the source host.

i. https://<RMM_IP>/windows/RWSSHDService_x64.msi

c. Run the installer package with administrator level privileges

i. Accept the license agreement and click next

ii. Accept default installation folder and click next

iii. Copy and paste contents of your RMM’s public ssh key

1. RMM > # sudo cat ~/.ssh/id_rsa.pub

2. Copy the ssh key info

3. Leave Username SYSTEM and Password fields blank.

4. Then click next

5. Click Next again

a. Accept UAC

b. Click Close

d. Test connectivity between Rackware RMM and your windows source

i. From RMM

ii. # ssh SYSTEM@<windows_ip>

[root@rackware-rmm ~]# ssh [email protected]

The authenticity of host 'x.x.x.x (x.x.x.x)' can't be established.

RSA key fingerprint is 01:aa:02:bb:03:cc:04:dd:05:00:00:00:00:00:00:00.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added 'x.x.x.x' (RSA) to the list of known hosts.

[system@rw-win-source ~]

rackware$

8. Create your Wave file for Migration using passthrough (no source data stored on rmm)

a. Login to the RMM GUI using Firefox or Chrome browser

b. User: admin

c. Password: (password you set earlier)

d. Download the Wave template

e. Save the .csv to your local workstation for editing

f. Edit the Wave file in Excel or an editor that can support tab delimited text file.

i. Add in the data for the following columns

1. Origin Name: Name of your source host – freeform no spaces

2. Origin IP: Can be ip address or FQDN that can be resolved on RMM

3. Target Name: Name you want your target host in OCI

4. Origin Username:

a. Windows = SYSTEM

b. Linx = Rackware

i. You created this user from step 5

5. Clonename: Name of your image to be stored in the rmm datastore

a. Leave blank unless you intend to keep a copy of your source host data on the rmm for Disaster Recovery purposes

6. OS:

a. windows

b. linux

7. Shape: Specify an OCI shape

a. Example: VM.Standard2.1

8. ssh only

a. for windows = TRUE

b. for linux leave blank

9. operation: host sync

Example:

9. Upload Wave file to RMM

a. Login to the RMM GUI using Firefox or Chrome browser

i. User: admin

ii. Password: (password you set earlier after licensing RMM)

b. Click on the upload file icon and browse the local file system for your edited wave template.

c. The wave list will load and the detailed list of individual servers to be migrated will appear.

10. Gather your Oracle OCI account information.

a. Api url for your region, Examples:

i. https://iaas.us-ashburn-1.oraclecloud.com

ii. https://iaas.us-phoenix-1.oraclecloud.com

b. User ID

i. From your OCI console. Select Identity > Users

ii. Copy the OCID for your user and paste it to a text file for now

c. Private Key File Path

i. Generate an API signing keys

1. Login to your RMM and elevate yourself to root level as described in license instructions earlier

2. #mkdir ~/.oci

3. # cd ~/.oci

4. # openssl genrsa -out ~/.oci/oci_api_key.pem 2048

5. # chmod go-rwx ~/.oci/oci_api_key.pem

6. # openssl rsa -pubout -in ~/.oci/oci_api_key.pem -out ~/.oci/oci_api_key_public.pem

7. Show the key values and copy to clipboard

8. cat ~/.oci/oci_api_key_public.pem

9. reference: https://docs.cloud.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm

10. get path to your key and copy it to notepad

a. # cd ~/.oci

b. # pwd

/root/.oci

c. Your private key path is: /root/.oci/oci_api_key.pem

d. Generate your OCI fingerprint

i. From your OCI console click on your user account as show above

ii. Select the link “Add Public Key”

iii. Copy the contents of the pubic key that was generated in the previous steps into the Add Public key window

iv. Copy your fingerprint to notepad for input later

e. Tenant ID

i. Gather the tenancy id and save for input later

ii. Passphrase: if you created an rsa key with passphrase (not mandatory)

iii. Compartment Name – if other than the root compartment

11. Add your OCI account information to the RMM Cloud Configuration

a. Login to your Rackware RMM Console

b. Expand the “Configuration” Tab on the left, select “Cloud” and click on the Add button

c. Change Cloud Provider to OCI

i. Input the information into all the additional fields from the previous section

ii. Name can be any name you wish to give this configuration

iii. Click Add

12. Attach your OCI account configuration to your Wave

a. Expand the Replication Option, click on waves and click on the blue link to your wave

b. Click on the blue “Not configured” link

c. Select your environment – the cloud user you set up in the previous step.

d. Enter the additional parameters

i. Datacenter

ii. AV Domain example (Availability Domain):

1.Nref:US-ASHBURN-AD-1

iii. Subnet Name

iv. VCN Name

e. Click Apply Changes

13. Start your Migrations

a. Set the parallel count to the number of migrations to run concurrently.

b. Press the play button

c. Status will change to running and the hosts will start their migration from source datacenter into the specified OCI environment.

d. Login to your OCI console to watch the new hosts being deployed.