Migration from Cloud A series to Cloud B series

Migration from Cloud A series to Cloud B series

Our B series Virtual Compute Nodes offer many advantages over A series Virtual Compute Nodes like one-click deployent, auto billing and hourly billing to name a few. To migrate from Cloud A series to Cloud B series please follow the process as mentioned below. [ht_message mstyle="danger" title="Important note" " show_icon="" id="" class="" style="" ]Please note that once you have migrated to Cloud B series, your IP address WILL be changed.[/ht_message]

Step 1: Signup into E2E Networks myaacount portal

Go to E2E Networks myaccount webpage and click on Sign Up and enter the required details. You can also use your Google+ account for signing up for myaccount portal. Once you complete the sign-up process,  you will be e-mailed credentials for accessing our CloudOne Portal. myac1If you have already created an account, then skip this step and start from step 2.

Step 2: Create a new instance

Now go to our CloudOne panel and log in using your credentials. Prior to creating/ launching any Virtual Compute Nodes, please add your SSH keys via the CloudOne portal. Only Virtual Compute Nodes created AFTER addition of SSH keys will have the SSH keys added to the root user of the Virtual Compute Nodes. If you do not have SSH keys or do not wish to use the additional security provided by SSH keys, please skip adding SSH keys. You will be e-mailed a username and password after creating virtual machine, which can be used to administer the Virtual Compute Node. Click on the icon just above your username (second from right on the top navigation) step2

Adding SSH Key

Click on “Add SSH Key”  option. step3Paste your public SSH key in the space provided and click the “Add SSH Key” button. Once you have done that, click on VMs button (third from right on the top navigation). step4

Virtual Compute Nodes Overview

You will be able to see an overview of all your Virtual Compute Nodes and their status (running/ deploying/ off/ error). Further details of each Virtual Compute Node can be viewed by clicking the Blue button. If you are logging in for the first time, it will show all totals as zero, since no Virtual Machines have been deployed by you as yet. To create a Virtual Compute Node, please click the Green “+” button. This will open the Create Virtual Machine page. step5

Selecting a Template

On the Create Virtual Machine page you must first enter a name for the Virtual Compute Node you are creating. In the below example we have used the name “virtualserver”, you can give any name you like. Once you have entered a name for your VM, you need to review from amongst the available “templates” and select a “template” based on your requirement. Once you click on the chosen template, you will be able to review the “capacity” (allocated compute resources) once again, prior to creating the Virtual Compute Node. In case you wish to change your selection at this time, please click on the “pencil” icon located to the right of the plan name. If you are ready to proceed please click the “Create” button.

Virtual Compute Nodes Details and Console

On clicking the create button, you will be taken to the VMs page, where you can see the status of all your Virtual Compute Nodes. The freshly created Virtual Compute Node will show it’s status as “Deploying”. Deployment usually takes only a few minutes. You can click the “refresh” button after a few minutes to confirm the current status of the newly created Virtual Compute Node.

12Step 3: Share login credentials with E2E Networks' team

Now that you have deployed a new Cloud B series Virtual Compute Node, you need to migrate the data from Cloud A series to Cloud B series (which you recently created). If required, E2E Networks can migrate your data. For the applicable managed migration fee, please contact sales@e2enetworks.com. For doing so we shall require root login credentials of your Cloud A series as well as Cloud B series Virtual Compute Nodes. Please e-mail your root login credentials to cloud-platform@e2enetworks.com to perform migration. Once we complete the migration process we will inform you about the same over an e-mail and would seek permission from you to deprovision your Cloud A series Virtual Compute Node. Upon confirmation, we shall deprovision it and you shall receive an e-mail on its deprovisioning.
    • Related Articles

    • Server Migration/Plan Upgrade

      Server Migration/Plan Upgrade, the idea is to transfer all the data from existing server to the new server. There are 2 scenarios in the Server migration/Plan Upgrade process, A. Server migration/Plan Upgrade with IP change. B. Server migration/Plan ...
    • An Essential Guide to understand the appropriate cloud solution

      E2E Networks understand that every business is unique on its own and cater to the custom requirements which cannot be met by a common model.This guide is made with a purpose to outline the aspects and to make you understand and clear your doubts so ...