Failed to resolve attachment in Confluence Server storage

Attachment Metadata Mismatch

In Confluence Server 7.x, a discrepancy can occur between the database index and the physical home directory. This typically manifests when a database record for an attachment persists, but the corresponding file is missing from the local file system.

Storage Bottlenecks and Latency

The attachment download component interacts directly with the file system, making disk I/O a primary factor in retrieval performance. During high-concurrency events, the balance between database metadata overhead and file system latency becomes a critical architectural consideration.

When physical files are deleted or shifted during incomplete backup restorations, the system may return a 404 Not Found error despite the attachment appearing in the UI.

• How does Confluence Server handle the synchronization between the database index and the physical storage to prevent stale attachment references?
• What is the documented behavior for resolving these mismatches without manual file system intervention?