I’ve recently gone through a complete migration of my server setup that involved reformatting the storage and moving from ext4 to XFS – not just for Nextcloud AIO, but for the entire Docker-based infrastructure.
In my case, I prepared a detailed step-by-step guide covering:
- Full backup of all Docker volumes (including Nextcloud AIO),
- Selected folders from the home directory (which contained configuration files and environment data for various containers),
- All persistent Docker volumes from
/var/lib/docker/volumes/, - And most importantly: the local backup drive was formatted as XFS, not EXT4, to ensure proper preservation of permissions, ownership (UID/GID), ACLs, and extended attributes when syncing data using
rsync.
Based on the error you’re encountering (“Appdata is not present…” and DNS resolution problems inside containers), it’s likely the restored data or volume structure is not aligned with what Nextcloud AIO expects — especially if the data directory path or structure changed during or after reinstallation. AIO is quite strict about that.
If it helps, I shared my full migration process on the forum — including the exact rsync commands (with all necessary flags), Proxmox VM settings (ballooning, IO thread), and how I reinstalled Ubuntu Server 24.04 on XFS. It might give you a clearer baseline to recover or start clean while preserving everything.
Migrating Nextcloud AIO Docker Server from ext4 to XFS
Note: This post was written with the help of an AI assistant as a writing aid only. The opinions, solutions, and technical recommendations are fully based on my personal experience.
More about how and why I use AI to write forum posts:
Is there limitations to installing Nextcloud via CT template on Proxmox - #4 by vawaver