3. Target: Microsoft Azure Source: Microsoft Azure Target: Microsoft Azure Source: AWS Target: Microsoft Azure Virtual or Physical machine to Azure AWS VM to Azure Azure to Azure Azure services your migration scenario migration tools this session Source: On-premise

5. ‘I am unable to deliver the services my business requires’ ‘My infrastructure is extremely complex and difficult to manage’ ‘I don’t have the capital budget required to keep my infrastructure up-to- date’

6. Extend Your DatacenterAchieve True Hybrid CloudTransform Your Business Harness powerful cloud capabilities, turning IT into a differentiator A unified platform across your datacenter and the cloud, making it easy to truly achieve a hybrid solution Dynamically respond to the needs of your business with the elasticity of Azure and the convenience of a pay-as-you-go model

7. Availability on Demand Empower your business with cloud services from Microsoft Azure Availability on Demand Long-Term Retention Cloud Backup Recovery Analytics/Reporting Cloud Bursting Cloud Migration DevTest

9. Replicate Test Migrate

10. Orchestration and Replication Microsoft Azure Site Recovery Primary Site Hyper-V Orchestration and Replication Microsoft Azure Site Recovery Primary Site vCenter VMware NEW Orchestration and Replication Microsoft Azure Site Recovery Primary Site Physical, Azure, or AWS NEW Key features include: Automated VM protection and replication Remote health monitoring Near zero RPO No-impact migration testing Customizable recovery plans Minimal RTO – few minutes to hours Orchestrated migration when needed Replicate to – and recover in – Azure Heterogeneous physical and virtual support

11. Microsoft Azure Data Channel Microsoft Azure Site Recovery Process Server – Used for Caching, Compression & Encryption Config Server – Used for Centralized Management Master Target – Used as a repository & for retention Source: VMware VMs & Physical Machines Process Server Customer 1 Process Server Customer 2 Source: VMware VMs & Physical Machines Mobility Service – Captures all data writes from memory Microsoft Azure Customer 1 Customer 2 Target: Microsoft Azure

16. Data Channel Microsoft Azure Site Recovery Source: Hyper-V VMs Customer Data Center Microsoft Azure Recovery Services Agent - Replicates data to Azure

20. Internet users ■ 500,000,000+ ■ 100,000,000 – 499,999,999 ■ 50,000,000 – 99,999,999 ■ 25,000,000 – 49,999,999 ■ 5,000,000 – 24,999,999 ■ 100,000 – 4,999,999 ■ 50,000 – 999,999 ■ 0 – 49,999 *Operated by 21Vianet 1 million+ servers 100+ Datacenters in over 40 countries India Central TBD India South TBD India West TBD Brazil South Sao Paulo China North* Beijing China South* Shanghai Australia East New South Wales Australia SouthEast Victoria Japan West Osaka Japan East Saitama New Regions launched in 2014

21. Target: Microsoft Azure Source: Microsoft Azure

22. BlobTable Source: Microsoft Azure Target: Microsoft Azure BlobTable Secondary (geo-redundant) Primary Target & Source (optional): On premise Server File MyStorageAccount2 File MyStorageAccount

23. VM Source: Microsoft Azure Target: Microsoft Azure Target & Source (optional): On premise Server VNET BlobTable VM VNET BlobTable MyVM MyVM2 File

24. Supported migration services Affinity groups, Networks, Cloud services, Storage accounts, Virtual machines (VMs) Supported migration scenarios… From one subscription to another subscription in either the same region or different regions In the same subscription with the same region or different regions ADCMS produces a JSON-based template of your subscription configuration metadata which can be edited offline before import Limitations The solution creates all storage accounts of the source subscription but excludes the VM-independent blobs. You must copy these blobs manually, if required. Migration occurs offline so the source VMs must be powered off Web roles and Worker roles Cloud services are not migrated

26. Source: Microsoft Azure Target: Microsoft Azure VM VNET BlobTable Worker role(s)Web role(s) Planning phase (piloting) Enumerate endpoints (ie Search keywords within data) Establish maintenance window Practice copying data and measure performance and time Prepare (dev work) Rebuild application with modified endpoints and deploy in new region. Don’t forget to change Management URL endpoint as well to point to new region Migrate (App Offline) Old application stopped and taken offline. Copy data from to new destination using data migration tools (Blob,Table,DB) Switchover VIP swap, DNS CName update. Validate. Compare source data and copied data. Rollback if needed SQL DB(s)

27. Regions Azure is in 19 regions today with more on the way. India private preview program for 3 new regions expected to open this year Guidance Best Practice documentation for Azure to Azure migration including born-in-cloud native multi-tier applications SourceAvailability Supported Guest OS Types Hyper-V 2012 R2Available All Guest OS types supported by Azure Hyper-V 2008 R2 SP1 and 2012 Available in Preview Windows and Linux VMware vCenter Server 5.1/5.5, ESXi 5.1/5.5, Physical Machines, Azure VMs Available in Preview Windows and Linux Amazon Web Services (Windows AMIs) Available in Preview Windows Server 2008 R2 SP1+ Amazon Web Services (Linux AMIs)RoadmapTBD Tooling ASR preview (2015): more Sources and guest OS types. Consistent experience (Roadmap): On-premise to Azure migration has a lot of overlap with Azure to Azure. Consider one solution/approach for both which includes all workloads. Migration-as-a-Service (North Star): migration is just a service you just click a button in the UI without managing the migration service Remove pain points for migration in Azure (North Star): investigate Azure platform improvements such as renaming storage accounts so applications don’t need to change endpoints Source: AWS

30. NO PURCHASE NECESSARY. Open only to event attendees. Winners must be present to win. Game ends May 9 th, 2015. For Official Rules, see The Cloud and Enterprise Lounge or myignite.com/challenge