![]() The following table describes network ports that must be opened to ensure proper communication with mail servers. Used to communicate with S3 compatible object storage. Used to communicate with IBM Cloud object storage. Used to communicate with Google Cloud storage through the following endpoints:Īll cloud endpoints are specified in this Google article. For more details, see also this Microsoft article. The actual list of addresses can be found in the certificate itself. ![]() ![]() .net (for Government region)Ĭonsider that the part of the address must be replaced with your actual storage account URL that can be found in the Azure management portal.Ĭonsider that certificate verification endpoints (CRL URLs and OCSP servers) are subject to change.Used to communicate with the Microsoft Azure object storage through the following endpoints: Used to verify the certificate status through the following endpoints:Ĭonsider that certificate verification endpoints (CRL URLs and OCSP servers) are subject to change. *. (for both Global and Government regions)Īll AWS service endpoints are specified in the AWS documentation.Used to communicate with the Amazon S3 object storage through the following endpoints: The following table describes network ports that must be opened to ensure proper communication with Veeam Cloud Connect repositories. If a CIFS (SMB) share is used as a backup repository and a Microsoft Windows server is selected as a gateway server for this CIFS share, these ports must be opened on the gateway Microsoft Windows server.Ĭommunication with Veeam Cloud Connect Repositories For more information, see this Microsoft article. Port 443 is used to connect the target CIFS (SMB) share over QUIC. Ports 137 to 139 are used by backup infrastructure components to communicate using NetBIOS. The full installation utilizes a local database to store configuration and job information by leveraging an embedded SQLite engine (in versions prior to Veeam Agent for Microsoft Windows v6, Microsoft’s SQL. Ports used as a transmission channel from the Veeam Agent computer to the target CIFS (SMB) share. The lightweight installation does not include a local database or any GUI elements so it cannot be managed on the local agent computer. Microsoft Windows server performing the role of a backup repositoryĭynamic RPC port range. For every TCP connection that a job uses, one port from this range is assigned. The management agent is responsible for transmitting commands from Veeam Service. Linux server performing the role of a backup repositoryĭefault range of ports used as data transmission channels. To manage Veeam backup agents in Veeam Service Provider Console, you must deploy two software components on managed computers: This software component acts as a broker between Veeam backup agent and Veeam Service Provider Console. Default port used by Veeam Agent for Microsoft Windows operating in the standalone mode for communication with the Veeam Backup server.ĭata between the Veeam Agent computer and backup repositories is transferred directly, bypassing Veeam backup servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |