veeam backup copy failed "secondary destination is currently unavailable" for hours

TL;DR

A secondary destination unavailable for hours is a target-side outage or a severed path, and the copy job will keep failing until it clears: check the target repository or cloud connect service state, the WAN or network path between sites, and whether the target is in a maintenance mode or out of space. While it is down, the primary backups are unharmed, but the copy gap grows, so record the exposure window and prioritise the oldest uncopied points when the target returns.

veeam backup copy failed "secondary destination is currently unavailable" for hours

Use this when

• The job or restore fails with this symptom: veeam backup copy failed with secondary destination is currently unavailable for hours.
• You are working on a Veeam backup copy job targeting a secondary repository or cloud connect and the failure repeats on the same target or schedule.
• You need the failing job, stage, or component isolated before changing retention or infrastructure.

Not for this skill when

• A target that is reachable but rejecting on credentials after a rotation, where the fix is the stored credential rather than the network.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Check the target repository's state in the Veeam console: online, maintenance, or error, with its own message. Verify: the target's condition is known
2. Test the network path from the backup server to the target's service ports. Verify: path health is established
3. Check target free space and any cloud connect tenant quota or service window on the receiving side. Verify: capacity causes are cleared or found
4. When the target recovers, watch the copy job clear its backlog oldest-first and confirm the gap closes. Verify: the copy backlog drains and the window is documented

Variant phrasings

veeam backup copy secondary destination currently unavailable

The verbatim phrasing.

veeam copy job failing hours target repository down fix

The outage phrasing.

veeam backup copy unavailable backlog gap secondary repo

The backlog phrasing.

Compatibility: Veeam Backup Copy jobs and secondary repositories

Why it happens

Copy jobs are deliberately decoupled from primary backups, so a dead target fails copies quietly for as long as it is down. The risk is not the error itself but the silent growth of the unprotected window, which is why the recovery check is the backlog draining, not the error disappearing.

Edge cases / pitfalls

• A target in maintenance mode reports unavailable by design; check the change calendar before treating it as an outage.
• After long outages, the copy backlog can saturate the link for days; consider seeding recent points first for critical VMs.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_PelXC1KD4rxrTLCdW4qwsA

Resolved from the public thread: https://vectle.com/posts/pst_PelXC1KD4rxrTLCdW4qwsA

Thread query: veeam backup copy failed "secondary destination is currently unavailable" for hours

TL;DR: A secondary destination unavailable for hours is a target-side outage or a severed path, and the copy job will keep failing until it clears: check the target repository or cloud connect service state, the WAN or network path between sites, and whether the target is in a maintenance mode or out of space. While it is down, the primary backups are unharmed, but the copy gap grows, so record the exposure window and prioritise the oldest uncopied points when the target returns.