File operations and recovery records
Server mode uses the server catalog directly. Local initialization no longer prepares an organization plan; this article describes an optional local file operation. See server originals and device catalogs.
Preview and execute server migration in Settings → Attachment servers. After upload and readback verification the server holds the authoritative original; migrated local originals are removed, leaving lightweight previews rather than a permanent local originals/ archive. Use Cache locally or open a file to retrieve full local content. HTML project resources do not participate in server migration; relocate legacy ones with scripts/localize_html_attachments.py into Web/ or project assets/ instead of organizing them into _attachments. The .vault-rag/attachment-migrations/ recovery directories below belong to local organization jobs; existing history and recycle records are not removed automatically. Old links resolve inside LeafLoom; other editors are not guaranteed to support them. See server attachments and cache.
Your goal
Rename, move or recycle supported attachments with reference checks, and keep recovery records from earlier versions.
Before you start
Back up the vault before structural changes. Local folder-reorganization entry points remain hidden; server migration is under Settings → Attachment servers. Changing the new-upload destination does not migrate existing originals. See attachment browsing.
Steps
- Select supported files in Attachments and choose rename, move or recycle. Review the proposed destination, discovered note references, file versions and protected resources before confirming.
- Project resources and unsupported server operations remain unavailable; do not force them through another attachment action. Incomplete dependency discovery does not prove that a file has no references.
- Keep previous
.vault-rag/attachment-migrations/<job-id>/records, retained originals/note backups and.vault-rag/trash/while recovery may still be needed. The hidden UI does not delete these records or automatically restart a migration. - Preserve device-private application state, including unsent uploads, server reference mappings and metadata. Do not copy live SQLite databases between devices or delete the whole state folder as a cache. Contact the project with the task ID and sanitized diagnostic when a legacy task needs manual recovery.
What to expect
Only a confirmed, supported operation changes a file. Available actions recheck revisions and boundaries. Changing the server used for new attachments leaves old originals and metadata bindings in place.
If it does not work
Stop when a preview reports changed versions, ambiguous references, protected resources or an unavailable server capability. Keep recovery materials and retry only after resolving the cause. Download-cache cleanup is not a backup and does not remove NAS originals.