Over 60 CIOs and Tech Leaders attended the #GoCloudWebinar on “AGILE INFRASTRUCTURE WITH WINDOWS AZURE” hosted by Aditi Technologies and Microsoft. Our CTO, Wade Wegner and Microsoft Azure solution specialist, Dina Frandsen discussed how Windows Azure Infrastructure Services (WAIS) can help organizations stay agile and what Windows Azure technology environment looks like and what it means to your organization.
We Explored
1. How IT teams can execute fast and stay lean with WAIS – A case study
2. Which enterprise workloads are best suited of WAIS migration
3. What are the best practices on how to plan, execute, deploy WAIS
Download this slidedeck and Sign up with the below link for viewing the Webinar - http://www.aditi.com/webevent/Agile_Infrastructure_with_WAIS/
19. 1919
WHO AM I?
Chief Technology Officer at Aditi Technologies
Formerly a Windows Azure Technical Evangelist at Microsoft
Blog: http://www.wadewegner.com/
Twitter: http://twitter.com/WadeWegner
Github: https://github.com/wadewegner
20. 20
SCENARIOS & WORKLOADS
Scenarios
Identity Modernization
Disaster Recovery
Development & Test
Product Workloads
Active Directory
SQL Server
SharePoint
22. 2222
IDENTITY
Regardless of your intended use of the cloud, identity is always the first thing that you
need to figure out when moving to the cloud.
Cornerstone to the Cloud
24. 2424
IDENTITY
Business drivers
Support pre-requisites for other Applications or Services
Serve as substitute or failover for branch-office/HQ domain controllers
Serve as primary authentication for cloud only data center
Why Active Directory on WAIS?
25. 2525
IDENTITY
Is it safe to virtualize DCs?
Placement of the Active Directory database (DIT)
Optimizing your deployment for traffic and cost
Read-Only DCs (RODC) or Read-Writes?
Global Catalog or not?
Trust or Replicate?
IP addressing and name resolution
Geo-distributed cloud-hosted DCs
Considerations
30. 3030
DISASTER RECOVERY
Design for Failure => Cloud Outages Happen
Compose with the proper building blocks
Infrastructure abstractions
Automation
Architectural options to mitigate failure
Fault tolerance
Design incorporating redundancy and replication
High availability
Disaster recovery
Considerations
31. 3131
DISASTER RECOVERY
Disaster recovery is about preparing for and recovering from a
disaster.
Hardware or software
Network or power outage
Physical damage to a building
Human error
… or something else!
Invest time and resources to plan, prepare, rehearse,
document, train, and update processes to deal with events.
Continual process of analysis and improvement
What is Disaster Recovery?
32. 32
DISASTER RECOVERY
SLAs
99% availability = 3.65 days of
downtime
99.5% = 1.83 days of downtime
99.9% = 8.76 hours of downtime
99.95% = 4.38 hours of
downtime
99.99% = 53 minutes of
downtime
99.999% = 5.26 minutes of
downtime
Compounding SLAs
Windows Azure Compute (2
instances) = 99.95%
SQL Azure = 99.9%
Windows Azure Storage = 99.9%
Total SLA
4.38 hours + 8.76 hours + 8.76
hours
21.9 hours
Target: 99.75%
34. 34
DISASTER RECOVER: COLD
Only provisioned
environment is
primary.
Not good if rapid
recovery is required.
Slow to replicate
data to other cloud.
Slow to bring
database to an
operational state.
35. 35
DISASTER RECOVERY: WARM
Database replicated
in secondary but all
traffic going to
primary.
Generally a
recommended DR
solution
Minimal additional
cost
Allows fairly rapid
recovery
36. 36
DISASTER RECOVER: HOT
Parallel deployment
with all servers
running but all traffic
going to primary.
Atypical. Very high
additional cost.
Allows rapid
recovery but not
significantly faster
than “warm”
configuration.
37. 37
DISASTER RECOVERY: HIGHLY AVAILABLE
Live/Live
configuration. May
use geo-targeting
services to direct
traffic to regional load
balancers.
Possible, but costly.
Provides high
availability, but
complex to
implement and
manage.
39. 3939
DEVELOPMENT & TEST
True cloud economics. Pay by the minute.
No hardware to purchase.
No staff to configure the environment.
No floor space or energy costs.
Automation.
Agility
Deploy and configure environments in minutes.
No procurement.
Reduce capital expenditures and maintenance costs.
Optimize utilization of existing hardware.
Provisioned (and de-provisioned) as many machines as you need in minutes.
Global footprint and access.
Opportunities
40. 4040
DEVELOPMENT & TEST
Create a development and test sandbox in minutes.
Develop Windows Server or Linux applications on Virtual Machines.
Script to completely automate deployment.
Test load or scalability.
Accelerate SharePoint or SQL development.
Connect securely from anywhere.
Upload your virtual hard disk.
Advantages to Cloud
43. 4343
APPLICATION WORKLOADS
Supported versions: 2012, 2008 R2, 2008
Provisioning: Use existing VM images or bring your own
Licensing: Pay by the hour or migrate existing licenses
SQL Server
SQL Server
(IaaS)
Windows Azure SQL Database
(PaaS)
Development Migrate Existing Apps Develop New Apps
Management Full Control Managed Service
Compatibility Full SQL Server Capabilities Based on SQL Server Technology
45. 4545
APPLICATION WORKLOADS
SharePoint for Internet Sites (FIS)
Public facing, anonymous access sites
Developer, Test and Staging Environments
Quickly provision and un-provision entire environments
Hybrid Applications
Applications that span your data center and the cloud
Disaster Recovery
Quickly recover from a disaster, only pay for use
SharePoint
48. 4848
OPPORTUNITIES
Along with a Windows Azure commitment to Windows Azure, Aditi will provide an
onsite cloud expert for a 3 or 7-day Cloud Workshop.
The key objectives are knowledge transfer and hands-on experience.
With the 7-day cloud workshop we also focus on pilots and prototypes.
Additional workshops:
Core Infrastructure
Disaster Recovery
Identity Modernization
SQL Server DR & HA
SharePoint Migration
Development & Test
Aditi Cloud Infrastructure Workshop