ML380 G9 - Migrate OS from mirror mechanical array, to single SSD array and then mirror it

[NULUSIOS]

This is the partial scenario, it has some more steps, but if this part works, then the rest is simple.

So I have an old ML380 G9, that its disks show their age.
(in fact I just got a refurbished replacement to make one array healthy - until this project finishes)

It is a Windows Server 2016 with a few VMs.
It uses the stock RAID controller (P440ar) and has just one disk slot empty.
Yes it is getting backed up (rather slowly).

So my (partial) plan is this:
1- Get two big SAS SSD.
2- Put one of them in the empty slot.
3- Make a new array with it.
4- Perform "move logical drive" from my OS array (a mirror) to this single disk.
5- Remove the two old disks.
6- Add the second SAS SSD.
7- Migrate the single disk array to a mirror with the second disk added.
8- "Grow" the usable volume.
9- (other similar steps to second non-OS array, but no point repeating)
10- Shut down server and move the new healthy array disks in the slots I want them.

a) Will this work? (especially step #4 and maybe step #7)
According to P440ar specs, it can perform both array move and migrate RAID level.
But I need to verify as much as I can that I can actually DO (again: esp. step #4 which is half the problem)

b) From inside the OS (using Array Configuration) or should I do this in the pre-boot environment?

So if this is a working scenario, how do I actually do it? Again, talking ESPECIALLY for #4.

[NULUSIOS]

I think I can answer "b" myself. At least step "move logical drive" CANNOT be done for the OS from inside OS, since it makes the drive unavailable for the duration of the procedure.

But the remaining questions remain.

[NULUSIOS]

Can someone help please?

[Sham82]

Hello, 
We would recommend to :

1. Take a valid Back-up.
2. Delete existing Array.
3. replace drives with SSD.
4. Create Same array again using SSD's.
5. restore from back up.

Regards
HPE

[NULUSIOS]

Thank you for your reply.

This is the way to do it in any system, server or not.

But means server down-time and UNDER-utilizes the advertized capabilities of the controller.

The controller supposedly can migrate RAID levels and supposedly is able to move logical drives between arrays.

So the question is, aside from your suggestion (and of course aside from having a good backup), can my scenario work as I list it in my initial post?

[Sham82]

Hello,

HPE Still recommends as mentioned earlier.
However you can try using the below User guide:
Page 32 Onwards - https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=dp00002639en_us

install Latest :Smart Storage Administrator 
https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_891c6d6803044e5db3e0c2a5ab&tab=revisionHistory

NOTE : Disclaimer : Data integrity is customer responsibility. HPE recommends to have data backup frequently and before performing any activity so that it can be restored during disaster recovery.

Regards
HPE

[NULUSIOS]

I have read about the process already.

BUT:

1) I don't understand how in your link SSA 4.21..7 is mentioned as "latest" when I already have SSA 6.25.9 and sees my controller fine...

2) I don't see the option to move the logical drive. Although I have set a new array (with a single SSD for now) that can be used (size is larger than old array with the source logical drive).
Why?

Can it be because it is the OS drive and the system protects us from killing our own system?

3) If that is the case, will the option work in a pre-boot environment?

Thank you.

[NULUSIOS]

OK issue is updated, NOT RESOLVED, but new data:

1) Pre-boot environment SSA does not see my controller as it says "a logical drive is configured with a new version of SSA".
This is NOT the SSD drive I added, because this comes up even when I remove it.

2) I managed to resolve #1, above using a newer provision DVD in the pre-boot environment. Although I don't know how to put this SSA that is working in my firmware.

3) I took Windows Server Backup, bare metal backup and tried to restore to my SSD array. Recovery environment did see my SSD array, but failed, causing that I didn't have the proper drive to recover to.
Old mechanical array is 2 x 300GB RAID1. New SSD array is single disk (temporarily) 1.9TB (1.7TB usable).
*** So you suggested method fails. ***

4) Move logical volume doesn't exist for P440ar controller (even after disabling cache as I found in the documentation). So I cannot migrate to the SSD using that method either.

Any ideas on how to be able to do a seemingly simple thing of mirroring my existing OS array to new SSD?

Thank you in advance.

[Sham82]

Hello,
please add both SSD's and then try "move Operation"
as equal number of drives would be needed to perform " Move operation".

Regards
HPE

[NULUSIOS]

This is very strange as the single disk has the size to fit the volume.
Also it would make sense to need the same number of disks in case of RAID0 or RAID5... but for RAID1 (mirror)???

The problem to try this proposal, is to FIT the disks. I have just one slot empty!
(removing the old mechanical disks will allow me to fit the second disk and make it a RAID1)

You think I can break the mechanical mirror array, so that I can stay in a single disk AND perform the move volume?
(I am trying to find scenarios to try next weekend - please)

[Sham82]

Hello,

as suggested earlier.

The new array must be created with equal number of drives.

Else Best would be :

1. Take a valid Back-up.
2. Delete existing Array.
3. replace drives with SSD.
4. Create Same array again using SSD's.
5. restore from back up.

Regards
HPE

[NULUSIOS]

I had a valid backup and will get a valid backup again.

I cannot create same array with SSD because the SSD are larger. Won't this be an issue?
Bare-metal backup seemed to ignore my SSD (although it was there when selecting drives to ignore - I didn't ignore it).

I am planning to do this:
1) Break the mirror (as SSA allows for that) and keep the second disk as (extra) backup. Now the array is single disk.
2) Insert an SSD and make it a single disk array.
3) See if this allows for "move logical volume".
4) If it doesn't allow that, get new backup of the SINGLE disk OS.
5) See if Windows Server Backup now sees the SSD as a valid destination for restore.

...all these are way more complex than they needed to be.
I will also try ghost or acronis, if the arrays can be seen by them.

This is definitely NOT great. A server is supposedly something that HELPS you do things, not make your life difficult.

[Sham82]

Hello,
You can try this.
Make sure to take backup before performing the activity

Regards

HPE

[NULUSIOS · Accepted solution]

Here is what I did eventually:

1) Took one more backup.
2) Deployed an offline (from bootable DVD) Acronis tool, not knowing if it will be able to see my arrays (but bet that EFI drivers would help).
3) Indeed it saw both my original array AND my single disk SSD array.
4) Cloned AND resized!
5) Removed disks of original mirror (not removing the array from SSA yet).
6) System did not boot. I thought it would be an issue of assigning active boot array in SSA.
7) Booted SSA from DVD (as my firmware SSA is old and doesn't see the configuration).
9) I selected the new single SSD array as boot.
10) System BOOTED and at the same time had already grown my OS partition to full SSD size (which I broke down again in two partitions for my own backup management reasons).
11) Shut down, fully physically removed my original OS array disks, reseat my SSD in the slot I wanted (slot 1), added the second SSD in slot 2.
12) Entered DVD SSA again.
13) Removed missing (old) array from configuration. Added second disk in my new SSD array and set it as mirror. Mirror started building.
14) System booted again. Not as fast as expected yet as RAID controller has temporarily killed cache to build the mirror.

Right now mirror is finishing up and I am already doing various file re-arrangements.
So everything ok WITH the help of 3rd party software AND server going offline more times than it should.
At least I can mark this as closed now.

[Sunitha_Mod]

Hello @NULUSIOS,

That's great!

We are glad to know the problem has been resolved and we appreciate you for keeping us posted.