Server Products
Data Center Products including boards, integrated systems, Intel® Xeon® Processors, RAID Storage, and Intel® Xeon® Processors
4778 Discussions

Moving existing array to RMS2AF080

idata
Employee
‎03-12-2013 06:13 AM
1,301 Views

Folks,

I have a currently running server 2008r2 using a S3420GPLX server board. I am using the onboard matrix raid for 5 drives, 4 in raid 10 and 1 non raid. I was looking for information on moving the raid set to an http://www.intel.com/cd/channel/reseller/asmo-na/eng/sales/459246.htm RMS2AF080, 8 port hardware raid "card". Is this a simple migration or much more involved than getting the new raid hardware installed and functioning and moving the cables to the same ports on the new hardware? I ordered a couple of the http://www.intel.com/cd/channel/reseller/asmo-na/eng/sales/459246.htm RMS2AF080 for another project that got shelved. Thought I would try using them instead of collecting dust. Thanks for any input.

Scott

0 Kudos

Link Copied

1 Reply
idata
Employee
‎03-12-2013 08:30 AM
488 Views

Scott,

You have two different RAID manufacturers. The Matrix RAID is Intel software RAID, the RMS2AF080 is LSI based hardware RAID. Because of this, the disk data format (RAID metadata) on the disks is different and it isn't a plug and play migration. Unfortunately you'll have to backup the old and restore to your new RAID if you choose to go that way.

Regards,

John

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.