BIN file, which will always equal the amount of RAM that is being consumed by the VM. Now I know you are asking yourselves why is there a difference between a VM that is off and a VM that is turned on? The answer lies in the Hyper-V. However, this is only true if the VM is off. There are currently no snapshots (checkpoints) created for it, so you can assume this VM will consume approximately 99GB of space. It’s running on a standalone Hyper-V Host and has a single, fixed 99 GB VHDx. It’s a lot easier to manage Hyper-V VMs if they are stored in a single, consistent location.ĭigging in a bit deeper, what you are looking at in the image above is a VM called TC-HQ-VEEAM01. Note: Although when creating a VM these locations can be split up into different locations it is not my best practice. When a VM is created, it has some core components that are required for it to start in Hyper-V: So, are you ready? Then let’s get started with the most basic concept of a Hyper-V Host and some basic storage to place the virtual machines as seen in the illustration below. BIN files and their impact on your environment. As this is a big topic, I’m going to limit the scope of this post to the management of Hyper-V. Hey Veeam fans, today we are back with another blog post! This time, let’s have a look at some basics of Hyper-V Storage management.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |