Nadee Perer
asked on
Creating a FIxed 1TB VHDX drive took 9-10 hours
I have a single Hyper-v host and running two VM's.All the VM's are sitting in local storage
My local storage specs- (Lenovo 600 GB Hard Drive - SAS (12Gb/s SAS) - 3.5" Drive - Internal 15000rpm - Hot Swappable) drive with Raid 5.
My hosting OS Server 2016 running on 128 GB Lenovo Solid State Drive - SATA (SATA/600) - Internal - M.2.
I tried to create a Fixed 1TB VHDX drive and it took me 9-10 hours.
Just wanted to find out is this normal or something to do with my storage.
My local storage specs- (Lenovo 600 GB Hard Drive - SAS (12Gb/s SAS) - 3.5" Drive - Internal 15000rpm - Hot Swappable) drive with Raid 5.
My hosting OS Server 2016 running on 128 GB Lenovo Solid State Drive - SATA (SATA/600) - Internal - M.2.
I tried to create a Fixed 1TB VHDX drive and it took me 9-10 hours.
Just wanted to find out is this normal or something to do with my storage.
It takes a long time as it zeroes out all blocks, but that is slower than normal. What controller do you have, what state is the cache battery and how many disks?
ASKER
Storage Controller Name : ThinkSystem RAID 530-8i
Cacheless (not upgradeable)
4 x 600 GB Hard Drive - SAS (12Gb/s SAS) - 3.5" Drives in Riad 5
server Model:Thinksystem SR530
7X08A03SNA
Cacheless (not upgradeable)
4 x 600 GB Hard Drive - SAS (12Gb/s SAS) - 3.5" Drives in Riad 5
server Model:Thinksystem SR530
7X08A03SNA
RAID 5 without cache so 4 I/Os per write, performance is about the same as a single disk. RAID 10 would be about than twice the speed.
ASKER
In your opinion this is nothing to do with the Raid card specs and the Hard drive specs.
any idea why it took so kind to creat a fixed disk?
any idea why it took so kind to creat a fixed disk?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
For any VHDX larger than 250GB to 300GB we use dynamic VHDX files after creating all of the fixed ones so that the growth of the remaining large one remains contiguous. We would never create 1TB or larger fixed VHDX.
I have two very thorough EE articles on all things Hyper-V:
Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations
I have two very thorough EE articles on all things Hyper-V:
Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations
ASKER
as you mention I did change the VHDX fixed to Dynamic and initiate the file transfer.
I couldn't access VM file server while transferring Data from the old server to my new Hyper-V VM. It took me 5-10 minutes to open file explorer
I couldn't access VM file server while transferring Data from the old server to my new Hyper-V VM. It took me 5-10 minutes to open file explorer