Backup Job Fails When CIFS Repository Connection Is Lost

Product version: 11.1

Last modified: 18 September 2025

Problem

When running a backup job to a CIFS repository, if the repository becomes unreachable due to network loss, the job may not always fail as expected. On Windows transporters, the following error message is displayed:

The <repository_name> backup repository location <repository_location> cannot be reached by the <transporter_name> transporter.

Make sure the backup repository location is reachable.

When using a Linux transporter, the job may continue running indefinitely without returning this error message. If the network connection is restored, the job resumes; otherwise, it continues running.

Background

When the transporter is running on Windows, the job fails with the error above, which is the expected behavior. When the transporter is Linux, the job can remain in progress indefinitely until connectivity is restored or the job is manually stopped. This inconsistent behavior may cause jobs to appear stuck and make monitoring more difficult.

Solution

• If possible, use a Windows transporter with CIFS repositories to ensure consistent error handling and automatic job failure when the repository becomes unreachable.

• If using a Linux transporter, be aware that jobs may remain in the running state indefinitely when connectivity to the repository is lost.