异步PD和快照保留在远程站点上

d
徽章 +3
嗨，大家好，

有没有办法更改最小值。在本地站点和远程站点中扣留保留率？
我们有一个PD WICH有两个时间表。
- 每60分钟 - 保持3：3
- 每24小时 - 保持4：4

现在的问题是，如果例如由于网络问题而复制60分钟时间表，或者由于复制所需的时间比正常情况更长，则远程站点上的快照到期。

因此，假设灾难发生在星期一晚上1点。如果第一个管理员到达7am，则每60分钟快照将过期，我们只能与较旧的24小时基础快照一起使用。

在Nutanix KB中，我只能找到本文：
https://portal.nutanix.com/#/page/kbs/details?targetId=ka0600000008dn2caa
其中说：“ ...也必须注意，最小缝制值仅影响当地保护域，而不是遥远的站点……”
\n
\nIs there a way to change the min. snap retention count for local site AND remote site?
\nWe have a PD wich has two schedules.
\n-every 60 mins - keep 3:3
\n-every 24 hours - keep 4:4
\n
\nThe problem now is that if for example the replication of the 60 min schedule fails because of network problems, or because the replication takes longer than normaly, the snapshots on the remote site expires.
\n
\nSo let's say the disaster happens monday night at 1am. If the first admin arrives at 7am, every 60min snapshot will be expired and we can only work with the older 24hour based snaps.
\n
\nIn the nutanix kb i can only find this article:
\nhttps:\/\/portal.nutanix.com\/#\/page\/kbs\/details?targetId=kA0600000008dn2CAA<\/a>
\nwhich says: \"...It's also important to note that the min-snaps value only affects local protection domains, not remote sites...\"","quoteUsername":"Domcura","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
该主题已关闭以供评论

5个答复

j
UserLevel 2
徽章 +11
你好呀，

我可能想念阅读您的帖子，但是遥控快照如何到期？

我最近没有检查过，但是您设置了要保留的快照量，因此目的地应保留快照，直到被新的快照代替。

“有没有办法更改最小的。

是的，您可以针对本地和远程站点制定不同的保留策略，此选项是在创建PD时的时间表

干杯

j
\n
\nI maybe miss reading your post but how are the remote snapshots expiring?
\n
\nI havent checked lately but you set the amount of snapshots to retain, so the destination should keep the snapshots until its replaced by a new one...
\n
\n\"Is there a way to change the min. snap retention count for local site AND remote site\"
\n
\nYes you can have different retention policies for local and remote sites, this option is in the schedule when creating the PD
\n
\nCheers
\n
\nJ","quoteUsername":"jasonc","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
徽章 +3
“我最近没有检查过，但是您设置了要保留的快照量，因此目的地应保留快照，直到被新的快照代替了……”

- 如果那样的话会很棒，但是不幸的是，远程站点 /目的地不在乎是否有新的快照。如果到达到期时间，将删除快照。只有最后一个会保留。但是，如果您有两个时间表的PD时间表，那么最后一个并不总是最新的。

以下是我们的一个PD时间表的屏幕截图：


我已经通过向PD添加1,5TB VM来测试这种行为。
我已经在上午11.30左右添加了机器。因此，最“最新”的快照是从上午11点开始。
然后复制大约需要12-14小时，我们在左侧的偏远站点上只有4个SNPA（3.30am和3天后）

我希望我已经正确解释了
\n
\n- It would be great if it were like that, but unfortunately the Remote site \/ Destination doesn't care if a new snapshot is there or not. If the expiry time is reached, the snapshot will be deleted. Only the last one will retain. But if you have two schedules for a PD, the last one is not always the newest.
\n
\nBelow is a screenshot of our schedule for one PD:
\n
\n

<\/a><\/p>
\nI have tested this behaviour by adding a 1,5TB vm to the PD.
\nI've added the machine around 11.30am to the PD. So the most \"up-to-date\" snapshot was from 11am.
\nThen the replication took about 12- 14 hours and we had only 4 snpas on the remote site left (3.30am and 3 day backwards)
\n
\ni hope i have explained this properly 🙂","quoteUsername":"Domcura","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

j
UserLevel 2
徽章 +11
为什么不只是先获取数据，然后设置您的时间表，以便它只有更新的块需要复制...

如果1.5TB的初始副本不在目的地，则该快照将是不正确的，因为VM数据不在目的地，因此，当您首次在目的地同步到目标时，这将是唯一的可用快照...
\n
\nIf the initial copy of 1.5TB is not at the destination the snaps betweeen will not be correct as the VM data is not at the destination, so when you first initital snapshot is synced at the destination this will be the only availble snapshot...","quoteUsername":"jasonc","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
徽章 +3
这是正确的，但这不是问题。我刚刚完成了这种大型VM快照复制，以证明我是对的。

问题是：
远程站点上的快照到期。无论该网站是否接收新网站。只有最后一个（基本）快照才能持续存在。但是有多个时间表，这不是最新的...

因此，如果我们设置数据保护以保留最后3个小时本地+遥控器和最后4天本地+遥控器，我们可能只能访问最后几天，因为除非我们在3个小时内注意到灾难，否则该小时快照将被删除。

我知道有一个“最小扣除计数”会影响当地的快照。在我们的示例中，我们可以将其设置为7。因此，无论发生什么情况，我们将始终拥有所有的快照。但这似乎不会影响远程站点...
\n
\nThe Problem is:
\nSnapshots on the remote site expire. No matter if the site is receiving a new one or not. Only the last (base) snapshot will persist. But with multiple schedule, this isn't the newest...
\n
\nSo if we setup our data protection to retain last 3 hours local+remote and last 4 days local+remote we might only have access to the last days, because the hour snapshots will be deleted unless we notice the disaster in under 3 hours.
\n
\nI know that there is a \"min-snap-retention-count\" which affects the local snapshots. In our example we could set this to 7. So no matter what happens, we will always have all the snaps. But this seems not to affect the remote site ...","quoteUsername":"Domcura","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
j
UserLevel 2
徽章 +11
它不是基于时间，它基于要保留多少快照，它说每个间隔...

您对远程站点的恢复要求是多少？

为什么不创建一个时间表并保持局部保留率高于遥控器？
\n
\nWhats your recovery requirement for the remote site?
\n
\nWhy not create one schedule and keep local retention higher than the remote?","quoteUsername":"jasonc","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu