Hello,   You have it correct.  Single members in their own pool, don't share data so only volumes on the failed member will be impacted.   When you move the 4100 would be a good time to upgrade the firmware on the array, and check to see if the drive firmware needs upgrading as well.  There's a new drive firmware kit, v9 available on the website.  You will also need to upgrade the 6210 to match of course.  6210's need to be running 7.1.9 or 8.1.1 to avoid a possible cache sync issue.  So the 4100 will need to have the same firmware.  Regards,   Don 
We currently have a group with one storage pool ("default") and two members: -PS4100, NL-SAS 7200rpm in RAID 10 (smallest member) -PS6210, SAS 10.000rpm in RAID 50 (largest member) I would like to convert both members to RAID 6 (to gain some space and increase RAID reliability) while at the same time split the members so they operate independently so the volumes are no longer 'striped' over both members. In case one of the members fails I would like to make sure the volumes on the remaining member stay on-line and accessible. I have enough free space in the group to remove the smallest member and move all the volumes to the largest member during the migration process. My idea is to: -create a new pool and move the smallest member to this pool (this should move all volumes to the largest member). -change the RAID level on the smallest member (at this time all volumes should have been evacuated from this member by the pool move action) -move some volumes back from the largest member to the the smallest member / the new pool) -change the RAID level on the largest member Will this work and will this leave the volumes completely independent on each of the members, or do I need to split the members into their own groups to create complete independency?
Re-arranging our group