Search the Community
Showing results for tags 'verification'.
Found 2 results
-
For over a few years I still cannot get the screenshot verification up and running for a Windows Server (at this moment 2022). The VM Recovery boot is slow as the Windows Server is using iSCSI and because of that a Nakivo proxy is needed. So setup is: Synology NAS -> ESXi proxy -> ESXi recovery host. I already put the VMTools service as delayed start, changed the registry for a longer service timeout (ServicePipeTimeout to 240.000) and set the screenshot settings in Nakivo to: - VMs simultaneously: 1 - Recovery time: 30 min - Screenshot delay: 800 seconds. Is there anything else possible to get this to work? For example put the VMTools service as dependent on another important service?
-
Hi, A bit of background relevant to the question; We have a hypervisor with 48GB RAM. This is intended for only 1 virtual machine, a very high volume MS SQL server on the underlying SSD storage. The guest VM will be using 32GB RAM, so 75% of the RAM on the host. It is not yet backed up by NAKIVO (I will be adding it this weekend to give it time to perform the initial backup). I would like to enable screenshot verification on the VM when I do add it, but this will take the memory usage over what the host has when it does a Flash Boot to verify the screenshot. Is it likely to just fail, or will it spill over to the configured page file? Or is there any way I can set it to have a lesser amount of RAM when it does the Flash Boot? Thanks in advance.
