Migrating Cloud Providers with RStudio Teams

Follow

Problem

I'd like to move from my current cloud provider (such as AWS, GCP, or Azure), to a different cloud provider. I would also like to move my RStudio Teams suite across to the new cloud provider whilst ensuring that my RStudio products will work as expected.

 

Is it possible?

Yes, it is most certainly possible to move your RStudio Teams suits to a different cloud vendor.

 

Will there be downtime during the migration?

Yes, unfortunately, it isn't possible to perform a hot migration with the RStudio Teams suite.

 

Can I use a migration tool provided by the cloud vendors to perform the migration?

Yes, a large part of the migration can be performed by migration tools provided by cloud vendors. That being said, each vendor handles these tools differently & it is important to ensure that after all of your data is moved across, it is structured identically to your old environment. Your RStudio configuration files point to specific IP addresses & DNS names, so it is crucial to ensure that these are consistent across your new virtual network. It is important to ensure that the matching firewall rules are also retained.

 

Considerations

Workbench | Connect | Package Manager 

 

Licensing

Your RStudio Teams suite will have a license that will need to be moved to your new infrastructure. This license is based on a "fingerprint" of your VM, and this cannot be moved from one server to another. You will need to deactivate the licenses in your current infrastructure, then re-activate them on the new infrastructure once they have been migrated to the new vendor.

Note: If you delete the VMs before deactivating the license, you will need to use our manual deactivation tool which can be found here: http://apps.rstudio.com/deactivate-license/

 

 

Deactivating your online license

Workbench

sudo rstudio-server license-manager deactivate

 

Connect

sudo /opt/rstudio-connect/bin/license-manager deactivate

 

Package Manager

/opt/rstudio-pm/bin/license-manager deactivate

 

Deactivating your offline license:

Workbench

sudo rstudio-server license-manager deactivate-offline <product-key>

 

Connect

sudo /opt/rstudio-connect/bin/license-manager deactivate-offline <product-key>

 

Package Manager

/opt/rstudio-pm/bin/license-manager deactivate-offline

 

Deactivating your floating license:

Workbench

sudo rsp-license-server deactivate

 

Connect

sudo connect-license-server stop
sudo connect-license-server deactivate

 

Once you have deactivated your license, you can set up your new infrastructure & proceed to reactivate your licenses.

 

Activating your online license

Workbench

sudo rstudio-server license-manager activate <product-key>
sudo rstudio-server restart

Then, to check the status of the license, run this command:

sudo rstudio-server license-manager status

 

Connect

sudo /opt/rstudio-connect/bin/license-manager activate <product-key>
sudo systemctl restart rstudio-connect

Then, to check the status of the license, run this command:

sudo /opt/rstudio-connect/bin/license-manager status

 

Package Manager

sudo /opt/rstudio-pm/bin/license-manager activate <product-key>
sudo restart rstudio-pm

Then, to check the status of the license, run this command:

$ sudo /opt/rstudio-pm/bin/license-manager status

 

Activating your offline license:

Workbench

  1. Enter the output in the app located here.  This will deactivate the license on our end.
  2. On your server run the following:
    sudo rstudio-server license-manager activate-offline-request <product-key>
  3. Enter the output in the app located here.  The app will respond with some activation XML, which you can use in the next step.
  4. Paste that code into an activation file on your server, then run:
    sudo rstudio-server license-manager activate-offline <full/path/to/activation-file>
  5. Restart the server with this command:
    sudo rstudio-server restart

Then, to check the status of the license, run this command:

sudo rstudio-server license-manager status

 

Connect

  1. sudo /opt/rstudio-connect/bin/license-manager activate-offline-request <product-key>
  2. Enter the output of steps 1 and 2 on the app located here.  The app will respond with some activation XML, which you can use in the next step.
  3. Paste that code into an activation file on your server, then run:
    sudo /opt/rstudio-connect/bin/license-manager activate-offline </full/path/to/activation-file>
  4. sudo systemctl stop rstudio-connect
  5. sudo systemctl start rstudio-connect

Then, to check the status of the license, run this command:

sudo /opt/rstudio-connect/bin/license-manager status-offline

 

Package Manager

  1. sudo /opt/rstudio-pm/bin/license-manager activate-offline-request <product-key>
  2. Enter the output of steps 1 and 2 on the app located here.  The app will respond with some activation XML, which you can use in the next step.
  3. Paste that code into an activation file on your server, then run:
    sudo /opt/rstudio-pm/bin/license-manager activate-offline <activation-file>
  4. sudo stop rstudio-pm
  5. sudo start rstudio-pm

Then, to check the status of the license, run this command:

sudo /opt/rstudio-pm/bin/license-manager status-offline

 

Activating your floating license:

Workbench

sudo rsp-license-server activate <product-key>
sudo rsp-license-server start

Then, to check the floating license activation, run this command: 

sudo rsp-license-server activation-status

 

Connect

sudo connect-license-server activate <product-key>
sudo connect-license-server start

Then, to check the floating license activation, run this command: 

sudo connect-license-server activation-status

 

Network

Your RStudio Workbench/Connect/Package manager suite will have IP addresses and/or DNS names contained within each configuration file. These configuration files may also refer to proxies, databases, storage mediums, and/or authentication servers. All of these IP addresses will need to remain the same or be modified within these configuration files to work accordingly with the new virtual network. 

 

Database

When moving your database server across to a new cloud provider, it is important to ensure that your database IP addressing & authentication credentials remain the same for each database, as well as the host itself. If any of this information is updated, then you will need to update your RStudio Workbench/Connect/Package Manager/proxy configuration accordingly.

 

Proxy

When moving your proxy server across to a new cloud provider, it is crucial to ensure that your proxy configuration & routing algorithm will work within the new environment. More often than not, your proxy configuration will only need to be modified if any IP addresses were to change on the hosts that exist behind it. If there is any network information that changes, your proxy configuration will need to be modified also.

 

Authentication

Depending on the type of authentication mechanism that you use, you will need to ensure that any dependencies that exist on your Authentication server, or authentication provider, are met by your RStudio Workbench/Connect/Package Manager configuration files.

 

Support Ticket

If you still have issues after completing the above, you can always lodge a support ticket, where our group of friendly, and incredibly knowledgeable staff can assist with any issues that you may be having. You can submit a ticket here:

https://support.rstudio.com/hc/en-us/requests/new

Comments