SQL backup job finishes instantly with tiny files

Scenario

A SQL backup job appears to succeed in seconds, but the resulting files are suspiciously small.

Recommended Resolution Path

1. Review SQL Agent job history and the actual backup command output.
2. Confirm the backup target path exists and has enough space.
3. Check whether a copy-only, tail-log, or failed compression context is being misread as success.
4. Always test restore headers and verify database names in the backup chain.

Technician Notes

Confirm the business impact, document the root cause, and capture any preventative follow-up in the PSA or client knowledge base.