Is what normal? There are neither warnings nor errors in that output, it’s simply status messages.
If you haven’t configured GitLab to upload backups to remote storage, it is normal for it to skip it.
In a production environment that has been running for some time, it’s not normal for it not to remove any old backups. But I have a feeling this is a really new setup, in that case there might very well not be any backups that are old enough that the cleanup will delete them.
I’m seeing this issue as well after an upgrade to 14 major version (via omnibus package on CentOS 7). All repositories report the repository skipped error and the backup is SIGNIFICANTLY smaller than previous.
All of that being said, the backup did take a while and the backup file is the same size as all of the others, approximately.
I installed though the official tagged docker images and have the following versions:
GitLab Shell: 13.19.1
GitLab Workhorse: 14.2.4
GetLab API: 4
I am having the same issue. I just upgraded to 14.3.2 and the issue persists. I have tried various solutions like using the rails console to recall repository sizes and invalidate caches. Nothing seems to work. Almost every repository with imported from gitea is not backing up. And a couple of new ones are doing the same.
I don’t think that’s the same error (the previous posts mostly are about projects being skipped when taking backups), please don’t pollute threads by posting other problems to them.
In making a new thread with your issue: If those lines simply saying “.” are your work, please try to find the actual errors and include them (the output can be really long, so trying to shorten it is a good thing).
I’m migrating my repositories from another platform to Gitlab. The version of gitlab installed on Ubuntu 20.04 LTS is 14.4.1 the same bug is reported. What I found strange is that the repositories are not empty, and also when restoring on another server they work.
Guys, I believe it’s correct. Inside the repositories there is the wiki feature, apparently it is also versioned. When creating a wiki in one of the repositories where the warning was presented, the message stopped occurring. I restored a backup and everything worked as expected.