Upload
lucas-dorsey
View
219
Download
1
Tags:
Embed Size (px)
Citation preview
MS Dynamics NAV (Navision) since 1997
MS SQL Server since 2003
100% Focus on „NAV/SQL Performance Optimization“STRYK System Improvement (since 2006)Worldwide support of MS Dynamics Partners & Customers
Microsoft Most Valuable Professional(MVP MS Dynamics NAV)
Book: “NAV/SQL Performance Field Guide” (ISBN 978-3-8370-1442-6)
Software: “NAV/SQL Performance Toolbox” http://www.stryk.info/toolbox.html
Blog: “NAV/SQL Performance – My Two Cents” http://dynamicsuser.net/blogs/stryk/
Contact: [email protected] http://www.stryk.info
Introduction Jörg Stryk
NAV/SQL High Availability:
High Availability with NAV and SQL ServerSome “Inspirations”
Abstract:
With increasing transaction volumes processed by NAV customers the need for HA solutions is also growing. This session will explain some available HA solutions with NAV and SQL as there are e.g. “Transaction Log-Shipping” and “Mirroring”, but also in addition with using “Database Snapshots”. The advantages and disadvantages of the several solutions are discussed to inspire NAV partners to implement the appropriate scenarios at their customer’s sites.
Agenda
Two Big Questions
What is the maximum acceptable Data-Loss?What is the maximum acceptable Server-Down-Time?
Off Topic
Backup Strategies (“Cold Stand-By”)
18:00 … 08:00 09:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00
Full
Diff Diff Diff Diff
Full
Log Log Log Log Log Log Log Log Log Log Log
Window Failover Cluster (“Hot Stand-By”)
Off Topic
Active Node Passive Node
Failover
Storage = „Single Point of Failure“
„Heartbeat“
Active Node Passive Node
Transaction Log Shipping
Warm-Standby Solutions
Failover NAVStandard NAV
Main Server Standby Server
NAV NAV(STANDBY)
Client PC
TRN
Monitor
Database Mirroring
Warm-Standby Solutions
Failover NAVStandard NAV
Principal Server Mirror Server
NAV NAV(NO RECOVERY)
Client PC
LSN
Witness
Synchronous vs. Asynchronous Mirroring
Warm-Standby Solutions
Principal Server Mirror ServerClient PC
LSN LSN
COMMIT COMMIT
aka „High Safety Mirroring“With Witness: „High Availability Mode“
No Witness: „High Protection Mode“
Witness
Synchronous vs. Asynchronous Mirroring
Warm-Standby Solutions
Principal Server Mirror ServerClient PC
LSN LSN
COMMIT COMMIT
aka „High Performance Mirroring“
Database Snapshots
Additional (?)
SQL Server (Enterprise)
NAV
NAV_SNAPSHOT(read only)
Client PC
SnapshotRead/Write
Read Only
Data „Freeze“
Overview
Option Edition Failover Witness Data-Loss Down-Time Performance MultipleMirrors
Connect to Mirror
Costs
Failover Cluster OS: EE Auto n/a minimal minimal high (Yes) n/a $$$
Mirroring (Async) SQL: EE Manual No small medium high No No $$
Mirroring (Sync) All (Auto) Yes minimal medium medium No No $
Log Shipping All (Auto) Yes medium medium medium Yes (Read Only) $
Backups All Manual No medium+ maximum medium Yes n/a $
DB Snapshots SQL: EE n/a n/a n/a n/a n/a n/a Read Only $$
HA & Failover Scenario
Failover NAV #1
Standard NAV
Reporting NAV
Principal Server Mirror Server
NAV NAV(NO RECOVERY)
NAV_SNAP(read only)
Snapshot
BackupBAK/TRN
SQL Backup
Client PC
Mirroring
Standby Server
NAV(STANDBY)
Log Shipping
Failover NAV #2
Challenges
What is the maximum acceptable Data-Loss?What is the maximum acceptable Server-Down-Time?
Transferring Logins
Notifications and Reactions
Time to get Standby-System online
Time to recover Backup
Time to get Primary-System online
Who/What/When
Re-Routing Clients/Service Tier(s)
Create detailed Checklistsand
Failover Plans.Weekend/Holiday
Interfaces
Licensing
Test your Plan!
SQL Server 2012 “Denali”
The Future
HADRON = High Availability & Disaster Recovery - Always ON
• Querying the Mirror (= Replica)• Multiple Replica• Database Availability Groups• Mirroring more than 10 databases• Faster Recovery• Automatic Failover
http://www.microsoft.com/sqlserver/en/us/product-info/future-editions.aspx