To be able to prepare S/4 1709 installation, we'll have to find the fastest HDD within the VM. Currently the SSDs are being used by S/4 1610, further more, even though S/4 1610's /hana disk was configured as 'thin provisioning', but there was one time that the HANA log files keep growing which fills up the 500GB disks.
Later we've cleaned those log files and configured HANA to run in a non-logging mode, but the already allocated space cannot be reclaimed from VMWare (this is weird, right?), disregarding it's configured as thin provisioning.
So to be able to relase those HDD space, we'll add a third 500GB disk from VMWare, then manually copy those HANA files to the new disk, rename mount point. After that we can delete the old 500GB SSD and ready for 1709 installation.
Old disk in VM "EVO_SSO_1TB_3"
New disk will be created in "WD_STAT_BLACK_4TB_2"

To be able to prepare S/4 1709 installation, we'll have to find the fastest HDD within the VM. Currently the SSDs are being used by S/4 1610, further more, even though S/4 1610's /hana disk was configured as 'thin provisioning', but there was one time that the HANA log files keep growing which fills up the 500GB disks.
Later we've cleaned those log files and configured HANA to run in a non-logging mode, but the already allocated space cannot be reclaimed from VMWare (this is weird, right?), disregarding it's configured as thin provisioning.
So to be able to relase those HDD space, we'll add a third 500GB disk from VMWare, then manually copy those HANA files to the new disk, rename mount point. After that we can delete the old 500GB SSD and ready for 1709 installation.
Old disk in VM "EVO_SSO_1TB_3"
New disk will be created in "WD_STAT_BLACK_4TB_2"
