You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of the untested status of this and other backup apps I've developed a new backup app (not forked, but build completely new) and we are approaching RC-status soon. It's in the app-store and well tested, though I recommend it as extra for now (beside your current method of backup), since there are only so many scenario's we can test ourselves. Therefor we invite all to try and test with us and help us improving this new app, which could replace the current options perhaps soon.
Because of the untested status of this and other backup apps I've developed a new backup app (not forked, but build completely new) and we are approaching RC-status soon. It's in the app-store and well tested, though I recommend it as extra for now (beside your current method of backup), since there are only so many scenario's we can test ourselves. Therefor we invite all to try and test with us and help us improving this new app, which could replace the current options perhaps soon.
More information: https://apps.nextcloud.com/apps/ng_backup
The next update will contain a feedback form we would all of you ask to fill in, so it helps us with more field-experiences.
Excellent work! Looking forward to giving this a try.
This is a shot in the dark, but do you know if it might be possible to use NG Backup as a way of migrating from say a Docker-based Nextcloud instance to running the AIO version in a VM?
Also interested in whether it's possible to restore a backup onto a Nextcloud instance that's using S3 primary storage. Not expecting it to, just extremely curious as the migration paths for either are a pain in the bum (but the new ADA engine is pretty sweet!).
Docker → AIO in a VM: that's what the full restore is meant for. Install a fresh AIO with the same Nextcloud major version, install NG Backup, import the recovery kit, add the same backup location and run occ backup:restore:full. The restored server keeps its own database settings, so moving from MariaDB/MySQL to AIO's PostgreSQL is part of the design. To be honest, though, we haven't done a full restore onto a second server in the field yet; that's next on our list. If you try it, please do it next to your current migration path and let us know how it went. One rule: only one server may write to a backup location, so stop backups on the old server once you've made the final one.
S3 primary storage: not yet. NG Backup currently backs up the data directory directly: it refuses to run on an instance with object storage as primary storage, and folders mounted through External storage are not included either. It is on the roadmap: the design reads files through Nextcloud's storage layer instead, which would cover both (with external mounts optional per mount, and never to the same bucket). See section 3.4 of the plan (in Dutch for now).
3. Thanks! On your questions: Docker → AIO in a VM: that's what the full restore is meant for. Install a fresh AIO with the same Nextcloud major version, install NG Backup, import the recovery kit, add the same backup location and run occ backup:restore:full. The restored server keeps its own database settings, so moving from MariaDB/MySQL to AIO's PostgreSQL is part of the design. To be honest, though, we haven't done a full restore onto a second server in the field yet; that's next on our list. If you try it, please do it next to your current migration path and let us know how it went. One rule: only one server may write to a backup location, so stop backups on the old server once you've made the final one. S3 primary storage: not yet. NG Backup currently backs up the data directory directly: it refuses to run on an instance with object storage as primary storage, and folders mounted through External storage are not included either. It is on the roadmap: the design reads files through Nextcloud's storage layer instead, which would cover both (with external mounts optional per mount, and never to the same bucket). See section 3.4 of the plan (in Dutch for now).
Tremendously exciting! Wow!! :- )
I'll try taking this for a spin over the weekend by attempting to restore a Docker instance into AIO; will let you know how it goes! Don't worry, got plenty of backups and will make sure to thoroughly test it! This has made my week!
Great to hear, thanks! A heads-up before you try it: making backups with rc1 (0.9.7) is fine, but for the restore I'd wait for rc2, expected tomorrow. Our own full restore test this week (AIO → plain Nextcloud, about 1 TB) ran into a few things rc1 doesn't handle yet: tables left behind by apps that were removed long ago, apps that must be installed first, and the foreign keys of the Mail app. rc2 fixes these, together with a step-by-step disaster recovery guide. So: back up with rc1 now, restore with rc2.
Activity
dillardblom commentedon Oct 15, 2026
Because of the untested status of this and other backup apps I've developed a new backup app (not forked, but build completely new) and we are approaching RC-status soon. It's in the app-store and well tested, though I recommend it as extra for now (beside your current method of backup), since there are only so many scenario's we can test ourselves. Therefor we invite all to try and test with us and help us improving this new app, which could replace the current options perhaps soon.
More information: https://apps.nextcloud.com/apps/ng_backup
The next update will contain a feedback form we would all of you ask to fill in, so it helps us with more field-experiences.
HammyHavoc commentedon Oct 15, 2026
Excellent work! Looking forward to giving this a try.
This is a shot in the dark, but do you know if it might be possible to use NG Backup as a way of migrating from say a Docker-based Nextcloud instance to running the AIO version in a VM?
Also interested in whether it's possible to restore a backup onto a Nextcloud instance that's using S3 primary storage. Not expecting it to, just extremely curious as the migration paths for either are a pain in the bum (but the new ADA engine is pretty sweet!).
dillardblom commentedon Oct 15, 2026
Thanks! On your questions:
Docker → AIO in a VM: that's what the full restore is meant for. Install a fresh AIO with the same Nextcloud major version, install NG Backup, import the recovery kit, add the same backup location and run
occ backup:restore:full. The restored server keeps its own database settings, so moving from MariaDB/MySQL to AIO's PostgreSQL is part of the design. To be honest, though, we haven't done a full restore onto a second server in the field yet; that's next on our list. If you try it, please do it next to your current migration path and let us know how it went. One rule: only one server may write to a backup location, so stop backups on the old server once you've made the final one.S3 primary storage: not yet. NG Backup currently backs up the data directory directly: it refuses to run on an instance with object storage as primary storage, and folders mounted through External storage are not included either. It is on the roadmap: the design reads files through Nextcloud's storage layer instead, which would cover both (with external mounts optional per mount, and never to the same bucket). See section 3.4 of the plan (in Dutch for now).
HammyHavoc commentedon Oct 15, 2026
Tremendously exciting! Wow!! :- )
I'll try taking this for a spin over the weekend by attempting to restore a Docker instance into AIO; will let you know how it goes! Don't worry, got plenty of backups and will make sure to thoroughly test it! This has made my week!
dillardblom commentedon Oct 17, 2026
Great to hear, thanks! A heads-up before you try it: making backups with rc1 (0.9.7) is fine, but for the restore I'd wait for rc2, expected tomorrow. Our own full restore test this week (AIO → plain Nextcloud, about 1 TB) ran into a few things rc1 doesn't handle yet: tables left behind by apps that were removed long ago, apps that must be installed first, and the foreign keys of the Mail app. rc2 fixes these, together with a step-by-step disaster recovery guide. So: back up with rc1 now, restore with rc2.