| The appliance itself | Web UI (HTTPS) | TCP 8443 from your browsers to the appliance | Nothing to install - open the port on any firewall between you and the appliance. |
| Internet (appliance) | Setup downloads, online license activation | TCP 443 outbound, or through your HTTP proxy | Direct internet access, or the proxy address entered during first-login setup. |
| VMware vCenter / ESXi | vSphere API + SSH | TCP 443 to vCenter / ESXi (API) TCP 22 to each ESXi host (SSH / SFTP) | A vSphere account with rights on the VMs and datastores, and the SSH service enabled on the ESXi hosts (data is read with dd over SSH, and written over SFTP when VMware is the destination). |
| Proxmox VE | Proxmox API + SSH | TCP 8006 (API) TCP 22 to every node (SSH) | An API token or user/password with the needed privileges, and SSH as root (or a user with password-less sudo) on each node. Data is written over SSH. |
| Hyper-V | WinRM over HTTPS or Windows OpenSSH - you choose one per host | TCP 5986 (WinRM over HTTPS) or TCP 22 (Windows OpenSSH) | A dedicated account in Hyper-V Administrators (or a local administrator). Disk data is read through the same connection - no separate file share is needed. Windows OpenSSH must be enabled on the host (the appliance's Documentation has the steps). |
| Hyper-V → Hyper-V (Replica) | Hyper-V's own Replica traffic between your hosts | TCP 80 (Kerberos) or TCP 443 (certificate) between the two Hyper-V hosts, plus the management port above | Replica enabled on the replica server. Hyper-V moves the data itself. |
| Nutanix AHV Beta | Prism Element API (and optionally Prism Central for change tracking) | TCP 9440 to the cluster virtual IP TCP 9440 to Prism Central, if used | A Prism account that can list VMs, take snapshots, and create images and VMs. With Prism Central the same account must be able to create and delete recovery points. |
| Nutanix AHV → AHV Beta | The Prism API on both clusters, plus NFS to the destination storage container | TCP 9440 to both clusters TCP 2049 (NFS) and TCP 111 (port mapper) to the destination cluster | Add the appliance's address to the destination container's Filesystem Whitelist in Prism, then mount the container on the appliance console (Application tools → NFS shares, answer yes to "Is this a Nutanix storage container?"). The replica's disk files live in that container; nothing is staged on the appliance. |
| Live mount (Protection) | NBD with TLS from the appliance | TCP 10809 from the machines (or the Proxmox / KVM host) you allow to the appliance TCP 22 to the Proxmox node or KVM host when the appliance sets the mount up there | Open the NBD port only to the addresses you allow in the Mount dialog. For "mount the files" or "test VM" the host needs qemu-nbd/qemu-img and an SSH login. |
| Linux KVM (libvirt) | SSH only - virsh -c qemu:///system on the host | TCP 22 to each KVM host | SSH as root, or a user with password-less sudo, on a host with libvirtd, perl and qemu-img; qemu-nbd and the nbd kernel module for qcow2 disks. Nothing is installed. |
| OpenStack | OpenStack APIs, plus SSH to the storage host | The Keystone identity URL and the Nova / Cinder / Glance / Neutron endpoints published in your service catalog (the ports your cloud uses - often 5000 for identity, or 443 behind a load balancer) TCP 22 to the storage host | A project credential (an application credential is recommended). For Ceph, LVM or NFS backends: SSH to a host with the Ceph client (rbd), the cinder-volume host, or a host that mounts the Cinder shares - as root or with password-less sudo. With API only, disks are copied through the API. |