Operating system and version (e.g., Ubuntu 24.04):
Docker: Nextcloud AIO
Is this the first time you’ve seen this error? (Yes / No):
Yes
When did this problem seem to first start?
Maybe during last MC update?
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO
Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
As above, basically nothing except current version is available anymore except for a few files that have been edited in the last month or so. Deleted Items folders are empty except for users that have deleted something in the last month. I don’t go into these very often so I have no clue when it first happened, but with nothing older than a month, I’m guessing it was an update to the AIO that did it. I think I’ve done 2 updates in the last month, with the lastest about a week ago.
I have some old versions of a full server backup but it will take a while to restore and see where these sit, but I’m concerned about this going forward if I can’t trust that the versioning system is stable. Is this a problem with the AIO install method, which has been awesome up until now?
So I looked at versions.retention.obligation and it’s set to “auto,30” so I guess it’s deleting anything over 30. I have never altered this setting since I installed the AIO a couple years ago, and I’ve recovered older versions in the past. So at some point this has gotten changed, but I have no clue how. I’m also quite sure I’ve looked at this in the past via OCCWeb and it was just on “auto” before.
I’m currently recovering an old version of the server and I guess I hope that I’ve got a copy in there somewhere.
To be clear how unlikely it is that I’ve changed this setting, I’m working right now to figure out how to fix it, and I’m at a loss since I can’t just down the server and edit config.php like I would have before using the AIO. I’ve never had to do anything in the config file with the AIO before. Edit: found it in the docker volumes.
I would agree with that, as I’ve gone into my backups from over a year ago and the file_versions have never been older than 30 days before that backup date. I must have moved to the AIO about 14 months ago if my backups are any indication.
I must have last done a long term version restore before I converted to AIO. I guess when I’ve done other version restores, I’ve never done it with older files so I didn’t twig to the fact that no versions were “old”.
And for the record, that’s a terrible default IMO, especially since the documentation linked above says the default should be “auto”, which makes sense to me.
I’ve fixed it now, but I’m a little suspicious of what else is going to bite me so I guess I’d better review everything in that config.php because I can’t believe the generic documentation. Been using NC for almost a decade and never had to alter that setting. I don’t use versions often (apparently) but when I do, I’d like to know it’s there.
And for the record, that’s a terrible default IMO, especially since the documentation linked above says the default should be “auto”, which makes sense to me.
I guess it could be documented somewhere on the AIO side. So that’s fair.
Though I’m not sure I’d say it’s a terrible default; just a slightly different one than for a bare metal install. The only difference between auto and auto, 30 is that the former may delete after 30 days (such as if an account gets close to its quota), while the latter always deletes after 30 days.
I can certainly see how it can be confusing across the documentation. It’s challenging to cover all these things, since there are numerous install methods. And some of those methods, such as AIO, are intentionally supposed to be opinionated (unlike bare metal installs, which is what the Admin Manual is centered around).
Haha, yes, I did fix the trash retention with it when I saw what it was. But thanks for the heads up anyway.
Just to my way of thinking, if the space limitations are respected as per the documentation, I’m not sure what the benefit of the changed default is. The containers mount the ncdata folder same as a baremetal install would so it’s not interfering with the performance as a container install (as far as I can determine).
I’m fine with opinionated, but optimistic is maybe going too far. A post-install checklist for administrators might go a long way to opening eyes about opinions that the AIO implements that aren’t the same as the baremetal admin guide.
In any case, I guess I’m suspicious now, but overall the AIO has been a godsend, because the upgrade process is 1000% more trustworthy than I ever experienced on any other method I’ve used NC with in the previous decade.