During setup, Veeam Backup & Replication automatically creates a firewall rule for the runtime process. Note: If you use default Microsoft Windows firewall settings, you do not need to configure dynamic RPC ports. For more information, see this Microsoft KB article. Note: Port 135 is optional to provide faster deployment.ĭefault port used by the Veeam Installer Service.ĭefault port used by the Veeam Data Mover.ĭynamic RPC port range for Microsoft Windows 2008 and later. Required for deploying Veeam Backup & Replication components. For more information about ports that must be opened between the backup proxy and specific backup repository, see Backup Repositories. The following table describes network ports that must be opened to ensure proper communication of backup proxies with other backup components. If you have upgraded from an earlier version of the product, the range of ports from 2500 to 5000 applies to the already added components. Note: This range of ports applies to newly installed Veeam Backup & Replication starting from version 10.0, without upgrade from previous versions. This port is used if the mount server is not located on the console. For every TCP connection that a job uses, one port from this range is assigned. Port used by the Veeam Backup & Replication console to connect to the backup server only when managing the Veeam Cloud Connect infrastructure.ĭ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. The following table describes network ports that must be opened to ensure proper communication with the Veeam Backup & Replication console installed remotely. If you use third-party solutions to connect to the backup server, other ports may need to be open.ĭefault port for communication with REST API service. 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 License Update Server (, )ĭefault port used for license auto-update. 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 communication with PostgreSQL server on which the Veeam Backup & Replication configuration database is deployed. PostgreSQL server hosting the Veeam Backup & Replication configuration database It is also used during guest OS file recovery if you recover files from replicas.ĭefault port used for connections to VMware Cloud Director. Port used for data transfer to ESXi host. This port is not required for VMware Cloud on AWS. If you use VMware Cloud Director, make sure you open port 443 on underlying vCenter Servers.ĭefault port used for connections to ESXi host. We also do all the dedup stuff on the proxy side and yes veeam and the vendors working hard to make such applances better and faster but it will not even come close to an standard server with disks.Communication with Virtualization Serversĭefault port used for connections to vCenter Server. We are using hpe storeonce as a secondary target and even the at the time biggest appliance 5650 with a lot of disks and 2 dedicated physical 48 core proxys will not delivering a “great” performance. Never myself used the retention lock feature but we do have a DD we use for LTR for clients with Cloud Tier also.ġ00% agree as a secondary target for backupcopy jobs with or without GFS or as VTL/replacement for physical tape library datadomain/storeonce/other dedup appliances are working well they are build for backup but can´t hold the todays requirements for restore or anything like “instant recovery”. The only reason is restore from DD is very slow and if this is your only means of backup you need to set expectations for SLAs and RTO cause it will take longer being a deduplication appliance. Everyone has commented on the retention lock but I would suggest not using DD as primary storage and rather secondary storage for longer retention.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |