Transporter Is Not Available or Reachable

Product version: 11.1

Last modified: 01 April 2026

Problem

Backup or recovery jobs fail with errors such as:

  • Transporter is not available or reachable over the network

  • Too many open files

  • Transporter load contention

Jobs may remain in a waiting or failed state due to transporter unavailability.

Background

This issue is typically caused by transporter overload. When multiple jobs start simultaneously, they create a burst load on the transporter.

As a result:

  • The transporter reaches system limits

  • Transporter resources become saturated

  • New jobs cannot acquire transporter load and fail or remain queued

Although typically caused by resource contention, the issue manifests as a network or availability error.

Solution

To resolve and prevent this issue:

  • Schedule jobs at different times to prevent multiple jobs from starting simultaneously and reduce burst load.

  • Adjust job priorities to ensure critical jobs receive transporter resources first.

  • If load management does not resolve the issue, verify your network configuration.