Why a VM after a Migration is bigger than before?

[pcrebe]

Hi,
I'm trying veeam VM migration and after a success the VM's dimension is bigger than before (2Gb more), why?
Is possible, deleting some files in the VM's folder, retur to the original dimension?

Thanks!

[dellock6]

Not sure what do you mean, can you post some screenshots or numbers to understand?

[Vitaliy S.]

Are you referring to virtual disks size?

[pcrebe]

Vitaliy,
my VM was 21Gb with a vmdk file of 19Gb befor migration after 23Gb with a vmdk file always of 19Gb.
Thanks

[foggy]

Carlo, you can browse both source and target folders with datastore browser to see what files make the difference. Though I could assume that you possibly have the source VM turned off and the target VM turned on and the VM has allocated memory of 2GB, which makes the difference.

[pcrebe]

thanks, it was the allocated memory.

[pcrebe]

Hi foggy,
The file is a .wmss file big like memory, so i wrote wrong il last post.
May i delete it?
Now the VM is power off not suspended (i never suspend it), that file (this time) was created after an entire restore from backup and a failback of the running state from his replica because the original VM was deleted for my DR test.

Thanks,
Carlo

[foggy]

Am I understanding you right that in this case you've deleted the source VM, performed a failover to its replica, restored the VM from backup and failed back to it (so we are not talking about Quick Migration here, right?)? And finally you've got this file created in source VM's folder?

[pcrebe]

Yes now isn't a Quik Migration job, but i've that file like in Quik Migration. Anyway the file is the same .wmss file.

Thanks,
Carlo

[foggy]

It is not surprising that .vmss is created during Quick Migration as when SmartSwitch is used, it suspends a VM to move its state file and changes between hosts.
However, during failover/failback operations VM is not suspended, so I can assume that this file was already created at the time you were setting up your replication job and was replicated along with the VM. If you want to investigate this further, please open a case as logs review is required.

[pcrebe]

Naturally you've reason

May i delete the .vmss file to clean the VM directory and retry the test sequence?

Thanks,
Carlo

[foggy]

Yes, I think you can delete it safely.