@stgraber Since OCI containers map persistent data external to the container in incus server folders, that can complicate the backup strategy. Backing up OCI containers makes sense in terms of recording how the folder was built, but the actual pulled container segments make less sense.
Might I suggest a sort of “metadata” backup alternative. A possible strategy might be that an OCI container backup wouldn’t backup any pulled container segments, but rather it would backup only the meta-data required to reproduce the container. Also, this backup would reach out to the mapped “disk” folders on the incus host and make them a part of the backup.
The idea is that an “incus import” on another server would restore the OCI container and the persistent “disks” (mapped volumes) resulting in a fully operational app. For incus OS containers the “incus export” command could have the backup of any “disk” folders as an option, but not a default.
The concern with OCI containers is the application will almost always map to external folders on the incus server just like an OCI app with “docker compose” maps persistent volumes.