Recommended deployment for protecting a Hyper-V standalone host

To protect a standalone Hyper-V host, we recommend the following:

• Install the Management service on a separate Windows server with local network access to the standalone host. The Management service server can be a virtual or physical machine that is on the same domain as the Hyper-V standalone host.

• Install the Host service on the standalone host.

This deployment method minimizes the performance impact in the environment and avoids reboots on the standalone host when you install, upgrade or uninstall the Management service. However, if you do not want to install the Management service on a separate server, see Alternate deployment for protecting a Hyper-V standalone host.

Note: You cannot install the Agent for Microsoft Windows on the standalone host. The Windows Agent is not compatible with the Host service.

Alternate deployment for protecting a Hyper-V standalone host

As described in Recommended deployment for protecting a Hyper-V standalone host, we recommend installing the Management service on a separate virtual or physical Windows server with local network access to the standalone host, and installing the Host service on the standalone host.

However, if you do not want to install the Management service on a separate server, you can install both the Management service and Host service on a standalone host. Beginning with Hyper-V Agent 8.84, this is not recommended. A driver required for file and folder restores is now installed with the Management service, and could require the host to be rebooted when you install, upgrade or uninstall the Agent Management service.

Note: You cannot install the Agent for Microsoft Windows on the standalone host. The Windows Agent is not compatible with the Host service.