May 19th, 2010 14:00


Unfortunately, no. You can't go backwards live. If you can borrow / rent an array to add to that group, you can evacuate that member, which will move the data to the loaner. that member will then be reset and you can add it back in at the new RAID level. Delete the loaner from the group and you're all set.

Otherwise you'd have to back everything up, reset the array and build it back up again.

There's is a "save-config" command at the CLI. This will store all the configuration information, volumes, ACLs, etc. ftp the file off and save it locally. Then all you'd need do is reset the array. Restore the configuration, then restore the data.

-don

4 Posts

May 20th, 2010 07:00

thank you very much...

May 20th, 2010 08:00

You are very welcome!

Hopefully, you can get a loaner to make the process easy.

-don

4 Posts

May 20th, 2010 09:00

I may have one, called one of our consultants we use, and they have a ps4000

May 20th, 2010 12:00

Fantastic! What's the firmware revision on the PS100? You'll need to be at 4.1.x or better to work with the PS4000.

Are you clear on the procedure? Make sure you enable both ports on the PS4000 before doing the migration.

-don

4 Posts

May 22nd, 2010 08:00

I'm at 3.3.2 on the ps100. And my vendor says it the ps5000 he can let me use.

May 22nd, 2010 14:00

Please check what version of firmware the PS5000 is. It could be 4.1.x or greater which you can't add to your 3.3.2 group. Upgrading would be a good idea as a best practice.

From 3.3.2, you first go to 4.0.7, then 4.1.7, then 4.3.5 to get to the current release. You'll need to restart the array after each upgrade. The 3.3.2->4.0.7 will be the longest restart. You might want to consider taking an outage. Once at 4.x, the array upgrade process leverages controller failover to shorten the downtime.

If you unsure of any of anything. Please don't hesitate to open a case with Dell.

-don
No Events found!

Top