Enhancing Scalability and Availability of the Microsoft Application Platform

Damir Bersinic Ruth MortonIT Pro Advisor IT Pro AdvisorMicrosoft Canada Microsoft Canadahttp://blogs.technet.com/canitpro http://blogs.technet.com/cdnitmanagers

Developer IT Professional

Where Are We Now?

Agenda

Application InfrastructureThe Web Tier (IIS 6)The Middle Tier (BizTalk Server 2006)The Data Tier (SQL Server 2005)

Microsoft Application Platform Stack

Application Infrastructure

Availability and Scalability

Availability

“It’s there when I want it”Scalability

“It performs the same with 1000 users as with 100 users”

The Web Tier

Content and Configuration ManagementIIS Configuration ReplicationContent Storage OptionsContent Replication

IIS Configuration Replication

Local Content Storage

Web andContent

Web andContent

Web andContent

Web andContent

Web andContent

` Firewall(s)

Internet

Load Balancer(s)

Remote Content Storage`

Firewall(s)

Internet

Load Balancer(s)

Content Server(s)

Content Replication

DFSReplication

NAS Storage2

Cluster1

Cluster2

NAS Storage1

DemonstrationUsing IISCnfg.vbs for Configuration ReplicationXcopy Deployment of Contoso Store Content

The Web Tier

Dealing with Web Traffic Scalability and AvailabilityDNS Round Robin3rd Party Load BalancersWindows Server 2003 Network Load Balancing

Demonstration Set-up Network Load Balancing on Front-End Web Servers

ASP.NET 2.0 Considerations

ASP.NET 2.0 ConsiderationsView stateForms authenticationWebresource.axdMachine key common valueCaching

ASP.NET Session StateCannot use default InProc

The Middle Tier

BizTalk Server 2006 functionality can be distributed across several machines

Hosts are running process on a machineHosts can be factored across BizTalk server machinesHosts can be clusteredNLB can also be used to scale some adaptersAlso need to consider BizTalk databases

The Data Tier

Key element in the application architectureUsed by web application to store and retrieve data

May also be used to store session state info

Used by BizTalk Server 2006 for all operations

Data tier must be available and perform well

SQL Server Always On Technologies

Technologies supporting mission critical applications that demand the highest level of availability

Increased availability during planned downtimeApplication, OS, hardware upgrade, maintenance & operations

Protection & fast recovery from unplanned downtimeHuman and system errors, data corruption, natural disasters

Available today in SQL Server 2005 Enterprise Edition

SQL Server 2005 Always On Solutions

High Availability Requirement

Solution

System Administration Online management

Recovery from application or user errors

Logical recovery

Site disaster protection Database or storage mirroring

Database workload scale out with redundancy

Replication

Online Management• Downtime Scenarios

– Applying a patch or upgrade– Moving a table as part of system maintenance– Deploying a new version of an application– Recovering from a corrupted data file

• Always On Solutions– Rolling Upgrades and Hotfixes utilizing Database Mirroring, Log

Shipping, or Replication– Online alter table, index create, index rebuild– Online granular restore

EnterpriseEdition

EnterpriseEdition

Recovery from User or Application Errors• Downtime Scenarios

– A table is accidentally dropped– An application makes incorrect updates to data– A user possibly made unauthorized changes to data

• Always On Solutions– View point in time snapshots of the system

• Take database snapshots at intervals• Log ship to another site using restore delay/standby options • Log marks taken at key points in time• Compare table to older version using tablediff utility

– Track history of DML statements • Use SQL Trace or customized replication

Local Protection - Microsoft Clustering

Local server hardware redundancy Using a shared disk subsystemEntire instance virtualized and fails over as a unitCan include other non-SQL Server resourcesClustering can also be combined with Database Mirroring, Log Shipping, or Replication

Site Disaster Protection

Downtime ScenariosEarthquake, fire, or flood causes datacenter outage

Always On SolutionsDatabase Mirroring to a secondary site

Optimized solution - allows very fast failover times to the secondary siteOptionally add log shipping for additional site protectionCannot be used for BizTalk Server 2006 databases

Third party geo-clustering solutions for data center storage level redundancy

Find SQL Server Always On reviewed solutions at the Microsoft Always On website: www.microsoft.com/SQL/AlwaysOn

Principal

Witness

Data Log

Mirror

Client

1. Commit

2. Write to Log

2. Transfer to mirror

6. Acknowledgement

7. Acknowledgement

4. Write to Log

5. Log written

Data Log

3. Log written

Synchronous Database Mirroring

Database Mirroring Client Setup

1. Add the failover partner property to the connection stringOLE DB IDBInitialize::Initialize and DBPROP_INIT_PROVIDERSTRING uses “…;FailoverPartner=serverName;…”OLE DB IDataInitialize::GetDataSource and pwszInitializationString parameter use “…;Failover Partner=serverName;…”ODBC “…;Failover_Partner=serverName;…”ADO and ADO.Net “…;Failover Partner=serverName;…”JDBC SQL Server 2005 Driver 1.1 “…;failoverPartner=servername;…”

2. Specify the default database in the connection stringDon’t rely on “use mydb” in your application logic

3. Ensure you have re-connect logic. The client does not automatically re-connect, it re-directs

DemonstrationConfiguring synchronous database mirroringConfiguring the application for database mirroring and failover

Database Scale Out with Redundancy

ScenarioReal time reporting on one or more secondary servers that can also be used for disaster recoveryTier of identical databases for scaling out applications which are partitioned by site

SolutionsTransactional Replication Peer to Peer Replication

EnterpriseEdition

Database Scale Out with Redundancy

Mississauga

Transactional ReplicationReporting + Redundancy

Peer to Peer ReplicationScale Out* + Redundancy

Toronto

Toronto

VancouverHalifax

Calgary

England

*Application data modifications must be partitioned by site to prevent conflicts

DemonstrationConfiguring Peer to Peer Replication

Putting it all together…

Database Mirroring

Hot Standby

Warm Standby

Logical RecoveryStandby

Log Shipping

Log Shipping With Restore Delay

ProductionDatabase

Replication

DatabaseScale Out

For Queries

Clustering

Database MirroringPrimary disaster site for databases

Log ShippingAdditional disaster sites for databasesLogical Recovery

ReplicationDatabase reporting and read scale out with redundancy

ClusteringLocal server redundancy

Session Summary

Web Tier Configuration and content replicationNetwork Load Balancing

Middle TierClustering

Data TierMost important to protect and have perform wellLeverage SQL Server Always On technologies

resourceswww.microsoft.ca/technet/unify/resources

Developer IT Professional

What’s Next?

Thanks! Please Fill Out Your Evaluations!