Since I could not find any information on this, and don't receive any response in other forums as well, I decided to go with Trial and error. - In the worst case I would have lost my VMs, but no data, since the storage pool could be included in the new VMs as well.
Heres the way, how I did it:
- I removed the mirror on the two HDDs, which worked perfect in this case.
- I replaced one Harddisk with one of the new SSDs and started the system again. (The one remaining harddisk was the one including the System-reserved Space)
- I used the Disk Management to create mirros for the System-Reserved Disk as well as for the C-drive (so we now have a mirror between one of the old hdds and one of the new ssds):
- Resyncing the drive to the new SSD (Disk 3) took some time, since the source is the hdd (Disk 4).
- After Resyncing the drive I created a new partition on the SSD and moved all VMs to that one using Hyper-V Migration Manager. (could not resync, since the new disk is smaller and the second partition wouldn't fit)
- After this step, I tried to break the Mirror again, to replace the remaining harddisk with the second SSD.
- But this time, it failed - I dunno way, but i was not able to remove the Mirror within Disk-Management.
- So I decided to simply detach the HDD in a physical way simulating a brokem mirror.
- After a reboot ofc. the mirror was reported broken (disk 4 is now the first ssd and disk3 the second new ssd):
- So all i had to do was:
- Remove the mirror from the first SSD again.
- Create a mirror on the second SSD again.
(Note: I resized the harddisks before doing that, which leads to the fact that the Virtualization-Drive on the first disk is now splitted into two, cause windows cannot move the "startpoint" of the partition - so the end of the partition is now physically ahead the start. This has no Impact on the mirror or the way the disk behaves.):
Using this approach I successfully migrated my Mirrored-hdd-server to a mirrored-ssd-server without haveing to reinstall or reconfigure anything.
Maybe this helps somebody, having the same question.
When cloning the system-reserved partition, you are ofc. cloning the Boot-Order.
Meaning, afterwards the system will not be able to access the primary plex anymore (cause its gone).
You can manually choose the secondary plex during startup, and then use
msconfig.msc to remove the no longer existing primary plex.
The new drives are named
secondary - and
secondary secondary - but who cares about names?