Secondary copy is not no longer transferred.
Probable causes
- WAN
- Soo.
- West Bank.
Verifications.
- Limit the impact. — Identify whether an endpoint, service, or whole site is affected.
- Collect evidence. — Keep the exact error message, timestamp, and associated logs.
- Test the simplest hypothesis first. — Compare the affected system with a known-good path.
- Correct the confirmed cause and validate the result. — Apply one controlled change at a time and retest.
Solutions.
- Correct the confirmed cause rather than the symptom.
- Document the change and its result.
- Establish monitoring if the fault can recur.
When to escalate?
Escalate if the impact expands, data are at risk, or remediation requires an irreversible change.
Backup Copy transport focus
When a copy job no longer reaches the remote site, identify whether the break is network reachability, name resolution, authentication, repository availability or the backup transport path. A successful ping alone does not prove the copy workflow is usable.
What to verify
- Check the remote repository, gateway or proxy service and confirm that its credentials are still valid.
- Test DNS and the required application ports from the actual backup component that opens the connection.
- Review WAN firewall, VPN and NAT changes made since the last successful copy.
- Inspect the source backup chain for missing restore points or a local job state that prevents the copy from starting.
Resolution path
Restore the failing dependency without recreating the copy job unless its configuration is corrupt. If the remote repository moved, update the supported repository or gateway mapping and rescan it before resuming transfers.
Validation
Run a copy session through to completion and verify that the new restore point is visible and readable at the remote site.