Extending a LUN that is using MirrorView requires you to remove the MV from the LUN. Because metaLUN allows to control the total capacity and user capacity of a LUN separately, when the replication relationship exists, the total capacity is allowed to increase, but the user capacity will not increase immediately until the MV is removed from the LUN.
Take an example of concatenation expansion. When the base LUN is being expanded, a component LUN is added to create a meta LUN. At this time, the total capacity is increased, but the extra space has not yet become a new user capacity. Of course, you can complete the striped expansion process first, and then remove the MV.
Amazingly , increasing the user capacity of a MetaLUN is an almost instantaneous process. Because the real space has just been added, it is only necessary to modify the attribute value of a user capacity on the LUN. And once the user capacity is increased, the MV can be recreated immediately. This can minimize the impact on the normal use of the system.
It is worth noting that before rebuilding, the user capacity of the mirrored LUN in the remote storage should also be extended to the same user capacity as the mirrored LUN.
In addition, if the I/O on the primary LUN is not completely stopped before the MV is released, remember to resynchronize later, otherwise it is not necessary. Here is a reference step for you: Execute at non-script runtime
1. Stop I/O on the primary LUN, remove the LUN from the storage group.
2. Make sure that the mirror LUN is in the synchronized state. For MV/S, after stopping I/O, wait for the mirror to become synchronized. For MV/A, after stopping the I/O, perform an update manually. The above two steps are the same as promoting a mirrored LUN.
liulei_it
3.2K 消息
0
2013年8月20日 04:00
偶用的symmetrix 做BCV就不用管这些。偶估计对您这个系列的还是需要有影响的
Password01_
416 消息
0
2013年8月20日 06:00
如果你做Lun expand，那么源LUN的容量就会发生变化，那么clone的目的LUN也需要做调整。建议还是将这些计划任务停掉。配置完成后，再重新启动任务。因为LUN ID没有发生变化，我认为expand完成后，再启动计划任务即可。
born_chen
1.8K 消息
1
2013年8月20日 09:00
我觉得应该暂停，或者删除任务，做完之后再重新配置。
参考附件。
1个附件
metaLUN Detailed Review.pdf
Roger_Wu
4K 消息
0
2013年8月20日 18:00
参考EMC MirrorView Knowledge Book: http://www.emc.com/collateral/hardware/white-papers/h2417-mirrorview-know-cx-series-flare-wp-ldv.pdf
所以MirrorView、SnapView之类的都要删了重配哦。
zhouzengchao
1.4K 消息
0
2013年8月20日 18:00
Hi yanzs,
Expansion可以做，但是过程中会提醒你新添加的空间（即你选择作为component LUN的那个LUN）暂时不能被使用，因为源LUN正在被另一个feature (clone, snapshot, mirrorview) 使用。所以你需要先撤掉所有这些feature之后，才能使用新添加的空间。撤掉的feature自然就需要重新配置了。
o17Uu33DCF12520
1.1K 消息
0
2013年8月20日 19:00
flare lun可以用过expansion的方式创建成meta lun，这样原来的flarelun就变成component lun。component lun是不能被用于snapshot、mirrorview、clone等功能的。所以，恐怕。。。
yanzs
913 消息
0
2013年8月21日 01:00
嗨，kevin，你的意思是说metalun不能做snapshot、mirrorview、clone吗？还是说一切相关配置要推倒重建，谢谢！！
o17Uu33DCF12520
1.1K 消息
1
2013年8月21日 03:00
Hi yanzs
Extending a LUN that is using MirrorView requires you to remove the MV from the LUN. Because metaLUN allows to control the total capacity and user capacity of a LUN separately, when the replication relationship exists, the total capacity is allowed to increase, but the user capacity will not increase immediately until the MV is removed from the LUN.
Take an example of concatenation expansion. When the base LUN is being expanded, a component LUN is added to create a meta LUN. At this time, the total capacity is increased, but the extra space has not yet become a new user capacity. Of course, you can complete the striped expansion process first, and then remove the MV.
Amazingly , increasing the user capacity of a MetaLUN is an almost instantaneous process. Because the real space has just been added, it is only necessary to modify the attribute value of a user capacity on the LUN. And once the user capacity is increased, the MV can be recreated immediately. This can minimize the impact on the normal use of the system.
It is worth noting that before rebuilding, the user capacity of the mirrored LUN in the remote storage should also be extended to the same user capacity as the mirrored LUN.
In addition, if the I/O on the primary LUN is not completely stopped before the MV is released, remember to resynchronize later, otherwise it is not necessary.
Here is a reference step for you: Execute at non-script runtime
1. Stop I/O on the primary LUN, remove the LUN from the storage group.
2. Make sure that the mirror LUN is in the synchronized state. For MV/S, after stopping I/O, wait for the mirror to become synchronized. For MV/A, after stopping the I/O, perform an update manually.
The above two steps are the same as promoting a mirrored LUN.
3. Refer to this document below: http://support.emc.com/kb/17016
CC12
93 消息
0
2013年8月21日 08:00
我记得以前听一个神码的工程师说是要删除之后重新配置的。