RackWare RMM Getting Started for Oracle Marketplace

May 2020

Pre-Requisites

There are 2 storage methods available for Disaster Recovery. You must choose one option

• Store and forward – requires block storage on RMM as described below

• Passthrough – no additional block storage required

Store and Forward

Store and Forward will create an image of your source workload in storage on the RMM’s database. When using this method, the RMM will need a datastore capable of containing the amount of used data from each source hosts minus typical compression savings.

Store and Forward is required if using the autoprovision feature whereby the RMM will only provision the compute resources during a DR event or test/drill event or to offer the multi stage protection of having data protected by a stored image and then sync’d from stored image to target compute resources.

Note: In order to take advantage of point in time snapshots for backup functionality you must choose the store and forward method.

Passthrough

Passthrough – 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.

You decide which method suites your deployment needs.

Store and Forward Example:

• Source Host01 100GB used data across all disks

• Source Host02 200GB used data across all disks

• Source Host03 50GB used data across all disk

Total used data = 350GB

Typical compression ratio for storage is 1.5x – 2x. 

In this scenario it would be advised to create a datastore on the RMM of the size 350 / 1.5 = 234GB

This would be considered a starting point. You can add additional storage to the storage pool at any time.

1. Deploy RMM instance and attach block volume for data storage

   1. Deploy Rackware RMM from Oracle Marketplace

   2. If you choose Store and Forward continue otherwise skip to step 2

      1. Create block storage disk for RMM data storage from the Calculations above

c. Attach block storage disk to RMM instance as paravirtual

1. Navigate to your compute instance

2. Scroll down to Resources > Attached Block Volumes

3. Click on Attached Block Volumes

4. Click on the Attach Block Volume blue box
   

5. Choose Paravirtualized and select an available path

Login and reboot the RMM instance

2. Configure RMM instance

1. Login through ssh to your RMM Instance

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

2. Verify path of your attached block storage data disk (skip this step if using passthrough)

   1. # sudo fdisk -l

C. Run the RMM configuration script and enter configuration options

i. # sudo rwadm init

1. Modify iptables rules for RMM operations (Y/N) [Y]: Y

2. Download ISO for linux vcenter autoprovision (Y/N) [N]: N

3. Do you want to continue with enabling the hub-role for the RMM (Y/N) [N]: N

4. Do you want to add extra disk to RMM storage pool? (Y/N) [N]: see note below

   1. Select Y for store and forward

   2. Select N for passthrough and continue to step 8 below

5. [A]dd disk or [F]inished [A]: A

6. Enter device name/path to be configured as RMM Storage pool. [ONE AT A TIME]: /dev/sdb

7. [A]dd disk or [F]inished [A]: F

8. [A]dd, [R]emove interfaces for rmm to listen on, or [F]inished [F]: A

9. Enter interface name, or 'all' [all]: all

10. [A]dd, [R]emove interfaces for rmm to listen on, or [F]inished [F]: F

11. This can be skipped in case of PS License type [N]: N

12. [A]dd, [R]emove NAT IP, or [F]inished [F]: F

13. Initialization Done.

1. Set your admin password for GUI access

   1. # sudo passwd admin

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

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

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

   3. 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

1. Click on Edit all rules

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

4. Login to the RackWare RMM GUI
a. Open a Chrome or firefox browser

1. https://<rmm_ip>

2. Username: admin

3. Password: <this password you created from step 2d>

5. Prepare your Linux source hosts

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

2. Login to your Source linux host through SSH

3. Create user "rackware" on Source linux hosts

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

4. Login to RMM and copy sudoers file information

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

5. Edit sudoer file on source host

   1. source> #sudo visudo

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

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

   1. $ sudo su - rackware

   2. $ mkdir -p /home/rackware/ .ssh
      $ touch /home/rackware/.ssh/authorized_keys

   3. $ chmod 700 ~/.ssh/

   4. $ chmod 600 ~/.ssh/authorized_keys

   1. Copy RMM SSH key to source host

      1. FROM RMM

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

   2. Paste ssh key into source host authorized_keys file

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

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

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

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

      2. You should connect without any password prompt.

7. 
   

   1. Prepare your windows source hosts

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

         1. 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.

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

c. Run the installer package with administrator level privileges
i.

ii. Accept the license agreement and click next

iii. Accept default installation folder and click next

iv. 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.

b. Accept UAC
c.

d. Click Close
e.

d. Test connectivity between Rackware RMM and your windows source

1. From RMM

2. # 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$

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

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

   2. User: admin

   3. Password: (password you set earlier)

d. Download the Wave template

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

g. 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:

   1. Windows = SYSTEM

   2. Linx = Rackware

      1. You created this user from step 5

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

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

6. OS:

   1. windows

   2. linux

7. Shape: Specify an OCI shape

   1. Example: VM.Standard2.1

8. ssh only

   1. for windows = TRUE

   2. for linux leave blank

9. operation: host sync
   
   Example

8. Upload Wave file to RMM

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

   1. User: admin

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

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

d.

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

9. Gather your Oracle OCI account information.

1. Api url for your region, Examples:

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

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

2. User ID

   1. From your OCI console. Select Identity > Users
      2.

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

c. Private Key File Path

1. 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

       1. # cd ~/.oci

       2. # pwd

/root/.oci

1. Your private key path is: /root/.oci/oci_api_key.pem
   d. Generate your OCI fingerprint

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

   2. Select the link “Add Public Key”
      3.

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

6. Copy your fingerprint to notepad for input later
7.

e. Tenant ID

1. Gather the tenancy id and save for input later
   2.

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

4. Compartment Name – if other than the root compartment
5.

6.

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

1. Login to your Rackware RMM Console

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

4. Change Cloud Provider to OCI
i.

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

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

iv.

v. Click Add
vi.

11. Attach your OCI account configuration to your Wave

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

3. Click on the blue “Not configured” link
4.

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

1. Enter the additional parameters

   1. Datacenter

   2. AV Domain example (Availability Domain):

      1. Nref:US-ASHBURN-AD-1

   3. Subnet Name

   4. VCN Name
      g.

h.Click Apply Changes
i.

12. Start your Migrations

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

2. Press the play button
   c.

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

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

RackWare Inc • Proprietary and Confidential