SQL Server 2008 R2 - Implementing High Availabilitty

1,183 views

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,183
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
52
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

SQL Server 2008 R2 - Implementing High Availabilitty

  1. 1. SQL Server 2008 R2<br />Implementing High Availability<br />
  2. 2. High availability Challenge<br />
  3. 3. SQL Server 2008 R2 High Availability<br />Goals<br />Hardware<br />Failover Clustering<br />Database Mirroring<br />Replication<br />Log Shipping<br />
  4. 4. Goals for High Availability<br />Second copy of our data<br />Have Real time or Near Real time switch over<br />Second copy – Updated Frequently<br />Reduce workload – Automatic Switch over to the second database<br />Less downtime for our users<br />
  5. 5. Techniques available<br />Hardware<br />Failover clustering<br />Database Mirroring<br />Replication<br />Log Shipping<br />
  6. 6. Hardware<br />Redundant Power supplies<br />RAID Arrays<br />Redundant CPU Power <br />Redundant Network Cards<br />SCSI/SAN Controllers<br />Key is redundancy<br />
  7. 7. SQL Server failover clustering<br />Node A<br />Node B<br />H/W<br />H/W<br />Nodes<br />Clients<br />Active - Passive<br />
  8. 8. SQL Server failover clustering<br />Node A<br />Node B<br />H/W<br />H/W<br />Nodes A<br />Nodes B<br />Active - Active<br />Clients<br />
  9. 9. A<br />SQL 1<br />SQL 2<br />D<br />B<br />SQL 7<br />SQL 3<br />SQL 8<br />SQL 4<br />C<br />SQL 5<br />SQL 6<br />
  10. 10. SQL 1<br />(Principal)<br />SQL 2<br />(Mirror)<br />A<br />A<br />(copy)<br />Transaction<br />B<br />Clients<br />SQL Native Client<br />
  11. 11. Database Mirroring<br /><ul><li>Hot Standby protects against database or server failure
  12. 12. Provides a fault-tolerant database
  13. 13. Cost effective as no specialized hardware is required
  14. 14. Straightforward setup and administration
  15. 15. Automatic or manual failover
  16. 16. SQL Server 2008 R2 does not require a database restart after manual failover
  17. 17. No shared components; two separate copies of data
  18. 18. SQL Server 2008 compresses the log stream from principal to mirror</li></li></ul><li>Database Mirroring<br />Several different modes available<br />It works on per database, clustering is per instance basis<br />Interaction with other database features which involve storage outside database<br />Log shipping<br />Full text catalogues<br />Database snapshots<br />Replication<br />Does not support FILESTREAM<br />Need to create server logins<br />
  19. 19. Replication<br />Transactional<br />Merge Replication<br />Snapshot Replication<br />There is no built in type of Failover<br />
  20. 20. A<br />B<br />C<br />
  21. 21. Clients<br />Tokyo<br />New York<br />New Delhi<br />
  22. 22. Replication<br />High performance ─ latency measured in seconds<br />Minimal load on the server<br />Cost effective as no specialized hardware is required<br />Straightforward setup and administration<br />Subscriber is accessible <br />Used mainly for Scalability<br />
  23. 23. SQL 1<br />SQL 2<br />A<br />A<br />(copy)<br />Transaction Log Backup<br />Transaction Log Backup<br />B<br />Clients<br />
  24. 24. Log Shipping<br />Not Real-time<br />Less Resource Hungary on Servers<br />Supports FILESTREAM<br />Provides database redundancy<br />Every some [Time]<br />Filestream<br />
  25. 25. Log Shipping<br />Cost effective as no specializedhardware is required<br />Straightforward setup andadministration<br />Running read operationssuch as reports on asecondary server is permitted<br />Users are disconnected when logrestore occurs<br />
  26. 26. Log Shipping<br />Can maintain multiple secondary servers<br />Records history and status of backup/restore jobs<br />May set up to raise alerts when jobs fail<br />
  27. 27. SQL Server 2008 R2 High Availability<br /><ul><li>Goals
  28. 28. Hardware
  29. 29. Failover Clustering
  30. 30. Database Mirroring
  31. 31. Replication
  32. 32. Log Shipping</li></li></ul><li>Thank you and Q.A.<br />

×