Getting Started

---

GETTING STARTED

Auto-Migrating Live Workloads to vCloud Air with ATAmotion from ATADATA Installation and Deployment Guide

Migrating server workloads has been challenging, until now. ATAmotion™ from ATADATA™ allows you to migrate machines from “any to any” with minimal server downtime, and without installing software agents. ATAmotion will migrate from any physical, virtual, or cloud source to all VMware targets, including ESX/ESXi hypervisors, vCloud Director Service Provider private clouds, and hybrid platform vCloud Air. This document provides an overview of the installation and deployment steps for ATAmotion.

ATAmotion Planning Recommendations: 

Operating systems and software o ATAmotion will migrate servers from the following operating systems:  Windows Server (2003, 2003 R2, 2008, 2008 R2, 2012, 2012 R2, x86/x64)  Linux (CentOS, Debian, RedHat, Suse, Ubuntu, Suse, x86/x64) o The ATAmotion GUI is accessed as a web application from anywhere that has visibility to the console. The console is a windows application which can be installed on any virtual, physical or cloud instance that has connectivity between source and target environments.  Windows Server 2008 R2 with Web Server (IIS) role installed  Microsoft SQL Server 2008 R2 and SQL Management Studio



Connectivity o Connectivity varies from environment to environment. Access between source and target environments, needs to be defined and established. A VPN tunnel is recommended between source and target environments. o ATAmotion requires specific ports to be opened as detailed in the User Guide and pre-requisite document provided on license purchase, or by contacting ATADATA Support. o Before deploying a VPN, we recommend a consultation with the ATDATA technical team.



Accounts o Although ATAmotion is an agentless deployment, authentication is required to access the source servers. Appropriate credentials are required for scripts to initiate and manage migrations. o VPN access, if required. Please contact ATADATA Support to verify.



Bandwidth o Ample bandwidth significantly impacts migration timelines. Although ATAmotion has no minimum bandwidth restrictions, more bandwidth results in faster data transfer. Using too much client bandwidth is not an issue as ATAmotion has the capability to throttle bandwidth usage during migration.

Getting Started | 1 P a g e

GETTING STARTED

Auto-Migrating Live Workloads to vCloud Air with ATAmotion from ATADATA Installation and Deployment Guide

ATAmotion Installation Download 1. Connect to ATADATA’s SFTP server using an FTP client. Credentials will be provided. 2. Once connected, locate the indicated folder and download the contents of the folder to the local hard drive of the selected console server. 3. License Keys will be either pre-installed in the console, and/or emailed separately at time of order. Console server setup 1. Select or provision a specified Windows 2008 R2 Server in the chosen environment. 2. Follow the ATADATA Users Guide to deploy the console and required SQL product. ATADATA Console Installation 1. Navigate to the ATADATA installer and launch the executable as Administrator. 2. Follow supplied steps in the ATADATA Users Guide for installation on the selected server. ATAmotion migration module deployment 1. Ensure appropriate connectivity is established between source and target (generally a VPN would be established.) 2. Check ATAmotion User Guide and verify appropriate ports are opened. 3. Import optional bulk wave plans from ATAvision module, and any bulk credentials (encrypted file.) 4. Follow steps in User Guide to deploy ATAmotion, select appropriate source servers, auto-provision target environment, and finally to initiate, schedule and monitor individual jobs, or waves. 5. Verify jobs are migrated in console and follow steps for synchronization and cutover.

Getting Started | 2 P a g e