Port 2145: LiveVault Bridge — The Backup Watchman

What Port 2145 Does

Port 2145 carries the LiveVault Bridge — a persistent connection maintained by Iron Mountain's LiveVault backup agent. While port 2144 handles the raw transfer of backup data to the vault, port 2145 handles the ongoing conversation: status updates, event notifications, and health reporting back to the LiveVault cloud service.

Iron Mountain calls this the LiveVault Event Notification Protocol. The bridge connection stays open as long as the agent is running, continuously relaying the state of your backups. Think of port 2144 as the truck that delivers the cargo and port 2145 as the radio the driver uses to call back and say "arrived safely."

IANA registered this port under the service name lv-pici.

The LiveVault System

LiveVault is Iron Mountain's managed cloud backup product for servers — a fully hosted solution where an on-premise agent encrypts and transmits data to Iron Mountain's data centers. The system uses a small cluster of ports together:

All three need to be open outbound through a firewall for LiveVault to function correctly. Block 2145 and the agent goes silent — data may still transfer on 2144, but the service loses visibility into whether it succeeded.

Checking What's on This Port

If you see traffic on port 2145 and you're not running LiveVault, it's worth investigating. A few ways to check:

On Linux/macOS:

# See what process is listening on port 2145
sudo lsof -i :2145

# Or with ss (faster on modern Linux)
sudo ss -tlnp sport = :2145

On Windows:

# Show process using port 2145
netstat -ano | findstr :2145

# Then look up the PID
tasklist | findstr <PID>

If nothing is listening, the port is simply idle — normal for most machines.

The Registered Port Range

Port 2145 sits in the registered ports range (1024–49151). These ports require IANA registration but don't need administrator privileges to open, unlike the well-known ports below 1024. The registered range is where purpose-built enterprise software tends to live — backup agents, database connectors, middleware — each claiming a small piece of the address space for their own persistent conversations.