Vmrs файл hyper v что это
We plan to use hyper v (on Windows Srv 2016) guests to run SSAS tabular model DBs with lots of memory but the VMRS file for the guest with big memory allocated becomes a storage problem: it grows as the memory grows. We are testing this on a hyper v cluster; we calculated storage for DW (from which SSAS reads). But the VMRS files for guests keeps getting bigger. Assuming to utilize ~700 GB of memory we will need 700+GB of disk space and i could not find it mentioned on Windows Server 2016 docs (neither in hyper v or planning sections). Dynamic or static memory does not effect the problem; you have to tax your storage with the amount of memory you provide to the guest.
The question is: is there a way to safely disable VMRS file for hyper v guests in Windows Server 2016; i do not want to allocate disk space for the memory i provide to the guest.
What happens if I don't upgrade the virtual machine configuration version?
If you have virtual machines that you created with an earlier version of Hyper-V, some features that are available on the newer host OS may not work with those virtual machines until you update the configuration version.
As a general guidance, we recommend updating the configuration version once you have successfully upgraded the virtualization hosts to a newer version of Windows and feel confident that you do not need to roll back. When you are using the cluster OS rolling upgrade feature, this would typically be after updating the cluster functional level. This way, you will benefit from new features and internal changes and optimizations as well.
Once the VM configuration version is updated, the VM won't be able to start on hosts that do not support the updated configuration version.
The following table shows the minimum virtual machine configuration version required to use some Hyper-V features.
Feature | Minimum VM configuration version |
---|---|
Allow additional processor features for Perfmon | 9.0 |
Automatically expose simultaneous multithreading configuration for VMs running on hosts using the Core Scheduler | 9.0 |
Hibernation support | 9.0 |
Increase the default maximum number for virtual devices to 64 per device (e.g. networking and assigned devices) | 8.3 |
Guest Virtualization-Based Security support (VBS) | 8.0 |
Key storage drive | 8.0 |
Large memory VMs | 8.0 |
Nested Virtualization | 8.0 |
Virtual processor count | 8.0 |
XSAVE support | 8.0 |
Virtual Machine Multi Queues (VMMQ) | 7.1 |
Virtual Trusted Platform Module (vTPM) | 7.0 |
Hot Add/Remove Memory | 6.2 |
PowerShell Direct | 6.2 |
Production Checkpoints | 6.2 |
Secure Boot for Linux VMs | 6.2 |
Virtual Machine Grouping | 6.2 |
For more information about these features, see What's new in Hyper-V on Windows Server.
We plan to use hyper v (on Windows Srv 2016) guests to run SSAS tabular model DBs with lots of memory but the VMRS file for the guest with big memory allocated becomes a storage problem: it grows as the memory grows. We are testing this on a hyper v cluster; we calculated storage for DW (from which SSAS reads). But the VMRS files for guests keeps getting bigger. Assuming to utilize ~700 GB of memory we will need 700+GB of disk space and i could not find it mentioned on Windows Server 2016 docs (neither in hyper v or planning sections). Dynamic or static memory does not effect the problem; you have to tax your storage with the amount of memory you provide to the guest.
The question is: is there a way to safely disable VMRS file for hyper v guests in Windows Server 2016; i do not want to allocate disk space for the memory i provide to the guest.
Answers
The question is: is there a way to safely disable VMRS file for hyper v guests in Windows Server 2016; i do not want to allocate disk space for the memory i provide to the guest.
I think you misinterpreted the answer provided by TheOnlyWizard, because the answer is 'yes'. Configure your VMs to not save state upon host shutdown. That configuration will not allocate any disk space for memory provided to the guest.
- Edited by Tim Cerling MVP Thursday, February 16, 2017 1:35 PM
- Marked as answer by AhmetKuru Monday, February 20, 2017 9:00 AM
Step 2: Upgrade the virtual machine configuration version
- Shut down the virtual machine in Hyper-V Manager.
- Select Action > Upgrade Configuration Version. If this option isn't available for the virtual machine, then it's already at the highest configuration version supported by the Hyper-V host.
To upgrade the virtual machine configuration version by using Windows PowerShell, use the Update-VMVersion cmdlet. Run the following command where vmname is the name of the virtual machine.
Supported VM configuration versions for long-term servicing hosts
The following table lists the VM configuration versions for hosts running a long-term servicing version of Windows.
Hyper-V host Windows version | 10.0 | 9.3 | 9.2 | 9.1 | 9.0 | 8.3 | 8.2 | 8.1 | 8.0 | 7.1 | 7.0 | 6.2 | 5.0 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows Server 2022 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✖ | ✖ | ✖ |
Windows 10 Enterprise LTSC 2021 | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✖ | ✖ | ✖ |
Windows Server 2019 | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows 10 Enterprise LTSC 2019 | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows Server 2016 | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows 10 Enterprise 2016 LTSB | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows 10 Enterprise 2015 LTSB | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ |
Windows Server 2012 R2 | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✔ |
Windows 8.1 | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✔ |
Ответы
The question is: is there a way to safely disable VMRS file for hyper v guests in Windows Server 2016; i do not want to allocate disk space for the memory i provide to the guest.
I think you misinterpreted the answer provided by TheOnlyWizard, because the answer is 'yes'. Configure your VMs to not save state upon host shutdown. That configuration will not allocate any disk space for memory provided to the guest.
- Изменено Tim Cerling MVP 16 февраля 2017 г. 13:35
- Помечено в качестве ответа AhmetKuru 20 февраля 2017 г. 9:00
Step 1: Check the virtual machine configuration versions
- On the Windows desktop, click the Start button and type any part of the name Windows PowerShell.
- Right-click Windows PowerShell and select Run as Administrator.
- Use the Get-VMcmdlet. Run the following command to get the versions of your virtual machines.
You can also see the configuration version in Hyper-V Manager by selecting the virtual machine and looking at the Summary tab.
Supported VM configuration versions for Semi-Annual Channel hosts
The following table lists the VM configuration versions for hosts running a Semi-Annual Channel version of Windows. To get more information on Semi-Annual Channel versions of Windows, visit the following pages for Windows Server and Windows.
Hyper-V host Windows version | 10.0 | 9.3 | 9.2 | 9.1 | 9.0 | 8.3 | 8.2 | 8.1 | 8.0 | 7.1 | 7.0 | 6.2 | 5.0 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows 11 (version 21H2) | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✖ | ✖ | ✖ |
Windows 10 November 2021 Update (version 21H2) | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✖ | ✖ | ✖ |
Windows 10 May 2021 Update (version 21H1) | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✖ | ✖ | ✖ |
Windows Server, version 20H2 | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✖ | ✖ | ✖ |
Windows 10 October 2020 Update (version 20H2) | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✖ | ✖ | ✖ |
Windows Server, version 2004 | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✖ | ✖ | ✖ |
Windows 10 May 2020 Update (version 2004) | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✖ | ✖ | ✖ | ✖ |
Windows Server, version 1909 | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows 10 November 2019 Update (version 1909) | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows Server, version 1903 | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows 10 May 2019 Update (version 1903) | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows Server, version 1809 | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows 10 October 2018 Update (version 1809) | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows Server, version 1803 | ✖ | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows 10 April 2018 Update (version 1803) | ✖ | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows 10 Fall Creators Update (version 1709) | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows 10 Creators Update (version 1703) | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Windows 10 Anniversary Update (version 1607) | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✔ | ✔ | ✔ | ✔ | ✔ |
Answers
The question is: is there a way to safely disable VMRS file for hyper v guests in Windows Server 2016; i do not want to allocate disk space for the memory i provide to the guest.
I think you misinterpreted the answer provided by TheOnlyWizard, because the answer is 'yes'. Configure your VMs to not save state upon host shutdown. That configuration will not allocate any disk space for memory provided to the guest.
- Edited by Tim Cerling MVP Thursday, February 16, 2017 1:35 PM
- Marked as answer by AhmetKuru Monday, February 20, 2017 9:00 AM
All replies
As far as I understand Hyper-V, 2012R2 .BIN files and 2016 VMRS-files are sparse-files, meaning they don''t take up any actual storage unless utilized. (Utilized meaning: You save the VM for example).
not sure about 2012R2 but in 2016 it seems to "eat" disk while running:
this is the VMRS file for selected VM:
this is the VM; running:
For 1.5 TB memory on 2 clustered hosts, i need arrange 1.5 TB on SAN storage which i do not want..
As I said, the space doesn't actually get taken up, unless you save the VM. So, to be able to keep a working VM in case something goes terribly wrong, you DO need to take that space being actually allocated into account from the start. If that's not what you want, well, that's how Hyper-V does it's thing. You're only option then would be to look for a different Hypervisor which does things differently (VMWare for example, although with that you get swapdisk-space to take into account).
You can set the clustered VM to shutdown instead of saving it, and you can NOT ever save the VM yourself but shut it down instead, and you can make sure to never use a "Quick migration" (which would save the VM) to prevent that space from ever getting allocated, but then still. In case the cluster somehow decides to go save the VM nevertheless, the space will get allocated, for the amount of the actual current Memory Demand + a little overhead.
Simply put: If your VM uses 700 Gbytes of Memory, even you have set it at 1.5 Tbytes of Memory total, then saving the VM would give you a VMRS-file of a little over 700 Gbytes. From VM start until save, the file gets created at start, but does NOT actually get allocated. It will roughly show the size of the current Memory Demand, not the amount of memory set. So if your VM starts using less, say you stop all the DBs inside the VM, your memory demand drops, and so would the size of this file. You can test that if you literally do that. Give the VM 700 Gbytes of mem. start it up, see the VMRS-file being created for 700 Gbytes. Then, stop the DBs, make the VM just use a little, say, 2Gbytes of mem., then save the VM. You'll see that when the save is done, the VMRS-file all of a sudden will be around 2Gbytes in size. Then, when you restore the VM, it will show to be 700 Gbytes again all of a sudden (But in reality on the storage, only 2 Gbytes is actually allocated so far).
Thanks for the detailed information, wish these were mentioned in the docs.
Would be nice to have the option though: not saving a VM (and be able to just live migrate) if VM fails just stop/start. Could be useful for read-heavy work loads.
Anyhow, if anyone from product team reads along please update the docs first, consider this option also.
You could post feedback to the following site. Microsoft engineering teams would monitor the feedbacks and may improve the products.
Make the latest Hyper-V features available on your virtual machines by upgrading the configuration version. Don't do this until:
- You upgrade your Hyper-V hosts to the latest version of Windows or Windows Server.
- You upgrade the cluster functional level.
- You're sure that you won't need to move the virtual machine back to a Hyper-V host that runs a previous version of Windows or Windows Server.
Все ответы
As far as I understand Hyper-V, 2012R2 .BIN files and 2016 VMRS-files are sparse-files, meaning they don''t take up any actual storage unless utilized. (Utilized meaning: You save the VM for example).
not sure about 2012R2 but in 2016 it seems to "eat" disk while running:
this is the VMRS file for selected VM:
this is the VM; running:
For 1.5 TB memory on 2 clustered hosts, i need arrange 1.5 TB on SAN storage which i do not want..
As I said, the space doesn't actually get taken up, unless you save the VM. So, to be able to keep a working VM in case something goes terribly wrong, you DO need to take that space being actually allocated into account from the start. If that's not what you want, well, that's how Hyper-V does it's thing. You're only option then would be to look for a different Hypervisor which does things differently (VMWare for example, although with that you get swapdisk-space to take into account).
You can set the clustered VM to shutdown instead of saving it, and you can NOT ever save the VM yourself but shut it down instead, and you can make sure to never use a "Quick migration" (which would save the VM) to prevent that space from ever getting allocated, but then still. In case the cluster somehow decides to go save the VM nevertheless, the space will get allocated, for the amount of the actual current Memory Demand + a little overhead.
Simply put: If your VM uses 700 Gbytes of Memory, even you have set it at 1.5 Tbytes of Memory total, then saving the VM would give you a VMRS-file of a little over 700 Gbytes. From VM start until save, the file gets created at start, but does NOT actually get allocated. It will roughly show the size of the current Memory Demand, not the amount of memory set. So if your VM starts using less, say you stop all the DBs inside the VM, your memory demand drops, and so would the size of this file. You can test that if you literally do that. Give the VM 700 Gbytes of mem. start it up, see the VMRS-file being created for 700 Gbytes. Then, stop the DBs, make the VM just use a little, say, 2Gbytes of mem., then save the VM. You'll see that when the save is done, the VMRS-file all of a sudden will be around 2Gbytes in size. Then, when you restore the VM, it will show to be 700 Gbytes again all of a sudden (But in reality on the storage, only 2 Gbytes is actually allocated so far).
Thanks for the detailed information, wish these were mentioned in the docs.
Would be nice to have the option though: not saving a VM (and be able to just live migrate) if VM fails just stop/start. Could be useful for read-heavy work loads.
Anyhow, if anyone from product team reads along please update the docs first, consider this option also.
You could post feedback to the following site. Microsoft engineering teams would monitor the feedbacks and may improve the products.
We plan to use hyper v (on Windows Srv 2016) guests to run SSAS tabular model DBs with lots of memory but the VMRS file for the guest with big memory allocated becomes a storage problem: it grows as the memory grows. We are testing this on a hyper v cluster; we calculated storage for DW (from which SSAS reads). But the VMRS files for guests keeps getting bigger. Assuming to utilize ~700 GB of memory we will need 700+GB of disk space and i could not find it mentioned on Windows Server 2016 docs (neither in hyper v or planning sections). Dynamic or static memory does not effect the problem; you have to tax your storage with the amount of memory you provide to the guest.
The question is: is there a way to safely disable VMRS file for hyper v guests in Windows Server 2016; i do not want to allocate disk space for the memory i provide to the guest.
Supported virtual machine configuration versions
Using the PowerShell cmdlet Get-VMHostSupportedVersion you can see what virtual machine configuration versions your Hyper-V Host supports. When you create a virtual machine, it's created with the default configuration version. To see which virtual machine configuration versions your Hyper-V Host supports and what the default is, run the following command.
If you need to create a virtual machine that you can move to a Hyper-V Host that runs an older version of Windows, use the New-VM cmdlet with the -Version parameter. For example, to create a virtual machine named "WindowsCV5" with configuration version 5.0, run the following command:
You can only import a virtual machine if the Hyper-V host supports that configuration version. Typically, this means that you can import a virtual machine to a Hyper-V host running a newer version of Hyper-V, but you cannot import a virtual machine created on a newer version of Hyper-V to an older version of Hyper-V.
If the VM's configuration version is not listed as supported for your Hyper-V host OS in the table below, you either have to upgrade the VM configuration version to a newer version or create a new VM of the same generation using the existing virtual hard disks before you can start the VM.
Answers
The question is: is there a way to safely disable VMRS file for hyper v guests in Windows Server 2016; i do not want to allocate disk space for the memory i provide to the guest.
I think you misinterpreted the answer provided by TheOnlyWizard, because the answer is 'yes'. Configure your VMs to not save state upon host shutdown. That configuration will not allocate any disk space for memory provided to the guest.
- Edited by Tim Cerling MVP Thursday, February 16, 2017 1:35 PM
- Marked as answer by AhmetKuru Monday, February 20, 2017 9:00 AM
Why should I upgrade the virtual machine configuration version?
When you move or import a virtual machine to a computer that runs Hyper-V on Windows Server 2019, Windows Server 2016, or Windows 10, the virtual machine's configuration isn't automatically updated. This means that you can move the virtual machine back to a Hyper-V host that runs a previous version of Windows or Windows Server. But, this also means that you can't use some of the new virtual machine features until you manually update the configuration version.
You can't downgrade a virtual machine configuration version after you've upgraded it.
The virtual machine configuration version represents the compatibility of the virtual machine's configuration, saved state, and snapshot files with the version of Hyper-V. When you update the configuration version, you change the file structure that is used to store the virtual machines configuration and the checkpoint files. You also update the configuration version to the latest version supported by that Hyper-V host. Upgraded virtual machines use a new configuration file format, which is designed to increase the efficiency of reading and writing virtual machine configuration data. The upgrade also reduces the potential for data corruption in the event of a storage failure.
The following table lists descriptions, file name extensions, and default locations for each type of file that's used for new or upgraded virtual machines.
Virtual machine file types | Description |
---|---|
Configuration | Virtual machine configuration information that is stored in binary file format. File name extension: .vmcx Default location: C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines |
Runtime state | Virtual machine runtime state information that is stored in binary file format. File name extension: .vmrs and .vmgs Default location: C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines |
Virtual hard disk | Stores virtual hard disks for the virtual machine. File name extension: .vhd or .vhdx Default location: C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Hard Disks |
Automatic virtual hard disk | Differencing disk files used for virtual machine checkpoints. File name extension: .avhdx Default location: C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Hard Disks |
Checkpoint | Checkpoints are stored in multiple checkpoint files. Each checkpoint creates a configuration file and runtime state file. File name extensions: .vmrs and .vmcx Default location: C:\ProgramData\Microsoft\Windows\Snapshots |
All replies
As far as I understand Hyper-V, 2012R2 .BIN files and 2016 VMRS-files are sparse-files, meaning they don''t take up any actual storage unless utilized. (Utilized meaning: You save the VM for example).
not sure about 2012R2 but in 2016 it seems to "eat" disk while running:
this is the VMRS file for selected VM:
this is the VM; running:
For 1.5 TB memory on 2 clustered hosts, i need arrange 1.5 TB on SAN storage which i do not want..
As I said, the space doesn't actually get taken up, unless you save the VM. So, to be able to keep a working VM in case something goes terribly wrong, you DO need to take that space being actually allocated into account from the start. If that's not what you want, well, that's how Hyper-V does it's thing. You're only option then would be to look for a different Hypervisor which does things differently (VMWare for example, although with that you get swapdisk-space to take into account).
You can set the clustered VM to shutdown instead of saving it, and you can NOT ever save the VM yourself but shut it down instead, and you can make sure to never use a "Quick migration" (which would save the VM) to prevent that space from ever getting allocated, but then still. In case the cluster somehow decides to go save the VM nevertheless, the space will get allocated, for the amount of the actual current Memory Demand + a little overhead.
Simply put: If your VM uses 700 Gbytes of Memory, even you have set it at 1.5 Tbytes of Memory total, then saving the VM would give you a VMRS-file of a little over 700 Gbytes. From VM start until save, the file gets created at start, but does NOT actually get allocated. It will roughly show the size of the current Memory Demand, not the amount of memory set. So if your VM starts using less, say you stop all the DBs inside the VM, your memory demand drops, and so would the size of this file. You can test that if you literally do that. Give the VM 700 Gbytes of mem. start it up, see the VMRS-file being created for 700 Gbytes. Then, stop the DBs, make the VM just use a little, say, 2Gbytes of mem., then save the VM. You'll see that when the save is done, the VMRS-file all of a sudden will be around 2Gbytes in size. Then, when you restore the VM, it will show to be 700 Gbytes again all of a sudden (But in reality on the storage, only 2 Gbytes is actually allocated so far).
Thanks for the detailed information, wish these were mentioned in the docs.
Would be nice to have the option though: not saving a VM (and be able to just live migrate) if VM fails just stop/start. Could be useful for read-heavy work loads.
Anyhow, if anyone from product team reads along please update the docs first, consider this option also.
You could post feedback to the following site. Microsoft engineering teams would monitor the feedbacks and may improve the products.
Это уникальное новшество. В Windows Server 2012 R2 Hyper-V можно было копировать файлы в виртуальные машины без сетевой связи с использованием VMBus. В Windows Server 2016 можно задействовать PowerShell Direct для запуска команд PowerShell в виртуальной машине с помощью VM Bus.
Изменения в настройках виртуальной машины
Новые расширения файлов:
• VMCX (Virtual Machine Configuration) — заменяет .xml-файл;
• VMRS (Virtual Machine Runtime State) — заменяет .bin- и .vsv-файл.
Контрольные точки производственных виртуальных машин
Контрольные точки виртуальных машин (в предыдущих версиях — моментальные снимки виртуальных машин) были отличным решением, позволяющим получить состояние виртуальной машины и сохранить его. Если внести изменения и какие-то из них окажутся неудачными, то легко вернуться к моменту создания контрольной точки. Этот механизм не предназначался для производственных целей из-за несовместимости со многими приложениями. Теперь ситуация изменилась: Microsoft обеспечивает его полную поддержку в производственной среде (см. скриншот выше). Сегодня для создания производственной контрольной точки вместо сохраненного состояния используется VSS. Это означает, что восстановление контрольной точки — то же самое, что восстановление системы из резервной копии. С точки зрения пользователя, все осталось как прежде. Производственные контрольные точки включены по умолчанию, но при необходимости можно вернуться к прежним методам. Все же при использовании контрольных точек возникают некоторые проблемы, например рост файла avhdx.
Hyper-V Replica — одно из наиболее примечательных новшеств Windows Server 2012 Hyper-V. В Windows Server 2012 и Windows Server 2012 R2 Hyper-V, если выполнить «горячее» подключение VHDX-файла к виртуальной машине, репликация завершалась неудачей. В Hyper-V 2016 новый виртуальный жесткий диск, добавляемый к реплицируемой виртуальной машине, автоматически подключается к нереплицированному набору. Таким образом, репликация продолжается, а затем можно обновить этот набор в сети с помощью PowerShell. Виртуальная машина автоматически синхронизируется, и работа продолжается без сбоев. Команда для этого следующая:
Читайте также: