PowerProtect Data Manager 19.11 Virtual Machine User Guide

Ensure that the AVS-on-Azure portal meets the following requirements:

• If you have deployed a PowerProtect Data Manager OVA to AVS on Azure or a PowerProtect Data Manager machine image to Azure, it is configured to use a custom DNS server.
  NOTE If you have already deployed PowerProtect Data Manager without a custom DNS server, you will have to redeploy it. For more information, see the PowerProtect Data Manager Deployment Guide or the PowerProtect Data Manager Azure Deployment Guide.
• Forward and reverse DNS lookups exist for PowerProtect Data Manager, vCenter, DDVE, ESXi, and each VM Direct Engine.
• DNS is configured to allow machines in the SDDC to resolve FQDNs to their IP addresses.
• DDVE is running in Azure. If you have more than one DDVE instance running in Azure to perform replication, the DDVE instances have the ability to ping each other using their FQDNs.
  NOTE DDVE running in AVS-on-Azure is not supported.
• DDVE has DNS entries for PowerProtect Data Manager and each VM Direct Engine.
• SDDC is connected to an Azure account, and an Azure cloud and subnet within that account is selected.
• Any DDVE instance on Azure is connected to the SDDC through a Vnet. This action allows the SDDC, the services in the Azure cloud, and subnets in the Azure account to communicate without having to route traffic through the Internet gateway.
• For an AVS-on-Azure environment, open the ESXi server inbound firewall rule with ports 902 and 443 for the PowerProtect-VM proxy solution.

The same Vnets are recommended for access to DDVE instances. For more information about configuring Vnets, see About Virtual Network.