VM size different after moving to new Hyper-V cluster

Marcus Wong Theen Nam 1,141

We are doing a hyper-v cluster VM migration to new hyper-v cluster and the environment is as below:

cluster A (2 nodes) - Windows Server 2012 R2 nodes
cluster B (2 nodes) - Windows Server 2019 nodes

We've moved 1 VM role from the Windows Server 2012 R2 Hyper-V node to Windows Server 2019 Hyper-V node. Initially the source VM size in WS2012R2 hyper-v node is about 50GB, but after moving to the WS2019 hyper-v node the size became 70GB something. The VM is running fine but just the size was increased.

Appreciate for assistance/explanation on why the migrated size was increased.

JiayaoZhu 3,911 Reputation points

2021-07-15T06:33:41.52+00:00

Hi,

I would like to check if the reply could be of help? If yes, please help accept answer, so that others meet a similar issue can find useful information quickly. If you have any other concerns or questions, please feel free to feedback.

Best Regards,
Joan

1 answer

JiayaoZhu 3,911 Reputation points

2021-07-14T09:08:46.04+00:00

Hi,

Thanks for posting on our forum!

Based on your description, I would like to firstly check how and where you observed that your VM size has increased by 20GB? And when you refer to VM size, you indicate VM OS file size or VM vhd size?

If possible, would you please show us the screenshot for the console that depicts the increased VM size?

Thanks for your support!

BR,
Joan

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Marcus Wong Theen Nam 1,141 Reputation points

2021-07-19T08:36:37.607+00:00

Hi,

We check the size by viewing the entire folder of that VM.

JiayaoZhu 3,911 Reputation points

2021-07-20T06:47:34.063+00:00

Hi,

Thanks for your reply!

So, from which platform did you check your VM size? from Hyper-V Manager or from failover cluster manager, performance monitor or Windows Admin Center?

Thanks for your support!

BR,
Joan

Marcus Wong Theen Nam 1,141 Reputation points

2021-07-22T01:44:14.77+00:00

From Hyper-V node we access to the VM folder and look at the size from properties.

JiayaoZhu 3,911 Reputation points

2021-07-27T03:12:34.233+00:00

Hi,

Thanks for your patience!

After a long-time research and test, there may be two reasons for explaining for your issue. For one thing, I think you can just click into your VM folder to see if there are any new system folders produced through your live migration. For another, go to check your VM's VHD size, since you applied live migration, your VM was still running during the process. In other words, your VM was normally produce data as usual during the migration, which increased your VHD size.

Thanks for your support!

BR,
Joan

Marcus Wong Theen Nam 1,141 Reputation points

2021-07-30T08:31:46.11+00:00

Hi Joan,

We are using cold migration for the VM, so is there any other possibilities that causing the difference of size? And for system folders yes, it has but some folders size were increased and some were decreased.

Thank you.

JiayaoZhu 3,911 Reputation points

2021-08-02T01:54:21.133+00:00

Hi,

If you used cold migration rather than live migration, your vhd size should remain the same as previously. So if possible, you can tell me which kind of folders increased in size. In terms of the decreased one, you probably used deduplication feature by default, which can help you clear any duplicated files. Above all, you can pay more attention to the folders that became bigger after migration.

Thanks for your support!

BR,
Joan
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

VM size different after moving to new Hyper-V cluster

1 answer

Your answer