You mean on the same physical MD3000i ?

The RAID groups virtual disks are controlled by either the controller in slot 0 or 1. The controllers don't control individual drives, only the groups. Make sense ? This picture should help --> http://www.delltechcenter.com/page/MD3000i+Pref+Owner

You can export the group and import the group onto a different MD3000i, or the same MD3000i if you needed to move drives across MD1000's for enclosure redundancy and that was something you didn't do in the original config. It's under "support" .. "Advanced Support Tasks"

Does this answer the question ? Or maybe explain more of what you're trying to accomplish.

Thanks Scott. My concern is I hae e7 drives all in slotes 0-6. If I lose RAID card 0 do I lose those drives or will RAID card 1 be able to access those drives?

thanks

Both RAID controllers on the MD3000i can access all disks in the enclosure. But only one can "own" them at any given time. If you have a controller failure, the other one picks up.

If you create the LUNs automatically on the controller you'll see that it automatically assigns the owner in a balanced fashion.

No need to worry about where the drives are. Don't overthink it :-)

"You mean on the same physical MD3000i ?

The RAID groups virtual disks are controlled by either the controller in slot 0 or 1. The controllers don't control individual drives, only the groups. Make sense ? This picture should help --> http://www.delltechcenter.com/page/MD3000i+Pref+Owner

You can export the group and import the group onto a different MD3000i, or the same MD3000i if you needed to move drives across MD1000's for enclosure redundancy and that was something you didn't do in the original config. It's under "support" .. "Advanced Support Tasks"

Does this answer the question ? Or maybe explain more of what you're trying to accomplish."

Any additional documentation on the export / import?
We have been using MD1000's to create enclosure protection. As of the gen 2 firmware, it has been causing loss of the disk group(s) on the MD3000i when we move it. This worked OK for us before the gen 2 FW, but I suppose the export / import would be a much better way to do it. I hate that it hoses the disk groups on the MD3000i, Not a big deal because you can run on the VD copies on the MD1000 until you can get them copied.

Define "move it"

"Define "move it""

This was addressed on a more dedicated thread.

We use our MD1000's for in essence san to san copy for redundant MD3000i's...

The import / export is pretty darn cool as you no longer need to down either MD3000i....