登录查看更多内容

How does database mirroring contribute to disaster recovery efforts?

由人工智能和领英社区提供技术支持

Database mirroring is a vital strategy in disaster recovery plans, ensuring that when the unforeseen strikes, your data remains accessible and secure. It involves creating a direct copy, or mirror, of your database on a separate server. This redundancy means that if your primary database fails due to hardware issues, software problems, or natural disasters, you can quickly switch to the mirrored server with minimal downtime. By preparing for the worst, you can maintain the integrity and availability of your critical data, which is the lifeblood of modern businesses.

此文章中的业界达人

由社区从 10 条内容中精选。了解更多

Nguyen Vu Quan

?Project Manager | Backend Engineer | AWS | 日本語（N1）
Jansel Fernández Guzmán

Sub Gerente de Bases de Datos en Asociación Popular de Ahorros y Préstamos | Bases de Datos, RDBMS
Rogerio Macedo

IT Senior Consultant / DBA

1 Mirror Basics

Database mirroring is a process where data is copied in real-time from one database (the principal) to another (the mirror) on a separate server. This ensures that an up-to-date copy of the database is always available. The principal and mirror databases are typically synchronized over a network, allowing for immediate failover in case the principal server encounters issues. This high availability setup is crucial for maintaining continuous operation and is a core component of a robust disaster recovery strategy.

添加您的观点

Rogerio Macedo

IT Senior Consultant / DBA
举报内容
A depender do tipo de base de dados escolhido (SQL Server, Oracle, Postgres, etc...) o espelhamento pode ser útil n?o apenas em caso de problemas, mas em atualiza??es do sistema operativo e também do próprio motor da base de dados. Ou seja, para o espelhamento deve-se levar em conta, além da disponibilidade desejada, a janela mensal de manuten??o disponível.

已翻译

赞
Nguyen Vu Quan

?Project Manager | Backend Engineer | AWS | 日本語（N1）
举报内容
Real-time data copying between the principal and mirror databases requires constant synchronization over the network, which can consume significant bandwidth, especially in environments with large databases or high transaction volumes. Should assess network bandwidth requirements and potentially implement network optimization strategies, such as Quality of Service (QoS) policies or dedicated network links, to ensure efficient data transfer without adversely affecting other critical business operations.

已翻译

赞

2 Configuration Types

There are two main types of database mirroring configurations: synchronous and asynchronous. Synchronous mirroring provides a high level of data protection by ensuring that transactions are committed on both the principal and mirror databases simultaneously. Asynchronous mirroring, while less protective, allows for the principal database to operate with less latency since transactions do not need to be confirmed by the mirror before proceeding. Your choice depends on the balance between performance needs and data safety requirements.

添加您的观点

Rogerio Macedo

IT Senior Consultant / DBA
举报内容
Normalmente se define sincronismos assíncronos quando o mesmo é feito para um site de contingência, como um terceiro mirror. Onde é se leva em considera??o a perda de dados aceitável (RPO) do sistema.

已翻译

赞
Nguyen Vu Quan

?Project Manager | Backend Engineer | AWS | 日本語（N1）
举报内容
Synchronous mirroring guarantees robust data protection by confirming transactions on both the principal and mirror databases before proceeding. However, this approach may introduce latency due to the wait time for confirmation. On the flip side, asynchronous mirroring, while offering lower latency, may entail a higher risk of data loss during failover since some transactions might not have been replicated to the mirror database. Hence, carefully assess the needs of their systems and applications to determine the most suitable mirroring configuration, factoring in transaction volume, acceptable latency, and tolerance for data loss.

已翻译

赞

3 Role Switching

In the event of a disaster, role switching is the process of promoting the mirror database to become the new principal database, ensuring continuous data availability. This can be done manually or automatically, depending on the configuration. Automatic failover is particularly useful in scenarios where immediate action is required and manual intervention may not be feasible, providing a seamless transition with minimal service interruption.

添加您的观点

Nguyen Vu Quan

?Project Manager | Backend Engineer | AWS | 日本語（N1）
举报内容
Administrators should establish clear guidelines and procedures for both manual and automatic role switching scenarios. Additionally, conducting regular failover drills and testing the failover mechanisms helps validate the effectiveness of the disaster recovery strategy.

已翻译

赞
Rogerio Macedo

IT Senior Consultant / DBA
举报内容
Em sistemas SQL Server a "troca de fun??o" pode ser utilizada até para as aplica??es dos patchs mensais da Microsoft, pois é possível o retorno ao "original" sem impactos. Em clusters Oracle se utiliza a metodologia "ativo-ativo" onde n?o se usa o "espelhamento", pode-se ter através de ferramentas da própria Oracle (Dataguard) uma base cópia que se assemelha a isso, mas essa é apenas para recupera??o de desastres. Em Postgresql uma cópia pode ser feita através de replica??o de dados, mas a troca de fun??o deve ser utilizada apenas para casos de desastres pois a volta pode n?o ser possível.

已翻译

赞

4 Monitoring Needs

To ensure that database mirroring contributes effectively to disaster recovery, constant monitoring is essential. You need to track the status and health of both principal and mirror databases. Monitoring tools can alert you to any synchronization issues or potential failures, allowing for preemptive action to prevent data loss. Regular monitoring also helps in maintaining performance levels and ensuring that failover systems are ready when needed.

添加您的观点

Nguyen Vu Quan

?Project Manager | Backend Engineer | AWS | 日本語（N1）
举报内容
Another aspect to consider for monitoring needs in database mirroring is the implementation of automated alerts and notifications. Administrators can configure monitoring tools to send alerts via email, SMS, or other communication channels when predefined thresholds or abnormal conditions are detected. For example, alerts can be triggered for unusually high latency in data synchronization, disk space shortages on the mirror server, or service disruptions. By promptly receiving alerts, administrators can take preemptive actions to address potential issues before they escalate into critical failures, thereby improving the overall effectiveness of disaster recovery measures.

已翻译

赞
Rogerio Macedo

IT Senior Consultant / DBA
举报内容
A troca automática para a falha de bases dados é um elemento crucial para reduzir o downtime e garantir a alta disponibilidade. O monitoramento quando configurado deve abranger a base principal e todas as suas cópias.

已翻译

赞

5 Performance Impact

While database mirroring offers significant benefits for disaster recovery, it can impact the performance of your system. The additional network traffic and disk I/O required for real-time data copying can lead to latency, especially with synchronous mirroring. It's important to assess the performance impact in relation to the level of data protection required and to consider network bandwidth and server capacity when implementing a mirroring solution.

添加您的观点

Rogerio Macedo

IT Senior Consultant / DBA
举报内容
Isso deve ser visto em tempo de projeto se possível, e é a principal causa do espelhamento para um site de contingência ser assíncrono.

已翻译

赞

6 Recovery Planning

Incorporating database mirroring into your disaster recovery plan requires careful consideration of recovery objectives. You must establish recovery point objectives (RPOs) and recovery time objectives (RTOs) to determine how much data loss is tolerable and how quickly systems must be restored. Database mirroring can help meet stringent RPOs and RTOs by providing an up-to-date copy of the database and enabling rapid failover in case of a disaster.

添加您的观点

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Jansel Fernández Guzmán

Sub Gerente de Bases de Datos en Asociación Popular de Ahorros y Préstamos | Bases de Datos, RDBMS
举报内容
El mirror es una solución en desuso para los motores con soporte propietario como SQL O Oracle, recomendaría solo usarlo si el costo de otras soluciones como replicación o Always On le resulta costoso, por supuesto en soluciones de base de datos OpenSource puede ser la opción mas fácil de implementar

已翻译

赞

Database Administration

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How does database mirroring contribute to disaster recovery efforts?

1

2

3

4

5

6

7

1 Mirror Basics

2 Configuration Types

3 Role Switching

4 Monitoring Needs

5 Performance Impact

6 Recovery Planning

7 Here’s what else to consider

Database Administration

给文章评分

感谢您的反馈

更多Database Administration相关文章

更多相关阅读内容

How does database mirroring contribute to disaster recovery efforts?

1

2

3

4

5

6

7

1 Mirror Basics

2 Configuration Types

3 Role Switching

4 Monitoring Needs

5 Performance Impact

6 Recovery Planning

7 Here’s what else to consider

Database Administration

给文章评分

感谢您的反馈

查看其他技能