As space is freed up on the member (for instance, a volume is deleted or bound to another member), any slices of the bound volume that were moved off of the bind member, will move back to the member assigned to the bind.
�
You are first say that the array will do the moving around by itself, and I understand this as the opposite?
Yes, the bind will have a higher preference. When the member is low on space to hold the bound volume(s), the firmware will still honor the Volume bind, and first move unbound volume slices to another member(s) in the same pool to free up space, or (second) move bound volume slices to another member(s) if there are no unbound volume slices to move.
As space is freed up on the member (for instance, a volume is deleted or bound to another member), any slices of the bound volume that were moved off of the bind member, will move back to the member assigned to the bind.
Be aware that binding a volume can take time to move to the assigned member, depending on the volume size, number of volumes you are binding, etc.
This was just an example. If you have a member with 3 bound volumes, and 2 unbound volumes on it, and the member becomes low on space, unbound volume slices will be moved to another member first. This example just states that if all the unbound volume slices are moved and you still do not have enough free space on the member, then bound slices will be moved to another member in the pool. If you then decide to unbind a volume, or delete one of the volumes, any bound volume slices on the other member are moved back to the member assigned to the bind.
Joe S586
7 Technologist
•
729 Posts
0
October 21st, 2013 06:00
Once you setup the volume binding, the operations discussed are done in the background automatically.
-joe
jensendk
13 Posts
0
October 17th, 2013 07:00
Hi
I don't understand this one:
As space is freed up on the member (for instance, a volume is deleted or bound to another member), any slices of the bound volume that were moved off of the bind member, will move back to the member assigned to the bind.
�
You are first say that the array will do the moving around by itself, and I understand this as the opposite?
Joe S586
7 Technologist
•
729 Posts
0
October 17th, 2013 07:00
Yes, the bind will have a higher preference. When the member is low on space to hold the bound volume(s), the firmware will still honor the Volume bind, and first move unbound volume slices to another member(s) in the same pool to free up space, or (second) move bound volume slices to another member(s) if there are no unbound volume slices to move.
As space is freed up on the member (for instance, a volume is deleted or bound to another member), any slices of the bound volume that were moved off of the bind member, will move back to the member assigned to the bind.
Be aware that binding a volume can take time to move to the assigned member, depending on the volume size, number of volumes you are binding, etc.
-joe
Joe S586
7 Technologist
•
729 Posts
0
October 17th, 2013 08:00
This was just an example. If you have a member with 3 bound volumes, and 2 unbound volumes on it, and the member becomes low on space, unbound volume slices will be moved to another member first. This example just states that if all the unbound volume slices are moved and you still do not have enough free space on the member, then bound slices will be moved to another member in the pool. If you then decide to unbind a volume, or delete one of the volumes, any bound volume slices on the other member are moved back to the member assigned to the bind.
-joe
jensendk
13 Posts
0
October 21st, 2013 03:00
Hi
Okay, thanks for you aswher.
Just to make it clear, all this is happen automatic?
Regards Kenneth Dalbjerg
jensendk
13 Posts
0
October 23rd, 2013 02:00
Hi
Great thank you for yours reply.
Regards Kenneth Dalbjerg
jensendk
13 Posts
0
October 29th, 2013 14:00
Do you know if it posible to bind a volume to tow Equallogic boxes?