当我被要求选择要备份的项目时,选择Hyper-V树中的条目与选择VM所在的分区之间的区别是什么？
我发现当我离开驱动器D：未经检查时,备份将在大多数日子里失败(但并非总是如此).
那么,当我不选择Hyper-V树而只是驱动D时,是否存在缺点？
由于所有VHD(X)文件和所有设置都存储在驱动器D：中,这应该没有区别,是吗？
备份VM的Hyper-V特定方法使用Volume Shadowcopy Service和VSS请求程序和写入程序,以允许guest虚拟机操作系统智能地参与其自己的备份过程.此方法的成功很大程度上取决于在来宾操作系统上正确安装和启用Integration Services /工具.
如果不通过Hyper-V备份VM,另一种获得VM备份的方法是在每个guest虚拟机上自行设置Windows Server Backup.
如果您只是在VM运行时复制VHD [X]文件,则无法获得VM的良好备份,因为VM处于易失性状态,RAM中的数据等.
至于为什么备份在设置为某个配置时失败,我们需要所有相关的事件和错误.
Backing Up Virtual Machines
Hyper-V uses one of two mechanisms to back up each VM. The default
backup mechanism is called the “Saved State” method,where the VM is
put into a saved state during the processing of the PrepareForSnapshot
event,snapshots are taken of the appropriate volumes,and the VM is
returned to the prevIoUs state during the processing of the
PostSnapshot event.The other backup mechanism is called the “Child VM Snapshot” method,
which uses VSS inside the child VM to participate in the backup. For
the “Child VM Snapshot” method to be supported,all of the following
conditions must be met:Backup (volume snapshot) Integration Service is installed and running in the child VM. The service name is “Hyper-V Volume Shadow
Copy Requestor”.Windows 2000: Backup Integration Service is not supported.
The child VM must be in the running state.
The Snapshot File Location for the VM is set to be the same volume in the host operating system as the VHD files for the VM.
All volumes in the child VM are basic disks and there are no dynamic disks.
All disks in the child VM must use a file system that supports snapshots (for example,NTFS).In general,the process for backing up VMs is the same as described in Overview of Processing a Backup Under VSS. The unique behavior happens when the Hyper-V VSS writer (part of the “Hyper-V Virtual Machine Management” service) processes the PrepareForSnapshot event. If the backup was done using the “Child VM Snapshot” method,there is additional processing done but it is not visible to the child VM.
