反向Logshipping以避免巨大的停机时间！ [英] Reverse Logshipping to avoid huge downtime !
问题描述
嗨专家，
需要你的帮助，我们正在进行从一个DC到另一个DC的非常大的MSSQL数据库迁移。
我们已配置日志传送，以减少迁移过程中的停机时间。我们的应用团队要求进行2-3次测试，他们需要DB在辅助服务器上使用最新可用数据在线（他们可以将此测试
数据复制到主数据库）
以下是我的问题：
假设A为主服务器，B为辅助服务器
在应用程序测试期间，反向日志传送可以完成两次，即B到A和A到B （目标是将主要作为主要，次要作为次要）。
还请告知是否在此反向日志传送过程中提出任何挑战？谢谢
$
问候，
Naren Poosa
Hi Experts,
Need your help,we are doing a very large MSSQL database migration from one DC to another DC.
We have configured log shipping to promote less downtime during the migration. Our application team requesting for 2-3 testings for which they need DB to be online in secondary server with latest available data (They are okay to replicate this testing
data to primary database)
Here is my question:
Assume A as Primary server and B as secondary server
During application testing, reverse log shipping can be done two times i.e B to A and A to B (goal is to make primary as primary and secondary as secondary).
please also advise if it raises any challenges during this reverse log shipping ? Thank you
Regards,
Naren Poosa
推荐答案
我们已配置日志传送，以减少迁移过程中的停机时间。
我们的应用团队要求进行2-3次测试，他们需要数据库在辅助服务器上联机，并提供最新的可用数据（他们可以将此测试数据复制到主数据库）
We have configured log shipping to promote less downtime during the migration. Our application team requesting for 2-3 testings for which they need DB to be online in secondary server with latest available data (They are okay to replicate this testing data to primary database)
我正确理解，应用团队需要在线辅助数据库（处于恢复模式）？你需要恢复它以使其在线，当你这样做时，数据库就没有日志传送。
Just so I understand correctly, the app team is needing the secondary DB (which is in restoring mode) online? you'd need to recover it to make it online and the moment you do that, the DB is out of log shipping.
一般的做法是在DEV / TEST环境使PROD可以正常运行。他们必须等到数据库完全切换，这将是您进行上次日志备份并删除/获取主脱机数据库
上的数据库，然后将上次日志备份还原到辅助服务器上并恢复数据库。
General practice is to do all sort of testing in the DEV/TEST environment so that PROD can go normally. They would have to wait until the DB is fully cut-over, which will be when you take the last log backup and remove/take the DB on the primary offline followed by restoring that last log backup on to the secondary server and recovering the DB.
这篇关于反向Logshipping以避免巨大的停机时间！的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
