Madsqlserver
Download as PPTX, PDF0 likes264 views
This document discusses various high availability mechanisms in Microsoft SQL Server 2008 including database mirroring, log shipping, replication, and failover clustering. It provides an overview of each technology, their roles and components, operating modes, and scenarios they are suited for. It also includes demonstrations of database mirroring and high availability configurations.
Madsqlserver
- 1. Mecanismos de alta disponibilidad con Microsoft SQL Server 2008 Por: ISC Lenin López Fernández de Lara
- 2. Temario Database Mirroring Log Shipping Replication Failover Clustering Demo
- 3. 1.1 Database Mirroring Roles
- 4. 1.2 Operating Modes High Availability High Safety High Performance
- 5. 1.2.1 High Availability Operating Mode synchronous Automatic failover Writes a transaction to th transaction log The transaction is first committed on the mirror database Performance impact Uses simple ping
- 6. 1.2.2 High Performance Operating Mode Asynchronou s No automatic failover
- 7. 1.2.3 High Safety Operating Mode Synchronous Manually failover Writes a transaction to th transaction log The transaction is first committed on the mirror database Performance impact
- 8. Log Shipping ¿What is? Provides a means to maintain a secondary server on an automated basis using a chain of transaction log backups Also allows you to configure a monitor server that can verify the health
- 9. 1.1 Log Shipping Scenarios Offloading Report Activity Initialization for Database Mirroring Upgrading Versions or Migrating to a New Platform Primary or Secondary Availability Solution
- 11. 1.1.2 Initialization for Database Mirroring backups of the principal principal and mirror are synchronized minimizes the time
- 12. 1.1.3 Upgrading Versions or Migrating to a New Platform build the new instance a brief outage on the applications move the databases
- 13. 1.1.4 Primary or Secondary Availability Solution Secondary databases an outage of the primary database that applications can switch
- 14. 1.2 Log Shipping Components
- 15. Replication ¿What is? Replication is designed as a data-distribution mechanism. The core replication engine is designed for very flexible implementation The core architecture can be used to provide availability for a database because a redundant copy of data is maintained in synchronization with a master copy
- 16. 1.1 Replication Components • The basic building block of replication • Can be defined against a table, view, stored procedure, or function Articles • Publications are groupings of articles that define the replication setPublications • You can apply one or more filters to each article that restrict the set of data that is replicated. • You can fi lter articles by rows or by columns Filters
- 17. 1.2 Replication Roles • Maintains the master copy of the data within a replication architecturepublisher • Is the database that is receiving changes from the replication engine defined by the publication to which it is subscribing subscriber • Is the main engine within a replication architecture • The distribution database is stored on the instance that is configured as the distributor (An instance of SQL). distributor
- 22. 1.6.1 Snapshot Replication 1. Snapshot Agent extracts the schema and BCPs the data 2. Distribution Agent then picks up and applies the snapshot to each subscriber (tables are dropped and re-created, then the data is copied using BCP) It is not normally used for high availability full replace of data
- 23. 1.6.2 Transactional Replication Begins with an initial snapshot being applied to the subscriber to ensure that the two databases are synchronized As subsequent transactions are issued against the publisher, the replication engine applies them to the subscriber.
- 25. Merge Replication ¿What is? Merge replication is another alternative that can be applied to high-availability systems. Merge replication was primarily designed for mobile, disconnected users. By translation, the mechanisms are already built in for changes to occur at any location and get synchronized, as well as to be able to withstand failures and continue processing
- 26. 3.1 Change Tracking (synchronize process) MSmerge _genhist ory MSmerge _tombston e MSmerge _genhist ory MSmerge _tombston e
- 27. Windows Clustering ¿What is? Windows clustering enables multiple pieces of hardware to act as a single platform for running applications.
- 29. 1.2 Types of Clusters Standard Windows Cluster Majority Node Set Cluster
- 30. 2.2 Failover Cluster Instance Components The components that you need to configure for a SQL Server failover clustered instance are the following: IP addresses Network names Disk drives on the shared drive array SQL Server services Service accounts
- 31. Demo Mirroring High Availability
- 32. ¿######?
Editor's Notes
- #4: You can confi gure an optional witness server for each session, and a single witness server can manage multiple Database Mirroring sessions.
- #11: Informe de Actividad de descarga. Usted puede utilizar el log shiping para mantener un servidor de informes. En lugar de restaurar copias de seguridad del registro de transacciones con la opción de No Recovery Option, se puede especificar en Standby en su lugar. Las bases de datos restauradas en Standby Mode habilitar las conexiones, así como las sentencias SELECT que se publicará. Las operaciones de restauración no se les permite, mientras que las conexiones a la base de datos existe. Para reducir al mínimo el tiempo de inactividad, la base de datos secundaria debe tener una latencia muy poco con los database.These principales competidoras requisitos descartar modo de espera como una opción de alta disponibilidad.
- #12: De inicializar la creación de reflejo de base de datos de copias de seguridad de la principal. Después de todo las copias de seguridad de las principales son restauradas, y el director y el espejo se sincronizan, iniciando la sesión de reflejo de base de datos requiere sólo uno o dos segundos. Un ejemplo muy común de la inicialización de una sesión de reflejo de base de datos es utilizar el trasvase para obtener el espejo principal y muy cerca en el tiempo de modo que sólo unos segundos son necesarios para que la base de datos en línea de reflejo sesión. Esto minimiza el tiempo requerido para iniciar el reflejo de base antes de que las aplicaciones pueden seguir para procesar transacciones.
- #13: Un lado a lado de actualización es muy similar a la migración a una nueva plataforma. En ambos casos, se construye la nueva instancia y luego mover las bases de datos. Si usted necesita para reducir al mínimo el tiempo de inactividad de las aplicaciones, puede utilizar el trasvase de registros de aplicar una cadena de registros de transacciones a la nueva instancia. Luego, bastaría con una breve interrupción en las aplicaciones, mientras que el resto de las copias de seguridad de registro de transacciones se aplican antes de las aplicaciones se puede cambiar a la nueva instancia.
- #14: The scope of log shipping is limited to a database SQL Server does not allow multidatabase transactions log shipping breaks this integrity in multiples databases
- #15: Secondary Standby Mode (SELECT statements) or No Recovery. You cannot restore transaction logs when users are connected to the database, so you should not use Standby Mode for high-availability architectures. The monitor server, which is optional within a log shipping architecture, contains a set of jobs that send alerts when the log shipping session is perceived to be out of sync.
- #20: A central publisher topology consists of a single publisher that has one or more subscribers. The central publisher contains the master copy of the data and is used to set up the replication architecture. In this topology, data changes generally occur at a single source, the publisher, and fl ow down to one or more subscribers, as shown in Figure 17-1. A central publisher is the most common topology used in replication.
- #21: A central subscriber topology consists of a single subscriber that has more than one publisher. Changes are written to multiple publishers and then consolidated into a single subscriber, as shown in Figure 17-2. A central subscriber topology is normally used for consolidating multiple databases or as a central reporting database.
- #27: Each time the merge engine runs, it makes one basic request of both the publisher and subscriber (manda lo que no tenga moves only the changes that do not already exist) When a change is applied, it is removed from the replication engine. The merge metadata tables are located in the same database as the articles you are publishing. Therefore, when you back up the database, you back up the merge metadata at the same time The merge engine uses the metadata to determine the changes that need to be applied. Because both publisher and subscriber maintain a full history of all changes and the metadata is stored within the same database participating in replication, backup/restore processes keep the metadata synchronized with the data being replicated. This ensures that the merge engine can recover, even from a restore operation, and incrementally resynchronize itself.
- #29: MSCS=Microsoft Cluster Server