Anyone have a clue on how the data is specifically laid out- algorithm? It seems parity is on each drive, but not sure if in groups or data-parity-data, etc.

_________________
"A problem is only an opportunity in work clothes"
Www.sandiegorecovery.com

This will have the typical delayed parity you see with all smart array controllers. Try with a delay of 2 first.

How many drives?
I agree with phishin_ca, most probably you'll have delayed parity like all HP servers.

Delay in HP always will be higher than 2...



Data and parity is written as in standard RAID5, except parity is written to the same disk for a set number of stripes - this is the delay.

For information, WinHex can handle delay for HP RAIDs...

_________________
Lemmy

I usually use R-Studio and create a custom block layout to deal with these.

Both fits for the same goal, euth a rewind differences between them.
Winhex is much better for analysis and r-studio is better for rebuilding.

I am just partial to the WinHex way. With a larger array you have to do a lot more work in RStudio. Once I have the volume snapshot in WinHex, I feel no reason to leave

Personally I always use both. Winhex is great for analysis of disks, has a great option to synchronise multiple windows while R-Studio has a nice interface, many useful features and is easily configured.

But then again, I do not think any engineer working on RAID arrays will limit themselves to 1 or even 2 software titles.

Totally right, a good DR engineer will adapt itself to any app.