解决了

保护域和灾难中的恢复

  • 2016年5月4日
  • 5回复
  • 1290观
B.
UserLevel 1.
徽章 +6
想到我张贴了这一点而不是一遍又一遍地颠簸;）

试图获得灾难恢复计划，以防止服务器室火灾等重大灾难......

我们在地理上分开了几个集群，我已设置为远程站点。网站A和B让他们打电话。

我已经使用VMS设置了PD W /一致性组，以保护和定期从站点A到B的快照。现在在站点A的火灾/被销毁的群集的情况下......显然，第一步是重建群集网站具有适当的配置，但然后...

使用全新的群集到位，从网站B返回新网站a的标准过程是什么标准的过程？

到目前为止，我已经激活了站点B上的备份（好像它是一个计划生命的中断并将其留下）。并重新创建新建网站上的远程站点链接A.我想我现在创建一个新的PD来将VM /一致性组返回到网站A，然后在那里激活我完成了？

我现在知道这件作品。但这是“首选方法”？

我很欣赏那里的大师的想法;）

谢谢，布伦特
图标

最好的答案j2016年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回复

    j
    秩
    UserLevel 6.
    徽章 +29
    基本上你用相同的名称重新发布PD，这将允许您拉回PD /捕捉
    Jon Kohler |技术总监，工程，Nutanix |Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用，请荣誉！
    j
    秩
    UserLevel 6.
    徽章 +29
    （标准免责声明）如果这是在现实生活中发生的话，始终在做任何事情之前进行支撑票，我们将帮助您指向正确的方向。
    Jon Kohler |技术总监，工程，Nutanix |Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用，请荣誉！
    B.
    UserLevel 1.
    徽章 +6
    哈！完美的谢谢你的指针，我完全错过了
    D.
    UserLevel 1.
    徽章 +2
    你能预制作故障恢复pd吗？没有预定的复制等。但是迁移到故障转移位置后，它可能允许加快故障恢复？
    j
    秩
    UserLevel 6.
    徽章 +29
    - hrmm，我不认为我了解那里的提示。

    如果您有2个群集，A和B，并且您将PD从A到B迁移，并且仍然存在群集，则根据定义PD将“与某些种子数据”为“，允许您重新复制和失败更容易。

    在集群A“离开”的情况下，那么你无法真正预制作任何东西。



    也就是说，如果我错过了了解这一点的标记，请随时重述，我会举行第二次挥杆。

    干杯，
    j
    Jon Kohler |技术总监，工程，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