Mount server (if the mount server is not located on the console)ĭefault range of ports used as data transmission channels. Port used by the process for managing database connections. Port used by the Veeam Backup & Replication console to connect to the backup server only when managing the Veeam Cloud Connect infrastructure. Port used by the Veeam Backup & Replication console to connect to the backup server. The following table describes network ports that must be opened to ensure proper communication with the Veeam Backup & Replication console installed remotely. Veeam Backup & Replication Console Connections If you use third-party solutions to connect to the backup server, other ports may need to be open. Port used to provide REST access to the Veeam Backup & Replication database.ĭefault port used by the Remote Desktop Services. Port used locally on the backup server for communication between Veeam Broker Service and Veeam services and components.
VEEAM BACKUP VCENTER UPDATE
Veeam License Update Server (, )ĭefault port used for license auto-update.
VEEAM BACKUP VCENTER DOWNLOAD
Veeam Update Notification Server ()ĭefault port used to download information about available updates from the Veeam Update Notification Server over the Internet. Port used for communication with the DNS Server. ĭNS server with forward/reverse name resolution of all backup servers For more information, see Microsoft Docs. Port used for communication with Microsoft SQL Server on which the Veeam Backup & Replication configuration database is deployed (if you use a Microsoft SQL Server default instance).Īdditional ports may need to be open depending on your configuration. Microsoft SQL Server hosting the Veeam Backup & Replication configuration database Port used for data transfer to ESXi host.ĭefault port used for connections to vCloud Director.
This port is not required for VMware Cloud on AWS.ĭefault port used for connections to ESXi host. This port is used for communication with vCenter Server 5.x only. Port used to access vCenter Inventory Service (HTTP or HTTPS) and collect vCenter Server tags. If you use vCloud Director, make sure you open port 443 on underlying vCenter Servers.
The snapshot backup is additional only for this very special case we have experienced.Default port used for connections to vCenter Server. With this we are able to recover the vCenter in the case the vCenter gets corrupted. Yes, for this scenario we do the file backup of the vCenter - with the VCSA, not with Veeam. (i'm assuming vcenter and other vm share the same hardware) If I am off base let me hit the base let's assume the case in which VCenter is corrupted and veeam’s task selected vcenter itself as center backup (and consequently the various other vm). Without the original vcenter active and fully functional, the rest of the backups can’t get recovered. You should not back up vCenter with Veeam typically as the newer 7.x should use the file level backups in the appliance then you just reinstall and restore the file backup for recovery. This is where you use the file backups for VCSA and not Veeam for the vCenter if that is what you are referring to. This is from my experience, if one of Legends wants to prove me wrong, so much the better. The only problem I see to keep the vcenter inside the rest of the structure is that if the relative vm goes corrupted, the backups become irrecoverable.
0 kommentar(er)
