我要关闭NX块以将其移动在另一个站点中。
我停止了地铁的可用性吗？你有程序吗？
谢谢
最好的答案mmcghee
Flavio77<\/a>
\n
\nI'm not sure if we have an official procedure but at a minimum I would disable metro availability. I assume your active protection domains will reside in the block that stays powered on and isn't moved. If your vm availability setting is at automatic, Metro will disable on its own anyway. If it's set to manual, then writes will not proceed if the other cluster is not available, I doubt you'd want that behavior during the move.
\n
\nThe other thing I might do is to take a snapshot of the metro protection domains before doing the disable. The snapshot will be used as a reference point to ensure incremental resync for when you re-enable after the move. The snapshots are taken regularly (depending on your AOS version once every 1 hr or 4 hrs). So if you havnen't had significant changes within the last few hours the manual snapshot won't be necessary.
\n
\nThanks,
\nMike","className":"post__content__best_answer"}">
查看原件
\n
\nI'm not sure if we have an official procedure but at a minimum I would disable metro availability. I assume your active protection domains will reside in the block that stays powered on and isn't moved. If your vm availability setting is at automatic, Metro will disable on its own anyway. If it's set to manual, then writes will not proceed if the other cluster is not available, I doubt you'd want that behavior during the move.
\n
\nThe other thing I might do is to take a snapshot of the metro protection domains before doing the disable. The snapshot will be used as a reference point to ensure incremental resync for when you re-enable after the move. The snapshots are taken regularly (depending on your AOS version once every 1 hr or 4 hrs). So if you havnen't had significant changes within the last few hours the manual snapshot won't be necessary.
\n
\nThanks,
\nMike","className":"post__content__best_answer"}">
