Question: What are Ports Needed to Configure Log Shipping?
Answer: I thought it would be easy to find that from the internet but looks like it was not as easy as I thought. So, in this blog, we would learn about ports needed for log shipping.
One of my clients was trying to configure Log Shipping in a highly secure environment where most of the things are expected to blocked or restricted. To make sure the configuration of all the applications goes smooth, the security/network have asked for ports which need to be unblocked. As a DBA, they were worried about Log Shipping as they used it extensively.
If the is a firewall configured between the primary server and a standby server, you need to open the following ports on the firewall:
- Port 1433 — This port is required for operations between default instances. This port must be open on both the primary server and a standby server. If you are using a named instance of SQL Server, you must open the port used by the named instance. I personally suggest you choose static port instead of a dynamic port.
- Port 135 — This port is required so that SQL Agent can copy transaction log backup files to the shared folder on the standby server.
- Ports 137, 138, and 139 or 445 — These ports are required to use Uniform Naming Convention (UNC) shares.
These are the only ports that need to be opened for log shipping. As you will be between a firewall, you also want to create firewall exceptions for using SSMS tool as you will be using it to configure Log Shipping. Other Windows services and applications may require additional ports to be opened.
Reference: Pinal Dave (https://blog.sqlauthority.com)