解决了

灾备中的保护域和恢复

  • 2016年5月4
  • 5回复
  • 1290的浏览量
B
Userlevel 1
徽章 ＋６
我的想法是发表这篇文章，而不是一遍又一遍地窃听我们的SE;)

试图准备一个灾难恢复计划，以防止重大灾难，如服务器室火灾……

我们在地理上有两个集群，我将它们设置为远程站点。A点和B点叫他们。

我已经和虚拟机建立了PD和一致性组来保护站点a到站点b，并定期进行快照。现在，在站点a集群发生火灾/烧毁的情况下……显然，第一步是使用适当的配置在该站点上重建集群，但然后……

有了一个全新的集群后，从站点B检索快照到新站点a的标准流程是什么?

到目前为止，我已经在站点B上激活了备份(就像它是一个计划外的中断并停止了它一样)。在新建的站点a上重新创建远程站点链接。我在想，我现在创建一个新的PD，将虚拟机/一致性组转移到站点a，然后在那里激活，这样就完成了?

我知道这是可行的，就像我现在做的。但这是“首选方法”吗?

我很感激那些大师们的任何想法;)

谢谢,布伦特
图标

最佳答案乔恩2016年5月4日18:42

查看原始
    \n
    \nTrying to get a disaster recovery plan in place to protect against a major disaster such as server room fire...
    \n
    \nWe have a couple of clusters geographically separated which I have set up as remote-sites. Site A and B lets call them.
    \n
    \nI've set up a PD w\/ consistency group with the VMs to protect and periodically snapshot from site A to B. Now in the case of a fire\/destroyed cluster at site A... obviously step one is rebuilding a cluster at that site with the appropriate configs, but then...
    \n
    \nWith a brand new cluster in place, what is the standard process to retreive the snapshots from site B back to the new site A ?
    \n
    \nSo far, I've activated the backup on site B (as if it was an unplanned outage and left it off). and recreated the remote-site link on the newly built out site A. I am thinking I now create a new PD to shuffle the VMs\/consistency group back to Site A and then activate there and I am done ?
    \n
    \nI know this works as I've done it now. But is this the 'preferred method'?
    \n
    \nI'd appreciate any thoughts from the gurus out there ;)
    \n
    \nthanks, Brent","quoteUsername":"BrentHysop","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    5回复

    乔恩
    排名
    Userlevel 6
    徽章 + 29
    基本上你用相同的名字重做PD，这将允许你拉PD/快照回来
    JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
    乔恩
    排名
    Userlevel 6
    徽章 + 29
    (标准免责声明)如果这发生在现实生活中，在做任何事情之前，总是做一个支持票，我们会帮助你在正确的方向。
    JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
    B
    Userlevel 1
    徽章 ＋６
    哈!非常感谢你的提示，我完全错过了
    D
    Userlevel 1
    徽章 ＋２
    你能预先构建failback PD吗?没有计划的复制等，但当您迁移到故障转移位置后，它可能允许加速故障恢复?
    乔恩
    排名
    Userlevel 6
    徽章 + 29
    -嗯，我想我没听懂你的提示。

    如果您有两个集群，A和B，并且您将一个PD从A迁移到B，并且集群A仍然存在，那么根据定义，PD将带有一些种子数据“在那里”，从而使您能够更容易地进行重复复制和返回失败。

    在集群A“消失”的情况下，那么您就不能真正地预先构建任何东西。



    也就是说，如果我没有理解这一点，请随意重申，我将再次回击。

    欢呼,
    乔恩
    JonKohler |技术总监，工程，Nutanix | Nutanix NPX #003, VCDX #116 | @JonKohler |如果有用请赞美!
    \n
    \nIf you had 2 clusters, A and B, and you migrated a PD from A to B, and cluster A still existed, then by definition the PD would \"be there\" with some seed data, allowing you to re-replicate and fail back much easier.
    \n
    \nIn the case where cluster A \"went away\", then you can't really pre-build anything.
    \n
    \n
    \n
    \nThat said, If I missed the mark on understanding this, feel free to restate and I'll take a second swing.
    \n
    \nCheers,
    \nJon","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    回复


    Baidu