* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Powerpoints
Microsoft Access wikipedia , lookup
Tandem Computers wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Extensible Storage Engine wikipedia , lookup
Relational model wikipedia , lookup
Team Foundation Server wikipedia , lookup
Clusterpoint wikipedia , lookup
Database model wikipedia , lookup
SQL Server DR in Microsoft Azure Building Your Second Data Centre SQL Server MVP, MSCE Business Intelligence Data Platform MBA Principal Consultant, Denny Cherry and Associates Co-author “Using Power BI in Hybrid Environment” @jdanton Joeydantoni.com bit.ly/HybridDR 2 3 3 4 Start With RPO and RTO Backup and Recovery RPO—How much data can you afford to lose for a given system? Backing up your data isn’t enough RTO—How long can you system be down without business impact? Regularly test recovery processes (great use case for Azure) Technology Decisions should be driven by these metrics •If you don’t test recovery, save the space and don’t back up your databases! Write everything down and get executive sign off Have a solid process—process is far more important than technology Send backups to multiple locations 5 5 • Types of Cloud Computing Software as a Service (SAAS)—Examples like Gmail, Salesforce.com Infrastructure as a Service (IAAS)— Windows Azure VMs, Amazon AWS, Rackspace Platform as a Service (PAAS)—Microsoft Windows Azure SQL Database (WASD), Amazon RDS (Relational Database Service) 6 6 Since June 2012 (GA as of May 2013), Azure Virtual Machines became available This is an infrastructure as a service model VMs are available preconfigured, or users can supply their own images Can connect to on premises Active Directory and/or DNS via VPN connectivity As of June 2013—available freely for development use with MSDN subscription 7 7 economics usage based automated elastic Managed Hybrid always up. always on. 9 Costs Logistics 10 Redundancy •A live full-time DR site is expensive •Site Rent and Maintenance •Idle Hardware •Ops •Many smaller orgs do not have near time DR at all Not for everyone or every system Is this your workload? Or is this your workload? If so, you probably want your own If hardware. so, you’re probably a good fit for using dedicated Azure virtual machines 11 Biggest question I’ve run into with clients is security Azure Data Centers comply with ISO 27001:2005 SSAE 16/ISAE 3402 Attestation HIPPA Business Associate Agreement VPN connections encrypt data end to end 14 Backup to Azure Backup to Azure Blob Storage 16 Uses Credential stored in SQL Server Starting with SQL 2014 easy encryption available With SQL Server Managed Backup to Windows Azure, you do not have to specify the type or frequency of the backups for a database. You specify the retention period, and SQL Server Managed Backup to Windows Azure determines the type and frequency of backups for a database stores the backups on Windows Azure Blob storage service. Databases must be in full recovery mode System Databases are not supported Azure Blob Storage is only option Max File Size is 1 TB Connecting to Azure Domain Controller SQL Servers VPN Appliance On-premises (Your DC/Colo) Windows Azure Creating Site to Site VPN Connection (MS) Configuring Windows Server 2012 to Use RRAS to Azure 21 22 SQL Server DR Options • Transaction Log Backups take place on primary • External Process ships logs to secondary server(s) • Data can be read on secondary (except during t-log apply) Secondary Server DB (S) Primary Server DB (P) Log Backup Secondary Server DB (S) Optional Pros • Standard Edition • Supports Multiple Targets • Can Read Secondary Copies • Easy to implement in Azure Cons • Dependent on Backup on Primary • Manual Failover Process • Reasonably High Complexity • Azure really requires network and AD This is a really high level view of replication There are numerous topologies and options involved in replication This is the nuts and bolts of it Image Credit—MS Books Online DB1 DB1 Pros • Can Replicate to Multiple Servers • Replicate subset of data • Standard Edition (transactional) • Works well in hybrid model Cons • Manual Failover • Unknown RPO • Can be fragile • Re-sync process can be ugly • Also requires connection change for failover Secondary Server Primary Server Mirror DB Mirror DB Witness Server • Database transactions are compressed and shipped to secondary server (2008+) • The optional witness server facilitates automatic failover • Good model, for secured hybrid environment • Transfer may be sync or async* *Enterprise Edition Only Pros • Automatic Failover (w/witness) • Configuration is fast and easy • Failover happens quickly • Corrupted pages get fixed on secondary • Certificate model good for cross domains and networks Cons • Is per database—multiple DB failovers need scripting • Async only available in EE • Marked as deprecated in SQL 2012 • Secondaries are inaccessible (except for snapshots) Brief Review of Windows Clustering Windows Cluster Q Node 1 Node 2 Node Majority Mode Node and Disk Majority In Node/Disk Majority Mode Cluster sustain node failure Instanc e1 Instanc e2 AG (P) Node A AG (S) Node B Chicago Washington Listener Name (AD VCO) Windows Cluster Requires SQL Server Enterprise Edition Windows Cluster All servers in same Windows Domain Databases Failover as a group No Shared Storage Needed Async and Sync Modes Automatic and Manual Failover Supports up to 8 replica copies Replicas can be read Backups on secondary copies These apply to both on-premises and hybrid AGs • Read Scaling—Can read secondary copies of data • Offload Read workload to Azure • Connect reporting/BI apps or migrate apps • One Button Hybrid Configuration • Offload backups • In the hybrid solution—offload backups to Azure storage to meet offsite backup requirements 35 36 10.1.1.0 Subnet Cloud DC 137.135.45.56 Service Input Endpoint 10.0.1.0 Subnet (VPN) SQL in Cloud 10.0.1.0 Subnet (VPN) Azure Gateway 137.135.45.101 10.0.0.0 Subnet Internet On-Premise DC 37 SQL On Premise SQL Instance 1 SQL Instance 2 On-premises Windows Server Failover Cluster (Same AD Domain) 38 38 • Configuring a Point to Site VPN • AlwaysOn Availablity Groups in Hybrid IT • Listener Configuration for AlwaysOn Availability Groups in Windows Azure • High Availability and Disaster Recovery for SQL Server in Windows Azure Virtual Machines • Using Power BI in Hybrid Environment Microsoft Azure Virtual Machines and Storage offer the same HA and DR options that we have on-site Point to Site VPN allows for testing from our machines Provider connect makes the networking easy(er) Good model for smaller shops that have critical systems 40