sysadminday2015 benedict berger. Über den sprecher benedict berger
Post on 06-Apr-2016
Embed Size (px)
SysAdminDay2015Benedict Bergerber den SprecherBenedict BergerSolutions Consultant Elanity Network Partner in HannoverHybrid Cloud GuyMicrosoft MVP Hyper-VAutor: Hyper-V Best Practicesbb@elanity.dehttp://blog.benedict-berger.de
AgendaAzure und Hyper-V Better togetherCloudOS berblickHybrid NetworkingHybrid IdentityVirtuelle Maschinen mit Hyper-V und AzureBackupDesaster RecoveryManagement
Die neue ra bei Microsoft setzt auf Devices und Services und damit auf Cloud OS - unsere Vision der modernen Plattform fr globale Anwendungen. Mit unserer Cloud OS Vision mchten wir Sie dabei untersttzen, Ihr Rechenzentrum zu transformieren, Einblicke in Daten jeglicher Art zu erhalten und eine benutzerorientierte IT sowie moderne Anwendungen bereitzustellen.Private CloudService ProviderPublicCloudeinekonsistentePlattformDas Cloud OSWindows AzureRemote Access SzenarioOn-Premises Network
AD / DNS
BranchC.AD / DNSSQL
BranchCacheIP Address Space: 10.1.0.0/16IP Address Space: 10.2.0.0/16
Subnet 10.2.1.0 / 24 - WebSubnet 10.2.0.0 / 24 - GatewaySubnet 10.2.2.0 / 24 - CoreIPv4 ffentliche AddresseHighly Available Active / PassiveCloudNetOnPremNetPoint-to-SiteVPN fr RemoteBenutzer10.3.0.0/24Site-to-Site IPSec VPN tunnelSlide Objective: Introduce Remote Access Scenario with Point-to-Site VPN support
Key Talking Points:On-premises VPN gateway must support Dynamic RoutingUp to 250 concurrent remote client connections supported5Desaster Supersturm Sandy
Azure Site RecoveryEine Lsung fr unterschiedliche Infrastrukturen
Hyper-V zu Hyper-V(on-premises)1Hyper-VHyper-VReplication
Hyper-V zu Microsoft Azure3Hyper-VMicrosoftAzureReplication
VMware/Physical zu VMware (on-premises)4VMware/PhysicalVMwareReplication
VMware/Physical zu Microsoft Azure5VMware/PhysicalMicrosoftAzureReplication
Hyper-V zu Hyper-V(on-premises) via SAN2Hyper-VHyper-V
ReplicationSANSANWhat are the different infrastructures that Azure Site Recovery can provide a solution for?
Well firstly, for customers who have multiple sites, or work with a service provider as a secondary site, and Hyper-V is running on both sites, they can take advantage of Azure Site Recovery to orchestrate the replication and recovery between those sites. In that example, the engine of replication will be Hyper-V Replica, an inbox VM replication technology thats built into Windows Server 2012 and 2012 R2.
For customers with an investment in SAN technology, that includes replication in the box, through integration with Hyper-V, System Center and Azure Site Recovery, customers can orchestrate the replication and recovery of their key workloads between those sites, this time, harnessing the power of the SAN, through asynchronous or synchronous replication, to transfer data between sites.
For customers who dont have a second site, and are running Hyper-V on their primary site, using Azure Site Recovery, customers can orchestrate the replication and recovery of their on-premises workloads, into the Microsoft Azure datacenters, enabling this as a target for failover in the event of a disaster. The engine of replication in this example is Hyper-V Replica.
What about customers who dont have Hyper-V within their datacenters? Well, as we mentioned at the start of the presentation, with the acquisition of InMage, under the umbrella of Azure Site Recovery, customers can orchestrate the replication and recovery of key workloads from physical, or VMware-based sites, over to a secondary site, running VMware also. This time, InMage Scout is providing the replication engine, and is transferring the data between the two on-premises locations.
Finally, just like we saw earlier, where a customers without a secondary location, could use ASR to replicate and recover Hyper-V-based VMs into Azure, with the new InMage technologies, in the future, you will be able to replicate and recover VMware-based VMs into Microsoft Azure. Again, this will be powered by InMage Scout.
2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.8/9/20157
Data Protection Manager
App Controller& Azure Pack
Virtual Machine ManagerEndpoint Protection