Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

Extending On-Premise Infrastructure To Cloud

Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Cargando en…3
×

Eche un vistazo a continuación

1 de 36 Anuncio
Anuncio

Más Contenido Relacionado

Presentaciones para usted (20)

A los espectadores también les gustó (20)

Anuncio

Similares a Extending On-Premise Infrastructure To Cloud (20)

Más de Lai Yoong Seng (20)

Anuncio

Más reciente (20)

Extending On-Premise Infrastructure To Cloud

  1. 1. http://www.ms4u.info
  2. 2. http://www.ms4u.info Book Video
  3. 3.  Defining Hybrid Cloud  Infrastructure As A Service  Take a Look Scenario  Summary & Wrap Up
  4. 4. Today’s Focus:
  5. 5. Microsoft Azure Storage
  6. 6. Microsoft Azure Storage Highly Durable Storage
  7. 7. WEST DC EAST DC > 400 miles continuous storage geo-replication Geo-Replicated Storage Microsoft Azure Storage
  8. 8. Azure Storage Scenario
  9. 9. Backup datacenter data to Windows using SystemCenter Data Protection Manager Backup and recover files/folders from Windows Server 2012 Benefits Reliable offsite data protection Simple, familiar, integrated Efficient backup and recovery Easy set up Your On-Premises Datacenter
  10. 10. Data Protection Manager Centralized protection for Hybrid Cloud workloads Workloads – DPM protects key workloads, at a granular application level, up to every 15 minutes. Disk/Tape – DPM supports protecting short-term to disk, and long-term to tape. Centralized – With integration with OpsMgr, the central console enables management of all DPM servers from a single location. Azure Integration – DPM now supports archiving data up to Microsoft Azure Low-Cost DR – DPM on site 1, can be protected by DPM on another site, for DR purposes. Scalable – 800 VMs per DPM server, parallel backups, page-file exclusion, Live Migration support
  11. 11. Azure Site Recovery Extensible Data Channel (Hyper-V Replica, SQL Always-ON)
  12. 12. Microsoft Azure Extensible Data Channel Microsoft Azure Site Recovery Compute Storage Networks
  13. 13. Options for On-Premises VPN Gateways
  14. 14. Virtual Network Scenario
  15. 15. Existing Datacenter Windows Azure Active Directory SharePoint SQL Server Branch Datacenter Point-to-Site VPN For Remote Users Windows Azure Active Directory SharePoint SQL Server
  16. 16. Virtual Network - Compute only. ExpressRoute - Provides customer choice and include access to compute, storage, and other Azure services. Public internet Public internet Public internet
  17. 17. Redundancy at every level
  18. 18. Virtual Machine Scenarios
  19. 19. 80/443 Cloud Service SQL DB Mirroring / AlwaysOn VPN Tunnel Distributed Filesystem Replication ( DFS-R ) Xcopy / Robocopy based Deployments
  20. 20. LB 80/443 WEB Cloud Service 2 SQL Cloud Service 1 AD/DNS Corp Users VPN Tunnel
  21. 21. {
  22. 22. Hyper-V, System Center & Microsoft Azure: A More Complete Solution Platform
  23. 23. Virtual Lai’s Blog Q&A www.ms4u.info Hyper-V 2012 R2 :-http://www.microsoft.com/en-us/ evalcenter/evaluate-hyper-v-server-2012-r2 System Center 2012 R2 :-http://www.microsoft.com/en-us/server-cloud/ products/system-center-2012- r2/default.aspx Microsoft Azure :-http://azure.microsoft.com/en-us/ Storsimple :- http://www.microsoft.com/en-us/server-cloud/ products/storsimple/ Thank you

Notas del editor

  • On-premise description
    -> scale out
    -> Building up
    -> maintaining

    Let look into how Azure present into different Cloud Computing Model
    Azure is the only provider that provide entire CCM
    1. As start of, most people will go Iaas -> where people deploy VM and deploy custom app. Hardware support offload to service provider (In this case: Microsoft)
    2. Next, step don’t create VM but leverage on MS Solution . Example:- Office 365 to hold mailbox, sharepoint, collaboration
    Last but not least SaaS, we just use our own pre-package and deploy app to cloud - website & database.
    You have choice to decide which CCM is suitable for you and today session we will talk on different layer of Iaas
  • 4 trillion object
    You can create 200 storage account
    Each storage account can hold 200 TB
  • How it work?
    We store data is 3 disk – like mirror
  • If die, it is durable. Azure will mark as die and create another copy
  • If 3 disk not enough, you can enable geo redundant by replicating to another DC. (more than 400 miles away)
    Why 400 miles?
  • After you have create storage account, now let look into where we can use it?
  • Deduplication
    Compressed
    Encrypted
  • Another piece is backup to Cloud. For remote office without invest expensive backup software/ tape library.
  • For enterprise solution, use DPM
    -data is encrypted
  • 2nd Topic- Virtual network
    We create another virtual network – different subnet from your on premise.
    It is similar as remote office/data center
  • One of option to bridge on-premise to Azure. We have supported list
    Generic VPN device will work as long it support IKE, AES, SHA
  • 1st- Site to Site VPN
    -setup a vpn tunnel-

    2nd – Site to Multisite VPN
    3rd – Vnet to Vnet
    4th – Point to site VPN
    -client computer can connect using certificate (protected connection)
  • Another option without using site to site vpn is
    Use Express Route
    Rely on Exchange provider – another leased line Equinex, Singtel (10GB link)
    Leased line to their datacenter & your data center

    2. Use MPLS
    -Can be part of your existing MPLS network
    -Give 1GBps connection (MPLS connection)
    -currently available in US

    Cloud on your MPLS VPN
    Avoid risks from exposure to Internet
    Avoid complexity and added costs
    Provides lower latency, higher bandwidth and greater availability
  • Switch gear to last gear, we are looking on Compute
  • Let start by looking on VM Sizes
    A2- A4 -> High IO
    A5 –A7 -> High memory
    A8- A9 -> High Compute
    For other , submit feedback.
  • Slide Objective: Discuss how to achieve an SLA of 99.95% for VMs

    Key Talking Points:
    Configuring at least two VMs performing the same workload in the same availability set provides a 99.95% SLA
    Virtual Network SLA = 99.9%
    VMs in same availability set are automatically placed in separate upgrade and failure domains ( racks ) within a datacenter.
    Azure SLA is more granular than competition – mapped to availability of specific infrastructure components that are hosting VMs, instead of generically mapped to edge of a datacenter region
    SLA for VM’s based on monthly availability instead of annual availability ( most of competition ).
    Complete SLA for VMs available at http://www.microsoft.com/en-us/download/details.aspx?id=38427
  • In term of management, you can use SC components to connect and manage Hybrid Cloud. Some of you may familiar with SC
    Example:-
    App C – connect Private Cloud & Public Cloud
    VMM – Manage different hypervisor (Hyper-V, Vmware, Citrix), manage compute , network , storage & create private cloud
    Hypervisor – use Hyper-V
    OM – for monitoring cloud fabric, app, & azure
    SM – for ticketing & self service provisioning
    SCOM – Orchestrating & automating datacenter
    DPM – backup and recovery when needed
  • To wrap up about our session today
    We have covered definition of Hybrid Cloud & talk about different CCM and we focus on Iaas
    We look on how durable and scalable storage to hold data, backup and setup DR
    Then leverage on virtual network to extend your datacenter to different network
    Last but no least, we can easily select different VM images to hold your application & SC to manage private & public cloud
    Among entire MS product, Hyper-V, SC and MS Azure is the solution best for your organization to a step extend your on-premise infrastructure to Azure

×