Download Microsoft.70-417.TestKing.2018-07-24.691q.tqb

For checkpoints created when the virtual machine is stopped The checkpoint contains the state of the hard disks only. For checkpoints created when the virtual machine is running The checkpoint contains the state of the hard disks and the data in memory. Note: A checkpoint saves the state of each virtual hard disk that is attached to a virtual machine and all of the hard disk's contents, including application data files. For virtual machines on Hyper-V and VMware ESX Server hosts, a checkpoint also saves the hardware configuration information. By creating checkpoints for a virtual machine, you can restore the virtual machine to a previous state.

http://technet.microsoft.com/en-us/library/jj679878.aspx#bkmk_portmirrorWhat's New in Hyper-V Virtual Switch Port Mirroring With Port Mirroring, traffic sent to or from a Hyper-V Virtual Switch port is copied and sent to a mirror port. There are a range of applications for port mirroring an entire ecosystem of network visibility companies exist that have products designed to consume port mirror data for performance management, security analysis, and network diagnostics. With Hyper-V Virtual Switch port mirroring, you can select the switch ports that are monitored as well as the switch port that receives copies of all the traffic. The following examples configure port mirroring so that all traffic that is sent and received by both MyVM and MyVM2 is also sent to the VM named MonitorVM. Set-VMNetworkAdapter VMName MyVM PortMirroring Source Set-VMNetworkAdapter VMName MyVM2 PortMirroring Source Set-VMNetworkAdapter VMName MonitorVM PortMirroring Destination

Backup Operations in Hyper-V No VSS Writer Available? In some cases, you need an Application-consistent backup but there is no VSS writer available. One example of this is MySQL. Hyper-V backups of virtual machines containing MySQL will always result in either a crash consistent or an image-level backup. For MySQL, the latter is probably acceptable as MySQL doesn't perpetually expand the log file. However, if you're using MySQL within a VSS-aware VM, then a Hyper-Vbased backup tool is going to take a crash-consistent backup. MySQL (like any other database system) isn't always recoverable from a crash-consistent backup; tool is going to take a crash-consistent backup. MySQL (like any other database system) isn't always recoverable from a crash-consistent backup; even when recovery is possible, it may be painful. MySQL is just one example; any number of line-of-business Applications could tell a similar tale. In the case of MySQL, one solution is to find a guest-level backup Application that is MySQL- aware and can back it up properly. For Applications for which no backup Application has a plug-in, you may need to have pre- and post-backup scripts that stop services or close Applications. If brief downtime is acceptable, you can disable the Backup item in Hyper-V Integration Services, thereby forcing Hyper-V to save the state of the VM during backup. This technique results in an image-level backup and can be used on any Application that doesn't have a VSS writer.        References: https://www.altaro.com/hyper-v/vss-crash-consistent-vs-application-consistent-vss-backups-post-2-of-2/