Here is what I have:
A MS Exchange 2013 (Windows 2008R2) VM currently running off antiquated slow SAN storage. The VM is stored on 1 LUN/1Volume as two separate hard drives. (C: = 120GB | D: = 800GB)
My intention is to move This VM to our new storage system which has a pool of SSDs and a Pool of Mechanical Drives. I would like to put the operating system drive (C: = 120GB) on the SSD’s and the database storage drive (D: = 800GB) on the Mechanical Drives. So basically, I am wanting to split the drives from one storage pool to two on a new appliance.
I am running backups via Veeam application aware backups daily on this device.
I have been currently moving all our other VM’s to this new storage simply by migrating the VM’s, but this one is different, I need to split the drives between two separate pools and have the VM be unaware of this.
Does anybody know a good “best practice” for this type of move? I had to build this VM several months ago from scratch when a bare metal server failed running the device, I really do not want to go through that again.
Thank You for your replies in advance.
You must be logged in to reply to this topic.
Create a free account today to participate in forum conversations, comment on posts and more.