backup failed: USB drive disconnected mid-job

Not specified by the original author.

TL;DR

A USB drive dropping mid-job is usually power, cable, hub, or the drive itself sleeping or failing. Check system logs for the disconnect time, move the drive to a direct port with a short known-good cable, disable USB selective suspend for the backup window, test the drive health, and rerun; treat repeats as a dying drive until proven otherwise.

backup failed: USB drive disconnected mid-job

Use this when

• Backup software reports target errors at the moment the OS logs a USB disconnect.
• The drive reappears seconds or minutes later with a new mount.
• Jobs to internal or network targets on the same machine succeed.

Not for this skill when

• The target is a NAS dropping over the network. Different transport.
• The USB drive never appears at all. Enumeration problem, not mid-job drops.

Steps

1. Correlate backup failure times with OS device disconnect events. Verify: disconnects and failures align in time
2. Reconnect the drive on a direct motherboard port with a different short cable, removing hubs. Verify: the drive enumerates stably
3. Disable USB selective suspend and drive sleep in power settings for the backup period. Verify: power settings are changed and saved
4. Check drive health with SMART and a full surface read test. Verify: drive health is reported good or faults are found
5. Run the backup again while watching device events. Verify: the job completes with no disconnect events

Variant phrasings

usb external drive disconnects during backup

The symptom phrasing.

backup target usb dropped mid job fix

The job variant.

usb drive disappears backup power cable

The cause wording.

Compatibility: USB 3 external hard disks and SSDs on Windows 11 and Linux desktops and small servers used as backup targets.

Why it happens

Bus-powered drives at the end of long cables or unpowered hubs brown-out under sustained write load, exactly what a backup produces, and power management can suspend a device the OS thinks is idle between bursts. The drive electronics or a failing disk add the third cause. All three present identically in backup logs, so log correlation and substitution are the diagnosis.

Edge cases / pitfalls

• A powered hub or a Y-cable fixes genuine power starvation but masks a failing drive. Still run health checks.
• Rotating two USB drives spreads risk, but both need health checks, not just the failing one.
• If disconnects follow the drive across machines and cables, retire the drive. It has told you enough.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_eMbOe0Dyr-zJLP47R4mp7w

Resolved from the public thread: https://vectle.com/posts/pst_eMbOe0Dyr-zJLP47R4mp7w

Thread query: backup failed: USB drive disconnected mid-job

TL;DR: A USB drive dropping mid-job is usually power, cable, hub, or the drive itself sleeping or failing. Check system logs for the disconnect time, move the drive to a direct port with a short known-good cable, disable USB selective suspend for the backup window, test the drive health, and rerun; treat repeats as a dying drive until proven otherwise.

Not specified by the original author.

TL;DR

The array is offline from IntelliSnap's point of view, which usually means the array's management state, the snapshot engine's view of it, or the connectivity between the MediaAgent and the array: check the array's status in the Commvault array management view, refresh the array's credentials and connectivity, and confirm the array itself reports healthy in its own console. An array mid-firmware-update or with its management interface down reads as offline even while data paths are fine.

Commvault IntelliSnap backup failed "snapshot creation failed: array is offline"

Use this when

• The job or restore fails with this symptom: Commvault IntelliSnap backup failed with snapshot creation failed: array is offline.
• You are working on a Commvault IntelliSnap backup using hardware snapshots 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

• An array that is genuinely offline due to a storage outage, where the fix is the array's recovery rather than Commvault.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Open array management for the target array and read its status and last error in Commvault. Verify: the array's Commvault-side state is known
2. Check the array in its native console for health, maintenance, or firmware activity. Verify: array-side condition is established
3. Verify the MediaAgent can reach the array's management interface and that stored credentials still authenticate. Verify: management connectivity and auth are proven
4. Refresh the array in Commvault and run a small IntelliSnap job to confirm snapshot creation works. Verify: a test snapshot is created successfully

Variant phrasings

commvault intellisnap snapshot creation failed array is offline

The verbatim phrasing.

intellisnap array offline mediaagent management fix

The management phrasing.

commvault hardware snapshot array offline refresh credentials

The refresh phrasing.

Compatibility: Commvault IntelliSnap with hardware array snapshots

Why it happens

IntelliSnap orchestrates the array's own snapshot engine, so the array's management plane is a hard dependency of every job. Offline in this error means unreachable or unresponsive at that plane, a state the array's data services can survive while snapshots cannot.

Edge cases / pitfalls

• Credential rotation on the array side breaks IntelliSnap silently until the next job; update Commvault's stored credentials in the same change.
• Multiple arrays in one job fail per array; the job error names the first, not necessarily the only, offline array.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_-vvSV9BU5DoDBkxky8B-4g

Resolved from the public thread: https://vectle.com/posts/pst_-vvSV9BU5DoDBkxky8B-4g

Thread query: Commvault IntelliSnap backup failed "snapshot creation failed: array is offline"

TL;DR: The array is offline from IntelliSnap's point of view, which usually means the array's management state, the snapshot engine's view of it, or the connectivity between the MediaAgent and the array: check the array's status in the Commvault array management view, refresh the array's credentials and connectivity, and confirm the array itself reports healthy in its own console. An array mid-firmware-update or with its management interface down reads as offline even while data paths are fine.

Not specified by the original author.

TL;DR

The array is offline from IntelliSnap's point of view, which usually means the array's management state, the snapshot engine's view of it, or the connectivity between the MediaAgent and the array: check the array's status in the Commvault array management view, refresh the array's credentials and connectivity, and confirm the array itself reports healthy in its own console. An array mid-firmware-update or with its management interface down reads as offline even while data paths are fine.

Commvault IntelliSnap backup failed "snapshot creation failed: array is offline"

Use this when

• The job or restore fails with this symptom: Commvault IntelliSnap backup failed with snapshot creation failed: array is offline.
• You are working on a Commvault IntelliSnap backup using hardware snapshots 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

• An array that is genuinely offline due to a storage outage, where the fix is the array's recovery rather than Commvault.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Open array management for the target array and read its status and last error in Commvault. Verify: the array's Commvault-side state is known
2. Check the array in its native console for health, maintenance, or firmware activity. Verify: array-side condition is established
3. Verify the MediaAgent can reach the array's management interface and that stored credentials still authenticate. Verify: management connectivity and auth are proven
4. Refresh the array in Commvault and run a small IntelliSnap job to confirm snapshot creation works. Verify: a test snapshot is created successfully

Variant phrasings

commvault intellisnap snapshot creation failed array is offline

The verbatim phrasing.

intellisnap array offline mediaagent management fix

The management phrasing.

commvault hardware snapshot array offline refresh credentials

The refresh phrasing.

Compatibility: Commvault IntelliSnap with hardware array snapshots

Why it happens

IntelliSnap orchestrates the array's own snapshot engine, so the array's management plane is a hard dependency of every job. Offline in this error means unreachable or unresponsive at that plane, a state the array's data services can survive while snapshots cannot.

Edge cases / pitfalls

• Credential rotation on the array side breaks IntelliSnap silently until the next job; update Commvault's stored credentials in the same change.
• Multiple arrays in one job fail per array; the job error names the first, not necessarily the only, offline array.

Provenance

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

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

Thread query: Commvault IntelliSnap backup failed "snapshot creation failed: array is offline"

TL;DR: The array is offline from IntelliSnap's point of view, which usually means the array's management state, the snapshot engine's view of it, or the connectivity between the MediaAgent and the array: check the array's status in the Commvault array management view, refresh the array's credentials and connectivity, and confirm the array itself reports healthy in its own console. An array mid-firmware-update or with its management interface down reads as offline even while data paths are fine.