File storage ยท October 30, 2026
Transparent file tiering with ObjectVeil
ObjectVeil keeps active file contents on local storage while using an object-storage backend for the larger archive. Perforce is an included integration.
Local files and remote contents
Applications access supported file paths through the file-access library. A cache hit uses local contents; a miss asks the daemon to retrieve and verify the contents from the backend. Operators configure the cache limits and storage policy.
The available backends are Amazon S3, Azure Blob, Google Cloud Storage, and NFS. Small-file packing and parallel multipart transfer settings are shared between the cache and migration tool.
Copying existing data
ObjectVeil Migrate uploads an existing file tree into the cache's storage layout and can restore contents to a local destination. For an online source, it checks for busy or changing files and defers them. Reports and resumable progress records make outstanding work visible.
A scan of a running server is not an atomic backup of the whole application. Preserve the application's database, journal, and other metadata using its supported backup procedure. Uploading archive contents alone does not replace those backups.
Planning an upgrade
Follow the installation and upgrade guide before replacing any component. Stop the daemon and application processes, apply the documented writer fence, retain the existing configuration and state, and deploy the matching daemon and file-access library together.
Application compatibility
ObjectVeil targets Linux and supported file operations. Validate other applications' read, write, and locking behavior before deploying them. Writes upload asynchronously, so unuploaded data remains dependent on the local machine.