A synchronised subscribed Content Library can contain an item's metadata without its complete payload. If the library downloads content only when needed, the presence of the item in the catalogue is not evidence that its files are available locally for an offline deployment. Check the download mode and the individual item's content state before treating a small size as corruption.
This source-only article uses the vSphere 8.0 Content Library guide. No library was synchronised, content downloaded or VM deployed. The worked example is fictional.
Publisher, subscriber and the two kinds of content
A published library supplies content to a subscribed library. The subscriber may be in the same vCenter instance or another one. The 8.0 synchronisation guide distinguishes item metadata from the item contents stored at the subscriber.
Metadata identifies an item in the library. The payload is the content that must actually be available for its intended use. Under the immediate-download choice, synchronisation covers metadata and content. Under the only-when-needed choice, synchronising the library does not mean that every item's complete content has been downloaded. The guide describes synchronising an individual item when its full content is needed: the item’s Synchronize operation is the targeted content-download remedy. It is a transfer action for separate approval, not an inspection step or a task performed here.
This is a distribution policy, not a statement about whether the guest operating system inside a template is correctly prepared. A perfectly generalised template can still be unavailable at a subscriber that has only its metadata.
Inspect the intended item and its download policy
Prerequisites are read access to both relevant library records where permitted, the exact vCenter build, the source library identity and the intended subscriber storage. Record the template or item identity and revision where shown; similarly named items in two libraries are not interchangeable.
Inspect Menu → Content Libraries → right-click the subscribed library → Edit Settings → Library Content. Read the selection, then cancel without saving. The two choices documented in the sources are Download all library content immediately and Download library content only when needed. Record which is selected without saving a change.
Then inspect the existing synchronisation history and the item's available content information. A library-level success and an item-level payload transfer answer different questions. Preserve the exact task or error and the item it names. Do not retry a full-library synchronisation merely because an item's displayed size is smaller than the source VM.
KB 427886 documents the characteristic case: a template reports only several KB, no library error is present, and the subscriber is configured to download only when needed. That combination supports a metadata-only explanation. The same small size with a failed transfer is a different evidence set and needs its actual transfer error investigated.
Worked example: preparing for a disconnected window
Imagine a branch subscriber that lists linux-base-r7. Its library synchronisation completed yesterday, but its download policy is only-when-needed and the item reports metadata-sized content. The branch plans to lose connectivity to the publisher during maintenance.
The library listing proves awareness of the item. It does not establish that the branch can obtain its payload while disconnected. The practical decision is to arrange an authorised item-content download before the window and verify the specific item transfer, or to retain publisher connectivity until that requirement is met. No bandwidth or completion time can be inferred from the metadata size.
Changing the whole library to immediate download is a broader choice: it can transfer more than the one required item and consume additional subscriber storage. A targeted item operation and a library-wide policy change should therefore not be treated as equivalent remedies. This article explains those choices without executing either.
When the download mode is not the answer
If the library is already set to immediate download, or the item transfer explicitly failed, keep the error and task identity. Investigate the documented source access, transfer and storage prerequisites for that error and build. Do not relabel a permission or transfer failure as expected on-demand behaviour.
The guide also limits which source-library types support which methods. This article assumes a vCenter-published source and does not extend that contract to every third-party catalogue. Template version presentation has its own limits: the guide notes that a subscribed VM-template view does not reproduce the source's full vertical version timeline. A visible latest template is not an archive of every earlier revision.
Acceptance and reversal
Read-only diagnosis is complete when the source, subscriber, selected item, download mode and existing transfer evidence explain the observed size or establish the unresolved failure. Future operational acceptance needs the required item's complete content at the subscriber and an independently approved deployment check appropriate to the maintenance requirement. Neither has been performed here.
Restoring a download-policy setting changes future behaviour; it does not necessarily remove already downloaded content or undo a deployed VM. Content deletion is a separate storage operation, not a generic rollback step. Preserve the required image until its owner has accepted any replacement.
Learning notes
- Catalogue metadata and usable local payload are different things.
- Library synchronisation and an individual item's download have different scopes.
- Offline readiness needs item-specific evidence, not a successful library task alone.
References
- A04-D2: Synchronize the Contents of a Subscribed Library
- A04-S2: Subscribed Content Library full sync does not happen immediately when new content is added.